draft-ietf-grow-mrt-16.txt   draft-ietf-grow-mrt-17.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: Standards Track Merit Network
Expires: February 18, 2012 C. Labovitz Expires: February 18, 2012 C. Labovitz
Deepfield Networks Deepfield Networks
August 17, 2011 August 17, 2011
MRT routing information export format MRT routing information export format
draft-ietf-grow-mrt-16.txt draft-ietf-grow-mrt-17.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 21, line 7 skipping to change at page 21, line 7
definitions must reference an existing Type Code to which the Subtype definitions must reference an existing Type Code to which the Subtype
belongs. Subtype assignments follow the assignment rules for the belongs. Subtype assignments follow the assignment rules for the
Type Codes to which they belong. Type Codes to which they belong.
5.3. Defined Type Codes 5.3. Defined Type Codes
This document defines the following message Type Codes: This document defines the following message Type Codes:
Name Value Definition Name Value Definition
---- ----- ---------- ---- ----- ----------
NULL 0 NULL 0 See Section B.1.1
START 1 START 1 See Section B.1.2
DIE 2 DIE 2 See Section B.1.3
I_AM_DEAD 3 I_AM_DEAD 3 See Section B.1.4
PEER_DOWN 4 PEER_DOWN 4 See Section B.1.5
BGP 5 BGP 5 See Section B.2.1
RIP 6 RIP 6 See Section B.2.2
IDRP 7 IDRP 7 See Section B.2.3
RIPNG 8 RIPNG 8 See Section B.2.4
BGP4PLUS 9 BGP4PLUS 9 See Section B.2.5
BGP4PLUS_01 10 BGP4PLUS_01 10 See Section B.2.5
OSPFv2 11 See Section 4.2 OSPFv2 11 See Section 4.1
TABLE_DUMP 12 See Section 4.3 TABLE_DUMP 12 See Section 4.2
TABLE_DUMP_v2 13 See Section 4.5 TABLE_DUMP_v2 13 See Section 4.3
BGP4MP 16 See Section 4.4 BGP4MP 16 See Section 4.4
BGP4MP_ET 17 See Section 4.4 BGP4MP_ET 17 See Section 4.4
ISIS 32 See Section 4.4 ISIS 32 See Section 4.5
ISIS_ET 33 See Section 4.4 ISIS_ET 33 See Section 4.5
OSPFv3 48 See Section 4.4 OSPFv3 48 See Section 4.6
OSPFv3_ET 49 See Section 4.4 OSPFv3_ET 49 See Section 4.6
5.4. Defined BGP, BGP4PLUS, and BGP4PLUS_01 Subtype Codes 5.4. Defined BGP, BGP4PLUS, and BGP4PLUS_01 Subtype Codes
This document defines the following message Subtype Codes for the This document defines the following message Subtype Codes for the
BGP, BGP4PLUS, and BGP4PLUS_01 Types: BGP, BGP4PLUS, and BGP4PLUS_01 Types:
Name Value Definition Name Value Definition
---- ----- ---------- ---- ----- ----------
BGP_NULL 0 BGP_NULL 0 See Section B.2.1
BGP_UPDATE 1 BGP_UPDATE 1 See Section B.2.1
BGP_PREF_UPDATE 2 BGP_PREF_UPDATE 2 See Section B.2.1
BGP_STATE_CHANGE 3 BGP_STATE_CHANGE 3 See Section B.2.1
BGP_SYNC 4 BGP_SYNC 4 See Section B.2.1
BGP_OPEN 5 BGP_OPEN 5 See Section B.2.1
BGP_NOTIFY 6 BGP_NOTIFY 6 See Section B.2.1
BGP_KEEPALIVE 7 BGP_KEEPALIVE 7 See Section B.2.1
5.5. Defined TABLE_DUMP Subtype Codes 5.5. Defined TABLE_DUMP Subtype Codes
This document defines the following message Subtype Codes for the This document defines the following message Subtype Codes for the
TABLE_DUMP Type: TABLE_DUMP Type:
Name Value Definition Name Value Definition
---- ----- ---------- ---- ----- ----------
AFI_IPv4 1 AFI_IPv4 1 See Section 4.2
AFI_IPv6 2 AFI_IPv6 2 See Section 4.2
5.6. Defined TABLE_DUMP_V2 Subtype Codes 5.6. Defined TABLE_DUMP_V2 Subtype Codes
This document defines the following message Subtype Codes for the This document defines the following message Subtype Codes for the
TABLE_DUMP_V2 Type: TABLE_DUMP_V2 Type:
Name Value Definition Name Value Definition
---- ----- ---------- ---- ----- ----------
PEER_INDEX_TABLE 1 PEER_INDEX_TABLE 1 See Section 4.3
RIB_IPV4_UNICAST 2 RIB_IPV4_UNICAST 2 See Section 4.3
RIB_IPV4_MULTICAST 3 RIB_IPV4_MULTICAST 3 See Section 4.3
RIB_IPV6_UNICAST 4 RIB_IPV6_UNICAST 4 See Section 4.3
RIB_IPV6_MULTICAST 5 RIB_IPV6_MULTICAST 5 See Section 4.3
RIB_GENERIC 6 RIB_GENERIC 6 See Section 4.3
5.7. Defined BGP4MP and BGP4MP_ET Subtype Codes 5.7. Defined BGP4MP and BGP4MP_ET Subtype Codes
This document defines the following message Subtype Codes for the This document defines the following message Subtype Codes for the
BGP4MP Type: BGP4MP Type:
Name Value Definition Name Value Definition
---- ----- ---------- ---- ----- ----------
BGP4MP_STATE_CHANGE 0 BGP4MP_STATE_CHANGE 0 See Section 4.4
BGP4MP_MESSAGE 1 BGP4MP_MESSAGE 1 See Section 4.4
BGP4MP_ENTRY 2 BGP4MP_ENTRY 2 See Section 4.4
BGP4MP_SNAPSHOT 3 BGP4MP_SNAPSHOT 3 See Section 4.4
BGP4MP_MESSAGE_AS4 4 BGP4MP_MESSAGE_AS4 4 See Section 4.4
BGP4MP_STATE_CHANGE_AS4 5 BGP4MP_STATE_CHANGE_AS4 5 See Section 4.4
BGP4MP_MESSAGE_LOCAL 6 BGP4MP_MESSAGE_LOCAL 6 See Section 4.4
BGP4MP_MESSAGE_AS4_LOCAL 7 BGP4MP_MESSAGE_AS4_LOCAL 7 See Section 4.4
6. 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.
 End of changes. 7 change blocks. 
43 lines changed or deleted 43 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/