draft-ietf-grow-geomrt-05.txt   draft-ietf-grow-geomrt-06.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 17, 2011 Intended status: Standards Track August 20, 2011
Expires: February 18, 2012 Expires: February 21, 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-05.txt draft-ietf-grow-geomrt-06.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 18, 2012. This Internet-Draft will expire on February 21, 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 14, line 11 skipping to change at page 14, line 11
information or not, or use its own methods to either trust or information or not, or use its own methods to either trust or
validate the data provided. It is not recommended that a BGP validate the data provided. It is not recommended that a BGP
Collector use geographical coordinates not supplied by a BGP peer. Collector use geographical coordinates not supplied by a BGP peer.
10. References 10. References
10.1. Normative References 10.1. Normative References
[I-D.ietf-grow-mrt] [I-D.ietf-grow-mrt]
Blunk, L., Karir, M., and C. Labovitz, "MRT routing Blunk, L., Karir, M., and C. Labovitz, "MRT routing
information export format", draft-ietf-grow-mrt-15 (work information export format", draft-ietf-grow-mrt-17 (work
in progress), July 2011. in progress), August 2011.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object
Format", RFC 4119, December 2005.
[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
Protocol 4 (BGP-4)", RFC 4271, January 2006. Protocol 4 (BGP-4)", RFC 4271, January 2006.
[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.
10.2. Informative References 10.2. Informative References
[IEEE754] IEEE, "IEEE Standard for Floating-Point Arithmetic", [IEEE754] IEEE, "IEEE Standard for Floating-Point Arithmetic",
August 2008, August 2008,
<http://ieeexplore.ieee.org/servlet/ <http://ieeexplore.ieee.org/servlet/
opac?punumber=4610933>. opac?punumber=4610933>.
[MRT-GUIDE] [MRT-GUIDE]
Labovitz, C., "MRT Programmer's Guide", November 1999, Labovitz, C., "MRT Programmer's Guide", November 1999,
<http://www.merit.edu/networkresearch/mrtprogrammer.pdf>. <http://www.merit.edu/networkresearch/mrtprogrammer.pdf>.
 End of changes. 6 change blocks. 
6 lines changed or deleted 14 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/