draft-ietf-grow-geomrt-06.txt   draft-ietf-grow-geomrt-07.txt 
Global Routing Operations Working Group T. Manderson Global Routing Operations Working Group T. Manderson
Internet-Draft ICANN Internet-Draft ICANN
Intended status: Standards Track August 20, 2011 Intended status: Standards Track August 26, 2011
Expires: February 21, 2012 Expires: February 27, 2012
Multi-threaded Routing Toolkit (MRT) Border Gateway Protocol (BGP) Multi-threaded Routing Toolkit (MRT) Border Gateway Protocol (BGP)
routing information export format with geo-location extensions routing information export format with geo-location extensions
draft-ietf-grow-geomrt-06.txt draft-ietf-grow-geomrt-07.txt
Abstract Abstract
This document updates the Multi-threaded Routing Toolkit (MRT) export This document updates the Multi-threaded Routing Toolkit (MRT) export
format for Border Gateway Protocol (BGP) routing information by format for Border Gateway Protocol (BGP) routing information by
extending it to include optional terrestrial coordinates of a BGP extending it to include optional terrestrial coordinates of a BGP
Collector and its BGP Peers. Collector and its BGP Peers.
Status of this Memo Status of this Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." 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 Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 4, line 20 skipping to change at page 4, line 20
Gateway Protocol [RFC4271] is the subject of study and the analysis Gateway Protocol [RFC4271] is the subject of study and the analysis
can be significantly aided by the availability and extension of the can be significantly aided by the availability and extension of the
"Multi-threaded Routing Toolkit (MRT) format" [I-D.ietf-grow-mrt]. "Multi-threaded Routing Toolkit (MRT) format" [I-D.ietf-grow-mrt].
The MRT format was originally defined in the Multi-threaded Routing The MRT format was originally defined in the Multi-threaded Routing
Toolkit Programmer's Guide [MRT-GUIDE]. Toolkit Programmer's Guide [MRT-GUIDE].
The addition of geo-location coordinates (longitude and latitude) The addition of geo-location coordinates (longitude and latitude)
pertaining to the geographical location of both the BGP collector and pertaining to the geographical location of both the BGP collector and
its BGP peers to BGP export data enables a researcher or enquiring 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 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 any disparity between the geographical location of networks and the
topological location of networks in addition to the relationships topological location of networks in addition to the relationships
between geographical position and routing anomolies. Such insight between geographical position and routing anomolies. Such insight
could provide future input into network design or network security. could provide future input into network design or network security.
This memo documents an optional extension to the "MRT format" This memo documents an optional extension to the "MRT format"
[I-D.ietf-grow-mrt] and introduces an additional definition of a MRT [I-D.ietf-grow-mrt] and introduces an additional definition of a MRT
subtype field that includes the terestrial coordinates of a BGP subtype field that includes the terestrial coordinates of a BGP
Collector and its BGP Peers. Collector and its BGP Peers.
skipping to change at page 9, line 7 skipping to change at page 9, line 7
Peer Latitude: Geographic latitude of the BGP peer in WGS84 [WGS-84] Peer Latitude: Geographic latitude of the BGP peer in WGS84 [WGS-84]
datum decimal degrees format stored as a single precision float. datum decimal degrees format stored as a single precision float.
Peer Longitude: Geographic Longitude of the BGP peer in WGS84 Peer Longitude: Geographic Longitude of the BGP peer in WGS84
[WGS-84] datum decimal degrees format stored as a single precision [WGS-84] datum decimal degrees format stored as a single precision
float. float.
5. BGP Collector Construction 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. BGP collector.
The BGP Collector is a device (hardware or software based) which The BGP Collector is a device (hardware or software based) which
speaks the Border Gateway Protocol and its intended function is to speaks the Border Gateway Protocol and its intended function is to
store (and archive) the BGP routing data it receives from other BGP store (and archive) the BGP routing data it receives from other BGP
speakers it has peering relationships with, providing data for later speakers it has peering relationships with, providing data for later
analysis. The general nature of a BGP Collector is that it is a 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 passive device in that it listens to route updates, and does not
announce nor propagate any information it knows or receives. It announce nor propagate any information it knows or receives. It
should be noted that this is not always the case, network operators should be noted that this is not always the case, network operators
skipping to change at page 10, line 12 skipping to change at page 10, line 12
BGP collector in a network topology is therefore limited by that BGP collector in a network topology is therefore limited by that
network's use of BGP. network's use of BGP.
6. Privacy Considerations 6. Privacy Considerations
The GEOPRIV [RFC6280] architecture requires that privacy rules The GEOPRIV [RFC6280] architecture requires that privacy rules
attached to a location object be transmitted alongside the location attached to a location object be transmitted alongside the location
information in the object. If a BGP Collector adds location information in the object. If a BGP Collector adds location
coordinates to an MRT record based on GEOPRIV location objects, then coordinates to an MRT record based on GEOPRIV location objects, then
it would have to include privacy rules as well. Since the MRT geo- it would have to include privacy rules as well. Since the MRT geo-
location format does not support the the provision of privacy rules, location format does not support the provision of privacy rules, each
each location entry in an MRT object is assigned the following location entry in an MRT object is assigned the following default
default privacy rules [RFC4119]: privacy rules [RFC4119]:
-- retransmission-allowed: True -- retransmission-allowed: True
-- retention-expires: 100 years from timestamp of the MRT object -- retention-expires: 100 years from timestamp of the MRT object
-- ruleset-reference: Empty -- ruleset-reference: Empty
-- note-well: Empty -- note-well: Empty
Location information derived from a location object with more Location information derived from a location object with more
restrictive privacy rules MUST NOT be included in a MRT geo-location restrictive privacy rules MUST NOT be included in a MRT geo-location
record unless there are non-technical measures in place that enforce record unless there are non-technical measures in place that enforce
and communicate the constraints on the use of the location and communicate the constraints on the use of the location
 End of changes. 6 change blocks. 
9 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/