Network Working Group P. Arberg
Request for Comments: 4937 Redback Networks
Category: Informational V. Mammoliti
Cisco Systems
June 2007
Network Working Group P. Arberg
Request for Comments: 4937 Redback Networks
Category: Informational V. Mammoliti
Cisco Systems
June 2007
IANA Considerations for PPP over Ethernet (PPPoE)
以太网PPP（PPPoE）的IANA注意事项
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 IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
Abstract
摘要
This document describes the IANA considerations for the PPP over Ethernet (PPPoE) protocol.
本文档描述了以太网PPP（PPPoE）协议的IANA注意事项。
Table of Contents
目录
1. Introduction ....................................................2
1.1. Terminology ................................................2
1.2. Specification of Requirements ..............................2
2. IANA Considerations .............................................2
2.1. Registration Policies for PPPoE TAG Values .................2
2.2. Reserved PPPoE TAG Values ..................................3
2.3. Registration Policies for PPPoE Code Fields ................3
2.4. Reserved PPPoE Code fields .................................4
3. Security Considerations .........................................4
4. References ......................................................4
4.1. Normative References .......................................4
4.2. Informative References .....................................4
1. Introduction ....................................................2
1.1. Terminology ................................................2
1.2. Specification of Requirements ..............................2
2. IANA Considerations .............................................2
2.1. Registration Policies for PPPoE TAG Values .................2
2.2. Reserved PPPoE TAG Values ..................................3
2.3. Registration Policies for PPPoE Code Fields ................3
2.4. Reserved PPPoE Code fields .................................4
3. Security Considerations .........................................4
4. References ......................................................4
4.1. Normative References .......................................4
4.2. Informative References .....................................4
This document provides guidance to the Internet Assigned Numbers Authority (IANA) regarding the registration of values related to the PPP over Ethernet Protocol (PPPoE), defined in [RFC2516], in accordance with BCP 26, [RFC2434]. It also reserves PPPoE TAG values as well as PPPoE packet Code fields, which are or have been in use on the Internet.
本文件根据BCP 26、[RFC2434]，就[RFC2516]中定义的以太网PPP协议（PPPoE）相关值的注册向互联网分配号码管理局（IANA）提供指导。它还保留PPPoE标签值以及PPPoE数据包代码字段，这些字段现在或已经在互联网上使用。
The following terms are used here with the meanings defined in BCP 26: "name space", "registration".
以下术语的含义见BCP 26：“名称空间”、“注册”。
The following policies are used here with the meanings defined in BCP 26: "First Come First Served".
此处使用以下政策，其含义见BCP 26：“先到先得”。
In this document, several words are used to signify the requirements of the specification. These words are often capitalized. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
在本文件中，使用了几个词来表示规范的要求。这些词通常大写。本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
The PPPoE protocol, as defined in [RFC2516], defines two name spaces that require registration, the PPPoE TAG and the PPPoE Code field.
[RFC2516]中定义的PPPoE协议定义了两个需要注册的名称空间，即PPPoE标签和PPPoE代码字段。
IANA has set up a registry of "PPPoE TAG Values". These are 16-bit values. PPPoE TAG values already in use are specified as reserved in this document. All other TAG values between 0 and 65535 are to be assigned by IANA, using the "First Come First Served" policy defined in [RFC2434].
IANA已经建立了一个“PPPoE标签值”注册表。这些是16位值。已使用的PPPoE标签值在本文档中指定为保留值。IANA将使用[RFC2434]中定义的“先到先得”策略分配0到65535之间的所有其他标记值。
A TAG-Name and a description for the usage, as well as a point of contact, MUST be provided for any assignment from this registry. A document reference SHOULD also be provided.
对于来自此注册表的任何分配，必须提供标记名和使用说明以及联系人。还应提供文件参考。
TAG Value TAG Name Tag Description Reference
----------- ------------------- --------------------- ---------
0 0x0000 End-Of-List See the reference [RFC2516]
TAG Value TAG Name Tag Description Reference
----------- ------------------- --------------------- ---------
0 0x0000 End-Of-List See the reference [RFC2516]
257 0x0101 Service-Name See the reference [RFC2516]
258 0x0102 AC-Name See the reference [RFC2516]
259 0x0103 Host-Uniq See the reference [RFC2516]
260 0x0104 AC-Cookie See the reference [RFC2516]
261 0x0105 Vendor-Specific See the reference [RFC2516]
262 0x0106 Credits See the reference [RFC4938]
263 0x0107 Metrics See the reference [RFC4938]
264 0x0108 Sequence Number See the reference [RFC4938]
257 0x0101 Service-Name See the reference [RFC2516]
258 0x0102 AC-Name See the reference [RFC2516]
259 0x0103 Host-Uniq See the reference [RFC2516]
260 0x0104 AC-Cookie See the reference [RFC2516]
261 0x0105 Vendor-Specific See the reference [RFC2516]
262 0x0106 Credits See the reference [RFC4938]
263 0x0107 Metrics See the reference [RFC4938]
264 0x0108 Sequence Number See the reference [RFC4938]
272 0x0110 Relay-Session-Id See the reference [RFC2516]
273 0x0111 HURL See the reference [CARREL]
274 0x0112 MOTM See the reference [CARREL]
272 0x0110 Relay-Session-Id See the reference [RFC2516]
273 0x0111 HURL See the reference [CARREL]
274 0x0112 MOTM See the reference [CARREL]
288 0x0120 PPP-Max-Payload See the reference [RFC4638] 289 0x0121 IP_Route_Add See the reference [CARREL]
288 0x0120 PPP最大有效载荷参见参考[RFC4638]289 0x0121 IP_路由_添加参见参考[CARREL]
513 0x0201 Service-Name-Error See the reference [RFC2516]
514 0x0202 AC-System-Error See the reference [RFC2516]
515 0x0203 Generic-Error See the reference [RFC2516]
513 0x0201 Service-Name-Error See the reference [RFC2516]
514 0x0202 AC-System-Error See the reference [RFC2516]
515 0x0203 Generic-Error See the reference [RFC2516]
IANA has set up a registry of PPPoE Active Discovery Code fields. These are 8-bit values. PPPoE Code fields already in use are specified as reserved in this document. All other Code values between 0 and 255 are to be assigned by IANA, using the "First Come First Served" policy defined in [RFC2434].
IANA已建立PPPoE活动发现代码字段的注册表。这些是8位值。已在使用的PPPoE代码字段在本文档中指定为保留字段。IANA将使用[RFC2434]中定义的“先到先得”策略分配0到255之间的所有其他代码值。
A PPPoE Active Discovery packet name and a description for the usage, as well as a point of contact, MUST be provided for any assignment from this registry.
对于来自此注册表的任何分配，必须提供PPPoE主动发现数据包名称和使用说明以及联系点。
A document reference SHOULD also be provided.
还应提供文件参考。
Code PPPoE Packet Name Description Reference
-------- ----------------------------- ----------------- ---------
0 0x00 PPP Session Stage See the reference [RFC2516]
Code PPPoE Packet Name Description Reference
-------- ----------------------------- ----------------- ---------
0 0x00 PPP Session Stage See the reference [RFC2516]
7 0x07 PADO, Offer See the reference [RFC2516] 9 0x09 PADI, Initiation See the reference [RFC2516]
7 0x07 PADO，报价见参考[RFC2516]9 0x09 PADI，启动见参考[RFC2516]
10 0x0a PADG, Session-Grant See the reference [RFC4938]
11 0x0b PADC, Session-Credit Response See the reference [RFC4938]
12 0x0c PADQ, Quality See the reference [RFC4938]
10 0x0a PADG, Session-Grant See the reference [RFC4938]
11 0x0b PADC, Session-Credit Response See the reference [RFC4938]
12 0x0c PADQ, Quality See the reference [RFC4938]
25 0x19 PADR, Request See the reference [RFC2516] 101 0x65 PADS, Session-confirmation See the reference [RFC2516]
25 0x19 PADR，请求参见参考[RFC2516]101 0x65 PADS，会话确认参见参考[RFC2516]
167 0xa7 PADT, Terminate See the reference [RFC2516]
167 0xa7焊盘，终止，参见参考[RFC2516]
211 0xd3 PADM, Message See the reference [CARREL] 212 0xd4 PADN, Network See the reference [CARREL]
211 0xd3 PADM，消息见参考[CARREL]212 0xd4 PADN，网络见参考[CARREL]
This document focuses on IANA considerations for the PPPoE protocol, and as such, should help remove the possibility of the same PPPoE code field and PPPoE TAG value being used for different functionalities.
本文件主要关注PPPoE协议的IANA注意事项，因此，应帮助消除相同PPPoE代码字段和PPPoE标签值用于不同功能的可能性。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[RFC2434]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。
[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.
[RFC2516]Mamakos，L.，Lidl，K.，Evarts，J.，Carrel，D.，Simone，D.，和R.Wheeler，“通过以太网传输PPP（PPPoE）的方法”，RFC 2516，1999年2月。
[CARREL] Carrel D., Simone D., Ho C. and T. Stoner, "Extensions to a Method for Transmitting PPP Over Ethernet (PPPoE)", Work in Progress.
[CARREL]CARREL D.，Simone D.，Ho C.和T.Stoner，“通过以太网传输PPP（PPPoE）方法的扩展”，正在进行中。
[RFC4938] Berry, B. and H. Holgate, "PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics", RFC 4938, June 2007.
[RFC4938]Berry，B.和H.Holgate，“信用流和链路度量的以太网PPP（PPPoE）扩展”，RFC 4938，2007年6月。
[RFC4638] Arberg, P., Kourkouzelis, D., Duckett, M., Anschutz, T., and J. Moisand, "Accommodating a Maximum Transit Unit/Maximum Receive Unit (MTU/MRU) Greater Than 1492 in the Point-to-Point Protocol over Ethernet (PPPoE)", RFC 4638, September 2006.
[RFC4638]Arberg，P.，Kourkouzelis，D.，Duckett，M.，Anschutz，T.，和J.Moissand，“在以太网点对点协议（PPPoE）中容纳大于1492的最大传输单元/最大接收单元（MTU/MRU）”，RFC 4638，2006年9月。
Authors' Addresses
作者地址
Peter Arberg Redback Networks, Inc. 300 Holger Way San Jose, CA 95134 USA EMail: parberg@redback.com
Peter Arberg Redback Networks，Inc.美国加利福尼亚州圣何塞霍尔格大道300号95134电子邮件：parberg@redback.com
Vince Mammoliti Cisco Systems, Inc. 181 Bay Street, Suite 3400 Toronto, Ontario, M5J 2T3 Canada EMail: vince@cisco.com
Vince Mammoliti Cisco Systems，Inc.加拿大安大略省多伦多市海湾街181号3400室M5J 2T3电子邮件：vince@cisco.com
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
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.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
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, THE IETF TRUST 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.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
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.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和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.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为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.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。