idnits 2.17.1 draft-brockners-inband-oam-data-01.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 (July 18, 2016) is 2838 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- -- Looks like a reference, but probably isn't: '0' on line 291 -- Looks like a reference, but probably isn't: '1' on line 232 == Unused Reference: 'P4' is defined on line 563, but no explicit reference was found in the text Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group F. Brockners 3 Internet-Draft S. Bhandari 4 Intended status: Experimental C. Pignataro 5 Expires: January 19, 2017 Cisco 6 H. Gredler 7 RtBrick Inc. 8 J. Leddy 9 Comcast 10 S. Youell 11 JMPC 12 July 18, 2016 14 Data Formats for In-band OAM 15 draft-brockners-inband-oam-data-01 17 Abstract 19 In-band operation, administration and maintenance (OAM) records 20 operational and telemetry information in the packet while the packet 21 traverses a path between two points in the network. This document 22 discusses the data types and data formats for in-band OAM data 23 records. In-band OAM data records can be embedded into a variety of 24 transports such as NSH, Segment Routing, VXLAN-GPE, native IPv6 (via 25 extension header), or IPv4. In-band OAM is to complement current 26 out-of-band OAM mechanisms based on ICMP or other types of probe 27 packets. 29 Status of This Memo 31 This Internet-Draft is submitted in full conformance with the 32 provisions of BCP 78 and BCP 79. 34 Internet-Drafts are working documents of the Internet Engineering 35 Task Force (IETF). Note that other groups may also distribute 36 working documents as Internet-Drafts. The list of current Internet- 37 Drafts is at http://datatracker.ietf.org/drafts/current/. 39 Internet-Drafts are draft documents valid for a maximum of six months 40 and may be updated, replaced, or obsoleted by other documents at any 41 time. It is inappropriate to use Internet-Drafts as reference 42 material or to cite them other than as "work in progress." 44 This Internet-Draft will expire on January 19, 2017. 46 Copyright Notice 48 Copyright (c) 2016 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (http://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 64 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 65 3. In-band OAM Data Types and Data Format . . . . . . . . . . . 3 66 3.1. In-band OAM Tracing Option . . . . . . . . . . . . . . . 4 67 3.1.1. In-band OAM Trace Type and Node Data Element . . . . 7 68 3.2. In-band OAM Proof of Transit Option . . . . . . . . . . . 10 69 3.3. In-band OAM Edge-to-Edge Option . . . . . . . . . . . . . 11 70 4. In-band OAM Data Export . . . . . . . . . . . . . . . . . . . 12 71 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 72 6. Manageability Considerations . . . . . . . . . . . . . . . . 12 73 7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 74 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 75 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 76 9.1. Normative References . . . . . . . . . . . . . . . . . . 13 77 9.2. Informative References . . . . . . . . . . . . . . . . . 13 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 80 1. Introduction 82 This document defines data record types for "in-band" operation, 83 administration, and maintenance (OAM). In-band OAM records OAM 84 information within the packet while the packet traverses a particular 85 network domain. The term "in-band" refers to the fact that the OAM 86 data is added to the data packets rather than is being sent within 87 packets specifically dedicated to OAM. A discussion of the 88 motivation and requirements for in-band OAM can be found in 89 [draft-brockners-inband-oam-requirements]. In-band OAM is to 90 complement "out-of-band" or "active" mechanisms such as ping or 91 traceroute, or more recent active probing mechanisms as described in 92 [I-D.lapukhov-dataplane-probe]. In-band OAM mechanisms can be 93 leveraged where current out-of-band mechanisms do not apply or do not 94 offer the desired results, such as proving that a certain set of 95 traffic takes a pre-defined path, SLA verification for the live data 96 traffic, detailed statistics on traffic distribution paths in 97 networks that distribute traffic across multiple paths, or scenarios 98 where probe traffic is potentially handled differently from regular 99 data traffic by the network devices. 101 This document defines the data types and data formats for in-band OAM 102 data records. The in-band OAM data records can be transported by a 103 variety of transport protocols, including NSH, Segment Routing, 104 VXLAN-GPE, IPv6, IPv4. Encapsulation details for these different 105 transport protocols are outside the scope of this document. 107 2. Conventions 109 Abbreviations used in this document: 111 MTU: Maximum Transmit Unit 113 OAM: Operations, Administration, and Maintenance 115 SR: Segment Routing 117 SID: Segment Identifier 119 NSH: Network Service Header 121 SFC: Service Function Chain 123 TLV: Type-Length-Value 125 VXLAN-GPE: Virtual eXtensible Local Area Network, Generic Protocol 126 Extension 128 3. In-band OAM Data Types and Data Format 130 This section defines in-band OAM data types and data formats of the 131 data records required for in-band OAM. The different uses of in-band 132 OAM require the definition of different types of data. The in-band 133 OAM data format for the data being carried corresponds to the three 134 main categories of in-band OAM data defined in 135 [draft-brockners-inband-oam-requirements], which are edge-to-edge, 136 per node, and for selected nodes only. 138 Transport options for in-band OAM data are found in 139 [draft-brockners-inband-oam-transport]. In-band OAM data is defined 140 as options in Type-Length-Value (TLV) format. The TLV format for 141 each of the three different types of in-band OAM data is defined in 142 this document. 144 In-band OAM is expected to be deployed in a specific domain rather 145 than on the overall Internet. The part of the network which employs 146 in-band OAM is referred to as "in-band OAM-domain". In-band OAM data 147 is added to a packet on entering the in-band OAM-domain and is 148 removed from the packet when exiting the domain. Within the in-band 149 OAM-domain, the in-band OAM data may be updated by network nodes that 150 the packet traverses. The device which adds in-band OAM data to the 151 packet is called the "in-band OAM encapsulating node", whereas the 152 device which removed the in-band OAM data is referred to as the "in- 153 band OAM decapsulating node". Nodes within the domain which are 154 aware of in-band OAM data and read and/or write or process the in- 155 band OAM data are called "in-band OAM transit nodes". Note that not 156 every node in an in-band OAM domain needs to be an in-band OAM 157 transit node. For example, a Segment Routing deployment might 158 require the segment routing path to be verified. In that case, only 159 the SR nodes would also be in-band OAM transit nodes rather than all 160 nodes. 162 3.1. In-band OAM Tracing Option 164 "In-band OAM tracing data" is expected to be collected at every hop 165 that a packet traverses, i.e., in a typical deployment all nodes in 166 an in-band OAM-domain would participate in in-band OAM and thus be 167 in-band OAM transit nodes, in-band OAM encapsulating or in-band OAM 168 decapsulating nodes. The network diameter of the in-band OAM domain 169 is assumed to be known. For in-band OAM tracing, the in-band OAM 170 encapsulating node allocates an array which is to store operational 171 data retrieved from every node while the packet traverses the domain. 172 Every entry is to hold information for a particular in-band OAM 173 transit node that is traversed by a packet. In-band OAM transit 174 nodes update the content of the array. A pointer which is part of 175 the in-band OAM trace data points to the next empty slot in the 176 array, which is where the next in-band OAM transit node fills in its 177 data. The in-band OAM decapsulating node removes the in-band OAM 178 data and process and/or export the metadata. In-band OAM data uses 179 its own name-space for information such as node identifier or 180 interface identifier. This allows for a domain-specific definition 181 and interpretation. For example: In one case an interface-id could 182 point to a physical interface (e.g., to understand which physical 183 interface of an aggregated link is used when receiving or 184 transmitting a packet) whereas in another case it could refer to a 185 logical interface (e.g., in case of tunnels). 187 The following in-band OAM data is defined for in-band OAM tracing: 189 o Identification of the in-band OAM node. An in-band OAM node 190 identifier can match to a device identifier or a particular 191 control point or subsystem within a device. 193 o Identification of the interface that a packet was received on. 195 o Identification of the interface that a packet was sent out on. 197 o Time of day when the packet was processed by the node. Different 198 definitions of processing time are feasible and expected, though 199 it is important that all devices of an in-band OAM domain follow 200 the same definition. 202 o Generic data: Format-free information where syntax and semantic of 203 the information is defined by the operator in a specific 204 deployment. For a specific deployment, all in-band OAM nodes 205 should interpret the generic data the same way. Examples for 206 generic in-band OAM data include geo-location information 207 (location of the node at the time the packet was processed), 208 buffer queue fill level or cache fill level at the time the packet 209 was processed, or even a battery charge level. 211 o A mechanism to detect whether in-band OAM trace data was added at 212 every hop or whether certain hops in the domain weren't in-band 213 OAM transit nodes. 215 The "Node data List" array in the packet is populated iteratively as 216 the packet traverses the network, starting with the last entry of the 217 array, i.e., "Node data List [n]" is the first entry to be populated, 218 "Node data List [n-1]" is the second one, etc. 220 In-band OAM Tracing Option: 222 0 1 2 3 223 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 224 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 225 | Option Type | Opt Data Len | OAM-trace-type| Elements-left | 226 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+ 227 | | | 228 | Node data List [0] | | 229 | | | 230 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ D 231 | | a 232 | Node data List [1] | t 233 | | a 234 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 235 . . . S 236 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ p 237 | | a 238 | Node data List [n-1] | c 239 | | e 240 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 241 | | | 242 | Node data List [n] | | 243 | | | 244 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+ 246 Option Type: 8-bit identifier of the type of option. Option number 247 is defined based on the encapsulation protocol. 249 Opt Data Len: 8-bit unsigned integer. Length of the Option Data 250 field of this option, in octets. 252 OAM-trace-type: 8-bit identifier of a particular trace element 253 variant. 255 The trace type value can be interpreted as a bit field. The 256 following bit fields are defined in this document, with details on 257 each field described in the next section. The order of packing 258 the trace data in each Node-data element follows the bit order for 259 setting each trace data element. Only a valid combination of 260 these fields defined in this document are valid in-band OAM-trace- 261 types. 263 Bit 0 When set indicates presence of node_id in the Node data. 265 Bit 1 When set indicates presence of ingress_if_id in the Node 266 data. 268 Bit 2 When set indicates presence of egress_if_id in the Node 269 data. 271 Bit 3 When set indicates presence of timestamp in the Node 272 data. 274 Bit 4 When set indicates presence of app_data in the Node data. 276 Bit 5-7 Undefined in this document. 278 Section 3.1.1 describes the format of a number of trace types. 279 Specifically, it exemplifies OAM-trace-types 0x00011111, 280 0x00000111, 0x00001001, 0x00010001, and 0x00011001. 282 Elements-left: 8-bit unsigned integer. A pointer that indicates the 283 next data recording point in the data space of the packet in 284 octets. It is the index into the "Node data List" array shown 285 above. 287 Node data List [n]: Variable-length field. The format of which is 288 determined by the OAM Type representing the n-th Node data in the 289 Node data List. The Node data List is encoded starting from the 290 last Node data of the path. The first element of the node data 291 list (Node data List [0]) contains the last node of the path while 292 the last node data of the Node data List (Node data List[n]) 293 contains the first Node data of the path traced. The index 294 contained in "Elements-left" identifies the current active Node 295 data to be populated. 297 3.1.1. In-band OAM Trace Type and Node Data Element 299 An entry in the "Node data List" array can have different formats, 300 following the needs of the a deployment. Some deployments might only 301 be interested in recording the node identifiers, whereas others might 302 be interested in recording node identifier and timestamp. The 303 section defines different formats that an entry in "Node data List" 304 can take. 306 Node data has the following format: 308 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 309 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 310 | Hop_Lim | ..... ~ 313 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 315 0x00011111: In-band OAM-trace-type is 0x00011111 then the format of 316 node data is: 318 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 319 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 320 | Hop_Lim | node_id | 321 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 322 | ingress_if_id | egress_if_id | 323 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 324 | timestamp | 325 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 326 | app_data | 327 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 329 0x00000111: In-band OAM-trace-type is 0x00000111 then the format is: 331 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 332 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 333 | Hop_Lim | node_id | 334 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 335 | ingress_if_id | egress_if_id | 336 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 338 0x00001001: In-band OAM-trace-type is 0x00001001 then the format is: 340 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 341 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 342 | Hop_Lim | node_id | 343 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 344 | timestamp | 345 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 347 0x00010001: In-band OAM-trace-type is 0x00010001 then the format is: 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 | Hop_Lim | node_id | 352 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 353 | app_data | 354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 356 0x00011001: In-band OAM-trace-type is 0x00011001 then the format is: 358 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 359 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 360 | Hop_Lim | node_id | 361 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 362 | timestamp | 363 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 364 | app_data | 365 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 367 Trace data elements in Node data are defined as follows: 369 Hop_Lim: 1 octet Hop limit that is set to the TTL value in the 370 packet at the node that records this data. 372 node_id: Node identifier node_id is a 3 octet field to uniquely 373 identify a node within in-band OAM domain. The procedure to 374 allocate, manage and map the node_ids is beyond the scope of this 375 document. 377 ingress_if_id: 2 octet interface identifier to record the ingress 378 interface the packet was received on. 380 egress_if_id: 2 octet interface identifier to record the egress 381 interface the packet is forwarded out of. 383 timestamp: 4 octet timestamp when packet has been processed by the 384 node. 386 app_data: 4 octet placeholder which can be used by the node to add 387 application specific data. 389 Hop Limit information is used to identify the location of the node in 390 the communication path. 392 3.2. In-band OAM Proof of Transit Option 394 In-band OAM Proof of Transit data is to support the path or service 395 function chain [RFC7665] verification use cases. Proof-of-transit 396 uses methods like nested hashing or nested encryption of the in-band 397 OAM data or mechanisms such as Shamir's Secret Sharing Schema (SSSS). 398 While details on how the in-band OAM data for the proof of transit 399 option is processed at in-band OAM encapsulating, decapsulating and 400 transit nodes are outside the scope of the document, all of these 401 approaches share the need to uniquely identify a packet as well as 402 iteratively operate on a set of information that is handed from node 403 to node. Correspondingly, two pieces of information are added as in- 404 band OAM data to the packet: 406 o Random: Unique identifier for the packet (e.g., 64-bits allow for 407 the unique identification of 2^64 packets). 409 o Cumulative: Information which is handed from node to node and 410 updated by every node according to a verification algorithm. 412 In-band OAM Proof of Transit option: 414 0 1 2 3 415 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 416 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 417 | Option Type | Opt Data Len | POT type = 0 |F| reserved | 418 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+ 419 | Random | | 420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ P 421 | Random(contd) | O 422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ T 423 | Cumulative | | 424 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 425 | Cumulative (contd) | | 426 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+ 428 Option Type: 8-bit identifier of the type of option. 430 Opt Data Len: 8-bit unsigned integer. Length of the Option Data 431 field of this option, in octets. 433 POT Type: 8-bit identifier of a particular POT variant that dictates 434 the POT data that is included. 436 * 16 Octet field as described below 438 Flag (F): 1-bit. Indicates which POT-profile is active. 0 means the 439 even POT-profile is active, 1 means the odd POT-profile is active. 441 Reserved: 7-bit. (Reserved Octet) Reserved octet for future use. 443 Random: 64-bit Per packet Random number. 445 Cumulative: 64-bit Cumulative that is updated at specific nodes by 446 processing per packet Random number field and configured 447 parameters. 449 Note: Larger or smaller sizes of "Random" and "Cumulative" data are 450 feasible and could be required for certain deployments (e.g. in case 451 of space constraints in the transport protocol used). Future 452 versions of this document will address different sizes of data for 453 "proof of transit". 455 3.3. In-band OAM Edge-to-Edge Option 457 The in-band OAM Edge-to-Edge Option is to carry data which is to be 458 interpreted only by the in-band OAM encapsulating and in-band OAM 459 decapsulating node, but not by in-band OAM transit nodes. 461 Currently only sequence numbers use the in-band OAM Edge-to-Edge 462 option. In order to detect packet loss, packet reordering, or packet 463 duplication in an in-band OAM-domain, sequence numbers can be added 464 to packets of a particular tube (see 465 [I-D.hildebrand-spud-prototype]). Each tube leverages a dedicated 466 namespace for its sequence numbers. 468 0 1 2 3 469 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 470 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 471 | Option Type | Opt Data Len | OAM-E2E-Type | reserved | 472 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 473 | E2E Option data format determined by iOAM-E2E-Type | 474 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 476 Option Type: 8-bit identifier of the type of option. 478 Opt Data Len: 8-bit unsigned integer. Length of the Option Data 479 field of this option, in octets. 481 iOAM-E2E-Type: 8-bit identifier of a particular in-band OAM E2E 482 variant. 484 0: E2E option data is a 64-bit sequence number added to a 485 specific tube which is used to identify packet loss and 486 reordering for that tube. 488 Reserved: 8-bit. (Reserved Octet) Reserved octet for future use. 490 4. In-band OAM Data Export 492 In-band OAM nodes collect information for packets traversing a domain 493 that supports in-band OAM. The device at the domain edge (which 494 could also be an end-host) which receives a packet with in-band OAM 495 information chooses how to process the in-band OAM data collected 496 within the packet. This decapsulating node can simply discard the 497 information collected, can process the information further, or export 498 the information using e.g., IPFIX. 500 The discussion of in-band OAM data processing and export is left for 501 a future version of this document. 503 5. IANA Considerations 505 IANA considerations will be added in a future version of this 506 document. 508 6. Manageability Considerations 510 Manageability considerations will be addressed in a later version of 511 this document.. 513 7. Security Considerations 515 Security considerations will be addressed in a later version of this 516 document. For a discussion of security requirements of in-band OAM, 517 please refer to [draft-brockners-inband-oam-requirements]. 519 8. Acknowledgements 521 The authors would like to thank Eric Vyncke, Nalini Elkins, Srihari 522 Raghavan, Ranganathan T S, Karthik Babu Harichandra Babu, Akshaya 523 Nadahalli, and Andrew Yourtchenko for the comments and advice. This 524 document leverages and builds on top of several concepts described in 525 [draft-kitamura-ipv6-record-route]. The authors would like to 526 acknowledge the work done by the author Hiroshi Kitamura and people 527 involved in writing it. 529 9. References 531 9.1. Normative References 533 [draft-brockners-inband-oam-requirements] 534 Brockners, F., Bhandari, S., and S. Dara, "Requirements 535 for in-band OAM", July 2016. 537 9.2. Informative References 539 [draft-brockners-inband-oam-transport] 540 Brockners, F., Bhandari, S., Pignataro, C., and H. 541 Gredler, "Encapsulations for in-band OAM", July 2016. 543 [draft-brockners-proof-of-transit] 544 Brockners, F., Bhandari, S., and S. Dara, "Proof of 545 transit", July 2016. 547 [draft-kitamura-ipv6-record-route] 548 Kitamura, H., "Record Route for IPv6 (PR6),Hop-by-Hop 549 Option Extension", November 2000. 551 [FD.io] "Fast Data Project: FD.io", . 553 [I-D.hildebrand-spud-prototype] 554 Hildebrand, J. and B. Trammell, "Substrate Protocol for 555 User Datagrams (SPUD) Prototype", draft-hildebrand-spud- 556 prototype-03 (work in progress), March 2015. 558 [I-D.lapukhov-dataplane-probe] 559 Lapukhov, P. and r. remy@barefootnetworks.com, "Data-plane 560 probe for in-band telemetry collection", draft-lapukhov- 561 dataplane-probe-01 (work in progress), June 2016. 563 [P4] Kim, , "P4: In-band Network Telemetry (INT)", September 564 2015. 566 [RFC7665] Halpern, J., Ed. and C. Pignataro, Ed., "Service Function 567 Chaining (SFC) Architecture", RFC 7665, 568 DOI 10.17487/RFC7665, October 2015, 569 . 571 Authors' Addresses 572 Frank Brockners 573 Cisco Systems, Inc. 574 Hansaallee 249, 3rd Floor 575 DUESSELDORF, NORDRHEIN-WESTFALEN 40549 576 Germany 578 Email: fbrockne@cisco.com 580 Shwetha Bhandari 581 Cisco Systems, Inc. 582 Cessna Business Park, Sarjapura Marathalli Outer Ring Road 583 Bangalore, KARNATAKA 560 087 584 India 586 Email: shwethab@cisco.com 588 Carlos Pignataro 589 Cisco Systems, Inc. 590 7200-11 Kit Creek Road 591 Research Triangle Park, NC 27709 592 United States 594 Email: cpignata@cisco.com 596 Hannes Gredler 597 RtBrick Inc. 599 Email: hannes@rtbrick.com 601 John Leddy 602 Comcast 604 Email: John_Leddy@cable.comcast.com 606 Stephen Youell 607 JP Morgan Chase 608 25 Bank Street 609 London E14 5JP 610 United Kingdom 612 Email: stephen.youell@jpmorgan.com