draft-ietf-detnet-ip-oam-00.txt   draft-ietf-detnet-ip-oam-01.txt 
DetNet Working Group G. Mirsky DetNet Working Group G. Mirsky
Internet-Draft ZTE Corp. Internet-Draft ZTE Corp.
Intended status: Informational M. Chen Intended status: Informational M. Chen
Expires: March 22, 2021 Huawei Expires: July 19, 2021 Huawei
D. Black D. Black
Dell EMC Dell EMC
September 18, 2020 January 15, 2021
Operations, Administration and Maintenance (OAM) for Deterministic Operations, Administration and Maintenance (OAM) for Deterministic
Networks (DetNet) with IP Data Plane Networks (DetNet) with IP Data Plane
draft-ietf-detnet-ip-oam-00 draft-ietf-detnet-ip-oam-01
Abstract Abstract
This document defines the principles for using Operations, This document defines the principles for using Operations,
Administration, and Maintenance protocols and mechanisms in the Administration, and Maintenance protocols and mechanisms in the
Deterministic Networking networks with the IP data plane. Deterministic Networking networks with the IP data plane.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 36 skipping to change at page 1, line 36
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 22, 2021. This Internet-Draft will expire on July 19, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions used in this document . . . . . . . . . . . . . . 3 2. Conventions used in this document . . . . . . . . . . . . . . 2
2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Keywords . . . . . . . . . . . . . . . . . . . . . . . . 3 2.2. Keywords . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Active OAM for DetNet Networks with the IP Data Plane . . . . 3 3. Active OAM for DetNet Networks with the IP Data Plane . . . . 3
3.1. Active OAM Using DetNet-in-UDP Encapsulation . . . . . . 4 3.1. Active OAM Using DetNet-in-UDP Encapsulation . . . . . . 4
3.2. Mapping Active OAM and IP DetNet flows . . . . . . . . . 4 3.2. Mapping Active OAM and IP DetNet flows . . . . . . . . . 4
3.3. Active OAM Using GRE-in-UDP Encapsulation . . . . . . . . 5 3.3. Active OAM Using GRE-in-UDP Encapsulation . . . . . . . . 5
4. Use of Hybrid OAM in DetNet . . . . . . . . . . . . . . . . . 5 4. OAM of DetNet IP Interworking with OAM of non-IP DetNet
5. OAM of DetNet IP Interworking with OAM of non-IP DetNet
domains . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 domains . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
7. Security Considerations . . . . . . . . . . . . . . . . . . . 6 6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
8. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 6 7. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 5
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
9.1. Normative References . . . . . . . . . . . . . . . . . . 6 8.1. Normative References . . . . . . . . . . . . . . . . . . 6
9.2. Informational References . . . . . . . . . . . . . . . . 7 8.2. Informational References . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
[RFC8655] introduces and explains Deterministic Networks (DetNet) [RFC8655] introduces and explains Deterministic Networks (DetNet)
architecture. architecture.
Operations, Administration and Maintenance (OAM) protocols are used Operations, Administration and Maintenance (OAM) protocols are used
to detect, localize defects in the network, and monitor network to detect, localize defects in the network, and monitor network
performance. Some OAM functions, e.g., failure detection, work in performance. Some OAM functions, e.g., failure detection, work in
the network proactively, while others, e.g., defect localization, the network proactively, while others, e.g., defect localization,
usually performed on-demand. These tasks achieved by a combination usually performed on-demand. These tasks achieved by a combination
of active and hybrid, as defined in [RFC7799], OAM methods. of active and hybrid, as defined in [RFC7799], OAM methods.
[I-D.ietf-detnet-mpls-oam] lists the functional requirements toward [I-D.tpmb-detnet-oam-framework] lists the functional requirements
OAM for DetNet domain. The list can further be used for gap analysis toward OAM for DetNet domain. The list can further be used for gap
of available OAM tools to identify possible enhancements of existing analysis of available OAM tools to identify possible enhancements of
or whether new OAM tools are required to support proactive and on- existing or whether new OAM tools are required to support proactive
demand path monitoring and service validation. Also, the document and on-demand path monitoring and service validation. Also, the
defines the OAM use principals for the DetNet networks with the IP document defines the OAM use principals for the DetNet networks with
data plane. the IP data plane.
2. Conventions used in this document 2. Conventions used in this document
2.1. Terminology 2.1. Terminology
The term "DetNet OAM" used in this document interchangeably with The term "DetNet OAM" used in this document interchangeably with
longer version "set of OAM protocols, methods and tools for longer version "set of OAM protocols, methods and tools for
Deterministic Networks". Deterministic Networks".
DetNet Deterministic Networks DetNet Deterministic Networks
DiffServ Differentiated Services DiffServ Differentiated Services
skipping to change at page 4, line 6 skipping to change at page 4, line 6
OAM protocols and mechanisms act within the data plane of the OAM protocols and mechanisms act within the data plane of the
particular networking layer. And thus it is critical that the data particular networking layer. And thus it is critical that the data
plane encapsulation supports OAM mechanisms in such a way that DetNet plane encapsulation supports OAM mechanisms in such a way that DetNet
OAM packets are in-band with a DetNet flow being monitored, i.e., OAM packets are in-band with a DetNet flow being monitored, i.e.,
DetNet OAM test packets follow precisely the same path as DetNet data DetNet OAM test packets follow precisely the same path as DetNet data
plane traffic both for unidirectional and bi-directional DetNet plane traffic both for unidirectional and bi-directional DetNet
paths. paths.
The DetNet data plane encapsulation in a transport network with IP The DetNet data plane encapsulation in a transport network with IP
encapsulations specified in Section 6 of [I-D.ietf-detnet-ip]. For encapsulations specified in Section 6 of [RFC8939]. For the IP
the IP underlay network, DetNet flows are identified by the ordered underlay network, DetNet flows are identified by the ordered match to
match to the provisioned information set that, among other elements, the provisioned information set that, among other elements, includes
includes the IP protocol, source port number, destination port the IP protocol, source port number, destination port number. Active
number. Active IP OAM protocols like Bidirectional Forwarding IP OAM protocols like Bidirectional Forwarding Detection (BFD)
Detection (BFD) [RFC5880] or STAMP [RFC8762], use UDP transport and [RFC5880] or STAMP [RFC8762], use UDP transport and the well-known
the well-known UDP port numbers as the destination port. Thus a UDP port numbers as the destination port. Thus a DetNet node MUST be
DetNet node MUST be able to associate an IP DetNet flow with the able to associate an IP DetNet flow with the particular test session
particular test session to ensure that test packets experience the to ensure that test packets experience the same treatment as the
same treatment as the DetNet flow packets. DetNet flow packets.
Most of on-demand failure detection and localization in IP networks Most of on-demand failure detection and localization in IP networks
is being done by using the Internet Control Message Protocol (ICMP) is being done by using the Internet Control Message Protocol (ICMP)
Echo Request, Echo Reply and the set of defined error messages, e.g., Echo Request, Echo Reply and the set of defined error messages, e.g.,
Destination Unreachable, with the more detailed information provided Destination Unreachable, with the more detailed information provided
through code points. [RFC0792] and [RFC4443] define the ICMP for through code points. [RFC0792] and [RFC4443] define the ICMP for
IPv4 and IPv6 networks, respectively. Because ICMP is another IP IPv4 and IPv6 networks, respectively. Because ICMP is another IP
protocol like, for example, UDP, a DetNet node MUST able to associate protocol like, for example, UDP, a DetNet node MUST able to associate
an ICMP packet generated by the specified IP DetNet node and an ICMP packet generated by the specified IP DetNet node and
addressed to the another IP DetnNet node with an IP DetNet flow addressed to the another IP DetnNet node with an IP DetNet flow
skipping to change at page 5, line 19 skipping to change at page 5, line 19
be used for IP DetNet OAM as it eases the task of mapping an OAM test be used for IP DetNet OAM as it eases the task of mapping an OAM test
session to a particular IP DetNet flow that is identified by N-tuple. session to a particular IP DetNet flow that is identified by N-tuple.
Matching a GRE-in-UDP tunnel to the monitored IP DetNet flow enables Matching a GRE-in-UDP tunnel to the monitored IP DetNet flow enables
the use of Y.1731/G.8013 [ITU-T.1731] as a comprehensive toolset of the use of Y.1731/G.8013 [ITU-T.1731] as a comprehensive toolset of
OAM. The Protocol Type field in GRE header MUST be set to 0x8902 OAM. The Protocol Type field in GRE header MUST be set to 0x8902
assigned by IANA to IEEE 802.1ag Connectivity Fault Management (CFM) assigned by IANA to IEEE 802.1ag Connectivity Fault Management (CFM)
Protocol / ITU-T Recommendation Y.1731. Y.1731/G.8013 supports Protocol / ITU-T Recommendation Y.1731. Y.1731/G.8013 supports
necessary for IP DetNet OAM functions, i.e., continuity check, one- necessary for IP DetNet OAM functions, i.e., continuity check, one-
way packet loss and packet delay measurement. way packet loss and packet delay measurement.
4. Use of Hybrid OAM in DetNet 4. OAM of DetNet IP Interworking with OAM of non-IP DetNet domains
Hybrid OAM methods are used in performance monitoring and defined in
[RFC7799] as:
Hybrid Methods are Methods of Measurement that use a combination
of Active Methods and Passive Methods.
A hybrid measurement method may produce metrics as close to passive,
but it still alters something in a data packet even if that is the
value of a designated field in the packet encapsulation. One example
of such a hybrid measurement method is the Alternate Marking method
(AMM) described in [RFC8321]. One of the advantages of the use of
AMM in a DetNet domain with the IP data plane is that the marking is
applied to a data flow, thus ensuring that measured metrics are
directly applicable to the DetNet flow.
5. OAM of DetNet IP Interworking with OAM of non-IP DetNet domains
A domain in which IP data plane provides DetNet service could be used A domain in which IP data plane provides DetNet service could be used
in conjunction with a TSN and a DetNet domain with MPLS data plane to in conjunction with a TSN and a DetNet domain with MPLS data plane to
deliver end-to-end service. In such scenarios, the ability to detect deliver end-to-end service. In such scenarios, the ability to detect
defects and monitor performance using OAM is essential. defects and monitor performance using OAM is essential.
[I-D.ietf-detnet-mpls-oam] identified two OAM interworking models - [I-D.ietf-detnet-mpls-oam] identified two OAM interworking models -
peering and tunneling. Interworking between DetNet domains with IP peering and tunneling. Interworking between DetNet domains with IP
and MPLS data planes analyzed in Section 6.2 of and MPLS data planes analyzed in Section 6.2 of
[I-D.ietf-detnet-mpls-oam]. Also, requirements and recommendations [I-D.ietf-detnet-mpls-oam]. Also, requirements and recommendations
for OAM interworking between a DetNet domain with MPLS data plane and for OAM interworking between a DetNet domain with MPLS data plane and
OAM of a TSN equally apply to a DetNet domain with an IP data plane. OAM of a TSN equally apply to a DetNet domain with an IP data plane.
6. IANA Considerations 5. IANA Considerations
This document does not have any requests for IANA allocation. This This document does not have any requests for IANA allocation. This
section can be deleted before the publication of the draft. section can be deleted before the publication of the draft.
7. Security Considerations 6. Security Considerations
This document describes the applicability of the existing Fault This document describes the applicability of the existing Fault
Management and Performance Monitoring IP OAM protocols, and does not Management and Performance Monitoring IP OAM protocols, and does not
raise any security concerns or issues in addition to ones common to raise any security concerns or issues in addition to ones common to
networking or already documented for the referenced DetNet and OAM networking or already documented for the referenced DetNet and OAM
protocols. protocols.
8. Acknowledgment 7. Acknowledgment
TBA TBA
9. References 8. References
9.1. Normative References
[I-D.ietf-detnet-ip] 8.1. Normative References
Varga, B., Farkas, J., Berger, L., Fedyk, D., and S.
Bryant, "DetNet Data Plane: IP", draft-ietf-detnet-ip-07
(work in progress), July 2020.
[I-D.ietf-detnet-mpls-oam] [I-D.ietf-detnet-mpls-oam]
Mirsky, G. and M. Chen, "Operations, Administration and Mirsky, G. and M. Chen, "Operations, Administration and
Maintenance (OAM) for Deterministic Networks (DetNet) with Maintenance (OAM) for Deterministic Networks (DetNet) with
MPLS Data Plane", draft-ietf-detnet-mpls-oam-01 (work in MPLS Data Plane", draft-ietf-detnet-mpls-oam-01 (work in
progress), July 2020. progress), July 2020.
[RFC0792] Postel, J., "Internet Control Message Protocol", STD 5, [RFC0792] Postel, J., "Internet Control Message Protocol", STD 5,
RFC 792, DOI 10.17487/RFC0792, September 1981, RFC 792, DOI 10.17487/RFC0792, September 1981,
<https://www.rfc-editor.org/info/rfc792>. <https://www.rfc-editor.org/info/rfc792>.
skipping to change at page 7, line 18 skipping to change at page 6, line 43
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas, [RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas,
"Deterministic Networking Architecture", RFC 8655, "Deterministic Networking Architecture", RFC 8655,
DOI 10.17487/RFC8655, October 2019, DOI 10.17487/RFC8655, October 2019,
<https://www.rfc-editor.org/info/rfc8655>. <https://www.rfc-editor.org/info/rfc8655>.
9.2. Informational References [RFC8939] Varga, B., Ed., Farkas, J., Berger, L., Fedyk, D., and S.
Bryant, "Deterministic Networking (DetNet) Data Plane:
IP", RFC 8939, DOI 10.17487/RFC8939, November 2020,
<https://www.rfc-editor.org/info/rfc8939>.
8.2. Informational References
[I-D.tpmb-detnet-oam-framework]
Mirsky, G., Theoleyre, F., Papadopoulos, G., and C.
Bernardos, "Framework of Operations, Administration and
Maintenance (OAM) for Deterministic Networking (DetNet)",
draft-tpmb-detnet-oam-framework-00 (work in progress),
January 2021.
[ITU-T.1731] [ITU-T.1731]
ITU-T, "Operations, administration and maintenance (OAM) ITU-T, "Operations, administration and maintenance (OAM)
functions and mechanisms for Ethernet-based networks", functions and mechanisms for Ethernet-based networks",
ITU-T G.8013/Y.1731, August 2015. ITU-T G.8013/Y.1731, August 2015.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
<https://www.rfc-editor.org/info/rfc5880>. <https://www.rfc-editor.org/info/rfc5880>.
[RFC7799] Morton, A., "Active and Passive Metrics and Methods (with [RFC7799] Morton, A., "Active and Passive Metrics and Methods (with
Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799, Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799,
May 2016, <https://www.rfc-editor.org/info/rfc7799>. May 2016, <https://www.rfc-editor.org/info/rfc7799>.
[RFC8321] Fioccola, G., Ed., Capello, A., Cociglio, M., Castaldelli,
L., Chen, M., Zheng, L., Mirsky, G., and T. Mizrahi,
"Alternate-Marking Method for Passive and Hybrid
Performance Monitoring", RFC 8321, DOI 10.17487/RFC8321,
January 2018, <https://www.rfc-editor.org/info/rfc8321>.
[RFC8762] Mirsky, G., Jun, G., Nydell, H., and R. Foote, "Simple [RFC8762] Mirsky, G., Jun, G., Nydell, H., and R. Foote, "Simple
Two-Way Active Measurement Protocol", RFC 8762, Two-Way Active Measurement Protocol", RFC 8762,
DOI 10.17487/RFC8762, March 2020, DOI 10.17487/RFC8762, March 2020,
<https://www.rfc-editor.org/info/rfc8762>. <https://www.rfc-editor.org/info/rfc8762>.
Authors' Addresses Authors' Addresses
Greg Mirsky Greg Mirsky
ZTE Corp. ZTE Corp.
 End of changes. 19 change blocks. 
67 lines changed or deleted 49 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/