From 4bfd864f10b68b71482b35c818559068ef8d5797 Mon Sep 17 00:00:00 2001 From: Thomas Voss Date: Wed, 27 Nov 2024 20:54:24 +0100 Subject: doc: Add RFC documents --- doc/rfc/rfc4603.txt | 283 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 283 insertions(+) create mode 100644 doc/rfc/rfc4603.txt (limited to 'doc/rfc/rfc4603.txt') diff --git a/doc/rfc/rfc4603.txt b/doc/rfc/rfc4603.txt new file mode 100644 index 0000000..29ba0a5 --- /dev/null +++ b/doc/rfc/rfc4603.txt @@ -0,0 +1,283 @@ + + + + + + +Network Working Group G. Zorn +Request for Comments: 4603 G. Weber +Category: Informational R. Foltak + Cisco Systems + July 2006 + + + Additional Values for the + NAS-Port-Type Attribute + +Status of This Memo + + This memo provides information for the Internet community. It does + not specify an Internet standard of any kind. Distribution of this + memo is unlimited. + +Copyright Notice + + Copyright (C) The Internet Society (2006). + +IESG Note + + This RFC is not a candidate for any level of Internet Standard. The + IETF disclaims any knowledge of the fitness of this RFC for any + purpose and in particular notes that the decision to publish is not + based on IETF review for such things as security, congestion control, + or inappropriate interaction with deployed protocols. The RFC Editor + has chosen to publish this document at its discretion. Readers of + 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 of values for the NAS-Port-Type RADIUS + Attribute. + +Table of Contents + + 1. Introduction ....................................................2 + 2. NAS-Port-Type Values ............................................2 + 3. IANA Considerations .............................................2 + 3.1. Attribute Values ...........................................2 + 4. Security Considerations .........................................2 + 5. References ......................................................3 + 5.1. Normative References .......................................3 + 5.2. Informative References .....................................3 + + + + + +Zorn, et al. Informational [Page 1] + +RFC 4603 New NAS-Port-Type Values July 2006 + + +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] over Ethernet) + + 33 PPPoEoVLAN (PPP over Ethernet [RFC2516] over VLAN) + + 34 PPPoEoQinQ (PPP over Ethernet [RFC2516] over IEEE 802.1QinQ) + +3. IANA Considerations + +3.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. + + + + + + + + + + + + + +Zorn, et al. Informational [Page 2] + +RFC 4603 New NAS-Port-Type Values July 2006 + + +5. References + +5.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.2. Informative References + + [RADTYP] Internet Assigned Numbers Authority, "RADIUS TYPES", + November 2005, . + + [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. + + + + + + + + + + + + + + + + + + + + + + + + + + +Zorn, et al. Informational [Page 3] + +RFC 4603 New NAS-Port-Type Values July 2006 + + +Authors' Addresses + + Glen Zorn + Cisco Systems + 2901 Third Avenue, Suite 600 + SEA1/5/ + Seattle, WA 98121 + US + + Phone: +1 (425) 344 8113 + EMail: gwz@cisco.com + + + Greg Weber + Cisco Systems + 10850 Murdock Road + KNV/1/ + Knoxville, TN 37932 + US + + 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-6557 + EMail: rfoltak@cisco.com + + + + + + + + + + + + + + + + + + + +Zorn, et al. Informational [Page 4] + +RFC 4603 New NAS-Port-Type Values July 2006 + + +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 Property + + The 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. + +Acknowledgement + + Funding for the RFC Editor function is provided by the IETF + Administrative Support Activity (IASA). + + + + + + + +Zorn, et al. Informational [Page 5] + -- cgit v1.2.3