idnits 2.17.1 draft-zorn-radius-port-type-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 182. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 159. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 166. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 172. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 5 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 83 has weird spacing: '... listed by IA...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 29, 2006) is 6596 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 4 errors (**), 0 flaws (~~), 3 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Zorn 3 Internet-Draft G. Weber 4 Expires: September 30, 2006 R. Foltak 5 Cisco Systems 6 March 29, 2006 8 Additional Values for the NAS-Port-Type Attribute 9 draft-zorn-radius-port-type-04.txt 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on September 30, 2006. 36 Copyright Notice 38 Copyright (C) The Internet Society (2006). 40 Abstract 42 This document defines a set of new values for the NAS-Port-Type 43 RADIUS Attribute. 45 Table of Contents 47 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 48 2. NAS-Port-Type Values . . . . . . . . . . . . . . . . . . . . . 3 49 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 50 3.1 Attribute Values . . . . . . . . . . . . . . . . . . . . . 3 51 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 52 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 5.1 Normative References . . . . . . . . . . . . . . . . . . . 3 54 5.2 Informative References . . . . . . . . . . . . . . . . . . 4 55 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 4 56 Intellectual Property and Copyright Statements . . . . . . . . 6 58 1. Introduction 60 This document defines a set of new values for the NAS-Port-Type 61 Attribute [RFC2865]. 63 2. NAS-Port-Type Values 65 This document defines new values for the NAS-Port-Type Attribute. 66 This specification concerns the following values: 68 30 PPPoA (PPP over ATM [RFC3336]) 70 31 PPPoEoA (PPP over Ethernet [RFC2516] over ATM) 72 32 PPPoEoE (PPP over Ethernet [RFC2516] over Ethernet 74 33 PPPoEoVLAN (PPP over Ethernet [RFC2516] over VLAN) 76 34 PPPoEoQinQ (PPP over Ethernet [RFC2516] over IEEE 802.1QinQ) 78 3. IANA Considerations 80 3.1 Attribute Values 82 This document is intended to act as a request for allocation of the 83 numbers listed by IANA in the appropriate registry [RADTYP], 84 according to the allocation policy given in [RFC3575]. 86 The values given have already been implemented by at least one vendor 87 without assignment by IANA. 89 4. Security Considerations 91 This specification neither adds to nor detracts from the security of 92 the RADIUS protocol. 94 5. References 96 5.1 Normative References 98 [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, 99 "Remote Authentication Dial In User Service (RADIUS)", 100 RFC 2865, June 2000. 102 [RFC3575] Aboba, B., "IANA Considerations for RADIUS (Remote 103 Authentication Dial In User Service)", RFC 3575, 104 July 2003. 106 5.2 Informative References 108 [RADTYP] Internet Assigned Numbers Authority, "RADIUS TYPES", 109 November 2005, 110 . 112 [RFC2516] Mamakos, L., Lidl, K., Evarts, J., Carrel, D., Simone, D., 113 and R. Wheeler, "A Method for Transmitting PPP Over 114 Ethernet (PPPoE)", RFC 2516, February 1999. 116 [RFC3336] Thompson, B., Koren, T., and B. Buffam, "PPP Over 117 Asynchronous Transfer Mode Adaptation Layer 2 (AAL2)", 118 RFC 3336, December 2002. 120 Authors' Addresses 122 Glen Zorn 123 Cisco Systems 124 2901 Third Avenue, Suite 600 125 SEA1/5/ 126 Seattle, WA 98121 127 US 129 Phone: +1 (425) 344 8113 130 Email: gwz@cisco.com 132 Greg Weber 133 Cisco Systems 134 10850 Murdock Road 135 KNV/1/ 136 Knoxville, TN 37932 137 US 139 Email: gdweber@cisco.com 140 Rich Foltak 141 Cisco Systems 142 2200 East President George Bush Turnpike 143 RCDN6/4/2 144 Richardson, TX 75082 145 US 147 Phone: +1 (469) 255-6557 148 Email: rfoltak@cisco.com 150 Intellectual Property Statement 152 The IETF takes no position regarding the validity or scope of any 153 Intellectual Property Rights or other rights that might be claimed to 154 pertain to the implementation or use of the technology described in 155 this document or the extent to which any license under such rights 156 might or might not be available; nor does it represent that it has 157 made any independent effort to identify any such rights. Information 158 on the procedures with respect to rights in RFC documents can be 159 found in BCP 78 and BCP 79. 161 Copies of IPR disclosures made to the IETF Secretariat and any 162 assurances of licenses to be made available, or the result of an 163 attempt made to obtain a general license or permission for the use of 164 such proprietary rights by implementers or users of this 165 specification can be obtained from the IETF on-line IPR repository at 166 http://www.ietf.org/ipr. 168 The IETF invites any interested party to bring to its attention any 169 copyrights, patents or patent applications, or other proprietary 170 rights that may cover technology that may be required to implement 171 this standard. Please address the information to the IETF at 172 ietf-ipr@ietf.org. 174 Disclaimer of Validity 176 This document and the information contained herein are provided on an 177 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 178 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 179 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 180 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 181 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 182 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 184 Copyright Statement 186 Copyright (C) The Internet Society (2006). This document is subject 187 to the rights, licenses and restrictions contained in BCP 78, and 188 except as set forth therein, the authors retain all their rights. 190 Acknowledgment 192 Funding for the RFC Editor function is currently provided by the 193 Internet Society.