idnits 2.17.1 draft-ioametal-ippm-6man-ioam-ipv6-options-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 (October 20, 2018) is 2014 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: April 23, 2019 Cisco 6 H. Gredler 7 RtBrick Inc. 8 J. Leddy 9 Comcast 10 S. Youell 11 JMPC 12 T. Mizrahi 13 Huawei Network.IO Innovation Lab 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 October 20, 2018 25 In-situ OAM IPv6 Options 26 draft-ioametal-ippm-6man-ioam-ipv6-options-01 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 https://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 April 23, 2019. 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 (https://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 . . . . . . . . . . . . . . . . . . . . . . 5 76 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 77 7.1. Normative References . . . . . . . . . . . . . . . . . . 6 78 7.2. Informative References . . . . . . . . . . . . . . . . . 6 79 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 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 IOAM data is carried in IPv6 packets as Hop-by-Hop or Destination 113 options. One IPv6 Destination Options and Hop-by-Hop Options Type 114 codepoint is assigned for IOAM. Multiple options with the same 115 Option Type MAY appear in the same Hop-by-Hop Options or Destination 116 Options header, with varying content. This mechanism of in-situ OAM 117 in IPv6 is used to enhance diagnostics of IPv6 networks. It 118 complements other mechanisms proposed to enhance diagnostics of IPv6 119 networks, such as the IPv6 Performance and Diagnostic Metrics 120 Destination Option described in [RFC8250]. 122 IPv6 Hop-by-Hop and Destination Option format for carrying in-situ 123 OAM data fields: 125 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 126 | Option Type | Opt Data Len | Reserved | IOAM Type | 127 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+ 128 | | | 129 . . I 130 . Option Data . O 131 . . A 132 . . M 133 . . . 134 . . O 135 . . P 136 . . T 137 . . I 138 . . O 139 . . N 140 . . | 141 | | | 142 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+ 143 Option Type: 8-bit identifier of the type of option. 145 Opt Data Len: 8-bit unsigned integer. Length of the Reserved and 146 Option Data field of this option, in octets. 148 Reserved: 8-bit field MUST be set to zero upon transmission and 149 ignored upon reception. 151 IOAM Type: 8-bit field as defined in section 7.2 in 152 [I-D.ietf-ippm-ioam-data]. 154 Option Data: Variable-length field. Option-Type-specific data. 156 In-situ OAM Options are inserted as Option data as follows: 158 1. Pre-allocated Tracing Option: The in-situ OAM Preallocated 159 Tracing option defined in [I-D.ietf-ippm-ioam-data] is 160 represented as a IPv6 option in hop by hop extension header: 162 Option Type: 001xxxxx 8-bit identifier of the IOAM type of 163 option. xxxxx=TBD. 165 IOAM Type: IOAM Pre-allocated Trace Option Type. 167 2. Incremental Tracing Option: The in-situ OAM Incremental Tracing 168 option defined in [I-D.ietf-ippm-ioam-data] is represented as a 169 IPv6 option in hop by hop extension header: 171 Option Type: 001xxxxx 8-bit identifier of the IOAM type of 172 option. xxxxx=TBD. 174 IOAM Type: IOAM Incremental Trace Option Type. 176 3. Proof of Transit Option: The in-situ OAM POT option defined in 177 [I-D.ietf-ippm-ioam-data] is represented as a IPv6 option in hop 178 by hop extension header: 180 Option Type: 001xxxxx 8-bit identifier of the IOAM type of 181 option. xxxxx=TBD. 183 IOAM Type: IOAM POT Option Type. 185 4. Edge to Edge Option: The in-situ OAM E2E option defined in 186 [I-D.ietf-ippm-ioam-data] is represented as a IPv6 option in IPv6 187 option in destination options extension header: 189 Option Type: 000xxxxx 8-bit identifier of the IOAM type of 190 option. xxxxx=TBD. 192 IOAM Type: IOAM E2E Option Type. 194 All the in-situ OAM IPv6 options defined here have alignment 195 requirements. Specifically, they all require 4n alignment. This 196 ensures that 4 octet fields specified in [I-D.ietf-ippm-ioam-data] 197 such as transit delay are aligned at a multiple-of-4 offset from the 198 start of the Hop-by-Hop Options header. In addition, to maintain 199 IPv6 extension header 8-octet alignment and avoid the need to add or 200 remove padding at every hop, the Trace-Type for Incremental Tracing 201 Option in IPv6 MUST be selected such that the IOAM node data length 202 is a multiple of 8-octets. 204 4. Security Considerations 206 This document describes the encapsulation of IOAM data fields in 207 IPv6. Security considerations of the specific IOAM data fields for 208 each case (i.e., Trace, Proof of Transit, and E2E) are described in 209 defined in [I-D.ietf-ippm-ioam-data]. 211 As this document describes new options for IPv6 , these are similar 212 to the security considerations of [RFC8200] and the new weakness 213 documented in [RFC8250]. 215 5. IANA Considerations 217 This draft requests the following IPv6 Option Type assignments from 218 the Destination Options and Hop-by-Hop Options sub-registry of 219 Internet Protocol Version 6 (IPv6) Parameters. 221 http://www.iana.org/assignments/ipv6-parameters/ipv6- 222 parameters.xhtml#ipv6-parameters-2 224 Hex Value Binary Value Description Reference 225 act chg rest 226 ---------------------------------------------------------------- 227 TBD_1_0 00 0 TBD_1 IOAM [This draft] 228 TBD_1_1 00 1 TBD_1 IOAM [This draft] 230 6. Acknowledgements 232 The authors would like to thank Tom Herbert, Eric Vyncke, Nalini 233 Elkins, Srihari Raghavan, Ranganathan T S, Karthik Babu Harichandra 234 Babu, Akshaya Nadahalli, Stefano Previdi, Hemant Singh, Erik 235 Nordmark, LJ Wobker, and Andrew Yourtchenko for the comments and 236 advice. For the IPv6 encapsulation, this document leverages concepts 237 described in [I-D.kitamura-ipv6-record-route]. The authors would 238 like to acknowledge the work done by the author Hiroshi Kitamura and 239 people involved in writing it. 241 7. References 243 7.1. Normative References 245 [I-D.ietf-ippm-ioam-data] 246 Brockners, F., Bhandari, S., Pignataro, C., Gredler, H., 247 Leddy, J., Youell, S., Mizrahi, T., Mozes, D., Lapukhov, 248 P., Chang, R., and d. daniel.bernier@bell.ca, "Data Fields 249 for In-situ OAM", draft-ietf-ippm-ioam-data-01 (work in 250 progress), October 2017. 252 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 253 Requirement Levels", BCP 14, RFC 2119, 254 DOI 10.17487/RFC2119, March 1997, 255 . 257 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 258 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 259 May 2017, . 261 7.2. Informative References 263 [I-D.kitamura-ipv6-record-route] 264 Kitamura, H., "Record Route for IPv6 (PR6) Hop-by-Hop 265 Option Extension", draft-kitamura-ipv6-record-route-00 266 (work in progress), November 2000. 268 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 269 (IPv6) Specification", STD 86, RFC 8200, 270 DOI 10.17487/RFC8200, July 2017, 271 . 273 [RFC8250] Elkins, N., Hamilton, R., and M. Ackermann, "IPv6 274 Performance and Diagnostic Metrics (PDM) Destination 275 Option", RFC 8250, DOI 10.17487/RFC8250, September 2017, 276 . 278 Authors' Addresses 280 Shwetha Bhandari 281 Cisco Systems, Inc. 282 Cessna Business Park, Sarjapura Marathalli Outer Ring Road 283 Bangalore, KARNATAKA 560 087 284 India 286 Email: shwethab@cisco.com 287 Frank Brockners 288 Cisco Systems, Inc. 289 Hansaallee 249, 3rd Floor 290 DUESSELDORF, NORDRHEIN-WESTFALEN 40549 291 Germany 293 Email: fbrockne@cisco.com 295 Carlos Pignataro 296 Cisco Systems, Inc. 297 7200-11 Kit Creek Road 298 Research Triangle Park, NC 27709 299 United States 301 Email: cpignata@cisco.com 303 Hannes Gredler 304 RtBrick Inc. 306 Email: hannes@rtbrick.com 308 John Leddy 309 Comcast 311 Email: John_Leddy@cable.comcast.com 313 Stephen Youell 314 JP Morgan Chase 315 25 Bank Street 316 London E14 5JP 317 United Kingdom 319 Email: stephen.youell@jpmorgan.com 321 Tal Mizrahi 322 Huawei Network.IO Innovation Lab 323 Israel 325 Email: tal.mizrahi.phd@gmail.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 342 Petr Lapukhov 343 Facebook 344 1 Hacker Way 345 Menlo Park, CA 94025 346 US 348 Email: petr@fb.com 350 Mickey Spiegel 351 Barefoot Networks 352 4750 Patrick Henry Drive 353 Santa Clara, CA 95054 354 US 356 Email: mspiegel@barefootnetworks.com 358 Suresh Krishnan 359 Kaloom 361 Email: suresh@kaloom.com