Network Working Group B. Volz
Request for Comments: 4580 Cisco Systems, Inc.
Category: Standards Track June 2006
Network Working Group B. Volz
Request for Comments: 4580 Cisco Systems, Inc.
Category: Standards Track June 2006
Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Subscriber-ID Option
IPv6（DHCPv6）中继代理订户ID选项的动态主机配置协议
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
Abstract
摘要
This memo defines a new Relay Agent Subscriber-ID option for the Dynamic Host Configuration Protocol for IPv6 (DHCPv6). The option allows a DHCPv6 relay agent to associate a stable "Subscriber-ID" with DHCPv6 client messages in a way that is independent of the client and of the underlying physical network infrastructure.
此备忘录为IPv6（DHCPv6）的动态主机配置协议定义了一个新的中继代理订户ID选项。该选项允许DHCPv6中继代理以独立于客户端和底层物理网络基础设施的方式将稳定的“订户ID”与DHCPv6客户端消息相关联。
Table of Contents
目录
1. Introduction ....................................................2
2. The Relay Agent Subscriber-ID Option ............................2
3. DHCPv6 Relay Agent Behavior .....................................3
4. DHCPv6 Server Behavior ..........................................3
5. Security Considerations .........................................4
6. IANA Considerations .............................................4
7. Acknowledgements ................................................4
8. References ......................................................4
8.1. Normative References .......................................4
8.2. Informative References .....................................4
1. Introduction ....................................................2
2. The Relay Agent Subscriber-ID Option ............................2
3. DHCPv6 Relay Agent Behavior .....................................3
4. DHCPv6 Server Behavior ..........................................3
5. Security Considerations .........................................4
6. IANA Considerations .............................................4
7. Acknowledgements ................................................4
8. References ......................................................4
8.1. Normative References .......................................4
8.2. Informative References .....................................4
DHCPv6 [1] provides IP addresses and configuration information for IPv6 clients. It includes a relay agent capability, in which processes within the network infrastructure receive multicast messages from clients and relay them to DHCPv6 servers. In some network environments, it will be useful for the relay agent to add information to the DHCPv6 message before relaying it.
DHCPv6[1]为IPv6客户端提供IP地址和配置信息。它包括中继代理功能，其中网络基础结构中的进程从客户端接收多播消息，并将其中继到DHCPv6服务器。在某些网络环境中，中继代理在中继DHCPv6消息之前将信息添加到DHCPv6消息中会很有用。
The information that relay agents supply can also be used in the server's decision-making about the addresses, delegated prefixes [2], and configuration parameters that the client is to receive.
中继代理提供的信息也可用于服务器的决策，包括客户机将接收的地址、委托前缀[2]和配置参数。
In many service-provider environments, it is believed to be desirable to associate some provider-specific information with clients' DHCPv6 messages that is independent of the physical network configuration and that the relay agent has learned through some means that is outside the scope of this memo.
在许多服务提供商环境中，希望将一些特定于提供商的信息与客户端的DHCPv6消息相关联，这些消息独立于物理网络配置，并且中继代理已通过本备忘录范围之外的某些方法了解到。
In complex service provider environments, there is a need to connect a customer's DHCPv6 configuration with the customer's administrative information. The Relay Agent Subscriber-ID option carries a value that can be independent of the physical network configuration through which the subscriber is connected. This value complements, and might well be used in addition to, the network-based information. The "subscriber-id" assigned by the provider is intended to be stable as customers connect through different paths, and as network changes occur.
在复杂的服务提供商环境中，需要将客户的DHCPv6配置与客户的管理信息连接起来。中继代理订户ID选项携带的值可以独立于订户所连接的物理网络配置。该值是对基于网络的信息的补充，并且很可能被用作补充。当客户通过不同路径连接时，以及当网络发生变化时，提供商分配的“订户id”是稳定的。
The subscriber-id information allows the service provider to assign/ activate subscriber-specific actions; e.g., assignment of specific IP addresses, prefixes, DNS configuration, trigger accounting, etc. This option is de-coupled from the access network's physical structure, so a subscriber that moves from one access-point to another, for example, would not require reconfiguration at the service provider's DHCPv6 servers.
用户id信息允许服务提供商分配/激活用户特定的操作；e、 例如，分配特定IP地址、前缀、DNS配置、触发器记帐等。此选项与接入网络的物理结构分离，因此，例如，从一个接入点移动到另一个接入点的订户不需要在服务提供商的DHCPv6服务器上重新配置。
The subscriber-id information is only intended for use within a single administrative domain and is only exchanged between the relay agents and DHCPv6 servers within that domain. Therefore, the format and encoding of the data in the option is not standardized, and this specification does not establish any semantic requirements on the data. This specification only defines the option for conveying this information from relay agents to DHCPv6 servers.
订户id信息仅用于单个管理域内，并且仅在该域内的中继代理和DHCPv6服务器之间交换。因此，选项中数据的格式和编码未标准化，本规范未对数据建立任何语义要求。本规范仅定义将此信息从中继代理传输到DHCPv6服务器的选项。
However, as the DHCPv4 Subscriber-ID suboption [3] specifies Network Virtual Terminal (NVT) American Standard Code for Information Interchange (ASCII) [4] encoded data, in environments where both DHCPv4 [5] and DHCPv6 are being used, it may be beneficial to use that encoding.
然而，由于DHCPv4用户ID子选项[3]指定了网络虚拟终端（NVT）美国信息交换标准代码（ASCII）[4]编码数据，因此在同时使用DHCPv4[5]和DHCPv6的环境中，使用该编码可能是有益的。
The format of the DHCPv6 Relay Agent Subscriber-ID option is shown below:
DHCPv6中继代理订户ID选项的格式如下所示：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_SUBSCRIBER_ID | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. subscriber-id .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_SUBSCRIBER_ID | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. subscriber-id .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code OPTION_SUBSCRIBER_ID (38)
选项代码选项用户ID（38）
option-len length, in octets, of the subscriber-id field. The minimum length is 1 octet.
选项len订户id字段的长度，以八位字节为单位。最小长度为1个八位组。
subscriber-id The subscriber's identity.
订户id订户的身份。
DHCPv6 relay agents may be configured to include a Subscriber-ID option in relayed (RELAY-FORW) DHCPv6 messages. How the subscriber-id is assigned and the mechanisms used to configure it are outside the scope of this memo.
DHCPv6中继代理可以配置为在中继（relay-FORW）DHCPv6消息中包括订户ID选项。如何分配订户id以及用于配置订户id的机制不在本备忘录的范围内。
This option provides additional information to the DHCPv6 server. The DHCPv6 server may use this information, if available, in addition to other relay agent option data, other options included in the DHCPv6 client messages, and physical network topology information in order to assign IP addresses, delegate prefixes, and/or other configuration parameters to the client. There is no special additional processing for this option.
此选项向DHCPv6服务器提供附加信息。除了其他中继代理选项数据、DHCPv6客户端消息中包含的其他选项和物理网络拓扑信息之外，DHCPv6服务器还可以使用此信息（如果可用），以便为客户端分配IP地址、代理前缀和/或其他配置参数。此选项没有特殊的附加处理。
There is no requirement that a server return this option and its data in a RELAY-REPLY message.
不要求服务器在中继回复消息中返回此选项及其数据。
As the subscriber-id option is only exchanged between relay agents and DHCPv6 servers, [1], Section 21.1, provides details on securing DHCPv6 messages sent between servers and relay agents. [1], Section 23, provides general DHCPv6 security considerations.
由于订户id选项仅在中继代理和DHCPv6服务器之间交换，[1]第21.1节提供了有关保护服务器和中继代理之间发送的DHCPv6消息的详细信息。[1] ，第23节提供了DHCPv6的一般安全注意事项。
IANA has assigned a DHCPv6 option code (38) for the Relay Agent Subscriber-ID Option.
IANA已为中继代理订户ID选项分配了DHCPv6选项代码（38）。
Thanks to Richard Johnson, Theyn Palaniappan, and Mark Stapp as this document is essentially an edited version of their memo [3].
感谢Richard Johnson、Theyn Palaniappan和Mark Stapp，因为本文件本质上是他们备忘录的编辑版本[3]。
[1] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, July 2003.
[1] Droms，R.，Bound，J.，Volz，B.，Lemon，T.，Perkins，C.，和M.Carney，“IPv6的动态主机配置协议（DHCPv6）”，RFC3315，2003年7月。
[2] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6", RFC 3633, December 2003.
[2] Troan，O.和R.Droms，“动态主机配置协议（DHCP）版本6的IPv6前缀选项”，RFC 3633，2003年12月。
[3] Johnson, R., Palaniappan, T., and M. Stapp, "Subscriber-ID Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option", RFC 3993, March 2005.
[3] Johnson，R.，Palaniappan，T.，和M.Stapp，“动态主机配置协议（DHCP）中继代理选项的用户ID子选项”，RFC 3993，2005年3月。
[4] Postel, J. and J. Reynolds, "Telnet Protocol Specification", STD 8, RFC 854, May 1983.
[4] Postel，J.和J.Reynolds，“Telnet协议规范”，STD 8，RFC 854，1983年5月。
[5] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, March 1997.
[5] Droms，R.，“动态主机配置协议”，RFC 2131，1997年3月。
Author's Address
作者地址
Bernard Volz Cisco Systems, Inc. 1414 Massachusetts Ave. Boxborough, MA 01719 USA
伯纳德·沃兹思科系统公司，美国马萨诸塞州博克斯伯勒马萨诸塞大道1414号，邮编01719
Phone: +1 978 936 0382
EMail: volz@cisco.com
Phone: +1 978 936 0382
EMail: volz@cisco.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（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.
本文件受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 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.
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 provided by the IETF Administrative Support Activity (IASA).
RFC编辑器功能的资金由IETF行政支持活动（IASA）提供。