idnits 2.17.1 draft-mirsky-detnet-ip-oam-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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (July 7, 2019) is 1749 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'I-D.ietf-detnet-ip-over-mpls' is defined on line 203, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-detnet-ip-over-tsn' is defined on line 209, but no explicit reference was found in the text == Outdated reference: A later version (-07) exists of draft-ietf-detnet-ip-01 == Outdated reference: A later version (-09) exists of draft-ietf-detnet-ip-over-mpls-01 == Outdated reference: A later version (-07) exists of draft-ietf-detnet-ip-over-tsn-00 == Outdated reference: A later version (-10) exists of draft-ietf-ippm-stamp-06 -- Obsolete informational reference (is this intentional?): RFC 8321 (Obsoleted by RFC 9341) Summary: 0 errors (**), 0 flaws (~~), 8 warnings (==), 2 comments (--). 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: January 8, 2020 Huawei 6 July 7, 2019 8 Operations, Administration and Maintenance (OAM) for Deterministic 9 Networks (DetNet) with IP Data Plane 10 draft-mirsky-detnet-ip-oam-00 12 Abstract 14 This document defines the principals for using Operations, 15 Administration, and Maintenance protocols and mechanisms in the 16 Deterministic Networking networks with IP data plane. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on January 8, 2020. 35 Copyright Notice 37 Copyright (c) 2019 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2. Conventions used in this document . . . . . . . . . . . . . . 2 54 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 55 2.2. Keywords . . . . . . . . . . . . . . . . . . . . . . . . 3 56 3. Active OAM for DetNet Networks with IP Data Plane . . . . . . 3 57 4. Use of Hybrid OAM in DetNet . . . . . . . . . . . . . . . . . 4 58 5. OAM of DetNet IP Interworking with OAM of DetNet MPLS . . . . 4 59 6. OAM of DetNet IP Interworking with OAM of TSN . . . . . . . . 4 60 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 61 8. Security Considerations . . . . . . . . . . . . . . . . . . . 4 62 9. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 4 63 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 64 10.1. Normative References . . . . . . . . . . . . . . . . . . 5 65 10.2. Informational References . . . . . . . . . . . . . . . . 5 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 68 1. Introduction 70 [I-D.ietf-detnet-architecture] introduces and explains Deterministic 71 Networks (DetNet) architecture. 73 Operations, Administration and Maintenance (OAM) protocols are used 74 to detect, localize defects in the network, and monitor network 75 performance. Some OAM functions, e.g., failure detection, work in 76 the network proactively, while others, e.g., defect localization, 77 usually performed on-demand. These tasks achieved by a combination 78 of active and hybrid, as defined in [RFC7799], OAM methods. 80 [I-D.mirsky-detnet-oam] lists the functional requirements toward OAM 81 for DetNet domain. The list can further be used for gap analysis of 82 available OAM tools to identify possible enhancements of existing or 83 whether new OAM tools are required to support proactive and on-demand 84 path monitoring and service validation. Also, the document defines 85 the OAM use principals for the DetNet networks with IP data plane. 87 2. Conventions used in this document 89 2.1. Terminology 91 The term "DetNet OAM" used in this document interchangeably with 92 longer version "set of OAM protocols, methods and tools for 93 Deterministic Networks". 95 DetNet Deterministic Networks 97 DiffServ Differentiated Services 98 DSCP DiffServ Code Point 100 OAM: Operations, Administration and Maintenance 102 PREF Packet Replication and Elimination Function 104 POF Packet Ordering Function 106 RDI Remote Defect Indication 108 Underlay Network or Underlay Layer: The network that provides 109 connectivity between the DetNet nodes. MPLS network providing LSP 110 connectivity between DetNet nodes is an example of the underlay 111 layer. 113 DetNet Node - a node that is an actor in the DetNet domain. DetNet 114 domain edge node and node that performs PREF within the domain are 115 examples of DetNet node. 117 2.2. Keywords 119 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 120 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 121 "OPTIONAL" in this document are to be interpreted as described in BCP 122 14 [RFC2119] [RFC8174] when, and only when, they appear in all 123 capitals, as shown here. 125 3. Active OAM for DetNet Networks with IP Data Plane 127 OAM protocols and mechanisms act within the data plane of the 128 particular networking layer. And thus it is critical that the data 129 plane encapsulation supports OAM mechanisms in such a way that DetNet 130 OAM packets are in-band with a DetNet flow being monitored, i.e., 131 DetNet OAM test packets follow precisely the same path as DetNet data 132 plane traffic both for unidirectional and bi-directional DetNet 133 paths. 135 The DetNet data plane encapsulation in a transport network with IP 136 encapsulations specified in [I-D.ietf-detnet-ip]. For the IP 137 underlay network, DetNet flows are identified by the 6-tuple that is 138 the destination IP address, source IP address, IP protocol, source 139 port number, destination port number, and differentiated services 140 (DiffServ) code point (DSCP). Active IP OAM protocols like 141 Bidirectional Forwarding Detection (BFD) [RFC5880] or STAMP 142 [I-D.ietf-ippm-stamp], use UDP transport and the well-known UDP port 143 numbers as the destination port. Thus a DetNet node should be able 144 to associate an IP DetNet flow with the particular test session to 145 ensure that test packets experience the same treatment as the DetNet 146 flow packets. 148 4. Use of Hybrid OAM in DetNet 150 Hybrid OAM methods are used in performance monitoring and defined in 151 [RFC7799] as: 153 Hybrid Methods are Methods of Measurement that use a combination 154 of Active Methods and Passive Methods. 156 A hybrid measurement method may produce metrics as close to passive, 157 but it still alters something in a data packet even if that is the 158 value of a designated field in the packet encapsulation. One example 159 of such a hybrid measurement method is the Alternate Marking method 160 (AMM) described in [RFC8321]. One of the advantages of the use of 161 AMM in a DetNet domain with IP data plane is that the marking is 162 applied to a data flow, thus ensuring that a measured metrics are 163 directly applicable to the DetNet flow. 165 5. OAM of DetNet IP Interworking with OAM of DetNet MPLS 167 TBA 169 6. OAM of DetNet IP Interworking with OAM of TSN 171 TBA 173 7. IANA Considerations 175 This document does not have any requests for IANA allocation. This 176 section can be deleted before the publication of the draft. 178 8. Security Considerations 180 This document describes the applicability of the existing Fault 181 Management and Performance Monitoring IP OAM protocols, and does not 182 raise any security concerns or issues in addition to ones common to 183 networking or already documented for the referenced OAM protocols. 185 9. Acknowledgment 187 TBA 189 10. References 191 10.1. Normative References 193 [I-D.ietf-detnet-architecture] 194 Finn, N., Thubert, P., Varga, B., and J. Farkas, 195 "Deterministic Networking Architecture", draft-ietf- 196 detnet-architecture-13 (work in progress), May 2019. 198 [I-D.ietf-detnet-ip] 199 Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A., 200 Bryant, S., and J. Korhonen, "DetNet Data Plane: IP", 201 draft-ietf-detnet-ip-01 (work in progress), July 2019. 203 [I-D.ietf-detnet-ip-over-mpls] 204 Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A., 205 Bryant, S., and J. Korhonen, "DetNet Data Plane: IP over 206 MPLS", draft-ietf-detnet-ip-over-mpls-01 (work in 207 progress), July 2019. 209 [I-D.ietf-detnet-ip-over-tsn] 210 Varga, B., Farkas, J., Malis, A., Bryant, S., and J. 211 Korhonen, "DetNet Data Plane: IP over IEEE 802.1 Time 212 Sensitive Networking (TSN)", draft-ietf-detnet-ip-over- 213 tsn-00 (work in progress), May 2019. 215 [I-D.mirsky-detnet-oam] 216 Mirsky, G. and M. Chen, "Operations, Administration and 217 Maintenance (OAM) for Deterministic Networks (DetNet)", 218 draft-mirsky-detnet-oam-03 (work in progress), May 2019. 220 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 221 Requirement Levels", BCP 14, RFC 2119, 222 DOI 10.17487/RFC2119, March 1997, 223 . 225 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 226 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 227 May 2017, . 229 10.2. Informational References 231 [I-D.ietf-ippm-stamp] 232 Mirsky, G., Jun, G., Nydell, H., and R. Foote, "Simple 233 Two-way Active Measurement Protocol", draft-ietf-ippm- 234 stamp-06 (work in progress), April 2019. 236 [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection 237 (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, 238 . 240 [RFC7799] Morton, A., "Active and Passive Metrics and Methods (with 241 Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799, 242 May 2016, . 244 [RFC8321] Fioccola, G., Ed., Capello, A., Cociglio, M., Castaldelli, 245 L., Chen, M., Zheng, L., Mirsky, G., and T. Mizrahi, 246 "Alternate-Marking Method for Passive and Hybrid 247 Performance Monitoring", RFC 8321, DOI 10.17487/RFC8321, 248 January 2018, . 250 Authors' Addresses 252 Greg Mirsky 253 ZTE Corp. 255 Email: gregimirsky@gmail.com 257 Mach(Guoyi) Chen 258 Huawei 260 Email: mach.chen@huawei.com