Internet Engineering Task Force (IETF) D. Farinacci
Request for Comments: 8060 lispers.net
Category: Experimental D. Meyer
ISSN: 2070-1721 Brocade
J. Snijders
NTT
February 2017
Internet Engineering Task Force (IETF) D. Farinacci
Request for Comments: 8060 lispers.net
Category: Experimental D. Meyer
ISSN: 2070-1721 Brocade
J. Snijders
NTT
February 2017
LISP Canonical Address Format (LCAF)
LISP规范地址格式（LCAF）
Abstract
摘要
This document defines a canonical address format encoding used in Locator/ID Separation Protocol (LISP) control messages and in the encoding of lookup keys for the LISP Mapping Database System.
本文档定义了一种规范的地址格式编码，用于定位器/ID分离协议（LISP）控制消息和LISP映射数据库系统的查找键编码。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation.
本文件不是互联网标准跟踪规范；它是为检查、实验实施和评估而发布的。
This document defines an Experimental Protocol for the Internet community. 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). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 7841.
本文档为互联网社区定义了一个实验协议。本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非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/rfc8060.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc8060.
Copyright Notice
版权公告
Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2017 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 ....................................................4
2. Terminology .....................................................5
2.1. Requirements Language ......................................5
2.2. Definition of Terms ........................................5
3. LISP Canonical Address Format Encodings .........................6
4. LISP Canonical Address Applications .............................8
4.1. Segmentation Using LISP ....................................8
4.2. Carrying AS Numbers in the Mapping Database ................9
4.3. Assigning Geo-Coordinates to Locator Addresses ............10
4.4. NAT Traversal Scenarios ...................................11
4.5. Multicast Group Membership Information ....................13
4.6. Traffic Engineering Using Re-encapsulating Tunnels ........15
4.7. Storing Security Data in the Mapping Database .............16
4.8. Source/Destination 2-Tuple Lookups ........................17
4.9. Replication List Entries for Multicast Forwarding .........18
4.10. Applications for AFI List LCAF Type ......................19
4.10.1. Binding IPv4 and IPv6 Addresses ...................19
4.10.2. Layer 2 VPNs ......................................20
4.10.3. ASCII Names in the Mapping Database ...............21
4.10.4. Using Recursive LISP Canonical Address Encodings ..22
4.10.5. Compatibility Mode Use Case .......................23
5. Experimental LISP Canonical Address Applications ...............24
5.1. Convey Application-Specific Data ..........................24
5.2. Generic Database Mapping Lookups ..........................25
5.3. PETR Admission Control Functionality ......................26
5.4. Data Model Encoding .......................................27
5.5. Encoding Key/Value Address Pairs ..........................28
5.6. Multiple Data-Planes ......................................29
6. Security Considerations ........................................31
7. IANA Considerations ............................................31
8. References .....................................................32
8.1. Normative References ......................................32
8.2. Informative References ....................................33
Acknowledgments ...................................................35
Authors' Addresses ................................................36
1. Introduction ....................................................4
2. Terminology .....................................................5
2.1. Requirements Language ......................................5
2.2. Definition of Terms ........................................5
3. LISP Canonical Address Format Encodings .........................6
4. LISP Canonical Address Applications .............................8
4.1. Segmentation Using LISP ....................................8
4.2. Carrying AS Numbers in the Mapping Database ................9
4.3. Assigning Geo-Coordinates to Locator Addresses ............10
4.4. NAT Traversal Scenarios ...................................11
4.5. Multicast Group Membership Information ....................13
4.6. Traffic Engineering Using Re-encapsulating Tunnels ........15
4.7. Storing Security Data in the Mapping Database .............16
4.8. Source/Destination 2-Tuple Lookups ........................17
4.9. Replication List Entries for Multicast Forwarding .........18
4.10. Applications for AFI List LCAF Type ......................19
4.10.1. Binding IPv4 and IPv6 Addresses ...................19
4.10.2. Layer 2 VPNs ......................................20
4.10.3. ASCII Names in the Mapping Database ...............21
4.10.4. Using Recursive LISP Canonical Address Encodings ..22
4.10.5. Compatibility Mode Use Case .......................23
5. Experimental LISP Canonical Address Applications ...............24
5.1. Convey Application-Specific Data ..........................24
5.2. Generic Database Mapping Lookups ..........................25
5.3. PETR Admission Control Functionality ......................26
5.4. Data Model Encoding .......................................27
5.5. Encoding Key/Value Address Pairs ..........................28
5.6. Multiple Data-Planes ......................................29
6. Security Considerations ........................................31
7. IANA Considerations ............................................31
8. References .....................................................32
8.1. Normative References ......................................32
8.2. Informative References ....................................33
Acknowledgments ...................................................35
Authors' Addresses ................................................36
The LISP architecture and protocol [RFC6830] introduces two new numbering spaces: Endpoint Identifiers (EIDs) and Routing Locators (RLOCs). To provide flexibility for current and future applications, these values can be encoded in LISP control messages using a general syntax that includes Address Family Identifier (AFI), length, and value fields.
LISP体系结构和协议[RFC6830]引入了两个新的编号空间：端点标识符（EID）和路由定位器（RLOC）。为了为当前和未来的应用程序提供灵活性，可以使用包含地址族标识符（AFI）、长度和值字段的通用语法在LISP控制消息中对这些值进行编码。
Currently defined AFIs include IPv4 and IPv6 addresses, which are formatted according to code-points assigned in the "Address Family Numbers" registry [AFN] as follows:
当前定义的AFI包括IPv4和IPv6地址，它们根据“地址系列号”注册表[AFN]中分配的代码点进行格式化，如下所示：
IPv4-Encoded Address:
IPv4编码地址：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 1 | IPv4 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 1 | IPv4 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IPv6-Encoded Address:
IPv6编码地址：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 2 | IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 2 | IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This document describes the currently defined AFIs that LISP uses along with their encodings and introduces the LISP Canonical Address Format (LCAF) that can be used to define the LISP-specific encodings for arbitrary AFI values.
本文档描述了LISP使用的当前定义的AFI及其编码，并介绍了可用于为任意AFI值定义LISP特定编码的LISP规范地址格式（LCAF）。
Specific detailed uses for the LCAF Types defined in this document can be found in the use-case documents that implement them. The same LCAF Type may be used by more than one use-case document. As an Experimental specification, this work is, by definition, incomplete.
本文档中定义的LCAF类型的具体详细用途可以在实现它们的用例文档中找到。同一LCAF类型可由多个用例文档使用。作为一个实验规范，根据定义，这项工作是不完整的。
The LCAF Types defined in this document are to support experimentation and are intended for cautious use in self-contained environments in support of the corresponding use-case documents. This document provides assignment for an initial set of approved LCAF Types (registered with IANA) and additional unapproved LCAF Types [RFC6830]. The unapproved LCAF encodings are defined to support further study and experimentation.
本文件中定义的LCAF类型用于支持实验，并用于在独立环境中谨慎使用，以支持相应的用例文件。本文件提供了一组初始批准的LCAF类型（在IANA注册）和其他未批准的LCAF类型的分配[RFC6830]。定义未经批准的LCAF编码以支持进一步的研究和实验。
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]中所述进行解释。
Address Family Identifier (AFI): a term used to describe an address encoding in a packet. Address families are defined for IPv4 and IPv6. See [AFN] and [RFC3232] for details. The reserved AFI value of 0 is used in this specification to indicate an unspecified encoded address where the length of the address is 0 bytes following the 16-bit AFI value of 0.
地址族标识符（AFI）：用于描述数据包中地址编码的术语。为IPv4和IPv6定义了地址族。有关详细信息，请参见[AFN]和[RFC3232]。在本规范中，保留的AFI值0用于指示未指定的编码地址，其中地址的长度在16位AFI值0之后为0字节。
Unspecified Address Format:
未指定的地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 0 | <no address 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 0 | <no address follows>
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Endpoint ID (EID): a 32-bit (for IPv4) or 128-bit (for IPv6) value used in the source and destination address fields of the first (most inner) LISP header of a packet. The host obtains a destination EID the same way it obtains a destination address today, for example, through a DNS lookup or SIP exchange. The source EID is obtained via existing mechanisms used to set a host's "local" IP address. An EID is allocated to a host from an EID-prefix block associated with the site where the host is located. An EID can be used by a host to refer to other hosts.
端点ID（EID）：数据包第一个（最内部）LISP头的源地址和目标地址字段中使用的32位（IPv4）或128位（IPv6）值。主机获取目标EID的方式与今天获取目标地址的方式相同，例如，通过DNS查找或SIP交换。源EID通过用于设置主机“本地”IP地址的现有机制获得。EID从与主机所在站点关联的EID前缀块分配给主机。主机可以使用EID引用其他主机。
Routing Locator (RLOC): the IPv4 or IPv6 address of an Egress Tunnel Router (ETR). It is the output of an EID-to-RLOC mapping lookup. An EID maps to one or more RLOCs. Typically, RLOCs are numbered from topologically aggregatable blocks that are assigned to a site at each point to which it attaches to the global Internet; where
路由定位器（RLOC）：出口隧道路由器（ETR）的IPv4或IPv6地址。它是EID到RLOC映射查找的输出。EID映射到一个或多个RLOC。通常，RLOC从拓扑上可聚合的块中进行编号，这些块被分配到其连接到全球互联网的每个点处的站点；哪里
the topology is defined by the connectivity of provider networks, RLOCs can be thought of as Provider-Assigned (PA) addresses. Multiple RLOCs can be assigned to the same ETR device or to multiple ETR devices at a site.
拓扑由提供商网络的连接性定义，RLOC可以被视为提供商分配（PA）地址。可以将多个RLOC分配给同一ETR设备或一个站点的多个ETR设备。
IANA has assigned AFI value 16387 (0x4003) to the LISP Canonical Address Format (LCAF). This specification defines the encoding format of the LISP Canonical Address (LCA). This section defines all Types for which an initial allocation in the LISP-LCAF registry is requested. See Section 7 for the complete list of such Types.
IANA已将AFI值16387（0x4003）分配给LISP规范地址格式（LCAF）。本规范定义了LISP规范地址（LCA）的编码格式。本节定义了在LISP-LCAF注册表中请求初始分配的所有类型。有关此类类型的完整列表，请参见第7节。
The AFI definitions in [AFN] only allocate code-points for the AFI value itself. The length of the address or entity that follows is not defined and is implied based on conventional experience. When LISP uses LCAF definitions from this document, the AFI-based address lengths are specified in this document. When new LCAF definitions are defined in other use-case documents, the AFI-based address lengths for any new AFI-encoded addresses are specified in those documents.
[AFN]中的AFI定义仅为AFI值本身分配代码点。以下地址或实体的长度没有定义，而是根据传统经验隐含的。当LISP使用本文档中的LCAF定义时，本文档中会指定基于AFI的地址长度。当新的LCAF定义在其他用例文档中定义时，任何新的AFI编码地址的基于AFI的地址长度都在这些文档中指定。
The first 6 bytes of a LISP Canonical Address are followed by a variable number of fields of variable length:
LISP规范地址的前6个字节后面是可变长度的可变字段数：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| . . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| . . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Rsvd1/Rsvd2: these 8-bit fields are reserved for future use and MUST be transmitted as 0 and ignored on receipt.
Rsvd1/Rsvd2：这些8位字段保留供将来使用，必须作为0传输，并在接收时忽略。
Flags: this 8-bit field is for future definition and use. For now, set to zero on transmission and ignored on receipt.
标志：此8位字段用于将来的定义和使用。目前，在传输时设置为零，在接收时忽略。
Type: this 8-bit field is specific to the LISP Canonical Address Format encodings. Both approved and unapproved values are listed below. Unapproved values are indicated; see Section 5 for more details.
类型：此8位字段特定于LISP规范地址格式编码。下面列出了已批准和未批准的值。指示未批准的值；详见第5节。
Type 0: Null Body
类型0:空正文
Type 1: AFI List
类型1：AFI列表
Type 2: Instance ID
类型2：实例ID
Type 3: AS Number
类型3：AS编号
Type 4: Application Data (unapproved; see Section 5)
类型4：应用程序数据（未批准；参见第5节）
Type 5: Geo-Coordinates
第5类：地理坐标
Type 6: Opaque Key (unapproved; see Section 5)
类型6：不透明密钥（未经批准；参见第5节）
Type 7: NAT-Traversal
类型7：NAT遍历
Type 8: Nonce Locator (unapproved; see Section 5)
类型8：临时定位器（未经批准；见第5节）
Type 9: Multicast Info
类型9：多播信息
Type 10: Explicit Locator Path
类型10：显式定位器路径
Type 11: Security Key
类型11：安全密钥
Type 12: Source/Dest Key
类型12：源/目标键
Type 13: Replication List Entry
类型13：复制列表条目
Type 14: JSON Data Model (unapproved; see Section 5)
类型14:JSON数据模型（未经批准；参见第5节）
Type 15: Key/Value Address Pair (unapproved; see Section 5)
Type 15: Key/Value Address Pair (unapproved; see Section 5)
Type 16: Encapsulation Format (unapproved; see Section 5)
类型16：封装格式（未经批准；见第5节）
Length: this 16-bit field is in units of bytes and covers all of the LISP Canonical Address payload, starting and including the byte after the Length field. When including the AFI, an LCAF-encoded address will have a minimum length of 8 bytes when the Length field is 0. The 8 bytes include the AFI, Flags, Type, Rsvd1, Rsvd2, and Length fields. When the AFI is not next to an encoded address in a control message, the encoded address will have a minimum length of 6 bytes when the Length field is 0. The 6 bytes include the Flags, Type, Rsvd1, Rsvd2, and Length fields.
长度：此16位字段以字节为单位，涵盖所有LISP规范地址有效负载，从长度字段后的字节开始并包括该字节。当包含AFI时，当长度字段为0时，LCAF编码地址的最小长度为8字节。这8个字节包括AFI、标志、类型、Rsvd1、Rsvd2和长度字段。当AFI不在控制消息中的编码地址旁边时，当长度字段为0时，编码地址的最小长度为6字节。这6个字节包括标志、类型、Rsvd1、Rsvd2和长度字段。
[RFC6830] states RLOC-records based on an IP address are sorted when encoded in control messages, so the locator-set has consistent order across all xTRs for a given EID. The sort order is based on sort-key {afi, RLOC-address}. When an RLOC based on an IP address is LCAF encoded, the sort-key is {afi, LCAF-Type}. Therefore, when a locator-set has a mix of AFI records and LCAF records, they are ordered from smallest to largest AFI value.
[RFC6830]基于IP地址的状态RLOC记录在编码到控制消息中时进行排序，因此定位器集在给定EID的所有XTR中具有一致的顺序。排序顺序基于排序键{afi，RLOC address}。当基于IP地址的RLOC采用LCAF编码时，排序键为{afi，LCAF Type}。因此，当定位器集混合了AFI记录和LCAF记录时，它们从最小的AFI值到最大的AFI值排序。
The following sections define the LCAF for the currently approved initial set of Type values.
以下各节定义了当前批准的初始类型值集的LCAF。
When multiple organizations inside of a LISP site are using private addresses [RFC1918] as EID prefixes, their address spaces must remain segregated due to possible address duplication. An Instance ID in the address encoding can aid in making the entire AFI-based address unique.
当LISP站点内的多个组织使用专用地址[RFC1918]作为EID前缀时，由于可能存在地址重复，它们的地址空间必须保持隔离。地址编码中的实例ID有助于使整个基于AFI的地址唯一。
Another use for the Instance ID LISP Canonical Address Format is when creating multiple segmented VPNs inside of a LISP site where keeping EID-prefix-based subnets is desirable.
实例ID LISP规范地址格式的另一个用途是在LISP站点内创建多个分段VPN时，需要保留基于EID前缀的子网。
Instance ID LISP Canonical Address Format:
实例ID LISP规范地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 2 | IID mask-len | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Instance ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 2 | IID mask-len | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Instance ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IID mask-len: if the AFI is set to 0, then this format is not encoding an extended EID prefix, but rather an Instance ID range where the 'IID mask-len' indicates the number of high-order bits used in the Instance ID field for the range. The low-order bits of the Instance ID field must be 0.
IID mask len：如果AFI设置为0，则此格式不是对扩展EID前缀进行编码，而是对实例ID范围进行编码，其中“IID mask len”表示该范围的实例ID字段中使用的高阶位数。实例ID字段的低位必须为0。
Length: length in bytes starting and including the byte after this Length field.
长度：以字节为单位的长度，从该长度字段开始，包括该长度字段后的字节。
Instance ID: the low-order 24 bits that can go into a LISP data header when the I bit is set. See [RFC6830] for details. The reason for the length difference is so that the maximum number of instances supported per mapping system is 2^32, while conserving space in the LISP data header. This comes at the expense of limiting the maximum number of instances per xTR to 2^24. If an xTR is configured with multiple Instance IDs where the value in the high-order 8 bits is the same, then the low-order 24 bits MUST be unique.
实例ID：设置I位时可以进入LISP数据头的低阶24位。详见[RFC6830]。长度差异的原因是，每个映射系统支持的最大实例数为2^32，同时保留LISP数据头中的空间。这是以将每个xTR的最大实例数限制为2^24为代价的。如果xTR配置了多个实例ID，其中高阶8位中的值相同，那么低阶24位必须是唯一的。
AFI = x: x can be any AFI value from [AFN].
AFI=x:x可以是[AFN]中的任何AFI值。
This LISP Canonical Address Type can be used to encode either EID or RLOC addresses.
此LISP规范地址类型可用于编码EID或RLOC地址。
Usage: When used as a lookup key, the EID is regarded as an extended-EID in the mapping system. This encoding is used in EID-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages. When LISP Delegated Database Tree (LISP-DDT) [LISP-DDT] is used as the mapping system mechanism, extended EIDs are used in Map-Referral messages.
用法：当用作查找键时，EID被视为映射系统中的扩展EID。此编码用于映射请求、映射回复、映射寄存器和映射通知消息中的EID记录。当LISP委托数据库树（LISP-DDT）[LISP-DDT]用作映射系统机制时，在映射引用消息中使用扩展EID。
When an Autonomous System (AS) number is stored in the LISP Mapping Database System for either policy or documentation reasons, it can be encoded in a LISP Canonical Address.
当自治系统（AS）编号出于策略或文档原因存储在LISP映射数据库系统中时，可以将其编码在LISP规范地址中。
AS Number LISP Canonical Address Format:
作为数字LISP标准地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 3 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AS Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 3 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AS Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes starting and including the byte after this Length field.
长度：以字节为单位的长度，从该长度字段开始，包括该长度字段后的字节。
AS Number: the 32-bit AS number of the autonomous system that has been assigned to either the EID or RLOC that follows.
AS编号：分配给EID或RLOC的自治系统的32位AS编号。
AFI = x: x can be any AFI value from [AFN].
AFI=x:x可以是[AFN]中的任何AFI值。
The AS Number LCAF Type can be used to encode either EID or RLOC addresses. The former is used to describe the LISP-ALT AS number the EID prefix for the site is being carried for. The latter is used to describe the AS that is carrying RLOC based prefixes in the underlying routing system.
AS编号LCAF类型可用于编码EID或RLOC地址。前者用于将LISP-ALT描述为站点的EID前缀的编号。后者用于描述在底层路由系统中承载基于RLOC前缀的AS。
Usage: This encoding can be used in EID-records or RLOC-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages. When LISP-DDT [LISP-DDT] is used as the mapping system mechanism, extended EIDs are used in Map-Referral messages.
用法：此编码可用于映射请求、映射回复、映射寄存器和映射通知消息中的EID记录或RLOC记录。当LISP-DDT[LISP-DDT]用作映射系统机制时，扩展EID将用于映射引用消息。
If an ETR desires to send a Map-Reply describing the Geo-Coordinates for each locator in its locator-set, it can use the Geo-Coordinates LCAF Type to convey physical location information.
如果ETR希望发送地图回复，描述其定位器集中每个定位器的地理坐标，则可以使用地理坐标LCAF类型来传递物理位置信息。
Coordinates are specified using the WGS 84 (World Geodetic System 1984) reference coordinate system [WGS-84].
使用WGS 84（世界大地测量系统1984）参考坐标系[WGS-84]指定坐标。
Geo-Coordinates LISP Canonical Address Format:
地理坐标LISP标准地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 5 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|N| Latitude Degrees | Minutes | Seconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|E| Longitude Degrees | Minutes | Seconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Altitude |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 5 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|N| Latitude Degrees | Minutes | Seconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|E| Longitude Degrees | Minutes | Seconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Altitude |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes starting and including the byte after this Length field.
长度：以字节为单位的长度，从该长度字段开始，包括该长度字段后的字节。
N: When set to 1 means north; otherwise, south.
N：设置为1时表示北；否则，南方。
Latitude Degrees: Valid values range from 0 to 90 degrees above or below the equator (northern or southern hemisphere, respectively).
纬度度：有效值范围为赤道上方或下方0到90度（分别为北半球或南半球）。
Latitude Minutes: Valid values range from 0 to 59.
纬度分钟数：有效值范围为0到59。
Latitude Seconds: Valid values range from 0 to 59.
纬度秒：有效值范围为0到59。
E: When set to 1 means east; otherwise, west.
E：当设置为1时，表示向东；否则，西方。
Longitude Degrees: Valid values are from 0 to 180 degrees right or left of the Prime Meridian.
经度：有效值为本初子午线右侧或左侧0到180度。
Longitude Minutes: Valid values range from 0 to 59.
经度分钟数：有效值范围为0到59。
Longitude Seconds: Valid values range from 0 to 59.
经度秒：有效值范围为0到59。
Altitude: Height relative to sea level in meters. This is a two's complement signed integer meaning that the altitude could be below sea level. A value of 0x7fffffff indicates no Altitude value is encoded.
海拔高度：相对于海平面的高度，单位为米。这是一个2的补码有符号整数，表示海拔可能低于海平面。0x7FFFFF值表示未编码高度值。
AFI = x: x can be any AFI value from [AFN].
AFI=x:x可以是[AFN]中的任何AFI值。
The Geo-Coordinates LCAF Type can be used to encode either EID or RLOC addresses. When used for EID encodings, you can determine the physical location of an EID along with the topological location by observing the locator-set.
地理坐标LCAF类型可用于编码EID或RLOC地址。用于EID编码时，可以通过观察定位器集来确定EID的物理位置以及拓扑位置。
Usage: This encoding can be used in EID-records or RLOC-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages. When LISP-DDT [LISP-DDT] is used as the mapping system mechanism, extended EIDs are used in Map-Referral messages.
用法：此编码可用于映射请求、映射回复、映射寄存器和映射通知消息中的EID记录或RLOC记录。当LISP-DDT[LISP-DDT]用作映射系统机制时，扩展EID将用于映射引用消息。
The use of the Geo-Coordinates LCAF encoding raises privacy issues as location information is privacy sensitive, and possibly unexpectedly privacy-sensitive information may be conveyed, e.g., if the location information corresponds to a router located in a person's home. Therefore, this encoding should not be used unless needed for operation of a LISP deployment. Before electing to utilize this encoding, care should be taken to ensure the appropriate policies are being used by the EID for controlling the conveyed information.
使用地理坐标LCAF编码会引起隐私问题，因为位置信息对隐私敏感，并且可能会意外地传递隐私敏感信息，例如，如果位置信息对应于位于个人家中的路由器。因此，除非LISP部署的操作需要，否则不应使用此编码。在选择使用此编码之前，应注意确保EID使用适当的策略来控制传输的信息。
When a LISP system is conveying global-address and mapped-port information when traversing through a NAT device, the NAT-Traversal LCAF Type is used. See [NAT-LISP] for details.
当LISP系统在穿越NAT设备时传输全局地址和映射端口信息时，将使用NAT穿越LCAF类型。有关详细信息，请参见[NAT-LISP]。
NAT-Traversal Canonical Address Format:
NAT遍历规范地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 7 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MS UDP Port Number | ETR UDP Port Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Global ETR RLOC Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | MS RLOC Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Private ETR RLOC Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | RTR RLOC Address 1 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | RTR RLOC Address k ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 7 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MS UDP Port Number | ETR UDP Port Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Global ETR RLOC Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | MS RLOC Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Private ETR RLOC Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | RTR RLOC Address 1 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | RTR RLOC Address k ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes starting and including the byte after this Length field.
长度：以字节为单位的长度，从该长度字段开始，包括该长度字段后的字节。
MS UDP Port Number: this is the UDP port number of the Map-Server and is set to 4342.
MS UDP端口号：这是地图服务器的UDP端口号，设置为4342。
ETR UDP Port Number: this is the port number returned to a LISP system that was copied from the source port from a packet that has flowed through a NAT device.
ETR UDP端口号：这是返回给LISP系统的端口号，该端口号是从流经NAT设备的数据包的源端口复制而来的。
AFI = x: x can be any AFI value from [AFN].
AFI=x:x可以是[AFN]中的任何AFI值。
Global ETR RLOC Address: this is an address known to be globally unique built by NAT-traversal functionality in a LISP router.
全局ETR RLOC地址：这是一个已知全局唯一的地址，由LISP路由器中的NAT遍历功能构建。
MS RLOC Address: this is the address of the Map-Server used in the destination RLOC of a packet that has flowed through a NAT device.
MS RLOC地址：这是在流经NAT设备的数据包的目标RLOC中使用的映射服务器的地址。
Private ETR RLOC Address: this is an address known to be a private address inserted in this LCAF by a LISP router that resides on the private side of a NAT device.
专用ETR RLOC地址：这是一个已知的地址，是驻留在NAT设备专用端的LISP路由器插入此LCAF的专用地址。
RTR RLOC Address: this is an encapsulation address used by an Ingress Tunnel Router (ITR) or Proxy Ingress Tunnel Router (PITR) that resides behind a NAT device. This address is known to have state in a NAT device so packets can flow from it to the LISP ETR
RTR RLOC地址：这是驻留在NAT设备后面的入口隧道路由器（ITR）或代理入口隧道路由器（PITR）使用的封装地址。已知该地址在NAT设备中具有状态，因此数据包可以从该地址流向LISP ETR
behind the NAT. There can be one or more NAT Re-encapsulating Tunnel Router (RTR) [NAT-LISP] addresses supplied in these set of fields. The number of RTRs encoded is determined by parsing each field. When there are no RTRs supplied, the RTR fields can be omitted and reflected by the LCAF length field or an AFI of 0 can be used to indicate zero RTRs encoded.
在NAT后面。在这些字段集中可以提供一个或多个NAT重新封装隧道路由器（RTR）[NAT-LISP]地址。通过解析每个字段来确定编码的RTR的数量。当没有提供RTR时，RTR字段可以省略并由LCAF长度字段反映，或者AFI为0可用于指示编码的零RTR。
Usage: This encoding can be used in Info-Request and Info-Reply messages. The mapping system does not store this information. The information is used by an xTR and Map-Server to convey private and public address information when traversing NAT and firewall devices.
用法：此编码可用于信息请求和信息回复消息。映射系统不存储此信息。当穿越NAT和防火墙设备时，xTR和Map服务器使用这些信息来传递私有和公共地址信息。
Care should be taken to protect privacy against the adverse use of a Global or Private ETR RLOC Address by ensuring policy controls are used during EID registrations that use this LCAF Type in RLOC-records. Refer to the use-case documents for additional information.
通过确保在RLOC记录中使用此LCAF类型的EID注册期间使用策略控制，应注意保护隐私，防止对全局或私有ETR RLOC地址的不利使用。有关更多信息，请参阅用例文档。
Multicast group information can be published in the mapping database. So a lookup on a group address EID can return a replication list of RLOC group addresses or RLOC unicast addresses. The intent of this type of unicast replication is to deliver packets to multiple ETRs at receiver LISP multicast sites. The locator-set encoding for this EID-record Type can be a list of ETRs when they each register with "Merge Semantics". The encoding can be a typical AFI-encoded locator address. When an RTR list is being registered (with multiple levels according to [LISP-RE]), the Replication List Entry LCAF Type is used for locator encoding.
可以在映射数据库中发布多播组信息。因此，查找组地址EID可以返回RLOC组地址或RLOC单播地址的复制列表。这种类型的单播复制的目的是将数据包传送到接收方LISP多播站点的多个ETR。当每个ETR使用“合并语义”注册时，此EID记录类型的定位器集编码可以是ETR列表。编码可以是典型的AFI编码的定位器地址。当注册RTR列表时（根据[LISP-RE]具有多个级别），复制列表条目LCAF类型用于定位器编码。
This LCAF encoding can be used to send broadcast packets to all members of a subnet when an EID is away from its home subnet location.
当EID远离其主子网位置时，此LCAF编码可用于向子网的所有成员发送广播数据包。
Multicast Info Canonical Address Format:
多播信息规范地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 9 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Instance ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Source MaskLen| Group MaskLen |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Source/Subnet Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Group Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 9 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Instance ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Source MaskLen| Group MaskLen |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Source/Subnet Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Group Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes starting and including the byte after this Length field.
长度：以字节为单位的长度，从该长度字段开始，包括该长度字段后的字节。
Reserved: must be set to zero and ignored on receipt.
保留：必须设置为零，并在收到时忽略。
Instance ID: the low-order 24 bits that can go into a LISP data header when the I bit is set. See [RFC6830] for details. The use of the Instance ID in this LCAF Type is to associate a multicast forwarding entry for a given VPN. The Instance ID describes the VPN and is registered to the mapping database system as a 3-tuple of (Instance ID, S-prefix, G-prefix).
实例ID：设置I位时可以进入LISP数据头的低阶24位。详见[RFC6830]。此LCAF类型中的实例ID用于关联给定VPN的多播转发条目。实例ID描述VPN，并作为3元组（实例ID、S前缀、G前缀）注册到映射数据库系统。
Source MaskLen: the mask length of the source prefix that follows. The length is the number of high-order mask bits set.
Source MaskLen：后面的源前缀的掩码长度。长度是设置的高阶掩码位数。
Group MaskLen: the mask length of the group prefix that follows. The length is the number of high-order mask bits set.
组掩码：后面的组前缀的掩码长度。长度是设置的高阶掩码位数。
AFI = x: x can be any AFI value from [AFN]. When a specific address family has a multicast address semantic, this field must be either a group address or a broadcast address.
AFI=x:x可以是[AFN]中的任何AFI值。当特定地址族具有多播地址语义时，此字段必须是组地址或广播地址。
Source/Subnet Address: the source address or prefix for encoding an (S,G) multicast entry.
源/子网地址：用于编码（S，G）多播条目的源地址或前缀。
Group Address: the group address or group prefix for encoding (S,G) or (*,G) multicast entries.
组地址：用于编码（S，G）或（*，G）多播条目的组地址或组前缀。
Usage: This encoding can be used in EID-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages. When LISP-DDT [LISP-DDT] is used as the mapping system mechanism, extended EIDs are used in Map-Referral messages.
用法：此编码可用于映射请求、映射回复、映射注册和映射通知消息中的EID记录。当LISP-DDT[LISP-DDT]用作映射系统机制时，扩展EID将用于映射引用消息。
For a given EID lookup into the mapping database, this LCAF can be returned to provide a list of locators in an explicit re-encapsulation path. See [LISP-TE] for details.
对于映射数据库中的给定EID查找，可以返回此LCAF以在显式重新封装路径中提供定位器列表。有关详细信息，请参见[LISP-TE]。
Explicit Locator Path (ELP) Canonical Address Format:
显式定位器路径（ELP）规范地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 10 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Rsvd3 |L|P|S| AFI = x |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reencap Hop 1 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Rsvd3 |L|P|S| AFI = x |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reencap Hop k ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 10 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Rsvd3 |L|P|S| AFI = x |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reencap Hop 1 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Rsvd3 |L|P|S| AFI = x |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reencap Hop k ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes starting and including the byte after this Length field.
长度：以字节为单位的长度，从该长度字段开始，包括该长度字段后的字节。
Rsvd3: this field is reserved for future use and MUST be transmitted as 0 and ignored on receipt.
Rsvd3:此字段保留供将来使用，必须作为0传输，并在收到时忽略。
Lookup bit (L): this is the Lookup bit used to indicate to the user of the ELP not to use this address for encapsulation but to look it up in the mapping database system to obtain an encapsulating RLOC address.
查找位（L）：这是一个查找位，用于指示ELP用户不要将此地址用于封装，而是在映射数据库系统中查找以获得封装RLOC地址。
RLOC Probe bit (P): this is the RLOC Probe bit that means the Reencap Hop allows RLOC-probe messages to be sent to it. When the R bit is set to 0, RLOC-probes must not be sent. When a Reencap Hop is an anycast address then multiple physical Reencap Hops are using the same RLOC address. In this case, RLOC-probes are not needed because when the closest RLOC address is not reachable, another RLOC address can be reachable.
RLOC探测位（P）：这是RLOC探测位，表示Reencap跃点允许向其发送RLOC探测消息。当R位设置为0时，不得发送RLOC探测。当Reencap跃点是选播地址时，则多个物理Reencap跃点使用相同的RLOC地址。在这种情况下，不需要RLOC探测，因为当无法访问最近的RLOC地址时，可以访问另一个RLOC地址。
Strict bit (S): this is the Strict bit, which means the associated Reencap Hop is required to be used. If this bit is 0, the re-encapsulator can skip this Reencap Hop and go to the next one in the list.
严格位：这是严格位，这意味着需要使用关联的Reencap跃点。如果此位为0，则重新封装器可以跳过此Reencap跃点并转到列表中的下一个跃点。
AFI = x: x can be any AFI value from [AFN]. When a specific AFI has its own encoding of a multicast address, this field must be either a group address or a broadcast address.
AFI=x:x可以是[AFN]中的任何AFI值。当特定AFI有自己的多播地址编码时，此字段必须是组地址或广播地址。
Usage: This encoding can be used in RLOC-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages. This encoding does not need to be understood by the mapping system for mapping database lookups, since this LCAF Type is not a lookup key.
用法：此编码可用于映射请求、映射回复、映射寄存器和映射通知消息中的RLOC记录。映射数据库查找时，映射系统不需要理解此编码，因为此LCAF类型不是查找键。
When a locator in a locator-set has a security key associated with it, this LCAF will be used to encode key material. See [LISP-DDT] for details.
当定位器集中的定位器具有与其关联的安全密钥时，此LCAF将用于对密钥材料进行编码。有关详细信息，请参见[LISP-DDT]。
Security Key Canonical Address Format:
安全密钥规范地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 11 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Key Count | Rsvd3 | Key Algorithm | Rsvd4 |R|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Key Length | Key Material ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... Key Material |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Locator Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 11 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Key Count | Rsvd3 | Key Algorithm | Rsvd4 |R|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Key Length | Key Material ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... Key Material |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Locator Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes starting and including the byte after this Length field.
长度：以字节为单位的长度，从该长度字段开始，包括该长度字段后的字节。
Key Count: the Key Count field declares the number of Key sections included in this LCAF. A Key section is made up of Key Length and Key Material fields.
密钥计数：密钥计数字段声明此LCAF中包含的密钥节数。关键部分由关键长度和关键材质字段组成。
Rsvd3: this field is reserved for future use and MUST be transmitted as 0 and ignored on receipt.
Rsvd3:此字段保留供将来使用，必须作为0传输，并在收到时忽略。
Key Algorithm: the Key Algorithm field identifies the key's cryptographic algorithm and specifies the format of the Public Key field. Refer to the [LISP-DDT] and [RFC8061] use cases for definitions of this field.
密钥算法：密钥算法字段标识密钥的加密算法，并指定公钥字段的格式。有关此字段的定义，请参阅[LISP-DDT]和[RFC8061]用例。
Rsvd4: this field is reserved for future use and MUST be transmitted as 0 and ignored on receipt.
Rsvd4:此字段保留供将来使用，必须作为0传输，并在收到时忽略。
R bit: this is the Revoke bit and, if set, it specifies that this key is being revoked.
R位：这是Revoke位，如果设置，则它指定该密钥被撤销。
Key Length: this field determines the length in bytes of the Key Material field.
密钥长度：该字段确定密钥材质字段的长度（以字节为单位）。
Key Material: the Key Material field stores the key material. The format of the key material stored depends on the Key Algorithm field.
关键材料：关键材料字段存储关键材料。存储的关键材料的格式取决于关键算法字段。
AFI = x: x can be any AFI value from [AFN]. This is the locator address that owns the encoded security key.
AFI=x:x可以是[AFN]中的任何AFI值。这是拥有编码安全密钥的定位器地址。
Usage: This encoding can be used in EID-records or RLOC-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages. When LISP-DDT [LISP-DDT] is used as the mapping system mechanism, extended EIDs are used in Map-Referral messages.
用法：此编码可用于映射请求、映射回复、映射寄存器和映射通知消息中的EID记录或RLOC记录。当LISP-DDT[LISP-DDT]用作映射系统机制时，扩展EID将用于映射引用消息。
When both a source and destination address of a flow need consideration for different locator-sets, this 2-tuple key is used in EID fields in LISP control messages. When the Source/Dest key is registered to the mapping database, it can be encoded as a source-prefix and destination-prefix. When the Source/Dest is used as a key for a mapping database lookup, the source and destination come from a data packet.
当流的源地址和目标地址都需要考虑不同的定位器集时，在LISP控制消息的EID字段中使用此2元组键。当源/目标密钥注册到映射数据库时，可以将其编码为源前缀和目标前缀。当源/目标用作映射数据库查找的键时，源和目标来自数据包。
Source/Dest Key Canonical Address Format:
源/目标密钥规范地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 12 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Source-ML | Dest-ML |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Source-Prefix ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = y | Destination-Prefix ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 12 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Source-ML | Dest-ML |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Source-Prefix ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = y | Destination-Prefix ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes starting and including the byte after this Length field.
长度：以字节为单位的长度，从该长度字段开始，包括该长度字段后的字节。
Reserved: must be set to zero and ignored on receipt.
保留：必须设置为零，并在收到时忽略。
Source-ML: the mask length of the source prefix that follows. The length is the number of high-order mask bits set.
Source ML：后面的源前缀的掩码长度。长度是设置的高阶掩码位数。
Dest-ML: the mask length of the destination prefix that follows. The length is the number of high-order mask bits set.
Dest ML：后面的目标前缀的掩码长度。长度是设置的高阶掩码位数。
AFI = x: x can be any AFI value from [AFN].
AFI=x:x可以是[AFN]中的任何AFI值。
AFI = y: y can be any AFI value from [AFN]. When a specific address family has a multicast address semantic, this field must be either a group address or a broadcast address.
AFI=y:y可以是[AFN]中的任何AFI值。当特定地址族具有多播地址语义时，此字段必须是组地址或广播地址。
Usage: This encoding can be used in EID-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages. When LISP-DDT [LISP-DDT] is used as the mapping system mechanism, extended EIDs are used in Map-Referral messages. Refer to [LISP-TE] for usage details of this LCAF Type.
用法：此编码可用于映射请求、映射回复、映射注册和映射通知消息中的EID记录。当LISP-DDT[LISP-DDT]用作映射系统机制时，扩展EID将用于映射引用消息。有关此LCAF类型的使用详情，请参阅[LISP-TE]。
The Replication List Entry LCAF Type is an encoding for a locator being used for unicast replication according to the specification in [LISP-RE]. This locator encoding is pointed to by a Multicast Info LCAF Type and is registered by Re-encapsulating Tunnel Routers (RTRs) that are participating in an overlay distribution tree. Each RTR will register its locator address and its configured level in the distribution tree.
复制列表条目LCAF Type是根据[LISP-RE]中的规范，用于单播复制的定位器的编码。此定位器编码由多播信息LCAF类型指向，并通过重新封装参与覆盖分发树的隧道路由器（RTR）进行注册。每个RTR将在分发树中注册其定位器地址及其配置级别。
Replication List Entry Canonical Address Format:
复制列表项规范地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 13 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Rsvd3 | Rsvd4 | Level Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | RTR/ETR #1 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Rsvd3 | Rsvd4 | Level Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | RTR/ETR #n ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 13 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Rsvd3 | Rsvd4 | Level Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | RTR/ETR #1 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Rsvd3 | Rsvd4 | Level Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | RTR/ETR #n ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes starting and including the byte after this Length field.
长度：以字节为单位的长度，从该长度字段开始，包括该长度字段后的字节。
Rsvd3/Rsvd4: must be set to zero and ignored on receipt.
Rsvd3/Rsvd4:必须设置为零，并在收到时忽略。
Level Value: this value is associated with the level within the overlay distribution tree hierarchy where the RTR resides. The level numbers are ordered from lowest value being close to the ITR (meaning that ITRs replicate to level-0 RTRs) and higher levels are further downstream on the distribution tree closer to ETRs of multicast receiver sites.
级别值：该值与RTR所在的覆盖分发树层次结构中的级别相关联。级别编号从接近ITR（意味着ITR复制到0级RTR）的最低值开始排序，更高级别在更靠近多播接收器站点ETR的分发树下游。
AFI = x: x can be any AFI value from [AFN]. A specific AFI has its own encoding of either a unicast or multicast locator address. For efficiency reasons, all RTR/ETR entries for the same level should be combined by a Map-Server to avoid searching through the entire multilevel list of locator entries in a Map-Reply message.
AFI=x:x可以是[AFN]中的任何AFI值。特定AFI有自己的单播或多播定位地址编码。出于效率考虑，同一级别的所有RTR/ETR条目应由地图服务器组合，以避免在地图回复消息中搜索定位器条目的整个多级列表。
Usage: This encoding can be used in RLOC-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages.
用法：此编码可用于映射请求、映射回复、映射寄存器和映射通知消息中的RLOC记录。
When header translation between IPv4 and IPv6 is desirable, a LISP Canonical Address can use the AFI List LCAF Type to carry a variable number of AFIs in one LCAF AFI.
当需要IPv4和IPv6之间的标头转换时，LISP规范地址可以使用AFI列表LCAF类型在一个LCAF AFI中携带可变数量的AFI。
Address Binding LISP Canonical Address Format:
地址绑定LISP规范地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 1 | IPv4 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv4 Address | AFI = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 1 | IPv4 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv4 Address | AFI = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes starting and including the byte after this Length field.
长度：以字节为单位的长度，从该长度字段开始，包括该长度字段后的字节。
This type of address format can be included in a Map-Request when the address is being used as an EID, but the LISP Mapping Database System lookup destination can use only the IPv4 address. This is so a Mapping Database Service Transport System, such as LISP-ALT [RFC6836], can use the Map-Request destination address to route the control message to the desired LISP site.
当地址用作EID时，这种类型的地址格式可以包含在映射请求中，但LISP映射数据库系统查找目标只能使用IPv4地址。这使得映射数据库服务传输系统（如LISP-ALT[RFC6836]）可以使用映射请求目标地址将控制消息路由到所需的LISP站点。
Usage: This encoding can be used in EID-records or RLOC-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages. See the other subsections in this section for specific use cases.
用法：此编码可用于映射请求、映射回复、映射寄存器和映射通知消息中的EID记录或RLOC记录。有关特定用例，请参见本节中的其他小节。
When Media Access Control (MAC) addresses are stored in the LISP Mapping Database System, the AFI List LCAF Type can be used to carry AFI 6.
当媒体访问控制（MAC）地址存储在LISP映射数据库系统中时，AFI列表LCAF类型可用于携带AFI 6。
MAC Address LISP Canonical Address Format:
MAC地址LISP标准地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 6 | Layer 2 MAC Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... Layer 2 MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 6 | Layer 2 MAC Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... Layer 2 MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes starting and including the byte after this Length field.
长度：以字节为单位的长度，从该长度字段开始，包括该长度字段后的字节。
This address format can be used to connect Layer 2 domains together using LISP over an IPv4 or IPv6 core network to create a Layer 2 VPN. In this use case, a MAC address is being used as an EID, and the locator-set that this EID maps to can be an IPv4 or IPv6 RLOC, or even another MAC address being used as an RLOC. See [EID-MOBILITY] for how Layer 2 VPNs operate when doing EID mobility.
此地址格式可用于通过IPv4或IPv6核心网络使用LISP将第2层域连接在一起，以创建第2层VPN。在此用例中，MAC地址用作EID，此EID映射到的定位器集可以是IPv4或IPv6 RLOC，甚至可以是另一个用作RLOC的MAC地址。请参阅[EID-MOBILITY]，了解进行EID移动时第2层VPN的操作方式。
Care should be taken to protect privacy against the adverse use of a Layer 2 MAC address by ensuring policy controls are used during EID registrations that use AFI=6 encodings in RLOC-records. Refer to the use-case documents for additional information.
通过确保在RLOC记录中使用AFI=6编码的EID注册期间使用策略控制，应注意保护隐私，以防第2层MAC地址的不利使用。有关更多信息，请参阅用例文档。
If DNS names [RFC1035] or URIs [RFC3986] are stored in the LISP Mapping Database System, the AFI List LCAF Type can be used to carry an ASCII string.
如果DNS名称[RFC1035]或URI[RFC3986]存储在LISP映射数据库系统中，则AFI列表LCAF类型可用于携带ASCII字符串。
ASCII LISP Canonical Address Format:
ASCII LISP标准地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 17 | DNS Name or URI ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 17 | DNS Name or URI ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes starting and including the byte after this Length field.
长度：以字节为单位的长度，从该长度字段开始，包括该长度字段后的字节。
An example for using DNS names is when an ETR registers a mapping with an EID-record encoded as (AFI=1, 10.0.0.0/8) with an RLOC-record (AFI=17, "router.abc.com").
使用DNS名称的一个示例是，ETR使用编码为（AFI=1，10.0.0.0/8）的EID记录和RLOC记录（AFI=17，“router.abc.com”）注册映射。
When any combination of above is desirable, the AFI List LCAF Type value can be used to carry within the LCAF AFI another LCAF AFI (for example, Application-Specific Data in Section 5.1).
当需要上述任何组合时，AFI列表LCAF类型值可用于在LCAF AFI中携带另一个LCAF AFI（例如，第5.1节中的特定应用数据）。
Recursive LISP Canonical Address Format:
递归LISP规范地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 4 | Rsvd2 | Length2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP TOS, IPv6 TC or Flow Label | Protocol |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Port (lower-range) | Local Port (upper-range) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remote Port (lower-range) | Remote Port (upper-range) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 1 | IPv4 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 4 | Rsvd2 | Length2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP TOS, IPv6 TC or Flow Label | Protocol |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Port (lower-range) | Local Port (upper-range) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remote Port (lower-range) | Remote Port (upper-range) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 1 | IPv4 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes starting and including the byte after this Length field.
长度：以字节为单位的长度，从该长度字段开始，包括该长度字段后的字节。
Length2: length in bytes starting and including the byte after this Length2 field.
Length2：以字节为单位的长度，从该Length2字段开始，包括该字段后面的字节。
This format could be used by a Mapping Database Service Transport System, such as LISP-ALT [RFC6836], where the AFI=1 IPv4 address is used as an EID and placed in the Map-Request destination address by the sending LISP system. The ALT system can deliver the Map-Request to the LISP destination site independent of the Application Data LCAF
此格式可由映射数据库服务传输系统使用，如LISP-ALT[RFC6836]，其中AFI=1 IPv4地址用作EID，并由发送LISP系统放置在映射请求目标地址中。ALT系统可以独立于应用程序数据LCAF向LISP目标站点发送映射请求
Type AFI payload values. When this AFI is processed by the destination LISP site, it can return different locator-sets based on the type of application or level of service that is being requested.
输入AFI有效载荷值。当目标LISP站点处理此AFI时，它可以根据所请求的应用程序类型或服务级别返回不同的定位器集。
A LISP system should use the AFI List LCAF Type format when sending to LISP systems that do not support a particular LCAF Type used to encode locators. This allows the receiving system to be able to parse a locator address for encapsulation purposes. The list of AFIs in an AFI List LCAF Type has no semantic ordering and a receiver should parse each AFI element no matter what the ordering.
当发送到不支持用于编码定位器的特定LCAF类型的LISP系统时，LISP系统应使用AFI List LCAF类型格式。这允许接收系统能够出于封装目的解析定位器地址。AFI list LCAF类型中的AFI列表没有语义顺序，接收者应该解析每个AFI元素，无论顺序如何。
Compatibility Mode Address Format:
兼容模式地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 5 | Rsvd2 | Length2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|N| Latitude Degrees | Minutes | Seconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|E| Longitude Degrees | Minutes | Seconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Altitude |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 0 | AFI = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 5 | Rsvd2 | Length2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|N| Latitude Degrees | Minutes | Seconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|E| Longitude Degrees | Minutes | Seconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Altitude |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 0 | AFI = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes starting and including the byte after this Length field.
长度：以字节为单位的长度，从该长度字段开始，包括该长度字段后的字节。
Length2: length in bytes starting and including the byte after this Length2 field.
Length2：以字节为单位的长度，从该Length2字段开始，包括该字段后面的字节。
If a system does not recognized the Geo-Coordinates LCAF Type that is accompanying a locator address, an encoder can include the Geo-Coordinates LCAF Type embedded in an AFI List LCAF Type where the AFI
如果系统无法识别定位器地址随附的地理坐标LCAF类型，编码器可以包括嵌入AFI列表LCAF类型中的地理坐标LCAF类型，其中AFI
in the Geo-Coordinates LCAF Type is set to 0 and the AFI encoded next in the list is encoded with a valid AFI value to identify the locator address.
在地理坐标中，LCAF类型设置为0，列表中下一个编码的AFI使用有效的AFI值进行编码，以标识定位器地址。
A LISP system is required to support the AFI List LCAF Type to use this procedure. It would skip over 10 bytes of the Geo-Coordinates LCAF Type to get to the locator address encoding (an IPv4 locator address). A LISP system that does support the Geo-Coordinates LCAF Type can support parsing the locator address within the Geo-Coordinates LCAF Type encoding or in the locator encoding that follows in the AFI List LCAF Type.
要使用本程序，需要LISP系统支持AFI列表LCAF类型。它将跳过10个字节的地理坐标LCAF类型，以获取定位器地址编码（IPv4定位器地址）。支持地理坐标LCAF类型的LISP系统可以支持在地理坐标LCAF类型编码或AFI列表LCAF类型后面的定位器编码中解析定位器地址。
The following sections describe experimental LCAF encodings. These LCAF Types are not approved (i.e., not registered with IANA). The inclusion of these encodings in this document is in support of further study and experimentation to determine whether these encodings are functional, if there is a demand for these use cases, and to better understand deployment considerations. As noted previously, these LCAF Types are restricted to cautious use in self-contained environments in support of the corresponding use-case documents.
以下各节描述了实验性LCAF编码。这些LCAF类型未经批准（即未在IANA注册）。在本文档中包含这些编码是为了支持进一步的研究和实验，以确定这些编码是否具有功能，是否需要这些用例，以及更好地理解部署注意事项。如前所述，这些LCAF类型仅限于在自包含环境中谨慎使用，以支持相应的用例文档。
When a locator-set needs to be conveyed based on the type of application or the Per-Hop Behavior (PHB) of a packet, the Application Data LCAF Type can be used.
当需要基于应用程序类型或数据包的每跳行为（PHB）传送定位器集时，可以使用应用程序数据LCAF类型。
Application Data LISP Canonical Address Format:
应用程序数据LISP规范地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 4 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP TOS, IPv6 TC, or Flow Label | Protocol |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Port (lower-range) | Local Port (upper-range) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remote Port (lower-range) | Remote Port (upper-range) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 4 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP TOS, IPv6 TC, or Flow Label | Protocol |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Port (lower-range) | Local Port (upper-range) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remote Port (lower-range) | Remote Port (upper-range) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes starting and including the byte after this Length field.
长度：以字节为单位的长度，从该长度字段开始，包括该长度字段后的字节。
IP TOS, IPv6 TC, or Flow Label: this field stores the 8-bit IPv4 TOS field used in an IPv4 header, the 8-bit IPv6 Traffic Class or Flow Label used in an IPv6 header.
IP TOS、IPv6 TC或流标签：此字段存储IPv4标头中使用的8位IPv4 TOS字段、IPv6标头中使用的8位IPv6流量类别或流标签。
Local Port/Remote Port Ranges: these fields are from the TCP, UDP, or Stream Control Transmission Protocol (SCTP) transport header. A range can be specified by using a lower value and an upper value. When a single port is encoded, the lower and upper value fields are the same.
本地端口/远程端口范围：这些字段来自TCP、UDP或流控制传输协议（SCTP）传输头。可以通过使用下限值和上限值来指定范围。对单个端口进行编码时，下限值字段和上限值字段是相同的。
AFI = x: x can be any AFI value from [AFN].
AFI=x:x可以是[AFN]中的任何AFI值。
The Application Data LCAF Type is used for an EID encoding when an ITR wants a locator-set for a specific application. When used for an RLOC encoding, the ETR is supplying a locator-set for each specific application is has been configured to advertise.
当ITR需要为特定应用设置定位器时，应用程序数据LCAF类型用于EID编码。当用于RLOC编码时，ETR为配置为播发的每个特定应用程序提供定位器集。
Usage: This encoding can be used in EID-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages. When LISP-DDT [LISP-DDT] is used as the mapping system mechanism, extended EIDs are used in Map-Referral messages. This LCAF Type is used as a lookup key to the mapping system that can return a longest-match or exact-match entry.
用法：此编码可用于映射请求、映射回复、映射注册和映射通知消息中的EID记录。当LISP-DDT[LISP-DDT]用作映射系统机制时，扩展EID将用于映射引用消息。此LCAF类型用作映射系统的查找键，可以返回最长匹配项或精确匹配项。
When the LISP Mapping Database System holds information accessed by a generic formatted key (where the key is not the usual IPv4 or IPv6 address), an opaque key may be desirable.
当LISP映射数据库系统保存由通用格式化密钥访问的信息（其中密钥不是通常的IPv4或IPv6地址）时，可能需要不透明密钥。
Opaque Key LISP Canonical Address Format:
不透明密钥LISP规范地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 6 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Key Field Num | Key Wildcard Fields | Key . . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| . . . Key |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 6 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Key Field Num | Key Wildcard Fields | Key . . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| . . . Key |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes starting and including the byte after this Length field.
长度：以字节为单位的长度，从该长度字段开始，包括该长度字段后的字节。
Key Field Num: the value of this field is the number of "Key" sub-fields minus 1, the Key field can be broken up into. So, if this field has a value of 0, there is one sub-field in the "Key". The width of the sub-fields are fixed length. So, for a key size of 8 bytes, with a Key Field Num of 3, four sub-fields of 2 bytes each in length are allowed. Allowing for a reasonable number of 16 sub-field separators, valid values range from 0 to 15.
Key Field Num：该字段的值为“Key”子字段的个数减去1，可以将Key字段拆分为多个字段。因此，如果该字段的值为0，“键”中有一个子字段。子字段的宽度为固定长度。因此，对于8字节的密钥大小，如果密钥字段Num为3，则允许四个子字段的长度各为2字节。考虑到16个子字段分隔符的合理数量，有效值范围为0到15。
Key Wildcard Fields: describes which fields in the key are not used as part of the key lookup. This wildcard encoding is a bitfield. Each bit is a don't-care bit for a corresponding field in the key. Bit 0 (the low-order bit) in this bitfield corresponds the first field, the low-order field in the key, bit 1 the second field, and so on. When a bit is set in the bitfield, it is a don't-care bit and should not be considered as part of the database lookup. When the entire 16 bits are set to 0, then all bits of the key are used for the database lookup.
密钥通配符字段：描述密钥中不作为密钥查找一部分使用的字段。此通配符编码是一个位字段。每个位都是键中相应字段的不关心位。该位字段中的位0（低阶位）对应第一个字段、键中的低阶字段、位1对应第二个字段，依此类推。在位字段中设置位时，它是一个不关心的位，不应被视为数据库查找的一部分。如果将整个16位设置为0，则该键的所有位都将用于数据库查找。
Key: the variable length key used to do a LISP Mapping Database System lookup. The length of the key is the value n (as shown above).
键：用于执行LISP映射数据库系统查找的可变长度键。键的长度是值n（如上所示）。
Usage: This is an experimental Type where the usage has not yet been defined.
用法：这是一种尚未定义用法的实验类型。
When a public Proxy Egress Tunnel Router (PETR) device wants to verify who is encapsulating to it, it can check for a specific nonce value in the LISP-encapsulated packet. To convey the nonce to admitted ITRs or PITRs, this LCAF is used in a Map-Register or Map-Reply locator-record.
当公共代理出口隧道路由器（PETR）设备想要验证谁封装到它时，它可以检查LISP封装的数据包中的特定nonce值。为了将nonce传送到允许的ITR或PITR，此LCAF用于映射寄存器或映射应答定位器记录中。
Nonce Locator Canonical Address Format:
Nonce定位器规范地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 8 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Nonce |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 8 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Nonce |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes starting and including the byte after this Length field.
长度：以字节为单位的长度，从该长度字段开始，包括该长度字段后的字节。
Reserved: must be set to zero and ignored on receipt.
保留：必须设置为零，并在收到时忽略。
Nonce: a nonce value returned by an ETR in a Map-Reply locator-record to be used by an ITR or PITR when encapsulating to the locator address encoded in the AFI field of this LCAF Type. This nonce value is inserted in the nonce field in the LISP header encapsulation.
Nonce：在映射应答定位器记录中由ETR返回的一个Nonce值，当封装到此LCAF类型的AFI字段中编码的定位器地址时，ITR或PITR将使用该值。此nonce值插入LISP头封装的nonce字段中。
AFI = x: x can be any AFI value from [AFN].
AFI=x:x可以是[AFN]中的任何AFI值。
Usage: This is an experimental Type where the usage has not yet been defined.
用法：这是一种尚未定义用法的实验类型。
This Type allows a JSON data model to be encoded as either an EID or an RLOC.
这种类型允许将JSON数据模型编码为EID或RLOC。
JSON Data Model Type Address Format:
JSON数据模型类型地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 14 | Rsvd2 |B| Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| JSON length | JSON binary/text encoding ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Optional Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 14 | Rsvd2 |B| Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| JSON length | JSON binary/text encoding ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Optional Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes starting and including the byte after this Length field.
长度：以字节为单位的长度，从该长度字段开始，包括该长度字段后的字节。
B bit: indicates that the JSON field is binary encoded according to [JSON-BINARY] when the bit is set to 1. Otherwise, the encoding is based on text encoding according to [RFC7159].
B位：表示当位设置为1时，JSON字段根据[JSON-binary]进行二进制编码。否则，编码基于根据[RFC7159]的文本编码。
JSON length: length in octets of the following JSON binary/text encoding field.
JSON长度：以下JSON二进制/文本编码字段的长度（以八位字节为单位）。
JSON binary/text encoding: a variable-length field that contains either binary or text encodings.
JSON二进制/文本编码：包含二进制或文本编码的可变长度字段。
AFI = x: x can be any AFI value from [AFN]. A specific AFI has its own encoding of either a unicast or multicast locator address. All RTR/ETR entries for the same level should be combined by a Map-Server to avoid searching through the entire multilevel list of locator entries in a Map-Reply message.
AFI=x:x可以是[AFN]中的任何AFI值。特定AFI有自己的单播或多播定位地址编码。同一级别的所有RTR/ETR条目应由地图服务器组合，以避免在地图回复消息中搜索整个多级定位器条目列表。
Usage: This is an experimental Type where the usage has not yet been defined. An example mapping is an EID-record encoded as a distinguished-name "cpe-router" and an RLOC-record encoded as a JSON string "{ "router-address" : "1.1.1.1", "router-mask" : "8" }".
用法：这是一种尚未定义用法的实验类型。示例映射是编码为可分辨名称“cpe路由器”的EID记录和编码为JSON字符串“{”路由器地址“：“1.1.1.1”，“路由器掩码“：“8”}”的RLOC记录。
The Key/Value pair is, for example, useful for attaching attributes to other elements of LISP packets, such as EIDs or RLOCs. When attaching attributes to EIDs or RLOCs, it's necessary to distinguish between the element that should be used as EID or RLOC and, hence, as the key for lookups and additional attributes. This is especially the case when the difference cannot be determined from the Types of the elements, such as when two IP addresses are being used.
例如，键/值对用于将属性附加到LISP数据包的其他元素，例如EID或RLOCs。将属性附加到EID或RLOC时，有必要区分应该用作EID或RLOC的元素，以及作为查找和附加属性键的元素。当无法从元素的类型确定差异时，尤其是当使用两个IP地址时。
Key/Value Address Pair Address Format:
键/值地址对地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 15 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address as Key ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = y | Address as Value ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 15 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address as Key ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = y | Address as Value ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes starting and including the byte after this Length field.
长度：以字节为单位的长度，从该长度字段开始，包括该长度字段后的字节。
AFI = x: x is the "Address as Key" AFI that can have any value from [AFN]. A specific AFI has its own encoding of either a unicast or a multicast locator address. All RTR/ETR entries for the same level should be combined by a Map-Server to avoid searching through the entire multilevel list of locator entries in a Map-Reply message.
AFI=x:x是“作为键的地址”AFI，可以具有[AFN]中的任何值。特定的AFI有自己的单播或多播定位地址编码。同一级别的所有RTR/ETR条目应由地图服务器组合，以避免在地图回复消息中搜索整个多级定位器条目列表。
Address as Key: AFI-encoded address that will be attached with the attributes encoded in "Address as Value", which follows this field.
地址作为键：AFI编码的地址，将附加在“地址作为值”中编码的属性，该属性位于该字段后面。
AFI = y: y is the "Address of Value" AFI that can have any value from [AFN]. A specific AFI has its own encoding of either a unicast or a multicast locator address. All RTR/ETR entries for the same level should be combined by a Map-Server to avoid searching through the entire multilevel list of locator entries in a Map-Reply message.
AFI=y:y是“值的地址”AFI，可以具有[AFN]中的任何值。特定的AFI有自己的单播或多播定位地址编码。同一级别的所有RTR/ETR条目应由地图服务器组合，以避免在地图回复消息中搜索整个多级定位器条目列表。
Address as Value: AFI-encoded address that will be the attribute address that goes along with "Address as Key" which precedes this field.
作为值的地址：AFI编码的地址，它将是属性地址，与此字段前面的“作为键的地址”一起使用。
Usage: This is an experimental Type where the usage has not yet been defined.
用法：这是一种尚未定义用法的实验类型。
Overlays are becoming popular in many parts of the network, which has created an explosion of data-plane encapsulation headers. Since the LISP mapping system can hold many types of address formats, it can represent the encapsulation format supported by an RLOC as well. When an encapsulator receives a Map-Reply with an Encapsulation Format LCAF Type encoded in an RLOC-record, it can select an encapsulation format, that it can support, from any of the encapsulation protocols that have the bit set to 1 in this LCAF Type.
覆盖在网络的许多部分变得越来越流行，这导致了数据平面封装头的爆炸。由于LISP映射系统可以保存多种类型的地址格式，因此它也可以表示RLOC支持的封装格式。当封装器接收到带有RLOC记录中编码的封装格式LCAF类型的Map应答时，它可以从该LCAF类型中位设置为1的任何封装协议中选择它可以支持的封装格式。
Encapsulation Format Address Format:
封装格式地址格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 16 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved-for-Future-Encapsulations |U|G|N|v|V|l|L|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 16 | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved-for-Future-Encapsulations |U|G|N|v|V|l|L|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes starting and including the byte after this Length field.
长度：以字节为单位的长度，从该长度字段开始，包括该长度字段后的字节。
Reserved-for-Future-Encapsulations: must be set to zero and ignored on receipt. This field will get bits allocated to future encapsulations, as they are created.
保留用于将来的封装：必须设置为零，并在收到时忽略。此字段将在创建以后的封装时获得分配给它们的位。
U: The RLOCs listed in the AFI-encoded addresses in the next longword can accept Generic UDP Encapsulation (GUE) using destination UDP port 6080 [GUE].
U：下一个长字中AFI编码地址中列出的RLOC可以使用目标UDP端口6080[GUE]接受通用UDP封装（GUE）。
G: The RLOCs listed in the AFI-encoded addresses in the next longword can accept Geneve encapsulation using destination UDP port 6081 [GENEVE].
G：下一个长字中AFI编码地址中列出的RLOC可以使用目标UDP端口6081[Geneve]接受Geneve封装。
N: The RLOCs listed in the AFI-encoded addresses in the next longword can accept NV-GRE (Network Virtualization - Generic Routing Encapsulation) using IPv4/IPv6 protocol number 47 [RFC7637].
N：下一个长单词中AFI编码地址中列出的RLOC可以使用IPv4/IPv6协议编号47[RFC7637]接受NV-GRE（网络虚拟化-通用路由封装）。
v: The RLOCs listed in the AFI-encoded addresses in the next longword can accept VXLAN-GPE (Generic Protocol Extension) encapsulation using destination UDP port 4790 [GPE-VXLAN].
v：下一个长字中AFI编码地址中列出的RLOC可以使用目标UDP端口4790[GPE-VXLAN]接受VXLAN-GPE（通用协议扩展）封装。
V: The RLOCs listed in the AFI-encoded addresses in the next longword can accept Virtual eXtensible Local Area Network (VXLAN) encapsulation using destination UDP port 4789 [RFC7348].
V：下一个长字中AFI编码地址中列出的RLOC可以使用目标UDP端口4789[RFC7348]接受虚拟可扩展局域网（VXLAN）封装。
l: The RLOCs listed in the AFI-encoded addresses in the next longword can accept Layer 2 LISP encapsulation using destination UDP port 8472 [LISP-L2].
l：下一个长字中AFI编码地址中列出的RLOC可以使用目标UDP端口8472[LISP-L2]接受第2层LISP封装。
L: The RLOCs listed in the AFI-encoded addresses in the next longword can accept Layer 3 LISP encapsulation using destination UDP port 4341 [RFC6830].
L：下一个长字中AFI编码地址中列出的RLOC可以使用目标UDP端口4341[RFC6830]接受第3层LISP封装。
Usage: This encoding can be used in RLOC-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages.
用法：此编码可用于映射请求、映射回复、映射寄存器和映射通知消息中的RLOC记录。
This document is classified as Experimental. The LCAF encodings defined in this document are intended to be used with their corresponding use cases and in self-contained environments. Users should carefully consider how the [LISP-SEC] threat model applies to their particular use case.
本文件被归类为实验性文件。本文件中定义的LCAF编码旨在与其相应的用例和自包含环境一起使用。用户应该仔细考虑[LISPSEC]威胁模型如何应用于他们的特定用例。
The use of the Geo-Coordinates LCAF Type may raise physical privacy issues. Care should be taken when configuring the mapping system to use specific policy parameters so geolocation information is not returned gratuitously. It is recommended that any documents that specify the use of the Geo-Coordinates LCAF Type should consider the applicability of RFC 6280 (BCP 160) [RFC6280] for location-based privacy protection.
使用地理坐标LCAF类型可能会引发物理隐私问题。在配置映射系统以使用特定策略参数时，应注意不要无偿返回地理位置信息。建议指定地理坐标LCAF类型的使用的任何文件应考虑RFC 6280（BCP 160）[RFC6280]用于基于位置的隐私保护的适用性。
Additional privacy concerns have arisen since publication of BCP 160, and future work on LISP should examine potential threats beyond BCP 160 and address improving privacy and security for LISP deployments.
自BCP 160发布以来，出现了更多隐私问题，未来关于LISP的工作应检查BCP 160以外的潜在威胁，并解决改善LISP部署的隐私和安全问题。
This document defines a canonical address format encoding used in LISP control messages and in the encoding of lookup keys for the LISP Mapping Database System. Such an address format is based on a fixed AFI (16387) and a LISP LCAF Type field.
本文档定义了LISP控制消息和LISP映射数据库系统的查找键编码中使用的规范地址格式编码。这种地址格式基于固定的AFI（16387）和LISP LCAF类型字段。
The LISP LCAF Type field is an 8-bit field specific to the LISP Canonical Address Format encodings. IANA has created a new registry (as outlined in [RFC5226]) titled "LISP Canonical Address Format (LCAF) Types". Initial values for the "LISP Canonical Address Format (LCAF) Types" registry are given below. Future assignments are to be made using the Specification Required policy [RFC5226]. Assignments consist of a LISP LCAF Type Name and its associated value:
LISP LCAF类型字段是特定于LISP规范地址格式编码的8位字段。IANA创建了一个名为“LISP规范地址格式（LCAF）类型”的新注册表（如[RFC5226]中所述）。下面给出了“LISP规范地址格式（LCAF）类型”注册表的初始值。未来的分配将使用规范要求的政策[RFC5226]进行。指定由LISP LCAF类型名称及其关联值组成：
+-------+------------------------+-----------+
| Value | LISP LCAF Type Name | Reference |
+-------+------------------------+-----------+
| 0 | Null Body | Section 3 |
| 1 | AFI List | Section 3 |
| 2 | Instance ID | Section 3 |
| 3 | AS Number | Section 3 |
| 5 | Geo-Coordinates | Section 3 |
| 7 | NAT-Traversal | Section 3 |
| 9 | Multicast Info | Section 3 |
| 10 | Explicit Locator Path | Section 3 |
| 11 | Security Key | Section 3 |
| 12 | Source/Dest Key | Section 3 |
| 13 | Replication List Entry | Section 3 |
+-------+------------------------+-----------+
+-------+------------------------+-----------+
| Value | LISP LCAF Type Name | Reference |
+-------+------------------------+-----------+
| 0 | Null Body | Section 3 |
| 1 | AFI List | Section 3 |
| 2 | Instance ID | Section 3 |
| 3 | AS Number | Section 3 |
| 5 | Geo-Coordinates | Section 3 |
| 7 | NAT-Traversal | Section 3 |
| 9 | Multicast Info | Section 3 |
| 10 | Explicit Locator Path | Section 3 |
| 11 | Security Key | Section 3 |
| 12 | Source/Dest Key | Section 3 |
| 13 | Replication List Entry | Section 3 |
+-------+------------------------+-----------+
Table 1: Initial Values in the "LISP Canonical Address Format (LCAF) Types" Registry
表1：“LISP规范地址格式（LCAF）类型”注册表中的初始值
[RFC1035] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, November 1987, <http://www.rfc-editor.org/info/rfc1035>.
[RFC1035]Mockapetris，P.，“域名-实现和规范”，STD 13，RFC 1035，DOI 10.17487/RFC1035，1987年11月<http://www.rfc-editor.org/info/rfc1035>.
[RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., and E. Lear, "Address Allocation for Private Internets", BCP 5, RFC 1918, DOI 10.17487/RFC1918, February 1996, <http://www.rfc-editor.org/info/rfc1918>.
[RFC1918]Rekhter，Y.，Moskowitz，B.，Karrenberg，D.，de Groot，G.，和E.Lear，“私人互联网地址分配”，BCP 5，RFC 1918，DOI 10.17487/RFC1918，1996年2月<http://www.rfc-editor.org/info/rfc1918>.
[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>.
[RFC3232] Reynolds, J., Ed., "Assigned Numbers: RFC 1700 is Replaced by an On-line Database", RFC 3232, DOI 10.17487/RFC3232, January 2002, <http://www.rfc-editor.org/info/rfc3232>.
[RFC3232]Reynolds，J.，Ed.，“分配号码：RFC 1700被在线数据库取代”，RFC 3232，DOI 10.17487/RFC3232，2002年1月<http://www.rfc-editor.org/info/rfc3232>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, DOI 10.17487/RFC3986, January 2005, <http://www.rfc-editor.org/info/rfc3986>.
[RFC3986]Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，STD 66，RFC 3986，DOI 10.17487/RFC3986，2005年1月<http://www.rfc-editor.org/info/rfc3986>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, DOI 10.17487/RFC5226, May 2008, <http://www.rfc-editor.org/info/rfc5226>.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，DOI 10.17487/RFC5226，2008年5月<http://www.rfc-editor.org/info/rfc5226>.
[RFC6280] Barnes, R., Lepinski, M., Cooper, A., Morris, J., Tschofenig, H., and H. Schulzrinne, "An Architecture for Location and Location Privacy in Internet Applications", BCP 160, RFC 6280, DOI 10.17487/RFC6280, July 2011, <http://www.rfc-editor.org/info/rfc6280>.
[RFC6280]Barnes，R.，Lepinski，M.，Cooper，A.，Morris，J.，Tschofenig，H.，和H.Schulzrinne，“互联网应用中的位置和位置隐私架构”，BCP 160，RFC 6280，DOI 10.17487/RFC6280，2011年7月<http://www.rfc-editor.org/info/rfc6280>.
[RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The Locator/ID Separation Protocol (LISP)", RFC 6830, DOI 10.17487/RFC6830, January 2013, <http://www.rfc-editor.org/info/rfc6830>.
[RFC6830]Farinaci，D.，Fuller，V.，Meyer，D.，和D.Lewis，“定位器/身份分离协议（LISP）”，RFC 6830，DOI 10.17487/RFC6830，2013年1月<http://www.rfc-editor.org/info/rfc6830>.
[RFC6836] Fuller, V., Farinacci, D., Meyer, D., and D. Lewis, "Locator/ID Separation Protocol Alternative Logical Topology (LISP+ALT)", RFC 6836, DOI 10.17487/RFC6836, January 2013, <http://www.rfc-editor.org/info/rfc6836>.
[RFC6836]Fuller，V.，Farinaci，D.，Meyer，D.，和D.Lewis，“定位器/ID分离协议替代逻辑拓扑（LISP+ALT）”，RFC 6836，DOI 10.17487/RFC6836，2013年1月<http://www.rfc-editor.org/info/rfc6836>.
[RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March 2014, <http://www.rfc-editor.org/info/rfc7159>.
[RFC7159]Bray，T.，Ed.“JavaScript对象表示法（JSON）数据交换格式”，RFC 7159，DOI 10.17487/RFC7159，2014年3月<http://www.rfc-editor.org/info/rfc7159>.
[RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger, L., Sridhar, T., Bursell, M., and C. Wright, "Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks", RFC 7348, DOI 10.17487/RFC7348, August 2014, <http://www.rfc-editor.org/info/rfc7348>.
[RFC7348]Mahalingam，M.，Dutt，D.，Duda，K.，Agarwal，P.，Kreeger，L.，Sridhar，T.，Bursell，M.，和C.Wright，“虚拟可扩展局域网（VXLAN）：在第3层网络上覆盖虚拟化第2层网络的框架”，RFC 7348，DOI 10.17487/RFC7348，2014年8月<http://www.rfc-editor.org/info/rfc7348>.
[RFC7637] Garg, P., Ed. and Y. Wang, Ed., "NVGRE: Network Virtualization Using Generic Routing Encapsulation", RFC 7637, DOI 10.17487/RFC7637, September 2015, <http://www.rfc-editor.org/info/rfc7637>.
[RFC7637]Garg，P.，Ed.和Y.Wang，Ed.，“NVGRE：使用通用路由封装的网络虚拟化”，RFC 7637，DOI 10.17487/RFC7637，2015年9月<http://www.rfc-editor.org/info/rfc7637>.
[AFN] IANA, "Address Family Numbers", <http://www.iana.org/assignments/address-family-numbers/>.
[AFN]IANA，“地址家庭编号”<http://www.iana.org/assignments/address-family-numbers/>.
[EID-MOBILITY] Portoles-Comeras, M., Ashtaputre, V., Moreno, V., Maino, F., and D. Farinacci, "LISP L2/L3 EID Mobility Using a Unified Control Plane", Work in Progress, draft-portoles-lisp-eid-mobility-01, October 2016.
[EID-MOBILITY]Portoles Comeras，M.，Ashtaputre，V.，Moreno，V.，Maino，F.，和D.Farinaci，“使用统一控制平面的LISP L2/L3 EID移动”，正在进行的工作，草稿-Portoles-LISP-EID-MOBILITY-01，2016年10月。
[GENEVE] Gross, J., Ganga, I., and T. Sridhar, "Geneve: Generic Network Virtualization Encapsulation", Work in Progress, draft-ietf-nvo3-geneve-03, September 2016.
[GENEVE]Gross，J.，Ganga，I.，和T.Sridhar，“GENEVE：通用网络虚拟化封装”，正在进行的工作，草稿-ietf-nvo3-GENEVE-032016年9月。
[GPE-VXLAN] Maino, F., Kreeger, L., and U. Elzur, "Generic Protocol Extension for VXLAN", Work in Progress, draft-ietf-nvo3-vxlan-gpe-03, October 2016.
[GPE-VXLAN]Maino，F.，Kreeger，L.，和U.Elzur，“VXLAN的通用协议扩展”，正在进行的工作，草案-ietf-nvo3-VXLAN-GPE-032016年10月。
[GUE] Herbert, T., Yong, L., and O. Zia, "Generic UDP Encapsulation", Work in Progress, draft-ietf-nvo3-gue-05, October 2016.
[GUE]Herbert，T.，Yong，L.和O.Zia，“通用UDP封装”，正在进行的工作，草案-ietf-nvo3-GUE-052016年10月。
[JSON-BINARY] "Universal Binary JSON Specification", <http://ubjson.org>.
[JSON-BINARY]“通用二进制JSON规范”<http://ubjson.org>.
[LISP-DDT] Fuller, V., Lewis, D., Ermagan, V., Jain, A., and A. Smirnov, "LISP Delegated Database Tree", Work in Progress, draft-ietf-lisp-ddt-09, January 2017.
[LISP-DDT]Fuller，V.，Lewis，D.，Ermagan，V.，Jain，A.，和A.Smirnov，“LISP委托数据库树”，正在进行的工作，草案-ietf-LISP-DDT-092017年1月。
[LISP-L2] Smith, M., Dutt, D., Farinacci, D., and F. Maino, "Layer 2 (L2) LISP Encapsulation Format", Work in Progress, draft-smith-lisp-layer2-03, September 2013.
[LISP-L2]Smith，M.，Dutt，D.，Farinaci，D.，和F.Maino，“第2（L2）层LISP封装格式”，正在进行的工作，草稿-Smith-LISP-layer2-032013年9月。
[LISP-RE] Coras, F., Cabellos-Aparicio, A., Domingo-Pascual, J., Maino, F., and D. Farinacci, "LISP Replication Engineering", Work in Progress, draft-coras-lisp-re-08, November 2015.
[LISP-RE]Coras，F.，Cabellos Aparicio，A.，Domingo Pascual，J.，Maino，F.，和D.Farinaci，“LISP复制工程”，在建工程，草稿-Coras-LISP-RE-082015年11月。
[LISP-SEC] Maino, F., Ermagan, V., Cabellos, A., and D. Saucez, "LISP-Security (LISP-SEC)", Work in Progress, draft-ietf-lisp-sec-12, November 2016.
[LISP-SEC]Maino，F.，Ermagan，V.，Cabellos，A.，和D.Saucez，“LISP安全（LISP-SEC）”，正在进行的工作，草案-ietf-LISP-SEC-12，2016年11月。
[LISP-TE] Farinacci, D., Kowal, M., and P. Lahiri, "LISP Traffic Engineering Use-Cases", Work in Progress, draft-farinacci-lisp-te-11, September 2016.
[LISP-TE]Farinaci，D.，Kowal，M.，和P.Lahiri，“LISP交通工程用例”，在建工程，草稿-Farinaci-LISP-TE-112016年9月。
[NAT-LISP] Ermagan, V., Farinacci, D., Lewis, D., Skriver, J., Maino, F., and C. White, "NAT traversal for LISP", Work in Progress, draft-ermagan-lisp-nat-traversal-11, August 2016.
[NAT-LISP]Ermagan，V.，Farinaci，D.，Lewis，D.，Skriver，J.，Maino，F.，和C.White，“LISP的NAT遍历”，正在进行的工作，草稿-Ermagan-LISP-NAT-traversal-112016年8月。
[RFC8061] Farinacci, D. and B. Weis, "Locator/ID Separation Protocol (LISP) Data-Plane Confidentiality", RFC 8061, DOI 10.17487/RFC8061, February 2017, <http://www.rfc-editor.org/info/rfc8061>.
[RFC8061]Farinaci，D.和B.Weis，“定位器/ID分离协议（LISP）数据平面机密性”，RFC 8061，DOI 10.17487/RFC8061，2017年2月<http://www.rfc-editor.org/info/rfc8061>.
[WGS-84] National Imagery and Mapping Agency, "Department of Defense World Geodetic System 1984", NIMA TR8350.2, January 2000, <http://earth-info.nga.mil/GandG/ publications/tr8350.2/wgs84fin.pdf>.
[WGS-84]国家图像和测绘局，“1984年国防部世界大地测量系统”，NIMA TR8350.22000年1月<http://earth-info.nga.mil/GandG/ 出版物/tr8350.2/wgs84fin.pdf>。
Acknowledgments
致谢
The authors would like to thank Vince Fuller, Gregg Schudel, Jesper Skriver, Luigi Iannone, Isidor Kouvelas, and Sander Steffann for their technical and editorial commentary.
作者要感谢文斯·富勒、格雷格·舒德尔、杰斯珀·斯克里弗、路易吉·伊安诺、伊西多·库韦拉斯和桑德·斯特凡的技术和编辑评论。
The authors would like to thank Victor Moreno for discussions that led to the definition of the Multicast Info LCAF Type.
作者要感谢Victor Moreno的讨论，这些讨论导致了多播信息LCAF类型的定义。
The authors would like to thank Parantap Lahiri and Michael Kowal for discussions that led to the definition of the Explicit Locator Path (ELP) LCAF Type.
作者要感谢Parantap Lahiri和Michael Kowal的讨论，这些讨论导致了显式定位器路径（ELP）LCAF类型的定义。
The authors would like to thank Fabio Maino and Vina Ermagan for discussions that led to the definition of the Security Key LCAF Type.
作者要感谢Fabio Maino和Vina Ermagan的讨论，讨论得出了安全密钥LCAF类型的定义。
The authors would like to thank Albert Cabellos-Aparicio and Florin Coras for discussions that led to the definition of the Replication List Entry LCAF Type.
作者要感谢Albert Cabellos Aparicio和Florin Coras的讨论，讨论导致了复制列表条目LCAF类型的定义。
Thanks goes to Michiel Blokzijl and Alberto Rodriguez-Natal for suggesting new LCAF Types.
感谢Michiel Blokzijl和Alberto Rodriguez Natal提出新的LCAF类型。
Thanks also goes to Terry Manderson for assistance obtaining a LISP AFI value from IANA.
还感谢Terry Manderson帮助从IANA获得LISP AFI值。
And finally, the authors thank Stephen Farrell (Security Area Director) and Deborah Brungard (Routing Area Director) for their suggested text to get the document through IESG review.
最后，作者感谢Stephen Farrell（安全区域主管）和Deborah Brungard（路由区域主管）提出的通过IESG审查获得文件的建议文本。
Authors' Addresses
作者地址
Dino Farinacci lispers.net San Jose, CA United States of America
美国加利福尼亚州圣何塞Dino Farinaci lispers.net
Email: farinacci@gmail.com
Email: farinacci@gmail.com
Dave Meyer Brocade San Jose, CA United States of America
Dave Meyer Brocade美国加利福尼亚州圣何塞市
Email: dmm@1-4-5.net
Email: dmm@1-4-5.net
Job Snijders NTT Communications Theodorus Majofskistraat 100 Amsterdam 1065 SZ The Netherlands
Job Snijders NTT Communications Theodorus Majofskistraat 100阿姆斯特丹1065 SZ荷兰
Email: job@ntt.net
Email: job@ntt.net