idnits 2.17.1 draft-ietf-grow-mrt-02.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 785. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 762. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 769. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 775. ** 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 : ---------------------------------------------------------------------------- No issues found here. 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 (March 6, 2006) is 6616 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: '9' is defined on line 734, 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 2858 (ref. '5') (Obsoleted by RFC 4760) ** Obsolete normative reference: RFC 2740 (ref. '7') (Obsoleted by RFC 5340) ** Obsolete normative reference: RFC 2434 (ref. '8') (Obsoleted by RFC 5226) Summary: 8 errors (**), 0 flaws (~~), 3 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: September 7, 2006 Merit Network 5 C. Labovitz 6 Arbor Networks 7 March 6, 2006 9 MRT routing information export format 10 draft-ietf-grow-mrt-02.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 September 7, 2006. 37 Copyright Notice 39 Copyright (C) The Internet Society (2006). 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.8.5. BGP4MP_MESSAGE_32BIT_AS Subtype . . . . . . . . . . . 15 81 4.9. BGP4MP_ET . . . . . . . . . . . . . . . . . . . . . . . . 15 82 4.10. ISIS Type . . . . . . . . . . . . . . . . . . . . . . . . 16 83 4.11. ISIS_ET Type . . . . . . . . . . . . . . . . . . . . . . . 16 84 4.12. OSPF_ET Type . . . . . . . . . . . . . . . . . . . . . . . 16 85 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 86 5.1. Type Codes . . . . . . . . . . . . . . . . . . . . . . . . 18 87 5.2. Subtype Codes . . . . . . . . . . . . . . . . . . . . . . 18 88 6. Security Considerations . . . . . . . . . . . . . . . . . . . 19 89 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 90 7.1. Normative References . . . . . . . . . . . . . . . . . . . 20 91 7.2. Informative References . . . . . . . . . . . . . . . . . . 20 92 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21 93 Intellectual Property and Copyright Statements . . . . . . . . . . 22 95 1. Introduction 97 Researchers and engineers often wish to analyze network behavior by 98 studying routing protocol transactions and routing information base 99 snapshots. To this end, the MRT format was developed to encapsulate, 100 export, and archive this information in a standardized data 101 representation. The BGP routing protocol, in particular, has been 102 the subject of extensive study and analysis which has been 103 significantly aided by the availability of the MRT format. 105 This memo serves to document the MRT format as currently implemented 106 in publicly available software. The format has been extended since 107 it's original introduction in the MRT toolset and these extensions 108 are also included in this memo. Further extensions may be introduced 109 at a later date through additional definitions of the MRT Type field 110 and Subtype fields. 112 2. Basic MRT Format 114 All MRT format messages have a common header which includes a 115 timestamp, Type, Subtype, and length field. The header is followed 116 by a message field. The basic MRT format is illustrated below. 118 0 1 2 3 119 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 120 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 121 | Timestamp | 122 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 123 | Type | Subtype | 124 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 125 | Length | 126 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 127 | Message... (variable) 128 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 130 Header Field Descriptions: 132 Timestamp: 134 Time in seconds since 1 January 1970 00:00:00 UTC 136 Type: 138 A 2-octet field that indicates the Type of information 139 contained in the message field. Types 1 through 5 are used for 140 MRT control information while Types 6 and higher are used for 141 routing information. 143 Subtype: 145 A 2-octet message Subtype field 147 Length: 149 A 4-octet message length field. The length does not include 150 the header. 152 Message: 154 A variable length message. The contents of this field are 155 context dependent on the Type and Subtype fields. 157 3. MRT Control Types 159 The MRT format defines five Control Type messages. These messages 160 are using to relay the current state of MRT message source. The 161 message field may contain an optional ASCII text string for 162 diagnostic purposes. These control messages are unidirectional in 163 nature and there is no form of an acknowledgment or response from the 164 receiver to the sender. The Subtype field is unused for these Types 165 and should be set to 0. 167 The MRT Control Types are defined below: 169 0 NULL 170 1 START 171 2 DIE 172 3 I_AM_DEAD 173 4 PEER_DOWN 175 3.1. NULL Type 177 The NULL Type message causes no operation, A sender may wish to send 178 these for synchronization or keep-alive purposes. 180 3.2. START Type 182 The START Type indicates a sender is about to begin sending MRT 183 messages 185 3.3. DIE Type 187 A DIE Type signals that the receiver should shut down. 189 3.4. I_AM_DEAD Type 191 A I_AM_DEAD indicates that the sender is shutting down. 193 3.5. PEER_DOWN Type 195 A PEER_DOWN is sent when the sender's peer is down. In practice, a 196 sender will likely have multiple peers. It is recommended that the 197 sender use the Message field to convey the IP address of the peer 198 represented in US-ASCII. 200 4. MRT Routing Information Types 202 The following Types are currently defined for the MRT format. Types 203 5-12 were defined in the initial MRT Toolkit package. The BGP4MP 204 Type, number 16, was initially defined in the Zebra routing software 205 package. 207 5 BGP 208 6 RIP 209 7 IDRP 210 8 RIPNG 211 9 BGP4PLUS 212 10 BGP4PLUS_01 213 11 OSPF 214 12 TABLE_DUMP 215 16 BGP4MP 216 17 BGP4MP_ET 217 32 ISIS 218 33 ISIS_ET 219 64 OSPF_ET 221 4.1. BGP Type 223 The BGP Type indicates the Message field contains BGP routing 224 information. The BGP routing protocol is defined in RFC 1771 [1]. 225 The information in the message is dependent on the Subtype value. 226 The BGP Type is considered to be deprecated by the BGP4MP Type. 228 The following BGP Subtypes are defined for the MRT BGP Type. 230 0 BGP_NULL 231 1 BGP_UPDATE 232 2 BGP_PREF_UPDATE 233 3 BGP_STATE_CHANGE 234 4 BGP_SYNC 235 5 BGP_OPEN 236 6 BGP_NOTIFY 237 7 BGP_KEEPALIVE 239 4.1.1. BGP_NULL Subtype 241 The BGP_NULL Subtype is a reserved Subtype. 243 4.1.2. BGP_UPDATE Subtype 245 The BGP_UPDATE Subtype is used to encode BGP UPDATE messages. The 246 format of the MRT Message field for this Subtype is as follows: 248 0 1 2 3 249 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 250 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 251 | Source AS number | 252 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 253 | Source IP address | 254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 255 | Destination AS number | 256 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 257 | Destination IP address | 258 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 259 | BGP UPDATE Contents (variable) 260 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 262 The BGP UPDATE contents include the entire BGP UPDATE message which 263 follows the BGP Message Header. The BGP Message Header itself is not 264 included. 266 4.1.3. BGP_PREF_UPDATE Subtype 268 The BGP_PREF_UPDATE Subtype is not defined. 270 4.1.4. BGP_STATE_CHANGE Subtype 272 The BGP_STATE_CHANGE Subtype is used to record changes in the BGP 273 finite state machine. These FSM states and their numeric encodings 274 are defined in RFC 1771 [1], Appendix 1. Both the old state value 275 and the new state value are encoded as 2-octet numbers. The format 276 of the MRT Message field is as follows: 278 0 1 2 3 279 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 280 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 281 | Source AS number | 282 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 283 | Source IP address | 284 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 285 | Old State | New State | 286 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 288 4.1.5. BGP_SYNC Subtype 290 The BGP_SYNC Subtype is used to indicate a File Name where BGP Table 291 Dump messages should be recorded. The View # corresponds to the View 292 # provided in the TABLE_DUMP Type messages. The following format 293 applies to this Subtype: 295 0 1 2 3 296 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 297 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 298 | View # | 299 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 300 | File Name... (variable) 301 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 303 The File Name is terminated with a NULL (0) character. 305 4.1.6. BGP_OPEN 307 The BGP_OPEN Subtype is used to encode BGP OPEN messages. The format 308 of the MRT Message field for this Subtype is the same as the 309 BGP_UPDATE, however, the last field contains the contents of the BGP 310 OPEN message. 312 4.1.7. BGP_NOTIFY 314 The BGP_NOTIFY Subtype is used to encode BGP NOTIFICATION messages. 315 The format of the MRT Message field for this Subtype is the same as 316 the BGP_UPDATE, however, the last field contains the contents of the 317 BGP NOTIFICATION message. 319 4.1.8. BGP_KEEPALIVE 321 The BGP_KEEPALIVE Subtype is used to encode BGP KEEPALIVE messages. 322 The format of the MRT Message field for this Subtype is the same as 323 the BGP_UPDATE, however, the last field contains no information. 325 4.2. RIP Type 327 The RIP Type is used to export RIP protocol packets as defined in RFC 328 1058 [2]. The Subtype field is currently reserved for this Type and 329 should be set to 0. 331 The format of the MRT Message field for the RIP Type is as follows: 333 0 1 2 3 334 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 335 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 336 | Source IP address | 337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 338 | Destination IP address | 339 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 340 | RIP Message Contents (variable) 341 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 343 4.3. IDRP Type 345 The IDRP Type is used to export Inter-Domain-Routing Protocol (IDRP) 346 protocol information as defined in the ISO/IEC 10747 standard. The 347 Subtype field is unused. This Type is deprecated due to lack of 348 deployment of IDRP. 350 4.4. RIPNG Type 352 The RIPNG Type is used to export RIPNG protocol packets as defined in 353 RFC 2080 [3]. The Subtype field is currently reserved for this Type 354 and should be set to 0. 356 The format of the MRT Message field for the RIPNG Type is as follows: 358 0 1 2 3 359 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 360 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 361 | Source IP address | 362 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 363 | Destination IP address | 364 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 365 | RIPNG Message Contents (variable) 366 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 368 4.5. BGP4PLUS and BGP4PLUS_01 Types 370 The BGP4PLUS and BGP4PLUS_01 Types were defined to support IPv6 BGP 371 routing information. The BGP4PLUS Type was specified based on the 372 initial Internet Draft for Multiprotocol Extensions to BGP-4. The 373 BGP4PLUS_01 Type was specified to correspond to the -01 revision of 374 this Internet Draft. The two Types share the same definitions in 375 terms of their MRT format specifications. 377 The Subtype field definitions are shared with the BGP Type, however, 378 the address fields in the BGP_UPDATE, BGP_OPEN, BGP_NOTIFY, 379 BGP_KEEPALIVE, and BGP_STATE_CHANGE Subtype messages are extended to 380 16 octets for IPv6 addresses. As with the BGP Type, the BGP4PLUS and 381 BGP4PLUS_01 Types are deprecated as they superseded by the BGP4MP 382 Type. 384 4.6. OSPF Type 386 This Type supports the OSPF Protocol as defined in RFC 2328 [4]. The 387 Subtype field may contain two possible values: 389 0 OSPF_STATE_CHANGE 390 1 OSPF_LSA_UPDATE 392 The format of the MRT Message field for the OSPF Type is as follows: 394 0 1 2 3 395 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 396 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 397 | Source IP address | 398 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 399 | Destination IP address | 400 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 401 | OSPF Message Contents (variable) 402 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 404 4.7. TABLE_DUMP Type 406 The TABLE_DUMP Type is used to encode routing table dumps. The 407 Subtype is used to encode whether the table entry contains IPv4 or 408 IPv6 addresses. There are currently two possible values for the 409 Subtype as shown below. 411 1 AFI_IPv4 412 2 AFI_IPv6 414 The format of the TABLE_DUMP Type is illustrated below. 416 0 1 2 3 417 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 418 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 419 | View # | Sequence number | 420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 421 | Prefix (variable) | 422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 423 | Prefix Length | Status | 424 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 425 | Originated Time | 426 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 427 | Peer IP address (variable) | 428 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 429 | Peer AS | Attribute Length | 430 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 431 | BGP Attribute... (variable) 432 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 434 The View field is normally 0 and is intended for cases where an 435 implementation may have multiple RIB views (such as a route server). 436 The Sequence field is a simple incremental counter for a concatenated 437 series of TABLE_DUMP Type messages. 439 The Prefix field contains the IP address of a particular routing 440 table dump entry. The size of this field is dependent on the value 441 of the Subtype for this message. For AFI_IPv4, this field is 4 442 octets, for AFI_IPv6, it is 16 octets in length. The Prefix Length 443 field indicates the length in bits of the prefix mask for the 444 preceding Prefix field. 446 The Status octet is not used in the TABLE_DUMP Type and should be set 447 to 1. 449 The Originated Time contains the 4-octet time at which this prefix 450 was heard. The value represents the time in seconds since 1 January 451 1970 00:00:00 UTC. 453 The Peer ID field is the IP address of the peer which provided the 454 update for this routing table entry. As with the Prefix field, the 455 size of this field is dependent on the Subtype. AFI_IPv4 indicates a 456 4 octet field and an IPv4 address, while a Subtype of AFI_IPv6 457 requires a 16 octet field and an IPv6 address. The Peer AS field 458 contains the AS number of the peer. 460 Attribute length is the length of Attribute field and is 2-octets. 461 The Attribute field contains the attribute information for the route 462 table entry. 464 4.8. BGP4MP Type 466 This Type was initially defined in the Zebra software package for the 467 BGP protocol with multiprotocol extension support as defined by RFC 468 2858 [5]. It supersedes the BGP, BGP4PLUS, BGP4PLUS_01 Types. The 469 BGP4MP Type has four Subtypes which are defined as follows: 471 0 BGP4MP_STATE_CHANGE 472 1 BGP4MP_MESSAGE 473 2 BGP4MP_ENTRY 474 3 BGP4MP_SNAPSHOT 475 4 BGP4MP_MESSAGE_32BIT_AS 477 4.8.1. BGP4MP_STATE_CHANGE Subtype 479 This record is used to encode state changes in the BGP finite state 480 machine. As with the BGP_STATE_CHANGE Subtype, the BGP FSM states 481 are encoded in the Old State and New State fields to indicate the 482 previous and current state. The format is illustrated below: 484 0 1 2 3 485 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 486 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 487 | Source AS number | Destination AS number | 488 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 489 | Interface Index | Address Family | 490 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 491 | Source IP address (variable) | 492 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 493 | Destination IP address (variable) | 494 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 495 | Old State | New State | 496 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 498 While BGP4MP_STATE_CHANGE message is similar to the BGP_STATE_CHANGE 499 message, however, it also includes interface index and Address Family 500 fields. As with the BGP_STATE_CHANGE message, the FSM states and 501 their numeric encodings are defined in RFC 1771 [1], Appendix 1. 502 Future updates to the BGP protocol specification will introduce a new 503 state machine and thus render this message Type obsolete. The 504 interface index provides the interface number of the peering session 505 and the Address Family indicates what Types of addresses are in the 506 the address fields. At present, only the following AFI Types are 507 supported: 509 1 AFI_IPv4 510 2 AFI_IPv6 512 4.8.2. BGP4MP_MESSAGE Subtype 514 This Subtype is used to encode BGP Messages. It is similar to the 515 BGP_UPDATE Subtype, except that is can be used to encode any Type of 516 message (not just BGP UPDATES). In order to determine the BGP 517 message Type, the entire BGP message, including the BGP header, is 518 included in the BGP Message field. The BGP4MP_MESSAGE fields are 519 shown below: 521 0 1 2 3 522 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 523 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 524 | Source AS number | Destination AS number | 525 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 526 | Interface Index | Address Family | 527 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 528 | Source IP address (variable) | 529 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 530 | Destination IP address (variable) | 531 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 532 | BGP Message... (variable) 533 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 535 4.8.3. BGP4MP_ENTRY Subtype 537 This Subtype is used to record routing table entries. It is similar 538 to the TABLE_DUMP Type. The primary difference being that the 539 Address Family is encoded in the Message itself. Further, a 540 Subsequence Address Family field (SAFI) is included as well. 542 0 1 2 3 543 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 544 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 545 | View # | Status | 546 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 547 | Time last change | 548 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 549 | Address Family | SAFI | Next-Hop-Len | 550 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 551 | Next Hop Address (variable) | 552 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 553 | Prefix Length | 554 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 555 | Address Prefix (variable) | 556 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 557 | Attribute Length | 558 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 559 | BGP Attribute... (variable) 560 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 562 4.8.4. BGP4MP_SNAPSHOT Subtype 564 This Subtype is used to indicate a filename containing BGP4MP_ENTRY 565 records. It is similar to the BGP_SYNC message Subtype and shares 566 the same fields. 568 0 1 2 3 569 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 570 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 571 | View # | 572 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 573 | File Name... (variable) 574 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 576 4.8.5. BGP4MP_MESSAGE_32BIT_AS Subtype 578 This Subtype updates the BGP4MP_MESSAGE Subtype to support 32BIT 579 Autonomous System numbers. As the current 16 bit Autonomous System 580 number space nears exhaustion, the introduction of 32 bit numbers 581 will be required to support future Autonomous System number 582 allocations. The BGP4MP_MESSAGE_32BIT_AS fields are shown below: 584 0 1 2 3 585 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 586 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 587 | Source AS number | 588 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 589 | Destination AS number | 590 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 591 | Interface Index | Address Family | 592 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 593 | Source IP address (variable) | 594 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 595 | Destination IP address (variable) | 596 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 597 | BGP Message... (variable) 598 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 600 4.9. BGP4MP_ET 602 This Type was initially defined in the Sprint Labs Python Routing 603 Toolkit (PyRT). It extends the header field of the BGP4MP Type to 604 include a 32-bit microsecond timestamp field. The Subtypes and other 605 field definitions remain as defined for the BGP4MP Type. The 32-bit 606 microsecond timestamp immediately follows the length field in the 607 BGP4MP Type and precedes all other fields in the message. The header 608 modification is illustrated below. 610 0 1 2 3 611 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 612 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 613 | Timestamp | 614 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 615 | Type | Subtype | 616 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 617 | Length | 618 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 619 | microsecond timestamp | 620 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 621 | Message... (variable) 622 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 624 4.10. ISIS Type 626 This Type was initially defined in the Sprint Labs Python Routing and 627 supports the IS-IS routing protocol as defined in RFC 1195 [6]. 628 There is no Type specific header for the ISIS Type. The Subtype code 629 for this Type is undefined. The ISIS PDU directly follows the MRT 630 common header fields. 632 4.11. ISIS_ET Type 634 The ISIS_ET Type extends the the ISIS Type to support microsecond 635 timestamps. As with the BGP4MP_ET Type, a 32-bit microsecond 636 timestamp field is appended to the MRT common header after the length 637 field. The ISIS_ET Type is otherwise identical to the ISIS Type. 639 4.12. OSPF_ET Type 641 The OSPF_ET Type extends the the OSPF Type to support microsecond 642 timestamps. As with the BGP4MP_ET and ISIS_ET Types, a 32-bit 643 microsecond timestamp field is appended to the MRT common header 644 after the length field. The OSPF_ET Type also extends the OSPF Type 645 to support IPv6 addresses for the OSPFv3 protocol as defined in RFC 646 2740 [7]. The format of the MRT Message field for the OSPF_ET Type 647 is as follows: 649 0 1 2 3 650 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 651 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 652 | Address Family | 653 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 654 | Source IP address (variable) | 655 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 656 | Destination IP address (variable) | 657 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 658 | OSPF Message Contents (variable) 659 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 661 5. IANA Considerations 663 This section provides guidance to the Internet Assigned Numbers 664 Authority (IANA) regarding registration of values related to the MRT 665 specification, in accordance with BCP 26, RFC 2434 [8]. 667 There are two name spaces in MRT that require registration: Type 668 Codes and Subtype Codes. 670 MRT is not intended as a general-purpose specification for protocol 671 information export, and allocations should not be made for purposes 672 unrelated to routing protocol information export. 674 The following terms are used here with the meanings defined in BCP 675 26: "name space", "assigned value", "registration". 677 The following policies are used here with the meanings defined in BCP 678 26: "First Come First Served", "Specification Required". 680 5.1. Type Codes 682 Type Codes have a range from 0 to 65535, of which 0-64 have been 683 allocated. New Type Codes should be allocated starting at 65 with 684 Specification Required. 686 5.2. Subtype Codes 688 Subtype Codes have a range from 0 to 65535. Subtype definitions are 689 specific to a particular Type Code definition. New Subtype Code 690 definition must reference an existing Type Code to which the Subtype 691 belongs. As Subtype Codes are specific to Type Codes, new numbers 692 must be unique for the particular Type Code to which the Subtype 693 applies with Specification Required for the Subtype code. 695 6. Security Considerations 697 The MRT Format utilizes a structure which can store routing protocol 698 information data. The fields defined in the MRT specification are of 699 a descriptive nature and provide information that is useful to 700 facilitate the analysis of routing data. As such, the fields 701 currently defined in the MRT specification do not in themselves 702 create additional security risks, since the fields are not used to 703 induce any particular behavior by the recipient application. 705 7. References 707 7.1. Normative References 709 [1] Rekhter, Y. and T. Li, "A Border Gateway Protocol 4 (BGP-4)", 710 RFC 1771, March 1995. 712 [2] Hedrick, C., "Routing Information Protocol", RFC 1058, 713 June 1988. 715 [3] Malkin, G. and R. Minnear, "RIPng for IPv6", RFC 2080, 716 January 1997. 718 [4] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. 720 [5] Bates, T., Rekhter, Y., Chandra, R., and D. Katz, "Multiprotocol 721 Extensions for BGP-4", RFC 2858, June 2000. 723 [6] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and dual 724 environments", RFC 1195, December 1990. 726 [7] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6", RFC 2740, 727 December 1999. 729 [8] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA 730 Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. 732 7.2. Informative References 734 [9] "The MRT Programmers Manual", November 1999. 736 Authors' Addresses 738 Larry Blunk 739 Merit Network 741 Email: ljb@merit.edu 743 Manish Karir 744 Merit Network 746 Email: mkarir@merit.edu 748 Craig Labovitz 749 Arbor Networks 751 Email: labovit@arbor.net 753 Intellectual Property Statement 755 The IETF takes no position regarding the validity or scope of any 756 Intellectual Property Rights or other rights that might be claimed to 757 pertain to the implementation or use of the technology described in 758 this document or the extent to which any license under such rights 759 might or might not be available; nor does it represent that it has 760 made any independent effort to identify any such rights. Information 761 on the procedures with respect to rights in RFC documents can be 762 found in BCP 78 and BCP 79. 764 Copies of IPR disclosures made to the IETF Secretariat and any 765 assurances of licenses to be made available, or the result of an 766 attempt made to obtain a general license or permission for the use of 767 such proprietary rights by implementers or users of this 768 specification can be obtained from the IETF on-line IPR repository at 769 http://www.ietf.org/ipr. 771 The IETF invites any interested party to bring to its attention any 772 copyrights, patents or patent applications, or other proprietary 773 rights that may cover technology that may be required to implement 774 this standard. Please address the information to the IETF at 775 ietf-ipr@ietf.org. 777 Disclaimer of Validity 779 This document and the information contained herein are provided on an 780 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 781 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 782 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 783 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 784 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 785 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 787 Copyright Statement 789 Copyright (C) The Internet Society (2006). This document is subject 790 to the rights, licenses and restrictions contained in BCP 78, and 791 except as set forth therein, the authors retain all their rights. 793 Acknowledgment 795 Funding for the RFC Editor function is currently provided by the 796 Internet Society.