Internet Engineering Task Force (IETF) S. Gundavelli, Ed.
Request for Comments: 6757 Cisco
Category: Standards Track J. Korhonen, Ed.
ISSN: 2070-1721 Nokia Siemens Networks
M. Grayson
K. Leung
R. Pazhyannur
Cisco
October 2012
Internet Engineering Task Force (IETF) S. Gundavelli, Ed.
Request for Comments: 6757 Cisco
Category: Standards Track J. Korhonen, Ed.
ISSN: 2070-1721 Nokia Siemens Networks
M. Grayson
K. Leung
R. Pazhyannur
Cisco
October 2012
Access Network Identifier (ANI) Option for Proxy Mobile IPv6
代理移动IPv6的访问网络标识符（ANI）选项
Abstract
摘要
The local mobility anchor in a Proxy Mobile IPv6 (PMIPv6) domain is able to provide access-network- and access-operator-specific handling or policing of the mobile node traffic using information about the access network to which the mobile node is attached. This specification defines a mechanism and a related mobility option for carrying the access network identifier and the access operator identification information from the mobile access gateway to the local mobility anchor over Proxy Mobile IPv6.
代理移动IPv6（PMIPv6）域中的本地移动性锚能够使用关于移动节点所连接的接入网络的信息来提供接入网络和接入运营商特定的移动节点流量处理或监管。本规范定义了用于通过代理移动IPv6将接入网络标识符和接入运营商标识信息从移动接入网关传送到本地移动锚的机制和相关移动选项。
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/rfc6757.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6757.
Copyright Notice
版权公告
Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2012 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
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您在以下方面的权利和限制：
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.
请参阅本文件。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................3
2. Conventions and Terminology .....................................5
2.1. Conventions ................................................5
2.2. Terminology ................................................5
3. Access Network Identifier Option ................................5
3.1. Format of the Access Network Identifier Sub-Option .........6
3.1.1. Network-Identifier Sub-Option .......................7
3.1.2. Geo-Location Sub-Option .............................8
3.1.3. Operator-Identifier Sub-Option ......................9
4. Protocol Considerations ........................................10
4.1. Mobile Access Gateway Considerations ......................10
4.2. Local Mobility Anchor Considerations ......................13
5. IANA Considerations ............................................14
6. Protocol Configuration Variables ...............................15
7. Security Considerations ........................................16
8. Acknowledgements ...............................................17
9. References .....................................................17
9.1. Normative References ......................................17
9.2. Informative References ....................................18
1. Introduction ....................................................3
2. Conventions and Terminology .....................................5
2.1. Conventions ................................................5
2.2. Terminology ................................................5
3. Access Network Identifier Option ................................5
3.1. Format of the Access Network Identifier Sub-Option .........6
3.1.1. Network-Identifier Sub-Option .......................7
3.1.2. Geo-Location Sub-Option .............................8
3.1.3. Operator-Identifier Sub-Option ......................9
4. Protocol Considerations ........................................10
4.1. Mobile Access Gateway Considerations ......................10
4.2. Local Mobility Anchor Considerations ......................13
5. IANA Considerations ............................................14
6. Protocol Configuration Variables ...............................15
7. Security Considerations ........................................16
8. Acknowledgements ...............................................17
9. References .....................................................17
9.1. Normative References ......................................17
9.2. Informative References ....................................18
Proxy Mobile IPv6 [RFC5213] can be used for supporting network-based mobility management in various types of network deployments. Network architectures such as service provider Wi-Fi access aggregation or Wireless Local Area Network (WLAN) integrated with mobile packet core are examples where Proxy Mobile IPv6 is a component of the overall architecture. Some of these architectures require the ability of the local mobility anchor (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 the Policy and Charging Control (PCC) Framework [TS23203] and the Access Network Discovery and Selection Function (ANDSF) [TS23402] in Third Generation Partnership Project (3GPP) systems 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 it is attached to an access network owned by the home operator than when owned by a roaming partner. The service treatment can also be different based on the configured Service Set Identifiers (SSIDs) in the case of access networks based on IEEE 802.11. Other examples of location services include the operator's ability to display a location-specific web page or apply tariff based on the location.
代理移动IPv6[RFC5213]可用于在各种类型的网络部署中支持基于网络的移动性管理。例如，服务提供商Wi-Fi接入聚合或与移动分组核心集成的无线局域网（WLAN）等网络架构是代理移动IPv6是整体架构的一个组件。其中一些架构要求本地移动锚（LMA）[RFC5213]能够基于移动节点所连接的接入网络向移动节点提供区分服务和流量监控。移动性架构中的策略系统，例如策略和计费控制（PCC）框架[TS23203]和第三代合作伙伴关系项目（3GPP）系统中的接入网络发现和选择功能（ANDSF）[TS23402]，允许基于接入网络信息配置具有条件的策略规则。例如，当移动节点的业务被连接到归属运营商拥有的接入网络时，其服务处理可能不同于当移动节点的业务被漫游伙伴拥有时的服务处理。在基于IEEE 802.11的接入网络的情况下，服务处理也可以基于配置的服务集标识符（ssid）而不同。位置服务的其他示例包括运营商能够显示特定于位置的网页或根据位置应用收费。
The Proxy Mobile IPv6 specification [RFC5213] requires the Access Technology Type (ATT) option to be carried from the mobile access gateway (MAG) to the local mobility anchor. This is a mandatory option. However, the Access Technology Type alone is not necessarily sufficient for a suitable policy to be applied at the local mobility anchor. Therefore, there is a need for additional access-network-related information to be available at the local mobility anchor. Learning the identity of the access network operator may not be possible for a local mobility anchor without the support of an additional policy framework that is able to provide required information out of band to the local mobility anchor. Such a policy framework may not be required for all Proxy Mobile IPv6 deployments; hence, an alternative approach for optionally carrying such information is required to ensure that additional information related to the access network is available.
代理移动IPv6规范[RFC5213]要求将接入技术类型（ATT）选项从移动接入网关（MAG）传输到本地移动锚。这是一个强制性的选择。然而，接入技术类型本身并不一定足以在本地移动性锚应用合适的策略。因此，需要在本地移动性锚点处提供额外的接入网络相关信息。如果没有能够向本地移动性锚提供带外所需信息的附加策略框架的支持，本地移动性锚可能不可能学习接入网络运营商的身份。并非所有代理移动IPv6部署都需要这样的策略框架；因此，需要可选地携带此类信息的替代方法，以确保与接入网络相关的附加信息可用。
This document defines a new mobility option, the Access Network Identifier (ANI) option, and its sub-options for Proxy Mobile IPv6, which can be used by the mobile access gateway to signal the access network information to the local mobility anchor. The specific details on how the local mobility anchor uses the information contained in the Access Network Identifier option are out of scope for this document. This information is intended for use between infrastructure nodes providing mobile management service and is not
本文档为代理移动IPv6定义了一个新的移动选项，即接入网络标识符（ANI）选项及其子选项，移动接入网关可使用该选项向本地移动锚发送接入网络信息信号。关于本地移动锚如何使用接入网络标识符选项中包含的信息的具体细节不在本文档的范围内。此信息旨在用于提供移动管理服务的基础架构节点之间，而不是
exposed to outside entities, which ensures the location of the network to which the mobile node is attached, or any other access-network-specific information, is not revealed to other mobile nodes within the PMIPv6 domain or to other nodes outside the PMIPv6 domain. However, the location and access information MAY be exposed to specific parties outside the PMIPv6 domain based on an agreement approved by the subscriber; otherwise, this information MUST NOT be exposed in the absence of such agreements. If the location information is to be exposed outside the PMIPv6 domain, then that MUST be done using a Presence Information Data Format Location Object (PIDF-LO) [RFC5139] carrying the usage rules to which the subscriber has agreed. This mobility option is optional and is not mandatory for the Proxy Mobile IPv6 protocol. However, the Access Technology Type option continues to be a mandatory option and always needs to be carried in the Proxy Mobile IPv6 signaling messages.
向外部实体公开，确保移动节点连接到的网络的位置或任何其他接入网络特定信息不会透露给PMIPv6域内的其他移动节点或PMIPv6域外的其他节点。然而，根据订户批准的协议，位置和访问信息可能暴露给PMIPv6域之外的特定方；否则，在没有此类协议的情况下，不得披露此类信息。如果要在PMIPv6域之外公开位置信息，则必须使用携带订户同意的使用规则的存在信息数据格式位置对象（PIDF-LO）[RFC5139]来完成。此移动性选项是可选的，对于代理移动IPv6协议不是强制性的。然而，接入技术类型选项仍然是一个强制性选项，并且始终需要在代理移动IPv6信令消息中携带。
SSID: IETF-1
Geo-Location: 37o49'11"N 122o28'43"W
Operator-Identifier: provider1.example.com
+--+
|AP|-------. {Access-Specific Policies)
+--+ | _-----_ |
+-----+ _( )_ +-----+
| MAG |-=====( PMIPv6 )======-| LMA |-
+-----+ (_ Tunnel_) +-----+
+--+ | '-----'
|AP|-------'
+--+
SSID: IETF-2
Geo-Location: 59o19'40.21"N 18o 3'18.36"E
Operator-Identifier: provider2.example.com
SSID: IETF-1
Geo-Location: 37o49'11"N 122o28'43"W
Operator-Identifier: provider1.example.com
+--+
|AP|-------. {Access-Specific Policies)
+--+ | _-----_ |
+-----+ _( )_ +-----+
| MAG |-=====( PMIPv6 )======-| LMA |-
+-----+ (_ Tunnel_) +-----+
+--+ | '-----'
|AP|-------'
+--+
SSID: IETF-2
Geo-Location: 59o19'40.21"N 18o 3'18.36"E
Operator-Identifier: provider2.example.com
Figure 1: Access Networks Attached to MAG
图1：连接到MAG的接入网络
Figure 1 illustrates an example Proxy Mobile IPv6 deployment where the mobile access gateway delivers the information elements related to the access network to the local mobility anchor over Proxy Mobile IPv6 signaling messages. In this example, the additional information could comprise the SSID of the used IEEE 802.11 network, the geo-location of the network to which the mobile node is attached, and the identities of the operators running the IEEE 802.11 access network infrastructure.
图1说明了一个示例代理移动IPv6部署，其中移动接入网关通过代理移动IPv6信令消息将与接入网络相关的信息元素传递给本地移动锚。在该示例中，附加信息可以包括所使用的IEEE 802.11网络的SSID、移动节点连接到的网络的地理位置以及运行IEEE 802.11接入网络基础设施的运营商的身份。
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]中所述进行解释。
All the mobility-related terms used in this document are to be interpreted as defined in the Proxy Mobile IPv6 specifications [RFC5213] and [RFC5844]. Additionally, this document uses the following abbreviations:
本文件中使用的所有移动相关术语应按照代理移动IPv6规范[RFC5213]和[RFC5844]中的定义进行解释。此外，本文件使用以下缩写：
Service Set Identifier
服务集标识
Service Set Identifier (SSID) identifies the name of the IEEE 802.11 network. SSID differentiates one network from 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 network attached to a specific interface of the mobile access gateway.
运营商标识符是IANA维护的“私有企业编号”注册表[SMI]的管理信息结构（SMI）网络管理私有企业代码。它标识运行连接到移动接入网关特定接口的网络的运营商。
The Access Network Identifier option is a mobility header option used to exchange information related to the access network between a local mobility anchor and a mobile access gateway. The option can be included in both Proxy Binding Update (PBU) and Proxy Binding Acknowledgement (PBA) messages, and there MUST NOT be more than a single instance of this mobility option in a mobility message. The Access Network Identifier mobility option MUST contain one or more Access Network Identifier sub-options. The Access Network Identifier sub-option is described in Section 3.1.
接入网络标识符选项是用于在本地移动锚和移动接入网关之间交换与接入网络相关的信息的移动报头选项。该选项可以包含在代理绑定更新（PBU）和代理绑定确认（PBA）消息中，并且在移动消息中该移动选项的实例不得超过一个。接入网络标识符移动选项必须包含一个或多个接入网络标识符子选项。第3.1节描述了接入网络标识符子选项。
The alignment requirement for this option is 4n [RFC2460].
该选项的对齐要求为4n[RFC2460]。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
... ANI Sub-option(s) ... ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
... ANI Sub-option(s) ... ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Access Network Identifier Option
图2：访问网络标识符选项
Type: MUST be set to the value of 52, indicating that it is a Network-Identifier option.
类型：必须设置为值52，表示它是网络标识符选项。
Length: 8-bit unsigned integer indicating the length in octets of the option, excluding the Type and Length fields.
长度：8位无符号整数，表示选项的长度（以八位字节为单位），不包括类型和长度字段。
The Access Network Identifier sub-options are used for carrying information elements related to the access network to which the mobile node is attached. These sub-options can be included in the Access Network Identifier option defined in Section 3. The format of this sub-option is as follows:
接入网络标识符子选项用于承载与移动节点所连接的接入网络相关的信息元素。这些子选项可以包括在第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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ANI Type | ANI Length | Option Data ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ANI Type | ANI Length | Option Data ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Access Network Identifier Sub-Option
图3：接入网络标识符子选项
ANI Type: 8-bit unsigned integer indicating the type of the Access Network Identifier sub-option. This specification defines the following types:
ANI类型：8位无符号整数，指示接入网络标识符子选项的类型。本规范定义了以下类型：
0 - Reserved
0-保留
1 - Network-Identifier sub-option
1-网络标识符子选项
2 - Geo-Location sub-option
2-地理位置子选项
3 - Operator-Identifier sub-option
3-操作员标识符子选项
ANI Length: 8-bit unsigned integer indicating the number of octets needed to encode the Option Data, excluding the ANI Type and ANI Length fields of the sub-option.
ANI长度：8位无符号整数，表示编码选项数据所需的八位字节数，不包括子选项的ANI类型和ANI长度字段。
The Network-Identifier is a mobility sub-option carried in the Access Network Identifier option defined in Section 3. This sub-option carries 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 3GPP access) to which the mobile node is attached. There MUST be no more than a single instance of this specific sub-option in any Access Network Identifier option. The format of this option is defined below.
网络标识符是在第3节中定义的接入网络标识符选项中携带的移动性子选项。该子选项携带移动节点连接到的接入网络的名称（例如，在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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ANI Type=1 | ANI Length |E| Reserved | Net-Name Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Name (e.g., SSID or PLMNID) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AP-Name 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ANI Type=1 | ANI Length |E| Reserved | Net-Name Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Name (e.g., SSID or PLMNID) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AP-Name Len | Access-Point Name ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Network-Identifier Sub-Option
图4：网络标识符子选项
ANI Type: MUST be set to the value of (1), indicating that it is a Network-Identifier sub-option
ANI类型：必须设置为（1）的值，表示它是网络标识符子选项
ANI Length: Total length of this sub-option in octets, excluding the ANI Type and ANI Length fields. The value can be in the range of 5 to 32 octets.
ANI长度：此子选项的总长度（以八位字节为单位），不包括ANI类型和ANI长度字段。该值可以在5到32个八位字节的范围内。
E: 1-bit flag indicating whether the Network Name is encoded in UTF-8. If this flag is set to one (1), then the Network Name is encoded using UTF-8 [RFC3629]. If the flag is set to zero (0), this indicates that the encoding is undefined and is determined by out-of-band mechanisms. Implementations SHOULD use UTF-8 encoding.
E：1位标志，指示网络名称是否以UTF-8编码。如果该标志设置为一（1），则使用UTF-8[RFC3629]对网络名称进行编码。如果标志设置为零（0），则表示编码未定义，由带外机制确定。实现应该使用UTF-8编码。
Reserved: MUST be set to zero when sending and ignored when received.
保留：发送时必须设置为零，接收时忽略。
Net-Name Length: 8-bit field for representing the length of the Network Name in octets. This field MUST NOT be set to zero.
网络名称长度：8位字段，用于表示网络名称的长度（以八位字节为单位）。此字段不能设置为零。
Network Name: The name of the access network to which the mobile node is attached. The type of the Network Name is dependent on the access technology to which the mobile node is attached. If it is 802.11 access, the Network Name MUST be the SSID of the network. If the access network is 3GPP access, the Network Name is the PLMN Identifier of the network. If the access network is 3GPP2 access, the Network Name is the Access Network Identifier [ANI].
网络名称：移动节点所连接的接入网络的名称。网络名称的类型取决于移动节点所连接的接入技术。如果是802.11访问，则网络名称必须是网络的SSID。如果接入网络是3GPP接入，则网络名称是网络的PLMN标识符。如果接入网络是3GPP2接入，则网络名称是接入网络标识符[ANI]。
When encoding the PLMN Identifier, both the Mobile Network Code (MNC) [TS23003] and Mobile Country Code (MCC) [TS23003] MUST be 3 digits. If the MNC in use only has 2 digits, then it MUST be preceded with a '0'. Encoding MUST be UTF-8.
编码PLMN标识符时，移动网络代码（MNC）[TS23003]和移动国家代码（MCC）[TS23003]必须为3位数字。如果使用中的MNC只有2位数字，则必须在其前面加上“0”。编码必须是UTF-8。
AP-Name Len: 8-bit field for representing the length of the Access-Point Name in octets. If the Access-Point Name is not included, then this length MUST be set to a value of zero.
AP Name Len：8位字段，以八位字节表示接入点名称的长度。如果未包括接入点名称，则此长度必须设置为零。
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 Network Name (e.g., SSID) identifies the operator's access network, 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 Media Access Control (MAC) address of the device or some unique identifier that can be used by the policy systems in the operator network to unambiguously identify the device. The string is carried in UTF-8 representation.
接入点名称：移动节点连接到的接入点的名称（物理设备名称）。这是唯一标识访问点的标识符。当网络名称（例如，SSID）标识运营商的接入网络时，接入点名称标识移动节点连接到的网络中的特定网络设备。在某些部署中，可以将接入点名称设置为设备的媒体访问控制（MAC）地址，或可由运营商网络中的策略系统用于明确标识设备的某种唯一标识符。字符串以UTF-8表示形式携带。
The Geo-Location is a mobility sub-option carried in the Access Network Identifier option defined in Section 3. This sub-option carries the geo-location of the network to which the mobile node is attached, as known to the mobile access gateway. There MUST be no more than a single instance of this specific sub-option in any Access Network Identifier option. The format of this option is defined below and encodes the coordinates of an ellipsoid point. The format is based on the coordinate reference system specified in the World Geodetic System 1984 [WGS84].
地理位置是第3节中定义的接入网络标识符选项中携带的移动性子选项。此子选项携带移动节点连接到的网络的地理位置，如移动接入网关所知。在任何访问网络标识符选项中，此特定子选项的实例不得超过一个。此选项的格式定义如下，并对椭球点的坐标进行编码。该格式基于1984年世界大地测量系统[WGS84]中规定的坐标参考系。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ANI Type=2 | ANI Length=6 | Latitude Degrees
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Longitude Degrees |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ANI Type=2 | ANI Length=6 | Latitude Degrees
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Longitude Degrees |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Geo-Location ANI Sub-Option
图5：地理位置ANI子选项
ANI Type: MUST be set to the value of (2), indicating that it is the Geo-Location sub-option
ANI类型：必须设置为（2）的值，表示它是地理位置子选项
ANI Length: Total length of this sub-option in octets, excluding the ANI Type and ANI Length fields. It MUST be set to a value of (6).
ANI长度：此子选项的总长度（以八位字节为单位），不包括ANI类型和ANI长度字段。必须将其设置为（6）的值。
Latitude Degrees: A 24-bit latitude degree value encoded as a two's complement, fixed point number with 9 whole bits. Positive degrees correspond to the Northern Hemisphere and negative degrees correspond to the Southern Hemisphere. The value ranges from -90 to +90 degrees.
纬度：一个24位的纬度值，编码为2的补码，带有9个整位的固定点数。正度数对应于北半球，负度数对应于南半球。该值的范围为-90到+90度。
Longitude Degrees: A 24-bit longitude degree value encoded as a two's complement, fixed point number with 9 whole bits. The value ranges from -180 to +180 degrees.
经度：一个24位的经度值，编码为2的补码，带有9个整位的固定点数。该值的范围为-180到+180度。
The Operator-Identifier is a mobility sub-option carried in the Access Network Identifier option defined in Section 3. This sub-option carries the Operator-Identifier of the access network to which the mobile node is attached. There MUST be no more than a single instance of this specific sub-option in any Access Network Identifier option. The format of this option is defined below.
运营商标识符是在第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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ANI Type=3 | ANI Length | Op-ID Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ANI Type=3 | ANI Length | Op-ID Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Operator-Identifier ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: Operator-Identifier Sub-Option
图6：操作员标识符子选项
ANI Type: It MUST be set to the value of (3), indicating that it is the Operator-Identifier sub-option
ANI类型：必须设置为（3）的值，表示它是操作员标识符子选项
ANI Length: Total length of this sub-option in octets, excluding the ANI Type and ANI Length fields.
ANI长度：此子选项的总长度（以八位字节为单位），不包括ANI类型和ANI长度字段。
Operator-Identifier (Op-ID) Type: 8-bit unsigned integer indicating the type of the Operator-Identifier. Currently, the following types are defined:
运算符标识符（Op ID）类型：表示运算符标识符类型的8位无符号整数。目前，定义了以下类型：
0 - Reserved.
0-保留。
1 - Operator-Identifier as a variable-length Private Enterprise Number (PEN) [SMI] encoded in a network-byte order. The maximum PEN value depends on the ANI Length and is calculated using the formula: maximum PEN = 2^((ANI_length-1)*8)-1. For example, the ANI Length of 4 allows for encoding PENs from 0 to 2^24-1, i.e., from 0 to 16777215, and uses 3 octets of Operator-Identifier space.
1-以网络字节顺序编码的可变长度私有企业编号（PEN）[SMI]的操作员标识符。最大笔值取决于ANI长度，并使用以下公式计算：最大笔=2^（（ANI_长度-1）*8）-1。例如，ANI长度4允许将笔从0编码到2^24-1，即从0编码到16777215，并使用3个八位字节的操作员标识符空间。
2 - Realm of the operator. Realm names are required to be unique and are piggybacked on the administration of the DNS namespace. Realms meet the syntactic requirements of the "Preferred Name Syntax" defined in Section 2.3.1 of [RFC1035]. They are encoded as US-ASCII. 3GPP specifications also define realm names that can be used to convey PLMN Identifiers [TS23003].
2-运算符的域。领域名称必须是唯一的，并且由DNS名称空间的管理提供。领域符合[RFC1035]第2.3.1节中定义的“首选名称语法”的语法要求。它们被编码为US-ASCII。3GPP规范还定义了可用于传送PLMN标识符的领域名称[TS23003]。
Operator-Identifier: Up to 253 octets of the Operator-Identifier. The encoding of the identifier depends on the used Operator-Identifier Type. For Operator-Identifiers defined in this specification, the Operator-Identifier MUST NOT be empty.
操作员标识符：操作员标识符最多253个八位字节。标识符的编码取决于使用的操作员标识符类型。对于本规范中定义的操作员标识符，操作员标识符不得为空。
The following considerations apply to the local mobility anchor and the mobile access gateway.
以下注意事项适用于本地移动锚和移动接入网关。
o The conceptual Binding Update List entry data structure maintained by the mobile access gateway, described in Section 6.1 of [RFC5213], MUST be extended to store the access-network-related information elements associated with the current session. Specifically, the following parameters MUST be defined:
o [RFC5213]第6.1节所述的移动接入网关维护的概念绑定更新列表条目数据结构必须扩展，以存储与当前会话相关的接入网络相关信息元素。具体而言，必须定义以下参数：
Network-Identifier
网络标识符
Operator-Identifier
操作员标识符
Geo-Location
地理位置
o If the mobile access gateway is configured to support the Access Network Information option, it SHOULD include this option with the specific sub-options in all Proxy Binding Update messages (including Proxy Binding Updates for lifetime extension and for deregistration) that it sends to the local mobility anchor. The Access Network Information option MUST be constructed as specified in Section 3. It SHOULD include the ANI sub-option(s) that the mobile access gateway is configured to carry in the Proxy Mobile IPv6 messages.
o 如果移动接入网关配置为支持接入网络信息选项，则它应在发送给本地移动锚的所有代理绑定更新消息（包括用于延长生存期和取消注册的代理绑定更新）中包括此选项和特定子选项。接入网络信息选项必须按照第3节的规定构造。它应包括移动接入网关配置为在代理移动IPv6消息中承载的ANI子选项。
o The access network information elements, such as Network-Identifier, Geo-Location, and Operator-Identifier, typically are statically configured on the mobile access gateway on a per-interface basis (for example, access point (AP-1) is attached through interface-1, and the SSID is X, Geo-Location is Y). In some deployments, this information can also be dynamically obtained, such as through DHCP Option (82), which is the DHCP Relay Agent Information option [RFC3046]. When the mobile node sends a DHCP Request, the access points typically add the SSID information to the Option 82 of the DHCP request, and when the mobile access gateway receives this request, it can parse the Option 82 of the DHCP request and obtain the SSID name. The mobility access gateway can also obtain this information from the DHCPv6 GeoLoc Option [RFC6225]. The specific details on how the mobile access gateway obtains these information elements are access technology and deployment specific and are outside the scope of this document. It is possible those information elements are configured on the MAG on a per-interface basis or dynamically obtained through some out-of-band means, such as based on the Control and Provisioning of Wireless Access Points (CAPWAP) protocol.
o 接入网络信息元素，例如网络标识符、地理位置和操作员标识符，通常基于每个接口在移动接入网关上静态地配置（例如，接入点（AP-1）通过接口1连接，并且SSID是X，地理位置是Y）。在某些部署中，还可以动态获取此信息，例如通过DHCP选项（82），它是DHCP中继代理信息选项[RFC3046]。当移动节点发送DHCP请求时，接入点通常将SSID信息添加到DHCP请求的选项82，并且当移动接入网关接收到该请求时，它可以解析DHCP请求的选项82并获得SSID名称。移动接入网关还可以从DHCPv6 GeoLoc选项[RFC6225]获取该信息。有关移动接入网关如何获取这些信息元素的具体细节是特定于接入技术和部署的，不在本文档的范围内。这些信息元素可能基于每个接口在MAG上配置，或者通过一些带外方式（例如基于无线接入点（CAPWAP）协议的控制和供应）动态获取。
o If the protocol configuration variable EnableANISubOptNetworkIdentifier (Section 6) is set to a value of (1), the mobile access gateway SHOULD include the Network-Identifier sub-option in the Access Network Identifier option carried in the Proxy Binding Update. However, if the mobile access gateway is unable to obtain the Network-Identifier, then it MUST NOT include this sub-option. For including the Network-Identifier sub-option, the mobile access gateway needs to be aware of the Network Name of the access network (e.g., SSID in the case of a WLAN access network) to which the mobile node is attached.
o 如果协议配置变量EnableANISubOptNetworkIdentifier（第6节）设置为值（1），则移动接入网关应在代理绑定更新中携带的接入网络标识符选项中包括网络标识符子选项。但是，如果移动接入网关无法获取网络标识符，则它不得包含此子选项。为了包括网络标识符子选项，移动接入网关需要知道移动节点连接到的接入网络的网络名称（例如，在WLAN接入网络的情况下为SSID）。
This sub-option also includes the Access-Point Name for carrying the name of the access point to which the mobile node is attached. The Access-Point Name is specially important for applying location services, given that the Network Name (e.g., SSID) may not provide the needed uniqueness for identifying a location. When included, this sub-option MUST be constructed as described in Section 3.1.1
该子选项还包括用于承载移动节点所连接的接入点的名称的接入点名称。接入点名称对于应用位置服务特别重要，因为网络名称（例如SSID）可能无法提供识别位置所需的唯一性。包含时，该子选项必须按照第3.1.1节所述进行构造
o If the protocol configuration variable EnableANISubOptGeoLocation (Section 6) is set to a value of (1), the mobile access gateway SHOULD include the Geo-Location sub-option in the Access Network Identifier option carried in the Proxy Binding Update. However, if the mobile access gateway is unable to obtain the Geo-location, then it MUST NOT include this sub-option. For including the Geo-Location sub-option, the mobile access gateway needs to be aware of the GPS coordinates of the network to which the mobile node is attached. When included, this sub-option MUST be constructed as described in Section 3.1.2.
o 如果协议配置变量EnableANISubOptGeoLocation（第6节）设置为值（1），则移动接入网关应在代理绑定更新中携带的接入网络标识符选项中包括地理位置子选项。但是，如果移动接入网关无法获取地理位置，则它不得包含此子选项。为了包括地理位置子选项，移动接入网关需要知道移动节点所连接的网络的GPS坐标。包含时，该子选项必须按照第3.1.2节所述进行构造。
o If the protocol configuration variable EnableANISubOptOperatorIdentifier (Section 6) is set to a value of (1), the mobile access gateway SHOULD include the Operator-Identifier sub-option in the Access Network Identifier option carried in the Proxy Binding Update. For including the Operator-Identifier sub-option, the mobile access gateway needs to be aware of the operator identity of that access network. The access network operator SHOULD obtain an identifier from the "Private Enterprise Number" registry, in order for the mobile access gateway to carry the Operator-Identifier. If a given access network operator has not obtained an identifier from the "Private Enterprise Number" registry or if the mobile access gateway is unable to learn the operator identity for any other administrative reasons, then it MUST NOT include this sub-option. When included, this sub-option MUST be constructed as described in Section 3.1.3.
o 如果协议配置变量EnableANISubOptOperatorIdentifier（第6节）设置为值（1），则移动接入网关应在代理绑定更新中携带的接入网络标识符选项中包括运营商标识符子选项。为了包括运营商标识符子选项，移动接入网关需要知道该接入网络的运营商标识。接入网运营商应从“私有企业号”注册处获取标识符，以便移动接入网关携带运营商标识符。如果给定的接入网络运营商尚未从“私有企业号”注册表中获得标识符，或者如果移动接入网关由于任何其他管理原因无法了解运营商标识，则不得包括此子选项。包含时，该子选项必须按照第3.1.3节所述进行构造。
If the mobile access gateway had any of the Access Network Information mobility options included the Proxy Binding Update sent to a local mobility anchor, then the Proxy Binding Acknowledgement received from the local mobility anchor SHOULD contain the Access Network Information mobility option with the specific sub-options. If the mobile access gateway receives a Proxy Binding Acknowledgement with a successful Status Value but without an Access Network Information mobility option, then the mobile access gateway SHOULD log the event and, based on its local policy, MAY proceed to terminate the mobility session. In this case, the mobile access gateway knows the local mobility anchor does not understand the Access Network Information mobility option and therefore MAY consider it as a misconfiguration of the Proxy Mobile IPv6 domain.
如果移动接入网关具有包括发送到本地移动锚的代理绑定更新的接入网络信息移动选项中的任何一个，则从本地移动锚接收的代理绑定确认应包含具有特定子选项的接入网络信息移动选项。如果移动接入网关接收到具有成功状态值但没有接入网络信息移动选项的代理绑定确认，则移动接入网关应当记录该事件，并且基于其本地策略，可以继续终止移动会话。在这种情况下，移动接入网关知道本地移动性锚不理解接入网络信息移动性选项，因此可以将其视为代理移动IPv6域的错误配置。
o The conceptual Binding Cache entry data structure maintained by the local mobility anchor, described in Section 5.1 of [RFC5213], MUST be extended to store the access-network-related information elements associated with the current session. Specifically, the following parameters MUST be defined:
o [RFC5213]第5.1节中描述的由本地移动锚维护的概念绑定缓存条目数据结构必须扩展，以存储与当前会话相关的接入网络相关信息元素。具体而言，必须定义以下参数：
Network-Identifier
网络标识符
Geo-Location
地理位置
Operator-Identifier
操作员标识符
o On receiving a Proxy Binding Update message [RFC5213] from a mobile access gateway with the Access Network Information option, the local mobility anchor must process the option and update the corresponding fields in the Binding Cache entry. If the option is not understood by that LMA implementation, it will skip the option.
o 当从具有接入网络信息选项的移动接入网关接收到代理绑定更新消息[RFC5213]时，本地移动锚必须处理该选项并更新绑定缓存条目中的相应字段。如果LMA实现不理解该选项，它将跳过该选项。
o If the local mobility anchor understands the Access Network Identifier mobility option received in a Proxy Binding Update and also supports the sub-option(s), then the local mobility anchor MUST echo the Access Network Identifier mobility option with the specific sub-option(s) that it accepted back to the mobile access gateway in a Proxy Binding Acknowledgement. The Access Network Identifier sub-options defined in this specification MUST NOT be altered by the local mobility anchor.
o 如果本地移动性锚点理解在代理绑定更新中接收的接入网络标识符移动性选项，并且还支持子选项，则本地移动性锚点必须使用特定子选项回显接入网络标识符移动性选项它在代理绑定确认中接受回移动接入网关。本地移动锚不得更改本规范中定义的接入网络标识符子选项。
o If the received Proxy Binding Update message does not include the Access Network Information option, then the mobility session associated with that Proxy Binding Update MUST be updated to remove any access network information elements.
o 如果收到的代理绑定更新消息不包括接入网络信息选项，则必须更新与该代理绑定更新相关联的移动会话，以删除任何接入网络信息元素。
o The local mobility anchor MAY choose to use the Access Network Information sub-options for applying any access-operator-specific handling or policing of the mobile node traffic. The specific details on how these sub-options are used is outside the scope of this document.
o 本地移动性锚可以选择使用接入网络信息子选项来应用任何接入运营商特定的对移动节点业务的处理或监管。关于如何使用这些子选项的具体细节不在本文档范围内。
Per this document, the following IANA actions have been completed.
根据本文件，已完成以下IANA行动。
o Action 1: This specification defines a new mobility header option, the Access Network Identifier. This mobility option is described in Section 3. The type value (52) for this option has been assigned from the same numbering space as allocated for the other mobility options, as defined in [RFC6275].
o 措施1：本规范定义了一个新的移动报头选项，即接入网络标识符。第3节介绍了该移动性选项。根据[RFC6275]中的定义，此选项的类型值（52）已从分配给其他移动选项的相同编号空间分配。
o Action 2: This specification defines a new mobility sub-option format, the Access Network Information (ANI) sub-option. The format of this mobility sub-option is described in Section 3.1. This sub-option can be carried in the Access Network Information option. The type value for this sub-option is managed by IANA, under the registry "Access Network Information (ANI) Sub-Option Type Values". This specification reserves the following type values. Approval of new Access Network Information (ANI) sub-option type values are to be made through IANA Expert Review.
o 行动2：本规范定义了一种新的移动性子选项格式，即接入网络信息（ANI）子选项。第3.1节描述了该移动性子选项的格式。此子选项可在接入网络信息选项中携带。此子选项的类型值由IANA在注册表“访问网络信息（ANI）子选项类型值”下管理。本规范保留以下类型值。新接入网信息（ANI）子选项类型值的批准将通过IANA专家评审进行。
+=========================================================+
| 0 | Reserved |
+=========================================================+
| 1 | Network-Identifier sub-option |
+=========================================================+
| 2 | Geo-Location sub-option |
+=========================================================+
| 3 | Operator-Identifier sub-option |
+=========================================================+
+=========================================================+
| 0 | Reserved |
+=========================================================+
| 1 | Network-Identifier sub-option |
+=========================================================+
| 2 | Geo-Location sub-option |
+=========================================================+
| 3 | Operator-Identifier sub-option |
+=========================================================+
o Action 3: This specification defines a new mobility sub-option, the Operator-Identifier sub-option. The format of this mobility sub-option is described in Section 3.1.3. The Operator-Identifier (Op-ID) Type field of this sub-option introduces a new number space. This number space is managed by IANA, under the registry "Operator-Identifier Type Registry". This specification reserves the following type values. Approval of new Operator-Identifier type values are to be made through IANA Expert Review.
o 行动3：本规范定义了一个新的移动性子选项，即操作员标识符子选项。第3.1.3节描述了该移动性子选项的格式。此子选项的操作员标识符（Op ID）类型字段引入了一个新的数字空间。此数字空间由IANA在注册表“操作员标识符类型注册表”下管理。本规范保留以下类型值。新操作员标识符类型值的批准将通过IANA专家评审进行。
+===============================================+
| 0 | Reserved |
+===+===========================================+
| 1 | Operator-Identifier as a variable-length |
| | Private Enterprise Number (PEN) |
+===+===========================================+
| 2 | Realm of the Operator |
+===+===========================================+
+===============================================+
| 0 | Reserved |
+===+===========================================+
| 1 | Operator-Identifier as a variable-length |
| | Private Enterprise Number (PEN) |
+===+===========================================+
| 2 | Realm of the Operator |
+===+===========================================+
This specification defines the following configuration variables that control the use of sub-options related to the Access Network Information in Proxy Mobile IPv6 signaling messages. The mobility entities, local mobility anchor, and mobile access gateway MUST allow these variables to be configured by the system management. The configured values for these protocol variables MUST survive server reboots and service restarts.
本规范定义了以下配置变量，用于控制代理移动IPv6信令消息中与接入网络信息相关的子选项的使用。移动实体、本地移动锚和移动接入网关必须允许系统管理层配置这些变量。这些协议变量的配置值必须在服务器重新启动和服务重新启动后仍然有效。
EnableANISubOptNetworkIdentifier
EnableANISubOptNetworkIdentifier
This flag indicates the operational state of the Network-Identifier sub-option support. This configuration variable is available at both the mobile access gateway and the local mobility anchor. The default value for this flag is set to (0), indicating that support for the Network-Identifier sub-option is disabled.
此标志指示网络标识符子选项支持的操作状态。此配置变量在移动接入网关和本地移动锚都可用。此标志的默认值设置为（0），表示已禁用对网络标识符子选项的支持。
When this flag on the mobile access gateway is set to a value of (1), the mobile access gateway SHOULD include this sub-option in the Proxy Binding Update messages that it sends to the local mobility anchor; otherwise, it SHOULD NOT include the sub-option. There can be situations where the mobile access gateway is unable to obtain the Network-Identifier and may not be able to construct this sub-option.
当移动接入网关上的该标志被设置为值（1）时，移动接入网关应在其发送给本地移动锚的代理绑定更新消息中包括该子选项；否则，它不应包括子选项。在某些情况下，移动接入网关无法获取网络标识符，并且可能无法构造此子选项。
Similarly, when this flag on the local mobility anchor is set to a value of (1), the local mobility anchor SHOULD enable support for this sub-option; otherwise, it SHOULD ignore this sub-option.
类似地，当本地移动性锚点上的该标志设置为值（1）时，本地移动性锚点应启用对该子选项的支持；否则，它应该忽略此子选项。
EnableANISubOptGeoLocation
使能性suboptgeolocation
This flag indicates the operational state of the Geo-Location sub-option support. This configuration variable is available at both the mobile access gateway and the local mobility anchor. The default value for this flag is set to (0), indicating that support for the Geo-Location sub-option is disabled.
此标志表示地理位置子选项支持的操作状态。此配置变量在移动接入网关和本地移动锚都可用。此标志的默认值设置为（0），表示已禁用对“地理位置”子选项的支持。
When this flag on the mobile access gateway is set to a value of (1), the mobile access gateway SHOULD include this sub-option in the Proxy Binding Update messages that it sends to the local mobility anchor; otherwise, it SHOULD NOT include the sub-option. There can be situations where the mobile access gateway is unable to obtain the geo-location information and may not be able to construct this sub-option.
当移动接入网关上的该标志被设置为值（1）时，移动接入网关应在其发送给本地移动锚的代理绑定更新消息中包括该子选项；否则，它不应包括子选项。在某些情况下，移动接入网关无法获取地理位置信息，并且可能无法构建此子选项。
Similarly, when this flag on the local mobility anchor is set to a value of (1), the local mobility anchor SHOULD enable support for this sub-option; otherwise, it SHOULD ignore this sub-option.
类似地，当本地移动性锚点上的该标志设置为值（1）时，本地移动性锚点应启用对该子选项的支持；否则，它应该忽略此子选项。
EnableANISubOptOperatorIdentifier
EnableANISubOptOperatorIdentifier
This flag indicates the operational state of the Operator-Identifier sub-option support. This configuration variable is available at both the mobile access gateway and the local mobility anchor. The default value for this flag is set to (0), indicating that support for the Operator-Identifier sub-option is disabled.
此标志表示操作员标识符子选项支持的操作状态。此配置变量在移动接入网关和本地移动锚都可用。此标志的默认值设置为（0），表示已禁用对操作员标识符子选项的支持。
When this flag on the mobile access gateway is set to a value of (1), the mobile access gateway SHOULD include this sub-option in the Proxy Binding Update messages that it sends to the local mobility anchor; otherwise, it SHOULD NOT include the sub-option. There can be situations where the mobile access gateway is unable to obtain the Operator-Identifier information and may not be able to construct this sub-option.
当移动接入网关上的该标志被设置为值（1）时，移动接入网关应在其发送给本地移动锚的代理绑定更新消息中包括该子选项；否则，它不应包括子选项。在某些情况下，移动接入网关无法获取运营商标识符信息，并且可能无法构造此子选项。
Similarly, when this flag on the local mobility anchor is set to a value of (1), the local mobility anchor SHOULD enable support for this sub-option; otherwise, it SHOULD ignore this sub-option.
类似地，当本地移动性锚点上的该标志设置为值（1）时，本地移动性锚点应启用对该子选项的支持；否则，它应该忽略此子选项。
The Access Network Information option defined in this specification is for use in Proxy Binding Update and Proxy Binding Acknowledgement messages. This option is carried like any other mobility header option as specified in [RFC6275] and does not require any special security considerations.
本规范中定义的访问网络信息选项用于代理绑定更新和代理绑定确认消息。该选项与[RFC6275]中规定的任何其他移动报头选项一样，不需要任何特殊的安全考虑。
The Geo-Location sub-option carried in the Access Network Information option exposes the geo-location of the network to which the mobile node is attached. This information is considered to be very sensitive, so care must be taken to secure the Proxy Mobile IPv6 signaling messages when carrying this sub-option. The base Proxy Mobile IPv6 specification [RFC5213] specifies the use of IPsec for securing the signaling messages, and those mechanisms can be enabled for protecting this information. Operators can potentially apply IPsec Encapsulating Security Payload (ESP) with confidentiality and integrity protection for protecting the location information.
接入网络信息选项中携带的地理位置子选项公开移动节点连接到的网络的地理位置。此信息被认为是非常敏感的，因此在携带此子选项时，必须注意保护代理移动IPv6信令消息的安全。基本代理移动IPv6规范[RFC5213]指定使用IPsec来保护信令消息，并且可以启用这些机制来保护此信息。运营商可以潜在地应用具有机密性和完整性保护的IPsec封装安全负载（ESP）来保护位置信息。
Access-network-specific information elements that the mobile access gateway sends may have been dynamically learned over DHCP or using other protocols. If proper security mechanisms are not in place, the exchanged information may be potentially compromised with the mobile access gateway sending incorrect access network parameters to the
移动接入网关发送的接入网络特定信息元素可能已经通过DHCP或使用其他协议动态地学习。如果没有适当的安全机制，交换的信息可能会受到移动接入网关向用户发送不正确的接入网络参数的潜在危害
local mobility anchor. This situation may potentially result in incorrect service policy enforcement at the local mobility anchor and impact to other services that depend on this access network information. This threat can be mitigated by ensuring the communication path between the mobile access gateway and the access points is properly secured by the use of IPsec, Transport Layer Security (TLS), or other security protocols.
本地移动锚。这种情况可能导致在本地移动性锚点执行错误的服务策略，并影响依赖于该接入网络信息的其他服务。通过使用IPsec、传输层安全（TLS）或其他安全协议，确保移动接入网关和接入点之间的通信路径得到适当保护，可以减轻这种威胁。
The authors would like to thank Basavaraj Patil, Carlos Bernardos, Gerardo Gieratta, Eric Voit, Hidetoshi Yokota, Ryuji Wakikawa, Sangram Kishore, William Wan, Stefano Faccin, and Brian Haberman for all the discussions related to this topic. The authors would also like to acknowledge the IESG reviews from Benoit Claise, Stephen Farrell, Pete Resnick, Robert Spark, Martin Thomson, and Ralph Droms.
作者要感谢Basavaraj Patil、Carlos Bernardos、Gerardo Gieratta、Eric Voit、Hidetoshi Yokota、Ryuji Wakikawa、Sangram Kishore、William Wan、Stefano Faccin和Brian Haberman与本主题相关的所有讨论。作者还想感谢来自Benoit Claise、Stephen Farrell、Pete Resnick、Robert Spark、Martin Thomson和Ralph Droms的IESG评论。
[RFC1035] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987.
[RFC1035]Mockapetris，P.，“域名-实现和规范”，STD 13，RFC 1035，1987年11月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003.
[RFC3629]Yergeau，F.，“UTF-8，ISO 10646的转换格式”，STD 63，RFC 3629，2003年11月。
[RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)", RFC 5139, February 2008.
[RFC5139]Thomson，M.和J.Winterbottom，“状态信息数据格式位置对象（PIDF-LO）的修订公民位置格式”，RFC 5139，2008年2月。
[RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008.
[RFC5213]Gundavelli，S.，Leung，K.，Devarapalli，V.，Chowdhury，K.，和B.Patil，“代理移动IPv6”，RFC 5213，2008年8月。
[RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy Mobile IPv6", RFC 5844, May 2010.
[RFC5844]Wakikawa，R.和S.Gundavelli，“代理移动IPv6的IPv4支持”，RFC 5844，2010年5月。
[RFC6275] Perkins, C., Johnson, D., and J. Arkko, "Mobility Support in IPv6", RFC 6275, July 2011.
[RFC6275]Perkins，C.，Johnson，D.，和J.Arkko，“IPv6中的移动支持”，RFC 62752011年7月。
[ANI] 3GPP2 TSG-A, "Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Radio Access Network Interfaces with Session Control in the Access Network", A.S0008-A v3.0, October 2008.
[ANI]3GPP2 TSG-A，“接入网络中具有会话控制的高速分组数据（HRPD）无线接入网络接口的互操作性规范（IOS）”，A.S0008-A v3.0，2008年10月。
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC 2460, December 1998.
[RFC2460]Deering，S.和R.Hinden，“互联网协议，第6版（IPv6）规范”，RFC 2460，1998年12月。
[RFC3046] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046, January 2001.
[RFC3046]Patrick，M.，“DHCP中继代理信息选项”，RFC3046，2001年1月。
[RFC6225] Polk, J., Linsner, M., Thomson, M., and B. Aboba, "Dynamic Host Configuration Protocol Options for Coordinate-Based Location Configuration Information", RFC 6225, July 2011.
[RFC6225]Polk，J.，Linsner，M.，Thomson，M.，和B.Aboba，“基于坐标的位置配置信息的动态主机配置协议选项”，RFC 62252011年7月。
[SMI] IANA, "PRIVATE ENTERPRISE NUMBERS", SMI Network Management Private Enterprise Codes, <http://www.iana.org/assignments/enterprise-numbers>.
[SMI]IANA，“私有企业编号”，SMI网络管理私有企业代码<http://www.iana.org/assignments/enterprise-numbers>.
[TS23003] 3GPP, "Numbering, addressing and identification", 3GPP TS 23.003 3.15.0, 2012.
[TS23003]3GPP，“编号、寻址和标识”，3GPP TS 23.003 3.15.012。
[TS23203] 3GPP, "Policy and Charging Control Architecture", 3GPP TS 23.203 10.7.0, 2012.
[TS23203]3GPP，“政策和收费控制体系结构”，3GPP TS 23.203 10.7.012。
[TS23402] 3GPP, "Architecture enhancements for non-3GPP accesses", 3GPP TS 23.402 10.7.0, 2012.
[TS23402]3GPP，“非3GPP接入的架构增强”，3GPP TS 23.402 10.7.01212。
[WGS84] NIMA, "World Geodetic System 1984", Third Edition, NIMA TR8350.2, June 2004.
[WGS84]NIMA，“1984年世界大地测量系统”，第三版，NIMA TR8350.2，2004年6月。
Authors' Addresses
作者地址
Sri Gundavelli (editor) Cisco 170 West Tasman Drive San Jose, CA 95134 USA
Sri Gundavelli（编辑）思科170西塔斯曼大道圣何塞，加利福尼亚州95134
EMail: sgundave@cisco.com
EMail: sgundave@cisco.com
Jouni Korhonen (editor) Nokia Siemens Networks Linnoitustie 6 Espoo FIN-02600 Finland
Jouni Korhonen（编辑）诺基亚西门子网络公司Linnoitustie 6 Espoo FIN-02600芬兰
EMail: jouni.nospam@gmail.com
EMail: jouni.nospam@gmail.com
Mark Grayson Cisco 11 New Square Park Bedfont Lakes, Feltham TW14 8HA England
马克·格雷森思科11新广场公园贝德方特湖，英格兰费尔瑟姆TW14 8HA
EMail: mgrayson@cisco.com
EMail: mgrayson@cisco.com
Kent Leung Cisco 170 West Tasman Drive San Jose, CA 95134 USA
美国加利福尼亚州圣何塞西塔斯曼大道170号，邮编95134
EMail: kleung@cisco.com
EMail: kleung@cisco.com
Rajesh Pazhyannur Cisco 170 West Tasman Drive San Jose, CA 95134 USA
美国加利福尼亚州圣何塞西塔斯曼大道170号，邮编95134
EMail: rpazhyan@cisco.com
EMail: rpazhyan@cisco.com