Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format
RFC 6396
| Document | Type |
RFC - Proposed Standard
(October 2011; Errata)
Was draft-ietf-grow-mrt (grow WG)
|
|
|---|---|---|---|
| Authors | Larry Blunk , Craig Labovitz , Manish Karir | ||
| Last updated | 2020-01-21 | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized with errata bibtex | ||
| Reviews | |||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 6396 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Ron Bonica | ||
| IESG note | Peter Schoenmaker (pds@lugs.com), co-chair of the GROW Working Group is the document shepherd. | ||
| Send notices to | (None) | ||
Internet Engineering Task Force (IETF) L. Blunk
Request for Comments: 6396 M. Karir
Category: Standards Track Merit Network
ISSN: 2070-1721 C. Labovitz
Deepfield Networks
October 2011
Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format
Abstract
This document describes the MRT format for routing information
export. This format was developed in concert with the Multi-threaded
Routing Toolkit (MRT) from whence the format takes it name. The
format can be used to export routing protocol messages, state
changes, and routing information base contents.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6396.
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
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Blunk, et al. Standards Track [Page 1]
RFC 6396 MRT Format October 2011
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Specification of Requirements . . . . . . . . . . . . . . 4
2. MRT Common Header . . . . . . . . . . . . . . . . . . . . . . 4
3. Extended Timestamp MRT Header . . . . . . . . . . . . . . . . 5
4. MRT Types . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. OSPFv2 Type . . . . . . . . . . . . . . . . . . . . . . . 6
4.2. TABLE_DUMP Type . . . . . . . . . . . . . . . . . . . . . 7
4.3. TABLE_DUMP_V2 Type . . . . . . . . . . . . . . . . . . . . 9
4.3.1. PEER_INDEX_TABLE Subtype . . . . . . . . . . . . . . . 9
4.3.2. AFI/SAFI-Specific RIB Subtypes . . . . . . . . . . . . 11
4.3.3. RIB_GENERIC Subtype . . . . . . . . . . . . . . . . . 11
4.3.4. RIB Entries . . . . . . . . . . . . . . . . . . . . . 12
4.4. BGP4MP Type . . . . . . . . . . . . . . . . . . . . . . . 13
4.4.1. BGP4MP_STATE_CHANGE Subtype . . . . . . . . . . . . . 13
4.4.2. BGP4MP_MESSAGE Subtype . . . . . . . . . . . . . . . . 14
4.4.3. BGP4MP_MESSAGE_AS4 Subtype . . . . . . . . . . . . . . 15
4.4.4. BGP4MP_STATE_CHANGE_AS4 Subtype . . . . . . . . . . . 15
4.4.5. BGP4MP_MESSAGE_LOCAL Subtype . . . . . . . . . . . . . 16
4.4.6. BGP4MP_MESSAGE_AS4_LOCAL Subtype . . . . . . . . . . . 16
4.5. ISIS Type . . . . . . . . . . . . . . . . . . . . . . . . 16
4.6. OSPFv3 Type . . . . . . . . . . . . . . . . . . . . . . . 17
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
5.1. Type Codes . . . . . . . . . . . . . . . . . . . . . . . . 17
5.2. Subtype Codes . . . . . . . . . . . . . . . . . . . . . . 18
5.3. Defined Type Codes . . . . . . . . . . . . . . . . . . . . 18
5.4. Defined BGP, BGP4PLUS, and BGP4PLUS_01 Subtype Codes . . . 19
5.5. Defined TABLE_DUMP Subtype Codes . . . . . . . . . . . . . 19
5.6. Defined TABLE_DUMP_V2 Subtype Codes . . . . . . . . . . . 19
Show full document text