idnits 2.17.1 draft-petrie-grow-mrt-bmp-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. 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 and authors Copyright Line does not match the current year -- The document date (November 1, 2019) is 1638 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '1' on line 156 Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Global Routing Operations C. Petrie 3 Internet-Draft NTT 4 Intended status: Standards Track November 1, 2019 5 Expires: May 4, 2020 7 Storing BMP messages in MRT Format 8 draft-petrie-grow-mrt-bmp-00 10 Abstract 12 This document extends the Multi-threaded Routing Toolkit (MRT) export 13 format to support the storage of BMP messages. 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at https://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on May 4, 2020. 32 Copyright Notice 34 Copyright (c) 2019 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (https://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 2. BMP Type . . . . . . . . . . . . . . . . . . . . . . . . . . 2 51 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 52 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 53 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 54 5.1. Normative References . . . . . . . . . . . . . . . . . . 4 55 5.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 4 56 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 58 1. Introduction 60 The MRT record format [RFC6396] was developed to provide researchers 61 and engineers a means to encapsulate, export, and archive routing 62 protocol transactions and routing information base snapshots. 64 BMP [RFC7854] was developed to monitor BGP sessions, and also 65 includes messages containing routing protocol transactions and 66 Routing Information Base contents and changes. BMP [RFC7854] does 67 not define a mechanism for exporting and archiving BMP messages. MRT 68 can be a suitable format for this. 70 This document contains an optional extension to the MRT format 71 [RFC6396] and defines additional MRT types to permit storage of BMP 72 messages. 74 2. BMP Type 76 This document defines the following new MRT Types: 78 o BMP 80 o BMP_ET 82 These MRT types support the BMP protocol. They are used to encode 83 the exchange of BMP messages. The _ET variant is for use with the 84 Extended Timestamp MRT Header. 86 The format of the MRT Message field for the BMP types is as follows: 88 0 1 2 3 89 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 90 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 91 | Address Family | 92 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 93 | Remote IP Address (variable) | 94 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 95 | Local IP Address (variable) | 96 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 97 | BMP Message Contents (variable) 98 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 100 Figure 1 102 The Address Family indicates what types of addresses are in the 103 subsequent address fields. At present, the following AFI Types are 104 supported: 106 1 - AFI_IPv4 108 2 - AFI_IPv6 110 The Address Family value only applies to the IP addresses contained 111 in the MRT header. The BMP type is otherwise transparent to the 112 contents of the actual message that may contain any valid AFI/SAFI 113 values. 115 Remote and Local IP addresses refer to the endpoints of the TCP 116 connection carrying the BMP session, from the perspective of the BMP 117 monitoring station that is recording these messages 119 3. IANA Considerations 121 This document requests that IANA assign Type codes to the MRT name 122 space [1]: 124 BMP = TBD1 (Section 2) 126 BMP_ET = TBD2 (Section 2) 128 In this draft document this is requested from the Specification 129 Required range, this may be changed to the IETF Review range by a 130 later version of this document. 132 4. Security Considerations 134 It is not believed that this document adds any additional security 135 considerations. 137 However, the security considerations of [RFC6396] and [RFC7854] are 138 equally applicable to this document. 140 5. References 142 5.1. Normative References 144 [RFC6396] Blunk, L., Karir, M., and C. Labovitz, "Multi-Threaded 145 Routing Toolkit (MRT) Routing Information Export Format", 146 RFC 6396, DOI 10.17487/RFC6396, October 2011, 147 . 149 [RFC7854] Scudder, J., Ed., Fernando, R., and S. Stuart, "BGP 150 Monitoring Protocol (BMP)", RFC 7854, 151 DOI 10.17487/RFC7854, June 2016, 152 . 154 5.2. URIs 156 [1] https://www.iana.org/assignments/mrt/mrt.xhtml 158 Author's Address 160 Colin Petrie 161 NTT 162 Siriusdreef 70-72 163 Hoofddorp 2132 WT 164 NL 166 Email: colin@ntt.net