Internet Engineering Task Force (IETF) M. Boucadair
Request for Comments: 7291 France Telecom
Category: Standards Track R. Penno
ISSN: 2070-1721 D. Wing
Cisco
July 2014
Internet Engineering Task Force (IETF) M. Boucadair
Request for Comments: 7291 France Telecom
Category: Standards Track R. Penno
ISSN: 2070-1721 D. Wing
Cisco
July 2014
DHCP Options for the Port Control Protocol (PCP)
端口控制协议（PCP）的DHCP选项
Abstract
摘要
This document specifies DHCP (IPv4 and IPv6) options to configure hosts with Port Control Protocol (PCP) server IP addresses. The use of DHCPv4 or DHCPv6 depends on the PCP deployment scenarios. The set of deployment scenarios to which DHCPv4 or DHCPv6 can be applied is outside the scope of this document.
本文档指定了DHCP（IPv4和IPv6）选项，用于配置具有端口控制协议（PCP）服务器IP地址的主机。DHCPv4或DHCPv6的使用取决于PCP部署场景。可以应用DHCPv4或DHCPv6的部署场景集不在本文档的范围内。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7291.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7291.
Copyright Notice
版权公告
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2014 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. DHCPv6 PCP Server Option . . . . . . . . . . . . . . . . . . 3
3.1. Format . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.2. DHCPv6 Client Behavior . . . . . . . . . . . . . . . . . 4
4. DHCPv4 PCP Option . . . . . . . . . . . . . . . . . . . . . . 5
4.1. Format . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.2. DHCPv4 Client Behavior . . . . . . . . . . . . . . . . . 6
5. DHCP Server Configuration Guidelines . . . . . . . . . . . . 6
6. Dual-Stack Hosts . . . . . . . . . . . . . . . . . . . . . . 8
7. Hosts with Multiple Interfaces . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . 8
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
9.1. DHCPv6 Option . . . . . . . . . . . . . . . . . . . . . . 8
9.2. DHCPv4 Option . . . . . . . . . . . . . . . . . . . . . . 9
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
11.1. Normative References . . . . . . . . . . . . . . . . . . 9
11.2. Informative References . . . . . . . . . . . . . . . . . 10
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. DHCPv6 PCP Server Option . . . . . . . . . . . . . . . . . . 3
3.1. Format . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.2. DHCPv6 Client Behavior . . . . . . . . . . . . . . . . . 4
4. DHCPv4 PCP Option . . . . . . . . . . . . . . . . . . . . . . 5
4.1. Format . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.2. DHCPv4 Client Behavior . . . . . . . . . . . . . . . . . 6
5. DHCP Server Configuration Guidelines . . . . . . . . . . . . 6
6. Dual-Stack Hosts . . . . . . . . . . . . . . . . . . . . . . 8
7. Hosts with Multiple Interfaces . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . 8
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
9.1. DHCPv6 Option . . . . . . . . . . . . . . . . . . . . . . 8
9.2. DHCPv4 Option . . . . . . . . . . . . . . . . . . . . . . 9
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
11.1. Normative References . . . . . . . . . . . . . . . . . . 9
11.2. Informative References . . . . . . . . . . . . . . . . . 10
This document defines DHCPv4 [RFC2131] and DHCPv6 [RFC3315] options that can be used to configure hosts with PCP server [RFC6887] IP addresses.
本文档定义了DHCPv4[RFC2131]和DHCPv6[RFC3315]选项，可用于配置具有PCP服务器[RFC6887]IP地址的主机。
This specification assumes a PCP server is reachable with one or multiple IP addresses. As such, a list of IP addresses can be returned in the DHCP PCP server option.
本规范假设可以使用一个或多个IP地址访问PCP服务器。因此，可以在DHCP PCP服务器选项中返回IP地址列表。
This specification allows returning one or multiple lists of PCP server IP addresses. This is used as a hint to guide the PCP client when determining whether to send PCP requests to one or multiple PCP servers. Concretely, the PCP client needs an indication to decide whether entries need to be instantiated in all PCP servers (e.g., multi-homing, multiple PCP-controlled devices providing distinct services, etc.) or use one IP address from the list (e.g., redundancy group scenario, proxy-based model, etc.). Refer to [PCP-DEPLOYMENT] for a discussion on PCP deployment scenarios.
此规范允许返回一个或多个PCP服务器IP地址列表。当决定是否向一个或多个PCP服务器发送PCP请求时，这被用作指导PCP客户端的提示。具体而言，PCP客户端需要指示来决定是否需要在所有PCP服务器中实例化条目（例如，多归属、提供不同服务的多个PCP控制设备等）或使用列表中的一个IP地址（例如，冗余组场景、基于代理的模型等）。有关PCP部署方案的讨论，请参阅[PCP-DEPLOYMENT]。
For guidelines on how a PCP client can use multiple IP addresses and multiple PCP servers, see [PCP-SERVER].
有关PCP客户端如何使用多个IP地址和多个PCP服务器的指导原则，请参阅[PCP-SERVER]。
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 RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
This document makes use of the following terms:
本文件使用了以下术语：
o "PCP server" denotes a functional element that receives and processes PCP requests from a PCP client. A PCP server can be co-located with or be separated from the function (e.g., NAT, Firewall) it controls. Refer to [RFC6887].
o “PCP服务器”表示从PCP客户端接收和处理PCP请求的功能元件。PCP服务器可以与其控制的功能（如NAT、防火墙）共存或分离。请参阅[RFC6887]。
o "PCP client" denotes a PCP software instance responsible for issuing PCP requests to a PCP server. Refer to [RFC6887].
o “PCP客户端”表示负责向PCP服务器发出PCP请求的PCP软件实例。请参阅[RFC6887]。
o "DHCP" refers to both DHCPv4 [RFC2131] and DHCPv6 [RFC3315].
o “DHCP”指DHCPv4[RFC2131]和DHCPv6[RFC3315]。
o "DHCP client" denotes a node that initiates requests to obtain configuration parameters from one or more DHCP servers.
o “DHCP客户端”表示发起请求以从一个或多个DHCP服务器获取配置参数的节点。
o "DHCP server" refers to a node that responds to requests from DHCP clients.
o “DHCP服务器”是指响应DHCP客户端请求的节点。
The DHCPv6 PCP server option can be used to configure a list of IPv6 addresses of a PCP server.
DHCPv6 PCP服务器选项可用于配置PCP服务器的IPv6地址列表。
The format of this option is shown in Figure 1.
此选项的格式如图1所示。
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_V6_PCP_SERVER | Option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| PCP Server IPv6 Address |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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_V6_PCP_SERVER | Option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| PCP Server IPv6 Address |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: DHCPv6 PCP Server Option
图1:DHCPv6 PCP服务器选项
The fields of the option shown in Figure 1 are as follows:
图1所示的选项字段如下所示：
o Option-code: OPTION_V6_PCP_SERVER (86; see Section 9.1)
o 选项代码：选项V6\U PCP\U服务器（86；见第9.1节）
o Option-length: Length of the "PCP Server IPv6 Address(es)" field in octets. MUST be a multiple of 16.
o 选项长度：“PCP服务器IPv6地址”字段的长度（以八位字节为单位）。必须是16的倍数。
o PCP Server IPv6 Addresses: Includes one or more IPv6 addresses [RFC4291] of the PCP server to be used by the PCP client. Note, IPv4-mapped IPv6 addresses (Section 2.5.5.2 of [RFC4291]) are allowed to be included in this option.
o PCP服务器IPv6地址：包括PCP客户端要使用的PCP服务器的一个或多个IPv6地址[RFC4291]。注意，IPv4映射的IPv6地址（RFC4291的第2.5.5.2节）允许包含在此选项中。
To return more than one PCP server to the DHCPv6 client (as opposed to more than one address for a single PCP server), the DHCPv6 server returns multiple instances of OPTION_V6_PCP_SERVER.
要将多个PCP服务器返回到DHCPv6客户端（与单个PCP服务器的多个地址相反），DHCPv6服务器将返回OPTION_V6_PCP_server的多个实例。
To discover one or more PCP servers, the DHCPv6 client requests PCP server IP addresses by including OPTION_V6_PCP_SERVER in an Option Request Option (ORO), as described in Section 22.7 of [RFC3315].
如[RFC3315]第22.7节所述，为了发现一个或多个PCP服务器，DHCPv6客户端通过在选项请求选项（ORO）中包含选项_V6_PCP_server来请求PCP服务器IP地址。
The DHCPv6 client MUST be prepared to receive multiple instances of OPTION_V6_PCP_SERVER; each instance is to be treated as a separate PCP server.
DHCPv6客户端必须准备好接收OPTION_V6_PCP_SERVER的多个实例；每个实例都将被视为一个单独的PCP服务器。
If an IPv4-mapped IPv6 address is received in OPTION_V6_PCP_SERVER, it indicates that the PCP server has the corresponding IPv4 address.
如果在选项_V6_PCP_服务器中接收到IPv4映射的IPv6地址，则表示PCP服务器具有相应的IPv4地址。
Note: When presented with the IPv4-mapped prefix, current versions of Windows and Mac OS generate IPv4 packets but will not send IPv6 packets [RFC6052]. Representing IPv4 addresses as IPv4-mapped IPv6 addresses follows the same logic as in Section 5 of [RFC6887].
注意：当显示IPv4映射前缀时，当前版本的Windows和Mac OS会生成IPv4数据包，但不会发送IPv6数据包[RFC6052]。将IPv4地址表示为IPv4映射的IPv6地址遵循与[RFC6887]第5节中相同的逻辑。
The DHCPv6 client MUST silently discard multicast and host loopback addresses [RFC6890] conveyed in OPTION_V6_PCP_SERVER.
DHCPv6客户端必须以静默方式放弃选项_V6_PCP_服务器中传输的多播和主机环回地址[RFC6890]。
The DHCPv4 PCP server option can be used to configure a list of IPv4 addresses of a PCP server. The format of this option is illustrated in Figure 2.
DHCPv4 PCP服务器选项可用于配置PCP服务器的IPv4地址列表。此选项的格式如图2所示。
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Code | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| List-Length | List of |
+-+-+-+-+-+-+-+-+ PCP Server |
/ IPv4 Addresses /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ---
| List-Length | List of | |
+-+-+-+-+-+-+-+-+ PCP Server | |
/ IPv4 Addresses / |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
. ... . optional
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| List-Length | List of | |
+-+-+-+-+-+-+-+-+ PCP Server | |
/ IPv4 Addresses / |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ---
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Code | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| List-Length | List of |
+-+-+-+-+-+-+-+-+ PCP Server |
/ IPv4 Addresses /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ---
| List-Length | List of | |
+-+-+-+-+-+-+-+-+ PCP Server | |
/ IPv4 Addresses / |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
. ... . optional
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| List-Length | List of | |
+-+-+-+-+-+-+-+-+ PCP Server | |
/ IPv4 Addresses / |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ---
Figure 2: DHCPv4 PCP Server Option
图2:DHCPv4 PCP服务器选项
The descriptions of the fields are as follows:
这些字段的描述如下所示：
o Code: OPTION_V4_PCP_SERVER (158; see Section 9.2);
o 代码：选项4\u PCP\u服务器（158；见第9.2节）；
o Length: Length of all included data in octets. The minimum length is 5.
o 长度：以八位字节为单位的所有包含数据的长度。最小长度为5。
o List-Length: Length of the "List of PCP Server IPv4 Addresses" field in octets. MUST be a multiple of 4.
o 列表长度：“PCP服务器IPv4地址列表”字段的长度（以八位字节为单位）。必须是4的倍数。
o List of PCP Server IPv4 Addresses: Contains one or more IPv4 addresses of the PCP server to be used by the PCP client. The format of this field is shown in Figure 3.
o PCP服务器IPv4地址列表：包含PCP客户端要使用的PCP服务器的一个或多个IPv4地址。该字段的格式如图3所示。
0 8 16 24 32 40 48
+-----+-----+-----+-----+-----+-----+--
| a1 | a2 | a3 | a4 | a1 | a2 | ...
+-----+-----+-----+-----+-----+-----+--
IPv4 Address 1 IPv4 Address 2 ...
0 8 16 24 32 40 48
+-----+-----+-----+-----+-----+-----+--
| a1 | a2 | a3 | a4 | a1 | a2 | ...
+-----+-----+-----+-----+-----+-----+--
IPv4 Address 1 IPv4 Address 2 ...
This format assumes that an IPv4 address is encoded as a1.a2.a3.a4.
此格式假定IPv4地址编码为a1.a2.a3.a4。
Figure 3: Format of the List of PCP Server IPv4 Addresses
图3:PCP服务器IPv4地址列表的格式
OPTION_V4_PCP_SERVER can include multiple lists of PCP server IPv4 addresses; each list is treated as a separate PCP server. When several lists of PCP server IPv4 addresses are to be included, the
OPTION_V4_PCP_服务器可以包括多个PCP服务器IPv4地址列表；每个列表都被视为一个单独的PCP服务器。如果要包括多个PCP服务器IPv4地址列表，则
"List-Length" and "List of PCP Server IPv4 Addresses" fields are repeated.
“列表长度”和“PCP服务器IPv4地址列表”字段重复。
OPTION_V4_PCP_SERVER is a concatenation-requiring option. As such, the mechanism specified in [RFC3396] MUST be used if OPTION_V4_PCP_SERVER exceeds the maximum DHCPv4 option size of 255 octets.
选项4\u PCP\u服务器是一个需要连接的选项。因此，如果OPTION_V4_PCP_SERVER超过最大DHCPv4选项大小255个八位字节，则必须使用[RFC3396]中指定的机制。
To discover one or more PCP servers, the DHCPv4 client requests PCP server IP addresses by including OPTION_V4_PCP_SERVER in a Parameter Request List option [RFC2132].
为了发现一个或多个PCP服务器，DHCPv4客户端通过在参数请求列表选项[RFC2132]中包含选项_V4_PCP_server来请求PCP服务器IP地址。
The DHCPv4 client MUST be prepared to receive multiple lists of PCP server IPv4 addresses in the same DHCPv4 PCP server option; each list is to be treated as a separate PCP server.
DHCPv4客户端必须准备好在同一DHCPv4 PCP服务器选项中接收PCP服务器IPv4地址的多个列表；每个列表将被视为一个单独的PCP服务器。
The DHCPv4 client MUST silently discard multicast and host loopback addresses [RFC6890] conveyed in OPTION_V4_PCP_SERVER.
DHCPv4客户端必须以静默方式放弃选项4\u PCP\u服务器中传输的多播和主机环回地址[RFC6890]。
DHCP servers supporting the DHCP PCP server option can be configured with a list of IP addresses of the PCP server(s). If multiple IP addresses are configured, the DHCP server MUST be explicitly configured whether all or some of these addresses refer to:
可以使用PCP服务器的IP地址列表配置支持DHCP PCP服务器选项的DHCP服务器。如果配置了多个IP地址，则必须显式配置DHCP服务器，无论这些地址中的所有或部分地址是指：
1. the same PCP server: the DHCP server returns multiple addresses in the same instance of the DHCP PCP server option.
1. 相同的PCP服务器：DHCP服务器在DHCP PCP服务器选项的同一实例中返回多个地址。
2. distinct PCP servers: the DHCP server returns multiple lists of PCP server IP addresses to the requesting DHCP client (encoded as multiple OPTION_V6_PCP_SERVERs or in the same OPTION_V4_PCP_SERVER); each list is referring to a distinct PCP server. For example, multiple PCP servers may be configured to a PCP client in some deployment contexts such as multi-homing. It is out of the scope of this document to enumerate all deployment scenarios that require multiple PCP servers to be returned.
2. 不同的PCP服务器：DHCP服务器将PCP服务器IP地址的多个列表返回给请求的DHCP客户端（编码为多个选项\u V6\u PCP\u服务器或同一选项\u V4\u PCP\u服务器）；每个列表都指向一个不同的PCP服务器。例如，在一些部署上下文中，例如多主机，可以将多个PCP服务器配置为PCP客户端。枚举需要返回多个PCP服务器的所有部署场景超出了本文档的范围。
Precisely how DHCP servers are configured to separate lists of IP addresses according to which PCP server they address is out of the scope of this document. However, DHCP servers MUST NOT combine the IP addresses of multiple PCP servers and return them to the DHCP client as if they belong to a single PCP server, and DHCP servers MUST NOT separate the addresses of a single PCP server and return them as if they belong to distinct PCP servers. For example, if an administrator configures the DHCP server by providing a Fully Qualified Domain Name (FQDN) for a PCP server, even if that FQDN resolves to multiple addresses, the DHCP server MUST deliver them within a single server address block.
DHCP服务器配置为根据其所寻址的PCP服务器分隔IP地址列表的确切方式不在本文档范围内。但是，DHCP服务器不得将多个PCP服务器的IP地址组合在一起，并将其返回给DHCP客户端，就像它们属于单个PCP服务器一样，DHCP服务器不得分离单个PCP服务器的地址，并将其返回给不同的PCP服务器一样。例如，如果管理员通过为PCP服务器提供完全限定的域名（FQDN）来配置DHCP服务器，则即使该FQDN解析为多个地址，DHCP服务器也必须在单个服务器地址块中传递这些地址。
DHCPv6 servers that implement this option and that can populate the option by resolving FQDNs will need a mechanism for indicating whether to query for A records or only AAAA records. When a query returns A records, the IP addresses in those records are returned in the DHCPv6 response as IPv4-mapped IPv6 addresses.
实现此选项并且可以通过解析FQDNs来填充选项的DHCPv6服务器将需要一种机制来指示是查询记录还是仅查询AAAA记录。当查询返回记录时，这些记录中的IP地址将在DHCPv6响应中作为IPv4映射的IPv6地址返回。
Discussion: The motivation for this design is to accommodate deployment cases where an IPv4 connectivity service is provided while only DHCPv6 is in use (e.g., an IPv4-only PCP server in a Dual-Stack Lite (DS-Lite) context [RFC6333]).
讨论：此设计的动机是为了适应仅使用DHCPv6时提供IPv4连接服务的部署情况（例如，双栈Lite（DS Lite）上下文[RFC6333]中仅IPv4的PCP服务器）。
Since this option requires support for IPv4-mapped IPv6 addresses, a DHCPv6 server implementation will not be complete if it does not query for A records and represent any that are returned as IPv4-mapped IPv6 addresses in DHCPv6 responses. This behavior is neither required nor suggested for DHCPv6 options in general: it is specific to OPTION_V6_PCP_SERVER. The mechanism whereby DHCPv6 implementations provide this functionality is beyond the scope of this document.
由于此选项要求支持IPv4映射的IPv6地址，因此，如果DHCPv6服务器实现不查询记录并表示在DHCPv6响应中作为IPv4映射的IPv6地址返回的任何记录，则该实现将不完整。通常，DHCPv6选项既不需要也不建议使用此行为：它特定于选项_V6_PCP_SERVER。DHCPv6实现提供此功能的机制超出了本文档的范围。
For guidelines on providing context-specific configuration information (e.g., returning a regional-based configuration) and information on how a DHCP server might be configured with FQDNs that get resolved on demand, see [DHC-CONFIG].
有关提供特定于上下文的配置信息（例如，返回基于区域的配置）的指导原则，以及关于如何使用FQDN配置DHCP服务器的信息，请参阅[DHC-CONFIG]。
A dual-stack host might receive a PCP server option via both DHCPv4 and DHCPv6. For guidance on how a DHCP client can handle PCP server IP lists for the same network but obtained via different mechanisms, see [PCP-SERVER].
双栈主机可能通过DHCPv4和DHCPv6接收PCP服务器选项。有关DHCP客户端如何处理同一网络但通过不同机制获得的PCP服务器IP列表的指导，请参阅[PCP-server]。
A host may have multiple network interfaces (e.g., 3G, IEEE 802.11, etc.), each configured differently. Each PCP server learned MUST be associated with the interface via which it was learned.
主机可具有多个网络接口（例如，3G、IEEE 802.11等），每个网络接口的配置不同。每个读入的PCP服务器必须与读入该服务器的接口相关联。
Refer to [PCP-SERVER] and Section 8.4 of [RFC6887] for more discussion on multi-interface considerations.
有关多接口注意事项的更多讨论，请参阅[PCP-SERVER]和[RFC6887]的第8.4节。
The security considerations in [RFC2131] and [RFC3315] are to be considered. PCP-related security considerations are discussed in [RFC6887].
应考虑[RFC2131]和[RFC3315]中的安全注意事项。[RFC6887]中讨论了PCP相关的安全注意事项。
The PCP server option defined here is applicable when operating under the simple threat model (Section 18.1 of [RFC6887]). Operation under the advanced threat model (Section 18.2 of [RFC6887]) may or may not be appropriate; analysis of this question is out of the scope of this document.
此处定义的PCP服务器选项适用于在简单威胁模型（RFC6887第18.1节）下运行的情况。高级威胁模型（RFC6887第18.2节）下的操作可能适用，也可能不适用；对这个问题的分析超出了本文件的范围。
IANA has assigned the following new DHCPv6 Option Code in the registry maintained in <http://www.iana.org/assignments/dhcpv6-parameters>:
IANA已在中维护的注册表中分配了以下新的DHCPv6选项代码<http://www.iana.org/assignments/dhcpv6-parameters>:
Option Name Value
-------------------- -----
OPTION_V6_PCP_SERVER 86
Option Name Value
-------------------- -----
OPTION_V6_PCP_SERVER 86
IANA has assigned the following new DHCPv4 Option Code in the registry maintained in <http://www.iana.org/assignments/bootp-dhcp-parameters>:
IANA在中维护的注册表中分配了以下新的DHCPv4选项代码：<http://www.iana.org/assignments/bootp-dhcp-parameters>:
Option Name Tag Data Length Meaning
-------------------- --- ----------- --------------------------------
OPTION_V4_PCP_SERVER 158 Variable; Includes one or multiple lists
the minimum of PCP server IP addresses; each
length is list is treated as a separate
5. PCP server.
Option Name Tag Data Length Meaning
-------------------- --- ----------- --------------------------------
OPTION_V4_PCP_SERVER 158 Variable; Includes one or multiple lists
the minimum of PCP server IP addresses; each
length is list is treated as a separate
5. PCP server.
Many thanks to C. Jacquenet, R. Maglione, D. Thaler, T. Mrugalski, T. Reddy, S. Cheshire, M. Wasserman, C. Holmberg, A. Farrel, S. Farrel, B. Haberman, and P. Resnick for their review and comments.
非常感谢C.Jacquenet、R.Maglione、D.Thaler、T.Mrugalski、T.Reddy、S.Cheshire、M.Wasserman、C.Holmberg、A.Farrel、S.Farrel、B.Haberman和P.Resnick的审查和评论。
Special thanks to T. Lemon and B. Volz for their reviews and their efforts to enhance this specification.
特别感谢T.Lemon和B.Volz对本规范的审查和改进。
[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月。
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, March 1997.
[RFC2131]Droms，R.，“动态主机配置协议”，RFC21311997年3月。
[RFC2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor Extensions", RFC 2132, March 1997.
[RFC2132]Alexander，S.和R.Droms，“DHCP选项和BOOTP供应商扩展”，RFC 21321997年3月。
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, July 2003.
[RFC3315]Droms，R.，Bound，J.，Volz，B.，Lemon，T.，Perkins，C.，和M.Carney，“IPv6的动态主机配置协议（DHCPv6）”，RFC3315，2003年7月。
[RFC3396] Lemon, T. and S. Cheshire, "Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4)", RFC 3396, November 2002.
[RFC3396]Lemon，T.和S.Cheshire，“动态主机配置协议（DHCPv4）中的长选项编码”，RFC 3396，2002年11月。
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, February 2006.
[RFC4291]Hinden，R.和S.Deering，“IP版本6寻址体系结构”，RFC 42912006年2月。
[RFC6887] Wing, D., Cheshire, S., Boucadair, M., Penno, R., and P. Selkirk, "Port Control Protocol (PCP)", RFC 6887, April 2013.
[RFC6887]南柴郡Wing，D.，布卡达尔，M.，佩诺，R.，和P.Selkirk，“港口控制协议（PCP）”，RFC 6887，2013年4月。
[RFC6890] Cotton, M., Vegoda, L., Bonica, R., and B. Haberman, "Special-Purpose IP Address Registries", BCP 153, RFC 6890, April 2013.
[RFC6890]Cotton，M.，Vegoda，L.，Bonica，R.，和B.Haberman，“特殊用途IP地址注册”，BCP 153，RFC 68902013年4月。
[DHC-CONFIG] Lemon, T. and T. Mrugalski, "Customizing DHCP Configuration on the Basis of Network Topology", Work in Progress, February 2014.
[DHC-CONFIG]Lemon，T.和T.Mrugalski，“根据网络拓扑定制DHCP配置”，正在进行的工作，2014年2月。
[PCP-DEPLOYMENT] Boucadair, M., "Port Control Protocol (PCP) Deployment Models", Work in Progress, April 2014.
[PCP-部署]Boucadair，M.，“端口控制协议（PCP）部署模型”，正在进行的工作，2014年4月。
[PCP-SERVER] Boucadair, M., Penno, R., Wing, D., Patil, P., and T. Reddy, "PCP Server Selection", Work in Progress, April 2014.
[PCP-SERVER]Boucadair，M.，Penno，R.，Wing，D.，Patil，P.，和T.Reddy，“PCP服务器选择”，正在进行的工作，2014年4月。
[RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X. Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052, October 2010.
[RFC6052]Bao，C.，Huitema，C.，Bagnulo，M.，Boucadair，M.，和X.Li，“IPv4/IPv6转换器的IPv6寻址”，RFC 6052010年10月。
[RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion", RFC 6333, August 2011.
[RFC6333]Durand，A.，Droms，R.，Woodyatt，J.，和Y.Lee，“IPv4耗尽后的双栈Lite宽带部署”，RFC 63332011年8月。
Authors' Addresses
作者地址
Mohamed Boucadair France Telecom Rennes 35000 France
穆罕默德·布卡达尔法国电信雷恩35000法国
EMail: mohamed.boucadair@orange.com
EMail: mohamed.boucadair@orange.com
Reinaldo Penno Cisco USA
美国思科公司
EMail: repenno@cisco.com
EMail: repenno@cisco.com
Dan Wing Cisco Systems, Inc. 170 West Tasman Drive San Jose, California 95134 USA
Dan Wing Cisco Systems，Inc.美国加利福尼亚州圣何塞西塔斯曼大道170号，邮编95134
EMail: dwing@cisco.com
EMail: dwing@cisco.com