idnits 2.17.1 draft-li-opsawg-ipfix-extended-message-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 : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([RFC7011], [I-D.ietf-opsawg-ipfix-bgp-community]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (June 30, 2017) is 2484 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) == Missing Reference: 'RFC768' is mentioned on line 182, but not defined == Missing Reference: 'RFC793' is mentioned on line 183, but not defined ** Obsolete undefined reference: RFC 793 (Obsoleted by RFC 9293) -- Possible downref: Non-RFC (?) normative reference: ref. 'IANA-IPFIX' == Outdated reference: A later version (-12) exists of draft-ietf-opsawg-ipfix-bgp-community-02 -- Obsolete informational reference (is this intentional?): RFC 4960 (Obsoleted by RFC 9260) Summary: 2 errors (**), 0 flaws (~~), 4 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 opsawg Z. Li 3 Internet-Draft China Mobile 4 Intended status: Standards Track P. Aitken 5 Expires: January 1, 2018 Brocade Communications Systems, Inc. 6 June 30, 2017 8 Extended Length Message Support for IP Flow Information Export (IPFIX) 9 draft-li-opsawg-ipfix-extended-message-00 11 Abstract 13 The specification of the IP Flow Information Export (IPFIX) Protocol 14 [RFC7011] defines an IPFIX Message length of 16 bits. As new 15 Information Elements (IEs) are introduced in IPFIX to export long 16 information, such as the BGP community information 17 [I-D.ietf-opsawg-ipfix-bgp-community], an IPFIX Message no longer has 18 sufficient space to fit all the information of a specific flow. This 19 document updates the IPFIX specification by extending the IPFIX 20 Message length from 16 bits to 32 bits. For backwards compatibility, 21 a new version of IPFIX (i.e., 11) is introduced to support the 32-bit 22 Message length. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on January 1, 2018. 41 Copyright Notice 43 Copyright (c) 2017 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 60 3. IPFIX Extended Length Message . . . . . . . . . . . . . . . . 3 61 3.1. IPFIX Extended Length Message Header . . . . . . . . . . 3 62 3.2. IPFIX Extended Length Set Header . . . . . . . . . . . . 3 63 3.3. IPFIX Extended Variable-Length IE . . . . . . . . . . . . 4 64 4. Transport Protocol Considerations . . . . . . . . . . . . . . 4 65 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 66 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 67 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 68 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 69 8.1. Normative References . . . . . . . . . . . . . . . . . . 5 70 8.2. Informative References . . . . . . . . . . . . . . . . . 5 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 73 1. Introduction 75 The IP Flow Information Export (IPFIX) Protocol [RFC7011] provides 76 network administrators with traffic flow information using the 77 Information Elements (IEs) defined in IANA's IPFIX registry 78 [IANA-IPFIX]. [RFC7011] specifies an IPFIX Message length of 16 79 bits. As new IEs are introduced in IPFIX to export long information, 80 such as the BGP community information 81 [I-D.ietf-opsawg-ipfix-bgp-community], one IPFIX Message no longer 82 has sufficient space to fit all the information of a specific flow. 83 The maximum IPFIX message size needs to be extended beyond 65535 84 octets. This document updates the IPFIX specification by extending 85 the IPFIX Message length from 16 bits to 32 bits, which means the 86 maximum IPFIX message size is 4 giga bytes. For backwards 87 compatibility, a new version of IPFIX (i.e., 11) is introduced to 88 support the 32-bit Message length. 90 2. Terminology 92 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 93 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 94 document are to be interpreted as described in [RFC2119]. 96 3. IPFIX Extended Length Message 98 The goal of this document is to allow the export of IPFIX messages up 99 to 4294967295 (4 giga) octets to satisfy the two situations that may 100 result in the IPFIX message beyond 65535 octets. One is the IPFIX 101 message consisting of many small fields where each field is 8-bits or 102 16-bits long. The other one is the IPFIX message consisting of at 103 least one IE which is longer than 65535 octets, such as the IEs 104 defined in [I-D.ietf-opsawg-ipfix-bgp-community]. 106 To satisfy the two situations, this document extends the following 107 length fields to 32 bits: the Length field in the IPFIX Message 108 Header, the Length field in the Set Header and the Length field in 109 the variable-length IE. 111 3.1. IPFIX Extended Length Message Header 113 The IPFIX Message Header with a 32 bits length field is called the 114 IPFIX Extended Length Message Header, whose format is shown in 115 Figure 1. The version number MUST be 11. The length field is 116 32-bits long. The meanings and other specifications of the fields in 117 the Extended Length Message Header are in accordance with [RFC7011]. 118 Please refer to Figure F in [RFC7011]. 120 0 1 2 3 121 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 122 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 123 | Version Number | 124 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 125 | Length | 126 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 127 | Export Time | 128 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 129 | Sequence Number | 130 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 131 | Observation Domain ID | 132 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 Figure 1: IPFIX Extended Length Message Header Format 136 3.2. IPFIX Extended Length Set Header 138 The IPFIX Set Header with a 32 bits length field is called the IPFIX 139 Extended Length Set Header, whose format is shown in Figure 2. The 140 meanings and other specifications of the fields in the Extended 141 Length Set Header are in accordance with [RFC7011]. Please refer to 142 Figure I in [RFC7011]. 144 0 1 2 3 145 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 146 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 147 | Set ID | 148 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 149 | Length | 150 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 152 Figure 2: Extended Length Set Header Format 154 3.3. IPFIX Extended Variable-Length IE 156 The Extended Variable-Length IE allows export of variable-length IEs 157 with size greater than or equal to 65535 octets, the length field of 158 which is extended to 32 bits as shown in Figure 3. The meanings and 159 other specifications of the fields in the Extended Variable-Length IE 160 are in accordance with [RFC7011]. Please refer to Figure S in 161 [RFC7011]. 163 0 1 2 3 164 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 165 +-+-+-+-+-+-+-+-+ 166 | 255 | 167 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 168 | Length (0 to 4294967295) | 169 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 170 | IE | 171 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 172 | ... continuing as needed | 173 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 175 Figure 3: Extended Variable-Length IE 177 4. Transport Protocol Considerations 179 As per section 10 of RFC7011, the IPFIX Protocol is transport 180 protocol independent. SCTP [RFC4960] using the Partially Reliable 181 SCTP (PR-SCTP) extension as specified in [RFC3758] MUST be 182 implemented by all compliant implementations. UDP [RFC768] MAY also 183 be implemented by compliant implementations. TCP [RFC793] MAY also 184 be implemented by compliant implementations. The Collecting Process 185 of a compliant implementation supporting IPFIX Extended Length 186 Message MUST be able to handle IPFIX Message lengths of up to 187 4294967295 octets. 189 5. Security Considerations 191 This extension to IPFIX does not change IPFIX's underlying security 192 issues, please refer to RFC7011. 194 6. IANA Considerations 196 A new IPFIX Version Number value of 11 is reserved in IANA's IPFIX 197 registry [IANA-IPFIX] for the IPFIX Extended Length Message specified 198 in this document. 200 7. Acknowledgements 202 The authors would like to thank Ignas Bagdonas and Stewart Bryant for 203 their constructive discussion. 205 8. References 207 8.1. Normative References 209 [IANA-IPFIX] 210 IANA, "IPFIX Information Elements registry", 211 . 213 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 214 Requirement Levels", BCP 14, RFC 2119, 215 DOI 10.17487/RFC2119, March 1997, 216 . 218 [RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken, 219 "Specification of the IP Flow Information Export (IPFIX) 220 Protocol for the Exchange of Flow Information", STD 77, 221 RFC 7011, DOI 10.17487/RFC7011, September 2013, 222 . 224 8.2. Informative References 226 [I-D.ietf-opsawg-ipfix-bgp-community] 227 Li, Z., Gu, R., and J. Dong, "Export BGP community 228 information in IP Flow Information Export (IPFIX)", draft- 229 ietf-opsawg-ipfix-bgp-community-02 (work in progress), 230 June 2017. 232 [RFC3758] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P. 233 Conrad, "Stream Control Transmission Protocol (SCTP) 234 Partial Reliability Extension", RFC 3758, 235 DOI 10.17487/RFC3758, May 2004, 236 . 238 [RFC4960] Stewart, R., Ed., "Stream Control Transmission Protocol", 239 RFC 4960, DOI 10.17487/RFC4960, September 2007, 240 . 242 Authors' Addresses 244 Zhenqiang Li 245 China Mobile 246 32 Xuanwumen West Ave, Xicheng District 247 Beijing 100053 248 China 250 Email: li_zhenqiang@hotmail.com 252 Paul Aitken 253 Brocade Communications Systems, Inc. 254 19a Canning Street, Level 3 255 Edinburgh, Scotland EH3 8EG 256 United Kingdom 258 Email: paitken@brocade.com