draft-ietf-detnet-oam-framework-02.txt   draft-ietf-detnet-oam-framework-03.txt 
DetNet G. Mirsky DetNet G. Mirsky
Internet-Draft ZTE Corp. Internet-Draft ZTE Corp.
Intended status: Informational F. Theoleyre Intended status: Informational F. Theoleyre
Expires: 29 December 2021 CNRS Expires: 7 January 2022 CNRS
G.Z. Papadopoulos G.Z. Papadopoulos
IMT Atlantique IMT Atlantique
CJ. Bernardos CJ. Bernardos
UC3M UC3M
27 June 2021 6 July 2021
Framework of Operations, Administration and Maintenance (OAM) for Framework of Operations, Administration and Maintenance (OAM) for
Deterministic Networking (DetNet) Deterministic Networking (DetNet)
draft-ietf-detnet-oam-framework-02 draft-ietf-detnet-oam-framework-03
Abstract Abstract
Deterministic Networking (DetNet), as defined in RFC 8655, is aimed Deterministic Networking (DetNet), as defined in RFC 8655, is aimed
to provide a bounded end-to-end latency on top of the network to provide a bounded end-to-end latency on top of the network
infrastructure, comprising both Layer 2 bridged and Layer 3 routed infrastructure, comprising both Layer 2 bridged and Layer 3 routed
segments. This document's primary purpose is to detail the specific segments. This document's primary purpose is to detail the specific
requirements of the Operation, Administration, and Maintenance (OAM) requirements of the Operation, Administration, and Maintenance (OAM)
recommended to maintain a deterministic network. With the recommended to maintain a deterministic network. With the
implementation of the OAM framework in DetNet, an operator will have implementation of the OAM framework in DetNet, an operator will have
skipping to change at page 1, line 46 skipping to change at page 1, line 46
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 29 December 2021. This Internet-Draft will expire on 7 January 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text extracted from this document must include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License. provided without warranty as described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3. Requirements Language . . . . . . . . . . . . . . . . . . 4 1.3. Requirements Language . . . . . . . . . . . . . . . . . . 5
2. Role of OAM in DetNet . . . . . . . . . . . . . . . . . . . . 4 2. Role of OAM in DetNet . . . . . . . . . . . . . . . . . . . . 5
3. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Information Collection . . . . . . . . . . . . . . . . . 6 3.1. Information Collection . . . . . . . . . . . . . . . . . 6
3.2. Continuity Check . . . . . . . . . . . . . . . . . . . . 7 3.2. Continuity Check . . . . . . . . . . . . . . . . . . . . 7
3.3. Connectivity Verification . . . . . . . . . . . . . . . . 7 3.3. Connectivity Verification . . . . . . . . . . . . . . . . 7
3.4. Route Tracing . . . . . . . . . . . . . . . . . . . . . . 7 3.4. Route Tracing . . . . . . . . . . . . . . . . . . . . . . 7
3.5. Fault Verification/detection . . . . . . . . . . . . . . 8 3.5. Fault Verification/detection . . . . . . . . . . . . . . 8
3.6. Fault Localization and Characterization . . . . . . . . . 8 3.6. Fault Localization and Characterization . . . . . . . . . 8
3.7. Use of Hybrid OAM in DetNet . . . . . . . . . . . . . . . 8 3.7. Use of Hybrid OAM in DetNet . . . . . . . . . . . . . . . 8
4. Administration . . . . . . . . . . . . . . . . . . . . . . . 9 4. Administration . . . . . . . . . . . . . . . . . . . . . . . 9
4.1. Collection of metrics . . . . . . . . . . . . . . . . . . 9 4.1. Collection of metrics . . . . . . . . . . . . . . . . . . 9
4.2. Worst-case metrics . . . . . . . . . . . . . . . . . . . 9 4.2. Worst-case metrics . . . . . . . . . . . . . . . . . . . 10
5. Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . 10 5. Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.1. Replication / Elimination . . . . . . . . . . . . . . . . 10 5.1. Replication / Elimination . . . . . . . . . . . . . . . . 10
5.2. Resource Reservation . . . . . . . . . . . . . . . . . . 10 5.2. Resource Reservation . . . . . . . . . . . . . . . . . . 11
5.3. Soft transition after reconfiguration . . . . . . . . . . 11 5.3. Soft transition after reconfiguration . . . . . . . . . . 11
6. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 11 6. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 11
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
8. Security Considerations . . . . . . . . . . . . . . . . . . . 13 8. Security Considerations . . . . . . . . . . . . . . . . . . . 13
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
10.1. Normative References . . . . . . . . . . . . . . . . . . 13 10.1. Normative References . . . . . . . . . . . . . . . . . . 13
10.2. Informative References . . . . . . . . . . . . . . . . . 13 10.2. Informative References . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
Deterministic Networking (DetNet) [RFC8655] has proposed to provide a Deterministic Networking (DetNet) [RFC8655] has proposed to provide a
skipping to change at page 4, line 29 skipping to change at page 4, line 29
* Active measurement methods (as defined in [RFC7799]) modify a * Active measurement methods (as defined in [RFC7799]) modify a
DetNet flow by inserting novel fields, injecting specially DetNet flow by inserting novel fields, injecting specially
constructed test packets [RFC2544]). constructed test packets [RFC2544]).
* Passive measurement methods [RFC7799] infer information by * Passive measurement methods [RFC7799] infer information by
observing unmodified existing flows. observing unmodified existing flows.
* Hybrid measurement methods [RFC7799] is the combination of * Hybrid measurement methods [RFC7799] is the combination of
elements of both active and passive measurement methods. elements of both active and passive measurement methods.
* In-band OAM is an active OAM is considered in-band in the
monitored DetNet OAM domain when it traverses the same set of
links and interfaces receiving the same QoS and Packet
Replication, Elimination, and Ordering Functions (PREOF) treatment
as the monitored DetNet flow.
* Out-of-band OAM is an active OAM whose path through the DetNet
domain is not topologically identical to the path of the monitored
DetNet flow, or its test packets receive different QoS and/or
PREOF treatment, or both.
* On-path telemetry can be realized as a hybrid OAM method. The
origination of the telemetry information is inherently in-band as
packets in a DetNet flow are used as triggers. Collection of the
on-path telemetry information can be performed using in-band or
out-of-band OAM methods.
1.2. Acronyms 1.2. Acronyms
OAM: Operations, Administration, and Maintenance OAM: Operations, Administration, and Maintenance
DetNet: Deterministic Networking DetNet: Deterministic Networking
SLO: Service Level Objective SLO: Service Level Objective
1.3. Requirements Language 1.3. Requirements Language
skipping to change at page 6, line 8 skipping to change at page 6, line 17
allow, for example, to recognize/discover DetNet relay nodes, to get allow, for example, to recognize/discover DetNet relay nodes, to get
information about their configuration, and to check their operation information about their configuration, and to check their operation
or status. or status.
DetNet service sub-layer functions using a sequence number. That DetNet service sub-layer functions using a sequence number. That
creates a challenge for inserting OAM packets in the DetNet flow. creates a challenge for inserting OAM packets in the DetNet flow.
Fault tolerance also assumes that multiple paths could be provisioned Fault tolerance also assumes that multiple paths could be provisioned
to maintain an end-to-end circuit by adapting to the existing to maintain an end-to-end circuit by adapting to the existing
conditions. The central controller/orchestrator typically controls conditions. The central controller/orchestrator typically controls
the Packet Replication, Elimination, and Ordering Functions (PREOF) the PREOF on a node. OAM is expected to support monitoring and
on a node. OAM is expected to support monitoring and troubleshooting troubleshooting PREOF on a particular node and within the domain.
PREOF on a particular node and within the domain.
Note that distributed controllers can also control PREOF in those Note that distributed controllers can also control PREOF in those
scenarios where DetNet solutions involve more than one single central scenarios where DetNet solutions involve more than one single central
controller. controller.
DetNet forwarding sub-layer is based on legacy technologies and has a DetNet forwarding sub-layer is based on legacy technologies and has a
much better coverage regarding OAM. However, the forwarding sub- much better coverage regarding OAM. However, the forwarding sub-
layer is terminated at DetNet relay nodes, so the end-to-end OAM layer is terminated at DetNet relay nodes, so the end-to-end OAM
state of forwarding may be created only based on the status of state of forwarding may be created only based on the status of
multiple forwarding sub-layer segments serving a given DetNet flow multiple forwarding sub-layer segments serving a given DetNet flow
skipping to change at page 13, line 9 skipping to change at page 13, line 14
7. IANA Considerations 7. IANA Considerations
This document has no actionable requirements for IANA. This section This document has no actionable requirements for IANA. This section
can be removed before the publication. can be removed before the publication.
8. Security Considerations 8. Security Considerations
This document lists the OAM requirements for a DetNet domain and does This document lists the OAM requirements for a DetNet domain and does
not raise any security concerns or issues in addition to ones common not raise any security concerns or issues in addition to ones common
to networking and those specific to a DetNet discussed in to networking and those specific to a DetNet discussed in [RFC9055].
[I-D.ietf-detnet-security].
9. Acknowledgments 9. Acknowledgments
The authors express their appreciation and gratitude to Pascal The authors express their appreciation and gratitude to Pascal
Thubert for the review, insightful questions, and helpful comments. Thubert for the review, insightful questions, and helpful comments.
10. References 10. References
10.1. Normative References 10.1. Normative References
skipping to change at page 13, line 37 skipping to change at page 13, line 41
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>.
10.2. Informative References 10.2. Informative References
[I-D.ietf-detnet-security]
Grossman, E., Mizrahi, T., and A. J. Hacker,
"Deterministic Networking (DetNet) Security
Considerations", Work in Progress, Internet-Draft, draft-
ietf-detnet-security-16, 2 March 2021,
<https://datatracker.ietf.org/doc/html/draft-ietf-detnet-
security-16>.
[I-D.ietf-ippm-ioam-data] [I-D.ietf-ippm-ioam-data]
Brockners, F., Bhandari, S., and T. Mizrahi, "Data Fields Brockners, F., Bhandari, S., and T. Mizrahi, "Data Fields
for In-situ OAM", Work in Progress, Internet-Draft, draft- for In-situ OAM", Work in Progress, Internet-Draft, draft-
ietf-ippm-ioam-data-14, 24 June 2021, ietf-ippm-ioam-data-14, 24 June 2021,
<https://datatracker.ietf.org/doc/html/draft-ietf-ippm- <https://datatracker.ietf.org/doc/html/draft-ietf-ippm-
ioam-data-14>. ioam-data-14>.
[I-D.ietf-ippm-ioam-direct-export] [I-D.ietf-ippm-ioam-direct-export]
Song, H., Gafni, B., Zhou, T., Li, Z., Brockners, F., Song, H., Gafni, B., Zhou, T., Li, Z., Brockners, F.,
Bhandari, S., Sivakolundu, R., and T. Mizrahi, "In-situ Bhandari, S., Sivakolundu, R., and T. Mizrahi, "In-situ
skipping to change at page 15, line 10 skipping to change at page 15, line 10
L., Chen, M., Zheng, L., Mirsky, G., and T. Mizrahi, L., Chen, M., Zheng, L., Mirsky, G., and T. Mizrahi,
"Alternate-Marking Method for Passive and Hybrid "Alternate-Marking Method for Passive and Hybrid
Performance Monitoring", RFC 8321, DOI 10.17487/RFC8321, Performance Monitoring", RFC 8321, DOI 10.17487/RFC8321,
January 2018, <https://www.rfc-editor.org/info/rfc8321>. January 2018, <https://www.rfc-editor.org/info/rfc8321>.
[RFC8939] Varga, B., Ed., Farkas, J., Berger, L., Fedyk, D., and S. [RFC8939] Varga, B., Ed., Farkas, J., Berger, L., Fedyk, D., and S.
Bryant, "Deterministic Networking (DetNet) Data Plane: Bryant, "Deterministic Networking (DetNet) Data Plane:
IP", RFC 8939, DOI 10.17487/RFC8939, November 2020, IP", RFC 8939, DOI 10.17487/RFC8939, November 2020,
<https://www.rfc-editor.org/info/rfc8939>. <https://www.rfc-editor.org/info/rfc8939>.
[RFC9055] Grossman, E., Ed., Mizrahi, T., and A. Hacker,
"Deterministic Networking (DetNet) Security
Considerations", RFC 9055, DOI 10.17487/RFC9055, June
2021, <https://www.rfc-editor.org/info/rfc9055>.
Authors' Addresses Authors' Addresses
Greg Mirsky Greg Mirsky
ZTE Corp. ZTE Corp.
Email: gregimirsky@gmail.com, gregory.mirsky@ztetx.com Email: gregimirsky@gmail.com, gregory.mirsky@ztetx.com
Fabrice Theoleyre Fabrice Theoleyre
CNRS CNRS
300 boulevard Sebastien Brant - CS 10413 300 boulevard Sebastien Brant - CS 10413
 End of changes. 13 change blocks. 
22 lines changed or deleted 34 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/