[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: WGLC draft-ietf-radext-digest-auth-01
- To: "Beck01, Wolfgang" <BeckW@t-systems.com>
- Subject: Re: WGLC draft-ietf-radext-digest-auth-01
- From: Bernard Aboba <firstname.lastname@example.org>
- Date: Mon, 21 Mar 2005 22:06:15 -0800 (PST)
- Cc: email@example.com
- In-reply-to: <76C27E1CE3FFC847B4D51C645D6F42AA15FE7D@E9JDF>
- References: <76C27E1CE3FFC847B4D51C645D6F42AA15FE7D@E9JDF>
> now that the WGLC has ended, what are the next steps? Do I need to
> submit the draft to the IESG now?
The IETF process has a number of steps between completion of WGLC and
publication as an RFC. These steps include:
a. Addressing WGLC issues. The Issues list indicates that two issues were
not resolved in DIGEST-01 (Issues 7 and 11). Plus in addition, there are
4 new issues filed. See http://www.drizzle.com/~aboba/RADEXT/ for
b. Chair review. Under the PROTO process, the WG Chairs need to review a
document and verify that it is acceptable before forwarding to the IESG.
For my review, see:
c. AD review. The Area Director needs to complete a review prior to
consideration by the IESG as a whole.
d. IETF Last Call. This provides an opportunity for the IETF community to
review and comment on the document.
e. IESG review. Here the IESG reviews the document.
f. DISCUSS comment resolution.
g. RFC Editor Review.
h. IANA Review.
to unsubscribe send a message to firstname.lastname@example.org with
the word 'unsubscribe' in a single line as the message text body.