idnits 2.17.1 draft-ioametal-ippm-6man-ioam-ipv6-options-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 (June 29, 2018) is 2129 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) == Outdated reference: A later version (-17) exists of draft-ietf-ippm-ioam-data-01 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ippm,6man S. Bhandari 3 Internet-Draft F. Brockners 4 Intended status: Standards Track C. Pignataro 5 Expires: December 31, 2018 Cisco 6 H. Gredler 7 RtBrick Inc. 8 J. Leddy 9 Comcast 10 S. Youell 11 JMPC 12 T. Mizrahi 13 Marvell 14 A. Kfir 15 B. Gafni 16 Mellanox Technologies, Inc. 17 P. Lapukhov 18 Facebook 19 M. Spiegel 20 Barefoot Networks 21 S. Krishnan 22 Kaloom 23 June 29, 2018 25 In-situ OAM IPv6 Options 26 draft-ioametal-ippm-6man-ioam-ipv6-options-00 28 Abstract 30 In-situ Operations, Administration, and Maintenance (IOAM) records 31 operational and telemetry information in the packet while the packet 32 traverses a path between two points in the network. This document 33 outlines how IOAM data fields are encapsulated in IPv6. 35 Status of This Memo 37 This Internet-Draft is submitted in full conformance with the 38 provisions of BCP 78 and BCP 79. 40 Internet-Drafts are working documents of the Internet Engineering 41 Task Force (IETF). Note that other groups may also distribute 42 working documents as Internet-Drafts. The list of current Internet- 43 Drafts is at http://datatracker.ietf.org/drafts/current/. 45 Internet-Drafts are draft documents valid for a maximum of six months 46 and may be updated, replaced, or obsoleted by other documents at any 47 time. It is inappropriate to use Internet-Drafts as reference 48 material or to cite them other than as "work in progress." 49 This Internet-Draft will expire on December 31, 2018. 51 Copyright Notice 53 Copyright (c) 2018 IETF Trust and the persons identified as the 54 document authors. All rights reserved. 56 This document is subject to BCP 78 and the IETF Trust's Legal 57 Provisions Relating to IETF Documents 58 (http://trustee.ietf.org/license-info) in effect on the date of 59 publication of this document. Please review these documents 60 carefully, as they describe your rights and restrictions with respect 61 to this document. Code Components extracted from this document must 62 include Simplified BSD License text as described in Section 4.e of 63 the Trust Legal Provisions and are provided without warranty as 64 described in the Simplified BSD License. 66 Table of Contents 68 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 69 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 2 70 2.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 71 2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3 72 3. In-situ OAM Metadata Transport in IPv6 . . . . . . . . . . . 3 73 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 74 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 75 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 76 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 77 7.1. Normative References . . . . . . . . . . . . . . . . . . 6 78 7.2. Informative References . . . . . . . . . . . . . . . . . 6 79 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 81 1. Introduction 83 In-situ Operations, Administration, and Maintenance (IOAM) records 84 operational and telemetry information in the packet while the packet 85 traverses a path between two points in the network. This document 86 outlines how IOAM data fields are encapsulated in the IPv6 [RFC8200]. 88 2. Conventions 90 2.1. Requirements Language 92 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 93 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 94 "OPTIONAL" in this document are to be interpreted as described in BCP 95 14 [RFC2119] [RFC8174] when, and only when, they appear in all 96 capitals, as shown here. 98 2.2. Abbreviations 100 Abbreviations used in this document: 102 E2E: Edge-to-Edge 104 IOAM: In-situ Operations, Administration, and Maintenance 106 OAM: Operations, Administration, and Maintenance 108 POT: Proof of Transit 110 3. In-situ OAM Metadata Transport in IPv6 112 An IPv6 option is defined corresponding to each of the IOAM data 113 fields defined in [I-D.ietf-ippm-ioam-data]. This mechanisms of in- 114 situ OAM in IPv6 is used to enhance diagnostics of IPv6 networks. It 115 complements other mechanisms proposed to enhance diagnostics of IPv6 116 networks, such as the IPv6 Performance and Diagnostic Metrics 117 Destination Option described in [RFC8250]. IOAM data is carried in 118 IPv6 packets as Hop-by-Hop or Destination options as specified in the 119 individual option definition below. 121 IPv6 hop-by-hop and destination option format for carrying in-situ 122 OAM data fields: 124 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 125 | Option Type | Opt Data Len | Reserved (MBZ) | 126 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+ 127 | | | 128 . . I 129 . Option Data . O 130 . . A 131 . . M 132 . . . 133 . . O 134 . . P 135 . . T 136 . . I 137 . . O 138 . . N 139 . . | 140 | | | 141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+ 143 Option Type 8-bit identifier of the type of option. 145 Opt Data Len 8-bit unsigned integer. Length of the 146 Reserved and Option Data field of this option, 147 in octets. 149 Reserved (MBZ) 16-bit field MUST be filled with zeroes. 151 Option Data Variable-length field. Option-Type-specific 152 data. 154 In-situ OAM Options are inserted as Option data as follows: 156 1. Pre-allocated Tracing Option: The in-situ OAM Preallocated 157 Tracing option defined in [I-D.ietf-ippm-ioam-data] is 158 represented as a IPv6 option in hop by hop extension header by 159 allocating following type: 161 Option Type: 001xxxxxx 8-bit identifier of the type of option. 162 xxxxxx=TBD1. 164 2. Incremental Tracing Option: The in-situ OAM Incremental Tracing 165 option defined in [I-D.ietf-ippm-ioam-data] is represented as a 166 IPv6 option in hop by hop extension header by allocating 167 following type: 169 Option Type: 001xxxxxx 8-bit identifier of the type of option. 170 xxxxxx=TBD2. 172 3. Proof of Transit Option: The in-situ OAM POT option defined in 173 [I-D.ietf-ippm-ioam-data] is represented as a IPv6 option in hop 174 by hop extension header by allocating following type: 176 Option Type: 001xxxxxx 8-bit identifier of the type of option. 177 xxxxxx=TBD3. 179 4. Edge to Edge Option: The in-situ OAM E2E option defined in 180 [I-D.ietf-ippm-ioam-data] is represented as a IPv6 option in IPv6 181 option in destination options extension header by allocating 182 following type: 184 Option Type: 000xxxxxx 8-bit identifier of the type of option. 185 xxxxxx=TBD4. 187 All the in-situ OAM IPv6 options defined here have alignment 188 requirement. Following the convention in IPv6, these options are 189 aligned in a packet so that multi-octet values within the Option Data 190 field of each option are 4-octet aligned as specified in 191 [I-D.ietf-ippm-ioam-data]. In addition, to maintain IPv6 extenstion 192 header 8-octet alignment requirement, Trace-Type for Incremental 193 Tracing Option in IPv6 MUST be selected such that the IOAM node data 194 length is a multiple of 8-octets. 196 4. Security Considerations 198 This document describes the encapsulation of IOAM data fields in 199 IPv6. Security considerations of the specific IOAM data fields for 200 each case (i.e., Trace, Proof of Transit, and E2E) are described in 201 defined in [I-D.ietf-ippm-ioam-data]. 203 As this document describes new options for IPv6 , these are similar 204 to the security considerations of [RFC8200] and the new weakness 205 documented in [RFC8250]. 207 5. IANA Considerations 209 This draft requests the following IPv6 Option Type assignments from 210 the Destination Options and Hop-by-Hop Options sub-registry of 211 Internet Protocol Version 6 (IPv6) Parameters. 213 http://www.iana.org/assignments/ipv6-parameters/ipv6- 214 parameters.xhtml#ipv6-parameters-2 215 Hex Value Binary Value Description Reference 216 act chg rest 217 ---------------------------------------------------------------- 218 TBD_1 00 1 TBD1 IOAM Pre-allocated [This draft] 219 Tracing Option 220 TBD_2 00 1 TBD2 IOAM Incremental [This draft] 221 Tracing Option 222 TBD_3 00 1 TBD3 IOAM Proof of Transit [This draft] 223 Option 224 TBD_4 00 0 TBD4 IOAM Edge to Edge [This draft] 225 Option 227 6. Acknowledgements 229 The authors would like to thank Tom Herbert, Eric Vyncke, Nalini 230 Elkins, Srihari Raghavan, Ranganathan T S, Karthik Babu Harichandra 231 Babu, Akshaya Nadahalli, Stefano Previdi, Hemant Singh, Erik 232 Nordmark, LJ Wobker, and Andrew Yourtchenko for the comments and 233 advice. For the IPv6 encapsulation, this document leverages concepts 234 described in [I-D.kitamura-ipv6-record-route]. The authors would 235 like to acknowledge the work done by the author Hiroshi Kitamura and 236 people involved in writing it. 238 7. References 240 7.1. Normative References 242 [I-D.ietf-ippm-ioam-data] 243 Brockners, F., Bhandari, S., Pignataro, C., Gredler, H., 244 Leddy, J., Youell, S., Mizrahi, T., Mozes, D., Lapukhov, 245 P., Chang, R., and d. daniel.bernier@bell.ca, "Data Fields 246 for In-situ OAM", draft-ietf-ippm-ioam-data-01 (work in 247 progress), October 2017. 249 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 250 Requirement Levels", BCP 14, RFC 2119, 251 DOI 10.17487/RFC2119, March 1997, . 254 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 255 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 256 May 2017, . 258 7.2. Informative References 260 [I-D.kitamura-ipv6-record-route] 261 Kitamura, H., "Record Route for IPv6 (PR6) Hop-by-Hop 262 Option Extension", draft-kitamura-ipv6-record-route-00 263 (work in progress), November 2000. 265 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 266 (IPv6) Specification", STD 86, RFC 8200, 267 DOI 10.17487/RFC8200, July 2017, . 270 [RFC8250] Elkins, N., Hamilton, R., and M. Ackermann, "IPv6 271 Performance and Diagnostic Metrics (PDM) Destination 272 Option", RFC 8250, DOI 10.17487/RFC8250, September 2017, 273 . 275 Authors' Addresses 277 Shwetha Bhandari 278 Cisco Systems, Inc. 279 Cessna Business Park, Sarjapura Marathalli Outer Ring Road 280 Bangalore, KARNATAKA 560 087 281 India 283 Email: shwethab@cisco.com 285 Frank Brockners 286 Cisco Systems, Inc. 287 Hansaallee 249, 3rd Floor 288 DUESSELDORF, NORDRHEIN-WESTFALEN 40549 289 Germany 291 Email: fbrockne@cisco.com 293 Carlos Pignataro 294 Cisco Systems, Inc. 295 7200-11 Kit Creek Road 296 Research Triangle Park, NC 27709 297 United States 299 Email: cpignata@cisco.com 301 Hannes Gredler 302 RtBrick Inc. 304 Email: hannes@rtbrick.com 305 John Leddy 306 Comcast 308 Email: John_Leddy@cable.comcast.com 310 Stephen Youell 311 JP Morgan Chase 312 25 Bank Street 313 London E14 5JP 314 United Kingdom 316 Email: stephen.youell@jpmorgan.com 318 Tal Mizrahi 319 Marvell 320 6 Hamada St. 321 Yokneam 20692 322 Israel 324 Email: talmi@marvell.com 326 Aviv Kfir 327 Mellanox Technologies, Inc. 328 350 Oakmead Parkway, Suite 100 329 Sunnyvale, CA 94085 330 U.S.A. 332 Email: avivk@mellanox.com 334 Barak Gafni 335 Mellanox Technologies, Inc. 336 350 Oakmead Parkway, Suite 100 337 Sunnyvale, CA 94085 338 U.S.A. 340 Email: gbarak@mellanox.com 341 Petr Lapukhov 342 Facebook 343 1 Hacker Way 344 Menlo Park, CA 94025 345 US 347 Email: petr@fb.com 349 Mickey Spiegel 350 Barefoot Networks 351 2185 Park Boulevard 352 Palo Alto, CA 94306 353 US 355 Email: mspiegel@barefootnetworks.com 357 Suresh Krishnan 358 Kaloom 360 Email: suresh@kaloom.com