Network Working Group G. ZornInternet-DraftRequest for Comments: 4603 G. WeberExpires: September 30, 2006Category: Informational R. Foltak Cisco SystemsMarch 29,July 2006 Additional Values for the NAS-Port-Type Attributedraft-zorn-radius-port-type-04.txtStatus ofthisThis MemoBy submitting this Internet-Draft, each author represents thatThis memo provides information for the Internet community. It does not specify an Internet standard of anyapplicable patent or other IPR claimskind. Distribution ofwhich he or shethis memo isaware have been or will be disclosed, andunlimited. Copyright Notice Copyright (C) The Internet Society (2006). IESG Note This RFC is not a candidate for any level ofwhich he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documentsInternet Standard. The IETF disclaims any knowledge of theInternet 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 maximumfitness ofsix months and may be updated, replaced, or obsoleted by other documents atthis RFC for anytime. It is inappropriatepurpose and in particular notes that the decision touse Internet-Draftspublish is not based on IETF review for such things asreference materialsecurity, congestion control, orto cite them other than as "work in progress."inappropriate interaction with deployed protocols. Thelist of current Internet-Drafts can be accessedRFC Editor has chosen to publish this document athttp://www.ietf.org/ietf/1id-abstracts.txt. The listits discretion. Readers ofInternet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on September 30, 2006. Copyright Notice Copyright (C) The Internet Society (2006).this document should exercise caution in evaluating its value for implementation and deployment. See RFC 3932 for more information. Abstract This document defines a set ofnewvalues for the NAS-Port-Type RADIUS Attribute. Table of Contents 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 3....................................................2 2. NAS-Port-Type Values. . . . . . . . . . . . . . . . . . . . . 3............................................2 3. IANA Considerations. . . . . . . . . . . . . . . . . . . . . 3 3.1.............................................2 3.1. Attribute Values. . . . . . . . . . . . . . . . . . . . . 3...........................................2 4. Security Considerations. . . . . . . . . . . . . . . . . . . 3.........................................2 5. References. . . . . . . . . . . . . . . . . . . . . . . . . . 3 5.1......................................................3 5.1. Normative References. . . . . . . . . . . . . . . . . . . 3 5.2.......................................3 5.2. Informative References. . . . . . . . . . . . . . . . . . 4 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 4 Intellectual Property and Copyright Statements . . . . . . . . 6.....................................3 1. Introduction This document defines a set of new values for the NAS-Port-Type Attribute [RFC2865]. 2. NAS-Port-Type Values This document defines new values for the NAS-Port-Type Attribute. This specification concerns the following values: 30 PPPoA (PPP over ATM [RFC3336]) 31 PPPoEoA (PPP over Ethernet [RFC2516] over ATM) 32 PPPoEoE (PPP over Ethernet [RFC2516] overEthernetEthernet) 33 PPPoEoVLAN (PPP over Ethernet [RFC2516] over VLAN) 34 PPPoEoQinQ (PPP over Ethernet [RFC2516] over IEEE 802.1QinQ) 3. IANA Considerations3.13.1. Attribute Values This document is intended to act as a request for allocation of the numbers listed by IANA in the appropriate registry [RADTYP], according to the allocation policy given in [RFC3575]. The values given have already been implemented by at least one vendor without assignment by IANA. IANA has registered the numbers listed in Section 2, per this request. 4. Security Considerations This specification neither adds to nor detracts from the security of the RADIUS protocol. 5. References5.15.1. Normative References [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, "Remote Authentication Dial In User Service (RADIUS)", RFC 2865, June 2000. [RFC3575] Aboba, B., "IANA Considerations for RADIUS (Remote Authentication Dial In User Service)", RFC 3575, July 2003.5.25.2. Informative References [RADTYP] Internet Assigned Numbers Authority, "RADIUS TYPES", November 2005,<http://www.iana.org/assignments/radius-types>.<http://www.iana.org/assignments/radius- types>. [RFC2516] Mamakos, L., Lidl, K., Evarts, J., Carrel, D., Simone, D., and R. Wheeler, "A Method for Transmitting PPP Over Ethernet (PPPoE)", RFC 2516, February 1999. [RFC3336] Thompson, B., Koren, T., and B. Buffam, "PPP Over Asynchronous Transfer Mode Adaptation Layer 2 (AAL2)", RFC 3336, December 2002. Authors' Addresses Glen Zorn Cisco Systems 2901 Third Avenue, Suite 600 SEA1/5/ Seattle, WA 98121 US Phone: +1 (425) 344 8113Email:EMail: gwz@cisco.com Greg Weber Cisco Systems 10850 Murdock Road KNV/1/ Knoxville, TN 37932 USEmail:EMail: gdweber@cisco.com Rich Foltak Cisco Systems 2200 East President George Bush Turnpike RCDN6/4/2 Richardson, TX 75082 US Phone: +1 (469) 255-6557Email:EMail: rfoltak@cisco.com Full Copyright Statement Copyright (C) The Internet Society (2006). This document is subject to the rights, licenses and restrictions contained in BCP 78 and at www.rfc-editor.org/copyright.html, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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. Intellectual PropertyStatementThe IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.Disclaimer of Validity This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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. Copyright Statement Copyright (C) The Internet Society (2006). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. AcknowledgmentAcknowledgement Funding for the RFC Editor function iscurrentlyprovided by theInternet Society.IETF Administrative Support Activity (IASA).