idnits 2.17.1 draft-ietf-grow-geomrt-04.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 (August 12, 2011) is 4641 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-17) exists of draft-ietf-grow-mrt-15 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Global Routing Operations Working Group T. Manderson 3 Internet-Draft ICANN 4 Intended status: Standards Track August 12, 2011 5 Expires: February 13, 2012 7 Multi-threaded Routing Toolkit (MRT) Border Gateway Protocol (BGP) 8 routing information export format with geo-location extensions 9 draft-ietf-grow-geomrt-04.txt 11 Abstract 13 This document updates the Multi-threaded Routing Toolkit (MRT) export 14 format for Border Gateway Protocol (BGP) routing information by 15 extending it to include optional terrestrial coordinates of a BGP 16 Collector and its BGP Peers. 18 Status of this Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on February 13, 2012. 35 Copyright Notice 37 Copyright (c) 2011 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 53 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 54 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 55 4. Geo-location aware MRT Routing Information Subtype . . . . . . 6 56 4.1. GEO_PEER_TABLE . . . . . . . . . . . . . . . . . . . . . . 6 57 4.2. GEO_PEER_TABLE and peer entry values. . . . . . . . . . . 7 58 5. BGP Collector Construction . . . . . . . . . . . . . . . . . . 9 59 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 60 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 61 8. Security Considerations . . . . . . . . . . . . . . . . . . . 12 62 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 63 9.1. Normative References . . . . . . . . . . . . . . . . . . . 13 64 9.2. Informative References . . . . . . . . . . . . . . . . . . 13 65 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14 67 1. Requirements notation 69 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 70 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 71 document are to be interpreted as described in [RFC2119]. 73 2. Introduction 75 Researchers and engineers often wish to analyze network behavior by 76 studying routing protocol transactions and routing information base 77 snapshots in relation to geographical topologies. Usually the Border 78 Gateway Protocol [RFC4271] is the subject of study and the analysis 79 can be significantly aided by the availability and extension of the 80 "Multi-threaded Routing Toolkit (MRT) format" [I-D.ietf-grow-mrt]. 81 The MRT format was originally defined in the Multi-threaded Routing 82 Toolkit Programmer's Guide [MRT-GUIDE]. 84 The addition of geo-location coordinates (longitude and latitude) 85 pertaining to the geographical location of both the BGP collector and 86 its BGP peers to BGP export data enables a researcher or enquiring 87 individual to gain a tererestrial insight to the routes seen by a BGP 88 speaker. Such data may ultimately aide reserachers in understanding 89 any disparity between the geographical location of networks and the 90 topological location of networks in addition to the relationships 91 between geographical position and routing anomolies. Such insight 92 could provide future input into network design or network security. 94 This memo documents an optional extension to the "MRT format" 95 [I-D.ietf-grow-mrt] and introduces an additional definition of a MRT 96 subtype field that includes the terestrial coordinates of a BGP 97 Collector and its BGP Peers. 99 3. Definitions 101 Coordinates: A set of geographic latitude and longitude specifying a 102 location on the Earth. 104 BGP Speaker: A network device which exchanges network routing 105 information using BGP. 107 Geo-location: Assigning a set of coordinates to a specific artifact, 108 in this case a BGP speaker. 110 BGP Collector: A BGP speaker (usually passive) that stores and 111 archives BGP routing data from active BGP peers for analysis. 113 BGP Peer: Either an internal or external BGP peer [RFC4271]. 115 Not A Number (NAN): numeric data type representing an undefined or 116 unrepresentable value. As defined in IEEE Standard for Floating- 117 Point Arithmetic [IEEE754]. 119 4. Geo-location aware MRT Routing Information Subtype 121 An additional subtype (GEO_PEER_TABLE) is defined for the 122 TABLE_DUMP_v2 format, extending TABLE_DUMP_V2 Type. 124 4.1. GEO_PEER_TABLE 126 The GEO_PEER_TABLE Subtype updates the TABLE_DUMP_v2 Types to include 127 Geo-location information in the form of WGS84 [WGS-84] formatted 128 coordinates. 130 The document adds the 7th subtype number and name below. The first 6 131 subtypes are defined by the "MRT format" [I-D.ietf-grow-mrt]. 133 Subtype Number Subtype Name 134 ---------------------------------- 135 7 GEO_PEER_TABLE 137 The GEO_PEER_TABLE MRT record provides the BGP ID of the collector, 138 its latitude and longitude in WGS84 [WGS-84] format, and a list of 139 indexed peers and their respective latitudes and longitudes in WGS84 140 [WGS-84] format. 142 The format and function of the Collector BGP ID, Peer Count are as 143 defined by the TABLE_DUMP_V2 PEER_INDEX_TABLE format. 144 [I-D.ietf-grow-mrt]. 146 The Collector Latitude and Collector Longitude are the geographical 147 coordinates of the collector in WGS84 [WGS-84] datum decimal degrees 148 format stored as a single precision float in the 32 bits allocated to 149 the Collector Latitude and Collector Longitude. The latitude and 150 longitude MAY be a Not A Number (NAN) [IEEE754] for situations where 151 the geo-location of the collector is considered private. The 152 Collector Latitude and Collector Longitude MUST NOT be a mix of WGS84 153 [WGS-84] datum coordinate and NAN values. 155 0 1 2 3 156 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 157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 158 | Collector BGP ID | 159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 160 | Collector Latitude | 161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 162 | Collector Longitude | 163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 164 | Peer Count | Peer entries (variable) 165 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 166 Format of the GEO_PEER_TABLE 168 The format of the peer entries is shown below. The Peer Type and the 169 Peer BGP ID is as defined in the TABLE_DUMP_V2 MRT 170 [I-D.ietf-grow-mrt] PEER_INDEX_TABLE format. The order of the Peer 171 entries in GEO_PEER_TABLE MUST match the order and number as existing 172 in the PEER_INDEX_TABLE. 174 0 1 2 3 175 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 176 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 177 | Peer Type | 178 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 179 | Peer BGP ID | 180 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 181 | Peer Latitude | 182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 183 | Peer Longitude | 184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 186 Format of peer entries 188 The Peer Latitude and Peer Longitude are the geographical coordinates 189 of the peer in WGS84 [WGS-84] datum decimal degrees format stored as 190 a single precision float in the 32 bits allocated to the Peer 191 Latitude and Peer Longitude. The latitude and longitude MAY be a Not 192 A Number (NAN) [IEEE754] for situations where the geo-location of the 193 peer is considered private. The Peer Latitude and Peer Longitude 194 MUST NOT be a mix of WGS84 [WGS-84] datum coordinate and NAN values 195 for a single Peer. 197 4.2. GEO_PEER_TABLE and peer entry values. 199 Collector BGP ID: Defined in the MRT format [I-D.ietf-grow-mrt] 201 Collector Latitude: Geographic latitude of the BGP collector in WGS84 202 [WGS-84] datum decimal degrees format stored as a single precision 203 float. 205 Collector Longitude: Geographic Longitude of the BGP collector in 206 WGS84 [WGS-84] datum decimal degrees format stored as a single 207 precision float. 209 Peer Count: Defined in the MRT format [I-D.ietf-grow-mrt] 211 Peer entries: Defined in the MRT format [I-D.ietf-grow-mrt] 212 Peer Type: Defined in the MRT format [I-D.ietf-grow-mrt] 214 Peer BGP ID: Defined in the MRT format [I-D.ietf-grow-mrt] 216 Peer Latitude: Geographic latitude of the BGP peer in WGS84 [WGS-84] 217 datum decimal degrees format stored as a single precision float. 219 Peer Longitude: Geographic Longitude of the BGP peer in WGS84 220 [WGS-84] datum decimal degrees format stored as a single precision 221 float. 223 5. BGP Collector Construction 225 This section is to aide the reader in understanding the function of a 226 BGP collector. 228 The BGP Collector is a device (hardware or software based) which 229 speaks the Border Gateway Protocol and its intended function is to 230 store (and archive) the BGP routing data it receives from other BGP 231 speakers it has peering relationships with, providing data for later 232 analysis. The general nature of a BGP Collector is that it is a 233 passive device in that it listens to route updates, and does not 234 announce nor propagate any information it knows or receives. It 235 should be noted that this is not always the case, network operators 236 sometimes enable the collection of BGP routing data on active BGP 237 speakers to obtain a situational view of the routing system as they 238 see it at a particular point in time. 240 As a fully fledged BGP speaker the BGP Collector can fit into any BGP 241 topology including iBGP, eBGP, and so on. The implementation of a 242 BGP collector in a network topology is therefore limited by that 243 network's use of BGP. 245 6. Acknowledgements 247 Thanks to Andrew Clark, Ernest Foo, Dave Meyer, Larry Bluck, Richard 248 Barnes, and Jeffrey Haas for reviewing this document. 250 This document describes a small portion of the research towards the 251 author's Ph.D. 253 7. IANA Considerations 255 This section requests the Internet Assigned Numbers Authority (IANA) 256 register the additional Subtype code value as: 258 7 GEO_PEER_TABLE 260 in the "MRT format" [I-D.ietf-grow-mrt] and Subtype code values 261 related to the TABLE_DUMP_v2 type in the MRT namespace. 263 8. Security Considerations 265 This extension to the "MRT format" [I-D.ietf-grow-mrt] defines fields 266 that are of a descriptive nature and provide information that is 267 useful in the analysis of routing systems. As such, the author 268 believes that they do not constitute an additional network based 269 security risk. It is recommended that the operators of the BGP 270 collector and BGP peers consider their own privacy and security 271 concerns before supplying geographical coordinates to BGP data 272 collection systems. Special attention should be given to the 273 physical security of an organisation before supplying geographical 274 coordinates, especially if the resulting BGP data with geo-location 275 extensions is made public. 277 Entities that operate BGP Collectors, and users of data provided by 278 BGP Collectors, should be aware that the geolocation data supplied by 279 a peer can only be taken at face value. It is possible that a BGP 280 peer may supply coordinates that is purposefully misleading or 281 inaccurate. It is therefore up to the BGP Collector to include this 282 information or not, or use its own methods to either trust or 283 validate the data provided. It is not recommended that a BGP 284 Collector use geographical coordinates not supplied by a BGP peer. 286 9. References 288 9.1. Normative References 290 [I-D.ietf-grow-mrt] 291 Blunk, L., Karir, M., and C. Labovitz, "MRT routing 292 information export format", draft-ietf-grow-mrt-15 (work 293 in progress), July 2011. 295 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 296 Requirement Levels", BCP 14, RFC 2119, March 1997. 298 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 299 Protocol 4 (BGP-4)", RFC 4271, January 2006. 301 9.2. Informative References 303 [IEEE754] IEEE, "IEEE Standard for Floating-Point Arithmetic", 304 August 2008, 305 . 308 [MRT-GUIDE] 309 Labovitz, C., "MRT Programmer's Guide", November 1999, 310 . 312 [WGS-84] Geodesy and Geophysics Department, DoD., "World Geodetic 313 System 1984", January 2000, . 316 Author's Address 318 Terry Manderson 319 ICANN 321 Email: terry.manderson@icann.org