--- 1/draft-ietf-grow-mrt-00.txt 2006-02-04 17:20:55.000000000 +0100 +++ 2/draft-ietf-grow-mrt-01.txt 2006-02-04 17:20:55.000000000 +0100 @@ -1,20 +1,20 @@ Network Working Group L. Blunk Internet-Draft M. Karir -Expires: January 6, 2006 Merit Network +Expires: April 27, 2006 Merit Network C. Labovitz Arbor Networks - July 5, 2005 + October 24, 2005 MRT routing information export format - draft-ietf-grow-mrt-00.txt + draft-ietf-grow-mrt-01.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that @@ -25,21 +25,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 January 6, 2006. + This Internet-Draft will expire on April 27, 2006. Copyright Notice Copyright (C) The Internet Society (2005). Abstract This document describes the MRT format for routing information export. This format was developed in concert with the Multi-threaded Routing Toolkit (MRT) from whence the format takes it name. The @@ -73,25 +73,27 @@ 4.6 OSPF Type . . . . . . . . . . . . . . . . . . . . . . . . 10 4.7 TABLE_DUMP Type . . . . . . . . . . . . . . . . . . . . . 11 4.8 BGP4MP Type . . . . . . . . . . . . . . . . . . . . . . . 12 4.8.1 BGP4MP_STATE_CHANGE Subtype . . . . . . . . . . . . . 12 4.8.2 BGP4MP_MESSAGE Subtype . . . . . . . . . . . . . . . . 13 4.8.3 BGP4MP_ENTRY Subtype . . . . . . . . . . . . . . . . . 14 4.8.4 BGP4MP_SNAPSHOT Subtype . . . . . . . . . . . . . . . 14 4.9 BGP4MP_ET . . . . . . . . . . . . . . . . . . . . . . . . 14 4.10 ISIS . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.11 ISIS_ET . . . . . . . . . . . . . . . . . . . . . . . . . 15 - 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 - 5.1 Normative References . . . . . . . . . . . . . . . . . . . 16 - 5.2 Informative References . . . . . . . . . . . . . . . . . . 16 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 16 - Intellectual Property and Copyright Statements . . . . . . . . 17 + 4.12 OSPF_ET . . . . . . . . . . . . . . . . . . . . . . . . . 15 + 5. Security Considerations . . . . . . . . . . . . . . . . . . . 17 + 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 + 6.1 Normative References . . . . . . . . . . . . . . . . . . . 18 + 6.2 Informative References . . . . . . . . . . . . . . . . . . 18 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 18 + Intellectual Property and Copyright Statements . . . . . . . . 19 1. Introduction Researchers and engineers often wish to analyze network behavior by studying routing protocol transactions and routing information base snapshots. To this end, the MRT format was developed to encapsulate, export, and archive this information in a standardized data representation. The BGP routing protocol, in particular, has been the subject of extensive study and analysis which has been significantly aided by the availability of the MRT format. @@ -201,20 +203,21 @@ 7 IDRP 8 RIPNG 9 BGP4PLUS 10 BGP4PLUS_01 11 OSPF 12 TABLE_DUMP 16 BGP4MP 17 BGP4MP_ET 32 ISIS 33 ISIS_ET + 64 OSPF_ET 4.1 BGP Type The BGP Type indicates the Message field contains BGP routing information. The BGP routing protocol is defined in RFC 1771 [1]. The information in the message is dependent on the Subtype value. The BGP Type is considered to be deprecated by the BGP4MP Type. The following BGP subtypes are defined for the MRT BGP Type. @@ -579,56 +582,91 @@ | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | microsecond timestamp | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Message... (variable) +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 4.10 ISIS This type was initially defined in the Sprint Labs Python Routing and - supports the IS-IS routing protocol as defined in RFC 1195 [5]. The - Subtype field may There is no type specific header for the ISIS Type. - The subtype code for this type is undefined. The ISIS PDU directly - follows the MRT common header fields. + supports the IS-IS routing protocol as defined in RFC 1195 [5]. + There is no type specific header for the ISIS Type. The subtype code + for this type is undefined. The ISIS PDU directly follows the MRT + common header fields. 4.11 ISIS_ET The ISIS_ET Type extends the the ISIS Type to support microsecond timestamps. As with the BGP4MP_ET Type, a 32-bit 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. References +4.12 OSPF_ET -5.1 Normative References + The OSPF_ET Type extends the the OSPF Type to support microsecond + timestamps. As with the BGP4MP_ET and ISIS_ET Types, a 32-bit + microsecond timestamp field is appended to the MRT common header + after the length field. The OSPF_ET Type also extends the OSPF Type + to support IPv6 addresses for the OSPFv3 protocol as defined in RFC + 2740 [6]. The format of the MRT Message field for the OSPF_ET Type + is as follows: + + 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 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Address Family | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Source IP address (variable) | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Destination IP address (variable) | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | OSPF Message Contents (variable) + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +5. Security Considerations + + The MRT Format utilizes a structure which can store routing protocol + information data. The fields defined in the MRT specification are of + a descriptive nature and provide information that is useful to + facilitate the analysis of routing data. As such, the fields + currently defined in the MRT specification do not in themselves + create additional security risks, since the fields are not used to + induce any particular behavior by the recipient application. + +6. References + +6.1 Normative References [1] Rekhter, Y. and T. Li, "A Border Gateway Protocol 4 (BGP-4)", RFC 1771, March 1995. [2] Hedrick, C., "Routing Information Protocol", RFC 1058, June 1988. [3] Malkin, G. and R. Minnear, "RIPng for IPv6", RFC 2080, January 1997. [4] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. [5] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and dual environments", RFC 1195, December 1990. - [6] Bates, T., Rekhter, Y., Chandra, R., and D. Katz, "Multiprotocol + [6] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6", RFC 2740, + December 1999. + + [7] Bates, T., Rekhter, Y., Chandra, R., and D. Katz, "Multiprotocol Extensions for BGP-4", RFC 2858, June 2000. -5.2 Informative References +6.2 Informative References - [7] "The MRT Programmers Manual", November 1999. + [8] "The MRT Programmers Manual", November 1999. Authors' Addresses Larry Blunk Merit Network Email: ljb@merit.edu Manish Karir Merit Network