[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"



Speaking as an individual (chair hat off), I have read the document and have no issues.


From: bernard_aboba@hotmail.com
To: radiusext@ops.ietf.org
Subject: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"
Date: Fri, 29 Apr 2011 09:43:39 -0700

This is a reminder of an ongoing RADEXT WG last call on "Crypto-Agility Requirements for RADIUS", prior to sending the document to the IESG for publication as an Informational RFC. 

The document is available for inspection here:

http://tools.ietf.org/html/draft-ietf-radext-crypto-agility-requirements


This RADEXT WG last call will last until May 1, 2011.   If you have comments on the document, please file them using the TRAC system.  If you read the draft and have no issues, please state this on the mailing list.  See below for summary of instructions.

 

1.       To submit an issue in TRAC, you first need to login to the RADEXT WG site on the tools server:  http://tools.ietf.org/wg/radext/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/radext/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 WG 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/radext/trac/report/1  Click on the ticket # you want to update, and then modify the ticket fields as required