RFC 6397: Multi-Threaded Routing Toolkit (MRT) Border Gateway Protocol (BGP) Routing Information Export Format with Geo-Location Extensions
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6397
- Published
- October 2011
- Authors
- T. Manderson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6396Multi-Threaded Routing Toolkit (MRT) Routing Information Export FormatCurrent
October 2011
- RFC 6390Guidelines for Considering New Performance Metric DevelopmentCurrent
October 2011
- RFC 6408Diameter Straightforward-Naming Authority Pointer (S-NAPTR) UsageCurrent
November 2011
- RFC 6382Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted ServicesCurrent
October 2011
- RFC 6412Terminology for Benchmarking Link-State IGP Data-Plane Route ConvergenceCurrent
November 2011
- RFC 6413Benchmarking Methodology for Link-State IGP Data-Plane Route ConvergenceCurrent
November 2011
- RFC 6414Benchmarking Terminology for Protection PerformanceCurrent
November 2011
- RFC 6441Time to Remove Filters for Previously Unallocated IPv4 /8sCurrent
November 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?