idnits 2.17.1 draft-arberg-pppoe-iana-03.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 18. -- Found old boilerplate from RFC 3978, Section 5.5 on line 232. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 243. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 250. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 256. ** 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 issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (October 2006) is 6403 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) ** Downref: Normative reference to an Informational RFC: RFC 2516 Summary: 5 errors (**), 0 flaws (~~), 1 warning (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft Peter Arberg 2 Redback Networks 3 Intended status: Best Current Practice 4 Expiration Date: April 2007 Vince Mammoliti 5 Cisco Systems 7 October 2006 9 IANA Considerations for PPP over Ethernet (PPPoE) 11 draft-arberg-pppoe-iana-03.txt 13 Status of this Memo 15 By submitting this Internet-Draft, each author represents that any 16 applicable patent or other IPR claims of which he or she is aware 17 have been or will be disclosed, and any of which he or she becomes 18 aware will be disclosed, in accordance with Section 6 of BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that other 22 groups may also distribute working documents as Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/1id-abstracts.html 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 This Internet-Draft will expire on April 19, 2007. 37 Copyright Notice 39 Copyright (C) The Internet Society (2006). 41 Abstract 43 This document describes the IANA considerations for the PPP over 44 Ethernet (PPPoE) protocol. 46 Table of Contents 48 1. Introduction............................................... 2 49 1.1 Terminology.............................................. 2 50 1.2 Specification of Requirements............................ 2 51 2. IANA Considerations........................................ 3 52 2.1 Registration Policies for PPPoE TAG Values............... 3 53 2.2 Reserved PPPoE TAG Values................................ 3 54 2.3 Registration Policies for PPPoE Code fields.............. 4 55 2.4 Reserved PPPoE Code fields............................... 4 56 3. Security Considerations.................................... 4 57 4. References................................................. 5 58 4.1 Normative References..................................... 5 59 4.2 Informative References................................... 5 60 Author's Address........................................... 5 61 Full Copyright Statement................................... 6 62 Intellectual Property Statement............................ 6 64 1. Introduction 66 This document provides guidance to the Internet Assigned Numbers 67 Authority (IANA) regarding the registration of values related to 68 the PPP over Ethernet Protocol (PPPoE), defined in [RFC2516], in 69 accordance with BCP 26, [RFC2434]. It also reserves PPPoE TAG 70 values as well as PPPoE packet Code fields which are or have been 71 in use on the Internet. 73 1.1 Terminology 75 The following terms are used here with the meanings defined in 76 BCP 26: "name space", "registration". 78 The following policies are used here with the meanings defined in 79 BCP 26: "First Come First Served". 81 1.2 Specification of Requirements 83 In this document, several words are used to signify the requirements 84 of the specification. These words are often capitalized. The key 85 words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", 86 "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document 87 are to be interpreted as described in [RFC2119]. 89 2. IANA Considerations 91 The PPPoE protocol as defined in [RFC2516] defines two name spaces 92 that requires registration, the PPPoE TAG and the PPPoE Code field. 94 2.1 Registration Policies for PPPoE TAG Values 96 IANA shall set up a registry of "PPPoE TAG Values". These are 97 16-bit values. PPPoE TAG values already in use are specified as 98 reserved in this document, all other TAG values between 0 and 65535 99 are to be assigned by IANA, using the "First Come First Served" 100 policy defined in [RFC2434]. 102 A TAG-Name and a description for the usage as well as a point of 103 contact MUST be provided for any assignment from this registry. 104 A document reference SHOULD also be provided. 106 2.2 Reserved PPPoE TAG Values 108 TAG Value TAG Name Tag Description Reference 109 ----------- ------------------- ---------------------- --------- 110 0 0x0000 End-Of-List See the reference [RFC2516] 112 257 0x0101 Service-Name See the reference [RFC2516] 113 258 0x0102 AC-Name See the reference [RFC2516] 114 259 0x0103 Host-Uniq See the reference [RFC2516] 115 260 0x0104 AC-Cookie See the reference [RFC2516] 116 261 0x0105 Vendor-Specific See the reference [RFC2516] 117 262 0x0106 Credits See the reference [BERRY] 118 263 0x0107 Metrics See the reference [BERRY] 119 264 0x0108 Sequence Number See the reference [BERRY] 121 272 0x0110 Relay-Session-Id See the reference [RFC2516] 122 273 0x0111 HURL See the reference [CARREL] 123 274 0x0112 MOTM See the reference [CARREL] 125 288 0x0120 PPP-Max-Payload See the reference [ARBERG] 126 289 0x0121 IP_Route_Add See the reference [CARREL] 128 513 0x0201 Service-Name-Error See the reference [RFC2516] 129 514 0x0202 AC-System-Error See the reference [RFC2516] 130 515 0x0203 Generic-Error See the reference [RFC2516] 132 2.3 Registration Policies for PPPoE Code fields 134 IANA shall set up a registry of PPPoE Active Discovery Code 135 fields. These are 8-bit values. PPPoE Code fields already in use 136 are specified as reserved in this document, all other Code values 137 between 0 and 255 are to be assigned by IANA, using the 138 "First Come First Served" policy defined in [RFC2434]. 140 A PPPoE Active Discovery packet name and a description for the usage 141 as well as a point of contact MUST be provided for any assignment 142 from this registry. 143 A document reference SHOULD also be provided. 145 2.4 Reserved PPPoE Code fields 147 Code PPPoE Packet Name Description Reference 148 -------- ------------------------------ ----------------- --------- 149 0 0x00 PPP Session Stage See the reference [RFC2516] 151 7 0x07 PADO, Offer See the reference [RFC2516] 152 9 0x09 PADI, Initiation See the reference [RFC2516] 154 10 0x0a PADG, Session-Grant See the reference [BERRY] 155 11 0x0b PADC, Session-Credit Response See the reference [BERRY] 156 12 0x0c PADQ, Quality See the reference [BERRY] 158 25 0x19 PADR, Request See the reference [RFC2516] 159 101 0x65 PADS, Session-confirmation See the reference [RFC2516] 161 167 0xa7 PADT, Terminate See the reference [RFC2516] 163 211 0xd3 PADM, Message See the reference [CARREL] 164 212 0xd4 PADN, Network See the reference [CARREL] 166 3. Security Considerations 168 This document focuses on IANA considerations for the PPPoE protocol, 169 and as such should help remove the possibility for the same PPPoE 170 code field and PPPoE TAG value being used for different 171 functionalities. 173 4. References 175 4.1 Normative References 177 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 178 Requirement Levels", BCP 14, RFC 2119, March 1997. 180 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing 181 an IANA Considerations Section in RFCs", BCP 26, RFC 182 2434, October 1998. 184 [RFC2516] Mamakos L., Lidl K., Evarts J., Carrel D., Simone D., 185 Wheeler R., "A Method for Transmitting PPP Over 186 Ethernet (PPPoE)", RFC 2516, February 1999 188 4.2 Informative References 190 [CARREL] Carrel D., Simone D., Ho C., Stoner T., "Extensions 191 to a Method for Transmitting PPP Over Ethernet 192 (PPPoE)", work in progress. 194 [BERRY] Berry B., Holgate H., "PPP Over Ethernet (PPPoE) 195 Extensions for Credit Flow and Link Metrics", 196 work in progress. 198 [ARBERG] Arberg P., Kourkouzelis D., Duckett M., Anschutz T., 199 Moisand J., "Accommodating an MTU/MRU greater than 200 1492 in PPPoE", work in progress. 202 Authors' Addresses 204 Peter Arberg 205 Redback Networks, Inc. 206 300 Holger Way 207 San Jose, CA 95134 208 USA 209 Email: parberg@redback.com 211 Vince Mammoliti 212 Cisco Systems, Inc. 213 181 Bay Street, Suite 3400 214 Toronto, Ontario, M5J 2T3 215 Canada 216 EMail: vince@cisco.com 218 Full Copyright Statement 220 Copyright (C) The Internet Society (2006). 222 This document is subject to the rights, licenses and restrictions 223 contained in BCP 78, and except as set forth therein, the authors 224 retain all their rights. 226 This document and the information contained herein are provided on an 227 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 228 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 229 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 230 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 231 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 232 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 234 Intellectual Property Statement 236 The IETF takes no position regarding the validity or scope of any 237 Intellectual Property Rights or other rights that might be claimed to 238 pertain to the implementation or use of the technology described in 239 this document or the extent to which any license under such rights 240 might or might not be available; nor does it represent that it has 241 made any independent effort to identify any such rights. Information 242 on the procedures with respect to rights in RFC documents can be 243 found in BCP 78 and BCP 79. 245 Copies of IPR disclosures made to the IETF Secretariat and any 246 assurances of licenses to be made available, or the result of an 247 attempt made to obtain a general license or permission for the use of 248 such proprietary rights by implementers or users of this 249 specification can be obtained from the IETF on-line IPR repository at 250 http://www.ietf.org/ipr. 252 The IETF invites any interested party to bring to its attention any 253 copyrights, patents or patent applications, or other proprietary 254 rights that may cover technology that may be required to implement 255 this standard. Please address the information to the IETF at ietf- 256 ipr@ietf.org. 258 Acknowledgement 260 Funding for the RFC Editor function is currently provided by the 261 Internet Society.