Internet Engineering Task Force (IETF) T. Manderson
Request for Comments: 6397 ICANN
Category: Standards Track October 2011
ISSN: 2070-1721
Internet Engineering Task Force (IETF) T. Manderson
Request for Comments: 6397 ICANN
Category: Standards Track October 2011
ISSN: 2070-1721
Multi-Threaded Routing Toolkit (MRT) Border Gateway Protocol (BGP) Routing Information Export Format with Geo-Location Extensions
带地理位置扩展的多线程路由工具包（MRT）边界网关协议（BGP）路由信息导出格式
Abstract
摘要
This document updates the Multi-threaded Routing Toolkit (MRT) export format for Border Gateway Protocol (BGP) routing information by extending it to include optional terrestrial coordinates of a BGP collector and its BGP peers.
本文档更新了边界网关协议（BGP）路由信息的多线程路由工具包（MRT）导出格式，将其扩展为包含BGP收集器及其BGP对等点的可选地面坐标。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6397.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6397.
Copyright Notice
版权公告
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2011 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Notation . . . . . . . . . . . . . . . . . . . . . 2
3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Geo-Location-Aware MRT Routing Information Subtype . . . . . . 3
4.1. GEO_PEER_TABLE . . . . . . . . . . . . . . . . . . . . . . 3
4.2. GEO_PEER_TABLE and Peer Entry Values . . . . . . . . . . . 5
5. BGP Collector Construction . . . . . . . . . . . . . . . . . . 5
6. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 6
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
9. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
10.1. Normative References . . . . . . . . . . . . . . . . . . . 7
10.2. Informative References . . . . . . . . . . . . . . . . . . 8
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Notation . . . . . . . . . . . . . . . . . . . . . 2
3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Geo-Location-Aware MRT Routing Information Subtype . . . . . . 3
4.1. GEO_PEER_TABLE . . . . . . . . . . . . . . . . . . . . . . 3
4.2. GEO_PEER_TABLE and Peer Entry Values . . . . . . . . . . . 5
5. BGP Collector Construction . . . . . . . . . . . . . . . . . . 5
6. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 6
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
9. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
10.1. Normative References . . . . . . . . . . . . . . . . . . . 7
10.2. Informative References . . . . . . . . . . . . . . . . . . 8
Researchers and engineers often wish to analyze network behavior by studying routing protocol transactions and routing information base snapshots in relation to geographical topologies. Usually, the Border Gateway Protocol [RFC4271] is the subject of study, and the analysis can be significantly aided by the availability and extension of the "Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format" [RFC6396]. The MRT format was originally defined in the MRT Programmer's Guide [MRT-GUIDE].
研究人员和工程师通常希望通过研究与地理拓扑相关的路由协议事务和路由信息库快照来分析网络行为。通常，边界网关协议[RFC4271]是研究的主题，而“多线程路由工具包（MRT）路由信息导出格式”[RFC6396]的可用性和扩展性可以极大地帮助分析。MRT格式最初在MRT程序员指南[MRT-Guide]中定义。
The addition of geo-location coordinates (longitude and latitude) pertaining to the geographical location of both the BGP collector and its BGP peers to BGP export data enables a researcher or enquiring individual to gain a terrestrial insight to the routes seen by a BGP speaker. Such data may ultimately aid researchers in understanding any disparity between the geographical location of networks and the topological location of networks in addition to the relationships between geographical position and routing anomalies. Such insight could provide future input into network design and network security.
将与BGP采集器及其BGP对等点的地理位置相关的地理位置坐标（经度和纬度）添加到BGP导出数据中，使研究人员或查询人员能够获得对BGP演讲者看到的路线的地面洞察。除了地理位置和路由异常之间的关系外，这些数据最终可能有助于研究人员理解网络地理位置和网络拓扑位置之间的任何差异。这种洞察可以为网络设计和网络安全提供未来的投入。
This memo documents an optional extension to the MRT format [RFC6396] and introduces an additional definition of an MRT Subtype field that includes the terrestrial coordinates of a BGP collector and its BGP peers.
本备忘录记录了MRT格式[RFC6396]的可选扩展，并介绍了MRT子类型字段的附加定义，其中包括BGP收集器及其BGP对等点的地面坐标。
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]中所述进行解释。
Coordinates: The geographic latitude and longitude specifying a location on the earth.
坐标：指定地球位置的地理纬度和经度。
BGP Speaker: A network device that exchanges network routing information using BGP.
BGP扬声器：使用BGP交换网络路由信息的网络设备。
Geo-location: Assigning a set of coordinates to a specific artifact, in this case a BGP speaker.
地理位置：为特定工件指定一组坐标，在本例中为BGP扬声器。
BGP Collector: A BGP speaker (usually passive) that stores and archives BGP routing data from active BGP peers for analysis.
BGP采集器：一种BGP扬声器（通常为无源），用于存储和归档来自活动BGP对等点的BGP路由数据，以供分析。
BGP Peer: Either an internal or external BGP peer [RFC4271].
BGP对等：内部或外部BGP对等[RFC4271]。
Not A Number (NAN): Numeric data type representing an undefined or unrepresentable value, as defined in the IEEE Standard for Floating-Point Arithmetic [IEEE754].
非数字（NAN）：表示未定义或不可表示值的数字数据类型，如IEEE浮点运算标准[IEEE754]中所定义。
An additional subtype (GEO_PEER_TABLE) is defined for the TABLE_DUMP_V2 format, extending TABLE_DUMP_V2 Type.
为TABLE_DUMP_V2格式定义了一个附加子类型（GEO_PEER_TABLE），扩展了TABLE_DUMP_V2类型。
The GEO_PEER_TABLE Subtype updates the TABLE_DUMP_V2 Types to include geo-location information in the form of the World Geodetic System 1984 (WGS84) [WGS-84] formatted coordinates.
GEO_PEER_TABLE子类型更新TABLE_DUMP_V2类型，以包含1984年世界大地测量系统（WGS84）[WGS-84]格式坐标形式的地理位置信息。
The document adds the 7th subtype number and name below. The first 6 subtypes are defined by the MRT format [RFC6396].
文档在下面添加了第7个子类型编号和名称。前6个子类型由MRT格式[RFC6396]定义。
Subtype Number Subtype Name
----------------------------------
7 GEO_PEER_TABLE
Subtype Number Subtype Name
----------------------------------
7 GEO_PEER_TABLE
The GEO_PEER_TABLE MRT record provides the BGP ID of the collector, its latitude and longitude in WGS84 [WGS-84] format, and a list of indexed peers and their respective latitudes and longitudes in WGS84 [WGS-84] format.
GEO_PEER_表MRT记录提供收集器的BGP ID、WGS84[WGS-84]格式的纬度和经度，以及WGS84[WGS-84]格式的索引对等点列表及其各自的纬度和经度。
The format and function of the Collector BGP ID and Peer Count are as defined by the TABLE_DUMP_V2, PEER_INDEX_TABLE format [RFC6396].
收集器BGP ID和对等计数的格式和功能由表\u DUMP\u V2、对等索引\u表格式[RFC6396]定义。
The Collector Latitude and Collector Longitude are the geographical coordinates of the collector in WGS84 [WGS-84] datum decimal degrees format stored as a single precision float in the 32 bits allocated to the Collector Latitude and Collector Longitude. The latitude and longitude MAY be a Not A Number (NAN) [IEEE754] for situations where the geo-location of the collector is considered private. The Collector Latitude and Collector Longitude MUST NOT be a mix of WGS84 [WGS-84] datum coordinates and NAN values.
采集器纬度和采集器经度是采集器的地理坐标，采用WGS84[WGS-84]基准十进制度数格式，作为单个精度浮点存储在分配给采集器纬度和采集器经度的32位中。对于收集器的地理位置被认为是私有的情况，纬度和经度可以是非数字（NAN）[IEEE754]。收集器纬度和收集器经度不得混合使用WGS84[WGS-84]基准坐标和NAN值。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Collector BGP ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Collector Latitude |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Collector Longitude |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Count | Peer Entries (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Collector BGP ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Collector Latitude |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Collector Longitude |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Count | Peer Entries (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Format of the GEO_PEER_TABLE
GEO_PEER_表的格式
The format of the Peer Entries is shown below. The Peer Type and the Peer BGP ID are as defined in the TABLE_DUMP_V2 MRT, PEER_INDEX_TABLE format [RFC6396]. The order of the Peer Entries in the GEO_PEER_TABLE MUST match the order and number as existing in the PEER_INDEX_TABLE.
对等条目的格式如下所示。对等类型和对等BGP ID在表\u DUMP\u V2 MRT、对等索引\u表格式[RFC6396]中定义。GEO_Peer_表中对等项的顺序必须与Peer_INDEX_表中现有的顺序和编号相匹配。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer BGP ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Latitude |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Longitude |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer BGP ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Latitude |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Longitude |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Format of Peer Entries
对等条目的格式
The Peer Latitude and Peer Longitude are the geographical coordinates of the peer in WGS84 [WGS-84] datum decimal degrees format stored as a single precision float in the 32 bits allocated to the Peer Latitude and Peer Longitude. The latitude and longitude MAY be a Not A Number (NAN) [IEEE754] for situations where the geo-location of the
对等纬度和对等经度是以WGS84[WGS-84]基准十进制度数格式存储的对等地理坐标，以单个精度浮点形式存储在分配给对等纬度和对等经度的32位中。纬度和经度可能是一个非数字（NAN）[IEEE754]，用于以下情况：
peer is considered private. The Peer Latitude and Peer Longitude MUST NOT be a mix of WGS84 [WGS-84] datum coordinates and NAN values for a single peer.
同伴被认为是私人的。对等纬度和对等经度不得是单个对等点的WGS84[WGS-84]基准坐标和NAN值的混合。
Collector BGP ID: Defined in the MRT format [RFC6396].
收集器BGP ID：以MRT格式[RFC6396]定义。
Collector Latitude: Geographic latitude of the BGP collector in WGS84 [WGS-84] datum decimal degrees format stored as a single precision float.
采集器纬度：BGP采集器的地理纬度，采用WGS84[WGS-84]基准十进制度数格式，存储为单精度浮点。
Collector Longitude: Geographic longitude of the BGP collector in WGS84 [WGS-84] datum decimal degrees format stored as a single precision float.
收集器经度：BGP收集器的地理经度，采用WGS84[WGS-84]基准十进制度数格式，存储为单精度浮点。
Peer Count: Defined in the MRT format [RFC6396].
对等计数：以MRT格式[RFC6396]定义。
Peer Entries: Defined in the MRT format [RFC6396].
对等条目：以MRT格式[RFC6396]定义。
Peer Type: Defined in the MRT format [RFC6396].
对等类型：以MRT格式[RFC6396]定义。
Peer BGP ID: Defined in the MRT format [RFC6396].
对等BGP ID：以MRT格式[RFC6396]定义。
Peer Latitude: Geographic latitude of the BGP peer in WGS84 [WGS-84] datum decimal degrees format stored as a single precision float.
对等纬度：以WGS84[WGS-84]基准十进制度数格式存储为单个精度浮点的BGP对等地理纬度。
Peer Longitude: Geographic longitude of the BGP peer in WGS84 [WGS-84] datum decimal degrees format stored as a single precision float.
对等经度：以WGS84[WGS-84]基准十进制度数格式存储为单精度浮点的BGP对等的地理经度。
This section aids the reader in understanding the function of a BGP collector.
本节帮助读者理解BGP采集器的功能。
The BGP collector is a hardware- or software-based device that speaks the Border Gateway Protocol. Its intended function is to store (and archive) the BGP routing data it receives from other BGP speakers with which it has peering relationships, providing data for later analysis. The general nature of a BGP collector is that it is a passive device in that it listens to route updates and does not announce or propagate any information it knows or receives. It should be noted that this is not always the case; network operators sometimes enable the collection of BGP routing data on active BGP speakers to obtain a situational view of the routing system as they see it at a particular point in time.
BGP收集器是一种基于硬件或软件的设备，使用边界网关协议。其预期功能是存储（和归档）从其他BGP扬声器接收的BGP路由数据，并与之建立对等关系，为以后的分析提供数据。BGP采集器的一般性质是，它是一个被动设备，因为它侦听路由更新，不宣布或传播它知道或接收的任何信息。应该指出的是，情况并非总是如此；网络运营商有时能够在活动BGP扬声器上收集BGP路由数据，以获得他们在特定时间点看到的路由系统的情景视图。
As a fully fledged BGP speaker, the BGP collector can fit into any BGP topology including Internal BGP (iBGP), External BGP (eBGP), and so on. The implementation of a BGP collector in a network topology is therefore limited by that network's use of BGP.
作为一个成熟的BGP扬声器，BGP采集器可以适应任何BGP拓扑，包括内部BGP（iBGP）、外部BGP（eBGP）等。因此，网络拓扑中BGP收集器的实现受到该网络使用BGP的限制。
The GEOPRIV [RFC6280] architecture requires that privacy rules attached to a location object be transmitted alongside the location information in the object. If a BGP collector adds location coordinates to an MRT record based on GEOPRIV location objects, then it would have to include privacy rules as well. Since the MRT geo-location format does not support the provision of privacy rules, each location entry in an MRT object is assigned the following default privacy rules [RFC4119]:
GEOPRIV[RFC6280]体系结构要求附加到位置对象的隐私规则与对象中的位置信息一起传输。如果BGP收集器根据GEOPRIV位置对象将位置坐标添加到MRT记录中，那么它还必须包括隐私规则。由于MRT地理位置格式不支持提供隐私规则，因此MRT对象中的每个位置条目都被分配以下默认隐私规则[RFC4119]：
-- retransmission-allowed: True
-- retention-expires: 100 years from timestamp of the MRT object
-- ruleset-reference: Empty
-- note-well: Empty
-- retransmission-allowed: True
-- retention-expires: 100 years from timestamp of the MRT object
-- ruleset-reference: Empty
-- note-well: Empty
Location information derived from a location object with more restrictive privacy rules MUST NOT be included in an MRT geo-location record unless there are non-technical measures in place that enforce and communicate the constraints on the use of the location information in the MRT geo-location format (e.g., contractual agreements between peers).
从具有更严格隐私规则的位置对象派生的位置信息不得包含在MRT地理位置记录中，除非有非技术性措施实施并传达对使用MRT地理位置格式的位置信息的限制（例如，对等方之间的合同协议）。
Thanks to Andrew Clark, Ernest Foo, Dave Meyer, Larry Blunk, Richard Barnes, and Jeffrey Haas for reviewing this document.
感谢Andrew Clark、Ernest Foo、Dave Meyer、Larry Blunk、Richard Barnes和Jeffrey Haas审阅本文档。
This document describes a small portion of the research towards the author's Ph.D.
本文件描述了作者博士研究的一小部分。
Per this section, the Internet Assigned Numbers Authority (IANA) has registered the additional Subtype code value as:
根据本节，互联网分配号码管理局（IANA）已将附加子类型代码值注册为：
7 GEO_PEER_TABLE
7 GEO_PEER_表
in the MRT format [RFC6396] and Subtype code values related to the TABLE_DUMP_V2 Type in the MRT namespace.
在MRT格式[RFC6396]中，与MRT命名空间中的表\u DUMP\u V2类型相关的子类型代码值。
This extension to the MRT format [RFC6396] defines fields that are of a descriptive nature and provides information that is useful in the analysis of routing systems. As such, the author believes that they do not constitute an additional network-based security risk. It is recommended that the operators of the BGP collector and BGP peers consider their own privacy and security concerns before supplying geographical coordinates to BGP data collection systems. Special attention should be given to the physical security of an organization before supplying geographical coordinates, especially if the resulting BGP data with geo-location extensions is made public.
MRT格式[RFC6396]的扩展定义了具有描述性的字段，并提供了在路由系统分析中有用的信息。因此，作者认为，它们并不构成额外的基于网络的安全风险。建议BGP收集器和BGP对等体的运营商在向BGP数据收集系统提供地理坐标之前考虑它们自己的隐私和安全问题。在提供地理坐标之前，应特别注意组织的物理安全，尤其是当带有地理位置扩展的BGP数据公开时。
Entities that operate BGP collectors, and users of data provided by BGP collectors, should be aware that the geo-location data supplied by a peer can only be taken at face value. It is possible that a BGP peer may supply coordinates that are purposefully misleading or inaccurate. It is therefore up to the BGP collector whether or not to include this information or use its own methods to either trust or validate the data provided. It is not recommended that a BGP collector use geographical coordinates not supplied by a BGP peer.
运营BGP采集器的实体以及BGP采集器提供的数据的用户应该知道，对等方提供的地理位置数据只能按面值获取。BGP对等方可能提供故意误导或不准确的坐标。因此，由BGP收集器决定是否包含此信息或使用其自己的方法信任或验证提供的数据。不建议BGP收集器使用BGP对等方未提供的地理坐标。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object Format", RFC 4119, December 2005.
[RFC4119]Peterson，J.，“一种基于状态的GEOPRIV定位对象格式”，RFC41192005年12月。
[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, January 2006.
[RFC4271]Rekhter，Y.，Li，T.，和S.Hares，“边境网关协议4（BGP-4）”，RFC 42712006年1月。
[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, July 2011.
[RFC6280]Barnes，R.，Lepinski，M.，Cooper，A.，Morris，J.，Tschofenig，H.，和H.Schulzrinne，“互联网应用中的位置和位置隐私架构”，BCP 160，RFC 62802011年7月。
[RFC6396] Blunk, L., Karir, M., and C. Labovitz, "Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format", RFC 6396, October 2011.
[RFC6396]Blunk，L.，Karir，M.，和C.Labovitz，“多线程路由工具包（MRT）路由信息导出格式”，RFC 63962011年10月。
[IEEE754] IEEE 754, "IEEE Standard for Floating-Point Arithmetic", August 2008, <http://ieeexplore.ieee.org/servlet/ opac?punumber=4610933>.
[IEEE754]IEEE 754，“IEEE浮点运算标准”，2008年8月<http://ieeexplore.ieee.org/servlet/ opac？punumber=4610933>。
[MRT-GUIDE] Labovitz, C., "MRT Programmer's Guide", November 1999, <http://www.merit.edu/networkresearch/ mrtprogrammer.pdf>.
[MRT-GUIDE]拉博维茨，C.，“MRT程序员指南”，1999年11月<http://www.merit.edu/networkresearch/ mrtprogrammer.pdf>。
[WGS-84] Geodesy and Geophysics Department, DoD., "World Geodetic System 1984", January 2000, <http://earth-info.nga.mil/ GandG/publications/tr8350.2/wgs84fin.pdf>.
[WGS-84]美国国防部大地测量和地球物理部，“1984年世界大地测量系统”，2000年1月<http://earth-info.nga.mil/ GandG/publications/tr8350.2/wgs84fin.pdf>。
Author's Address
作者地址
Terry Manderson ICANN
特里·曼德森
EMail: terry.manderson@icann.org
EMail: terry.manderson@icann.org