draft-ietf-grow-mrt-02.txt   draft-ietf-grow-mrt-03.txt 
Network Working Group L. Blunk Network Working Group L. Blunk
Internet-Draft M. Karir Internet-Draft M. Karir
Expires: September 7, 2006 Merit Network Expires: December 28, 2006 Merit Network
C. Labovitz C. Labovitz
Arbor Networks Arbor Networks
March 6, 2006 June 26, 2006
MRT routing information export format MRT routing information export format
draft-ietf-grow-mrt-02.txt draft-ietf-grow-mrt-03.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of 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
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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 September 7, 2006. This Internet-Draft will expire on December 28, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
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 MRT
format was initially defined in the MRT Programmer's Guide [9]. 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.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Basic MRT Format . . . . . . . . . . . . . . . . . . . . . . . 4 2. Basic MRT Format . . . . . . . . . . . . . . . . . . . . . . . 4
3. MRT Control Types . . . . . . . . . . . . . . . . . . . . . . 6 3. MRT Control Types . . . . . . . . . . . . . . . . . . . . . . 6
3.1. NULL Type . . . . . . . . . . . . . . . . . . . . . . . . 6 3.1. NULL Type . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2. START Type . . . . . . . . . . . . . . . . . . . . . . . . 6 3.2. START Type . . . . . . . . . . . . . . . . . . . . . . . . 6
skipping to change at page 18, line 18 skipping to change at page 18, line 18
Authority (IANA) regarding registration of values related to the MRT Authority (IANA) regarding registration of values related to the MRT
specification, in accordance with BCP 26, RFC 2434 [8]. specification, in accordance with BCP 26, RFC 2434 [8].
There are two name spaces in MRT that require registration: Type There are two name spaces in MRT that require registration: Type
Codes and Subtype Codes. Codes and Subtype Codes.
MRT is not intended as a general-purpose specification for protocol MRT is not intended as a general-purpose specification for protocol
information export, and allocations should not be made for purposes information export, and allocations should not be made for purposes
unrelated to routing protocol information export. unrelated to routing protocol information export.
The following terms are used here with the meanings defined in BCP
26: "name space", "assigned value", "registration".
The following policies are used here with the meanings defined in BCP The following policies are used here with the meanings defined in BCP
26: "First Come First Served", "Specification Required". 26: "Specification Required", "IETF Consensus".
5.1. Type Codes 5.1. Type Codes
Type Codes have a range from 0 to 65535, of which 0-64 have been Type Codes have a range from 0 to 65535, of which 0-64 have been
allocated. New Type Codes should be allocated starting at 65 with allocated. New Type Codes should be allocated starting at 65. Type
Specification Required. Codes 65 - 32767 are to be assigned by IETF Consensus. Type Codes
32768 - 65535 are assigned based on Specification Required.
5.2. Subtype Codes 5.2. Subtype Codes
Subtype Codes have a range from 0 to 65535. Subtype definitions are Subtype Codes have a range from 0 to 65535. Subtype definitions are
specific to a particular Type Code definition. New Subtype Code specific to a particular Type Code definition. New Subtype Code
definition must reference an existing Type Code to which the Subtype definition must reference an existing Type Code to which the Subtype
belongs. As Subtype Codes are specific to Type Codes, new numbers belongs. As Subtype Codes are specific to Type Codes, new numbers
must be unique for the particular Type Code to which the Subtype must be unique for the particular Type Code to which the Subtype
applies with Specification Required for the Subtype code. applies. Subtype Codes specific to the Type Codes 0 - 32767 are
assigned by IETF Consensus. Suptype Codes specific to Type Codes
32768 - 65535 are assigned based on Specification Required.
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.
skipping to change at page 20, line 34 skipping to change at page 20, line 34
environments", RFC 1195, December 1990. environments", RFC 1195, December 1990.
[7] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6", RFC 2740, [7] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6", RFC 2740,
December 1999. December 1999.
[8] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA [8] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
7.2. Informative References 7.2. Informative References
[9] "The MRT Programmers Manual", November 1999. [9] "MRT Programmer's Guide", November 1999,
<http://www.merit.edu/nrd/resources/mrtprogrammer.pdf>.
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. 10 change blocks. 
13 lines changed or deleted 15 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/