idnits 2.17.1 draft-ietf-detnet-ip-oam-04.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 (7 February 2022) is 803 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-15) exists of draft-ietf-detnet-mpls-oam-06 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DetNet Working Group G. Mirsky 3 Internet-Draft Ericsson 4 Intended status: Informational M. Chen 5 Expires: 11 August 2022 Huawei 6 D. Black 7 Dell EMC 8 7 February 2022 10 Operations, Administration and Maintenance (OAM) for Deterministic 11 Networks (DetNet) with IP Data Plane 12 draft-ietf-detnet-ip-oam-04 14 Abstract 16 This document defines the principles for using Operations, 17 Administration, and Maintenance protocols and mechanisms in the 18 Deterministic Networking networks with the IP data plane. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at https://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on 11 August 2022. 37 Copyright Notice 39 Copyright (c) 2022 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 44 license-info) in effect on the date of publication of this document. 45 Please review these documents carefully, as they describe your rights 46 and restrictions with respect to this document. Code Components 47 extracted from this document must include Revised BSD License text as 48 described in Section 4.e of the Trust Legal Provisions and are 49 provided without warranty as described in the Revised BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. Conventions used in this document . . . . . . . . . . . . . . 3 55 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 56 2.2. Keywords . . . . . . . . . . . . . . . . . . . . . . . . 3 57 3. Active OAM for DetNet Networks with the IP Data Plane . . . . 4 58 3.1. Active OAM Using DetNet-in-UDP Encapsulation . . . . . . 4 59 3.2. Mapping Active OAM and IP DetNet flows . . . . . . . . . 5 60 3.3. Active OAM Using GRE-in-UDP Encapsulation . . . . . . . . 6 61 4. OAM of DetNet IP Interworking with OAM of non-IP DetNet 62 domains . . . . . . . . . . . . . . . . . . . . . . . . . 6 63 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 64 6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 65 7. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 6 66 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 67 8.1. Normative References . . . . . . . . . . . . . . . . . . 6 68 8.2. Informational References . . . . . . . . . . . . . . . . 7 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 71 1. Introduction 73 [RFC8655] introduces and explains Deterministic Networks (DetNet) 74 architecture. 76 Operations, Administration and Maintenance (OAM) protocols are used 77 to detect, localize defects in the network, and monitor network 78 performance. Some OAM functions, e.g., failure detection, work in 79 the network proactively, while others, e.g., defect localization, 80 usually performed on-demand. These tasks achieved by a combination 81 of active and hybrid, as defined in [RFC7799], OAM methods. 83 [I-D.tpmb-detnet-oam-framework] lists the functional requirements 84 toward OAM for DetNet domain. The list can further be used for gap 85 analysis of available OAM tools to identify possible enhancements of 86 existing or whether new OAM tools are required to support proactive 87 and on-demand path monitoring and service validation. Also, the 88 document defines the OAM use principals for the DetNet networks with 89 the IP data plane. 91 2. Conventions used in this document 93 2.1. Terminology 95 The term "DetNet OAM" used in this document interchangeably with 96 longer version "set of OAM protocols, methods and tools for 97 Deterministic Networks". 99 DetNet Deterministic Networks 101 DiffServ Differentiated Services 103 OAM: Operations, Administration and Maintenance 105 PREF Packet Replication and Elimination Function 107 POF Packet Ordering Function 109 RDI Remote Defect Indication 111 ICMP Internet Control Message Protocol 113 ACH Associated Channel Header 115 Underlay Network or Underlay Layer: The network that provides 116 connectivity between the DetNet nodes. MPLS network providing LSP 117 connectivity between DetNet nodes is an example of the underlay 118 layer. 120 DetNet Node - a node that is an actor in the DetNet domain. DetNet 121 domain edge node and node that performs PREF within the domain are 122 examples of DetNet node. 124 2.2. Keywords 126 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 127 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 128 "OPTIONAL" in this document are to be interpreted as described in BCP 129 14 [RFC2119] [RFC8174] when, and only when, they appear in all 130 capitals, as shown here. 132 3. Active OAM for DetNet Networks with the IP Data Plane 134 OAM protocols and mechanisms act within the data plane of the 135 particular networking layer. And thus it is critical that the data 136 plane encapsulation supports OAM mechanisms in such a way that DetNet 137 OAM packets are in-band with a DetNet flow being monitored, i.e., 138 DetNet OAM test packets follow precisely the same path as DetNet data 139 plane traffic both for unidirectional and bi-directional DetNet 140 paths. 142 The DetNet data plane encapsulation in a transport network with IP 143 encapsulations specified in Section 6 of [RFC8939]. For the IP 144 underlay network, DetNet flows are identified by the ordered match to 145 the provisioned information set that, among other elements, includes 146 the IP protocol, source port number, destination port number. Active 147 IP OAM protocols like Bidirectional Forwarding Detection (BFD) 148 [RFC5880] or STAMP [RFC8762], use UDP transport and the well-known 149 UDP port numbers as the destination port. Thus a DetNet node MUST be 150 able to associate an IP DetNet flow with the particular test session 151 to ensure that test packets experience the same treatment as the 152 DetNet flow packets. 154 Most of on-demand failure detection and localization in IP networks 155 is being done by using the Internet Control Message Protocol (ICMP) 156 Echo Request, Echo Reply and the set of defined error messages, e.g., 157 Destination Unreachable, with the more detailed information provided 158 through code points. [RFC0792] and [RFC4443] define the ICMP for 159 IPv4 and IPv6 networks, respectively. Because ICMP is another IP 160 protocol like, for example, UDP, a DetNet node MUST able to associate 161 an ICMP packet generated by the specified IP DetNet node and 162 addressed to the another IP DetnNet node with an IP DetNet flow 163 between this pair of endpoints. 165 3.1. Active OAM Using DetNet-in-UDP Encapsulation 167 Active OAM in IP DetNet can be realized using DetNet-in-UDP 168 encapsulation. Using DetNet-in-UDP tunnel between IP DetNet nodes 169 ensures that active OAM test packets are fate-sharing with the 170 monitored IP DetNet flow packets. As a result, a test packet shares 171 the tunnel with the IP DetNet flow and shares the fate, statistically 172 speaking, of the IP DetNet flow being monitored. 174 [I-D.varga-detnet-ip-preof] describes how DetNet with MPLS over UDP/ 175 IP data plane [RFC9025] can be used to support Packet Replication, 176 Elimination, and Ordering Functions to potentially lower packet loss, 177 improve the probability of on-time packet delivery and ensure in- 178 order packet delivery in IP DetNet's service sub-layer. To ensure 179 that an active OAM test packet follows the path of the monitored 180 DetNet flow in the DetNet service sub-layer the encapsulation shown 181 in Figure 1 is used. 183 +---------------------------------+ 184 | | 185 | DetNet App-Flow | 186 | (original IP) Packet | 187 | | 188 +---------------------------------+ <--\ 189 | DetNet ACH | | 190 +---------------------------------+ +--> PREOF capable 191 | Service-ID (S-Label) | | DetNet IP data 192 +---------------------------------+ | plane encapsulation 193 | UDP Header | | 194 +---------------------------------+ | 195 | IP Header | | 196 +---------------------------------+ <--/ 197 | Data-Link | 198 +---------------------------------+ 199 | Physical | 200 +---------------------------------+ 202 Figure 1: DetNet Associated Channel Header Format 204 where DetNet ACH is the DetNet Associated Channel Header defined in 205 [I-D.ietf-detnet-mpls-oam]. 207 3.2. Mapping Active OAM and IP DetNet flows 209 IP OAM protocols that use UDP transport, e.g., BFD and STAMP, can be 210 used to detect failures or performance degradation that affects an IP 211 DetNet flow. When the UDP destination port number used by the OAM 212 protocol is one of the assigned by IANA, then the UDP source port can 213 be used to achieve co-routedness of OAM, and the monitored IP DetNet 214 flow in the multipath environments, e.g., LAG or ECMP. To maximize 215 the accuracy of OAM results in detecting failures and monitoring 216 performance of IP DetNet, test packets should receive the same 217 treatment by the nodes as experienced by the IP DetNet packet. 218 Hence, the DSCP value used for a test packet MUST be mapped to 219 DetNet. 221 3.3. Active OAM Using GRE-in-UDP Encapsulation 223 [RFC8086] has defined the method of encapsulating GRE (Generic 224 Routing Encapsulation) headers in UDP. GRE-in-UDP encapsulation can 225 be used for IP DetNet OAM as it eases the task of mapping an OAM test 226 session to a particular IP DetNet flow that is identified by N-tuple. 227 Matching a GRE-in-UDP tunnel to the monitored IP DetNet flow enables 228 the use of Y.1731/G.8013 [ITU-T.1731] as a comprehensive toolset of 229 OAM. The Protocol Type field in GRE header MUST be set to 0x8902 230 assigned by IANA to IEEE 802.1ag Connectivity Fault Management (CFM) 231 Protocol / ITU-T Recommendation Y.1731. Y.1731/G.8013 supports 232 necessary for IP DetNet OAM functions, i.e., continuity check, one- 233 way packet loss and packet delay measurement. 235 4. OAM of DetNet IP Interworking with OAM of non-IP DetNet domains 237 A domain in which IP data plane provides DetNet service could be used 238 in conjunction with a TSN and a DetNet domain with MPLS data plane to 239 deliver end-to-end service. In such scenarios, the ability to detect 240 defects and monitor performance using OAM is essential. 241 [I-D.ietf-detnet-mpls-oam] identified two OAM interworking models - 242 peering and tunneling. Interworking between DetNet domains with IP 243 and MPLS data planes analyzed in Section 6.2 of 244 [I-D.ietf-detnet-mpls-oam]. Also, requirements and recommendations 245 for OAM interworking between a DetNet domain with MPLS data plane and 246 OAM of a TSN equally apply to a DetNet domain with an IP data plane. 248 5. IANA Considerations 250 This document does not have any requests for IANA allocation. This 251 section can be deleted before the publication of the draft. 253 6. Security Considerations 255 This document describes the applicability of the existing Fault 256 Management and Performance Monitoring IP OAM protocols, and does not 257 raise any security concerns or issues in addition to ones common to 258 networking or already documented for the referenced DetNet and OAM 259 protocols. 261 7. Acknowledgment 263 TBA 265 8. References 267 8.1. Normative References 269 [I-D.ietf-detnet-mpls-oam] 270 Mirsky, G., Chen, M., Varga, B., and J. Farkas, 271 "Operations, Administration and Maintenance (OAM) for 272 Deterministic Networks (DetNet) with MPLS Data Plane", 273 Work in Progress, Internet-Draft, draft-ietf-detnet-mpls- 274 oam-06, 10 December 2021, 275 . 278 [RFC0792] Postel, J., "Internet Control Message Protocol", STD 5, 279 RFC 792, DOI 10.17487/RFC0792, September 1981, 280 . 282 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 283 Requirement Levels", BCP 14, RFC 2119, 284 DOI 10.17487/RFC2119, March 1997, 285 . 287 [RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet 288 Control Message Protocol (ICMPv6) for the Internet 289 Protocol Version 6 (IPv6) Specification", STD 89, 290 RFC 4443, DOI 10.17487/RFC4443, March 2006, 291 . 293 [RFC8086] Yong, L., Ed., Crabbe, E., Xu, X., and T. Herbert, "GRE- 294 in-UDP Encapsulation", RFC 8086, DOI 10.17487/RFC8086, 295 March 2017, . 297 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 298 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 299 May 2017, . 301 [RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas, 302 "Deterministic Networking Architecture", RFC 8655, 303 DOI 10.17487/RFC8655, October 2019, 304 . 306 [RFC8939] Varga, B., Ed., Farkas, J., Berger, L., Fedyk, D., and S. 307 Bryant, "Deterministic Networking (DetNet) Data Plane: 308 IP", RFC 8939, DOI 10.17487/RFC8939, November 2020, 309 . 311 [RFC9025] Varga, B., Ed., Farkas, J., Berger, L., Malis, A., and S. 312 Bryant, "Deterministic Networking (DetNet) Data Plane: 313 MPLS over UDP/IP", RFC 9025, DOI 10.17487/RFC9025, April 314 2021, . 316 8.2. Informational References 318 [I-D.tpmb-detnet-oam-framework] 319 Mirsky, G., Theoleyre, F., Papadopoulos, G. Z., and C. J. 320 Bernardos, "Framework of Operations, Administration and 321 Maintenance (OAM) for Deterministic Networking (DetNet)", 322 Work in Progress, Internet-Draft, draft-tpmb-detnet-oam- 323 framework-01, 30 March 2021, 324 . 327 [I-D.varga-detnet-ip-preof] 328 Varga, B., Farkas, J., and A. G. Malis, "Deterministic 329 Networking (DetNet): DetNet PREOF via MPLS over UDP/IP", 330 Work in Progress, Internet-Draft, draft-varga-detnet-ip- 331 preof-02, 1 February 2022, 332 . 335 [ITU-T.1731] 336 ITU-T, "Operations, administration and maintenance (OAM) 337 functions and mechanisms for Ethernet-based networks", 338 ITU-T G.8013/Y.1731, August 2015. 340 [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection 341 (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, 342 . 344 [RFC7799] Morton, A., "Active and Passive Metrics and Methods (with 345 Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799, 346 May 2016, . 348 [RFC8762] Mirsky, G., Jun, G., Nydell, H., and R. Foote, "Simple 349 Two-Way Active Measurement Protocol", RFC 8762, 350 DOI 10.17487/RFC8762, March 2020, 351 . 353 Authors' Addresses 355 Greg Mirsky 356 Ericsson 358 Email: gregimirsky@gmail.com 360 Mach(Guoyi) Chen 361 Huawei 363 Email: mach.chen@huawei.com 364 David Black 365 Dell EMC 366 176 South Street 367 Hopkinton, MA, 01748 368 United States of America 370 Email: david.black@dell.com