Internet Engineering Task Force (IETF) T. Mrugalski
Request for Comments: 7598 ISC
Category: Standards Track O. Troan
ISSN: 2070-1721 Cisco Systems
I. Farrer
Deutsche Telekom AG
S. Perreault
Jive Communications
W. Dec
Cisco Systems
C. Bao
Tsinghua University
L. Yeh
Freelancer Technologies
X. Deng
The University of New South Wales
July 2015
Internet Engineering Task Force (IETF) T. Mrugalski
Request for Comments: 7598 ISC
Category: Standards Track O. Troan
ISSN: 2070-1721 Cisco Systems
I. Farrer
Deutsche Telekom AG
S. Perreault
Jive Communications
W. Dec
Cisco Systems
C. Bao
Tsinghua University
L. Yeh
Freelancer Technologies
X. Deng
The University of New South Wales
July 2015
DHCPv6 Options for Configuration of Softwire Address and Port-Mapped Clients
用于配置软线地址和端口映射客户端的DHCPv6选项
Abstract
摘要
This document specifies DHCPv6 options, termed Softwire46 options, for the provisioning of Softwire46 Customer Edge (CE) devices. Softwire46 is a collective term used to refer to architectures based on the notion of IPv4 Address plus Port (A+P) for providing IPv4 connectivity across an IPv6 network.
本文档规定了DHCPv6选项，称为Softwire46选项，用于供应Softwire46客户边缘（CE）设备。Softwire46是一个集合术语，用于指基于IPv4地址加端口（a+P）概念的架构，用于跨IPv6网络提供IPv4连接。
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/rfc7598.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7598.
Copyright Notice
版权公告
Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2015 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 ....................................................3
2. Conventions .....................................................3
3. Softwire46 Overview .............................................4
4. Common Softwire46 DHCPv6 Options ................................5
4.1. S46 Rule Option ............................................5
4.2. S46 BR Option ..............................................7
4.3. S46 DMR Option .............................................8
4.4. S46 IPv4/IPv6 Address Binding Option .......................9
4.5. S46 Port Parameters Option ................................10
5. Softwire46 Containers ..........................................11
5.1. S46 MAP-E Container Option ................................11
5.2. S46 MAP-T Container Option ................................12
5.3. S46 Lightweight 4over6 Container Option ...................13
6. Softwire46 Options Encapsulation ...............................14
7. DHCPv6 Server Behavior .........................................14
8. DHCPv6 Client Behavior .........................................14
9. Security Considerations ........................................15
10. IANA Considerations ...........................................16
11. References ....................................................16
11.1. Normative References .....................................16
11.2. Informative References ...................................17
Acknowledgements ..................................................18
Authors' Addresses ................................................19
1. Introduction ....................................................3
2. Conventions .....................................................3
3. Softwire46 Overview .............................................4
4. Common Softwire46 DHCPv6 Options ................................5
4.1. S46 Rule Option ............................................5
4.2. S46 BR Option ..............................................7
4.3. S46 DMR Option .............................................8
4.4. S46 IPv4/IPv6 Address Binding Option .......................9
4.5. S46 Port Parameters Option ................................10
5. Softwire46 Containers ..........................................11
5.1. S46 MAP-E Container Option ................................11
5.2. S46 MAP-T Container Option ................................12
5.3. S46 Lightweight 4over6 Container Option ...................13
6. Softwire46 Options Encapsulation ...............................14
7. DHCPv6 Server Behavior .........................................14
8. DHCPv6 Client Behavior .........................................14
9. Security Considerations ........................................15
10. IANA Considerations ...........................................16
11. References ....................................................16
11.1. Normative References .....................................16
11.2. Informative References ...................................17
Acknowledgements ..................................................18
Authors' Addresses ................................................19
A number of architectural solution proposals discussed in the IETF Softwire Working Group use Address plus Port (A+P) [RFC6346] as their technology base for providing IPv4 connectivity to end users using Customer Edge (CE) devices across a service provider's IPv6 network, while allowing for shared or dedicated IPv4 addressing of CEs.
IETF Softwire工作组中讨论的许多架构解决方案建议使用地址加端口（A+P）[RFC6346]作为其技术基础，通过服务提供商的IPv6网络向使用客户边缘（CE）设备的最终用户提供IPv4连接，同时允许CE的共享或专用IPv4寻址。
An example is Mapping of Address and Port with Encapsulation (MAP-E) as defined in [RFC7597]. The MAP solution consists of one or more MAP Border Relay (BR) routers responsible for stateless forwarding between a MAP IPv6 domain and an IPv4 network, and one or more MAP Customer Edge (CE) routers responsible for forwarding between a user's IPv4 network and the MAP IPv6 network domain. Collectively, the MAP CE and BR form a domain when configured with common service parameters. This characteristic is common to all of the Softwire46 mechanisms.
一个例子是地址和端口与[RFC7597]中定义的封装（MAP-E）的映射。MAP解决方案包括一个或多个MAP边界中继（BR）路由器，负责MAP IPv6域和IPv4网络之间的无状态转发，以及一个或多个MAP客户边缘（CE）路由器，负责用户的IPv4网络和MAP IPv6网络域之间的转发。当配置公共服务参数时，MAP CE和BR共同构成一个域。该特性是所有软线46机构的共同特征。
To function in such a domain, a CE needs to be provisioned with the appropriate A+P service parameters for that domain. These consist primarily of the CE's IPv4 address and transport-layer port range(s). Furthermore, the IPv6 transport mode (i.e., encapsulation or translation) needs to be specified. Provisioning of other IPv4 configuration information not derived directly from the A+P service parameters is not covered in this document. It is expected that provisioning of other IPv4 configuration information will continue to use DHCPv4 [RFC2131].
要在这样的域中运行，需要为CE提供该域的适当a+P服务参数。这些主要包括CE的IPv4地址和传输层端口范围。此外，需要指定IPv6传输模式（即封装或转换）。本文档不包括其他不是直接从A+P服务参数派生的IPv4配置信息的设置。预计其他IPv4配置信息的提供将继续使用DHCPv4[RFC2131]。
This memo specifies a set of DHCPv6 [RFC3315] options to provision Softwire46 configuration information to CE routers. Although the focus is to deliver IPv4 service to an end-user network (such as a residential home network), it can equally be applied to an individual host acting as a CE. Configuration of the BR is out of scope for this document.
此备忘录指定了一组DHCPv6[RFC3315]选项，用于向CE路由器提供Softwire46配置信息。尽管重点是向最终用户网络（如住宅家庭网络）提供IPv4服务，但它同样可以应用于充当CE的单个主机。BR的配置超出了本文档的范围。
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 describes a set of common DHCPv6 options for configuring the Mapping of Address and Port with Encapsulation (MAP-E) [RFC7597], Mapping of Address and Port using Translation (MAP-T) [RFC7599], and Lightweight 4over6 [RFC7596] mechanisms. For definitions of the terminology used in this document, please see the relevant terminology sections in [RFC7597], [RFC7599], and [RFC7596].
本文档描述了一组常见的DHCPv6选项，用于配置带有封装（MAP-E）[RFC7597]的地址和端口映射、使用转换（MAP-T）[RFC7599]的地址和端口映射以及轻量级4over6[RFC7596]机制。有关本文件中使用的术语的定义，请参见[RFC7597]、[RFC7599]和[RFC7596]中的相关术语部分。
MAP-E, MAP-T, and Lightweight 4over6 are essentially providing the same functionality: IPv4 service to a CE router over an IPv6-only access network. MAP-E and MAP-T may embed parts of the IPv4 address in IPv6 prefixes, thereby supporting many clients with a fixed set of mapping rules and Mesh mode (direct CE-to-CE communication). MAP-E and MAP-T CEs may also be provisioned in hub-and-spoke mode and in 1:1 mode (with no embedded address bits). The difference between MAP-E and MAP-T is that they use different means to connect to the IPv6 domain. MAP-E uses IPv4-over-IPv6 tunneling [RFC2473], while MAP-T uses IPv4-to-IPv6 translation based on [RFC6145]. Lightweight 4over6 is a hub-and-spoke IPv4-over-IPv6 tunneling mechanism, with complete independence of IPv4 and IPv6 addressing (zero embedded address bits).
MAP-E、MAP-T和轻量级4over6基本上提供了相同的功能：通过仅限IPv6的接入网络向CE路由器提供IPv4服务。MAP-E和MAP-T可以在IPv6前缀中嵌入部分IPv4地址，从而通过一组固定的映射规则和网状模式（直接CE到CE通信）支持许多客户端。MAP-E和MAP-T CE也可以在集线器和分支模式以及1:1模式（没有嵌入式地址位）下提供。MAP-E和MAP-T之间的区别在于，它们使用不同的方式连接到IPv6域。MAP-E使用IPv4-over-IPv6隧道[RFC2473]，而MAP-T使用基于[RFC6145]的IPv4-to-IPv6转换。轻量级4over6是一种中心辐射式IPv4-over-IPv6隧道机制，完全独立于IPv4和IPv6寻址（零嵌入地址位）。
The DHCPv6 options described here tie the provisioning parameters, and hence the IPv4 service itself, to the End-user IPv6 prefix lifetime. The validity of a Softwire46's IPv4 address, prefix, or shared IPv4 address; port set; and any authorization and accounting are tied to the lifetime of its associated End-user IPv6 prefix.
这里描述的DHCPv6选项将配置参数以及IPv4服务本身与最终用户IPv6前缀生存期联系起来。Softwire46的IPv4地址、前缀或共享IPv4地址的有效性；端口集；任何授权和记帐都与相关最终用户IPv6前缀的生存期相关联。
To support more than one mechanism at a time and to allow for a possibility of transition between them, the DHCPv6 Option Request Option (ORO) [RFC3315] is used. Each mechanism has a corresponding DHCPv6 container option. A DHCPv6 client can request a particular mechanism by including the option code for a particular container option in its ORO. The provisioning parameters for that mechanism are expressed by embedding the common format options within the respective container option.
为了一次支持多个机制并允许在它们之间进行转换，使用了DHCPv6选项请求选项（ORO）[RFC3315]。每个机制都有相应的DHCPv6容器选项。DHCPv6客户端可以通过在其ORO中包含特定容器选项的选项代码来请求特定机制。该机制的配置参数通过在相应的容器选项中嵌入公共格式选项来表示。
This approach implies that all of the provisioning options appear only within the container options. Softwire46 DHCPv6 clients that receive provisioning options that are not encapsulated in container options MUST silently ignore these options. DHCPv6 server administrators are advised to ensure that DHCPv6 servers are configured to send these options in the proper encapsulation.
这种方法意味着所有的配置选项都只出现在容器选项中。接收未封装在容器选项中的配置选项的Softwire46 DHCPv6客户端必须以静默方式忽略这些选项。建议DHCPv6服务器管理员确保将DHCPv6服务器配置为以正确的封装方式发送这些选项。
This document is organized with the common encapsulated options described first (Section 4), followed by the three container options (Section 5). Some encapsulated options are mandatory in some containers, some are optional, and some are not permitted. This is shown in Table 1 (Section 6).
本文档首先使用了常见的封装选项（第4节），然后是三个容器选项（第5节）。有些封装选项在某些容器中是强制性的，有些是可选的，有些是不允许的。如表1（第6节）所示。
The DHCPv6 protocol is used for Softwire46 CE provisioning following regular DHCPv6 notions, with the CE assuming the role of a DHCPv6 client, and the DHCPv6 server providing options following DHCPv6 server-side policies. The format and usage of the options are defined in the following subsections.
DHCPv6协议用于遵循常规DHCPv6概念的Softwire 46 CE资源调配，CE承担DHCPv6客户端的角色，DHCPv6服务器提供遵循DHCPv6服务器端策略的选项。选项的格式和用法在以下小节中定义。
Each CE needs to be provisioned with enough information to calculate its IPv4 address, IPv4 prefix, or shared IPv4 address. MAP-E and MAP-T use the OPTION_S46_RULE option, while Lightweight 4over6 uses the OPTION_S46_V4V6BIND option. A CE that needs to communicate outside of the A+P domain also needs the address or prefix of the BR. MAP-E and Lightweight 4over6 use the OPTION_S46_BR option to communicate the IPv6 address of the BR. MAP-T forms an IPv6 destination address by embedding an IPv4 destination address into the BR's IPv6 prefix conveyed via the OPTION_S46_DMR option. Optionally, all mechanisms can include the OPTION_S46_PORTPARAMS option to specify parameters and port sets for the port-range algorithm.
每个CE都需要提供足够的信息来计算其IPv4地址、IPv4前缀或共享IPv4地址。MAP-E和MAP-T使用选项S46_RULE选项，而轻量级4over6使用选项S46_V4V6BIND选项。需要在A+P域之外通信的CE也需要BR的地址或前缀。MAP-E和轻量级4over6使用选项_S46_BR选项通信BR的IPv6地址。MAP-T通过将IPv4目标地址嵌入BR的IPv6前缀（通过选项_S46_DMR选项传送）来形成IPv6目标地址。（可选）所有机制都可以包括选项S46_PORTPARAMS选项，以指定端口范围算法的参数和端口集。
Softwire46 options use addresses rather than Fully Qualified Domain Names (FQDNs). For the rationale behind this design choice, see Section 8 of [RFC7227].
Softwire46选项使用地址而不是完全限定域名（FQDN）。有关此设计选择背后的基本原理，请参见[RFC7227]第8节。
Figure 1 shows the format of the S46 Rule option (OPTION_S46_RULE) used for conveying the Basic Mapping Rule (BMR) and Forwarding Mapping Rule (FMR).
图1显示了用于传输基本映射规则（BMR）和转发映射规则（FMR）的S46规则选项（option_S46_Rule）的格式。
This option follows behavior described in Sections 17.1.1 and 18.1.1 of [RFC3315]. Clients can send those options, encapsulated in their respective container options, with specific values as hints for the server. See Section 5 for details. Depending on the server configuration and policy, it may accept or ignore the hints. Clients MUST be able to process received values that are different than the hints it sent earlier.
该选项遵循[RFC3315]第17.1.1节和第18.1.1节中描述的行为。客户端可以发送封装在各自容器选项中的选项，并将特定值作为服务器提示。详见第5节。根据服务器配置和策略，它可能接受或忽略提示。客户端必须能够处理接收到的值，这些值与它先前发送的提示不同。
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_S46_RULE | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| flags | ea-len | prefix4-len | ipv4-prefix |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (continued) | prefix6-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ipv6-prefix |
| (variable length) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. S46_RULE-options .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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_S46_RULE | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| flags | ea-len | prefix4-len | ipv4-prefix |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (continued) | prefix6-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ipv6-prefix |
| (variable length) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. S46_RULE-options .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: S46 Rule Option
图1:S46规则选项
o option-code: OPTION_S46_RULE (89)
o 选项代码：选项46规则（89）
o option-length: length of the option, excluding option-code and option-length fields, including length of all encapsulated options; expressed in octets.
o 选项长度：选项的长度，不包括选项编码和选项长度字段，包括所有封装选项的长度；以八位字节表示。
o flags: 8 bits long; carries flags applicable to the rule. The meanings of the specific bits are explained in Figure 2.
o 标志：8位长；携带适用于规则的标志。图2中解释了特定位的含义。
o ea-len: 8 bits long; specifies the Embedded Address (EA) bit length. Allowed values range from 0 to 48.
o ealen:8位长；指定嵌入地址（EA）位长度。允许的值范围为0到48。
o prefix4-len: 8 bits long; expresses the prefix length of the Rule IPv4 prefix specified in the ipv4-prefix field. Allowed values range from 0 to 32.
o prefix4 len:8位长；表示在IPv4前缀字段中指定的规则IPv4前缀的前缀长度。允许的值范围为0到32。
o ipv4-prefix: a fixed-length 32-bit field that specifies the IPv4 prefix for the S46 rule. The bits in the prefix after prefix4-len number of bits are reserved and MUST be initialized to zero by the sender and ignored by the receiver.
o ipv4前缀：一个固定长度的32位字段，用于指定S46规则的ipv4前缀。prefix4 len位数之后的前缀中的位是保留的，发送方必须将其初始化为零，接收方则忽略。
o prefix6-len: 8 bits long; expresses the length of the Rule IPv6 prefix specified in the ipv6-prefix field. Allowed values range from 0 to 128.
o prefix6 len:8位长；表示在IPv6前缀字段中指定的规则IPv6前缀的长度。允许的值范围为0到128。
o ipv6-prefix: a variable-length field that specifies the IPv6 domain prefix for the S46 rule. The field is padded on the right with zero bits up to the nearest octet boundary when prefix6-len is not evenly divisible by 8.
o ipv6前缀：一个可变长度字段，用于指定S46规则的ipv6域前缀。当prefix6 len不能被8平均整除时，字段在右侧填充零位，直到最近的八位字节边界。
o S46_RULE-options: a variable-length field that may contain zero or more options that specify additional parameters for this S46 rule. This document specifies one such option: OPTION_S46_PORTPARAMS.
o S46_RULE-options：一个可变长度字段，可能包含零个或多个选项，这些选项指定此S46规则的附加参数。本文档指定了一个这样的选项：option_S46_PORTPARAMS。
The format of the S46 Rule Flags field is:
S46规则标志字段的格式为：
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
|Reserved |F|
+-+-+-+-+-+-+-+-+
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
|Reserved |F|
+-+-+-+-+-+-+-+-+
Figure 2: S46 Rule Flags
图2:S46规则标志
o Reserved: 7 bits; reserved for future use as flags.
o 预留：7位；保留供将来用作标志。
o F-flag: 1-bit field that specifies whether the rule is to be used for forwarding (FMR). If set, this rule is used as an FMR; if not set, this rule is a BMR only and MUST NOT be used for forwarding. Note: A BMR can also be used as an FMR for forwarding if the F-flag is set. The BMR is determined by a longest-prefix match of the Rule IPv6 prefix against the End-user IPv6 prefix(es).
o F标志：指定规则是否用于转发（FMR）的1位字段。如果设置，则该规则用作FMR；如果未设置，则此规则仅为BMR，不得用于转发。注意：如果设置了F标志，BMR也可以用作转发的FMR。BMR由规则IPv6前缀与最终用户IPv6前缀的最长前缀匹配确定。
It is expected that in a typical mesh deployment scenario there will be a single BMR, which could also be designated as an FMR using the F-flag.
预计在典型的mesh部署场景中，将有一个BMR，也可以使用F标志将其指定为FMR。
The S46 BR option (OPTION_S46_BR) is used to convey the IPv6 address of the Border Relay. Figure 3 shows the format of the OPTION_S46_BR option.
S46 BR选项（option_S46_BR）用于传送边界中继的IPv6地址。图3显示了选项_S46_BR选项的格式。
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_S46_BR | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| br-ipv6-address |
| |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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_S46_BR | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| br-ipv6-address |
| |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: S46 BR Option
图3:S46 BR选项
o option-code: OPTION_S46_BR (90)
o 选项代码：选项_S46_BR（90）
o option-length: 16
o 选项长度：16
o br-ipv6-address: a fixed-length field of 16 octets that specifies the IPv6 address for the S46 BR.
o br-ipv6-address：16个八位字节的固定长度字段，用于指定S46 br的ipv6地址。
BR redundancy can be implemented by using an anycast address for the BR IPv6 address. Multiple OPTION_S46_BR options MAY be included in the container; this document does not further explore the use of multiple BR IPv6 addresses.
BR冗余可以通过使用BR IPv6地址的选播地址来实现。容器中可包括多个选项_S46 _BR选项；本文档不进一步探讨多个BR IPv6地址的使用。
The S46 DMR option (OPTION_S46_DMR) is used to convey values for the Default Mapping Rule (DMR). Figure 4 shows the format of the OPTION_S46_DMR option used for conveying a DMR.
S46 DMR选项（option_S46_DMR）用于传递默认映射规则（DMR）的值。图4显示了用于传输DMR的选项_S46_DMR选项的格式。
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_S46_DMR | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|dmr-prefix6-len| dmr-ipv6-prefix |
+-+-+-+-+-+-+-+-+ (variable length) |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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_S46_DMR | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|dmr-prefix6-len| dmr-ipv6-prefix |
+-+-+-+-+-+-+-+-+ (variable length) |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: S46 DMR Option
图4:S46 DMR选项
o option-code: OPTION_S46_DMR (91)
o 选项代码：选项_S46_DMR（91）
o option-length: 1 + length of dmr-ipv6-prefix specified in octets.
o 选项长度：1+以八位字节指定的dmr-ipv6-前缀长度。
o dmr-prefix6-len: 8 bits long; expresses the bitmask length of the IPv6 prefix specified in the dmr-ipv6-prefix field. Allowed values range from 0 to 128.
o dmr-prefix6-len：8位长；表示在dmr-IPv6-prefix字段中指定的IPv6前缀的位掩码长度。允许的值范围为0到128。
o dmr-ipv6-prefix: a variable-length field specifying the IPv6 prefix or address for the BR. This field is right-padded with zeros to the nearest octet boundary when dmr-prefix6-len is not divisible by 8.
o dmr-ipv6-prefix：一个可变长度字段，指定BR的ipv6前缀或地址。当dmr-prefix6-len不能被8整除时，此字段用零右填充到最近的八位字节边界。
The S46 IPv4/IPv6 Address Binding option (OPTION_S46_V4V6BIND) MAY be used to specify the full or shared IPv4 address of the CE. The IPv6 prefix field is used by the CE to identify the correct prefix to use for the tunnel source.
S46 IPv4/IPv6地址绑定选项（选项S46_V4V6BIND）可用于指定CE的完整或共享IPv4地址。CE使用IPv6前缀字段来标识用于隧道源的正确前缀。
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_S46_V4V6BIND | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ipv4-address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|bindprefix6-len| bind-ipv6-prefix |
+-+-+-+-+-+-+-+-+ (variable length) |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. S46_V4V6BIND-options .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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_S46_V4V6BIND | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ipv4-address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|bindprefix6-len| bind-ipv6-prefix |
+-+-+-+-+-+-+-+-+ (variable length) |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. S46_V4V6BIND-options .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: S46 IPv4/IPv6 Address Binding Option
图5:S46 IPv4/IPv6地址绑定选项
o option-code: OPTION_S46_V4V6BIND (92)
o 选项代码：选项_S46_V4V6BIND（92）
o option-length: length of the option, excluding option-code and option-length fields, including length of all encapsulated options; expressed in octets.
o 选项长度：选项的长度，不包括选项编码和选项长度字段，包括所有封装选项的长度；以八位字节表示。
o ipv4-address: a fixed-length field of 4 octets specifying an IPv4 address.
o ipv4地址：指定ipv4地址的4个八位字节的固定长度字段。
o bindprefix6-len: 8 bits long; expresses the bitmask length of the IPv6 prefix specified in the bind-ipv6-prefix field. Allowed values range from 0 to 128.
o bindprefix6透镜：8位长；表示在bind-IPv6-prefix字段中指定的IPv6前缀的位掩码长度。允许的值范围为0到128。
o bind-ipv6-prefix: a variable-length field specifying the IPv6 prefix or address for the S46 CE. This field is right-padded with zeros to the nearest octet boundary when bindprefix6-len is not divisible by 8.
o bind-ipv6-prefix：一个可变长度字段，指定S46 CE的ipv6前缀或地址。当bindprefix6 len不能被8整除时，此字段用零右填充到最近的八位字节边界。
o S46_V4V6BIND-options: a variable-length field that may contain zero or more options that specify additional parameters. This document specifies one such option: OPTION_S46_PORTPARAMS.
o S46_V4V6BIND-options：一个可变长度字段，可能包含零个或多个指定附加参数的选项。本文档指定了一个这样的选项：option_S46_PORTPARAMS。
The S46 Port Parameters option (OPTION_S46_PORTPARAMS) specifies optional port set information that MAY be provided to CEs.
S46端口参数选项（option_S46_PORTPARAMS）指定可提供给CEs的可选端口集信息。
See Section 5.1 of [RFC7597] for a description of the MAP algorithm and detailed explanation of all of the parameters.
有关MAP算法的说明和所有参数的详细说明，请参见[RFC7597]第5.1节。
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_S46_PORTPARAMS | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| offset | PSID-len | PSID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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_S46_PORTPARAMS | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| offset | PSID-len | PSID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: S46 Port Parameters Option
图6:S46端口参数选项
o option-code: OPTION_S46_PORTPARAMS (93)
o 选项代码：选项_S46_端口参数（93）
o option-length: 4
o 选项长度：4
o offset: Port Set Identifier (PSID) offset. 8 bits long; specifies the numeric value for the S46 algorithm's excluded port range/ offset bits (a-bits), as per Section 5.1 of [RFC7597]. Allowed values are between 0 and 15. Default values for this field are specific to the softwire mechanism being implemented and are defined in the relevant specification document.
o 偏移量：端口集标识符（PSID）偏移量。8位长；根据[RFC7597]第5.1节，指定S46算法排除的端口范围/偏移位（a位）的数值。允许的值介于0和15之间。此字段的默认值特定于正在实施的软线机制，并在相关规范文档中定义。
o PSID-len: 8 bits long; specifies the number of significant bits in the PSID field (also known as 'k'). When set to 0, the PSID field is to be ignored. After the first 'a' bits, there are k bits in the port number representing the value of the PSID. Consequently, the address-sharing ratio would be 2^k.
o PSID len：8位长；指定PSID字段中的有效位数（也称为“k”）。设置为0时，将忽略PSID字段。在第一个“a”位之后，端口号中有k位表示PSID的值。因此，地址共享比率将为2^k。
o PSID: 16 bits long. The PSID value algorithmically identifies a set of ports assigned to a CE. The first k bits on the left of this field contain the PSID binary value. The remaining (16 - k) bits on the right are padding zeros.
o PSID:16位长。PSID值通过算法识别分配给CE的一组端口。该字段左侧的前k位包含PSID二进制值。右边剩余的（16-k）位是填充零。
When receiving the OPTION_S46_PORTPARAMS option with an explicit PSID, the client MUST use this explicit PSID when configuring its softwire interface. The OPTION_S46_PORTPARAMS option with an explicit PSID MUST be discarded if the S46 CE isn't configured with a full IPv4 address (e.g., IPv4 prefix).
当接收带有显式PSID的选项_S46_PORTPARAMS选项时，客户端在配置其软线接口时必须使用此显式PSID。如果S46 CE未配置完整的IPv4地址（例如IPv4前缀），则必须放弃带有显式PSID的选项\u S46\u PORTPARAMS选项。
The OPTION_S46_PORTPARAMS option is contained within an OPTION_S46_RULE option or an OPTION_S46_V4V6BIND option.
选项“”PORTPARAMS选项包含在选项“”规则选项或选项“”V4V6BIND选项中。
The S46 MAP-E Container option (OPTION_S46_CONT_MAPE) specifies the container used to group all rules and optional port parameters for a specified domain.
S46 MAP-E容器选项（Options46_CONT_MAPE）指定用于为指定域对所有规则和可选端口参数进行分组的容器。
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_S46_CONT_MAPE | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. encapsulated-options (variable length) .
. .
+---------------------------------------------------------------+
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_S46_CONT_MAPE | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. encapsulated-options (variable length) .
. .
+---------------------------------------------------------------+
Figure 7: S46 MAP-E Container Option
图7:S46 MAP-E容器选项
o option-code: OPTION_S46_CONT_MAPE (94)
o 选项代码：选项46\u CONT\u MAPE（94）
o option-length: length of encapsulated options, expressed in octets.
o 选项长度：封装选项的长度，以八位字节表示。
o encapsulated-options: options associated with this Softwire46 MAP-E domain.
o 封装选项：与此Softwire46 MAP-E域关联的选项。
The encapsulated-options field conveys options specific to the OPTION_S46_CONT_MAPE option. Currently, there are two encapsulated options specified: OPTION_S46_RULE and OPTION_S46_BR. There MUST be at least one OPTION_S46_RULE option and at least one OPTION_S46_BR option.
封装选项字段传递特定于选项的选项。目前，指定了两个封装选项：OPTION_S46_RULE和OPTION_S46_BR。必须至少有一个选项\u S46\u规则选项和至少一个选项\u S46\u BR选项。
Other options applicable to a domain may be defined in the future. A DHCPv6 message MAY include multiple OPTION_S46_CONT_MAPE options (representing multiple domains).
将来可能会定义适用于域的其他选项。DHCPv6消息可以包括多个选项（表示多个域）。
The S46 MAP-T Container option (OPTION_S46_CONT_MAPT) specifies the container used to group all rules and optional port parameters for a specified domain.
S46 MAP-T容器选项（options46_CONT_MAPT）指定用于为指定域对所有规则和可选端口参数进行分组的容器。
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_S46_CONT_MAPT | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. encapsulated-options (variable length) .
. .
+---------------------------------------------------------------+
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_S46_CONT_MAPT | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. encapsulated-options (variable length) .
. .
+---------------------------------------------------------------+
Figure 8: S46 MAP-T Container Option
图8:S46 MAP-T容器选项
o option-code: OPTION_S46_CONT_MAPT (95)
o 选项代码：选项46\u CONT\u MAPT（95）
o option-length: length of encapsulated options, expressed in octets.
o 选项长度：封装选项的长度，以八位字节表示。
o encapsulated-options: options associated with this Softwire46 MAP-T domain.
o 封装选项：与此Softwire46 MAP-T域关联的选项。
The encapsulated-options field conveys options specific to the OPTION_S46_CONT_MAPT option. Currently, there are two options specified: the OPTION_S46_RULE and OPTION_S46_DMR options. There MUST be at least one OPTION_S46_RULE option and exactly one OPTION_S46_DMR option.
封装的选项字段传递特定于选项\u S46\u CONT\u MAPT选项的选项。目前，指定了两个选项：OPTION_S46_规则和OPTION_S46_DMR选项。必须至少有一个选项\u S46\u规则选项和一个选项\u S46\u DMR选项。
The S46 Lightweight 4over6 Container option (OPTION_S46_CONT_LW) specifies the container used to group all rules and optional port parameters for a specified domain.
S46轻量级4over6容器选项（option_S46_CONT_LW）指定用于对指定域的所有规则和可选端口参数进行分组的容器。
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_S46_CONT_LW | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ encapsulated-options (variable length) .
. .
+---------------------------------------------------------------+
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_S46_CONT_LW | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ encapsulated-options (variable length) .
. .
+---------------------------------------------------------------+
Figure 9: S46 Lightweight 4over6 Container Option
图9:S46轻型4over6容器选项
o option-code: OPTION_S46_CONT_LW (96)
o 选件代码：选件编号46选件编号LW（96）
o option-length: length of encapsulated options, expressed in octets.
o 选项长度：封装选项的长度，以八位字节表示。
o encapsulated-options: options associated with this Softwire46 Lightweight 4over6 domain.
o 封装选项：与此Softwire46轻量级4over6域关联的选项。
The encapsulated-options field conveys options specific to the OPTION_S46_CONT_LW option. Currently, there are two options specified: OPTION_S46_V4V6BIND and OPTION_S46_BR. There MUST be at most one OPTION_S46_V4V6BIND option and at least one OPTION_S46_BR option.
封装选项字段传递特定于选项的选项。目前，指定了两个选项：选项_S46_V4V6BIND和选项_S46_BR。必须最多有一个选项_S46_v4v6绑定选项和至少一个选项_S46_BR选项。
The table below shows which encapsulated options are mandatory, optional, or not permitted for each defined container option.
下表显示了对于每个已定义的容器选项，哪些封装选项是必需的、可选的或不允许的。
+-----------------------+-------+-------+--------------------+
| Option | MAP-E | MAP-T | Lightweight 4over6 |
+-----------------------+-------+-------+--------------------+
| OPTION_S46_RULE | M | M | N/P |
| OPTION_S46_BR | M | N/P | M |
| OPTION_S46_PORTPARAMS | O | O | O |
| OPTION_S46_DMR | N/P | M | N/P |
| OPTION_S46_V4V6BIND | N/P | N/P | O |
+-----------------------+-------+-------+--------------------+
+-----------------------+-------+-------+--------------------+
| Option | MAP-E | MAP-T | Lightweight 4over6 |
+-----------------------+-------+-------+--------------------+
| OPTION_S46_RULE | M | M | N/P |
| OPTION_S46_BR | M | N/P | M |
| OPTION_S46_PORTPARAMS | O | O | O |
| OPTION_S46_DMR | N/P | M | N/P |
| OPTION_S46_V4V6BIND | N/P | N/P | O |
+-----------------------+-------+-------+--------------------+
M - Mandatory, O - Optional, N/P - Not Permitted
M - Mandatory, O - Optional, N/P - Not Permitted
Table 1: Options for Container Mappings
表1：容器映射的选项
Softwire46 DHCPv6 clients that receive container options that violate any of the above rules MUST silently ignore such container options.
接收违反上述任何规则的容器选项的Softwire46 DHCPv6客户端必须以静默方式忽略此类容器选项。
Section 17.2.2 of [RFC3315] describes how a DHCPv6 client and server negotiate configuration values using the ORO. As a convenience for the reader, we mention here that by default a server will not reply with a Softwire46 container option if the client has not explicitly enumerated one in its ORO.
[RFC3315]的第17.2.2节描述了DHCPv6客户端和服务器如何使用ORO协商配置值。为了方便读者，我们在这里提到，默认情况下，如果客户端没有在其ORO中显式枚举Softwire46容器选项，服务器将不会使用Softwire46容器选项进行回复。
A CE router may support several (or all) of the mechanisms mentioned here. In the case where a client requests multiple mechanisms in its ORO, the server will reply with the corresponding Softwire46 container options for which it has configuration information.
CE路由器可以支持这里提到的几种（或全部）机制。如果客户机在其ORO中请求多个机制，服务器将使用其具有配置信息的相应Softwire46容器选项进行回复。
An S46 CE acting as a DHCPv6 client will request S46 configuration parameters from the DHCPv6 server located in the IPv6 network. Such a client MUST request the S46 container option(s) that it is configured for in its ORO in SOLICIT, REQUEST, RENEW, REBIND, and INFORMATION-REQUEST messages.
充当DHCPv6客户端的S46 CE将从位于IPv6网络中的DHCPv6服务器请求S46配置参数。这样的客户端必须在请求、请求、续订、重新绑定和信息请求消息中请求其ORO中配置的S46容器选项。
When processing received S46 container options, the following behavior is expected:
处理收到的S46容器选项时，预期会出现以下行为：
o A client MUST support processing multiple received OPTION_S46_RULE options in a container OPTION_S46_CONT_MAPE or OPTION_S46_CONT_MAPT option.
o 客户端必须支持在容器选项\u S46\u CONT\u MAPE或选项\u S46\u CONT\u MAPT选项中处理多个接收到的选项\u S46\u RULE选项。
o A client receiving an unsupported S46 option or an invalid parameter value SHOULD discard that S46 container option and log the event.
o 接收到不受支持的S46选项或无效参数值的客户端应放弃该S46容器选项并记录事件。
The behavior of a client that supports multiple Softwire46 mechanisms is out of scope for this document. [Unified-v4-in-v6] describes client behavior for the prioritization and handling of multiple mechanisms simultaneously.
支持多个Softwire46机制的客户端的行为超出本文档的范围。[Unified-v4-in-v6]描述了同时对多个机制进行优先级排序和处理的客户端行为。
Note that a system implementing CE functionality may have multiple network interfaces, and these interfaces may be configured differently; some may be connected to networks using a Softwire46 mechanism, and some may be connected to networks that are using normal dual-stack or other means. The CE should approach this specification on an interface-by-interface basis. For example, if the CE system is MAP-E capable and is attached to multiple networks that provide the OPTION_S46_CONT_MAPE option, then the CE MUST configure MAP-E for each interface separately.
注意，实现CE功能的系统可以具有多个网络接口，并且这些接口可以不同地配置；一些可以使用软线46机制连接到网络，一些可以连接到使用普通双栈或其他方式的网络。CE应在逐个接口的基础上接近本规范。例如，如果CE系统支持MAP-E，并且连接到提供选项_S46_CONT_MAPE选项的多个网络，则CE必须分别为每个接口配置MAP-E。
Failure modes are out of scope for this document. Failure recovery mechanisms may be defined in the future. See Section 5 of [RFC7597] for a discussion of valid MAP Rule combinations. See Section 11 of [RFC7227] and Sections 18.1.3, 18.1.4, and 19.1 of [RFC3315] for parameter-update mechanisms in DHCPv6 that can be leveraged to update configuration after a failure.
故障模式超出了本文档的范围。将来可能会定义故障恢复机制。有关有效映射规则组合的讨论，请参见[RFC7597]第5节。参见[RFC7227]第11节和[RFC3315]第18.1.3、18.1.4和19.1节，了解DHCPv6中可用于在故障后更新配置的参数更新机制。
Section 23 of [RFC3315] discusses DHCPv6-related security issues.
[RFC3315]第23节讨论了DHCPv6相关的安全问题。
As with all DHCPv6-derived configuration states, it is possible that configuration is actually being delivered by a third party (Man in the Middle). As such, there is no basis on which access over MAP or Lightweight 4over6 can be trusted. Therefore, softwires should not bypass any security mechanisms such as IP firewalls.
与所有DHCPv6派生的配置状态一样，配置可能实际上是由第三方（中间人）交付的。因此，通过MAP或轻量级4over6进行访问是不可信的。因此，软线不应绕过任何安全机制，如IP防火墙。
In IPv6-only networks that lack IPv4 firewalls, a device that supports MAP could be tricked into enabling its IPv4 stack and directing IPv4 traffic to the attacker, thus exposing itself to previously infeasible IPv4 attack vectors.
在缺少IPv4防火墙的纯IPv6网络中，支持MAP的设备可能会被诱骗启用其IPv4堆栈并将IPv4流量定向给攻击者，从而使自己暴露于以前不可行的IPv4攻击向量中。
Section 10 of [RFC7597] discusses security issues related to the MAP-E mechanism, Section 9 of [RFC7596] discusses security issues related to the Lightweight 4over6 mechanism, and Section 13 of [RFC7599] discusses security issues related to the MAP-T mechanism.
[RFC7597]的第10节讨论了与MAP-E机制相关的安全问题，[RFC7596]的第9节讨论了与轻量级4over6机制相关的安全问题，[RFC7599]的第13节讨论了与MAP-T机制相关的安全问题。
Readers concerned with the security of Softwire46 provisioning over DHCPv6 are encouraged to read [Secure-DHCPv6].
鼓励关心DHCPv6上Softwire 46资源调配安全性的读者阅读[Secure-DHCPv6]。
IANA has allocated the following DHCPv6 option codes:
IANA已分配以下DHCPv6选项代码：
89 for OPTION_S46_RULE
89对于选项_S46 _规则
90 for OPTION_S46_BR
选项为90\u S46\u BR
91 for OPTION_S46_DMR
91用于选项46\U DMR
92 for OPTION_S46_V4V6BIND
92用于选项_S46_V4V6BIND
93 for OPTION_S46_PORTPARAMS
93用于选项_S46_端口参数
94 for OPTION_S46_CONT_MAPE
94用于选项46\u CONT\u MAPE
95 for OPTION_S46_CONT_MAPT
95用于选项46\u CONT\u MAPT
96 for OPTION_S46_CONT_LW
96用于选项46（续）
All values have been added to the "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)" option code space defined in Section 24.3 of [RFC3315].
所有值都已添加到[RFC3315]第24.3节中定义的“IPv6动态主机配置协议（DHCPv6）”选项代码空间中。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，DOI 10.17487/RFC2119，1997年3月<http://www.rfc-editor.org/info/rfc2119>.
[RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July 2003, <http://www.rfc-editor.org/info/rfc3315>.
[RFC3315]Droms，R.，Ed.，Bound，J.，Volz，B.，Lemon，T.，Perkins，C.，和M.Carney，“IPv6的动态主机配置协议（DHCPv6）”，RFC 3315，DOI 10.17487/RFC3315，2003年7月<http://www.rfc-editor.org/info/rfc3315>.
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, DOI 10.17487/RFC2131, March 1997, <http://www.rfc-editor.org/info/rfc2131>.
[RFC2131]Droms，R.，“动态主机配置协议”，RFC 2131，DOI 10.17487/RFC2131，1997年3月<http://www.rfc-editor.org/info/rfc2131>.
[RFC2473] Conta, A. and S. Deering, "Generic Packet Tunneling in IPv6 Specification", RFC 2473, DOI 10.17487/RFC2473, December 1998, <http://www.rfc-editor.org/info/rfc2473>.
[RFC2473]Conta，A.和S.Deering，“IPv6规范中的通用数据包隧道”，RFC 2473，DOI 10.17487/RFC2473，1998年12月<http://www.rfc-editor.org/info/rfc2473>.
[RFC6145] Li, X., Bao, C., and F. Baker, "IP/ICMP Translation Algorithm", RFC 6145, DOI 10.17487/RFC6145, April 2011, <http://www.rfc-editor.org/info/rfc6145>.
[RFC6145]Li，X.，Bao，C.，和F.Baker，“IP/ICMP翻译算法”，RFC 6145DOI 10.17487/RFC6145，2011年4月<http://www.rfc-editor.org/info/rfc6145>.
[RFC6346] Bush, R., Ed., "The Address plus Port (A+P) Approach to the IPv4 Address Shortage", RFC 6346, DOI 10.17487/RFC6346, August 2011, <http://www.rfc-editor.org/info/rfc6346>.
[RFC6346]Bush，R.，Ed.，“IPv4地址短缺的地址加端口（A+P）方法”，RFC 6346，DOI 10.17487/RFC6346，2011年8月<http://www.rfc-editor.org/info/rfc6346>.
[RFC7227] Hankins, D., Mrugalski, T., Siodelski, M., Jiang, S., and S. Krishnan, "Guidelines for Creating New DHCPv6 Options", BCP 187, RFC 7227, DOI 10.17487/RFC7227, May 2014, <http://www.rfc-editor.org/info/rfc7227>.
[RFC7227]Hankins，D.，Mrugalski，T.，Siodelski，M.，Jiang，S.，和S.Krishnan，“创建新DHCPv6选项的指南”，BCP 187，RFC 7227，DOI 10.17487/RFC7227，2014年5月<http://www.rfc-editor.org/info/rfc7227>.
[RFC7596] Cui, Y., Sun, Q., Boucadair, M., Tsou, T., Lee, Y., and I. Farrer, "Lightweight 4over6: An Extension to the Dual-Stack Lite Architecture", RFC 7596, DOI 10.17487/RFC7596, July 2015, <http://www.rfc-editor.org/info/rfc7596>.
[RFC7596]Cui，Y.，Sun，Q.，Boucadair，M.，Tsou，T.，Lee，Y.，和I.Farrer，“轻量级4over6：双栈精简架构的扩展”，RFC 7596，DOI 10.17487/RFC75962015年7月<http://www.rfc-editor.org/info/rfc7596>.
[RFC7597] Troan, O., Ed., Dec, W., Li, X., Bao, C., Matsushima, S., Murakami, T., and T. Taylor, Ed., "Mapping of Address and Port with Encapsulation (MAP-E)", RFC 7597, DOI 10.17487/RFC7597, July 2015, <http://www.rfc-editor.org/info/rfc7597>.
[RFC7597]Troan，O.，Ed.，Dec，W.，Li，X.，Bao，C.，Matsushima，S.，Murakami，T.，和T.Taylor，Ed.，“地址和端口的封装映射（MAP-E）”，RFC 7597，DOI 10.17487/RFC7597，2015年7月<http://www.rfc-editor.org/info/rfc7597>.
[RFC7599] Li, X., Bao, C., Dec, W., Ed., Troan, O., Matsushima, S., and T. Murakami, "Mapping of Address and Port using Translation (MAP-T)", RFC 7599, DOI 10.17487/RFC7599, July 2015, <http://www.rfc-editor.org/info/rfc7599>.
[RFC7599]Li，X.，Bao，C.，Dec，W.，Ed.，Troan，O.，Matsushima，S.，和T.Murakami，“地址和端口映射使用翻译（MAP-T）”，RFC 7599，DOI 10.17487/RFC7599，2015年7月<http://www.rfc-editor.org/info/rfc7599>.
[Secure-DHCPv6] Jiang, S., Ed., Shen, S., Zhang, D., and T. Jinmei, "Secure DHCPv6", Work in Progress, draft-ietf-dhc-sedhcpv6-08, June 2015.
[Secure-DHCPv6]蒋S.，Ed.，沈S.，张D.，和T.Jinmei，“安全DHCPv6”，正在进行的工作，草案-ietf-dhc-sedhcpv6-082015年6月。
[Unified-v4-in-v6] Boucadair, M., Farrer, I., Perreault, S., Ed., and S. Sivakumar, Ed., "Unified IPv4-in-IPv6 Softwire CPE", Work in Progress, draft-ietf-softwire-unified-cpe-01, May 2013.
[Unified-v4-in-v6]Boucadair，M.，Farrer，I.，Perreault，S.，Ed.，和S.Sivakumar，Ed.，“统一IPv4-in-IPv6软线CPE”，正在进行的工作，草稿-ietf-Softwire-Unified-CPE-01，2013年5月。
Acknowledgements
致谢
This document was created as a product of a MAP design team. The following people were members of that team: Congxiao Bao, Mohamed Boucadair, Gang Chen, Maoke Chen, Wojciech Dec, Xiaohong Deng, Jouni Korhonen, Xing Li, Satoru Matsushima, Tomek Mrugalski, Tetsuya Murakami, Jacni Qin, Necj Scoberne, Qiong Sun, Tina Tsou, Dan Wing, Leaf Yeh, and Jan Zorz.
本文档是作为地图设计团队的产品创建的。以下人员是该团队的成员：聪晓宝、穆罕默德·布卡代尔、陈刚、陈茂科、沃伊切赫·德克、邓晓红、朱尼·科霍宁、邢莉、松岛佐藤、多梅克·姆鲁加尔斯基、村上铁树、秦杰尼、尼基·斯科伯尼、琼孙、邹天娜、丹荣、叶莉和简·佐尔茨。
The authors would like to thank Bernie Volz and Tom Taylor for their insightful comments and suggestions.
作者要感谢伯尼·沃尔兹和汤姆·泰勒提出的见解和建议。
Authors' Addresses
作者地址
Tomek Mrugalski Internet Systems Consortium, Inc. 950 Charter Street Redwood City, CA 94063 United States
美国加利福尼亚州红木市Charter Street 950号Tomek Mrugalski Internet Systems Consortium，Inc.94063
Phone: +1 650 423 1345
Email: tomasz.mrugalski@gmail.com
URI: http://www.isc.org/
Phone: +1 650 423 1345
Email: tomasz.mrugalski@gmail.com
URI: http://www.isc.org/
Ole Troan Cisco Systems Philip Pedersens vei 1 Lysaker 1366 Norway
Ole Troan Cisco Systems Philip Pedersens vei 1 Lysaker 1366挪威
Email: ot@cisco.com
Email: ot@cisco.com
Ian Farrer Deutsche Telekom AG CTO-ATI, Landgrabenweg 151 Bonn, NRW 53227 Germany
Ian Farrer Deutsche Telekom AG CTO-ATI，德国新南威尔士州波恩市兰德格拉本韦151号，邮编53227
Email: ian.farrer@telekom.de
Email: ian.farrer@telekom.de
Simon Perreault Jive Communications Quebec, QC Canada
Simon Perreault Jive Communications魁北克，加拿大QC
Email: sperreault@jive.com
Email: sperreault@jive.com
Wojciech Dec Cisco Systems, Inc. The Netherlands
Wojciech Dec思科系统公司，荷兰
Email: wdec@cisco.com
URI: http://cisco.com
Email: wdec@cisco.com
URI: http://cisco.com
Congxiao Bao CERNET Center/Tsinghua University Room 225, Main Building, Tsinghua University Beijing 100084 China
中国北京清华大学主楼225室/聪晓宝CERNET中心北京100084
Phone: +86 10-62785983
Email: congxiao@cernet.edu.cn
Phone: +86 10-62785983
Email: congxiao@cernet.edu.cn
Leaf Y. Yeh Freelancer Technologies China
叶Y.叶自由职业者技术中国
Email: leaf.y.yeh@hotmail.com
Email: leaf.y.yeh@hotmail.com
Xiaohong Deng The University of New South Wales Sydney NSW 2052 Australia
萧红登新南威尔士大学悉尼新南威尔士2052澳大利亚
Email: dxhbupt@gmail.com
URI: https://www.unsw.edu.au/
Email: dxhbupt@gmail.com
URI: https://www.unsw.edu.au/