idnits 2.17.1 draft-ietf-detnet-ip-oam-02.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 (30 March 2021) is 1095 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-02 == Outdated reference: A later version (-01) exists of draft-tpmb-detnet-oam-framework-00 Summary: 0 errors (**), 0 flaws (~~), 3 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 ZTE Corp. 4 Intended status: Informational M. Chen 5 Expires: 1 October 2021 Huawei 6 D. Black 7 Dell EMC 8 30 March 2021 10 Operations, Administration and Maintenance (OAM) for Deterministic 11 Networks (DetNet) with IP Data Plane 12 draft-ietf-detnet-ip-oam-02 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 1 October 2021. 37 Copyright Notice 39 Copyright (c) 2021 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 Simplified BSD License text 48 as described in Section 4.e of the Trust Legal Provisions and are 49 provided without warranty as described in the Simplified 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 . . . . 3 58 3.1. Active OAM Using DetNet-in-UDP Encapsulation . . . . . . 4 59 3.2. Mapping Active OAM and IP DetNet flows . . . . . . . . . 4 60 3.3. Active OAM Using GRE-in-UDP Encapsulation . . . . . . . . 5 61 4. OAM of DetNet IP Interworking with OAM of non-IP DetNet 62 domains . . . . . . . . . . . . . . . . . . . . . . . . . 5 63 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 64 6. Security Considerations . . . . . . . . . . . . . . . . . . . 5 65 7. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 5 66 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 67 8.1. Normative References . . . . . . . . . . . . . . . . . . 5 68 8.2. Informational References . . . . . . . . . . . . . . . . 6 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 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 Underlay Network or Underlay Layer: The network that provides 114 connectivity between the DetNet nodes. MPLS network providing LSP 115 connectivity between DetNet nodes is an example of the underlay 116 layer. 118 DetNet Node - a node that is an actor in the DetNet domain. DetNet 119 domain edge node and node that performs PREF within the domain are 120 examples of DetNet node. 122 2.2. Keywords 124 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 125 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 126 "OPTIONAL" in this document are to be interpreted as described in BCP 127 14 [RFC2119] [RFC8174] when, and only when, they appear in all 128 capitals, as shown here. 130 3. Active OAM for DetNet Networks with the IP Data Plane 132 OAM protocols and mechanisms act within the data plane of the 133 particular networking layer. And thus it is critical that the data 134 plane encapsulation supports OAM mechanisms in such a way that DetNet 135 OAM packets are in-band with a DetNet flow being monitored, i.e., 136 DetNet OAM test packets follow precisely the same path as DetNet data 137 plane traffic both for unidirectional and bi-directional DetNet 138 paths. 140 The DetNet data plane encapsulation in a transport network with IP 141 encapsulations specified in Section 6 of [RFC8939]. For the IP 142 underlay network, DetNet flows are identified by the ordered match to 143 the provisioned information set that, among other elements, includes 144 the IP protocol, source port number, destination port number. Active 145 IP OAM protocols like Bidirectional Forwarding Detection (BFD) 146 [RFC5880] or STAMP [RFC8762], use UDP transport and the well-known 147 UDP port numbers as the destination port. Thus a DetNet node MUST be 148 able to associate an IP DetNet flow with the particular test session 149 to ensure that test packets experience the same treatment as the 150 DetNet flow packets. 152 Most of on-demand failure detection and localization in IP networks 153 is being done by using the Internet Control Message Protocol (ICMP) 154 Echo Request, Echo Reply and the set of defined error messages, e.g., 155 Destination Unreachable, with the more detailed information provided 156 through code points. [RFC0792] and [RFC4443] define the ICMP for 157 IPv4 and IPv6 networks, respectively. Because ICMP is another IP 158 protocol like, for example, UDP, a DetNet node MUST able to associate 159 an ICMP packet generated by the specified IP DetNet node and 160 addressed to the another IP DetnNet node with an IP DetNet flow 161 between this pair of endpoints. 163 3.1. Active OAM Using DetNet-in-UDP Encapsulation 165 Active OAM in IP DetNet can be realized using DetNet-in-UDP 166 encapsulation [Ed.note: Do we define it in this document or start a 167 new one?]. Using DetNet-in-UDP tunnel between IP DetNet nodes 168 ensures that active OAM test packets are fate-sharing with the 169 monitored IP DetNet flow packets. As a result, a test packet shares 170 the tunnel with the IP DetNet flow and shares the fate, statistically 171 speaking, of the IP DetNet flow being monitored. 173 3.2. Mapping Active OAM and IP DetNet flows 175 IP OAM protocols that use UDP transport, e.g., BFD and STAMP, can be 176 used to detect failures or performance degradation that affects an IP 177 DetNet flow. When the UDP destination port number used by the OAM 178 protocol is one of the assigned by IANA, then the UDP source port can 179 be used to achieve co-routedness of OAM, and the monitored IP DetNet 180 flow in the multipath environments, e.g., LAG or ECMP. To maximize 181 the accuracy of OAM results in detecting failures and monitoring 182 performance of IP DetNet, test packets should receive the same 183 treatment by the nodes as experienced by the IP DetNet packet. 184 Hence, the DSCP value used for a test packet MUST be mapped to 185 DetNet. 187 3.3. Active OAM Using GRE-in-UDP Encapsulation 189 [RFC8086] has defined the method of encapsulating GRE (Generic 190 Routing Encapsulation) headers in UDP. GRE-in-UDP encapsulation can 191 be used for IP DetNet OAM as it eases the task of mapping an OAM test 192 session to a particular IP DetNet flow that is identified by N-tuple. 193 Matching a GRE-in-UDP tunnel to the monitored IP DetNet flow enables 194 the use of Y.1731/G.8013 [ITU-T.1731] as a comprehensive toolset of 195 OAM. The Protocol Type field in GRE header MUST be set to 0x8902 196 assigned by IANA to IEEE 802.1ag Connectivity Fault Management (CFM) 197 Protocol / ITU-T Recommendation Y.1731. Y.1731/G.8013 supports 198 necessary for IP DetNet OAM functions, i.e., continuity check, one- 199 way packet loss and packet delay measurement. 201 4. OAM of DetNet IP Interworking with OAM of non-IP DetNet domains 203 A domain in which IP data plane provides DetNet service could be used 204 in conjunction with a TSN and a DetNet domain with MPLS data plane to 205 deliver end-to-end service. In such scenarios, the ability to detect 206 defects and monitor performance using OAM is essential. 207 [I-D.ietf-detnet-mpls-oam] identified two OAM interworking models - 208 peering and tunneling. Interworking between DetNet domains with IP 209 and MPLS data planes analyzed in Section 6.2 of 210 [I-D.ietf-detnet-mpls-oam]. Also, requirements and recommendations 211 for OAM interworking between a DetNet domain with MPLS data plane and 212 OAM of a TSN equally apply to a DetNet domain with an IP data plane. 214 5. IANA Considerations 216 This document does not have any requests for IANA allocation. This 217 section can be deleted before the publication of the draft. 219 6. Security Considerations 221 This document describes the applicability of the existing Fault 222 Management and Performance Monitoring IP OAM protocols, and does not 223 raise any security concerns or issues in addition to ones common to 224 networking or already documented for the referenced DetNet and OAM 225 protocols. 227 7. Acknowledgment 229 TBA 231 8. References 233 8.1. Normative References 235 [I-D.ietf-detnet-mpls-oam] 236 Mirsky, G. and M. Chen, "Operations, Administration and 237 Maintenance (OAM) for Deterministic Networks (DetNet) with 238 MPLS Data Plane", Work in Progress, Internet-Draft, draft- 239 ietf-detnet-mpls-oam-02, 15 January 2021, 240 . 243 [RFC0792] Postel, J., "Internet Control Message Protocol", STD 5, 244 RFC 792, DOI 10.17487/RFC0792, September 1981, 245 . 247 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 248 Requirement Levels", BCP 14, RFC 2119, 249 DOI 10.17487/RFC2119, March 1997, 250 . 252 [RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet 253 Control Message Protocol (ICMPv6) for the Internet 254 Protocol Version 6 (IPv6) Specification", STD 89, 255 RFC 4443, DOI 10.17487/RFC4443, March 2006, 256 . 258 [RFC8086] Yong, L., Ed., Crabbe, E., Xu, X., and T. Herbert, "GRE- 259 in-UDP Encapsulation", RFC 8086, DOI 10.17487/RFC8086, 260 March 2017, . 262 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 263 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 264 May 2017, . 266 [RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas, 267 "Deterministic Networking Architecture", RFC 8655, 268 DOI 10.17487/RFC8655, October 2019, 269 . 271 [RFC8939] Varga, B., Ed., Farkas, J., Berger, L., Fedyk, D., and S. 272 Bryant, "Deterministic Networking (DetNet) Data Plane: 273 IP", RFC 8939, DOI 10.17487/RFC8939, November 2020, 274 . 276 8.2. Informational References 278 [I-D.tpmb-detnet-oam-framework] 279 Mirsky, G., Theoleyre, F., Papadopoulos, G. Z., and C. J. 280 Bernardos, "Framework of Operations, Administration and 281 Maintenance (OAM) for Deterministic Networking (DetNet)", 282 Work in Progress, Internet-Draft, draft-tpmb-detnet-oam- 283 framework-00, 15 January 2021, 284 . 287 [ITU-T.1731] 288 ITU-T, "Operations, administration and maintenance (OAM) 289 functions and mechanisms for Ethernet-based networks", 290 ITU-T G.8013/Y.1731, August 2015. 292 [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection 293 (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, 294 . 296 [RFC7799] Morton, A., "Active and Passive Metrics and Methods (with 297 Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799, 298 May 2016, . 300 [RFC8762] Mirsky, G., Jun, G., Nydell, H., and R. Foote, "Simple 301 Two-Way Active Measurement Protocol", RFC 8762, 302 DOI 10.17487/RFC8762, March 2020, 303 . 305 Authors' Addresses 307 Greg Mirsky 308 ZTE Corp. 310 Email: gregimirsky@gmail.com, gregory.mirsky@ztetx.com 312 Mach(Guoyi) Chen 313 Huawei 315 Email: mach.chen@huawei.com 317 David Black 318 Dell EMC 319 176 South Street 320 Hopkinton, MA, 01748 321 United States of America 323 Email: david.black@dell.com