draft-ietf-detnet-mpls-oam-02.txt   draft-ietf-detnet-mpls-oam-03.txt 
DetNet Working Group G. Mirsky DetNet Working Group G. Mirsky
Internet-Draft ZTE Corp. Internet-Draft ZTE Corp.
Intended status: Standards Track M. Chen Intended status: Standards Track M. Chen
Expires: July 19, 2021 Huawei Expires: 1 October 2021 Huawei
January 15, 2021 30 March 2021
Operations, Administration and Maintenance (OAM) for Deterministic Operations, Administration and Maintenance (OAM) for Deterministic
Networks (DetNet) with MPLS Data Plane Networks (DetNet) with MPLS Data Plane
draft-ietf-detnet-mpls-oam-02 draft-ietf-detnet-mpls-oam-03
Abstract Abstract
This document defines format and use principals of the Deterministic This document defines format and use principals of the Deterministic
Network (DetNet) service Associated Channel (ACH) over a DetNet Network (DetNet) service Associated Channel (ACH) over a DetNet
network with the MPLS data plane. The DetNet service ACH can be used network with the MPLS data plane. The DetNet service ACH can be used
to carry test packets of active Operations, Administration, and to carry test packets of active Operations, Administration, and
Maintenance protocols that are used to detect DetNet failures and Maintenance protocols that are used to detect DetNet failures and
measure performance metrics. measure performance metrics.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 July 19, 2021. This Internet-Draft will expire on 1 October 2021.
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 Provisions Relating to IETF Documents (https://trustee.ietf.org/
(https://trustee.ietf.org/license-info) in effect on the date of license-info) in effect on the date of publication of this document.
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document. Code Components
to this document. Code Components extracted from this document must extracted from this document must include Simplified BSD License text
include Simplified BSD License text as described in Section 4.e of as described in Section 4.e of the Trust Legal Provisions and are
the Trust Legal Provisions and are provided without warranty as 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 . . . . . . . . . . . . . . 2 2. Conventions used in this document . . . . . . . . . . . . . . 3
2.1. Terminology and Acronyms . . . . . . . . . . . . . . . . 3 2.1. Terminology and Acronyms . . . . . . . . . . . . . . . . 3
2.2. Keywords . . . . . . . . . . . . . . . . . . . . . . . . 4 2.2. Keywords . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Active OAM for DetNet Networks with MPLS Data Plane . . . . . 4 3. Active OAM for DetNet Networks with MPLS Data Plane . . . . . 4
3.1. DetNet Active OAM Encapsulation . . . . . . . . . . . . . 5 3.1. DetNet Active OAM Encapsulation . . . . . . . . . . . . . 5
3.2. DetNet Replication, Elimination, and Ordering Sub- 3.2. DetNet Replication, Elimination, and Ordering Sub-functions
functions Interaction with Active OAM . . . . . . . . . . 7 Interaction with Active OAM . . . . . . . . . . . . . . . 7
4. Use of Hybrid OAM in DetNet . . . . . . . . . . . . . . . . . 7 4. Use of Hybrid OAM in DetNet . . . . . . . . . . . . . . . . . 7
5. OAM Interworking Models . . . . . . . . . . . . . . . . . . . 7 5. OAM Interworking Models . . . . . . . . . . . . . . . . . . . 8
5.1. OAM of DetNet MPLS Interworking with OAM of TSN . . . . . 8 5.1. OAM of DetNet MPLS Interworking with OAM of TSN . . . . . 8
5.2. OAM of DetNet MPLS Interworking with OAM of DetNet IP . . 9 5.2. OAM of DetNet MPLS Interworking with OAM of DetNet IP . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
8. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 9 8. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 9
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
9.1. Normative References . . . . . . . . . . . . . . . . . . 9 9.1. Normative References . . . . . . . . . . . . . . . . . . 9
9.2. Informational References . . . . . . . . . . . . . . . . 10 9.2. Informational References . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
skipping to change at page 4, line 48 skipping to change at page 4, line 48
pseudowires (PW) over MPLS packet switched network, as described in pseudowires (PW) over MPLS packet switched network, as described in
[RFC3985], [RFC4385]. Generic PW MPLS Control Word (CW), defined in [RFC3985], [RFC4385]. Generic PW MPLS Control Word (CW), defined in
[RFC4385], for DetNet displayed in Figure 1. [RFC4385], for DetNet displayed in Figure 1.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0| Sequence Number | |0 0 0 0| Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: DetNet Control Word Format Figure 1: DetNet Control Word Format
PREF in the DetNet domain composed by a combination of nodes that PREF in the DetNet domain composed by a combination of nodes that
perform replication and elimination sub-functions. The elimination perform replication and elimination sub-functions. The elimination
sub-function always uses the S-Label and packet sequencing sub-function always uses the S-Label and packet sequencing
information, e.g., the value in the Sequence Number field of DetNet information, e.g., the value in the Sequence Number field of DetNet
CW (d-CW). The replication sub-function uses the S-Label information CW (d-CW). The replication sub-function uses the S-Label information
only. For data packets Figure 2 presents an example of PREF in only. For data packets Figure 2 presents an example of PREF in
DetNet domain. DetNet domain.
1111 11111111 111111 112212 112212 132213 1111 11111111 111111 112212 112212 132213
skipping to change at page 6, line 26 skipping to change at page 6, line 26
+---------------------------------+ <--+ +---------------------------------+ <--+
| UDP Header | | | UDP Header | |
+---------------------------------+ +--> DetNet data plane +---------------------------------+ +--> DetNet data plane
| IP Header | | IP encapsulation | IP Header | | IP encapsulation
+---------------------------------+ <--/ +---------------------------------+ <--/
| Data-Link | | Data-Link |
+---------------------------------+ +---------------------------------+
| Physical | | Physical |
+---------------------------------+ +---------------------------------+
Figure 4: DetNet Active OAM Packet Encapsulation in MPLS-over-UDP/IP Figure 4: DetNet Active OAM Packet Encapsulation in MPLS-over-UDP/IP
Figure 5 displays the format of the DetNet Associated Channel Header Figure 5 displays the format of the DetNet Associated Channel Header
(d-ACH). (d-ACH).
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 1|Version|Sequence Number| Channel Type | |0 0 0 1|Version|Sequence Number| Channel Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 8, line 39 skipping to change at page 8, line 49
inform the upstream DetNet MPLS node of a failure of the TSN segment. inform the upstream DetNet MPLS node of a failure of the TSN segment.
Performance monitoring can be supported by [RFC6374] in the DetNet Performance monitoring can be supported by [RFC6374] in the DetNet
MPLS and [ITU.Y1731] in the TSN domains, respectively. Performance MPLS and [ITU.Y1731] in the TSN domains, respectively. Performance
objectives for each domain should refer to metrics that additive or objectives for each domain should refer to metrics that additive or
be defined for each domain separately. be defined for each domain separately.
The following considerations are to be realized when using the The following considerations are to be realized when using the
tunneling model of OAM interworking between DetNet MPLS and TSN tunneling model of OAM interworking between DetNet MPLS and TSN
domains: domains:
o Active OAM test packet MUST be mapped to the same TSN Stream ID as * Active OAM test packet MUST be mapped to the same TSN Stream ID as
the monitored DetNet flow. the monitored DetNet flow.
o Active OAM test packets MUST be treated in the TSN domain based on * Active OAM test packets MUST be treated in the TSN domain based on
its S-label and CoS marking (TC field value). its S-label and CoS marking (TC field value).
Note that the tunneling model of the OAM interworking requires that Note that the tunneling model of the OAM interworking requires that
the remote peer of the E2E OAM domain supports the active OAM the remote peer of the E2E OAM domain supports the active OAM
protocol selected on the ingress endpoint. For example, if BFD is protocol selected on the ingress endpoint. For example, if BFD is
used for proactive path continuity monitoring in the DetNet MPLS used for proactive path continuity monitoring in the DetNet MPLS
domain, a TSN endpoint of the DetNet service has also support BFD as domain, a TSN endpoint of the DetNet service has also support BFD as
defined in [RFC5885]. defined in [RFC5885].
5.2. OAM of DetNet MPLS Interworking with OAM of DetNet IP 5.2. OAM of DetNet MPLS Interworking with OAM of DetNet IP
skipping to change at page 9, line 39 skipping to change at page 10, line 6
Authors extend their appreciation to Pascal Thubert for his Authors extend their appreciation to Pascal Thubert for his
insightful comments and productive discussion that helped to improve insightful comments and productive discussion that helped to improve
the document. the document.
9. References 9. References
9.1. Normative References 9.1. Normative References
[I-D.ietf-detnet-mpls] [I-D.ietf-detnet-mpls]
Varga, B., Farkas, J., Berger, L., Malis, A., Bryant, S., Varga, B., Farkas, J., Berger, L., Malis, A. G., Bryant,
and J. Korhonen, "DetNet Data Plane: MPLS", draft-ietf- S., and J. Korhonen, "Deterministic Networking (DetNet)
detnet-mpls-13 (work in progress), October 2020. Data Plane: MPLS", Work in Progress, Internet-Draft,
draft-ietf-detnet-mpls-13, 11 October 2020,
<https://tools.ietf.org/html/draft-ietf-detnet-mpls-13>.
[I-D.ietf-detnet-mpls-over-udp-ip] [I-D.ietf-detnet-mpls-over-udp-ip]
Varga, B., Farkas, J., Berger, L., Malis, A., and S. Varga, B., Farkas, J., Berger, L., Malis, A. G., and S.
Bryant, "DetNet Data Plane: MPLS over UDP/IP", draft-ietf- Bryant, "DetNet Data Plane: MPLS over UDP/IP", Work in
detnet-mpls-over-udp-ip-08 (work in progress), December Progress, Internet-Draft, draft-ietf-detnet-mpls-over-udp-
2020. ip-08, 14 December 2020, <https://tools.ietf.org/html/
draft-ietf-detnet-mpls-over-udp-ip-08>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC7023] Mohan, D., Ed., Bitar, N., Ed., Sajassi, A., Ed., DeLord, [RFC7023] Mohan, D., Ed., Bitar, N., Ed., Sajassi, A., Ed., DeLord,
S., Niger, P., and R. Qiu, "MPLS and Ethernet Operations, S., Niger, P., and R. Qiu, "MPLS and Ethernet Operations,
Administration, and Maintenance (OAM) Interworking", Administration, and Maintenance (OAM) Interworking",
RFC 7023, DOI 10.17487/RFC7023, October 2013, RFC 7023, DOI 10.17487/RFC7023, October 2013,
skipping to change at page 10, line 23 skipping to change at page 10, line 42
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 9.2. Informational References
[I-D.ietf-detnet-mpls-over-tsn] [I-D.ietf-detnet-mpls-over-tsn]
Varga, B., Farkas, J., Malis, A., and S. Bryant, "DetNet Varga, B., Farkas, J., Malis, A. G., and S. Bryant,
Data Plane: MPLS over IEEE 802.1 Time Sensitive Networking "DetNet Data Plane: MPLS over IEEE 802.1 Time-Sensitive
(TSN)", draft-ietf-detnet-mpls-over-tsn-05 (work in Networking (TSN)", Work in Progress, Internet-Draft,
progress), December 2020. draft-ietf-detnet-mpls-over-tsn-07, 19 February 2021,
<https://tools.ietf.org/html/draft-ietf-detnet-mpls-over-
tsn-07>.
[I-D.ietf-detnet-security] [I-D.ietf-detnet-security]
Grossman, E., Mizrahi, T., and A. Hacker, "Deterministic Grossman, E., Mizrahi, T., and A. J. Hacker,
Networking (DetNet) Security Considerations", draft-ietf- "Deterministic Networking (DetNet) Security
detnet-security-13 (work in progress), December 2020. Considerations", Work in Progress, Internet-Draft, draft-
ietf-detnet-security-16, 2 March 2021,
<https://tools.ietf.org/html/draft-ietf-detnet-security-
16>.
[I-D.ietf-ippm-stamp-option-tlv] [I-D.ietf-ippm-stamp-option-tlv]
Mirsky, G., Min, X., Nydell, H., Foote, R., Masputra, A., Mirsky, G., Min, X., Nydell, H., Foote, R., Masputra, A.,
and E. Ruffini, "Simple Two-way Active Measurement and E. Ruffini, "Simple Two-Way Active Measurement
Protocol Optional Extensions", draft-ietf-ippm-stamp- Protocol Optional Extensions", Work in Progress, Internet-
option-tlv-10 (work in progress), November 2020. Draft, draft-ietf-ippm-stamp-option-tlv-10, 15 November
2020, <https://tools.ietf.org/html/draft-ietf-ippm-stamp-
option-tlv-10>.
[I-D.tpmb-detnet-oam-framework] [I-D.tpmb-detnet-oam-framework]
Mirsky, G., Theoleyre, F., Papadopoulos, G., and C. Mirsky, G., Theoleyre, F., Papadopoulos, G. Z., and C. J.
Bernardos, "Framework of Operations, Administration and Bernardos, "Framework of Operations, Administration and
Maintenance (OAM) for Deterministic Networking (DetNet)", Maintenance (OAM) for Deterministic Networking (DetNet)",
draft-tpmb-detnet-oam-framework-00 (work in progress), Work in Progress, Internet-Draft, draft-tpmb-detnet-oam-
January 2021. framework-00, 15 January 2021,
<https://tools.ietf.org/html/draft-tpmb-detnet-oam-
framework-00>.
[IEEE.CFM] [IEEE.CFM] IEEE, "Connectivity Fault Management clause of IEEE
IEEE, "Connectivity Fault Management clause of IEEE
802.1Q", IEEE 802.1Q, 2013. 802.1Q", IEEE 802.1Q, 2013.
[ITU.Y1731] [ITU.Y1731]
ITU-T, "OAM functions and mechanisms for Ethernet based ITU-T, "OAM functions and mechanisms for Ethernet based
Networks", ITU-T Recommendation G.8013/Y.1731, November Networks", ITU-T Recommendation G.8013/Y.1731, November
2013. 2013.
[RFC3985] Bryant, S., Ed. and P. Pate, Ed., "Pseudo Wire Emulation [RFC3985] Bryant, S., Ed. and P. Pate, Ed., "Pseudo Wire Emulation
Edge-to-Edge (PWE3) Architecture", RFC 3985, Edge-to-Edge (PWE3) Architecture", RFC 3985,
DOI 10.17487/RFC3985, March 2005, DOI 10.17487/RFC3985, March 2005,
skipping to change at page 12, line 21 skipping to change at page 12, line 42
[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.
Email: gregimirsky@gmail.com Email: gregimirsky@gmail.com, gregory.mirsky@ztetx.com
Mach(Guoyi) Chen Mach(Guoyi) Chen
Huawei Huawei
Email: mach.chen@huawei.com Email: mach.chen@huawei.com
 End of changes. 21 change blocks. 
44 lines changed or deleted 54 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/