idnits 2.17.1 draft-ietf-grow-mrt-05.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, updated by RFC 4748 on line 978. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 989. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 996. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1002. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust 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 (November 16, 2007) is 6005 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) == Missing Reference: 'RFC 4760' is mentioned on line 604, but not defined ** Downref: Normative reference to an Historic RFC: RFC 1058 ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) ** Obsolete normative reference: RFC 2740 (Obsoleted by RFC 5340) Summary: 4 errors (**), 0 flaws (~~), 2 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 Intended status: Standards Track Merit Network 5 Expires: May 19, 2008 C. Labovitz 6 Arbor Networks 7 November 16, 2007 9 MRT routing information export format 10 draft-ietf-grow-mrt-05.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 May 19, 2008. 37 Copyright Notice 39 Copyright (C) The IETF Trust (2007). 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. Requirements notation . . . . . . . . . . . . . . . . . . . . 4 52 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 53 3. Basic MRT Format . . . . . . . . . . . . . . . . . . . . . . . 6 54 4. MRT Control Types . . . . . . . . . . . . . . . . . . . . . . 8 55 4.1. NULL Type . . . . . . . . . . . . . . . . . . . . . . . . 8 56 4.2. START Type . . . . . . . . . . . . . . . . . . . . . . . . 8 57 4.3. DIE Type . . . . . . . . . . . . . . . . . . . . . . . . . 8 58 4.4. I_AM_DEAD Type . . . . . . . . . . . . . . . . . . . . . . 8 59 4.5. PEER_DOWN Type . . . . . . . . . . . . . . . . . . . . . . 8 60 5. MRT Routing Information Types . . . . . . . . . . . . . . . . 9 61 5.1. BGP Type . . . . . . . . . . . . . . . . . . . . . . . . . 9 62 5.1.1. BGP_NULL Subtype . . . . . . . . . . . . . . . . . . . 9 63 5.1.2. BGP_UPDATE Subtype . . . . . . . . . . . . . . . . . . 10 64 5.1.3. BGP_PREF_UPDATE Subtype . . . . . . . . . . . . . . . 10 65 5.1.4. BGP_STATE_CHANGE Subtype . . . . . . . . . . . . . . . 10 66 5.1.5. BGP_SYNC Subtype . . . . . . . . . . . . . . . . . . . 11 67 5.1.6. BGP_OPEN Subtype . . . . . . . . . . . . . . . . . . . 11 68 5.1.7. BGP_NOTIFY Subtype . . . . . . . . . . . . . . . . . . 11 69 5.1.8. BGP_KEEPALIVE Subtype . . . . . . . . . . . . . . . . 11 70 5.2. RIP Type . . . . . . . . . . . . . . . . . . . . . . . . . 11 71 5.3. IDRP Type . . . . . . . . . . . . . . . . . . . . . . . . 12 72 5.4. RIPNG Type . . . . . . . . . . . . . . . . . . . . . . . . 12 73 5.5. BGP4PLUS and BGP4PLUS_01 Types . . . . . . . . . . . . . . 12 74 5.6. OSPF Type . . . . . . . . . . . . . . . . . . . . . . . . 13 75 5.7. TABLE_DUMP Type . . . . . . . . . . . . . . . . . . . . . 13 76 5.8. TABLE_DUMP_V2 Type . . . . . . . . . . . . . . . . . . . . 15 77 5.9. BGP4MP Type . . . . . . . . . . . . . . . . . . . . . . . 17 78 5.9.1. BGP4MP_STATE_CHANGE Subtype . . . . . . . . . . . . . 18 79 5.9.2. BGP4MP_MESSAGE Subtype . . . . . . . . . . . . . . . . 19 80 5.9.3. BGP4MP_ENTRY Subtype . . . . . . . . . . . . . . . . . 19 81 5.9.4. BGP4MP_SNAPSHOT Subtype . . . . . . . . . . . . . . . 20 82 5.9.5. BGP4MP_STATE_CHANGE_AS4 Subtype . . . . . . . . . . . 20 83 5.9.6. BGP4MP_MESSAGE_AS4 Subtype . . . . . . . . . . . . . . 21 84 5.10. BGP4MP_ET . . . . . . . . . . . . . . . . . . . . . . . . 21 85 5.11. ISIS Type . . . . . . . . . . . . . . . . . . . . . . . . 22 86 5.12. ISIS_ET Type . . . . . . . . . . . . . . . . . . . . . . . 22 87 5.13. OSPFv3 Type . . . . . . . . . . . . . . . . . . . . . . . 22 88 5.14. OSPFv3_ET Type . . . . . . . . . . . . . . . . . . . . . . 23 89 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 90 6.1. Type Codes . . . . . . . . . . . . . . . . . . . . . . . . 24 91 6.2. Subtype Codes . . . . . . . . . . . . . . . . . . . . . . 24 92 7. Security Considerations . . . . . . . . . . . . . . . . . . . 25 93 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 26 94 8.1. Normative References . . . . . . . . . . . . . . . . . . . 26 95 8.2. Informative References . . . . . . . . . . . . . . . . . . 26 96 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 27 97 Intellectual Property and Copyright Statements . . . . . . . . . . 28 99 1. Requirements notation 101 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 102 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 103 document are to be interpreted as described in [RFC2119]. 105 2. Introduction 107 Researchers and engineers often wish to analyze network behavior by 108 studying routing protocol transactions and routing information base 109 snapshots. To this end, the MRT format was developed to encapsulate, 110 export, and archive this information in a standardized data 111 representation. The BGP routing protocol, in particular, has been 112 the subject of extensive study and analysis which has been 113 significantly aided by the availability of the MRT format. The MRT 114 format was initially defined in the MRT Programmer's Guide [MRT PROG 115 GUIDE]. 117 This memo serves to document the MRT format as currently implemented 118 in publicly available software. The format has been extended since 119 it's original introduction in the MRT toolset and these extensions 120 are also included in this memo. Further extensions may be introduced 121 at a later date through additional definitions of the MRT Type field 122 and Subtype fields. 124 3. Basic MRT Format 126 All MRT format messages have a common header which includes a 127 timestamp, Type, Subtype, and length field. The header is followed 128 by a message field. The MRT common header is illustrated below. 130 0 1 2 3 131 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 132 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 133 | Timestamp | 134 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 135 | Type | Subtype | 136 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 137 | Length | 138 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 139 | Message... (variable) 140 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 142 Header Field Descriptions: 144 Timestamp: 146 Time in seconds since 1 January 1970 00:00:00 UTC 148 Type: 150 A 2-octet field that indicates the Type of information 151 contained in the message field. Types 1 through 5 are used for 152 MRT control information while Types 6 and higher are used for 153 routing information. 155 Subtype: 157 A 2-octet message Subtype field 159 Length: 161 A 4-octet message length field. The length does not include 162 the header. 164 Message: 166 A variable length message. The contents of this field are 167 context dependent on the Type and Subtype fields. 169 4. MRT Control Types 171 The MRT format defines five Control Type messages. These messages 172 are OPTIONAL and MAY be used to communicate the state of the MRT 173 message source and it's peering sessions. The message field MAY 174 contain an OPTIONAL message string for diagnostic purposes. The 175 message string encoding MUST follow the UTF-8 transformation format. 176 The Subtype field is unused for these Types and SHOULD be set to 0. 178 The MRT Control Types are defined below: 180 0 NULL 181 1 START 182 2 DIE 183 3 I_AM_DEAD 184 4 PEER_DOWN 186 4.1. NULL Type 188 The NULL Type message causes no operation, A sender may wish to send 189 these for synchronization or keep-alive purposes. 191 4.2. START Type 193 The START Type indicates a sender is about to begin sending MRT 194 messages 196 4.3. DIE Type 198 A DIE Type signals that the receiver should shut down. 200 4.4. I_AM_DEAD Type 202 A I_AM_DEAD indicates that the sender is shutting down. 204 4.5. PEER_DOWN Type 206 A PEER_DOWN indicates when one of the sender's peers is down. In 207 practice, a sender will likely have multiple peers. The sender 208 SHOULD use the Message field to convey the IP address of the peer 209 represented in UTF-8. 211 5. MRT Routing Information Types 213 The following Types are currently defined for the MRT format. Types 214 5-12 were defined in the initial MRT Toolkit package. The BGP4MP 215 Type, number 16, was initially defined in the Zebra routing software 216 package. The BGP4MP_ET, ISIS, and ISIS_ET Types were initially 217 defined in the Sprint Labs Python Routing Toolkit (PyRT). 219 5 BGP *DEPRECATED* 220 6 RIP 221 7 IDRP *DEPRECATED* 222 8 RIPNG 223 9 BGP4PLUS *DEPRECATED* 224 10 BGP4PLUS_01 *DEPRECATED* 225 11 OSPF 226 12 TABLE_DUMP 227 13 TABLE_DUMP_V2 228 16 BGP4MP 229 17 BGP4MP_ET 230 32 ISIS 231 33 ISIS_ET 232 48 OSPFv3 233 49 OSPFv3_ET 235 5.1. BGP Type 237 The BGP Type indicates the Message field contains BGP routing 238 information. The BGP routing protocol is defined in RFC 4271 239 [RFC4271]. The information in the message is dependent on the 240 Subtype value. The BGP Type and all associated Subtypes are 241 considered to be DEPRECATED by the BGP4MP Type. 243 The following BGP Subtypes are defined for the MRT BGP Type. 245 0 BGP_NULL 246 1 BGP_UPDATE 247 2 BGP_PREF_UPDATE 248 3 BGP_STATE_CHANGE 249 4 BGP_SYNC 250 5 BGP_OPEN 251 6 BGP_NOTIFY 252 7 BGP_KEEPALIVE 254 5.1.1. BGP_NULL Subtype 256 The BGP_NULL Subtype is a reserved Subtype. 258 5.1.2. BGP_UPDATE Subtype 260 The BGP_UPDATE Subtype is used to encode BGP UPDATE messages. The 261 format of the MRT Message field for this Subtype is as follows: 263 0 1 2 3 264 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 265 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 266 | Source AS number | 267 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 268 | Source IP address | 269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 270 | Destination AS number | 271 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 272 | Destination IP address | 273 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 274 | BGP UPDATE Contents (variable) 275 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 277 The BGP UPDATE contents include the entire BGP UPDATE message which 278 follows the BGP Message Header. The BGP Message Header itself is not 279 included. 281 5.1.3. BGP_PREF_UPDATE Subtype 283 The BGP_PREF_UPDATE Subtype is not defined. 285 5.1.4. BGP_STATE_CHANGE Subtype 287 The BGP_STATE_CHANGE Subtype is used to record changes in the BGP 288 finite state machine. These FSM states and their numeric encodings 289 are defined in RFC 4271 [RFC4271], Appendix 1. Both the old state 290 value and the new state value are encoded as 2-octet numbers. The 291 format of the MRT Message field is as follows: 293 0 1 2 3 294 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 295 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 296 | Source AS number | 297 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 298 | Source IP address | 299 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 300 | Old State | New State | 301 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 303 5.1.5. BGP_SYNC Subtype 305 The BGP_SYNC Subtype is used to indicate a File Name where BGP Table 306 Dump messages should be recorded. The View # corresponds to the View 307 # provided in the TABLE_DUMP Type messages. The following format 308 applies to this Subtype: 310 0 1 2 3 311 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 312 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 313 | View # | 314 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 315 | File Name... (variable) 316 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 318 The File Name is terminated with a NULL (0) character. 320 5.1.6. BGP_OPEN Subtype 322 The BGP_OPEN Subtype is used to encode BGP OPEN messages. The format 323 of the MRT Message field for this Subtype is the same as the 324 BGP_UPDATE, however, the last field contains the contents of the BGP 325 OPEN message. 327 5.1.7. BGP_NOTIFY Subtype 329 The BGP_NOTIFY Subtype is used to encode BGP NOTIFICATION messages. 330 The format of the MRT Message field for this Subtype is the same as 331 the BGP_UPDATE, however, the last field contains the contents of the 332 BGP NOTIFICATION message. 334 5.1.8. BGP_KEEPALIVE Subtype 336 The BGP_KEEPALIVE Subtype is used to encode BGP KEEPALIVE messages. 337 The format of the MRT Message field for this Subtype is the same as 338 the BGP_UPDATE, however, the last field contains no information. 340 5.2. RIP Type 342 The RIP Type is used to export RIP protocol packets as defined in RFC 343 1058 [RFC1058]. The Subtype field is currently reserved for this 344 Type and SHOULD be set to 0. 346 The format of the MRT Message field for the RIP Type is as follows: 348 0 1 2 3 349 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 350 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 351 | Source IP address | 352 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 353 | Destination IP address | 354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 355 | RIP Message Contents (variable) 356 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 358 5.3. IDRP Type 360 The IDRP Type is used to export Inter-Domain-Routing Protocol (IDRP) 361 protocol information as defined in the ISO/IEC 10747 standard. The 362 Subtype field is unused. This Type is deprecated due to lack of 363 deployment of IDRP. 365 5.4. RIPNG Type 367 The RIPNG Type is used to export RIPNG protocol packets as defined in 368 RFC 2080 [RFC2080]. The Subtype field is currently reserved for this 369 Type and SHOULD be set to 0. 371 The format of the MRT Message field for the RIPNG Type is as follows: 373 0 1 2 3 374 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 375 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 376 | Source IP address | 377 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 378 | Destination IP address | 379 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 380 | RIPNG Message Contents (variable) 381 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 383 5.5. BGP4PLUS and BGP4PLUS_01 Types 385 The BGP4PLUS and BGP4PLUS_01 Types were defined to support IPv6 BGP 386 routing information. The BGP4PLUS Type was specified based on the 387 initial Internet Draft for Multiprotocol Extensions to BGP-4. The 388 BGP4PLUS_01 Type was specified to correspond to the -01 revision of 389 this Internet Draft. The two Types share the same definitions in 390 terms of their MRT format specifications. 392 The Subtype field definitions are shared with the BGP Type, however, 393 the address fields in the BGP_UPDATE, BGP_OPEN, BGP_NOTIFY, 394 BGP_KEEPALIVE, and BGP_STATE_CHANGE Subtype messages are extended to 395 16 octets for IPv6 addresses. As with the BGP Type, the BGP4PLUS and 396 BGP4PLUS_01 Types are deprecated as they superseded by the BGP4MP 397 Type. 399 5.6. OSPF Type 401 This Type supports the OSPF Protocol as defined in RFC 2328 402 [RFC2328]. The Subtype field may contain two possible values: 404 0 OSPF_STATE_CHANGE 405 1 OSPF_LSA_UPDATE 407 The format of the MRT Message field for the OSPF Type is as follows: 409 0 1 2 3 410 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 411 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 412 | Source IP address | 413 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 414 | Destination IP address | 415 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 416 | OSPF Message Contents (variable) 417 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 419 5.7. TABLE_DUMP Type 421 The TABLE_DUMP Type is used to encode the contents of a BGP Routing 422 Information Base (RIB). Each RIB entry is encoded in a distinct 423 sequential MRT record. The Subtype field is used to encode whether 424 the RIB entry contains IPv4 or IPv6 addresses. There are two 425 possible values for the Subtype as shown below. 427 1 AFI_IPv4 428 2 AFI_IPv6 430 The format of the TABLE_DUMP Type is illustrated below. 432 0 1 2 3 433 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 434 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 435 | View # | Sequence number | 436 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 437 | Prefix (variable) | 438 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 439 | Prefix Length | Status | 440 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 441 | Originated Time | 442 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 443 | Peer IP address (variable) | 444 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 445 | Peer AS | Attribute Length | 446 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 447 | BGP Attribute... (variable) 448 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 450 The View field is normally 0 and is intended for cases where an 451 implementation may have multiple RIB views (such as a route server). 452 The Sequence field is a simple incremental counter for each RIB 453 entry. A typical RIB dump will exceed the 16-bit bounds of this 454 counter and implementation should simply wrap back to zero and 455 continue incrementing the counter in such cases. 457 The Prefix field contains the IP address of a particular routing RIB 458 entry. The size of this field is dependent on the value of the 459 Subtype for this message. For AFI_IPv4, this field is 4 octets, for 460 AFI_IPv6, it is 16 octets in length. The Prefix Length field 461 indicates the length in bits of the prefix mask for the preceding 462 Prefix field. 464 The Status octet is not used in the TABLE_DUMP Type and SHOULD be set 465 to 1. 467 The Originated Time contains the 4-octet time at which this prefix 468 was heard. The value represents the time in seconds since 1 January 469 1970 00:00:00 UTC. 471 The Peer IP field is the IP address of the peer which provided the 472 update for this RIB entry. As with the Prefix field, the size of 473 this field is dependent on the Subtype. AFI_IPv4 indicates a 4 octet 474 field and an IPv4 address, while a Subtype of AFI_IPv6 requires a 16 475 octet field and an IPv6 address. The Peer AS field contains the AS 476 number of the peer. 478 Attribute length is the length of Attribute field and is 2-octets. 479 The Attribute field contains the attribute information for the RIB 480 entry. 482 5.8. TABLE_DUMP_V2 Type 484 The TABLE_DUMP_V2 type updates the TABLE_DUMP type to include 32-bit 485 ASN support and full support for BGP Multiprotocol extensions. It 486 also improves upon the space efficiency of the TABLE_DUMP type by 487 employing an index table for peers and permitting a single MRT record 488 per NLRI entry. The following subtypes are used with the 489 TABLE_DUMP_V2 type. 491 1 PEER_INDEX_TABLE 492 2 RIB_IPV4_UNICAST 493 3 RIB_IPV4_MULTICAST 494 4 RIB_IPV6_UNICAST 495 5 RIB_IPV6_MULTICAST 496 6 RIB_GENERIC 498 An initial PEER_INDEX_TABLE MRT record provides the BGP ID of the 499 collector, an optional view name, and a list of indexed peers. 500 Following the PEER_INDEX_TABLE MRT record, a series of MRT records 501 are used to encode RIB table entries. The header of the 502 PEER_INDEX_TABLE Subtype is shown below. The View Name is optional 503 and, if not present, the View Name Length MUST be set to 0. The View 504 Name encoding MUST follow the UTF-8 transformation format. 506 0 1 2 3 507 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 508 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 509 | Collector BGP ID | 510 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 511 | View Name Length | View Name (variable) | 512 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 513 | Peer Count | 514 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 516 The format of the peer entries is shown below. The PEER_INDEX_TABLE 517 record contains Peer Count peer entries. 519 0 1 2 3 520 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 521 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 522 | Peer Type | 523 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 524 | Peer BGP ID | 525 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 526 | Peer IP address (variable) | 527 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 528 | Peer AS (variable) | 529 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 531 The Peer Type, Peer BGP ID, Peer IP, and Peer AS fields are repeated 532 as indicated by the Peer Count field. The position of the Peer in 533 the PEER_INDEX_TABLE is used as an index in the subsequent 534 TABLE_DUMP_V2 MRT records. The index number begins with 0. 536 The Peer Type field is a bit field which encodes the type of the AS 537 and IP address as follows: 539 Bit 0 - unset for IPv4 Peer IP address, set for IPv6 540 Bit 1 - unset when Peer AS field is 16 bits, set when it's 32 bits 542 The records which follow the PEER_INDEX_TABLE record constitute the 543 RIB entries and include a header which specifies a sequence number, 544 NLRI, and a count of the number of RIB entries which follow. 546 The format for the RIB_IPV4_UNICAST, RIB_IPV4_MULTICAST, 547 RIB_IPV6_UNICAST, and RIB_IPV6_MULTICAST headers are shown below. 548 The Prefix Length and Prefix fields are encoded in the same manner as 549 the BGP NLRI encoding for IPV4 and IPV6 prefixes. Namely, the Prefix 550 field contains address prefixes followed by enough trailing bits to 551 make the end of the field fall on an octet boundary. Note that the 552 value of trailing bits is irrelevant. 554 0 1 2 3 555 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 556 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 557 | Sequence number | 558 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 559 | Prefix Length | 560 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 561 | Prefix (variable) | 562 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 563 | Entry Count | 564 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 566 The RIB_GENERIC header is shown below. It includes Address Family 567 Identifier (AFI), Subsequent AFI and a single NLRI entry. The NLRI 568 information is specific to the AFI and SAFI values. An 569 implementation which does not recognize particular AFI and SAFI 570 values SHOULD discard the remainder of the MRT record. 572 0 1 2 3 573 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 574 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 575 | Sequence number | 576 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 577 | Address Family Identifier |Subsequent AFI | 578 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 579 | Network Layer Reachability Information (variable) | 580 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 581 | Entry Count | 582 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 584 The RIB entry headers are followed by a series of RIB entries which 585 are repeated Entry Count times. These entries share a common format 586 as shown below. They include a Peer Index from the PEER_INDEX_TABLE 587 MRT record, an originated time for the RIB entry, and the BGP path 588 attribute length and attributes encoded as provided in a BGP Update 589 message. 591 0 1 2 3 592 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 593 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 594 | Peer Index | 595 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 596 | Originated Time | 597 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 598 | Attribute Length | 599 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 600 | BGP Attributes... (variable) 601 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 603 There is one exception to the encoding of BGP attributes for the BGP 604 MP_REACH_NLRI attribute (BGP Type Code 14) [RFC 4760]. Since the 605 AFI, SAFI, and NLRI information is already encoded in the 606 MULTIPROTOCOL header, only the Next Hop Address Length and Next Hop 607 Address fields are included. The Reserved field is omitted. The 608 attribute length is also adjusted to reflect only the length of the 609 Next Hop Address Length and Next Hop Address fields. 611 5.9. BGP4MP Type 613 This Type was initially defined in the Zebra software package for the 614 BGP protocol with multiprotocol extension support as defined by RFC 615 4760 [RFC4760]. It supersedes the BGP, BGP4PLUS, BGP4PLUS_01 Types. 616 The BGP4MP Type has four Subtypes which are defined as follows: 618 0 BGP4MP_STATE_CHANGE 619 1 BGP4MP_MESSAGE 620 2 BGP4MP_ENTRY *DEPRECATED* 621 3 BGP4MP_SNAPSHOT 622 4 BGP4MP_STATE_CHANGE_AS4 623 5 BGP4MP_MESSAGE_AS4 625 5.9.1. BGP4MP_STATE_CHANGE Subtype 627 This record is used to encode state changes in the BGP finite state 628 machine. As with the BGP_STATE_CHANGE Subtype, the BGP FSM states 629 are encoded in the Old State and New State fields to indicate the 630 previous and current state. The format is illustrated below: 632 0 1 2 3 633 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 634 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 635 | Source AS number | Destination AS number | 636 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 637 | Interface Index | Address Family | 638 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 639 | Source IP address (variable) | 640 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 641 | Destination IP address (variable) | 642 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 643 | Old State | New State | 644 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 646 While BGP4MP_STATE_CHANGE message is similar to the BGP_STATE_CHANGE 647 message, it also includes interface index and Address Family fields. 648 As with the BGP_STATE_CHANGE message, the FSM states and their 649 numeric encodings are defined in RFC 4271 [RFC4271], Appendix 1. The 650 interface index provides the interface number of the peering session. 651 The index value is OPTIONAL and MAY be zero if unknown or 652 unsupported. The Address Family indicates what types of addresses 653 are in the the address fields. At present, the following AFI Types 654 are supported: 656 1 AFI_IPv4 657 2 AFI_IPv6 659 5.9.2. BGP4MP_MESSAGE Subtype 661 This Subtype is used to encode BGP Messages. It is similar to the 662 BGP_UPDATE Subtype, except that is can be used to encode any Type of 663 message (not just BGP UPDATES). In order to determine the BGP 664 message Type, the entire BGP message, including the BGP header, is 665 included in the BGP Message field. The BGP4MP_MESSAGE fields are 666 shown below: 668 0 1 2 3 669 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 670 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 671 | Source AS number | Destination AS number | 672 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 673 | Interface Index | Address Family | 674 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 675 | Source IP address (variable) | 676 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 677 | Destination IP address (variable) | 678 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 679 | BGP Message... (variable) 680 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 682 The interface index provides the interface number of the peering 683 session. The index value is OPTIONAL and MAY be zero if unknown or 684 unsupported. The Address Family indicates what types of addresses 685 are in the the subsequent address fields. At present, the following 686 AFI Types are supported: 688 1 AFI_IPv4 689 2 AFI_IPv6 691 Note that the Address Family value only applies to the IP addresses 692 contained in the MRT header. The BGP4MP_MESSAGE Subtype is otherwise 693 transparent to the contents of the actual message which may contain 694 any valid AFI/SAFI values. Only one BGP message may be encoded in 695 the BGP4MP_MESSAGE Subtype. 697 5.9.3. BGP4MP_ENTRY Subtype 699 This Subtype is similar to the TABLE_DUMP Type and is used to record 700 RIB table entries. It extends the TABLE_DUMP Type to include true 701 multiprotocol support. However, this type does not support 32-bit AS 702 numbers and has not been widely implemented. This type is deprecated 703 in favor of the TABLE_DUMP_V2 which includes 32-bit AS number support 704 and a more compact format. 706 0 1 2 3 707 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 708 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 709 | Source AS number | Destination AS number | 710 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 711 | Interface Index | Address Family | 712 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 713 | Source IP address (variable) | 714 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 715 | Destination IP address (variable) | 716 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 717 | View # | Status | 718 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 719 | Time last change | 720 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 721 | Address Family | SAFI | Next-Hop-Len | 722 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 723 | Next Hop Address (variable) | 724 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 725 | Prefix Length | 726 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 727 | Address Prefix (variable) | 728 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 729 | Attribute Length | 730 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 731 | BGP Attribute... (variable) 732 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 734 5.9.4. BGP4MP_SNAPSHOT Subtype 736 This Subtype is used to indicate a filename containing BGP4MP_ENTRY 737 records. It is similar to the BGP_SYNC message Subtype and shares 738 the same fields. 740 0 1 2 3 741 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 742 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 743 | View # | 744 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 745 | File Name... (variable) 746 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 748 5.9.5. BGP4MP_STATE_CHANGE_AS4 Subtype 750 This Subtype updates the BGP4MP_STATE_CHANGE Subtype to support 32BIT 751 Autonomous System numbers. As with the BGP4MP_STATE_CHANGE Subtype, 752 the BGP FSM states are encoded in the Old State and New State fields 753 to indicate the previous and current state. Aside from the extension 754 of the source and destination AS fields to 32 bits, this subtype is 755 otherwise identical to the BGP4MP_STATE_CHANGE Subtype. The 756 BGP4MP_STATE_CHANGE_AS4 fields are shown below: 758 0 1 2 3 759 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 760 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 761 | Source AS number | 762 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 763 | Destination AS number | 764 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 765 | Interface Index | Address Family | 766 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 767 | Source IP address (variable) | 768 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 769 | Destination IP address (variable) | 770 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 771 | Old State | New State | 772 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 774 5.9.6. BGP4MP_MESSAGE_AS4 Subtype 776 This Subtype updates the BGP4MP_MESSAGE Subtype to support 32BIT 777 Autonomous System numbers. The BGP4MP_MESSAGE_AS4 fields are shown 778 below: 780 0 1 2 3 781 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 782 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 783 | Source AS number | 784 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 785 | Destination AS number | 786 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 787 | Interface Index | Address Family | 788 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 789 | Source IP address (variable) | 790 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 791 | Destination IP address (variable) | 792 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 793 | BGP Message... (variable) 794 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 796 5.10. BGP4MP_ET 798 This Type was initially defined in the Sprint Labs Python Routing 799 Toolkit (PyRT). It extends the MRT common header field to include a 800 32-bit microsecond timestamp field. The type and subtype field 801 definitions remain as defined for the BGP4MP Type. The 32-bit 802 microsecond timestamp immediately follows the length field in the MRT 803 common header and precedes all other fields in the message. The 32- 804 bit microsecond field is included in the computation of the length 805 field value. The MRT common header modification is illustrated 806 below. 808 0 1 2 3 809 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 810 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 811 | Timestamp | 812 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 813 | Type | Subtype | 814 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 815 | Length | 816 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 817 | microsecond timestamp | 818 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 819 | Message... (variable) 820 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 822 5.11. ISIS Type 824 This Type was initially defined in the Sprint Labs Python Routing and 825 supports the IS-IS routing protocol as defined in RFC 1195 [RFC1195]. 826 There is no Type specific header for the ISIS Type. The Subtype code 827 for this Type is undefined. The ISIS PDU directly follows the MRT 828 common header fields. 830 5.12. ISIS_ET Type 832 The ISIS_ET Type extends the the ISIS Type to support microsecond 833 timestamps. As with the BGP4MP_ET Type, a 32-bit microsecond 834 timestamp field is appended to the MRT common header after the length 835 field. The ISIS_ET Type is otherwise identical to the ISIS Type. 837 5.13. OSPFv3 Type 839 The OSPFv3 Type extends the original OSPF Type to support IPv6 840 addresses for the OSPFv3 protocol as defined in RFC 2740 [RFC2740]. 841 The format of the MRT Message field for the OSPFv3 Type is as 842 follows: 844 0 1 2 3 845 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 846 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 847 | Address Family | 848 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 849 | Source IP address (variable) | 850 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 851 | Destination IP address (variable) | 852 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 853 | OSPF Message Contents (variable) 854 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 856 5.14. OSPFv3_ET Type 858 The OSPFv3_ET Type extends the the OSPFv3 Type to support microsecond 859 timestamps. As with the BGP4MP_ET Type, a 32-bit microsecond 860 timestamp field is appended to the MRT common header after the length 861 field and its length is included in the calculation of the length 862 field value. The OSPFv3_ET Type is otherwise identical to the OSPFv3 863 Type. 865 6. IANA Considerations 867 This section provides guidance to the Internet Assigned Numbers 868 Authority (IANA) regarding registration of values related to the MRT 869 specification, in accordance with BCP 26, RFC 2434 [RFC2434]. 871 There are two name spaces in MRT that require registration: Type 872 Codes and Subtype Codes. 874 MRT is not intended as a general-purpose specification for protocol 875 information export, and allocations should not be made for purposes 876 unrelated to routing protocol information export. 878 The following policies are used here with the meanings defined in BCP 879 26: "Specification Required", "IETF Consensus". 881 6.1. Type Codes 883 Type Codes have a range from 0 to 65535, of which 0-64 have been 884 allocated. New Type Codes MUST be allocated starting at 65. Type 885 Codes 65 - 32767 are to be assigned by IETF Consensus. Type Codes 886 32768 - 65535 are assigned based on Specification Required. 888 6.2. Subtype Codes 890 Subtype Codes have a range from 0 to 65535. Subtype definitions are 891 specific to a particular Type Code definition. New Subtype Code 892 definition must reference an existing Type Code to which the Subtype 893 belongs. As Subtype Codes are specific to Type Codes, new numbers 894 must be unique for the particular Type Code to which the Subtype 895 applies. Subtype Codes specific to the Type Codes 0 - 32767 are 896 assigned by IETF Consensus. Subtype Codes specific to Type Codes 897 32768 - 65535 are assigned based on Specification Required. 899 7. Security Considerations 901 The MRT Format utilizes a structure which can store routing protocol 902 information data. The fields defined in the MRT specification are of 903 a descriptive nature and provide information that is useful to 904 facilitate the analysis of routing data. As such, the fields 905 currently defined in the MRT specification do not in themselves 906 create additional security risks, since the fields are not used to 907 induce any particular behavior by the recipient application. 909 8. References 911 8.1. Normative References 913 [RFC1058] Hedrick, C., "Routing Information Protocol", RFC 1058, 914 June 1988. 916 [RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and 917 dual environments", RFC 1195, December 1990. 919 [RFC2080] Malkin, G. and R. Minnear, "RIPng for IPv6", RFC 2080, 920 January 1997. 922 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 923 Requirement Levels", BCP 14, RFC 2119, March 1997. 925 [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. 927 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an 928 IANA Considerations Section in RFCs", BCP 26, RFC 2434, 929 October 1998. 931 [RFC2740] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6", 932 RFC 2740, December 1999. 934 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 935 Protocol 4 (BGP-4)", RFC 4271, January 2006. 937 [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, 938 "Multiprotocol Extensions for BGP-4", RFC 4760, 939 January 2007. 941 8.2. Informative References 943 [MRT PROG GUIDE] 944 Labovitz, C., "MRT Programmer's Guide", November 1999, 945 . 947 Authors' Addresses 949 Larry Blunk 950 Merit Network 952 Email: ljb@merit.edu 954 Manish Karir 955 Merit Network 957 Email: mkarir@merit.edu 959 Craig Labovitz 960 Arbor Networks 962 Email: labovit@arbor.net 964 Full Copyright Statement 966 Copyright (C) The IETF Trust (2007). 968 This document is subject to the rights, licenses and restrictions 969 contained in BCP 78, and except as set forth therein, the authors 970 retain all their rights. 972 This document and the information contained herein are provided on an 973 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 974 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 975 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 976 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 977 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 978 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 980 Intellectual Property 982 The IETF takes no position regarding the validity or scope of any 983 Intellectual Property Rights or other rights that might be claimed to 984 pertain to the implementation or use of the technology described in 985 this document or the extent to which any license under such rights 986 might or might not be available; nor does it represent that it has 987 made any independent effort to identify any such rights. Information 988 on the procedures with respect to rights in RFC documents can be 989 found in BCP 78 and BCP 79. 991 Copies of IPR disclosures made to the IETF Secretariat and any 992 assurances of licenses to be made available, or the result of an 993 attempt made to obtain a general license or permission for the use of 994 such proprietary rights by implementers or users of this 995 specification can be obtained from the IETF on-line IPR repository at 996 http://www.ietf.org/ipr. 998 The IETF invites any interested party to bring to its attention any 999 copyrights, patents or patent applications, or other proprietary 1000 rights that may cover technology that may be required to implement 1001 this standard. Please address the information to the IETF at 1002 ietf-ipr@ietf.org. 1004 Acknowledgment 1006 Funding for the RFC Editor function is provided by the IETF 1007 Administrative Support Activity (IASA).