draft-ietf-grow-mrt-13.txt   draft-ietf-grow-mrt-14.txt 
Network Working Group L. Blunk Network Working Group L. Blunk
Internet-Draft M. Karir Internet-Draft M. Karir
Intended status: Standards Track Merit Network Intended status: Informational Merit Network
Expires: March 13, 2011 C. Labovitz Expires: October 22, 2011 C. Labovitz
Arbor Networks Arbor Networks
September 9, 2010 April 20, 2011
MRT routing information export format MRT routing information export format
draft-ietf-grow-mrt-13.txt draft-ietf-grow-mrt-14.txt
Abstract Abstract
This document describes the MRT format for routing information This document describes the MRT format for routing information
export. This format was developed in concert with the Multi-threaded export. This format was developed in concert with the Multi-threaded
Routing Toolkit (MRT) from whence the format takes it name. The Routing Toolkit (MRT) from whence the format takes it name. The
format can be used to export routing protocol messages, state format can be used to export routing protocol messages, state
changes, and routing information base contents. changes, and routing information base contents.
Status of this Memo Status of this Memo
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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 March 13, 2011. This Internet-Draft will expire on October 22, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 7 skipping to change at page 3, line 7
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.1. Specification of Requirements . . . . . . . . . . . . . . 4
3. Basic MRT Format . . . . . . . . . . . . . . . . . . . . . . . 6 2. MRT Common Header . . . . . . . . . . . . . . . . . . . . . . 5
4. MRT Informational Types . . . . . . . . . . . . . . . . . . . 8 3. Extended Timestamp MRT Header . . . . . . . . . . . . . . . . 7
4.1. START Type . . . . . . . . . . . . . . . . . . . . . . . . 8 4. MRT Types . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.2. I_AM_DEAD Type . . . . . . . . . . . . . . . . . . . . . . 8 4.1. OSPFv2 Type . . . . . . . . . . . . . . . . . . . . . . . 8
5. MRT Routing Information Types . . . . . . . . . . . . . . . . 9 4.2. TABLE_DUMP Type . . . . . . . . . . . . . . . . . . . . . 9
5.1. OSPF Type . . . . . . . . . . . . . . . . . . . . . . . . 9 4.3. TABLE_DUMP_V2 Type . . . . . . . . . . . . . . . . . . . . 10
5.2. TABLE_DUMP Type . . . . . . . . . . . . . . . . . . . . . 9 4.3.1. PEER_INDEX_TABLE Subtype . . . . . . . . . . . . . . . 11
5.3. TABLE_DUMP_V2 Type . . . . . . . . . . . . . . . . . . . . 11 4.3.2. AFI/SAFI specific RIB Subtypes . . . . . . . . . . . . 12
5.4. BGP4MP Type . . . . . . . . . . . . . . . . . . . . . . . 14 4.3.3. RIB_GENERIC Subtype . . . . . . . . . . . . . . . . . 13
5.4.1. BGP4MP_STATE_CHANGE Subtype . . . . . . . . . . . . . 15 4.3.4. RIB Entries . . . . . . . . . . . . . . . . . . . . . 13
5.4.2. BGP4MP_MESSAGE Subtype . . . . . . . . . . . . . . . . 16 4.4. BGP4MP Type . . . . . . . . . . . . . . . . . . . . . . . 14
5.4.3. BGP4MP_MESSAGE_AS4 Subtype . . . . . . . . . . . . . . 17 4.4.1. BGP4MP_STATE_CHANGE Subtype . . . . . . . . . . . . . 15
5.4.4. BGP4MP_STATE_CHANGE_AS4 Subtype . . . . . . . . . . . 17 4.4.2. BGP4MP_MESSAGE Subtype . . . . . . . . . . . . . . . . 16
5.4.5. BGP4MP_MESSAGE_LOCAL Subtype . . . . . . . . . . . . . 18 4.4.3. BGP4MP_MESSAGE_AS4 Subtype . . . . . . . . . . . . . . 17
5.4.6. BGP4MP_MESSAGE_AS4_LOCAL Subtype . . . . . . . . . . . 18 4.4.4. BGP4MP_STATE_CHANGE_AS4 Subtype . . . . . . . . . . . 17
5.5. BGP4MP_ET Type . . . . . . . . . . . . . . . . . . . . . . 18 4.4.5. BGP4MP_MESSAGE_LOCAL Subtype . . . . . . . . . . . . . 18
5.6. ISIS Type . . . . . . . . . . . . . . . . . . . . . . . . 19 4.4.6. BGP4MP_MESSAGE_AS4_LOCAL Subtype . . . . . . . . . . . 18
5.7. ISIS_ET Type . . . . . . . . . . . . . . . . . . . . . . . 19 4.5. ISIS Type . . . . . . . . . . . . . . . . . . . . . . . . 18
5.8. OSPFv3 Type . . . . . . . . . . . . . . . . . . . . . . . 19 4.6. OSPFv3 Type . . . . . . . . . . . . . . . . . . . . . . . 19
5.9. OSPFv3_ET Type . . . . . . . . . . . . . . . . . . . . . . 20 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 21 6. Security Considerations . . . . . . . . . . . . . . . . . . . 21
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22
7.1. Type Codes . . . . . . . . . . . . . . . . . . . . . . . . 22 7.1. Normative References . . . . . . . . . . . . . . . . . . . 22
7.2. Subtype Codes . . . . . . . . . . . . . . . . . . . . . . 22 7.2. Informative References . . . . . . . . . . . . . . . . . . 22
8. Security Considerations . . . . . . . . . . . . . . . . . . . 23 Appendix A. MRT Encoding Examples . . . . . . . . . . . . . . . . 24
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Appendix B. Deprecated MRT Types . . . . . . . . . . . . . . . . 27
9.1. Normative References . . . . . . . . . . . . . . . . . . . 24 B.1. Deprecated MRT Informational Types . . . . . . . . . . . . 27
9.2. Informative References . . . . . . . . . . . . . . . . . . 24 B.1.1. NULL Type . . . . . . . . . . . . . . . . . . . . . . 27
Appendix A. Deprecated MRT types . . . . . . . . . . . . . . . . 25 B.1.2. START Type . . . . . . . . . . . . . . . . . . . . . . 27
A.1. Deprecated MRT Informational Types . . . . . . . . . . . . 25 B.1.3. DIE Type . . . . . . . . . . . . . . . . . . . . . . . 27
A.1.1. NULL Type . . . . . . . . . . . . . . . . . . . . . . 25 B.1.4. I_AM_DEAD Type . . . . . . . . . . . . . . . . . . . . 27
A.1.2. DIE Type . . . . . . . . . . . . . . . . . . . . . . . 25 B.1.5. PEER_DOWN Type . . . . . . . . . . . . . . . . . . . . 28
A.1.3. PEER_DOWN Type . . . . . . . . . . . . . . . . . . . . 25 B.2. Other Deprecated MRT Types . . . . . . . . . . . . . . . . 28
A.2. Deprecated MRT Routing Information Types . . . . . . . . . 25 B.2.1. BGP Type . . . . . . . . . . . . . . . . . . . . . . . 28
A.2.1. BGP Type . . . . . . . . . . . . . . . . . . . . . . . 25 B.2.2. RIP Type . . . . . . . . . . . . . . . . . . . . . . . 31
A.2.2. RIP Type . . . . . . . . . . . . . . . . . . . . . . . 28 B.2.3. IDRP Type . . . . . . . . . . . . . . . . . . . . . . 31
A.2.3. IDRP Type . . . . . . . . . . . . . . . . . . . . . . 28 B.2.4. RIPNG Type . . . . . . . . . . . . . . . . . . . . . . 31
A.2.4. RIPNG Type . . . . . . . . . . . . . . . . . . . . . . 29 B.2.5. BGP4PLUS and BGP4PLUS_01 Types . . . . . . . . . . . . 32
A.2.5. BGP4PLUS and BGP4PLUS_01 Types . . . . . . . . . . . . 29 B.2.6. Deprecated BGP4MP Subtypes . . . . . . . . . . . . . . 32
A.2.6. Deprecated BGP4MP Subtypes . . . . . . . . . . . . . . 29 Appendix C. Acknowledgements . . . . . . . . . . . . . . . . . . 34
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 35
1. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
2. Introduction 1. Introduction
Researchers and engineers often wish to analyze network behavior by Researchers and engineers often wish to analyze network behavior by
studying routing protocol transactions and routing information base studying routing protocol transactions and routing information base
snapshots. To this end, the MRT format was developed to encapsulate, snapshots. To this end, the MRT record format was developed to
export, and archive this information in a standardized data encapsulate, export, and archive this information in a standardized
representation. The BGP routing protocol, in particular, has been data representation.
the subject of extensive study and analysis which has been
significantly aided by the availability of the MRT format. The MRT
format was initially defined in the MRT Programmer's Guide [MRT PROG
GUIDE].
This memo serves to document the MRT format as currently implemented The BGP routing protocol, in particular, has been the subject of
in publicly available software. The format has been extended since extensive study and analysis which has been significantly aided by
its original introduction in the MRT toolset and these extensions are the availability of the MRT format. Two examples of large-scale MRT
also included in this memo. Further extensions may be introduced at based BGP archival projects include the University of Oregon Route
a later date through additional definitions of the MRT Type field and Views Project and the RIPE NCC Routing Information Service (RIS).
Subtype fields.
A number of MRT message types have been documented in some references The MRT format was initially defined in the MRT Programmer's Guide
but are not known to have been implemented. Further, several types [MRT PROG GUIDE]. Subsequent extensions were made in the the GNU
were employed in early MRT implementations, but are no longer Zebra software routing suite and the Sprint Advanced Technology Labs
actively being used. These types are considered to be deprecated and Python Routing Toolkit (PyRT). Further extensions may be introduced
are documented in a separate appendix at the end of this document. at a later date through additional definitions of the MRT Type field
Some of the deprecated types may of interest to researchers examining and Subtype fields.
historical MRT archives.
A number of MRT record types listed in the MRT Programmer's Guide
[MRT PROG GUIDE] are not known to have been implemented and, in some
cases, were incompletely specified. Further, several types were
employed in early MRT implementations, but saw limited use and were
updated by improved versions. These types are considered to be
deprecated and are documented in the Deprecated MRT Types
(Appendix B) section at the end of this document. The deprecated
types consist of codes 0 through 10 inclusive. Some of the
deprecated types may be of interest to researchers examining
historical MRT format archives.
Fields which contain multi-octet numeric values are encoded in Fields which contain multi-octet numeric values are encoded in
network octet order from most significant octet to least significant network octet order from most significant octet to least significant
octet. Fields which contain routing message fields are encoded in octet. Fields which contain routing message fields are encoded in
the same order as they appear in the packet contents. the same order as they appear in the packet contents.
3. Basic MRT Format 1.1. Specification of Requirements
All MRT format messages have a common header which includes a The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
timestamp, Type, Subtype, and length field. The header is followed "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
by a message field. The MRT common header is illustrated below. document are to be interpreted as described in [RFC2119].
2. MRT Common Header
All MRT format records have a Common Header which consists of a
Timestamp, Type, Subtype, and Length field. The header is followed
by a Message field. The MRT Common Header is illustrated below.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp | | Timestamp |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Subtype | | Type | Subtype |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message... (variable) | Message... (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Basic MRT Format Figure 1: MRT Common Header
Header Field Descriptions: Header Field Descriptions:
Timestamp: Timestamp:
Time in seconds since 1 January 1970 00:00:00 UTC A 4-octet field whose integer value is the number of seconds,
excluding leap seconds, elapsed since midnight proleptic
Coordinated Universal Time (UTC). This representation of time
is sometimes called "UNIX time" POSIX [IEEE.P1003.1-1990].
This time format cannot represent time values prior to January
1, 1970. The latest UTC time value that can be represented by
a four-octet integer value is 03:14:07 on January 19, 2038,
which is represented by the hexadecimal value 7FFFFFFF.
Implementations which wish to create MRT records after this
date will need to provide an alternate EPOCH time base for the
Timestamp field. Mechanisms for indicating this alternate
EPOCH are currently outside the scope of this document.
Type: Type:
A 2-octet field that indicates the Type of information A 2-octet field that indicates the Type of information
contained in the message field. Types 0 through 4 are contained in the message field. Types 0 through 4 are
informational messages pertaining to the state of an MRT informational messages pertaining to the state of an MRT
collector, while Types 5 and higher are used to convey routing collector, while Types 5 and higher are used to convey routing
information. information.
Subtype: Subtype:
A 2-octet field that is used to further distinguish message A 2-octet field that is used to further distinguish message
information within a particular message Type. information within a particular record Type.
Length: Length:
A 4-octet message length field. The length field contains the A 4-octet message length field. The length field contains the
number of octets within the message. The length field does not number of octets within the message. The length field does not
include the length of the MRT common header. include the length of the MRT Common Header.
Message: Message:
A variable length message. The contents of this field are A variable length message. The contents of this field are
context dependent upon the Type and Subtype fields. context dependent upon the Type and Subtype fields.
4. MRT Informational Types 3. Extended Timestamp MRT Header
The MRT format defines five Informational Type messages. These
messages are intended to signal the state of an MRT data collector
and do not contain routing information. These messages are OPTIONAL
and were largely intended for use when MRT messages are sent over a
network to a remote repository store. However, MRT message
repository stores have traditionally resided on the same device as
the collector and these Informational Types have seen limited
implementation. Further, transport mechanisms for MRT messages are
considered to be outside the scope of this document.
The START and I_AM_DEAD messages MAY be used to provide a time
reference when a data collector begins and ends the collection
process. The time reference is obtained from the Timestamp field in
the MRT message header.
The message field MAY contain an OPTIONAL message string for
diagnostic purposes. The message string encoding MUST follow the
UTF-8 transformation format. The Subtype field is unused for these
Types and SHOULD be set to 0.
The MRT Informational Types are defined below:
1 START
3 I_AM_DEAD
4.1. START Type
The START Type indicates a collector is about to begin generating MRT Several MRT format record types support a variant type with an
messages. extended timestamp field. The purpose of this field is to support
measurements at sub-second resolutions. This field, Microsecond
Timestamp, contains an unsigned 32BIT offset value in microseconds
which is added to the Timestamp field value. The Timestamp field
remains as defined in the MRT Common Header. The Microsecond
Timestamp immediately follows the length field in the MRT Common
Header and precedes all other fields in the message. The Microsecond
Timestamp is included in the computation of the length field value.
The Extended Timestamp MRT Header is illustrated below.
4.2. I_AM_DEAD Type 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Subtype |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Microsecond Timestamp |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message... (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
An I_AM_DEAD MRT message indicates that a collector has shut down and Figure 2: Extended Timestamp MRT Header
has stopped generating MRT messages.
5. MRT Routing Information Types 4. MRT Types
The following MRT Routing Information Types are currently defined for The following MRT Types are currently defined for the MRT format.
the MRT format: The MRT Types which contain the "_ET" suffix in their names identify
those types which use an Extended Timestamp MRT Header. The subtype
and message fields in these types remain as defined for the MRT Types
of the same name without the "_ET" suffix.
11 OSPF 11 OSPFv2
12 TABLE_DUMP 12 TABLE_DUMP
13 TABLE_DUMP_V2 13 TABLE_DUMP_V2
16 BGP4MP 16 BGP4MP
17 BGP4MP_ET 17 BGP4MP_ET
32 ISIS 32 ISIS
33 ISIS_ET 33 ISIS_ET
48 OSPFv3 48 OSPFv3
49 OSPFv3_ET 49 OSPFv3_ET
5.1. OSPF Type 4.1. OSPFv2 Type
This Type supports the OSPF Protocol as defined in RFC 2328 This Type supports the OSPFv2 Protocol as defined in RFC 2328
[RFC2328]. The Subtype field may contain two possible values: [RFC2328]. The Subtype field MAY contain two possible values:
0 OSPF_STATE_CHANGE 0 OSPF_STATE_CHANGE
1 OSPF_LSA_UPDATE 1 OSPF_LSA_UPDATE
The format of the MRT Message field for the OSPF Type is as follows: The format of the MRT Message field for the OSPFv2 Type is as
follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remote IP address | | Remote IP address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local IP address | | Local IP address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OSPF Message Contents (variable) | OSPF Message Contents (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: OSPF Type Figure 3: OSPFv2 Type
5.2. TABLE_DUMP Type The Remote IP address field contains source IPv4 [RFC0791] address
from the IP header of the OSPF message. The Local IP address
contains the destination IPv4 address from the IP header. The OSPF
Message Contents field contains the complete contents of the OSPF
packet following the IP header.
4.2. TABLE_DUMP Type
The TABLE_DUMP Type is used to encode the contents of a BGP Routing The TABLE_DUMP Type is used to encode the contents of a BGP Routing
Information Base (RIB). Each RIB entry is encoded in a distinct Information Base (RIB). Each RIB entry is encoded in a distinct
sequential MRT record. The Subtype field is used to encode whether sequential MRT record. It is RECOMMENDED that new MRT encoding
the RIB entry contains IPv4 or IPv6 addresses. There are two implementations use the TABLE_DUMP_V2 Type (see below) instead of the
possible values for the Subtype as shown below. TABLE_DUMP Type due to limitations in this type. However, due to the
significant volume of historical data encoded with this type, MRT
decoding applications MAY wish to support this type.
The Subtype field is used to encode whether the RIB entry contains
IPv4 or IPv6 [RFC2460] addresses. There are two possible values for
the Subtype as shown below.
1 AFI_IPv4 1 AFI_IPv4
2 AFI_IPv6 2 AFI_IPv6
The format of the TABLE_DUMP Type is illustrated below. The format of the TABLE_DUMP Type is illustrated below.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| View # | Sequence number | | View # | Sequence number |
skipping to change at page 10, line 25 skipping to change at page 9, line 42
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originated Time | | Originated Time |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer IP address (variable) | | Peer IP address (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer AS | Attribute Length | | Peer AS | Attribute Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Attribute... (variable) | BGP Attribute... (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: TABLE_DUMP Type Figure 4: TABLE_DUMP Type
The View field is normally 0 and is intended for cases where an The View field is normally 0 and is intended for cases where an
implementation may have multiple RIB views (such as a route server). implementation may have multiple RIB views (such as a route server).
In cases where multiple RIB views are present, an implementation may In cases where multiple RIB views are present, an implementation MAY
use the the view field to distinguish entries from each view. The use the the view field to distinguish entries from each view. The
Sequence field is a simple incremental counter for each RIB entry. A Sequence field is a simple incremental counter for each RIB entry. A
typical RIB dump will exceed the 16-bit bounds of this counter and typical RIB dump will exceed the 16-bit bounds of this counter and
implementation should simply wrap back to zero and continue implementation SHOULD simply wrap back to zero and continue
incrementing the counter in such cases. incrementing the counter in such cases.
The Prefix field contains the IP address of a particular RIB entry. The Prefix field contains the IP address of a particular RIB entry.
The size of this field is dependent on the value of the Subtype for The size of this field is dependent on the value of the Subtype for
this message. For AFI_IPv4, this field is 4 octets, for AFI_IPv6, it this record. The AFI_IPv4 Subtype value specifies an Address Family
is 16 octets in length. The Prefix Length field indicates the length [IANA-AF] Identifier (AFI) type of IPv4. It specifies a prefix field
in bits of the prefix mask for the preceding Prefix field. length of 4 octets. For AFI_IPv6, it is 16 octets in length. The
Prefix Length field indicates the length in bits of the prefix mask
for the preceding Prefix field.
The Status octet is unused in the TABLE_DUMP Type and SHOULD be set The Status octet is unused in the TABLE_DUMP Type and SHOULD be set
to 1. to 1.
The Originated Time contains the 4-octet time at which this prefix The Originated Time contains the 4-octet time at which this prefix
was heard. The value represents the time in seconds since 1 January was heard. The value represents the time in seconds since 1 January
1970 00:00:00 UTC. 1970 00:00:00 UTC.
The Peer IP field is the IP address of the peer which provided the The Peer IP field is the IP address of the peer which provided the
update for this RIB entry. As with the Prefix field, the size of update for this RIB entry. As with the Prefix field, the size of
this field is dependent on the Subtype. AFI_IPv4 indicates a 4 octet this field is dependent on the Subtype. AFI_IPv4 indicates a 4 octet
field and an IPv4 address, while a Subtype of AFI_IPv6 requires a 16 field and an IPv4 address, while a Subtype of AFI_IPv6 requires a 16
octet field and an IPv6 address. The Peer AS field contains the 2 octet field and an IPv6 address. The Peer AS field contains the 2
octet AS number of the peer. octet Autonomous System (AS) number of the peer.
Note that the TABLE_DUMP Type does not permit 4-Byte Peer AS numbers. The TABLE_DUMP Type does not permit 4-Byte Peer AS numbers. Nor does
Nor does it allow the AFI of the peer IP to differ from the AFI of it allow the AFI of the peer IP to differ from the AFI of the Prefix
the Prefix field. The TABLE_DUMP_V2 Type must be used in these field. The TABLE_DUMP_V2 Type MUST be used in these situations.
situations.
Attribute Length contains the length of Attribute field and is Attribute Length contains the length of Attribute field and is
2-octets. The BGP Attribute field contains the BGP attribute 2-octets. The BGP Attribute field contains the BGP attribute
information for the RIB entry. information for the RIB entry. The AS_PATH attribute MUST only
consist of 2-Byte AS numbers. The TABLE_DUMP_V2 supports 4-Byte AS
numbers in the AS_PATH attribute.
5.3. TABLE_DUMP_V2 Type 4.3. TABLE_DUMP_V2 Type
The TABLE_DUMP_V2 Type updates the TABLE_DUMP Type to include 4-Byte The TABLE_DUMP_V2 Type updates the TABLE_DUMP Type to include 4-Byte
ASN support and full support for BGP Multiprotocol extensions. It Autonomous System Number (ASN) support and full support for BGP
also improves upon the space efficiency of the TABLE_DUMP Type by Multiprotocol extensions. It also improves upon the space efficiency
employing an index table for peers and permitting a single MRT record of the TABLE_DUMP Type by employing an index table for peers and
per NLRI entry. The following subtypes are used with the permitting a single MRT record per Network Layer Reachability
Information (NLRI) entry. The following subtypes are used with the
TABLE_DUMP_V2 Type. TABLE_DUMP_V2 Type.
1 PEER_INDEX_TABLE 1 PEER_INDEX_TABLE
2 RIB_IPV4_UNICAST 2 RIB_IPV4_UNICAST
3 RIB_IPV4_MULTICAST 3 RIB_IPV4_MULTICAST
4 RIB_IPV6_UNICAST 4 RIB_IPV6_UNICAST
5 RIB_IPV6_MULTICAST 5 RIB_IPV6_MULTICAST
6 RIB_GENERIC 6 RIB_GENERIC
4.3.1. PEER_INDEX_TABLE Subtype
An initial PEER_INDEX_TABLE MRT record provides the BGP ID of the An initial PEER_INDEX_TABLE MRT record provides the BGP ID of the
collector, an optional view name, and a list of indexed peers. collector, an OPTIONAL view name, and a list of indexed peers.
Following the PEER_INDEX_TABLE MRT record, a series of MRT records Following the PEER_INDEX_TABLE MRT record, a series of MRT records
are used to encode RIB table entries. This series of MRT records use are used to encode RIB table entries. This series of MRT records use
subtypes 2-6 and are separate from the PEER_INDEX_TABLE MRT record subtypes 2-6 and are separate from the PEER_INDEX_TABLE MRT record
itself and include full MRT record headers. Note that the RIB entry itself and include full MRT record headers. The RIB entry MRT
MRT records MUST immediately follow the PEER_INDEX_TABLE MRT record. records MUST immediately follow the PEER_INDEX_TABLE MRT record.
The header of the PEER_INDEX_TABLE Subtype is shown below. The View The header of the PEER_INDEX_TABLE Subtype is shown below. The View
Name is optional and, if not present, the View Name Length MUST be Name is OPTIONAL and, if not present, the View Name Length MUST be
set to 0. The View Name encoding MUST follow the UTF-8 set to 0. The View Name encoding MUST follow the UTF-8
transformation format. transformation format [RFC3629].
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Collector BGP ID | | Collector BGP ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| View Name Length | View Name (variable) | | View Name Length | View Name (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Count | Peer Entries (variable) | Peer Count | Peer Entries (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: PEER_INDEX_TABLE Subtype Figure 5: PEER_INDEX_TABLE Subtype
The format of the Peer Entries is shown below. The PEER_INDEX_TABLE The format of the Peer Entries is shown below. The PEER_INDEX_TABLE
record contains Peer Count number of Peer Entries. record contains Peer Count number of Peer Entries.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Type | | Peer Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer BGP ID | | Peer BGP ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer IP address (variable) | | Peer IP address (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer AS (variable) | | Peer AS (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Peer Entries Figure 6: Peer Entries
The Peer Type, Peer BGP ID, Peer IP, and Peer AS fields are repeated The Peer Type, Peer BGP ID, Peer IP, and Peer AS fields are repeated
as indicated by the Peer Count field. The position of the Peer in as indicated by the Peer Count field. The position of the Peer in
the PEER_INDEX_TABLE is used as an index in the subsequent the PEER_INDEX_TABLE is used as an index in the subsequent
TABLE_DUMP_V2 MRT records. The index number begins with 0. TABLE_DUMP_V2 MRT records. The index number begins with 0.
The Peer Type field is a bit field which encodes the type of the AS The Peer Type field is a bit field which encodes the type of the AS
and IP address as follows: and IP address as identified by the A and I bits, respectively,
below.
Bit 0 - unset for IPv4 Peer IP address, set for IPv6 0 1 2 3 4 5 6 7
Bit 1 - unset when Peer AS is 16 bits, set when it's 32 bits +-+-+-+-+-+-+-+-+
| | | | | | |A|I|
+-+-+-+-+-+-+-+-+
The MRT records which follow the PEER_INDEX_TABLE MRT record contain Bit 6: Peer AS number size: 0 = 16 bits, 1 = 32 bits
the RIB entries and include a header which specifies a sequence Bit 7: Peer IP Address family: 0 = IPv4, 1 = IPv6
number, NLRI, and a count of the number of RIB entries which follow.
The format for the RIB_IPV4_UNICAST, RIB_IPV4_MULTICAST, Figure 7: Peer Type Field
RIB_IPV6_UNICAST, and RIB_IPV6_MULTICAST headers are shown below.
The Prefix Length and Prefix fields are encoded in the same manner as The MRT records which follow the PEER_INDEX_TABLE MRT record consist
the BGP NLRI encoding for IPV4 and IPV6 prefixes. Namely, the Prefix of the subtypes listed below and contain the actual RIB table
field contains address prefixes followed by enough trailing bits to entries. They include a header which specifies a sequence number, a
make the end of the field fall on an octet boundary. Note that the NLRI field, and a count of the number of RIB entries contained within
value of trailing bits is irrelevant. the record.
4.3.2. AFI/SAFI specific RIB Subtypes
The AFI/SAFI specific RIB Subtypes consist of the RIB_IPV4_UNICAST,
RIB_IPV4_MULTICAST, RIB_IPV6_UNICAST, and RIB_IPV6_MULTICAST
Subtypes. These specific RIB table entries are given their own MRT
TABLE_DUMP_V2 subtypes as they are the most common type of RIB table
instances and providing specific MRT subtypes for them permits more
compact encodings. These subtypes permit a single MRT record to
encode multiple RIB table entries for a single prefix. The Prefix
Length and Prefix fields are encoded in the same manner as the BGP
NLRI encoding for IPV4 and IPV6 prefixes. Namely, the Prefix field
contains address prefixes followed by enough trailing bits to make
the end of the field fall on an octet boundary. The value of
trailing bits is irrelevant.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence number | | Sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Prefix Length | | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Prefix (variable) | | Prefix (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Entry Count | RIB Entries (variable) | Entry Count | RIB Entries (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: RIB Entry Header Figure 8: RIB Entry Header
4.3.3. RIB_GENERIC Subtype
The RIB_GENERIC header is shown below. It is used to cover RIB The RIB_GENERIC header is shown below. It is used to cover RIB
entries which do not fall under the common case entries defined entries which do not fall under the common case entries defined
above. It includes Address Family Identifier (AFI), Subsequent AFI above. It consists of an AFI, Subsequent AFI (SAFI) and a single
and a single NLRI entry. The NLRI information is specific to the AFI NLRI entry. The NLRI information is specific to the AFI and SAFI
and SAFI values. An implementation which does not recognize values. An implementation which does not recognize particular AFI
particular AFI and SAFI values SHOULD discard the remainder of the and SAFI values SHOULD discard the remainder of the MRT record.
MRT record.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence number | | Sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address Family Identifier |Subsequent AFI | | Address Family Identifier |Subsequent AFI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Layer Reachability Information (variable) | | Network Layer Reachability Information (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Entry Count | RIB Entries (variable) | Entry Count | RIB Entries (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 7: RIB_GENERIC Entry Header Figure 9: RIB_GENERIC Entry Header
The RIB and RIB_GENERIC Entry Headers are followed by a series of RIB 4.3.4. RIB Entries
Entries which are repeated Entry Count times. These entries share a
common format as shown below. They include a Peer Index from the The RIB Entries are repeated Entry Count times. These entries share
a common format as shown below. They include a Peer Index from the
PEER_INDEX_TABLE MRT record, an originated time for the RIB Entry, PEER_INDEX_TABLE MRT record, an originated time for the RIB Entry,
and the BGP path attribute length and attributes encoded as provided and the BGP path attribute length and attributes. All AS numbers in
in a BGP Update message. the AS_PATH attribute MUST be encoded as 4-Byte AS numbers.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Index | | Peer Index |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originated Time | | Originated Time |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Attribute Length | | Attribute Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Attributes... (variable) | BGP Attributes... (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 8: RIB Entries Figure 10: RIB Entries
There is one exception to the encoding of BGP attributes for the BGP There is one exception to the encoding of BGP attributes for the BGP
MP_REACH_NLRI attribute (BGP Type Code 14) RFC 4760 [RFC4760]. Since MP_REACH_NLRI attribute (BGP Type Code 14) RFC 4760 [RFC4760]. Since
the AFI, SAFI, and NLRI information is already encoded in the the AFI, SAFI, and NLRI information is already encoded in the
MULTIPROTOCOL header, only the Next Hop Address Length and Next Hop MULTIPROTOCOL header, only the Next Hop Address Length and Next Hop
Address fields are included. The Reserved field is omitted. The Address fields are included. The Reserved field is omitted. The
attribute length is also adjusted to reflect only the length of the attribute length is also adjusted to reflect only the length of the
Next Hop Address Length and Next Hop Address fields. Next Hop Address Length and Next Hop Address fields.
5.4. BGP4MP Type 4.4. BGP4MP Type
This Type was initially defined in the Zebra software package for the This Type was initially defined in the Zebra software package for the
BGP protocol with multiprotocol extension support as defined by RFC BGP protocol with multiprotocol extension support as defined by RFC
4760 [RFC4760]. It supersedes the BGP, BGP4PLUS, BGP4PLUS_01 Types. 4760 [RFC4760]. The BGP4MP Type has six Subtypes which are defined
The BGP4MP Type has six Subtypes which are defined as follows: as follows:
0 BGP4MP_STATE_CHANGE 0 BGP4MP_STATE_CHANGE
1 BGP4MP_MESSAGE 1 BGP4MP_MESSAGE
4 BGP4MP_MESSAGE_AS4 4 BGP4MP_MESSAGE_AS4
5 BGP4MP_STATE_CHANGE_AS4 5 BGP4MP_STATE_CHANGE_AS4
6 BGP4MP_MESSAGE_LOCAL 6 BGP4MP_MESSAGE_LOCAL
7 BGP4MP_MESSAGE_AS4_LOCAL 7 BGP4MP_MESSAGE_AS4_LOCAL
5.4.1. BGP4MP_STATE_CHANGE Subtype 4.4.1. BGP4MP_STATE_CHANGE Subtype
This record is used to encode state changes in the BGP finite state This message is used to encode state changes in the BGP finite state
machine. The BGP FSM states are encoded in the Old State and New machine. The BGP Finite State Machine (FSM) states are encoded in
State fields to indicate the previous and current state. In some the Old State and New State fields to indicate the previous and
cases, the Peer AS number may be undefined. In such cases, the value current state. In some cases, the Peer AS number may be undefined.
of this field may be set to zero. The format is illustrated below: In such cases, the value of this field MAY be set to zero. The
format is illustrated below:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer AS number | Local AS number | | Peer AS number | Local AS number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Index | Address Family | | Interface Index | Address Family |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer IP address (variable) | | Peer IP address (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local IP address (variable) | | Local IP address (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Old State | New State | | Old State | New State |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 9: BGP4MP_STATE_CHANGE Subtype Figure 11: BGP4MP_STATE_CHANGE Subtype
The FSM states are defined in RFC 4271 [RFC4271], Section 8.2.2. The FSM states are defined in RFC 4271 [RFC4271], Section 8.2.2.
Both the old state value and the new state value are encoded as Both the old state value and the new state value are encoded as
2-octet numbers. The state values are defined numerically as 2-octet numbers. The state values are defined numerically as
follows: follows:
1 Idle 1 Idle
2 Connect 2 Connect
3 Active 3 Active
4 OpenSent 4 OpenSent
skipping to change at page 16, line 27 skipping to change at page 16, line 27
The BGP4MP_STATE_CHANGE message also includes interface index and The BGP4MP_STATE_CHANGE message also includes interface index and
Address Family fields. The interface index provides the interface Address Family fields. The interface index provides the interface
number of the peering session. The index value is OPTIONAL and MAY number of the peering session. The index value is OPTIONAL and MAY
be zero if unknown or unsupported. The Address Family indicates what be zero if unknown or unsupported. The Address Family indicates what
types of addresses are in the the address fields. At present, the types of addresses are in the the address fields. At present, the
following AFI Types are supported: following AFI Types are supported:
1 AFI_IPv4 1 AFI_IPv4
2 AFI_IPv6 2 AFI_IPv6
5.4.2. BGP4MP_MESSAGE Subtype 4.4.2. BGP4MP_MESSAGE Subtype
This Subtype is used to encode BGP Messages. It can be used to This Subtype is used to encode BGP messages. It can be used to
encode any Type of BGP message. The entire BGP message is encode any Type of BGP message. The entire BGP message is
encapsulated in the BGP Message field, including the 16-octet marker, encapsulated in the BGP Message field, including the 16-octet marker,
the 2-octet length, and the 1-octet type fields. Note that the the 2-octet length, and the 1-octet type fields. The BGP4MP_MESSAGE
BGP4MP_MESSAGE Subtype does not support 4-Byte AS numbers. Further, Subtype does not support 4-Byte AS numbers. The AS_PATH contained in
the AS_PATH contained in these messages MUST only consist of 2-Byte these messages MUST only consist of 2-Byte AS numbers. The
AS numbers. The BGP4MP_MESSAGE_AS4 Subtype updates the BGP4MP_MESSAGE_AS4 Subtype updates the BGP4MP_MESSAGE Subtype in
BGP4MP_MESSAGE Subtype in order to support 4-Byte AS numbers. The order to support 4-Byte AS numbers. The BGP4MP_MESSAGE fields are
BGP4MP_MESSAGE fields are shown below: shown below:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer AS number | Local AS number | | Peer AS number | Local AS number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Index | Address Family | | Interface Index | Address Family |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer IP address (variable) | | Peer IP address (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local IP address (variable) | | Local IP address (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Message... (variable) | BGP Message... (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 10: BGP4MP_MESSAGE Subtype Figure 12: BGP4MP_MESSAGE Subtype
The interface index provides the interface number of the peering The interface index provides the interface number of the peering
session. The index value is OPTIONAL and MAY be zero if unknown or session. The index value is OPTIONAL and MAY be zero if unknown or
unsupported. The Address Family indicates what types of addresses unsupported. The Address Family indicates what types of addresses
are in the the subsequent address fields. At present, the following are in the the subsequent address fields. At present, the following
AFI Types are supported: AFI Types are supported:
1 AFI_IPv4 1 AFI_IPv4
2 AFI_IPv6 2 AFI_IPv6
Note that the Address Family value only applies to the IP addresses The Address Family value only applies to the IP addresses contained
contained in the MRT header. The BGP4MP_MESSAGE Subtype is otherwise in the MRT header. The BGP4MP_MESSAGE Subtype is otherwise
transparent to the contents of the actual message which may contain transparent to the contents of the actual message which may contain
any valid AFI/SAFI values. Only one BGP message may be encoded in any valid AFI/SAFI values. Only one BGP message SHALL be encoded in
the BGP4MP_MESSAGE Subtype. the BGP4MP_MESSAGE Subtype.
5.4.3. BGP4MP_MESSAGE_AS4 Subtype 4.4.3. BGP4MP_MESSAGE_AS4 Subtype
This Subtype updates the BGP4MP_MESSAGE Subtype to support 4-Byte This Subtype updates the BGP4MP_MESSAGE Subtype to support 4-Byte AS
Autonomous System numbers. The BGP4MP_MESSAGE_AS4 Subtype is numbers. The BGP4MP_MESSAGE_AS4 Subtype is otherwise identical to
otherwise identical to the BGP4MP_MESSAGE Subtype. The AS_PATH in the BGP4MP_MESSAGE Subtype. The AS_PATH in these messages MUST only
these messages MUST only consist of 4-Byte AS numbers. The consist of 4-Byte AS numbers. The BGP4MP_MESSAGE_AS4 fields are
BGP4MP_MESSAGE_AS4 fields are shown below: shown below:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer AS number | | Peer AS number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local AS number | | Local AS number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Index | Address Family | | Interface Index | Address Family |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer IP address (variable) | | Peer IP address (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local IP address (variable) | | Local IP address (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Message... (variable) | BGP Message... (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 11: BGP4MP_MESSAGE_AS4 Subtype Figure 13: BGP4MP_MESSAGE_AS4 Subtype
5.4.4. BGP4MP_STATE_CHANGE_AS4 Subtype 4.4.4. BGP4MP_STATE_CHANGE_AS4 Subtype
This Subtype updates the BGP4MP_STATE_CHANGE Subtype to support This Subtype updates the BGP4MP_STATE_CHANGE Subtype to support
4-Byte Autonomous System numbers. As with the BGP4MP_STATE_CHANGE 4-Byte AS numbers. As with the BGP4MP_STATE_CHANGE Subtype, the BGP
Subtype, the BGP FSM states are encoded in the Old State and New FSM states are encoded in the Old State and New State fields to
State fields to indicate the previous and current state. Aside from indicate the previous and current state. Aside from the extension of
the extension of the peer and local AS fields to 4-Bytes, this the peer and local AS fields to 4-Bytes, this subtype is otherwise
subtype is otherwise identical to the BGP4MP_STATE_CHANGE Subtype. identical to the BGP4MP_STATE_CHANGE Subtype. The
The BGP4MP_STATE_CHANGE_AS4 fields are shown below: BGP4MP_STATE_CHANGE_AS4 fields are shown below:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer AS number | | Peer AS number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local AS number | | Local AS number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Index | Address Family | | Interface Index | Address Family |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer IP address (variable) | | Peer IP address (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local IP address (variable) | | Local IP address (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Old State | New State | | Old State | New State |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 12: BGP4MP_STATE_CHANGE_AS4 Subtype Figure 14: BGP4MP_STATE_CHANGE_AS4 Subtype
5.4.5. BGP4MP_MESSAGE_LOCAL Subtype 4.4.5. BGP4MP_MESSAGE_LOCAL Subtype
Implementations of MRT have largely focused on collecting remotely Implementations of MRT have largely focused on collecting remotely
generated BGP messages in a passive route collector role. However, generated BGP messages in a passive route collector role. However,
for active BGP implementations, it can be useful to archive locally for active BGP implementations, it can be useful to archive locally
generated BGP messages in addition to remote messages. This subtype generated BGP messages in addition to remote messages. This subtype
is added to indicated a locally generated BGP message. The fields is added to indicated a locally generated BGP message. The fields
remain identical to the BGP4MP_MESSAGE type including the Peer and remain identical to the BGP4MP_MESSAGE type including the Peer and
Local IP and AS fields. The Local fields continue to refer to the Local IP and AS fields. The Local fields continue to refer to the
local IP and AS number of the collector which generated the message local IP and AS number of the collector which generated the BGP
and the Peer IP and AS fields refer to the receipient of the message and the Peer IP and AS fields refer to the recipient of the
generated BGP messages. generated BGP messages.
5.4.6. BGP4MP_MESSAGE_AS4_LOCAL Subtype 4.4.6. BGP4MP_MESSAGE_AS4_LOCAL Subtype
As with the BGP4MP_MESSAGE_LOCAL type, this type indicate locally As with the BGP4MP_MESSAGE_LOCAL type, this type indicate locally
generated messages. The fields are identical to the generated messages. The fields are identical to the
BGP4MP_MESSAGE_AS4 message type. BGP4MP_MESSAGE_AS4 message type.
5.5. BGP4MP_ET Type 4.5. ISIS Type
This type extends the MRT common header field to include a 32BIT
microsecond timestamp field. The type and subtype field definitions
remain as defined for the BGP4MP Type. The 32BIT microsecond
timestamp immediately follows the length field in the MRT common
header and precedes all other fields in the message. The 32BIT
microsecond field is included in the computation of the length field
value. The MRT common header modification is illustrated below.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Subtype |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| microsecond timestamp |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message... (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 13: BGP4MP_ET Type
5.6. ISIS Type
This Type supports the IS-IS routing protocol as defined in RFC 1195 This Type supports the IS-IS routing protocol as defined in RFC 1195
[RFC1195]. There is no Type specific header for the ISIS Type. The [RFC1195]. There is no Type specific header for the ISIS Type. The
Subtype code for this Type is undefined. The ISIS PDU directly Subtype code for this Type is undefined. The ISIS PDU directly
follows the MRT common header fields. follows the MRT Common Header fields.
5.7. ISIS_ET Type
The ISIS_ET Type extends the ISIS Type to support microsecond
timestamps. As with the BGP4MP_ET Type, a 32BIT microsecond
timestamp field is appended to the MRT common header after the length
field. The ISIS_ET Type is otherwise identical to the ISIS Type.
5.8. OSPFv3 Type 4.6. OSPFv3 Type
The OSPFv3 Type extends the original OSPF Type to support IPv6 The OSPFv3 Type extends the original OSPFv2 Type to support IPv6
addresses for the OSPFv3 protocol as defined in RFC 5340 [RFC5340]. addresses for the OSPFv3 protocol as defined in RFC 5340 [RFC5340].
The format of the MRT Message field for the OSPFv3 Type is as The format of the MRT Message field for the OSPFv3 Type is as
follows: follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address Family | | Address Family |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remote IP address (variable) | | Remote IP address (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local IP address (variable) | | Local IP address (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OSPF Message Contents (variable) | OSPF Message Contents (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 14: OSPFv3 Type Figure 15: OSPFv3 Type
5.9. OSPFv3_ET Type
The OSPFv3_ET Type extends the OSPFv3 Type to support microsecond
timestamps. As with the BGP4MP_ET Type, a 32BIT microsecond
timestamp field is appended to the MRT common header after the length
field and its length is included in the calculation of the length
field value. The OSPFv3_ET Type is otherwise identical to the OSPFv3
Type.
6. Acknowledgements
The initial MRT specification was developed by Craig Labovitz for use
in the Multi-thread Routing Toolkit (MRT) project. The BGP4MP Type
was introduced in the Zebra routing software project by Kunihiro
Ishiguro. The BGP4MP_ET, ISIS, and ISIS_ET Types were defined in the
Python Routeing Toolkit (PyRT) developed by Richard Mortier while at
Sprint Advanced Technology Labs.
7. IANA Considerations
This section provides guidance to the Internet Assigned Numbers
Authority (IANA) regarding registration of values related to the MRT
specification, in accordance with BCP 26, RFC 5226 [RFC5226].
There are two name spaces in MRT that require registration: Type
Codes and Subtype Codes.
MRT is not intended as a general-purpose specification for protocol
information export, and allocations should not be made for purposes
unrelated to routing protocol information export.
The following policies are used here with the meanings defined in BCP
26: "Specification Required", "IETF Consensus", "Experimental Use",
"First Come First Served".
7.1. Type Codes
Type Codes have a range from 0 to 65535, of which 1-64 have been
allocated. New Type Codes MUST be allocated starting at 65. Type
Codes 65 - 511 are to be assigned by IETF Review. Type Codes 512 -
2047 are assigned based on Specification Required. Type Codes 2048 -
64511 are available on a First Come First Served policy. Type Codes
64512 - 65534 are available for Experimental Use. The Type Code
Values of 0 and 65535 are reserved.
7.2. Subtype Codes 5. IANA Considerations
Subtype Codes have a range from 0 to 65535. Subtype definitions are This document has no IANA actions.
specific to a particular Type Code definition. New Subtype Code
definition must reference an existing Type Code to which the Subtype
belongs. Subtype assignmnents to Type Codes 0 - 511 are to be
assigned by IETF Review. Subtype assignments for the remaning Type
Codes follow the assignment rules for the Type Codes to which they
belong.
8. Security Considerations 6. Security Considerations
The MRT Format utilizes a structure which can store routing protocol The MRT Format utilizes a structure which can store routing protocol
information data. The fields defined in the MRT specification are of information data. The fields defined in the MRT specification are of
a descriptive nature and provide information that is useful to a descriptive nature and provide information that is useful to
facilitate the analysis of routing data. As such, the fields facilitate the analysis of routing data. As such, the fields
currently defined in the MRT specification do not in themselves currently defined in the MRT specification do not in themselves
create additional security risks, since the fields are not used to create additional security risks, since the fields are not used to
induce any particular behavior by the recipient application. induce any particular behavior by the recipient application.
9. References Some information contained in an MRT data structure might be
considered sensitive or private. For example, a BGP peer that sends
a message to an MRT-enabled router might not expect that message to
be shared beyond the AS to which it is sent. The proposed
geolocation extension to MRT could reveal the location of an MRT
router's peers [I- D.ietf-grow-geomrt]. An organization that intends
to use the MRT structure to export routing information beyond the
domain where it normally accessible (e.g., publishing MRT dumps for
use by researchers) should verify with any peers whose information
might be included, and possibly remove sensitive fields.
9.1. Normative References 7. References
7.1. Normative References
[IANA-AF] "Address Family Numbers",
<http://www.iana.org/numbers.html>.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
September 1981.
[RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and [RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and
dual environments", RFC 1195, December 1990. dual environments", RFC 1195, December 1990.
[RFC2080] Malkin, G. and R. Minnear, "RIPng for IPv6", RFC 2080,
January 1997.
[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.
[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998.
[RFC2453] Malkin, G., "RIP Version 2", STD 56, RFC 2453, [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
November 1998. (IPv6) Specification", RFC 2460, December 1998.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, November 2003.
[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.
[RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
"Multiprotocol Extensions for BGP-4", RFC 4760, "Multiprotocol Extensions for BGP-4", RFC 4760,
January 2007. January 2007.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
[RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF [RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF
for IPv6", RFC 5340, July 2008. for IPv6", RFC 5340, July 2008.
9.2. Informative References 7.2. Informative References
[IEEE.P1003.1-1990]
Institute of Electrical and Electronics Engineers,
"P1003.1, Information Technology Portable Operating System
Interface (POSIX) Part 1: System Application Program
Interface (API) [C Language], 1990.", IEEE Standard
P1003.1.
[MRT PROG GUIDE] [MRT PROG 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>.
Appendix A. Deprecated MRT types [RFC2080] Malkin, G. and R. Minnear, "RIPng for IPv6", RFC 2080,
January 1997.
[RFC2453] Malkin, G., "RIP Version 2", STD 56, RFC 2453,
November 1998.
Appendix A. MRT Encoding Examples
This appendix, which is not a normative reference, contains a MRT
encoding examples.
The following example shows the encoding for a MRT record type of
BGP4MP and subtype BGP4MP_MESSAGE_AS4. The Peer AS and Local AS
numbers are encoded in 4 bytes fields due to the use of the
BGP4MP_MESSAGE_AS4 subtype. The encoded BGP Update is shown in
hexadecimal. The AS numbers in the ASPATH in the BGP Update are
encoded as 4 byte values in accord with the MRT BGP4MP_MESSAGE_AS4
subtype.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp = 1300475700 epoch sec (2011-03-18 19:15:00) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 16 | Subtype = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length = 82 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer AS = 64496 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local AS = 64497 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Index = 0 | Address Family = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer IP address = 192.0.2.85 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local IP address = 198.51.100.4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Update =
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
00 3e 02 00 00 00 1f 40 01 01 02 40 02 0e 02 03
00 00 fb f0 00 00 fb ff 00 00 fb f6 40 03 04 c6
33 64 55 c0 08 04 fb f0 00 0e 18 cb 00 71
Figure 16: MRT BGP4MP_MESSAGE_AS4 Example
The contents of the BGP Update Message above are as follows:
ORIGIN: INCOMPLETE
ASPATH: 64496 64511 64502
NEXT_HOP: 198.51.100.188
COMMUNITY: 64496:14
NLRI: 203.0.113.0/24
Figure 17: BGP Message Contents
The following example displays the encoding for a MRT record type of
TABLE_DUMP_V2 and subtype PEER_INDEX_TABLE. The table in this
example contains 2 entries.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp = 1300475700 epoch sec (2011-03-18 19:15:00) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 13 | Subtype = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length = 34 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Collector BGP ID = 198.51.100.4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| View Name Length = 0 | Peer Count = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Type = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer BGP ID = 198.51.100.5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer IP address = 198.51.100.5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer AS = 65541 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Type = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer BGP ID = 192.0.2.33 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer IP address = 192.0.2.33 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer AS = 65542 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 18: MRT PEER_INDEX_TABLE Example
The following example displays the encoding for a MRT record type of
TABLE_DUMP_V2 and subtype RIB_IPV6_UNICAST. This entry applies to
the NLRI prefix of 2001:0DB8::/32. There is a single entry for this
prefix. The entry applies to the peer identified by index location
15 in a preceding MRT PEER_INDEX_TABLE record.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp = 1300475700 epoch sec (2011-03-18 19:15:00) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 13 | Subtype = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length = 87 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence number = 42 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Preflen = 32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Prefix = 2001:0DB8::/32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Entry Count = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Index = 15 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Originated Time = 1300475700 epoch sec (2011-03-18 19:15:00) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Attribute Length = 68 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Path Attributes =
40 01 01 00 50 02 00 0e 02 03 00 00 fb f0 00 00
fb ff 00 00 fb f6 80 0e 2b 00 02 01 20 20 01 0d
b8 00 0d 00 ff 00 00 00 00 00 00 01 87 fe 80 00
00 00 00 00 00 02 12 f2 ff fe 9f 1b 00 00 00 20
20 01 0d b8
Figure 19: MRT RIB_IPV6_UNICAST Example
The contents of the BGP Path Attribute field above are as follows:
ORIGIN: IGP
ASPATH: 64496 64511 64502
MP_REACH_NLRI(IPv6 Unicast)
NEXT_HOP: 2001:db8:d:ff::187
NEXT_HOP: fe80::212:f2ff:fe9f:1b00
NLRI: 2001:0DB8::/32
Figure 20: BGP Path Attribute contents
Appendix B. Deprecated MRT Types
This Appendix lists deprecated MRT types. These types are documented This Appendix lists deprecated MRT types. These types are documented
for informational purposes only. While documented in some for informational purposes.
references, they are not known to have been generally implemented.
A.1. Deprecated MRT Informational Types B.1. Deprecated MRT Informational Types
The deprecated MRT Informational Types are defined below: The initial MRT format defined five Informational Type records.
These records were intended to signal the state of an MRT data
collector and do not contain routing information. These records were
intended for use when MRT records were sent over a network to a
remote repository store. However, MRT record repository stores have
traditionally resided on the same device as the collector and these
Informational Types are not known to be implemented. Further,
transport mechanisms for MRT records are considered to be outside the
scope of this document.
The message field MAY contain an OPTIONAL string for diagnostic
purposes. The message string encoding MUST follow the UTF-8
transformation format [RFC3629]. The Subtype field is unused for
these Types and SHOULD be set to 0.
The MRT Informational Types are defined below:
0 NULL 0 NULL
1 START
2 DIE 2 DIE
3 I_AM_DEAD
4 PEER_DOWN 4 PEER_DOWN
A.1.1. NULL Type B.1.1. NULL Type
The NULL Type message causes no operation. The NULL Type message causes no operation.
A.1.2. DIE Type B.1.2. START Type
The DIE Type signals a remote MRT repository it should stop accepting The START Type indicates a collector is about to begin generating MRT
records.
B.1.3. DIE Type
The DIE Type signals a remote MRT repository it SHOULD stop accepting
messages. messages.
A.1.3. PEER_DOWN Type B.1.4. I_AM_DEAD Type
An I_AM_DEAD MRT record indicates that a collector has shut down and
has stopped generating MRT records.
B.1.5. PEER_DOWN Type
The PEER_DOWN message was intended to indicate that a collector had The PEER_DOWN message was intended to indicate that a collector had
lost association with a BGP peer. However, the MRT format provides lost association with a BGP peer. However, the MRT format provides
BGP state change message types which duplicate this functionality. BGP state change message types which duplicate this functionality.
A.2. Deprecated MRT Routing Information Types B.2. Other Deprecated MRT Types
5 BGP 5 BGP
6 RIP 6 RIP
7 IDRP 7 IDRP
8 RIPNG 8 RIPNG
9 BGP4PLUS 9 BGP4PLUS
10 BGP4PLUS_01 10 BGP4PLUS_01
A.2.1. BGP Type B.2.1. BGP Type
The BGP Type indicates the Message field contains BGP routing The BGP Type indicates the Message field contains BGP routing
information. The BGP routing protocol is defined in RFC 4271 information. The BGP routing protocol is defined in RFC 4271
[RFC4271]. The information in the message is dependent on the [RFC4271]. The information in the message is dependent on the
Subtype value. The BGP Type and all associated Subtypes below are Subtype value. The BGP Type and all associated Subtypes below are
considered to be deprecated by the BGP4MP Type. considered to be deprecated by the BGP4MP Type.
The following BGP Subtypes are defined for the MRT BGP Type. As with The following BGP Subtypes are defined for the MRT BGP Type. As with
the BGP Type itself, they are all considered to be deprecated. the BGP Type itself, they are all considered to be deprecated.
0 BGP_NULL 0 BGP_NULL
1 BGP_UPDATE 1 BGP_UPDATE
2 BGP_PREF_UPDATE 2 BGP_PREF_UPDATE
3 BGP_STATE_CHANGE 3 BGP_STATE_CHANGE
4 BGP_SYNC 4 BGP_SYNC
5 BGP_OPEN 5 BGP_OPEN
6 BGP_NOTIFY 6 BGP_NOTIFY
7 BGP_KEEPALIVE 7 BGP_KEEPALIVE
A.2.1.1. BGP_NULL Subtype B.2.1.1. BGP_NULL Subtype
The BGP_NULL Subtype is a reserved Subtype. The BGP_NULL Subtype is a reserved Subtype.
A.2.1.2. BGP_UPDATE Subtype B.2.1.2. BGP_UPDATE Subtype
The BGP_UPDATE Subtype is used to encode BGP UPDATE messages. The The BGP_UPDATE Subtype is used to encode BGP UPDATE messages. The
format of the MRT Message field for this Subtype is as follows: format of the MRT Message field for this Subtype is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer AS number | | Peer AS number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer IP address | | Peer IP address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local AS number | | Local AS number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local IP address | | Local IP address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP UPDATE Contents (variable) | BGP UPDATE Contents (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 15: BGP_UPDATE Subtype Figure 21: BGP_UPDATE Subtype
The BGP UPDATE Contents include the entire BGP UPDATE message which The BGP UPDATE Contents include the entire BGP UPDATE message which
follows the BGP Message Header. The BGP Message Header itself is not follows the BGP Message Header. The BGP Message Header itself is not
included. The Peer AS number and IP address fields contain the AS included. The Peer AS number and IP address fields contain the AS
number and IP address of the remote system which are generating the number and IP address of the remote system which are generating the
BGP UPDATE messages. The Local AS number and IP address fields BGP UPDATE messages. The Local AS number and IP address fields
contain the AS number and IP address of the local collector system contain the AS number and IP address of the local collector system
which is archiving the messages. which is archiving the messages.
A.2.1.3. BGP_PREF_UPDATE Subtype B.2.1.3. BGP_PREF_UPDATE Subtype
The BGP_PREF_UPDATE Subtype is not defined. The BGP_PREF_UPDATE Subtype is not defined.
A.2.1.4. BGP_STATE_CHANGE Subtype B.2.1.4. BGP_STATE_CHANGE Subtype
The BGP_STATE_CHANGE Subtype is used to record changes in the BGP The BGP_STATE_CHANGE Subtype is used to reflect changes in the BGP
finite state machine. These FSM states are defined in RFC 4271 finite state machine. These FSM states are defined in RFC 4271
[RFC4271], Section 8.2.2. Both the old state value and the new state [RFC4271], Section 8.2.2. Both the old state value and the new state
value are encoded as 2-octet numbers. The state values are defined value are encoded as 2-octet numbers. The state values are defined
numerically as follows: numerically as follows:
1 Idle 1 Idle
2 Connect 2 Connect
3 Active 3 Active
4 OpenSent 4 OpenSent
5 OpenConfirm 5 OpenConfirm
skipping to change at page 27, line 33 skipping to change at page 30, line 15
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer AS number | | Peer AS number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer IP address | | Peer IP address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Old State | New State | | Old State | New State |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 16: BGP_STATE_CHANGE Subtype Figure 22: BGP_STATE_CHANGE Subtype
A.2.1.5. BGP_SYNC Subtype B.2.1.5. BGP_SYNC Subtype
The BGP_SYNC Subtype was intended to convey a system file name where The BGP_SYNC Subtype was intended to convey a system file name where
BGP Table Dump messages should be recorded. The View # was to BGP Table Dump messages MAY be recorded. The View # was to
correspond to the View # provided in the TABLE_DUMP Type messages. correspond to the View # provided in the TABLE_DUMP Type records.
There are no known implementations of this subtype and it SHOULD be There are no known implementations of this subtype and it SHOULD be
ignored. The following format applies to this Subtype: ignored. The following format applies to this Subtype:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| View # | | View # |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| File Name... (variable) | File Name... (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 17: BGP_SYNC Subtype Figure 23: BGP_SYNC Subtype
The File Name is terminated with a NULL (0) character. The File Name is terminated with a NULL (0) character.
A.2.1.6. BGP_OPEN Subtype B.2.1.6. BGP_OPEN Subtype
The BGP_OPEN Subtype is used to encode BGP OPEN messages. The format The BGP_OPEN Subtype is used to encode BGP OPEN messages. The format
of the MRT Message field for this Subtype is the same as the of the MRT Message field for this Subtype is the same as the
BGP_UPDATE, however, the last field contains the contents of the BGP BGP_UPDATE, however, the last field contains the contents of the BGP
OPEN message. OPEN message.
A.2.1.7. BGP_NOTIFY Subtype B.2.1.7. BGP_NOTIFY Subtype
The BGP_NOTIFY Subtype is used to encode BGP NOTIFICATION messages. The BGP_NOTIFY Subtype is used to encode BGP NOTIFICATION messages.
The format of the MRT Message field for this Subtype is the same as The format of the MRT Message field for this Subtype is the same as
the BGP_UPDATE, however, the last field contains the contents of the the BGP_UPDATE, however, the last field contains the contents of the
BGP NOTIFICATION message. BGP NOTIFICATION message.
A.2.1.8. BGP_KEEPALIVE Subtype B.2.1.8. BGP_KEEPALIVE Subtype
The BGP_KEEPALIVE Subtype is used to encode BGP KEEPALIVE messages. The BGP_KEEPALIVE Subtype is used to encode BGP KEEPALIVE messages.
The format of the MRT Message field for this Subtype is the same as The format of the MRT Message field for this Subtype is the same as
the BGP_UPDATE, however, the last field contains no information. the BGP_UPDATE, however, the last field contains no information.
A.2.2. RIP Type B.2.2. RIP Type
The RIP Type is used to export RIP protocol packets as defined in RFC The RIP Type is used to export RIP protocol packets as defined in RFC
2453 [RFC2453]. The Subtype field is currently reserved for this 2453 [RFC2453]. The Subtype field is currently reserved for this
Type and SHOULD be set to 0. Type and SHOULD be set to 0.
The format of the MRT Message field for the RIP Type is as follows: The format of the MRT Message field for the RIP Type is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer IP address | | Peer IP address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local IP address | | Local IP address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RIP Message Contents (variable) | RIP Message Contents (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 18: RIP Type Figure 24: RIP Type
A.2.3. IDRP Type B.2.3. IDRP Type
The IDRP Type is used to export Inter-Domain-Routing Protocol (IDRP) The IDRP Type was intended to be used to export Inter-Domain-Routing
protocol information as defined in the ISO/IEC 10747 standard. The Protocol (IDRP) protocol information as defined in the ISO/IEC 10747
Subtype field is unused. This Type is deprecated due to lack of standard. However, this Type has seen no known use and there are no
deployment of IDRP. details on protocol encoding for this Type.
A.2.4. RIPNG Type B.2.4. RIPNG Type
The RIPNG Type is used to export RIPNG protocol packets as defined in The RIPNG Type is used to export RIPNG protocol packets as defined in
RFC 2080 [RFC2080]. The RIPNG protocol updates the RIP protocol to RFC 2080 [RFC2080]. The RIPNG protocol updates the RIP protocol to
support IPv6. The Subtype field is currently reserved for this Type support IPv6. The Subtype field is currently reserved for this Type
and SHOULD be set to 0. and SHOULD be set to 0.
The format of the MRT Message field for the RIPNG Type is as follows: The format of the MRT Message field for the RIPNG Type is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
skipping to change at page 29, line 28 skipping to change at page 32, line 19
~ Peer IPv6 address ~ ~ Peer IPv6 address ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Local IPv6 address ~ ~ Local IPv6 address ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RIPNG Message Contents (variable) | RIPNG Message Contents (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 19: RIPNG Type Figure 25: RIPNG Type
A.2.5. BGP4PLUS and BGP4PLUS_01 Types B.2.5. BGP4PLUS and BGP4PLUS_01 Types
The BGP4PLUS and BGP4PLUS_01 Types were defined to support IPv6 BGP The BGP4PLUS and BGP4PLUS_01 Types were defined to support IPv6 BGP
routing information. The BGP4PLUS Type was specified based on the routing information. The BGP4PLUS Type was specified based on the
initial Internet Draft for Multiprotocol Extensions to BGP-4. The initial Internet Draft for Multiprotocol Extensions to BGP-4. The
BGP4PLUS_01 Type was specified to correspond to the -01 revision of BGP4PLUS_01 Type was specified to correspond to the -01 revision of
this Internet Draft. The two Types share the same definitions in this Internet Draft. The two Types share the same definitions in
terms of their MRT format specifications. terms of their MRT format specifications.
The Subtype field definitions are shared with the BGP Type, however, The Subtype field definitions are shared with the BGP Type, however,
the address fields in the BGP_UPDATE, BGP_OPEN, BGP_NOTIFY, the address fields in the BGP_UPDATE, BGP_OPEN, BGP_NOTIFY,
BGP_KEEPALIVE, and BGP_STATE_CHANGE Subtype messages are extended to BGP_KEEPALIVE, and BGP_STATE_CHANGE Subtype records are extended to
16 octets for IPv6 addresses. As with the BGP Type, the BGP4PLUS and 16 octets for IPv6 addresses. As with the BGP Type, the BGP4PLUS and
BGP4PLUS_01 Types are deprecated as they superseded by the BGP4MP BGP4PLUS_01 Types are deprecated as they superseded by the BGP4MP
Type. Type.
A.2.6. Deprecated BGP4MP Subtypes B.2.6. Deprecated BGP4MP Subtypes
The following two subtypes of the BGP4MP Type are considered to be The following two subtypes of the BGP4MP Type are considered to be
deprecated. deprecated.
2 BGP4MP_ENTRY 2 BGP4MP_ENTRY
3 BGP4MP_SNAPSHOT 3 BGP4MP_SNAPSHOT
A.2.6.1. BGP4MP_ENTRY Subtype B.2.6.1. BGP4MP_ENTRY Subtype
This Subtype is similar to the TABLE_DUMP Type and is used to record This Subtype is similar to the TABLE_DUMP Type and is used to record
RIB table entries. It extends the TABLE_DUMP Type to include true RIB table entries. It was intended to include true multiprotocol
multiprotocol support. However, this Type does not support 4-Byte AS support. However, this Subtype does not support 4-Byte AS numbers
numbers and has not been widely implemented. This Type is deprecated and has not been widely implemented.
in favor of the TABLE_DUMP_V2 which includes 4-Byte AS number support
and a more compact format.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer AS number | Local AS number | | Peer AS number | Local AS number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Index | Address Family | | Interface Index | Address Family |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer IP address (variable) | | Peer IP address (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 30, line 42 skipping to change at page 33, line 33
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Prefix Length | | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address Prefix (variable) | | Address Prefix (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Attribute Length | | Attribute Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Attribute... (variable) | BGP Attribute... (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 20: BGP4MP_ENTRY Subtype Figure 26: BGP4MP_ENTRY Subtype
A.2.6.2. BGP4MP_SNAPSHOT Subtype B.2.6.2. BGP4MP_SNAPSHOT Subtype
This Subtype was intended to convey a system file name where This Subtype was intended to convey a system file name where
BGP4MP_ENTRY messages should be recorded. It is similar to the BGP4MP_ENTRY records MAY be recorded. It is similar to the BGP_SYNC
BGP_SYNC message Subtype and is deprecated. Subtype and is deprecated.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| View # | | View # |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| File Name... (variable) | File Name... (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 21: BGP4MP_SNAPSHOT Subtype Figure 27: BGP4MP_SNAPSHOT Subtype
Appendix C. Acknowledgements
The initial MRT specification was developed by Craig Labovitz for use
in the Multi-thread Routing Toolkit (MRT) project. The BGP4MP Type
was introduced in the Zebra routing software project by Kunihiro
Ishiguro. The BGP4MP_ET, ISIS, and ISIS_ET Types were defined in the
Python Routeing Toolkit (PyRT) developed by Richard Mortier while at
Sprint Advanced Technology Labs.
Authors' Addresses Authors' Addresses
Larry Blunk Larry Blunk
Merit Network Merit Network
Email: ljb@merit.edu Email: ljb@merit.edu
Manish Karir Manish Karir
Merit Network Merit Network
 End of changes. 130 change blocks. 
374 lines changed or deleted 536 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/