draft-ietf-grow-mrt-09.txt   draft-ietf-grow-mrt-10.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: August 29, 2009 C. Labovitz Expires: January 14, 2010 C. Labovitz
Arbor Networks Arbor Networks
February 25, 2009 July 13, 2009
MRT routing information export format MRT routing information export format
draft-ietf-grow-mrt-09.txt draft-ietf-grow-mrt-10.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 29, 2009. This Internet-Draft will expire on January 14, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 3, line 20 skipping to change at page 3, line 20
4. MRT Informational Types . . . . . . . . . . . . . . . . . . . 8 4. MRT Informational Types . . . . . . . . . . . . . . . . . . . 8
4.1. START Type . . . . . . . . . . . . . . . . . . . . . . . . 8 4.1. START Type . . . . . . . . . . . . . . . . . . . . . . . . 8
4.2. I_AM_DEAD Type . . . . . . . . . . . . . . . . . . . . . . 8 4.2. I_AM_DEAD Type . . . . . . . . . . . . . . . . . . . . . . 8
5. MRT Routing Information Types . . . . . . . . . . . . . . . . 9 5. MRT Routing Information Types . . . . . . . . . . . . . . . . 9
5.1. OSPF Type . . . . . . . . . . . . . . . . . . . . . . . . 9 5.1. OSPF Type . . . . . . . . . . . . . . . . . . . . . . . . 9
5.2. TABLE_DUMP Type . . . . . . . . . . . . . . . . . . . . . 9 5.2. TABLE_DUMP Type . . . . . . . . . . . . . . . . . . . . . 9
5.3. TABLE_DUMP_V2 Type . . . . . . . . . . . . . . . . . . . . 11 5.3. TABLE_DUMP_V2 Type . . . . . . . . . . . . . . . . . . . . 11
5.4. BGP4MP Type . . . . . . . . . . . . . . . . . . . . . . . 13 5.4. BGP4MP Type . . . . . . . . . . . . . . . . . . . . . . . 13
5.4.1. BGP4MP_STATE_CHANGE Subtype . . . . . . . . . . . . . 14 5.4.1. BGP4MP_STATE_CHANGE Subtype . . . . . . . . . . . . . 14
5.4.2. BGP4MP_MESSAGE Subtype . . . . . . . . . . . . . . . . 15 5.4.2. BGP4MP_MESSAGE Subtype . . . . . . . . . . . . . . . . 15
5.4.3. BGP4MP_STATE_CHANGE_AS4 Subtype . . . . . . . . . . . 15 5.4.3. BGP4MP_MESSAGE_AS4 Subtype . . . . . . . . . . . . . . 15
5.4.4. BGP4MP_MESSAGE_AS4 Subtype . . . . . . . . . . . . . . 16 5.4.4. BGP4MP_STATE_CHANGE_AS4 Subtype . . . . . . . . . . . 16
5.5. BGP4MP_ET Type . . . . . . . . . . . . . . . . . . . . . . 17 5.5. BGP4MP_ET Type . . . . . . . . . . . . . . . . . . . . . . 17
5.6. ISIS Type . . . . . . . . . . . . . . . . . . . . . . . . 17 5.6. ISIS Type . . . . . . . . . . . . . . . . . . . . . . . . 17
5.7. ISIS_ET Type . . . . . . . . . . . . . . . . . . . . . . . 17 5.7. ISIS_ET Type . . . . . . . . . . . . . . . . . . . . . . . 17
5.8. OSPFv3 Type . . . . . . . . . . . . . . . . . . . . . . . 17 5.8. OSPFv3 Type . . . . . . . . . . . . . . . . . . . . . . . 17
5.9. OSPFv3_ET Type . . . . . . . . . . . . . . . . . . . . . . 18 5.9. OSPFv3_ET Type . . . . . . . . . . . . . . . . . . . . . . 18
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
6.1. Type Codes . . . . . . . . . . . . . . . . . . . . . . . . 19 6.1. Type Codes . . . . . . . . . . . . . . . . . . . . . . . . 19
6.2. Subtype Codes . . . . . . . . . . . . . . . . . . . . . . 19 6.2. Subtype Codes . . . . . . . . . . . . . . . . . . . . . . 19
7. Security Considerations . . . . . . . . . . . . . . . . . . . 20 7. Security Considerations . . . . . . . . . . . . . . . . . . . 20
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21
skipping to change at page 14, line 9 skipping to change at page 14, line 9
5.4. BGP4MP Type 5.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]. It supersedes the BGP, BGP4PLUS, BGP4PLUS_01 Types.
The BGP4MP Type has six Subtypes which are defined as follows: The BGP4MP Type has six Subtypes which are defined as follows:
0 BGP4MP_STATE_CHANGE 0 BGP4MP_STATE_CHANGE
1 BGP4MP_MESSAGE 1 BGP4MP_MESSAGE
4 BGP4MP_STATE_CHANGE_AS4 4 BGP4MP_MESSAGE_AS4
5 BGP4MP_MESSAGE_AS4 5 BGP4MP_STATE_CHANGE_AS4
5.4.1. BGP4MP_STATE_CHANGE Subtype 5.4.1. BGP4MP_STATE_CHANGE Subtype
This record is used to encode state changes in the BGP finite state This record 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 FSM states are encoded in the Old State and New
State fields to indicate the previous and current state. The format State fields to indicate the previous and current state. The format
is illustrated below: 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
skipping to change at page 15, line 48 skipping to change at page 15, line 48
1 AFI_IPv4 1 AFI_IPv4
2 AFI_IPv6 2 AFI_IPv6
Note that the Address Family value only applies to the IP addresses Note that the Address Family value only applies to the IP addresses
contained in the MRT header. The BGP4MP_MESSAGE Subtype is otherwise contained 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 may be encoded in
the BGP4MP_MESSAGE Subtype. the BGP4MP_MESSAGE Subtype.
5.4.3. BGP4MP_STATE_CHANGE_AS4 Subtype 5.4.3. BGP4MP_MESSAGE_AS4 Subtype
This Subtype updates the BGP4MP_STATE_CHANGE Subtype to support 32BIT This Subtype updates the BGP4MP_MESSAGE Subtype to support 32BIT
Autonomous System numbers. As with the BGP4MP_STATE_CHANGE Subtype, Autonomous System numbers. The BGP4MP_MESSAGE_AS4 Subtype is
the BGP FSM states are encoded in the Old State and New State fields otherwise identical to the BGP4MP_MESSAGE Subtype. The
to indicate the previous and current state. Aside from the extension BGP4MP_MESSAGE_AS4 fields are shown below:
of the peer and local AS fields to 32 bits, this subtype is otherwise
identical to the BGP4MP_STATE_CHANGE Subtype. The
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 | | BGP Message... (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5.4.4. BGP4MP_MESSAGE_AS4 Subtype 5.4.4. BGP4MP_STATE_CHANGE_AS4 Subtype
This Subtype updates the BGP4MP_MESSAGE Subtype to support 32BIT This Subtype updates the BGP4MP_STATE_CHANGE Subtype to support 32BIT
Autonomous System numbers. The BGP4MP_MESSAGE_AS4 Subtype is Autonomous System numbers. As with the BGP4MP_STATE_CHANGE Subtype,
otherwise identical to the BGP4MP_MESSAGE Subtype. The the BGP FSM states are encoded in the Old State and New State fields
BGP4MP_MESSAGE_AS4 fields are shown below: to indicate the previous and current state. Aside from the extension
of the peer and local AS fields to 32 bits, this subtype is otherwise
identical to the BGP4MP_STATE_CHANGE Subtype. The
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) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Message... (variable) | Old State | New State |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5.5. BGP4MP_ET Type 5.5. BGP4MP_ET Type
This Type was initially defined in the Sprint Labs Python Routing This Type was initially defined in the Sprint Labs Python Routing
Toolkit (PyRT). It extends the MRT common header field to include a Toolkit (PyRT). It extends the MRT common header field to include a
32BIT microsecond timestamp field. The type and subtype field 32BIT microsecond timestamp field. The type and subtype field
definitions remain as defined for the BGP4MP Type. The 32BIT definitions remain as defined for the BGP4MP Type. The 32BIT
microsecond timestamp immediately follows the length field in the MRT microsecond timestamp immediately follows the length field in the MRT
common header and precedes all other fields in the message. The common header and precedes all other fields in the message. The
32BIT microsecond field is included in the computation of the length 32BIT microsecond field is included in the computation of the length
 End of changes. 12 change blocks. 
25 lines changed or deleted 25 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/