idnits 2.17.1 draft-gandhi-spring-ioam-sr-mpls-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 (October 23, 2018) is 1984 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 SPRING Working Group R. Gandhi, Ed. 3 Internet-Draft Z. Ali 4 Intended status: Standards Track C. Filsfils 5 Expires: April 26, 2019 F. Brockners 6 Cisco Systems, Inc. 7 B. Wen 8 V. Kozak 9 Comcast 10 October 23, 2018 12 Segment Routing with MPLS Data Plane encapsulation 13 for In-situ OAM Data 14 draft-gandhi-spring-ioam-sr-mpls-00 16 Abstract 18 In-situ Operations, Administration, and Maintenance (IOAM) records 19 operational and telemetry information in the data packet while the 20 packet traverses a path between two points in the network. This 21 document defines how IOAM data fields are transported with the 22 Segment Routing with MPLS data plane (SR-MPLS) encapsulation. 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 Copyright Notice 41 Copyright (c) 2018 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 2 58 2.1. Requirement Language . . . . . . . . . . . . . . . . . . . 2 59 2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3 60 3. IOAM Data Field Encapsulation in SR-MPLS Header . . . . . . . 3 61 4. Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 63 6. Security Considerations . . . . . . . . . . . . . . . . . . . 5 64 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 65 8. Normative References . . . . . . . . . . . . . . . . . . . . . 6 66 Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 69 1. Introduction 71 In-situ Operations, Administration, and Maintenance (IOAM) records 72 OAM information within the packet while the packet traverses a 73 particular network domain. The term "in-situ" refers to the fact 74 that the IOAM data fields are added to the data packets rather than 75 being sent within probe packets specifically dedicated to OAM. 77 This document defines how IOAM data fields are transported with the 78 Segment Routing with MPLS data plane 79 [I-D.ietf-spring-segment-routing-mpls] encapsulation. 81 The IOAM data fields carried are defined in 82 [I-D.ietf-ippm-ioam-data], and can be used for various use-cases 83 including Performance Measurement (PM). 85 2. Conventions 87 2.1. Requirement Language 89 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 90 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 91 document are to be interpreted as described in [RFC2119] [RFC8174] 92 when, and only when, they appear in all capitals, as shown here. 94 2.2. Abbreviations 96 Abbreviations used in this document: 98 IOAM In-situ Operations, Administration, and Maintenance 100 OAM Operations, Administration, and Maintenance 102 PM Performance Measurement 104 PoT Proof-of-Transit 106 SR Segment Routing 108 SR-MPLS Segment Routing with MPLS Data plane 110 3. IOAM Data Field Encapsulation in SR-MPLS Header 112 SR-MPLS encapsulation is defined in 113 [I-D.ietf-spring-segment-routing-mpls]. IOAM data fields are carried 114 in the SR-MPLS header, as an IOAM data fields. The different IOAM 115 data fields defined in [I-D.ietf-ippm-ioam-data] are added as TLVs. 116 More than one TLV can be present in the IOAM data fields. The IOAM 117 Indicator Label (value TBA1) is added at the bottom of the MPLS label 118 stack to indicate the presence of the IOAM data fields in the header. 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 | IOAM Indicator Label (TBA1) | TC |S| TTL | 124 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+ 125 | IOAM-Type | IOAM HDR LEN | RESERVED | | 126 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ I 127 ! | O 128 ! | A 129 ~ IOAM Option and Data Space ~ M 130 | | | 131 | | | 132 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+ 133 | | 134 | | 135 | Payload + Padding (L2/L3/ESP/...) | 136 | | 137 | | 138 | | 139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 141 Figure 1: IOAM data encapsulation in SR-MPLS Header 143 IOAM Indicator Label is defined in this document as value TBA1. 145 The fields related to the encapsulation of IOAM data fields in the 146 SR-MPLS header are defined as follows: 148 IOAM-Type: 8-bit field defining the IOAM Option type, as defined in 149 Section 7.2 of [I-D.ietf-ippm-ioam-data]. 151 IOAM HDR LEN: 8-bit unsigned integer. Length of the IOAM HDR in 152 4-octet units. 154 RESERVED: 8-bit reserved field MUST be set to zero upon 155 transmission and ignored upon receipt. 157 IOAM Option and Data Space: IOAM option header and data is present 158 as defined by the IOAM-Type field, and is defined in Section 4 of 159 [I-D.ietf-ippm-ioam-data]. 161 4. Procedure 163 This section summarizes the procedure for IOAM data encapsulation in 164 SR-MPLS. 166 o The ingress node inserts the IOAM Indicator Label and IOAM TLV in 167 the MPLS header. 169 o On the ultimate node where the last MPLS label is popped from the 170 header, the node "forwards and punts the timestamped copy" of the 171 data packet with IOAM TLV when the node recognizes the IOAM 172 Indicator Label. 174 o The ultimate node also pops the IOAM Indicator Label and the IOAM 175 data fields from the MPLS header. 177 5. IANA Considerations 179 IANA maintains the "Special-Purpose Multiprotocol Label Switching 180 (MPLS) Label Values" registry (see 181 ). IANA is requested to allocate IOAM Indicator Label 183 value from the "Special-Purpose MPLS Label Values" registry: 185 +---------------+-------------------------+---------------+ 186 | Value | Description | Reference | 187 +---------------+-------------------------+---------------+ 188 | TBA1 | IOAM Indicator Label | This document | 189 +---------------+-------------------------+---------------+ 191 6. Security Considerations 193 The security considerations of SR-MPLS are discussed in 194 [I-D.ietf-spring-segment-routing-mpls], and the security 195 considerations of IOAM in general are discussed in 196 [I-D.ietf-ippm-ioam-data]. 198 IOAM is considered a "per domain" feature, where one or several 199 operators decide on leveraging and configuring IOAM according to 200 their needs. Still, operators need to properly secure the IOAM 201 domain to avoid malicious configuration and use, which could include 202 injecting malicious IOAM packets into a domain. 204 7. Acknowledgements 206 The authors would like to thank Shwetha Bhandari and Vengada Prasad 207 Govindan for the discussions on IOAM. 209 8. Normative References 211 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 212 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 213 RFC2119, March 1997. 215 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 216 2119 Key Words", RFC 8174, May 2017. 218 [I-D.ietf-spring-segment-routing-mpls] Bashandy, A., Filsfils, C., 219 Previdi, S., Decraene, B., Litkowski, S., and R. Shakir, 220 "Segment Routing with MPLS data plane", 221 draft-ietf-spring-segment-routing-mpls, work in progress. 223 [I-D.ietf-ippm-ioam-data] Brockners, F., Bhandari, S., Pignataro, 224 C., Gredler, H., Leddy, J., Youell, S., Mizrahi, T., 225 Mozes, D., Lapukhov, P., Chang, R., and Bernier, D., "Data 226 Fields for In-situ OAM", draft-ietf-ippm-ioam-data, work 227 in progress. 229 Contributors 231 Sagar Soni 232 Cisco Systems, Inc. 233 Email: sagsoni@cisco.com 235 Patrick Khordoc 236 Cisco Systems, Inc. 237 Email: pkhordoc@cisco.com 239 Authors' Addresses 241 Rakesh Gandhi (editor) 242 Cisco Systems, Inc. 243 Canada 245 Email: rgandhi@cisco.com 247 Zafar Ali 248 Cisco Systems, Inc. 250 Email: zali@cisco.com 251 Clarence Filsfils 252 Cisco Systems, Inc. 253 Belgium 255 Email: cf@cisco.com 257 Frank Brockners 258 Cisco Systems, Inc. 259 Hansaallee 249, 3rd Floor 260 DUESSELDORF, NORDRHEIN-WESTFALEN 40549 261 Germany 263 Email: fbrockne@cisco.com 265 Bin Wen 266 Comcast 268 Email: Bin_Wen@cable.comcast.com 270 Voitek Kozak 271 Comcast 273 Email: Voitek_Kozak@comcast.com