W3C home > Mailing lists > Public > public-web-security@w3.org > January 2013

Fwd: Call for Comment: "Issues in Identifier Comparison for Security Purposes"

From: Thomas Roessler <tlr@w3.org>
Date: Wed, 9 Jan 2013 21:52:40 +0100
Message-Id: <5163CFE7-E88A-45C3-95EA-E11152157658@w3.org>
To: public-web-security <public-web-security@w3.org>
This looks like a document that might be worth reviewing from a Web security perspective.

Regards,
-- 
Thomas Roessler, W3C <tlr@w3.org> (@roessler)



Begin forwarded message:

> From: IAB Chair <iab-chair@iab.org>
> Subject: Call for Comment: "Issues in Identifier Comparison for Security Purposes"
> Date: January 9, 2013 21:42:34 +0100
> To: ietf-announce@ietf.org
> 
> This is an announcement of an IETF-wide Call for Comment on 'Issues in Identifier Comparison for Security Purposes'. 
> 
> The document is being considered for publication as an Informational RFC within the IAB stream, and is available for inspection here: 
> http://tools.ietf.org/html/draft-iab-identifier-comparison
> 
> The Call for Comment will last until February 10, 2013. Please send comments to iab at iab.org or submit them via TRAC (see below). 
> =============================================================== 
> Submitting Comments via TRAC 
> 1. To submit an issue in TRAC, you first need to login to the IAB site on the tools server: 
> http://tools.ietf.org/wg/iab/trac/login 
>  
> 2. If you don't already have a login ID, you can obtain one by navigating to this site: 
> http://trac.tools.ietf.org/newlogin 
>  
> 3. Once you have obtained an account, and have logged in, you can file an issue by navigating to the ticket entry form: 
> http://trac.tools.ietf.org/wg/iab/trac/newticket 
>  
> 4. When opening an issue: 
> a. The Type: field should be set to "defect" for an issue with the current document text, or "enhancement" for a proposed addition of functionality (such as an additional requirement). 
> b. The Priority: field is set based on the severity of the Issue. For example, editorial issues are typically "minor" or "trivial". 
> c. The Milestone: field should be set to milestone1 (useless, I know). 
> d. The Component: field should be set to the document you are filing the issue on. 
> e. The Version: field should be set to "1.0". 
> f. The Severity: field should be set to based on the status of the document (e.g. "In WG Last Call" for a document in IAB last call) 
> g. The Keywords: and CC: fields can be left blank unless inspiration seizes you. 
> h. The Assign To: field is generally filled in with the email address of the editor. 
>  
> 5. Typically it won't be necessary to enclose a file with the ticket, but if you need to, select "I have files to attach to this ticket". 
>  
> 6. If you want to preview your Issue, click on the "Preview" button.  When you're ready to submit the issue, click on the "Create Ticket" button. 
>  
> 7. If you want to update an issue, go to the "View Tickets" page: 
> http://trac.tools.ietf.org/wg/iab/trac/report/1 
>  
> Click on the ticket # you want to update, and then modify the ticket fields as required. 
Received on Wednesday, 9 January 2013 20:52:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 January 2013 20:52:43 GMT