[LinkSec] Fwd: IETF Status Report
>Envelope-to: tony@jeffree.co.uk
>Date: Sat, 17 May 2003 18:52:08 -0700 (PDT)
>From: Bernard Aboba <aboba@internaut.com>
>To: tony@jeffree.co.uk
>Subject: IETF Status Report
>
>On April 21, 2003 "IEEE 802.1X RADIUS Usage Guidelines" was approved for
>publication as an Informational RFC, and now awaits publication in the
>RFC Editor Queue. Details of the announcement are available at:
>http://www1.ietf.org/mail-archive/ietf-announce/Current/msg23959.html
>
>On May 5, 2003 "IANA Considerations for RADIUS" was approved as an IETF
>Proposed Standard, and now awaits publication in the RFC Editor Queue.
>This document affects the procedures for allocation of RADIUS protocol
>parameters, including those requested by standards organizations such
>as IEEE 802. For details of the announcement, see:
>http://www1.ietf.org/mail-archive/ietf-announce/Current/msg23959.html
>
>On May 15, 2003 "Dynamic Authorization Extensions to Remote Authentication
>Dial In User Service (RADIUS)" was reviewed by the IESG. Initial
>comments have been incorporated into a revised version of the document.
>Since this document is in the final stages of revision in response to
>IESG review, those interested in the document MUST send in
>their comments immediately. The current version of the document is
>available for inspection at:
>http://www.ietf.org/internet-drafts/draft-chiba-radius-dynamic-authorization-20.txt
>
>RFC 2869bis has completed IETF Last Call, and has incorporated initial
>IESG review comments. It now enters a two week waiting period where final
>comments can be incorporated. After June 2, 2003 it will be sent to the
>IESG for final review. Those interested in the document, MUST send in
>their comments immediately. The current version of the document is
>available for inspection at:
>http://www.ietf.org/internet-drafts/draft-aboba-radius-rfc2869bis-22.txt
>
>RFC2284bis has completed EAP WG Last Call, and has incorporated most of
>the last call comments. 3 open issues remain. Open and resolved issues
>with EAP WG documents are tracked here:
>http://www.drizzle.com/~aboba/EAP/eapissues.html
>
>A new version of the draft has been issued and is available here:
>http://www.ietf.org/internet-drafts/draft-ietf-eap-rfc2284bis-03.txt
>
>The EAP State Machine document has been received an initial Chair
>review, for compatibility with RFC 2284bis. Comments are available
>for inspection here:
>
>http://mail.frascone.com/pipermail/public/eap/2003-May/001216.html
>http://mail.frascone.com/pipermail/public/eap/2003-May/001217.html
>http://mail.frascone.com/pipermail/public/eap/2003-May/001218.html
>http://mail.frascone.com/pipermail/public/eap/2003-May/001222.html
Regards,
Tony