idnits 2.17.1 draft-ietf-grow-mrt-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 17. -- Found old boilerplate from RFC 3978, Section 5.5 on line 713. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 690. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 697. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 703. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 24, 2005) is 6759 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '7' is defined on line 657, but no explicit reference was found in the text == Unused Reference: '8' is defined on line 662, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1771 (ref. '1') (Obsoleted by RFC 4271) ** Downref: Normative reference to an Historic RFC: RFC 1058 (ref. '2') ** Obsolete normative reference: RFC 2740 (ref. '6') (Obsoleted by RFC 5340) ** Obsolete normative reference: RFC 2858 (ref. '7') (Obsoleted by RFC 4760) Summary: 8 errors (**), 0 flaws (~~), 4 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group L. Blunk 3 Internet-Draft M. Karir 4 Expires: April 27, 2006 Merit Network 5 C. Labovitz 6 Arbor Networks 7 October 24, 2005 9 MRT routing information export format 10 draft-ietf-grow-mrt-01.txt 12 Status of this Memo 14 By submitting this Internet-Draft, each author represents that any 15 applicable patent or other IPR claims of which he or she is aware 16 have been or will be disclosed, and any of which he or she becomes 17 aware will be disclosed, in accordance with Section 6 of BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt. 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 This Internet-Draft will expire on April 27, 2006. 37 Copyright Notice 39 Copyright (C) The Internet Society (2005). 41 Abstract 43 This document describes the MRT format for routing information 44 export. This format was developed in concert with the Multi-threaded 45 Routing Toolkit (MRT) from whence the format takes it name. The 46 format can be used to export routing protocol messages, state 47 changes, and routing information base contents. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 2. Basic MRT Format . . . . . . . . . . . . . . . . . . . . . . . 4 53 3. MRT Control Types . . . . . . . . . . . . . . . . . . . . . . 6 54 3.1 NULL Type . . . . . . . . . . . . . . . . . . . . . . . . 6 55 3.2 START Type . . . . . . . . . . . . . . . . . . . . . . . . 6 56 3.3 DIE Type . . . . . . . . . . . . . . . . . . . . . . . . . 6 57 3.4 I_AM_DEAD Type . . . . . . . . . . . . . . . . . . . . . . 6 58 3.5 PEER_DOWN Type . . . . . . . . . . . . . . . . . . . . . . 6 59 4. MRT Routing Information Types . . . . . . . . . . . . . . . . 7 60 4.1 BGP Type . . . . . . . . . . . . . . . . . . . . . . . . . 7 61 4.1.1 BGP_NULL Subtype . . . . . . . . . . . . . . . . . . . 7 62 4.1.2 BGP_UPDATE Subtype . . . . . . . . . . . . . . . . . . 7 63 4.1.3 BGP_PREF_UPDATE Subtype . . . . . . . . . . . . . . . 8 64 4.1.4 BGP_STATE_CHANGE Subtype . . . . . . . . . . . . . . . 8 65 4.1.5 BGP_SYNC Subtype . . . . . . . . . . . . . . . . . . . 8 66 4.1.6 BGP_OPEN . . . . . . . . . . . . . . . . . . . . . . . 9 67 4.1.7 BGP_NOTIFY . . . . . . . . . . . . . . . . . . . . . . 9 68 4.1.8 BGP_KEEPALIVE . . . . . . . . . . . . . . . . . . . . 9 69 4.2 RIP Type . . . . . . . . . . . . . . . . . . . . . . . . . 9 70 4.3 IDRP Type . . . . . . . . . . . . . . . . . . . . . . . . 10 71 4.4 RIPNG Type . . . . . . . . . . . . . . . . . . . . . . . . 10 72 4.5 BGP4PLUS and BGP4PLUS_01 Types . . . . . . . . . . . . . . 10 73 4.6 OSPF Type . . . . . . . . . . . . . . . . . . . . . . . . 10 74 4.7 TABLE_DUMP Type . . . . . . . . . . . . . . . . . . . . . 11 75 4.8 BGP4MP Type . . . . . . . . . . . . . . . . . . . . . . . 12 76 4.8.1 BGP4MP_STATE_CHANGE Subtype . . . . . . . . . . . . . 12 77 4.8.2 BGP4MP_MESSAGE Subtype . . . . . . . . . . . . . . . . 13 78 4.8.3 BGP4MP_ENTRY Subtype . . . . . . . . . . . . . . . . . 14 79 4.8.4 BGP4MP_SNAPSHOT Subtype . . . . . . . . . . . . . . . 14 80 4.9 BGP4MP_ET . . . . . . . . . . . . . . . . . . . . . . . . 14 81 4.10 ISIS . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 82 4.11 ISIS_ET . . . . . . . . . . . . . . . . . . . . . . . . . 15 83 4.12 OSPF_ET . . . . . . . . . . . . . . . . . . . . . . . . . 15 84 5. Security Considerations . . . . . . . . . . . . . . . . . . . 17 85 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 86 6.1 Normative References . . . . . . . . . . . . . . . . . . . 18 87 6.2 Informative References . . . . . . . . . . . . . . . . . . 18 88 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 18 89 Intellectual Property and Copyright Statements . . . . . . . . 19 91 1. Introduction 93 Researchers and engineers often wish to analyze network behavior by 94 studying routing protocol transactions and routing information base 95 snapshots. To this end, the MRT format was developed to encapsulate, 96 export, and archive this information in a standardized data 97 representation. The BGP routing protocol, in particular, has been 98 the subject of extensive study and analysis which has been 99 significantly aided by the availability of the MRT format. 101 This memo serves to document the MRT format as currently implemented 102 in publicly available software. The format has been extended since 103 it's original introduction in the MRT toolset and these extensions 104 are also included in this memo. Further extensions may be introduced 105 at a later date through additional definitions of the MRT Type field. 107 2. Basic MRT Format 109 All MRT format messages have a common header which includes a 110 timestamp, type, subtype, and length field. The header is followed 111 by a message field. The basic MRT format is illustrated below. 113 0 1 2 3 114 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 115 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 116 | Timestamp | 117 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 118 | Type | Subtype | 119 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 120 | Length | 121 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 122 | Message... (variable) 123 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 125 Header Field Descriptions: 127 Timestamp: 129 Time in seconds since 1 January 1970 00:00:00 UTC 131 Type: 133 A 2-octet field that indicates the type of information 134 contained in the message field. Types 1 through 5 are used for 135 MRT control information while Types 6 and higher are used for 136 routing information. 138 Subtype: 140 A 2-octet message subtype field 142 Length: 144 A 4-octet message length field. The length does not include 145 the header. 147 Message: 149 A variable length message. The contents of this field are 150 context dependent on the type and subtype fields. 152 3. MRT Control Types 154 The MRT format defines five control type messages. These messages 155 are using to relay the current state of MRT message source. The 156 message field may contain an optional ASCII text string for 157 diagnostic purposes. These control messages are unidirectional in 158 nature and there is no form of an acknowledgment or response from the 159 receiver to the sender. The subtype field is unused for these types 160 and should be set to 0. 162 The MRT Control Types are defined below: 164 0 NULL 165 1 START 166 2 DIE 167 3 I_AM_DEAD 168 4 PEER_DOWN 170 3.1 NULL Type 172 The NULL Type message causes no operation, A sender may wish to send 173 these for synchronization or keep-alive purposes. 175 3.2 START Type 177 The START Type indicates a sender is about to begin sending MRT 178 messages 180 3.3 DIE Type 182 A DIE Type signals that the receiver should shut down. 184 3.4 I_AM_DEAD Type 186 A I_AM_DEAD indicates that the sender is shutting down. 188 3.5 PEER_DOWN Type 190 A PEER_DOWN is sent when the sender's peer is down. In practice, a 191 sender will likely have multiple peers. It is recommended that the 192 sender use the Message field to convey the IP address of the peer 193 represented in US-ASCII. 195 4. MRT Routing Information Types 197 The following types are currently defined for the MRT format. Types 198 5-12 were defined in the initial MRT Toolkit package. The BGP4MP 199 type, number 16, was defined in the Zebra routing software package. 201 5 BGP 202 6 RIP 203 7 IDRP 204 8 RIPNG 205 9 BGP4PLUS 206 10 BGP4PLUS_01 207 11 OSPF 208 12 TABLE_DUMP 209 16 BGP4MP 210 17 BGP4MP_ET 211 32 ISIS 212 33 ISIS_ET 213 64 OSPF_ET 215 4.1 BGP Type 217 The BGP Type indicates the Message field contains BGP routing 218 information. The BGP routing protocol is defined in RFC 1771 [1]. 219 The information in the message is dependent on the Subtype value. 220 The BGP Type is considered to be deprecated by the BGP4MP Type. 222 The following BGP subtypes are defined for the MRT BGP Type. 224 0 BGP_NULL 225 1 BGP_UPDATE 226 2 BGP_PREF_UPDATE 227 3 BGP_STATE_CHANGE 228 4 BGP_SYNC 229 5 BGP_OPEN 230 6 BGP_NOTIFY 231 7 BGP_KEEPALIVE 233 4.1.1 BGP_NULL Subtype 235 The BGP_NULL Subtype is a reserved subtype. 237 4.1.2 BGP_UPDATE Subtype 239 The BGP_UPDATE Subtype is used to encode BGP UPDATE messages. The 240 format of the MRT Message field for this subtype is as follows: 242 0 1 2 3 243 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 244 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 245 | Source AS number | 246 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 247 | Source IP address | 248 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 249 | Destination AS number | 250 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 251 | Destination IP address | 252 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 253 | BGP UPDATE Contents (variable) 254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 256 The BGP UPDATE contents include the entire BGP UPDATE message which 257 follows the BGP Message Header. The BGP Message Header itself is not 258 included. 260 4.1.3 BGP_PREF_UPDATE Subtype 262 The BGP_PREF_UPDATE Subtype is not defined. 264 4.1.4 BGP_STATE_CHANGE Subtype 266 The BGP_STATE_CHANGE Subtype is used to record changes in the BGP 267 finite state machine. These FSM states and their numeric encodings 268 are defined in RFC 1771 [1], Appendix 1. Both the old state value 269 and the new state value are encoded as 2-octet numbers. The format 270 of the MRT Message field is as follows: 272 0 1 2 3 273 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 274 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 275 | Source AS number | 276 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 277 | Source IP address | 278 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 279 | Old State | New State | 280 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 282 4.1.5 BGP_SYNC Subtype 284 The BGP_SYNC Subtype is used to indicate a File Name where BGP Table 285 Dump messages should be recorded. The View # corresponds to the View 286 # provided in the TABLE_DUMP Type messages. The following format 287 applies to this Subtype: 289 0 1 2 3 290 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 291 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 292 | View # | 293 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 294 | File Name... (variable) 295 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 297 The File Name is terminated with a NULL (0) character. 299 4.1.6 BGP_OPEN 301 The BGP_OPEN Subtype is used to encode BGP OPEN messages. The format 302 of the MRT Message field for this subtype is the same as the 303 BGP_UPDATE, however, the last field contains the contents of the BGP 304 OPEN message. 306 4.1.7 BGP_NOTIFY 308 The BGP_NOTIFY Subtype is used to encode BGP NOTIFICATION messages. 309 The format of the MRT Message field for this subtype is the same as 310 the BGP_UPDATE, however, the last field contains the contents of the 311 BGP NOTIFICATION message. 313 4.1.8 BGP_KEEPALIVE 315 The BGP_KEEPALIVE Subtype is used to encode BGP KEEPALIVE messages. 316 The format of the MRT Message field for this subtype is the same as 317 the BGP_UPDATE, however, the last field contains no information. 319 4.2 RIP Type 321 The RIP Type is used to export RIP protocol packets as defined in RFC 322 1058 [2]. The Subtype field is currently reserved for this type and 323 should be set to 0. 325 The format of the MRT Message field for the RIP Type is as follows: 327 0 1 2 3 328 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 329 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 330 | Source IP address | 331 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 332 | Destination IP address | 333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 334 | RIP Message Contents (variable) 335 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 337 4.3 IDRP Type 339 The IDRP Type is used to export Inter-Domain-Routing Protocol (IDRP) 340 protocol information as defined in the ISO/IEC 10747 standard. The 341 Subtype field is unused. This type is deprecated due to lack of 342 deployment of IDRP. 344 4.4 RIPNG Type 346 The RIPNG Type is used to export RIPNG protocol packets as defined in 347 RFC 2080 [3]. The Subtype field is currently reserved for this type 348 and should be set to 0. 350 The format of the MRT Message field for the RIPNG Type is as follows: 352 0 1 2 3 353 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 354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 355 | Source IP address | 356 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 357 | Destination IP address | 358 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 359 | RIPNG Message Contents (variable) 360 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 362 4.5 BGP4PLUS and BGP4PLUS_01 Types 364 The BGP4PLUS and BGP4PLUS_01 Types were defined to support IPv6 BGP 365 routing information. The BGP4PLUS Type was specified based on the 366 initial Internet Draft for Multiprotocol Extensions to BGP-4. The 367 BGP4PLUS_01 Type was specified to correspond to the -01 revision of 368 this Internet Draft. The two types share the same definitions in 369 terms of their MRT format specifications. 371 The Subtype field definitions are shared with the BGP Type, however, 372 the address fields in the BGP_UPDATE, BGP_OPEN, BGP_NOTIFY, 373 BGP_KEEPALIVE, and BGP_STATE_CHANGE subtype messages are extended to 374 16 octets for IPv6 addresses. As with the BGP Type, the BGP4PLUS and 375 BGP4PLUS_01 Types are deprecated as they superseded by the BGP4MP 376 Type. 378 4.6 OSPF Type 380 This type supports the OSPF Protocol as defined in RFC 2328 [4]. The 381 Subtype field may contain two possible values: 383 0 OSPF_STATE_CHANGE 384 1 OSPF_LSA_UPDATE 386 The format of the MRT Message field for the OSPF Type is as follows: 388 0 1 2 3 389 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 390 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 391 | Source IP address | 392 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 393 | Destination IP address | 394 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 395 | OSPF Message Contents (variable) 396 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 398 4.7 TABLE_DUMP Type 400 The TABLE_DUMP Type is used to encode routing table dumps. The 401 Subtype is used to encode whether the table entry contains IPv4 or 402 IPv6 addresses. There are currently two possible values for the 403 Subtype as shown below. 405 1 AFI_IPv4 406 2 AFI_IPv6 408 The format of the TABLE_DUMP Type is illustrated below. 410 0 1 2 3 411 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 412 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 413 | View # | Sequence number | 414 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 415 | Prefix (variable) | 416 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 417 | Prefix Length | Status | 418 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 419 | Originated Time | 420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 421 | Peer IP address (variable) | 422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 423 | Peer AS | Attribute Length | 424 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 425 | BGP Attribute... (variable) 426 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 428 The View field is normally 0 and is intended for cases where an 429 implementation may have multiple RIB views (such as a route server). 430 The Sequence field is a simple incremental counter for a concatenated 431 series of TABLE_DUMP Type messages. 433 The Prefix field contains the IP address of a particular routing 434 table dump entry. The size of this field is dependent on the value 435 of the Subtype for this message. For AFI_IPv4, this field is 4 436 octets, for AFI_IPv6, it is 16 octets in length. The Prefix Length 437 field indicates the length in bits of the prefix mask for the 438 preceding Prefix field. 440 The Status octet is not used in the TABLE_DUMP Type and should be set 441 to 1. 443 The Originated Time contains the 4-octet time at which this prefix 444 was heard. The value represents the time in seconds since 1 January 445 1970 00:00:00 UTC. 447 The Peer ID field is the IP address of the peer which provided the 448 update for this routing table entry. As with the Prefix field, the 449 size of this field is dependent on the Subtype. AFI_IPv4 indicates a 450 4 octet field and an IPv4 address, while a Subtype of AFI_IPv6 451 requires a 16 octet field and an IPv6 address. The Peer AS field 452 contains the AS number of the peer. 454 Attribute length is the length of Attribute field and is 2-octets. 455 The Attribute field contains the attribute information for the route 456 table entry. 458 4.8 BGP4MP Type 460 This type was initially defined in the Zebra software package for the 461 BGP protocol with multiprotocol extension support. It supersedes the 462 BGP, BGP4PLUS, BGP4PLUS_01 Types. The BGP4MP Type has four subtypes 463 which are defined as follows: 465 0 BGP4MP_STATE_CHANGE 466 1 BGP4MP_MESSAGE 467 2 BGP4MP_ENTRY 468 3 BGP4MP_SNAPSHOT 470 4.8.1 BGP4MP_STATE_CHANGE Subtype 472 This record is used to encode state changes in the BGP finite state 473 machine. As with the BGP_STATE_CHANGE Subtype, the BGP FSM states 474 are encoded in the Old State and New State fields to indicate the 475 previous and current state. The format is illustrated below: 477 0 1 2 3 478 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 479 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 480 | Source AS number | Destination AS number | 481 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 482 | Interface Index | Address Family | 483 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 484 | Source IP address (variable) | 485 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 486 | Destination IP address (variable) | 487 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 488 | Old State | New State | 489 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 491 While BGP4MP_STATE_CHANGE message is similar to the BGP_STATE_CHANGE 492 message, it also includes interface index and Address Family fields. 493 The interface index provides the interface number of the peering 494 session and the Address Family indicates what types of addresses are 495 in the the address fields. At present, only the following AFI types 496 are supported: 498 1 AFI_IPv4 499 2 AFI_IPv6 501 4.8.2 BGP4MP_MESSAGE Subtype 503 This Subtype is used to encode BGP Messages. It is similar to the 504 BGP_UPDATE subtype, except that is can be used to encode any type of 505 message (not just BGP UPDATES). In order to determine the BGP 506 message type, the entire BGP message, including the BGP header, is 507 included in the BGP Message field. The BGP4MP_MESSAGE fields are 508 shown below: 510 0 1 2 3 511 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 512 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 513 | Source AS number | Destination AS number | 514 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 515 | Interface Index | Address Family | 516 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 517 | Source IP address (variable) | 518 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 519 | Destination IP address (variable) | 520 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 521 | BGP Message... (variable) 522 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 524 4.8.3 BGP4MP_ENTRY Subtype 526 This Subtype is used to record routing table entries. It is similar 527 to the TABLE_DUMP Type. The primary difference being that the 528 Address Family is encoded in the Message itself. Further, a 529 Subsequence Address Family field (SAFI) is included as well. 531 0 1 2 3 532 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 533 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 534 | View # | Status | 535 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 536 | Time last change | 537 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 538 | Address Family | SAFI | Next-Hop-Len | 539 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 540 | Next Hop Address (variable) | 541 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 542 | Prefix Length | 543 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 544 | Address Prefix (variable) | 545 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 546 | Attribute Length | 547 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 548 | BGP Attribute... (variable) 549 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 551 4.8.4 BGP4MP_SNAPSHOT Subtype 553 This Subtype is used to indicate a filename containing BGP4MP_ENTRY 554 records. It is similar to the BGP_SYNC message subtype and shares 555 the same fields. 557 0 1 2 3 558 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 559 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 560 | View # | 561 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 562 | File Name... (variable) 563 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 565 4.9 BGP4MP_ET 567 This type was initially defined in the Sprint Labs Python Routing 568 Toolkit (PyRT). It extends the header field of the BGP4MP Type to 569 include a 32-bit microsecond timestamp field. The subtypes and other 570 field definitions remain as defined for the BGP4MP Type. The 32-bit 571 microsecond timestamp immediately follows the length field in the 572 BGP4MP Type and precedes all other fields in the message. The header 573 modification is illustrated below. 575 0 1 2 3 576 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 577 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 578 | Timestamp | 579 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 580 | Type | Subtype | 581 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 582 | Length | 583 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 584 | microsecond timestamp | 585 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 586 | Message... (variable) 587 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 589 4.10 ISIS 591 This type was initially defined in the Sprint Labs Python Routing and 592 supports the IS-IS routing protocol as defined in RFC 1195 [5]. 593 There is no type specific header for the ISIS Type. The subtype code 594 for this type is undefined. The ISIS PDU directly follows the MRT 595 common header fields. 597 4.11 ISIS_ET 599 The ISIS_ET Type extends the the ISIS Type to support microsecond 600 timestamps. As with the BGP4MP_ET Type, a 32-bit microsecond 601 timestamp field is appended to the MRT common header after the length 602 field. The ISIS_ET Type is otherwise identical to the ISIS Type. 604 4.12 OSPF_ET 606 The OSPF_ET Type extends the the OSPF Type to support microsecond 607 timestamps. As with the BGP4MP_ET and ISIS_ET Types, a 32-bit 608 microsecond timestamp field is appended to the MRT common header 609 after the length field. The OSPF_ET Type also extends the OSPF Type 610 to support IPv6 addresses for the OSPFv3 protocol as defined in RFC 611 2740 [6]. The format of the MRT Message field for the OSPF_ET Type 612 is as follows: 614 0 1 2 3 615 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 616 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 617 | Address Family | 618 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 619 | Source IP address (variable) | 620 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 621 | Destination IP address (variable) | 622 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 623 | OSPF Message Contents (variable) 624 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 626 5. Security Considerations 628 The MRT Format utilizes a structure which can store routing protocol 629 information data. The fields defined in the MRT specification are of 630 a descriptive nature and provide information that is useful to 631 facilitate the analysis of routing data. As such, the fields 632 currently defined in the MRT specification do not in themselves 633 create additional security risks, since the fields are not used to 634 induce any particular behavior by the recipient application. 636 6. References 638 6.1 Normative References 640 [1] Rekhter, Y. and T. Li, "A Border Gateway Protocol 4 (BGP-4)", 641 RFC 1771, March 1995. 643 [2] Hedrick, C., "Routing Information Protocol", RFC 1058, 644 June 1988. 646 [3] Malkin, G. and R. Minnear, "RIPng for IPv6", RFC 2080, 647 January 1997. 649 [4] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. 651 [5] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and dual 652 environments", RFC 1195, December 1990. 654 [6] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6", RFC 2740, 655 December 1999. 657 [7] Bates, T., Rekhter, Y., Chandra, R., and D. Katz, "Multiprotocol 658 Extensions for BGP-4", RFC 2858, June 2000. 660 6.2 Informative References 662 [8] "The MRT Programmers Manual", November 1999. 664 Authors' Addresses 666 Larry Blunk 667 Merit Network 669 Email: ljb@merit.edu 671 Manish Karir 672 Merit Network 674 Email: mkarir@merit.edu 676 Craig Labovitz 677 Arbor Networks 679 Email: labovit@arbor.net 681 Intellectual Property Statement 683 The IETF takes no position regarding the validity or scope of any 684 Intellectual Property Rights or other rights that might be claimed to 685 pertain to the implementation or use of the technology described in 686 this document or the extent to which any license under such rights 687 might or might not be available; nor does it represent that it has 688 made any independent effort to identify any such rights. Information 689 on the procedures with respect to rights in RFC documents can be 690 found in BCP 78 and BCP 79. 692 Copies of IPR disclosures made to the IETF Secretariat and any 693 assurances of licenses to be made available, or the result of an 694 attempt made to obtain a general license or permission for the use of 695 such proprietary rights by implementers or users of this 696 specification can be obtained from the IETF on-line IPR repository at 697 http://www.ietf.org/ipr. 699 The IETF invites any interested party to bring to its attention any 700 copyrights, patents or patent applications, or other proprietary 701 rights that may cover technology that may be required to implement 702 this standard. Please address the information to the IETF at 703 ietf-ipr@ietf.org. 705 Disclaimer of Validity 707 This document and the information contained herein are provided on an 708 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 709 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 710 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 711 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 712 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 713 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 715 Copyright Statement 717 Copyright (C) The Internet Society (2005). This document is subject 718 to the rights, licenses and restrictions contained in BCP 78, and 719 except as set forth therein, the authors retain all their rights. 721 Acknowledgment 723 Funding for the RFC Editor function is currently provided by the 724 Internet Society.