< draft-mariblanca-aaa-eap-lla-00.txt   draft-mariblanca-aaa-eap-lla-01.txt >
AAA Working Group David Mariblanca AAA Working Group David Mariblanca
INTERNET-DRAFT Ericsson INTERNET-DRAFT Ericsson
Expires: November 2004 Expires: December 2004
May, 2004 June, 2004
EAP lower layer attributes for AAA protocols EAP lower layer attributes for AAA protocols
<draft-mariblanca-aaa-eap-lla-00.txt> <draft-mariblanca-aaa-eap-lla-01.txt>
Status of this memo Status of this memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 1, line 33 skipping to change at page 1, line 33
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or cite them other than as "work in progress". material or cite them other than as "work in progress".
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/lid-abstracts.txt http://www.ietf.org/ietf/lid-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This document is an individual submission to the IETF. Comments This document is an individual submission to the IETF. Comments
should be directed to the authors. should be directed to the author.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
This document defines a new AVP to be transported in RADIUS or This document defines a new AVP to be transported in RADIUS or
Diameter when EAP is carried over these protocols. The purpose of Diameter when EAP is carried over these protocols. The purpose of
this AVP is to determine which layer 2 protocol was used to this AVP is to determine which layer 2 protocol was used to
skipping to change at page 4, line 4 skipping to change at page 4, line 5
This AVP MAY be included in the Diameter-EAP-Request (DER) Command. This AVP MAY be included in the Diameter-EAP-Request (DER) Command.
It MUST NOT be present in the Diameter-EAP-Answer (DEA) Command. It MUST NOT be present in the Diameter-EAP-Answer (DEA) Command.
In case of RADIUS, the EAP-Lower-Layer AVP MAY be included in the In case of RADIUS, the EAP-Lower-Layer AVP MAY be included in the
Access-Request message, and MUST NOT be included in any other RADIUS Access-Request message, and MUST NOT be included in any other RADIUS
message. message.
The format of the EAP-Lower-Layer AVP is shown below. The format of the EAP-Lower-Layer AVP is shown below.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|EAP-Lower-Layer| Length = 1 | Underlying Protocol | |EAP-Lower-Layer| Length = 1 | Underlying Protocol |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The values for this attribute are: The values for this attribute are:
Protocol Value Protocol Value
PPP 1 PPP 1
802.1X 2 802.1X 2
IKEv2 3 IKEv2 3
PANA 4 PANA 4
4. IANA considerations
New values for the EAP-Lower-Layer AVP are to be allocated by First
Come First Served [RFC 2434], in accordance with RADIUS and Diameter
IANA guidelines [RFC 3575] [RFC 3588].
4. Acknowledgements 4. Acknowledgements
The author would like to thank Hannes Tschofenig, Bernard Aboba and The author would like to thank Hannes Tschofenig, Bernard Aboba and
Jari Arkko for their help in the creation and edition of this Jari Arkko for their help in the creation and edition of this
document. document.
5. Authors' Addresses 5. Authors' Addresses
David Mariblanca David Mariblanca
Ericsson Espana S.A. Ericsson Espana S.A.
Via de los Poblados 13
28033 Madrid 28033 Madrid
Spain Spain
Phone: +34-91-339-3422 Phone: +34-91-339-3422
Email: david.mariblanca@ericsson.com Email: david.mariblanca@ericsson.com
6. References 6. Normative References
[EAP] Blunk, L., Vollbrecht, J., Aboba, B., Carlson, J. and H. [EAP] Blunk, L., Vollbrecht, J., Aboba, B., Carlson, J. and H.
Levkowetz, "Extensible Authentication Protocol (EAP)", Levkowetz, "Extensible Authentication Protocol (EAP)",
draft-ietf-eap-rfc2284bis-09 (work in progress), February draft-ietf-eap-rfc2284bis-09 (work in progress), February
2004. 2004.
[DEAPapp] P. Eronen, T. Hiller, G. Zorn, “Diameter Extensible [DEAPapp] P. Eronen, T. Hiller, G. Zorn, ôDiameter Extensible
Authentication Protocol (EAP) Application”, draft-ietf- Authentication Protocol (EAP) Applicationö, draft-ietf-
aaa-eap-05.txt (work in progress), April 2004. aaa-eap-07.txt (work in progress), June 2004.
[RFC3579] B. Aboba, P. Calhoun, “RADIUS (Remote Authentication Dial [RFC3575] B. Aboba, ôIANA considerations for RADIUSö, RFC 3575,
July 2003.
[RFC3588] P. Calhoun, J. Loughney, E. Guttman, G. Zorn, J. Arkko,
ôDiameter Base Protocolö, RFC 3588, September 2003
7. Informative References
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998.
[RFC3579] B. Aboba, P. Calhoun, ôRADIUS (Remote Authentication Dial
In User Service) Support For Extensible Authentication In User Service) Support For Extensible Authentication
Protocol (EAP)“, RFC 3579, September 2003 Protocol (EAP)ô, RFC 3579, September 2003.
Full Copyright Statement [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
Full Copyright Statement
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
 End of changes. 12 change blocks. 
13 lines changed or deleted 32 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/