--- 1/draft-ietf-grow-geomrt-06.txt 2011-08-26 04:16:33.000000000 +0200 +++ 2/draft-ietf-grow-geomrt-07.txt 2011-08-26 04:16:33.000000000 +0200 @@ -1,19 +1,19 @@ Global Routing Operations Working Group T. Manderson Internet-Draft ICANN -Intended status: Standards Track August 20, 2011 -Expires: February 21, 2012 +Intended status: Standards Track August 26, 2011 +Expires: February 27, 2012 Multi-threaded Routing Toolkit (MRT) Border Gateway Protocol (BGP) routing information export format with geo-location extensions - draft-ietf-grow-geomrt-06.txt + draft-ietf-grow-geomrt-07.txt 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. Status of this Memo @@ -23,21 +23,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on February 21, 2012. + This Internet-Draft will expire on February 27, 2012. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. 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 @@ -79,21 +79,21 @@ 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) format" [I-D.ietf-grow-mrt]. The MRT format was originally defined in the Multi-threaded Routing Toolkit Programmer's Guide [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 tererestrial insight to the routes seen by a BGP - speaker. Such data may ultimately aide reserachers in understanding + speaker. Such data may ultimately aid reserachers 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 anomolies. Such insight could provide future input into network design or network security. This memo documents an optional extension to the "MRT format" [I-D.ietf-grow-mrt] and introduces an additional definition of a MRT subtype field that includes the terestrial coordinates of a BGP Collector and its BGP Peers. @@ -216,21 +216,21 @@ Peer Latitude: Geographic latitude of the BGP peer in WGS84 [WGS-84] datum decimal degrees format stored as a single precision float. Peer Longitude: Geographic Longitude of the BGP peer in WGS84 [WGS-84] datum decimal degrees format stored as a single precision float. 5. BGP Collector Construction - This section is to aide the reader in understanding the function of a + This section is to aid the reader in understanding the function of a BGP collector. The BGP Collector is a device (hardware or software based) which speaks the Border Gateway Protocol and its intended function is to store (and archive) the BGP routing data it receives from other BGP speakers it has peering relationships with, 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 nor propagate any information it knows or receives. It should be noted that this is not always the case, network operators @@ -243,23 +243,23 @@ BGP collector in a network topology is therefore limited by that network's use of BGP. 6. Privacy Considerations 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 the provision of privacy rules, - each location entry in an MRT object is assigned the following - default privacy rules [RFC4119]: + 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]: -- 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 a MRT geo-location record unless there are non-technical measures in place that enforce and communicate the constraints on the use of the location