idnits 2.17.1 draft-ietf-grow-geomrt-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (December 14, 2010) is 4882 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC4271' is defined on line 197, but no explicit reference was found in the text == Unused Reference: 'RFC4760' is defined on line 200, but no explicit reference was found in the text == Outdated reference: A later version (-17) exists of draft-ietf-grow-mrt-13 ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Global Routing Operations Working T. Manderson 3 Group ICANN 4 Internet-Draft December 14, 2010 5 Intended status: Informational 6 Expires: June 17, 2011 8 MRT BGP routing information export format with geo-location extensions 9 draft-ietf-grow-geomrt-01.txt 11 Abstract 13 This document extends the Border Gateway Protocol (BGP) MRT export 14 format for routing information to include terrestrial coordinates. 16 Status of this Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on June 17, 2011. 33 Copyright Notice 35 Copyright (c) 2010 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 51 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 52 3. Geo-location aware MRT Routing Information Subtype . . . . . . 5 53 3.1. GEO_PEER_TABLE . . . . . . . . . . . . . . . . . . . . . . 5 54 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 55 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 56 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 57 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 58 7.1. Normative References . . . . . . . . . . . . . . . . . . . 10 59 7.2. Informative References . . . . . . . . . . . . . . . . . . 10 60 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 11 62 1. Requirements notation 64 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 65 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 66 document are to be interpreted as described in [RFC2119]. 68 2. Introduction 70 Research is underway that analyzes the network behavior of routing 71 protocol transactions from routing information base snapshots in 72 relation to geographical coordinates. Specifically the BGP routing 73 protocol is the subject of study and the analysis has been 74 significantly aided by the availability and extension of the "MRT 75 format" [I-D.ietf-grow-mrt] originally defined in the MRT 76 Programmer's Guide [MRT PROG GUIDE]. 78 This memo documents an extension to the "MRT format" 79 [I-D.ietf-grow-mrt] and introduces an additional definition of a MRT 80 Subtype field. 82 3. Geo-location aware MRT Routing Information Subtype 84 The additional Subtype is defined for the TABLE_DUMP_v format, which 85 extends the TABLE_DUMP_V2 type. 87 3.1. GEO_PEER_TABLE 89 The GEO_PEER_TABLE Subtype updates the TABLE_DUMP_v2 Types to include 90 Geo-location information in the form of WGS84 [WGS 84] formatted 91 coordinates. The MRT subtypes would be as follows. 93 1 PEER_INDEX_TABLE 94 2 RIB_IPV4_UNICAST 95 3 RIB_IPV4_MULTICAST 96 4 RIB_IPV6_UNICAST 97 5 RIB_IPV6_MULTICAST 98 6 RIB_GENERIC 99 7 GEO_PEER_TABLE 101 The GEO_PEER_TABLE MRT record provides the BGP ID of the collector, 102 Its latitude and longitude in WGS84 [WGS 84] format, and a list of 103 indexed peers. 105 The format and function of the Collector BGP ID, Peer Count are as 106 defined by the TABLE_DUMP_V2 MRT PEER_INDEX_TABLE format. 107 [I-D.ietf-grow-mrt]. 109 The Collector Latitude and Collector Longitude are the geographical 110 coordinates of the collector in WGS84 [WGS 84] datum decimal degrees 111 format stored as a single precision float in the 32 bits allocated to 112 the Collector Latitude and Collector Longitude. The latitude and 113 longitude may be a Not A Number (NAN) for situations where the geo- 114 location of the collector is considered private. The Collector 115 Latitude and Collector Longitude MUST NOT be a mix of WGS84 [WGS 84] 116 datum coordinate and NAN values. 118 0 1 2 3 119 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 120 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 121 | Collector BGP ID | 122 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 123 | Collector Latitude | 124 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 125 | Collector Longitude | 126 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 127 | Peer Count | Peer entries (variable) 128 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 129 The format of the peer entries is shown below. The Peer Type and the 130 Peer BGP ID is as defined in the TABLE_DUMP_V2 MRT 131 [I-D.ietf-grow-mrt] PEER_INDEX_TABLE format. The order of the Peer 132 entries in GEO_PEER_TABLE MUST match the order and number as existing 133 in the PEER_INDEX_TABLE. 135 0 1 2 3 136 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 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 | Peer Type | 139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 140 | Peer BGP ID | 141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 142 | Peer Latitude | 143 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 144 | Peer Longitude | 145 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 147 The Peer Latitude and Peer Longitude are the geographical coordinates 148 of the peer in WGS84 [WGS 84] datum decimal degrees format stored as 149 a single precision float in the 32 bits allocated to the Peer 150 Latitude and Peer Longitude. The latitude and longitude may be a Not 151 A Number (NAN) for situations where the geo-location of the peer is 152 considered private. The Peer Latitude and Peer Longitude MUST NOT be 153 a mix of WGS84 [WGS 84] datum coordinate and NAN values for a single 154 Peer. 156 4. Acknowledgements 158 Thanks to Andrew Clark, Ernest Foo, Dave Meyer, Larry Bluck, Richard 159 Barnes, and Jeffrey Haas for reviewing this document. 161 This document describes a small portion of the research towards the 162 author's PhD. 164 5. IANA Considerations 166 This section requests the Internet Assigned Numbers Authority (IANA) 167 register the additional Subtype code value as: 169 7 GEO_PEER_TABLE 171 in the "MRT format" [I-D.ietf-grow-mrt] and Subtype code values 172 related to the TABLE_DUMP_v2 type in the MRT namespace, in accordance 173 with BCP 26, RFC 5226 [RFC5226]. 175 6. Security Considerations 177 This extension to the "MRT format" [I-D.ietf-grow-mrt] defines fields 178 that are of a descriptive nature and provide information that is 179 useful in the analysis of routing systems. As such, the author 180 believes that they do not constitute an additional security risk. It 181 is recommended that the operators of the BGP collector and Peers 182 consider their own privacy concerns before supplying geographical 183 coordinates in MRT dumps. 185 7. References 187 7.1. Normative References 189 [I-D.ietf-grow-mrt] 190 Blunk, L., Karir, M., and C. Labovitz, "MRT routing 191 information export format", draft-ietf-grow-mrt-13 (work 192 in progress), September 2010. 194 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 195 Requirement Levels", BCP 14, RFC 2119, March 1997. 197 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 198 Protocol 4 (BGP-4)", RFC 4271, January 2006. 200 [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, 201 "Multiprotocol Extensions for BGP-4", RFC 4760, 202 January 2007. 204 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 205 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 206 May 2008. 208 7.2. Informative References 210 [MRT PROG GUIDE] 211 Labovitz, C., "MRT Programmer's Guide", November 1999, 212 . 214 [WGS 84] Geodesy and Geophysics Department, DoD., "World Geodetic 215 System 1984", January 2000, . 218 Author's Address 220 Terry Manderson 221 ICANN 223 Email: terry.manderson@icann.org