AAA Working Group David Mariblanca INTERNET-DRAFT Ericsson Expires: December 2004 June, 2004 EAP lower layer attributes for AAA protocols Status of this memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or cite them other than as "work in progress". The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/lid-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html This document is an individual submission to the IETF. Comments should be directed to the author. Copyright Notice Copyright (C) The Internet Society (2003). All Rights Reserved. Abstract This document defines a new AVP to be transported in RADIUS or Diameter when EAP is carried over these protocols. The purpose of this AVP is to determine which layer 2 protocol was used to encapsulate the EAP messages at the point they were initiated. TABLE OF CONTENTS 1. Introduction.......................................................3 Mariblanca [Page 1] INTERNET-DRAFT EAP lower layer attributes June, 2004 1.1 Abbreviations....................................................3 2. Conventions........................................................3 3. Attributes.........................................................3 3.1 EAP-Lower-Layer AVP................................................3 4. Acknowledgements...................................................5 5. Authors' Addresses.................................................5 6. References.........................................................5 Mariblanca [Page 2] INTERNET-DRAFT EAP lower layer attributes June, 2004 1. Introduction This document defines a new AVP to be transported in RADIUS or Diameter when EAP [EAP] is carried over these protocols. This information will be useful for the EAP server to determine which service initiated the EAP procedure. This situation will be common when EAP is used over a layer 2 protocol for which the EAP server is not one of the termination points. The access node where EAP is decapsulated from such layer 2 protocol will package the EAP messages over RADIUS [RFC3579] or Diameter [DEAPapp] and send them to the EAP server, which in some situations will need to have some information about the origin of the EAP messages. For example, the EAP server may wish to allow/deny access from a given lower layer for every subscriber. The AVP defined in this document will provide this information to the EAP server. The EAP server MAY use this AVP at the moment of the authorization decision, and once this decision is taken, the rest of the exchange SHOULD NOT be affected. 1.1 Abbreviations EAP Extensible Authentication Protocol 2. Conventions The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when they appear in this document, are to be interpreted as described in [RFC2119]. 3. Attributes 3.1 EAP-Lower-Layer AVP The EAP-Lower-Layer AVP indicates the layer 2 protocol which has been used to carry EAP messages. This attribute MAY be used by access devices acting as EAP pass-through authenticators, such as network access servers passing EAP from a PPP interface to a RADIUS or DIAMETER interface. This AVP MAY be included in the Diameter-EAP-Request (DER) 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 Access-Request message, and MUST NOT be included in any other RADIUS message. The format of the EAP-Lower-Layer AVP is shown below. 0 1 2 3 Mariblanca [Page 3] INTERNET-DRAFT EAP lower layer attributes June, 2004 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The values for this attribute are: Protocol Value PPP 1 802.1X 2 IKEv2 3 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]. Mariblanca [Page 4] INTERNET-DRAFT EAP lower layer attributes June, 2004 4. Acknowledgements The author would like to thank Hannes Tschofenig, Bernard Aboba and Jari Arkko for their help in the creation and edition of this document. 5. Authors' Addresses David Mariblanca Ericsson Espana S.A. 28033 Madrid Spain Phone: +34-91-339-3422 Email: david.mariblanca@ericsson.com 6. Normative References [EAP] Blunk, L., Vollbrecht, J., Aboba, B., Carlson, J. and H. Levkowetz, "Extensible Authentication Protocol (EAP)", draft-ietf-eap-rfc2284bis-09 (work in progress), February 2004. [DEAPapp] P. Eronen, T. Hiller, G. Zorn, ôDiameter Extensible Authentication Protocol (EAP) Applicationö, draft-ietf- aaa-eap-07.txt (work in progress), June 2004. [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 Protocol (EAP)ô, RFC 3579, September 2003. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. Mariblanca [Page 5] INTERNET-DRAFT EAP lower layer attributes June, 2004 Full Copyright Statement Copyright (C) The Internet Society (2004). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Mariblanca [Page 6]