DetNet Working Group G. Mirsky
Internet-Draft ZTE Corp.
Intended status: Informational M. Chen
Expires: July 9, 2020 Huawei
January 6, 2020
Operations, Administration and Maintenance (OAM) for Deterministic
Networks (DetNet) with IP Data Plane
draft-mirsky-detnet-ip-oam-01
Abstract
This document defines the principals for using Operations,
Administration, and Maintenance protocols and mechanisms in the
Deterministic Networking networks with IP data plane.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 9, 2020.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Mirsky & Chen Expires July 9, 2020 [Page 1]
Internet-Draft OAM for DetNet over IP January 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions used in this document . . . . . . . . . . . . . . 2
2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
2.2. Keywords . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Active OAM for DetNet Networks with IP Data Plane . . . . . . 3
4. Use of Hybrid OAM in DetNet . . . . . . . . . . . . . . . . . 4
5. OAM of DetNet IP Interworking with OAM of DetNet MPLS . . . . 4
6. OAM of DetNet IP Interworking with OAM of TSN . . . . . . . . 4
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
8. Security Considerations . . . . . . . . . . . . . . . . . . . 4
9. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 4
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
10.1. Normative References . . . . . . . . . . . . . . . . . . 4
10.2. Informational References . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
[RFC8655] introduces and explains Deterministic Networks (DetNet)
architecture.
Operations, Administration and Maintenance (OAM) protocols are used
to detect, localize defects in the network, and monitor network
performance. Some OAM functions, e.g., failure detection, work in
the network proactively, while others, e.g., defect localization,
usually performed on-demand. These tasks achieved by a combination
of active and hybrid, as defined in [RFC7799], OAM methods.
[I-D.mirsky-detnet-mpls-oam] lists the functional requirements toward
OAM for DetNet domain. The list can further be used for gap analysis
of available OAM tools to identify possible enhancements of existing
or whether new OAM tools are required to support proactive and on-
demand path monitoring and service validation. Also, the document
defines the OAM use principals for the DetNet networks with IP data
plane.
2. Conventions used in this document
2.1. Terminology
The term "DetNet OAM" used in this document interchangeably with
longer version "set of OAM protocols, methods and tools for
Deterministic Networks".
DetNet Deterministic Networks
Mirsky & Chen Expires July 9, 2020 [Page 2]
Internet-Draft OAM for DetNet over IP January 2020
DiffServ Differentiated Services
OAM: Operations, Administration and Maintenance
PREF Packet Replication and Elimination Function
POF Packet Ordering Function
RDI Remote Defect Indication
Underlay Network or Underlay Layer: The network that provides
connectivity between the DetNet nodes. MPLS network providing LSP
connectivity between DetNet nodes is an example of the underlay
layer.
DetNet Node - a node that is an actor in the DetNet domain. DetNet
domain edge node and node that performs PREF within the domain are
examples of DetNet node.
2.2. Keywords
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
3. Active OAM for DetNet Networks with IP Data Plane
OAM protocols and mechanisms act within the data plane of the
particular networking layer. And thus it is critical that the data
plane encapsulation supports OAM mechanisms in such a way that DetNet
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
plane traffic both for unidirectional and bi-directional DetNet
paths.
The DetNet data plane encapsulation in a transport network with IP
encapsulations specified in Section 6 of [I-D.ietf-detnet-ip]. For
the IP underlay network, DetNet flows are identified by the ordered
match to the provisioned information set that, among other elements,
includes the IP protocol, source port number, destination port
number. Active IP OAM protocols like Bidirectional Forwarding
Detection (BFD) [RFC5880] or STAMP [I-D.ietf-ippm-stamp], use UDP
transport and the well-known UDP port numbers as the destination
port. Thus a DetNet node MUST be able to associate an IP DetNet flow
with the particular test session to ensure that test packets
experience the same treatment as the DetNet flow packets.
Mirsky & Chen Expires July 9, 2020 [Page 3]
Internet-Draft OAM for DetNet over IP January 2020
4. Use of Hybrid OAM in DetNet
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 IP data plane is that the marking is
applied to a data flow, thus ensuring that a measured metrics are
directly applicable to the DetNet flow.
5. OAM of DetNet IP Interworking with OAM of DetNet MPLS
TBA
6. OAM of DetNet IP Interworking with OAM of TSN
TBA
7. IANA Considerations
This document does not have any requests for IANA allocation. This
section can be deleted before the publication of the draft.
8. Security Considerations
This document describes the applicability of the existing Fault
Management and Performance Monitoring IP OAM protocols, and does not
raise any security concerns or issues in addition to ones common to
networking or already documented for the referenced OAM protocols.
9. Acknowledgment
TBA
10. References
10.1. Normative References
Mirsky & Chen Expires July 9, 2020 [Page 4]
Internet-Draft OAM for DetNet over IP January 2020
[I-D.ietf-detnet-ip]
Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,
Bryant, S., and J. Korhonen, "DetNet Data Plane: IP",
draft-ietf-detnet-ip-04 (work in progress), November 2019.
[I-D.mirsky-detnet-mpls-oam]
Mirsky, G. and M. Chen, "Operations, Administration and
Maintenance (OAM) for Deterministic Networks (DetNet) with
MPLS Data Plane", draft-mirsky-detnet-mpls-oam-00 (work in
progress), July 2019.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas,
"Deterministic Networking Architecture", RFC 8655,
DOI 10.17487/RFC8655, October 2019,
<https://www.rfc-editor.org/info/rfc8655>.
10.2. Informational References
[I-D.ietf-ippm-stamp]
Mirsky, G., Jun, G., Nydell, H., and R. Foote, "Simple
Two-way Active Measurement Protocol", draft-ietf-ippm-
stamp-10 (work in progress), October 2019.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
<https://www.rfc-editor.org/info/rfc5880>.
[RFC7799] Morton, A., "Active and Passive Metrics and Methods (with
Hybrid Types In-Between)", RFC 7799, DOI 10.17487/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>.
Mirsky & Chen Expires July 9, 2020 [Page 5]
Internet-Draft OAM for DetNet over IP January 2020
Authors' Addresses
Greg Mirsky
ZTE Corp.
Email: gregimirsky@gmail.com
Mach(Guoyi) Chen
Huawei
Email: mach.chen@huawei.com
Mirsky & Chen Expires July 9, 2020 [Page 6]