idnits 2.17.1 draft-patki-srv6-ipfix-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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (June 24, 2020) is 1401 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: '0' on line 266 -- Looks like a reference, but probably isn't: '1' on line 268 -- Looks like a reference, but probably isn't: '2' on line 270 -- Possible downref: Non-RFC (?) normative reference: ref. 'IANA-IPFIX' Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 SPRING D. Patki 3 Internet-Draft Cisco Systems, Inc. 4 Intended status: Standards Track June 24, 2020 5 Expires: December 26, 2020 7 IPFIX export of Segment Routing IPv6 information 8 draft-patki-srv6-ipfix-00 10 Abstract 12 This document introduces new IP Flow Information Exchange (IPFIX) 13 information elemements for exporting IPv6 Segment Routing Header 14 (SRH). 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at https://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on December 26, 2020. 33 Copyright Notice 35 Copyright (c) 2020 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (https://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 51 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 52 2. New IPFIX Information Elements . . . . . . . . . . . . . . . 3 53 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 54 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 55 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 56 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 57 6.1. Normative References . . . . . . . . . . . . . . . . . . 4 58 6.2. Informative References . . . . . . . . . . . . . . . . . 4 59 Appendix A. Encoding Example . . . . . . . . . . . . . . . . . . 5 60 A.1. Template Record . . . . . . . . . . . . . . . . . . . . . 5 61 A.2. Data Set . . . . . . . . . . . . . . . . . . . . . . . . 6 62 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8 64 1. Introduction 66 IP Flow Information Export (IPFIX) [RFC7011] provides network 67 administrators with traffic flow information using the Information 68 Elements (IEs) defined in the "IPFIX Information Elements" registry 69 [IANA-IPFIX]. Based on the traffic flow information, network 70 administrators know the amount and direction of the traffic in their 71 network and can then optimize the network when needed. For example, 72 the collected information could be used for traffic monitoring and, 73 optionally, for traffic optimization according to the operator's 74 policy. 76 A new type of Routing Extension Header called Segment Routing Header 77 (SRH) is defined by [RFC8754] which is used for applying Segment 78 Routing on IPv6 data plane. This document defined new IPFIX IEs to 79 export the contents of SRH. 81 Currently this document is limited to exporting based SRH excluding 82 the TLV, however, further versions of this document intend to include 83 TLVs and variations in the SRH that may be defined in the near 84 future. 86 1.1. Requirements Language 88 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 89 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 90 document are to be interpreted as described in [RFC2119]. 92 2. New IPFIX Information Elements 94 This section defines new IPFIX IEs corresponding to various fields in 95 the SRH. 97 ipv6SRHLastEntry 98 The index (zero based) in the Segment List in the SRH, of the last 99 element of the Segment List. 101 ipv6SRHFlags 102 8-bit flags defined in the SRH. 104 ipv6SRHTag 105 Tag is an identifier that marks a packet as part of a class or 106 group of packets, e.g., packets sharing the same set of 107 properties. This information element contains the value of the 108 Tag field. 110 ipv6SRHSegment 111 128-bit IPv6 address that represents an SRv6 segment. 113 ipv6SRHSegmentList 114 A basicList [RFC6313][RFC7012] of ipv6SRHSegment that contains the 115 Segment List in the SRH header. Like in the SRH header, the 116 basicList is encoded starting from the last segment of the SR 117 Policy. That is, the first element of the basicList contains the 118 last segment of the SR Policy, the second element contains the 119 penultimate segment of the SR Policy, and so on. This information 120 element has variable length. 122 3. IANA Considerations 124 This document specifies IPFIX IEs to enable export of Segment Routing 125 IPv6 information. IANA needs to assign the following Element IDs for 126 these IEs in the "IPFIX Information Elements" registry [IANA-IPFIX]: 128 -------------------------------------------------------------------- 129 | Element | Name | Abstract | Data Type | Refer- | 130 | ID | | Data Type | Semantics | ence | 131 -------------------------------------------------------------------- 132 | TBD1 | ipv6SRHLastEntry | unsigned8 | identifier | RFC8754 | 133 | TBD2 | ipv6SRHFlags | unsigned8 | flags | RFC8754 | 134 | TBD3 | ipv6SRHTag | unsigned16 | identifier | RFC8754 | 135 | TBD4 | ipv6SRHSegment | ipv6address| default | RFC8754 | 136 | TBD5 | ipv6SRHSegmentList | basicList | list | RFC8754 | 137 -------------------------------------------------------------------- 139 4. Security Considerations 141 The security considerations in [RFC7011] apply. 143 5. Acknowledgements 145 TBD 147 6. References 149 6.1. Normative References 151 [IANA-IPFIX] 152 IANA, "IP Flow Information Export (IPFIX) Entities", 153 . 155 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 156 Requirement Levels", BCP 14, RFC 2119, 157 DOI 10.17487/RFC2119, March 1997, 158 . 160 [RFC6313] Claise, B., Dhandapani, G., Aitken, P., and S. Yates, 161 "Export of Structured Data in IP Flow Information Export 162 (IPFIX)", RFC 6313, DOI 10.17487/RFC6313, July 2011, 163 . 165 [RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken, 166 "Specification of the IP Flow Information Export (IPFIX) 167 Protocol for the Exchange of Flow Information", STD 77, 168 RFC 7011, DOI 10.17487/RFC7011, September 2013, 169 . 171 [RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J., 172 Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header 173 (SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020, 174 . 176 6.2. Informative References 178 [RFC7012] Claise, B., Ed. and B. Trammell, Ed., "Information Model 179 for IP Flow Information Export (IPFIX)", RFC 7012, 180 DOI 10.17487/RFC7012, September 2013, 181 . 183 Appendix A. Encoding Example 185 In this section, an example is provided to show IPFIX encoding format 186 for the newly introduced IEs. Template definition and data set 187 corresponding to 3 observed SRH headers are illustrated. 189 Observed SRH headers: 191 SRH 1: 192 Segments Left = 2, Last Entry = 2, Flags = 0, Tag = 0, 193 Segment List = 1111::1, 2222::2, 3333::3 195 SRH 2: 196 Segments Left = 1, Last Entry = 1, Flags = 0, Tag = 100, 197 Segment List = 4444::4, 5555::5 199 SRH 3: 200 Segments Left = 1, Last Entry = 2, Flags = 0, Tag = 200, 201 Segment List = 6666::6, 7777::7, 8888::8 203 A.1. Template Record 205 Sample template consisting of the new IEs: 207 0 1 2 3 208 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 209 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 210 | SET ID = 2 | Length = 24 | 211 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 212 | Template ID = 256 | Field Count = 4 | 213 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 214 |0| ipv6SRHLastEntry = TBD1 | Field Length = 1 | 215 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 216 |0| ipv6SRHFlags = TBD2 | Field Length = 1 | 217 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 218 |0| ipv6SRHTag = TBD3 | Field Length = 2 | 219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 220 |0| ipv6SRHSegmentList = TBD5 | Field Length = 0xFFFF | 221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 223 Figure 1: Sample Template 225 A.2. Data Set 227 Data set for the observed SRH headers using the template defined 228 above: 230 0 1 2 3 231 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 232 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 233 | SET ID = 256 | Length = 168 | 234 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 235 | ipv6SRHLast | ipv6SRHFlags | ipv6SRHTag = 0 | 236 | Entry = 2 | = 0 | | 237 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 238 | 255 | List Length = 53 |semantic=allof | 239 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 240 | ipv6SRHSegment = TBD4 | Field Length = 16 | 241 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 242 | Segment List[0] = 1111::1 (16 bytes) | 243 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 244 | Segment List[1] = 2222::2 (16 bytes) | 245 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 246 | Segment List[2] = 3333::3 (16 bytes) | 247 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 248 | ipv6SRHLast | ipv6SRHFlags | ipv6SRHTag = 100 | 249 | Entry = 1 | = 0 | | 250 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 251 | 255 | List Length = 37 |semantic=allof | 252 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 253 | ipv6SRHSegment = TBD4 | Field Length = 16 | 254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 255 | Segment List[0] = 4444::4 (16 bytes) | 256 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 257 | Segment List[1] = 5555::5 (16 bytes) | 258 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 259 | ipv6SRHLast | ipv6SRHFlags | ipv6SRHTag = 200 | 260 | Entry = 2 | = 0 | | 261 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 262 | 255 | List Length = 53 |semantic=allof | 263 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 264 | ipv6SRHSegment = TBD4 | Field Length = 16 | 265 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 266 | Segment List[0] = 6666::6 (16 bytes) | 267 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 268 | Segment List[1] = 7777::7 (16 bytes) | 269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 270 | Segment List[2] = 8888::8 (16 bytes) | 271 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 273 Figure 2: Data Set 275 Author's Address 277 Dhananjay Patki 278 Cisco Systems, Inc. 279 Cessna Business Park SEZ, Kadubeesanahalli 280 Bangalore, Karnataka 560087 281 India 283 Email: dhpatki@cisco.com