--- 1/draft-ietf-grow-mrt-09.txt 2009-07-13 16:12:29.000000000 +0200 +++ 2/draft-ietf-grow-mrt-10.txt 2009-07-13 16:12:29.000000000 +0200 @@ -1,20 +1,20 @@ Network Working Group L. Blunk Internet-Draft M. Karir Intended status: Standards Track Merit Network -Expires: August 29, 2009 C. Labovitz +Expires: January 14, 2010 C. Labovitz Arbor Networks - February 25, 2009 + July 13, 2009 MRT routing information export format - draft-ietf-grow-mrt-09.txt + draft-ietf-grow-mrt-10.txt Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. @@ -23,21 +23,21 @@ and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at 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 (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights @@ -59,22 +59,22 @@ 4. MRT Informational Types . . . . . . . . . . . . . . . . . . . 8 4.1. START Type . . . . . . . . . . . . . . . . . . . . . . . . 8 4.2. I_AM_DEAD Type . . . . . . . . . . . . . . . . . . . . . . 8 5. MRT Routing Information Types . . . . . . . . . . . . . . . . 9 5.1. OSPF Type . . . . . . . . . . . . . . . . . . . . . . . . 9 5.2. TABLE_DUMP Type . . . . . . . . . . . . . . . . . . . . . 9 5.3. TABLE_DUMP_V2 Type . . . . . . . . . . . . . . . . . . . . 11 5.4. BGP4MP Type . . . . . . . . . . . . . . . . . . . . . . . 13 5.4.1. BGP4MP_STATE_CHANGE Subtype . . . . . . . . . . . . . 14 5.4.2. BGP4MP_MESSAGE Subtype . . . . . . . . . . . . . . . . 15 - 5.4.3. BGP4MP_STATE_CHANGE_AS4 Subtype . . . . . . . . . . . 15 - 5.4.4. BGP4MP_MESSAGE_AS4 Subtype . . . . . . . . . . . . . . 16 + 5.4.3. BGP4MP_MESSAGE_AS4 Subtype . . . . . . . . . . . . . . 15 + 5.4.4. BGP4MP_STATE_CHANGE_AS4 Subtype . . . . . . . . . . . 16 5.5. BGP4MP_ET Type . . . . . . . . . . . . . . . . . . . . . . 17 5.6. ISIS Type . . . . . . . . . . . . . . . . . . . . . . . . 17 5.7. ISIS_ET Type . . . . . . . . . . . . . . . . . . . . . . . 17 5.8. OSPFv3 Type . . . . . . . . . . . . . . . . . . . . . . . 17 5.9. OSPFv3_ET Type . . . . . . . . . . . . . . . . . . . . . . 18 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 6.1. Type Codes . . . . . . . . . . . . . . . . . . . . . . . . 19 6.2. Subtype Codes . . . . . . . . . . . . . . . . . . . . . . 19 7. Security Considerations . . . . . . . . . . . . . . . . . . . 20 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 @@ -452,22 +452,22 @@ 5.4. BGP4MP Type This Type was initially defined in the Zebra software package for the BGP protocol with multiprotocol extension support as defined by RFC 4760 [RFC4760]. It supersedes the BGP, BGP4PLUS, BGP4PLUS_01 Types. The BGP4MP Type has six Subtypes which are defined as follows: 0 BGP4MP_STATE_CHANGE 1 BGP4MP_MESSAGE - 4 BGP4MP_STATE_CHANGE_AS4 - 5 BGP4MP_MESSAGE_AS4 + 4 BGP4MP_MESSAGE_AS4 + 5 BGP4MP_STATE_CHANGE_AS4 5.4.1. BGP4MP_STATE_CHANGE Subtype 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 State fields to indicate the previous and current state. The format 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 @@ -538,68 +538,68 @@ 1 AFI_IPv4 2 AFI_IPv6 Note that the Address Family value only applies to the IP addresses contained in the MRT header. The BGP4MP_MESSAGE Subtype is otherwise transparent to the contents of the actual message which may contain any valid AFI/SAFI values. Only one BGP message may be encoded in 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 - Autonomous System numbers. As with the BGP4MP_STATE_CHANGE Subtype, - the BGP FSM states are encoded in the Old State and New State fields - 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: + This Subtype updates the BGP4MP_MESSAGE Subtype to support 32BIT + Autonomous System numbers. The BGP4MP_MESSAGE_AS4 Subtype is + otherwise identical to the BGP4MP_MESSAGE Subtype. The + BGP4MP_MESSAGE_AS4 fields are shown 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Peer AS number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Local AS number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Interface Index | Address Family | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Peer 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 - Autonomous System numbers. The BGP4MP_MESSAGE_AS4 Subtype is - otherwise identical to the BGP4MP_MESSAGE Subtype. The - BGP4MP_MESSAGE_AS4 fields are shown below: + This Subtype updates the BGP4MP_STATE_CHANGE Subtype to support 32BIT + Autonomous System numbers. As with the BGP4MP_STATE_CHANGE Subtype, + the BGP FSM states are encoded in the Old State and New State fields + 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 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Interface Index | Address Family | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Peer IP address (variable) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Local IP address (variable) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | BGP Message... (variable) - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Old State | New State | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 5.5. BGP4MP_ET Type This Type was initially defined in the Sprint Labs Python Routing Toolkit (PyRT). It 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