Evaluation: draft-aboba-radius-rfc2869bis - RADIUS Support For Extensible Authentication Protocol (EAP) to Informational

[IESG Secretary <iesg-secretary@ietf.org>]

Last Call to expire on: 2003-3-11

	Please return the full line with your position.

                    Yes    No-Objection  Discuss *  Abstain  


Harald Alvestrand   [   ]     [   ]       [   ]      [   ]
Steve Bellovin      [   ]     [   ]       [   ]      [   ]
Scott Bradner       [   ]     [   ]       [   ]      [   ]
Randy Bush          [ X ]     [   ]       [   ]      [   ]
Patrik Faltstrom    [   ]     [   ]       [   ]      [   ]
Bill Fenner         [   ]     [   ]       [   ]      [   ]
Ned Freed           [   ]     [   ]       [   ]      [   ]
Allison Mankin      [   ]     [   ]       [   ]      [   ]
Thomas Narten       [   ]     [   ]       [   ]      [   ]
Erik Nordmark       [   ]     [   ]       [   ]      [   ]
Jeff Schiller       [   ]     [   ]       [   ]      [   ]
Bert Wijnen         [   ]     [   ]       [   ]      [   ]
Alex Zinin          [   ]     [   ]       [   ]      [   ]


 2/3 (9) Yes or No-Objection opinions needed to pass. 
 
 * Indicate reason if 'Discuss'.
 
^L
To: IETF-Announce:;
Dcc: *******
Cc: RFC Editor <rfc-editor@isi.edu>,
 Internet Architecture Board <iab@iab.org>, 
From: The IESG <iesg-secretary@ietf.org>
Subject: Document Action: RADIUS Support For Extensible 
	   Authentication Protocol (EAP) to Informational
-------------

The IESG has approved the Internet-Draft 'RADIUS Support For Extensible 
Authentication Protocol (EAP)' <draft-aboba-radius-rfc2869bis-09.txt> 
as an Informational RFC. 

This has been reviewed in the IETF but is not the product of an IETF 
Working Group. The IESG contact persons are Randy Bush and Bert Wijnen.

Technical Summary
   
This specification describes RADIUS attributes supporting the Extensible
Authentication Protocol (EAP): EAP-Message and Message-Authenticator.
These attributes now have extensive field experience, and so the purpose
of this document is to provide clarification and resolve interoperability
issues.

As noted in [RFC2865], a Network Access Server (NAS) that does not
implement a given service MUST NOT implement the RADIUS attributes for
that service. This implies that a NAS that is unable to offer EAP service
MUST NOT implement the RADIUS attributes for EAP. A NAS MUST treat a
RADIUS Access-Accept requesting an unavailable service as an Access-Reject
instead.

All attributes are comprised of variable length Type-Length-Value 3-
tuples. New attribute values can be added without disturbing existing
implementations of the protocol.

This document updates RFC 2869.
   
Working Group Summary
   
As this document was not the product of an IETF working group, there
was no discussion in the origin WG. But the document was brought
to the attention of all relevant WGs and a four-week IETF-wide last
call was conducted with no negative comments.
   
Protocol Quality
   
This document was reviewed for the IESG by Randy Bush.