Internet Engineering Task Force (IETF) S. Bhandari
Request for Comments: 7839 S. Gundavelli
Category: Standards Track M. Grayson
ISSN: 2070-1721 B. Volz
Cisco Systems
J. Korhonen
Broadcom Limited
June 2016
Internet Engineering Task Force (IETF) S. Bhandari
Request for Comments: 7839 S. Gundavelli
Category: Standards Track M. Grayson
ISSN: 2070-1721 B. Volz
Cisco Systems
J. Korhonen
Broadcom Limited
June 2016
Access-Network-Identifier Option in DHCP
DHCP中的访问网络标识符选项
Abstract
摘要
This document specifies the format and mechanism that is to be used for encoding Access-Network Identifiers in DHCPv4 and DHCPv6 messages by defining new Access-Network-Identifier options and sub-options.
本文档通过定义新的访问网络标识符选项和子选项，指定了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 7841.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 7841第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/rfc7839.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7839.
Copyright Notice
版权公告
Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2016 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. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. DHCPv4 Access-Network-Identifier Option . . . . . . . . . . . 5
4.1. DHCPv4 Access-Network-Identifier Sub-options . . . . . . 5
4.2. DHCPv4 Access-Technology-Type Sub-option . . . . . . . . 6
4.3. DHCPv4 Network-Identifier Sub-options . . . . . . . . . . 7
4.3.1. DHCPv4 Network-Name Sub-option . . . . . . . . . . . 7
4.3.2. DHCPv4 Access-Point-Name Sub-option . . . . . . . . . 8
4.3.3. DHCPv4 Access-Point-BSSID Sub-option . . . . . . . . 9
4.4. DHCPv4 Operator-Identifier Sub-options . . . . . . . . . 9
4.4.1. DHCPv4 Operator-Identifier Sub-option . . . . . . . . 9
4.4.2. DHCPv4 Operator-Realm Sub-option . . . . . . . . . . 10
5. DHCPv6 Access-Network-Identifier Options . . . . . . . . . . 10
5.1. DHCPv6 Access-Technology-Type Option . . . . . . . . . . 11
5.2. DHCPv6 Network-Identifier Options . . . . . . . . . . . . 11
5.2.1. DHCPv6 Network-Name Option . . . . . . . . . . . . . 12
5.2.2. DHCPv6 Access-Point-Name Option . . . . . . . . . . . 12
5.2.3. DHCPv6 Access-Point-BSSID Option . . . . . . . . . . 13
5.3. DHCPv6 Operator-Identifier Options . . . . . . . . . . . 13
5.3.1. DHCPv6 Operator-Identifier Option . . . . . . . . . . 13
5.3.2. DHCPv6 Operator-Realm Option . . . . . . . . . . . . 14
6. Relay Agent Behavior . . . . . . . . . . . . . . . . . . . . 14
7. Server Behavior . . . . . . . . . . . . . . . . . . . . . . . 15
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
9. Security Considerations . . . . . . . . . . . . . . . . . . . 17
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
10.1. Normative References . . . . . . . . . . . . . . . . . . 18
10.2. Informative References . . . . . . . . . . . . . . . . . 18
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. DHCPv4 Access-Network-Identifier Option . . . . . . . . . . . 5
4.1. DHCPv4 Access-Network-Identifier Sub-options . . . . . . 5
4.2. DHCPv4 Access-Technology-Type Sub-option . . . . . . . . 6
4.3. DHCPv4 Network-Identifier Sub-options . . . . . . . . . . 7
4.3.1. DHCPv4 Network-Name Sub-option . . . . . . . . . . . 7
4.3.2. DHCPv4 Access-Point-Name Sub-option . . . . . . . . . 8
4.3.3. DHCPv4 Access-Point-BSSID Sub-option . . . . . . . . 9
4.4. DHCPv4 Operator-Identifier Sub-options . . . . . . . . . 9
4.4.1. DHCPv4 Operator-Identifier Sub-option . . . . . . . . 9
4.4.2. DHCPv4 Operator-Realm Sub-option . . . . . . . . . . 10
5. DHCPv6 Access-Network-Identifier Options . . . . . . . . . . 10
5.1. DHCPv6 Access-Technology-Type Option . . . . . . . . . . 11
5.2. DHCPv6 Network-Identifier Options . . . . . . . . . . . . 11
5.2.1. DHCPv6 Network-Name Option . . . . . . . . . . . . . 12
5.2.2. DHCPv6 Access-Point-Name Option . . . . . . . . . . . 12
5.2.3. DHCPv6 Access-Point-BSSID Option . . . . . . . . . . 13
5.3. DHCPv6 Operator-Identifier Options . . . . . . . . . . . 13
5.3.1. DHCPv6 Operator-Identifier Option . . . . . . . . . . 13
5.3.2. DHCPv6 Operator-Realm Option . . . . . . . . . . . . 14
6. Relay Agent Behavior . . . . . . . . . . . . . . . . . . . . 14
7. Server Behavior . . . . . . . . . . . . . . . . . . . . . . . 15
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
9. Security Considerations . . . . . . . . . . . . . . . . . . . 17
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
10.1. Normative References . . . . . . . . . . . . . . . . . . 18
10.2. Informative References . . . . . . . . . . . . . . . . . 18
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
Access-network identification of a network device has a range of applications. For example, the Local Mobility Anchor (LMA) in a Proxy Mobile IPv6 (PMIPv6) domain is able to provide service treatment for the mobile node's traffic based on the access network to which the mobile node is attached.
网络设备的接入网标识具有广泛的应用。例如，代理移动IPv6（PMIPv6）域中的本地移动锚（LMA）能够基于移动节点所连接的接入网络为移动节点的业务提供服务处理。
This document specifies the Dynamic Host Configuration Protocol for IPv4 (DHCPv4) [RFC2131] and the Dynamic Host Configuration Protocol for IPv6 (DHCPv6) [RFC3315] options for access-network identification that is added by the relay agent in the DHCPv4 or DHCPv6 messages sent towards the server. The scope of applicability for this option is between a DHCP relay agent and a mobile access gateway where the same operator typically operates both these functions
本文档指定了IPv4的动态主机配置协议（DHCPv4）[RFC2131]和IPv6的动态主机配置协议（DHCPv6）[RFC3315]选项，用于中继代理在发送到服务器的DHCPv4或DHCPv6消息中添加的访问网络标识。此选项的适用范围在DHCP中继代理和移动接入网关之间，同一运营商通常操作这两种功能
A DHCP relay agent that is aware of the access network and access operator adds this information in the DHCP messages. This information can be used to provide differentiated services and policing of traffic based on the access network to which a client is attached. Examples of how this information can be used in mobile networks can be found in [RFC6757].
知道访问网络和访问操作员的DHCP中继代理将此信息添加到DHCP消息中。此信息可用于根据客户端所连接的接入网络提供差异化服务和流量监控。[RFC6757]中提供了如何在移动网络中使用这些信息的示例。
PMIPv6 [RFC5213] can be used for supporting network-based mobility management in various types of network deployments. The network architectures, such as service provider Wi-Fi access aggregation or WLAN integrated mobile packet core, are examples where PMIPv6 is a component of the overall architecture. Some of these architectures require the ability of the LMA [RFC5213] to provide differentiated services and policing of traffic to the mobile nodes based on the access network to which they are attached. Policy systems in mobility architectures, such as Policy and Charging Control (PCC) [TS23203] and Access Network Discovery and Selection Function (ANDSF) [TS23402] in the 3GPP system, allow configuration of policy rules with conditions based on the access-network information. For example, the service treatment for the mobile node's traffic may be different when they are attached to an access network owned by the home operator than when owned by a roaming partner. In the case of access networks based on IEEE 802.11, the service treatment can also be different based on the configured Service Set Identifiers (SSIDs). Other examples of services include the operator's ability to apply tariff based on the location.
PMIPv6[RFC5213]可用于在各种类型的网络部署中支持基于网络的移动性管理。网络架构（例如服务提供商Wi-Fi接入聚合或WLAN集成移动分组核心）是PMIPv6是整体架构的组件的示例。其中一些架构要求LMA[RFC5213]能够基于移动节点所连接的接入网络向移动节点提供区分服务和流量监控。移动性架构中的策略系统，例如3GPP系统中的策略和计费控制（PCC）[TS23203]和接入网络发现和选择功能（ANDSF）[TS23402]，允许基于接入网络信息配置具有条件的策略规则。例如，当移动节点的业务被连接到归属运营商拥有的接入网络时，其服务处理可能不同于当移动节点的业务被漫游伙伴拥有时的服务处理。在基于IEEE 802.11的接入网络的情况下，服务处理也可以基于配置的服务集标识符（ssid）而不同。服务的其他示例包括运营商根据位置应用电价的能力。
The PMIPv6 extension as specified in [RFC6757] defines PMIPv6 options to carry Access-Network Identifiers in PMIPv6 signaling from the Mobile Access Gateway (MAG) to the LMA. The MAG can learn this
[RFC6757]中规定的PMIPv6扩展定义了PMIPv6选项，以在PMIPv6信令中从移动接入网关（MAG）向LMA传送接入网络标识符。杂志可以了解这一点
information from the DHCP options as inserted by the DHCP relay agent in the access network. If the MAG relays the DHCP messages to the LMA as specified in [RFC5844], this information can be inserted by the MAG towards the LMA in the forwarded DHCP messages.
DHCP中继代理在访问网络中插入的来自DHCP选项的信息。如果MAG按照[RFC5844]中的规定将DHCP消息中继到LMA，则MAG可将此信息插入转发的DHCP消息中的LMA。
Figure 1 illustrates an example of PMIPv6 deployment. In this example, the access network is based on IEEE 802.11 technology, the DHCP relay agent function is located on the Access Point (AP), and the DHCP server function is located on the MAG. The MAG delivers the information elements related to the access network to the LMA over PMIPv6 signaling messages. The MAG obtains these information elements from the DHCP relay agent as per this specification. The information elements related to the access network include the SSID of the used IEEE 802.11 network, the geo-location of the access network to which the mobile node is attached, and the identity of the operator running the IEEE 802.11 access-network infrastructure.
图1展示了PMIPv6部署的示例。在此示例中，接入网络基于IEEE 802.11技术，DHCP中继代理功能位于接入点（AP）上，DHCP服务器功能位于MAG上。MAG通过PMIPv6信令消息向LMA发送与接入网络相关的信息元素。MAG根据本规范从DHCP中继代理获取这些信息元素。与接入网络相关的信息元素包括所使用的IEEE 802.11网络的SSID、移动节点连接到的接入网络的地理位置以及运行IEEE 802.11接入网络基础设施的运营商的身份。
SSID: IETF-1 Operator-Identifier: provider1.example
SSID:IETF-1操作员标识符：provider1.example
+--+
|AP|-----------. {Access-Specific Policies)
+--+ | (DHCP Server) _-----_ |
(DHCP Relay) +-----+ _( )_ +-----+
| MAG |-=========( PMIPv6 )======-| LMA |-
+-----+ (_ Tunnel_) +-----+
+--+ | '-----'
|AP|-----------'
+--+
(DHCP Relay)
+--+
|AP|-----------. {Access-Specific Policies)
+--+ | (DHCP Server) _-----_ |
(DHCP Relay) +-----+ _( )_ +-----+
| MAG |-=========( PMIPv6 )======-| LMA |-
+-----+ (_ Tunnel_) +-----+
+--+ | '-----'
|AP|-----------'
+--+
(DHCP Relay)
SSID: IETF-2 Operator-Identifier: provider2.example
SSID:IETF-2操作员标识符：provider2.example
Access Networks Attached to MAG
连接到MAG的接入网络
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]中所述进行解释。
All the DHCP-related terms used in this document are to be interpreted as defined in DHCPv4 [RFC2131] and DHCPv6 [RFC3315] specifications. "DHCP message" refers to both DHCPv4 and DHCPv6 messages throughout this document.
本文件中使用的所有DHCP相关术语应按照DHCPv4[RFC2131]和DHCPv6[RFC3315]规范中的定义进行解释。“DHCP消息”在本文档中同时指DHCPv4和DHCPv6消息。
All the mobility-related terms used in this document are to be interpreted as defined in the PMIPv6 specifications [RFC5213] and [RFC5844]. Additionally, this document uses the following abbreviations:
本文件中使用的所有移动性相关术语应按照PMIPv6规范[RFC5213]和[RFC5844]中的定义进行解释。此外，本文件使用以下缩写：
Service Set Identifier (SSID)
服务集标识符（SSID）
The Service Set Identifier (SSID) identifies the name of the IEEE 802.11 network. The SSID differentiates from one network to the other.
服务集标识符（SSID）标识IEEE 802.11网络的名称。SSID在不同的网络中有所不同。
Operator-Identifier
操作员标识符
The Operator-Identifier is the Structure of Management Information (SMI) Network Management Private Enterprise Code of the IANA-maintained "Private Enterprise Numbers" registry [SMI]. It identifies the operator running the access network where the client is attached.
运营商标识符是IANA维护的“私有企业编号”注册表[SMI]的管理信息结构（SMI）网络管理私有企业代码。它标识运行连接客户端的接入网络的运营商。
The Access-Network Identifier (ANI) carries information related to the identity of the access network to which the client is attached. This information includes access-technology type, network identifier, and access network operator identifiers.
接入网络标识符（ANI）携带与客户端所连接的接入网络的标识相关的信息。该信息包括接入技术类型、网络标识符和接入网络运营商标识符。
Relay agents that include ANI information include one or more sub-options (see Section 4.1) in the Relay Agent Information option [RFC3046].
包含ANI信息的中继代理包括中继代理信息选项[RFC3046]中的一个或多个子选项（见第4.1节）。
The Access-Network-Identifier information will be defined in multiple sub-options allocated from the "DHCP Relay Agent Sub-Option Codes" registry.
接入网络标识符信息将在从“DHCP中继代理子选项代码”注册表分配的多个子选项中定义。
ANI Sub-options: The ANI sub-options consist of a sequence of Sub-Option Code, Length, and Value tuples for each sub-option, encoded in the following manner:
ANI子选项：ANI子选项由每个子选项的子选项代码、长度和值元组序列组成，编码方式如下：
Subopt Len Sub-option Data
+------+------+------+------+------+------+--...-+------+
| code | N | s1 | s2 | s3 | s4 | | sN |
+------+------+------+------+------+------+--...-+------+
Subopt Len Sub-option Data
+------+------+------+------+------+------+--...-+------+
| code | N | s1 | s2 | s3 | s4 | | sN |
+------+------+------+------+------+------+--...-+------+
Subopt code The 1-octet code for the sub-options defined in the following sections.
Subopt代码以下各节中定义的sub选项的1-octet代码。
Len An unsigned 8-bit integer giving the length of the Sub-option Data field in this sub-option in octets.
Len一个无符号8位整数，给出此子选项中子选项数据字段的长度（以八位字节为单位）。
Sub-option Data (s1 to sN) The data area for the sub-option.
子选项数据（s1到sN）子选项的数据区域。
The initial assignment of the DHCP Access-Network-Identifier sub-options is as follows:
DHCP接入网络标识符子选项的初始分配如下：
+=================+=======================================+
| SUB-OPTION CODE | SUB-OPTION DESCRIPTION |
+=================+=======================================+
| 13 | Access-Technology-Type Sub-option |
+=========================================================+
| 14 | Access-Network-Name Sub-option |
+=========================================================+
| 15 | Access-Point-Name Sub-option |
+=========================================================+
| 16 | Access-Point-BSSID Sub-option |
+=========================================================+
| 17 | Operator-Identifier Sub-option |
+=========================================================+
| 18 | Operator-Realm Sub-option |
+=========================================================+
+=================+=======================================+
| SUB-OPTION CODE | SUB-OPTION DESCRIPTION |
+=================+=======================================+
| 13 | Access-Technology-Type Sub-option |
+=========================================================+
| 14 | Access-Network-Name Sub-option |
+=========================================================+
| 15 | Access-Point-Name Sub-option |
+=========================================================+
| 16 | Access-Point-BSSID Sub-option |
+=========================================================+
| 17 | Operator-Identifier Sub-option |
+=========================================================+
| 18 | Operator-Realm Sub-option |
+=========================================================+
This sub-option is used for exchanging the type of the access technology of the network to which the client is attached. Its format is as follows:
此子选项用于交换客户端所连接网络的访问技术类型。其格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Subopt Code | Length | Reserved | ATT |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Subopt Code | Length | Reserved | ATT |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Subopt Code 13
子节点代码13
Length 2
长度2
Reserved An 8-bit field that is unused for now. The value MUST be initialized to 0 by the sender and MUST be ignored by the receiver.
保留目前未使用的8位字段。发送方必须将该值初始化为0，接收方必须忽略该值。
Access-Technology-Type (ATT) An 8-bit field that specifies the access technology through which the client is connected to the access link from the IANA name space "Access Technology Type Option type values" registry defined in [RFC5213].
访问技术类型（ATT）：一个8位字段，用于指定访问技术，客户机通过该访问技术从[RFC5213]中定义的IANA名称空间“访问技术类型选项类型值”注册表连接到访问链路。
These sub-options are used for carrying the name of the access network (e.g., an SSID in the case of an IEEE 802.11 access network or a Public Land-based Mobile Network (PLMN) Identifier [TS23003] in the case of a 3GPP access network) and the Access-Point Name to which the client is attached. The format of these sub-options is defined in the following sections. The Network-Identifier sub-options are only for the currently known access-technology types.
这些子选项用于承载接入网络的名称（例如，在IEEE 802.11接入网络的情况下是SSID，在3GPP接入网络的情况下是公共陆地移动网络（PLMN）标识符[TS23003]）和客户端连接到的接入点名称。这些子选项的格式在以下部分中定义。网络标识符子选项仅适用于当前已知的访问技术类型。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Subopt Code | Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
. .
. Network-Name (e.g., SSID or PLMNID) .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Subopt Code | Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
. .
. Network-Name (e.g., SSID or PLMNID) .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Subopt Code 14
子节点代码14
Length The length of the Network-Name field.
Length网络名称字段的长度。
Network-Name The name of the access network to which the mobile node is attached. The encoding MUST be UTF-8 as described in [RFC3629].
Network Name移动节点所连接的接入网络的名称。编码必须为[RFC3629]中所述的UTF-8。
The type of the Network-Name is dependent on the access technology to which the mobile node is attached. For networks based on IEEE 802.11, the Network-Name will be the SSID of the network. For 3GPP access-based networks, it is the PLMN Identifier of the access network, and for 3GPP2 access, the Network-Name is the ANI [ANI].
网络名称的类型取决于移动节点所连接的接入技术。对于基于IEEE 802.11的网络，网络名称将是网络的SSID。对于基于3GPP接入的网络，它是接入网络的PLMN标识符，对于3GPP2接入，网络名称是ANI[ANI]。
When encoding the PLMN Identifier, both the Mobile Network Code (MNC) [TS23003] and Mobile Country Code (MCC) [TS23003] MUST be three digits. If the MNC in use only has two digits, then it MUST be preceded with a '0'.
编码PLMN标识符时，移动网络代码（MNC）[TS23003]和移动国家代码（MCC）[TS23003]必须为三位数字。如果使用中的MNC只有两位数字，则必须在其前面加上“0”。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Subopt Code | Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
. .
. Access-Point-Name .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Subopt Code | Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
. .
. Access-Point-Name .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Subopt Code 15
子节点代码15
Length The length of the Access-Point-Name field.
长度访问点名称字段的长度。
Access-Point-Name The name of the access point (physical device name) to which the mobile node is attached. This is the identifier that uniquely identifies the access point. While the Network-Name (e.g., SSID) identifies the operator's access network, the Access-Point-Name identifies a specific network device in the network to which the mobile node is attached. In some deployments, the Access-Point-Name can be set to the string representation of the Media Access Control (MAC) address of the device as specified in [RFC6991] (see mac-address typedef) or some unique identifier that can be used by the policy systems in the operator network to unambiguously identify the device. The encoding MUST be UTF-8 as described in [RFC3629].
接入点名称移动节点所连接的接入点的名称（物理设备名称）。这是唯一标识访问点的标识符。当网络名称（例如，SSID）标识运营商的接入网络时，接入点名称标识移动节点连接到的网络中的特定网络设备。在某些部署中，可以将接入点名称设置为[RFC6991]（请参阅MAC地址类型定义）中指定的设备的媒体访问控制（MAC）地址的字符串表示形式，或可由运营商网络中的策略系统用于明确标识设备的某个唯一标识符。编码必须为[RFC3629]中所述的UTF-8。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Subopt Code | Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| Access-Point-BSSID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Subopt Code | Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| Access-Point-BSSID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Subopt Code 16
子节点代码16
Length 6
长度6
Access-Point-BSSID The 48-bit Basic SSSID (BSSID) of the access point to which the mobile node is attached.
接入点BSSID移动节点所连接的接入点的48位基本SSSID（BSSID）。
The Operator-Identifier sub-options can be used for carrying the Operator-Identifiers of the access network to which the client is attached. The format of these sub-options is defined below.
操作员标识符子选项可用于承载客户端所连接的接入网络的操作员标识符。这些子选项的格式定义如下。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Subopt Code | Length | .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. Operator-Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Subopt Code | Length | .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. Operator-Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Subopt Code 17
子节点代码17
Length 4
长度4
Operator-Identifier The Operator-Identifier is a variable-length Private Enterprise Number (PEN) [SMI] encoded in a network byte order. Please refer to Section 3.1.3 of [RFC6757] for additional details.
操作员标识符操作员标识符是以网络字节顺序编码的可变长度私有企业编号（PEN）[SMI]。更多详细信息，请参考[RFC6757]第3.1.3节。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Subopt Code | Length | |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
. .
. Operator-Realm .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Subopt Code | Length | |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
. .
. Operator-Realm .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Subopt Code 18
子节点代码18
Length The length of the Operator-Realm field.
Length运算符域字段的长度。
Operator-Realm Realm of the operator (e.g., EXAMPLE.COM). Please refer to Section 3.1.3 of [RFC6757] for additional details.
操作员领域操作员的领域（例如，EXAMPLE.COM）。更多详细信息，请参考[RFC6757]第3.1.3节。
The Access-Network-Identifier options defined here may be added by the DHCPv6 relay agent in Relay-forward messages.
这里定义的接入网络标识符选项可由DHCPv6中继代理添加到中继转发消息中。
+=================+=======================================+
| OPTION CODE | OPTION DESCRIPTION |
+=================+=======================================+
| 105 | OPTION_ANI_ATT |
+=========================================================+
| 106 | OPTION_ANI_NETWORK_NAME |
+=========================================================+
| 107 | OPTION_ANI_AP_NAME |
+=========================================================+
| 108 | OPTION_ANI_AP_BSSID |
+=========================================================+
| 109 | OPTION_ANI_OPERATOR_ID |
+=========================================================+
| 110 | OPTION_ANI_OPERATOR_REALM |
+=========================================================+
+=================+=======================================+
| OPTION CODE | OPTION DESCRIPTION |
+=================+=======================================+
| 105 | OPTION_ANI_ATT |
+=========================================================+
| 106 | OPTION_ANI_NETWORK_NAME |
+=========================================================+
| 107 | OPTION_ANI_AP_NAME |
+=========================================================+
| 108 | OPTION_ANI_AP_BSSID |
+=========================================================+
| 109 | OPTION_ANI_OPERATOR_ID |
+=========================================================+
| 110 | OPTION_ANI_OPERATOR_REALM |
+=========================================================+
This option is used for exchanging the type of access technology the client uses to attach to the network. Its format is as follows:
此选项用于交换客户端用于连接到网络的访问技术类型。其格式如下：
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_ANI_ATT | Option-Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | ATT |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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_ANI_ATT | Option-Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | ATT |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option-Code OPTION_ANI_ATT (105)
选项代码选项ANI_附件（105）
Option-Len 2
选项2
Reserved An 8-bit field that is unused for now. The value MUST be initialized to 0 by the sender and MUST be ignored by the receiver.
保留目前未使用的8位字段。发送方必须将该值初始化为0，接收方必须忽略该值。
Access-Technology-Type (ATT): The contents of this field are the same as the ATT field described in Section 4.2.
接入技术类型（ATT）：该字段的内容与第4.2节中描述的ATT字段相同。
These options can be used for carrying the name of the access network (e.g., an SSID in the case of an IEEE 802.11 access network or a PLMN Identifier [TS23003] in the case of a 3GPP access network) and an Access-Point Name to which the client is attached. The format of these options is defined below.
这些选项可用于承载接入网络的名称（例如，在IEEE 802.11接入网络的情况下是SSID，在3GPP接入网络的情况下是PLMN标识符[TS23003]）和客户端连接到的接入点名称。这些选项的格式定义如下。
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_ANI_NETWORK_NAME | Option-Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. Network-Name (e.g., SSID or PLMNID) .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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_ANI_NETWORK_NAME | Option-Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. Network-Name (e.g., SSID or PLMNID) .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option-Code OPTION_ANI_NETWORK_NAME (106)
选项代码选项ANI网络名称（106）
Option-Len The length of the Network-Name field.
选项Len网络名称字段的长度。
Network-Name The contents of this field are the same as the Network-Name field described in Section 4.3.1.
网络名称该字段的内容与第4.3.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_ANI_AP_NAME | Option-Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. Access-Point-Name .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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_ANI_AP_NAME | Option-Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. Access-Point-Name .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option-Code OPTION_ANI_AP_NAME (107)
选项代码选项名称（107）
Option-Len The length of the Access-Point-Name field.
选项Len访问点名称字段的长度。
Access-Point-Name The contents of this field are the same as the Access-Point-Name field described in Section 4.3.2.
接入点名称该字段的内容与第4.3.2节中描述的接入点名称字段相同。
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_ANI_AP_BSSID | Option-Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access-Point-BSSID |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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_ANI_AP_BSSID | Option-Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access-Point-BSSID |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option-Code OPTION_ANI_AP_BSSID (108)
选项代码选项ANI AP BSSID（108）
Option-Len 6
选项Len 6
Access-Point-BSSID The contents of this field are the same as the Access-Point-BSSID field described in Section 4.3.3.
接入点BSSID该字段的内容与第4.3.3节中描述的接入点BSSID字段相同。
The Operator-Identifier options can be used for carrying the Operator-Identifier of the access network to which the client is attached. The format of these options is defined below.
操作员标识符选项可用于承载客户端所连接的接入网络的操作员标识符。这些选项的格式定义如下。
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_ANI_OPERATOR_ID | Option-Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Operator-Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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_ANI_OPERATOR_ID | Option-Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Operator-Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option-Code OPTION_ANI_OPERATOR_ID (109)
选项代码选项ANI操作员ID（109）
Option-Len 4
选项Len 4
Operator-Identifier The contents of this field are the same as the DHCPv4 Operator-Identifier Sub-option field described in Section 4.4.1.
操作员标识符该字段的内容与第4.4.1节中描述的DHCPv4操作员标识符子选项字段相同。
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_ANI_OPERATOR_REALM | Option-Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. Operator-Realm .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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_ANI_OPERATOR_REALM | Option-Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. Operator-Realm .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option-Code OPTION_ANI_OPERATOR_REALM (110)
选项代码选项ANI运算符领域（110）
Option-Len The length of the Operator-Realm field.
选项Len运算符域字段的长度。
Operator-Realm The contents of this field are the same as the Operator-Realm field described in Section 4.4.2.
操作员领域该字段的内容与第4.4.2节中描述的操作员领域字段相同。
DHCPv4 relay agents MAY include sub-options as defined in Section 4.2 through 4.4 of [RFC3046] in the Relay Agent Information option for providing information about the access network over which DHCP messages from the client are received.
DHCPv4中继代理可以在中继代理信息选项中包括[RFC3046]第4.2节至第4.4节中定义的子选项，用于提供有关接收来自客户端的DHCP消息的接入网络的信息。
The DHCPv4 relay agent MUST include the DHCPv4 Access-Technology-Type Sub-option (Section 4.2) when including any of these sub-options in the DHCP message: DHCPv4 Network-Name Sub-option (Section 4.3.1), DHCPv4 Access-Point-Name Sub-option (Section 4.3.2), and DHCPv4 Access-Point-BSSID Sub-option (Section 4.3.3).
当在DHCP消息中包括以下任何子选项时，DHCPv4中继代理必须包括DHCPv4访问技术类型子选项（第4.2节）：DHCPv4网络名称子选项（第4.3.1节）、DHCPv4访问点名称子选项（第4.3.2节）和DHCPv4访问点BSSID子选项（第4.3.3节）。
DHCPv6 Relay Agents MAY include options (defined in Section 5) in the Relay-forward message when forwarding any DHCPv6 message type from clients to the servers to provide information about the access network over which DHCPv6 messages from the client are received.
当从客户端向服务器转发任何DHCPv6消息类型时，DHCPv6中继代理可以在中继转发消息中包括选项（在第5节中定义），以提供有关接收来自客户端的DHCPv6消息的接入网络的信息。
The DHCPv6 relay agent MUST include the DHCPv6 Access-Technology-Type Option (Section 5.1) when including any of these options in the DHCP message: DHCPv6 Network-Name Option (Section 5.2.1), DHCPv6 Access-Point-Name Option (Section 5.2.2), and DHCPv6 Access-Point-BSSID Option (Section 5.2.3).
在DHCP消息中包括以下选项时，DHCPv6中继代理必须包括DHCPv6访问技术类型选项（第5.1节）：DHCPv6网络名称选项（第5.2.1节）、DHCPv6访问点名称选项（第5.2.2节）和DHCPv6访问点BSSID选项（第5.2.3节）。
The DHCPv4 base specification [RFC2131] requires that the DHCPv4 server ignore the DHCPv4 Access-Network-Identifier Option if it does not understand the option.
DHCPv4基本规范[RFC2131]要求DHCPv4服务器忽略DHCPv4访问网络标识符选项（如果不理解该选项）。
If the DHCPv4 server does not understand the received sub-option defined in Sections 4.1 through 4.4 of [RFC3046], the DHCPv4 Relay-Agent-Information Option, it MUST ignore those sub-options only. If the DHCPv4 server is able to process the DHCPv4 Access-Network-Identifier sub-options defined in Sections 4.1 through 4.4 of [RFC3046], the DHCPv4 Relay-Agent-Information Option, it MAY use this information obtained from the sub-option for address pool selection or for policy decisions as per its configured policy. This information obtained from the sub-option SHOULD NOT be stored unless it is absolutely needed. However, if it is stored, the information MUST be deleted as quickly as possible to eliminate any possibility of the information getting exposed to an intruder.
如果DHCPv4服务器不理解[RFC3046]第4.1节至第4.4节中定义的接收子选项，DHCPv4中继代理信息选项，则必须仅忽略这些子选项。如果DHCPv4服务器能够处理[RFC3046]第4.1节至第4.4节中定义的DHCPv4访问网络标识符子选项（DHCPv4中继代理信息选项），则它可以使用从子选项获得的该信息来选择地址池或根据其配置的策略进行策略决策。除非绝对需要，否则不应存储从子选项获得的信息。但是，如果存储了该信息，则必须尽快删除该信息，以消除信息暴露给入侵者的任何可能性。
The DHCPv4 server MUST ignore the received DHCPv4 Access-Network-Identifier Option and process the rest of the message as per the base DHCPv4 specifications if the received DHCPv4 message does not include the DHCPv4 Access-Technology-Type Sub-option (Section 4.2) but does include any one of these other options: DHCPv4 Network Name Sub-option (Section 4.3.1), DHCPv4 Access-Point-Name Sub-option (Section 4.3.2), or DHCPv4 Access-Point-BSSID Sub-option (Section 4.3.3).
如果接收到的DHCPv4消息不包括DHCPv4访问技术类型子选项（第4.2节），但包括其他选项中的任何一个：DHCPv4网络名称子选项，则DHCPv4服务器必须忽略接收到的DHCPv4访问网络标识符选项，并按照基本DHCPv4规范处理消息的其余部分（第4.3.1节）、DHCPv4接入点名称子选项（第4.3.2节）或DHCPv4接入点BSSID子选项（第4.3.3节）。
DHCPv6 base specification [RFC3315] requires that the DHCPv6 server ignore the DHCPv6 Access-Network-Identifier Option if it does not understand the option.
DHCPv6基本规范[RFC3315]要求DHCPv6服务器在不理解DHCPv6访问网络标识符选项时忽略该选项。
If the DHCPv6 server receives the options defined in Section 5 and is configured to use the options defined in Section 5, it SHOULD look for the DHCPv6 Access-Network-Identifier options in the Relay-forward message of the DHCPv6 relay agent(s) based on its configured policy. The server MAY use received ANI options for its address pool selection policy decisions as per its configured policy. This information obtained from the options SHOULD NOT be stored unless it is absolutely needed. However, if it is stored, the information MUST be deleted as quickly as possible to eliminate any possibility of the information getting exposed to an intruder.
如果DHCPv6服务器接收到第5节中定义的选项并配置为使用第5节中定义的选项，则它应根据其配置的策略在DHCPv6中继代理的中继转发消息中查找DHCPv6访问网络标识符选项。服务器可以根据其配置的策略，将收到的ANI选项用于其地址池选择策略决策。除非绝对需要，否则不应存储从选项中获得的信息。但是，如果存储了该信息，则必须尽快删除该信息，以消除信息暴露给入侵者的任何可能性。
The DHCPv6 server MUST ignore the received DHCPv6 Access-Network-Identifier Option and process the rest of the message as per the base DHCPv6 specifications if the received DHCPv6 message does not include the DHCPv6 Access-Technology-Type Option (Section 5.1) but it does includes any one of these other options: DHCPv6 Network-Name Option
如果收到的DHCPv6消息不包括DHCPv6访问技术类型选项（第5.1节），但包含以下任何一个其他选项：DHCPv6网络名称选项，则DHCPv6服务器必须忽略收到的DHCPv6访问网络标识符选项，并根据基本DHCPv6规范处理消息的其余部分
(Section 5.2.1), DHCPv6 Access-Point-Name Option (Section 5.2.2), or DHCPv6 Access-Point-BSSID Option (Section 5.2.3).
（第5.2.1节）、DHCPv6接入点名称选项（第5.2.2节）或DHCPv6接入点BSSID选项（第5.2.3节）。
IANA has assigned sub-option codes for the following DHCPv4 sub-options from the "DHCP Relay Agent Sub-Option Codes" registry, <http://www.iana.org/assignments/bootp-dhcp-parameters>:
IANA已从“DHCP中继代理子选项代码”注册表为以下DHCPv4子选项分配子选项代码<http://www.iana.org/assignments/bootp-dhcp-parameters>:
+=================+=======================================+
| SUB-OPTION CODE | SUB-OPTION DESCRIPTION |
+=================+=======================================+
| 13 | Access-Technology-Type Sub-option |
+=========================================================+
| 14 | Access-Network-Name Sub-option |
+=========================================================+
| 15 | Access-Point-Name Sub-option |
+=========================================================+
| 16 | Access-Point-BSSID Sub-option |
+=========================================================+
| 17 | Operator-Identifier Sub-option |
+=========================================================+
| 18 | Operator-Realm Sub-option |
+=========================================================+
+=================+=======================================+
| SUB-OPTION CODE | SUB-OPTION DESCRIPTION |
+=================+=======================================+
| 13 | Access-Technology-Type Sub-option |
+=========================================================+
| 14 | Access-Network-Name Sub-option |
+=========================================================+
| 15 | Access-Point-Name Sub-option |
+=========================================================+
| 16 | Access-Point-BSSID Sub-option |
+=========================================================+
| 17 | Operator-Identifier Sub-option |
+=========================================================+
| 18 | Operator-Realm Sub-option |
+=========================================================+
IANA has assigned option codes for the following DHCPv6 options from the "Option Codes" registry for DHCPv6, <http://www.iana.org/assignments/dhcpv6-parameters>, as specified in [RFC3315]:
IANA已从DHCPv6的“选项代码”注册表中为以下DHCPv6选项分配了选项代码<http://www.iana.org/assignments/dhcpv6-parameters>，如[RFC3315]所述：
+=================+=======================================+
| OPTION CODE | OPTION DESCRIPTION |
+=================+=======================================+
| 105 | OPTION_ANI_ATT |
+=========================================================+
| 106 | OPTION_ANI_NETWORK_NAME |
+=========================================================+
| 107 | OPTION_ANI_AP_NAME |
+=========================================================+
| 108 | OPTION_ANI_AP_BSSID |
+=========================================================+
| 109 | OPTION_ANI_OPERATOR_ID |
+=========================================================+
| 110 | OPTION_ANI_OPERATOR_REALM |
+=========================================================+
+=================+=======================================+
| OPTION CODE | OPTION DESCRIPTION |
+=================+=======================================+
| 105 | OPTION_ANI_ATT |
+=========================================================+
| 106 | OPTION_ANI_NETWORK_NAME |
+=========================================================+
| 107 | OPTION_ANI_AP_NAME |
+=========================================================+
| 108 | OPTION_ANI_AP_BSSID |
+=========================================================+
| 109 | OPTION_ANI_OPERATOR_ID |
+=========================================================+
| 110 | OPTION_ANI_OPERATOR_REALM |
+=========================================================+
Since there is no privacy protection for DHCP messages, an eavesdropper who can monitor the link between the DHCP server and relay agent can discover access-network information.
由于DHCP消息没有隐私保护，可以监视DHCP服务器和中继代理之间链接的窃听者可以发现访问网络信息。
[RFC3118] and [RFC3315] describe many of the threats in using DHCP. [RFC3118] and [RFC3315] each provide a solution; the Authentication Option for DHCPv4 and DHCPv6 (respectively). However, neither of these options are in active use and therefore are not a viable mitigation option. DHCP itself is inherently insecure and thus link-layer confidentiality and integrity protection SHOULD be employed to reduce the risk of disclosure and tampering.
[RFC3118]和[RFC3315]描述了使用DHCP时的许多威胁。[RFC3118]和[RFC3315]各提供一种解决方案；DHCPv4和DHCPv6的身份验证选项（分别）。然而，这两种方案均未得到积极使用，因此不是可行的缓解方案。DHCP本身固有的不安全性，因此应采用链路层机密性和完整性保护，以降低泄露和篡改的风险。
It is possible for a rogue DHCP relay agent to insert or overwrite with incorrect Access-Network-Identifier options for malicious purposes. A DHCP client can also pose as a rogue DHCP relay agent by sending incorrect Access-Network-Identifier options. While the introduction of fraudulent DHCP relay agent information options can be prevented by a perimeter defense that blocks these options unless the DHCP relay agent is trusted, a deeper defense using the authentication sub-option for the DHCPv4 Relay-Agent-Information Option [RFC4030] SHOULD be deployed as well. Administrators SHOULD configure DHCP servers that use this option to communicate with their relay agents using IPsec, as described in Section 21.1 of [RFC3315].
恶意DHCP中继代理可能出于恶意目的插入或覆盖不正确的访问网络标识符选项。通过发送不正确的访问网络标识符选项，DHCP客户端还可以冒充恶意DHCP中继代理。虽然引入欺诈性DHCP中继代理信息选项可以通过周界防御来防止，除非DHCP中继代理受信任，否则周界防御会阻止这些选项，但也应部署使用DHCPv4中继代理信息选项[RFC4030]的身份验证子选项的更深入防御。管理员应配置使用此选项的DHCP服务器，以使用IPsec与其中继代理进行通信，如[RFC3315]第21.1节所述。
The information elements that this document is exposing are the client's access-network information. These pertain to the access network to which the client is attached, such as Access-Technology Type (e.g., WLAN, Ethernet, etc.), Access-Point Identity (Name, BSSID), and Operator-Identifier and Operator-Realm. In deployments where this information cannot be secured using IPsec [RFC4301] or other security protocols, administrators SHOULD disable the capability specified in this document on the DHCP entities.
此文档公开的信息元素是客户端的访问网络信息。这些与客户端所连接的接入网络有关，例如接入技术类型（例如，WLAN、以太网等）、接入点标识（名称、BSSID）以及运营商标识符和运营商领域。在无法使用IPsec[RFC4301]或其他安全协议保护此信息的部署中，管理员应在DHCP实体上禁用本文档中指定的功能。
[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>.
[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>.
[RFC3046] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046, DOI 10.17487/RFC3046, January 2001, <http://www.rfc-editor.org/info/rfc3046>.
[RFC3046]Patrick，M.，“DHCP中继代理信息选项”，RFC 3046，DOI 10.17487/RFC3046，2001年1月<http://www.rfc-editor.org/info/rfc3046>.
[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>.
[ANI] "Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Radio Access Network Interfaces with Session Control in the Access Network", 3GPP2 A.S0008-C v4.0, April 2011.
[ANI]“接入网络中具有会话控制的高速分组数据（HRPD）无线接入网络接口的互操作性规范（IOS）”，3GPP2 A.S0008-C v4.0，2011年4月。
[RFC3118] Droms, R., Ed. and W. Arbaugh, Ed., "Authentication for DHCP Messages", RFC 3118, DOI 10.17487/RFC3118, June 2001, <http://www.rfc-editor.org/info/rfc3118>.
[RFC3118]Droms，R.，Ed.和W.Arbaugh，Ed.，“DHCP消息的身份验证”，RFC 3118，DOI 10.17487/RFC3118，2001年6月<http://www.rfc-editor.org/info/rfc3118>.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November 2003, <http://www.rfc-editor.org/info/rfc3629>.
[RFC3629]Yergeau，F.，“UTF-8，ISO 10646的转换格式”，STD 63，RFC 3629，DOI 10.17487/RFC3629，2003年11月<http://www.rfc-editor.org/info/rfc3629>.
[RFC4030] Stapp, M. and T. Lemon, "The Authentication Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option", RFC 4030, DOI 10.17487/RFC4030, March 2005, <http://www.rfc-editor.org/info/rfc4030>.
[RFC4030]Stapp，M.和T.Lemon，“动态主机配置协议（DHCP）中继代理选项的身份验证子选项”，RFC 4030，DOI 10.17487/RFC4030，2005年3月<http://www.rfc-editor.org/info/rfc4030>.
[RFC4301] Kent, S. and K. Seo, "Security Architecture for the Internet Protocol", RFC 4301, DOI 10.17487/RFC4301, December 2005, <http://www.rfc-editor.org/info/rfc4301>.
[RFC4301]Kent，S.和K.Seo，“互联网协议的安全架构”，RFC 4301，DOI 10.17487/RFC4301，2005年12月<http://www.rfc-editor.org/info/rfc4301>.
[RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V., Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", RFC 5213, DOI 10.17487/RFC5213, August 2008, <http://www.rfc-editor.org/info/rfc5213>.
[RFC5213]Gundavelli，S.，Ed.，Leung，K.，Devarapalli，V.，Chowdhury，K.，和B.Patil，“代理移动IPv6”，RFC 5213，DOI 10.17487/RFC5213，2008年8月<http://www.rfc-editor.org/info/rfc5213>.
[RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy Mobile IPv6", RFC 5844, DOI 10.17487/RFC5844, May 2010, <http://www.rfc-editor.org/info/rfc5844>.
[RFC5844]Wakikawa，R.和S.Gundavelli，“代理移动IPv6的IPv4支持”，RFC 5844，DOI 10.17487/RFC5844，2010年5月<http://www.rfc-editor.org/info/rfc5844>.
[RFC6757] Gundavelli, S., Ed., Korhonen, J., Ed., Grayson, M., Leung, K., and R. Pazhyannur, "Access Network Identifier (ANI) Option for Proxy Mobile IPv6", RFC 6757, DOI 10.17487/RFC6757, October 2012, <http://www.rfc-editor.org/info/rfc6757>.
[RFC6757]Gundavelli，S.，Ed.，Korhonen，J.，Ed.，Grayson，M.，Leung，K.，和R.Pazhyannur，“代理移动IPv6的接入网络标识符（ANI）选项”，RFC 6757，DOI 10.17487/RFC6757，2012年10月<http://www.rfc-editor.org/info/rfc6757>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6991, DOI 10.17487/RFC6991, July 2013, <http://www.rfc-editor.org/info/rfc6991>.
[RFC6991]Schoenwaeld，J.，Ed.，“常见杨数据类型”，RFC 6991，DOI 10.17487/RFC69911913年7月<http://www.rfc-editor.org/info/rfc6991>.
[SMI] IANA, "PRIVATE ENTERPRISE NUMBERS, SMI Network Management Private Enterprise Codes", March 2016, <https://www.iana.org/assignments/enterprise-numbers>.
[SMI]IANA，“私营企业编号、SMI网络管理私营企业代码”，2016年3月<https://www.iana.org/assignments/enterprise-numbers>.
[TS23003] 3GPP, "Numbering, addressing and identification", 3GPP TS 23.003 13.4.0, December 2015.
[TS23003]3GPP，“编号、寻址和标识”，3GPP TS 23.003 13.4.012015年12月。
[TS23203] 3GPP, "Policy and charging control architecture", 3GPP TS 23.203 13.6.0, December 2015.
[TS23203]3GPP，“政策和收费控制体系结构”，3GPP TS 23.203 13.6.0，2015年12月。
[TS23402] 3GPP, "Architecture enhancements for non-3GPP accesses", 3GPP TS 23.402 13.4.0, December 2015.
[TS23402]3GPP，“非3GPP接入的架构增强”，3GPP TS 23.402 13.4.0，2015年12月。
Acknowledgements
致谢
The authors would like to thank Kim Kinnear, Ted Lemon, Gaurav Halwasia, Hidetoshi Yokota, Sheng Jiang, and Francis Dupont for their valuable input. Also, thank you to Tomek Mrugalski for a thorough review of the document.
作者要感谢Kim Kinnear、Ted Lemon、Gaurav Halwasia、横田英寿、盛江和Francis Dupont的宝贵意见。同时，感谢托梅克·姆鲁加尔斯基对该文件的全面审查。
Authors' Addresses
作者地址
Shwetha Bhandari Cisco Systems Cessna Business Park, Sarjapura Marathalli Outer Ring Road Bangalore, KARNATAKA 560 087 India
印度卡纳塔克邦班加罗尔Sarjapura Maratalli外环路Shwetha Bhandari Cisco Systems Cessna商业园560087
Phone: +91 80 4426 0474
Email: shwethab@cisco.com
Phone: +91 80 4426 0474
Email: shwethab@cisco.com
Sri Gundavelli Cisco Systems 170 West Tasman Drive San Jose, CA 95134 United States
美国加利福尼亚州圣何塞市西塔斯曼大道170号，邮编95134
Email: sgundave@cisco.com
Email: sgundave@cisco.com
Mark Grayson Cisco Systems 11 New Square Park Bedfont Lakes, FELTHAM TW14 8HA England
马克·格雷森思科系统11新广场公园贝德方特湖，英格兰费尔瑟姆TW14 8HA
Email: mgrayson@cisco.com
Email: mgrayson@cisco.com
Bernie Volz Cisco Systems 1414 Massachusetts Ave Boxborough, MA 01719 United States
伯尼·沃兹思科系统公司美国马萨诸塞州伯斯堡马萨诸塞大道1414号，邮编01719
Email: volz@cisco.com
Email: volz@cisco.com
Jouni Korhonen Broadcom Limited 3151 Zanker Rd San Jose, CA 95134 United States
Jouni Korhonen Broadcom Limited美国加利福尼亚州圣何塞市赞克路3151号，邮编95134
Email: jouni.nospam@gmail.com
Email: jouni.nospam@gmail.com