rfc9546.original.xml   rfc9546.xml 
<?xml version="1.0" encoding="utf-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!-- pre-edited by ST 01/30/24 -->
<!DOCTYPE rfc [ <!DOCTYPE rfc [
<!ENTITY nbsp "&#160;"> <!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;"> <!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;"> <!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;"> <!ENTITY wj "&#8288;">
]> ]>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std" ipr="trust200902"
docName="draft-ietf-detnet-mpls-oam-15" obsoletes="" updates="" submissionType=
"IETF" xml:lang="en" tocInclude="true" tocDepth="3" symRefs="true" sortRefs="tru
e" version="3">
<!-- xml2rfc v2v3 conversion 3.6.0 -->
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<front> <rfc xmlns:xi="http://www.w3.org/2001/XInclude"
<title abbrev="OAM for DetNet over MPLS">Operations, Administration and Main category="std"
tenance (OAM) for Deterministic Networks (DetNet) with MPLS Data Plane</title> ipr="trust200902"
<seriesInfo name="Internet-Draft" value="draft-ietf-detnet-mpls-oam-15"/> docName="draft-ietf-detnet-mpls-oam-15"
number="9546"
obsoletes=""
updates=""
submissionType="IETF"
xml:lang="en"
consensus="true"
tocInclude="true"
tocDepth="3"
symRefs="true"
sortRefs="true"
version="3">
<front>
<title abbrev="OAM for DetNet over MPLS">Operations, Administration, and Mai
ntenance (OAM) for Deterministic Networking (DetNet) with the MPLS Data Plane</t
itle>
<seriesInfo name="RFC" value="9546"/>
<author initials="G." surname="Mirsky" fullname="Greg Mirsky"> <author initials="G." surname="Mirsky" fullname="Greg Mirsky">
<organization>Ericsson</organization> <organization>Ericsson</organization>
<address> <address>
<email>gregimirsky@gmail.com</email> <email>gregimirsky@gmail.com</email>
</address> </address>
</author> </author>
<author fullname="Mach(Guoyi) Chen" initials="M." surname="Chen"> <author fullname="Mach(Guoyi) Chen" initials="M." surname="Chen">
<organization>Huawei</organization> <organization>Huawei</organization>
<address> <address>
<postal>
<street/>
<city/>
<code/>
<country/>
</postal>
<email>mach.chen@huawei.com</email> <email>mach.chen@huawei.com</email>
</address> </address>
</author> </author>
<author fullname="Balazs Varga" initials="B." surname="Varga"> <author fullname="Balazs Varga" initials="B." surname="Varga">
<organization>Ericsson</organization> <organization>Ericsson</organization>
<address> <address>
<postal> <postal>
<street>Magyar Tudosok krt. 11.</street> <street>Magyar Tudosok krt. 11.</street>
<city>Budapest</city> <city>Budapest</city>
<country>Hungary</country> <country>Hungary</country>
<code>1117</code> <code>1117</code>
</postal> </postal>
<email>balazs.a.varga@ericsson.com</email> <email>balazs.a.varga@ericsson.com</email>
</address> </address>
</author> </author>
<!-- <date month="February" year="2024"/>
<author fullname="Janos Farkas" initials="J." surname="Farkas">
<organization>Ericsson</organization> <area>RTG</area>
<address> <workgroup>detnet</workgroup>
<postal>
<street>Magyar Tudosok krt. 11.</street>
<city>Budapest</city>
<country>Hungary</country>
<code>1117</code>
</postal>
<email>janos.farkas@ericsson.com</email>
</address>
</author>
-->
<date year="2024"/>
<area>Routing</area>
<workgroup>DetNet Working Group</workgroup>
<keyword>Internet-Draft</keyword>
<keyword>DetNet</keyword> <keyword>DetNet</keyword>
<keyword>OAM</keyword> <keyword>OAM</keyword>
<abstract> <abstract>
<t> <t>
This document defines format and usage principles of the This document defines format and usage principles of the
Deterministic Network (DetNet) service Associated Channel over a DetNe t network with the MPLS data plane. Deterministic Networking (DetNet) service Associated Channel over a De tNet network with the MPLS data plane.
The DetNet service Associated Channel can be used to carry test packet s of active The DetNet service Associated Channel can be used to carry test packet s of active
Operations, Administration, and Maintenance protocols Operations, Administration, and Maintenance (OAM) protocols
that are used to detect DetNet failures and measure performance metric s. that are used to detect DetNet failures and measure performance metric s.
</t> </t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section anchor="intro" numbered="true" toc="default"> <section anchor="intro" numbered="true" toc="default">
<name>Introduction</name> <name>Introduction</name>
<t> <t>
<xref target="RFC8655" format="default"/> introduces and explains Determinist <xref target="RFC8655" format="default"/> introduces and explains Determinist
ic Networks (DetNet) ic Networking (DetNet)
architecture and how the Packet Replication, Elimination, and Ordering functi architecture and how the Packet Replication, Elimination, and Ordering Functi
ons (PREOF) can be used to ons (PREOF) can be used to
ensure a low packet drop ratio in a DetNet domain. ensure a low packet drop ratio in a DetNet domain.
</t> </t>
<t> <t>
Operations, Administration, and Maintenance (OAM) protocols are used to d etect and localize network defects, Operations, Administration, and Maintenance (OAM) protocols are used to d etect and localize network defects
and to monitor network performance. Some OAM functions (e.g., failure det ection) are usually performed proactively and to monitor network performance. Some OAM functions (e.g., failure det ection) are usually performed proactively
in the network, while others (e.g., defect localization) are typically pe rformed on demand. in the network, while others (e.g., defect localization) are typically pe rformed on demand.
These tasks can be achieved through a combination of active and hybrid These tasks can be achieved through a combination of active and hybrid
OAM methods, as classified in <xref target="RFC7799" format="default"/>. OAM methods, as classified in <xref target="RFC7799" format="default"/>.
This document presents a format for active OAM in DetNet networks with MP LS data plane. This document presents a format for active OAM in DetNet networks with th e MPLS data plane.
</t> </t>
<t> <t>
Also, this document defines format and usage principles of the Also, this document defines format and usage principles of the
DetNet service Associated Channel over a DetNet network with DetNet service Associated Channel over a DetNet network with
the MPLS data plane <xref target="RFC8964" format="default"/>. the MPLS data plane <xref target="RFC8964" format="default"/>.
</t> </t>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Conventions used in this document</name> <name>Conventions Used in This Document</name>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Terminology and Acronyms</name> <name>Terminology and Acronyms</name>
<t> <t>
The term "DetNet OAM" is used in this document interchangeably with longer versi The term "DetNet OAM" in this document is used interchangeably with a "set of OA
on M protocols, methods, and tools for Deterministic Networking".
"set of OAM protocols, methods and tools for Deterministic Networks". </t>
</t> <dl spacing="normal">
<t>DetNet Deterministic Network</t> <dt>BFD:</dt><dd>Bidirectional Forwarding Detection</dd>
<t>d-ACH DetNet Associated Channel Header</t> <dt>CFM:</dt><dd>Connectivity Fault Management</dd>
<t>OAM Operations, Administration, and Maintenance</t> <dt>d-ACH:</dt><dd>DetNet Associated Channel Header</dd>
<t>PREOF Packet Replication, Elimination, and Ordering Functions</t> <dt>DetNet:</dt><dd>Deterministic Networking</dd>
<t>PW Pseudowire</t> <dt>DetNet Node:</dt><dd>A node that is an actor in the DetNet domain.
<t>E2E End-to-end</t> Examples of DetNet nodes include DetNet domain edge nodes
<t>BFD Bidirectional Forwarding Detection</t> and DetNet nodes that perform PREOF within the DetNet domain.</dd>
<t>TSN IEEE 802.1 Time-Sensitive Networking</t> <dt>E2E:</dt><dd>End to end</dd>
<t>CFM Connectivity Fault Management</t> <dt>F-Label:</dt><dd>A DetNet "forwarding" label. The F-Label identifies
<t>F-Label - a DetNet "forwarding" label. The F-Label identifies the LSP the Label Switched Path (LSP)
used to forward a DetNet flow across an MPLS PSN, e.g., used to forward a DetNet flow across an MPLS Packet Switched Ne
a hop-by-hop label used between label switching routers.</t> twork (PSN), e.g.,
<t>S-Label - a DetNet "service" label. An S-Label is used between DetNet a hop-by-hop label used between label switching routers.</dd>
<dt>OAM:</dt><dd>Operations, Administration, and Maintenance</dd>
<dt>PREOF:</dt><dd>Packet Replication, Elimination, and Ordering Functio
ns</dd>
<dt>PW:</dt><dd>Pseudowire</dd>
<dt>S-Label:</dt><dd>A DetNet "service" label. An S-Label is used betwee
n DetNet
nodes that implement the DetNet service sub-layer nodes that implement the DetNet service sub-layer
functions. An S-Label is also used to identify a functions. An S-Label is also used to identify a
DetNet flow at DetNet service sub-layer.</t> DetNet flow at the DetNet service sub-layer.</dd>
<t> Underlay Network or Underlay Layer - the network that provides <dt>TSN:</dt><dd>Time-Sensitive Networking</dd>
<dt>Underlay Network or Underlay Layer:</dt><dd>The network that provide
s
connectivity between the DetNet nodes. One example of an underlay connectivity between the DetNet nodes. One example of an underlay
layer is an MPLS network that provides Label Switched Path (LSP) connectivity layer is an MPLS network that provides LSP connectivity between DetNet nodes.
between DetNet nodes.</t> </dd>
<t>DetNet Node - a node that is an actor in the DetNet domain. </dl>
Examples of DetNet nodes include DetNet domain Edge nodes,
and DetNet nodes that perform PREOF within the DetNet domain.</t>
</section> </section>
<section numbered="true" toc="default"> <section numbered="true" toc="default">
<name>Keywords</name> <name>Key Words</name>
<t> <t>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>
"MAY", and "OPTIONAL" in this document are to be interpreted as ",
described in BCP 14 <xref target="RFC2119" format="default"/> <xref target="R "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
FC8174" format="default"/> "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
when, and only when, they appear in all capitals, as shown here. "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to
be
interpreted as described in BCP&nbsp;14 <xref target="RFC2119"/> <xref
target="RFC8174"/> when, and only when, they appear in all capitals, as
shown here.
</t> </t>
</section> </section>
</section> </section>
<section anchor="oam-data-plane" numbered="true" toc="default"> <section anchor="oam-data-plane" numbered="true" toc="default">
<name>Active OAM for DetNet Networks with MPLS Data Plane</name> <name>Active OAM for DetNet Networks with the MPLS Data Plane</name>
<t> <t>
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, thus it is critical that the data particular networking layer; thus, it is critical that the data
plane encapsulation supports OAM mechanisms that comply plane encapsulation supports OAM mechanisms that comply
with the OAM requirements listed in <xref target="I-D.ietf-detnet-oam-framework" format="default"/>. with the OAM requirements listed in <xref target="I-D.ietf-detnet-oam-framework" format="default"/>.
</t> </t>
<!-- One such example that requires special consideration is requirement #5:
</t>
<ul empty="true" spacing="normal">
<li>
DetNet OAM packets MUST be in-band, i.e., follow precisely the same
path as DetNet data plane traffic both for unidirectional and bi-directional D
etNet paths.
</li>
</ul> -->
<t> <t>
Operation of a DetNet data plane with an MPLS underlay network is specified in < xref target="RFC8964"/>. Operation of a DetNet data plane with an MPLS underlay network is specified in < xref target="RFC8964"/>.
Within the MPLS underlay network, DetNet flows are to be encapsulated analogous Within the MPLS underlay network, DetNet flows are to be encapsulated analogous
to pseudowires to pseudowires (PWs)
as specified in <xref target="RFC3985"/>, <xref target="RFC4385"/>. For referenc as specified in <xref target="RFC3985"/> and <xref target="RFC4385"/>. For refer
e, ence,
the Generic Pseudowire (PW) MPLS Control Word (as defined in <xref target="RFC4 the Generic PW MPLS Control Word (as defined in <xref target="RFC4385"/> and use
385"/> and used with DetNet) d with DetNet)
is reproduced in <xref target="detnet-pw-cw"/>. is reproduced in <xref target="detnet-pw-cw"/>.
</t> </t>
<figure anchor="detnet-pw-cw"> <figure anchor="detnet-pw-cw">
<name>DetNet Control Word Format</name> <name>Generic PW MPLS Control Word Format</name>
<artwork name="" type="" align="left" alt=""><![CDATA[ <artwork name="" type="" align="left" alt=""><![CDATA[
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork> ]]></artwork>
</figure> </figure>
<t> <t>
PREOF in the DetNet domain is composed of a combination of nodes that perform re plication and elimination functions. PREOF in the DetNet domain is composed of a combination of nodes that perform re plication and elimination functions.
The Elimination sub-function always uses the S-Label in conjunction with the pac ket sequencing information The Elimination sub-function always uses the S-Label in conjunction with the pac ket sequencing information
(i.e., the Sequence Number encoded in the DetNet Control Word). The Replication sub-function uses the S-Label information only. (i.e., the Sequence Number encoded in the DetNet Control Word). The Replication sub-function uses the S-Label information only.
</t> </t>
<section anchor="active-oam-data-plane" numbered="true" toc="default"> <section anchor="active-oam-data-plane" numbered="true" toc="default">
<name>DetNet Active OAM Encapsulation</name> <name>DetNet Active OAM Encapsulation</name>
<t> <t>
DetNet OAM, like PW OAM, uses the PW Associated Channel Header defined in <xref target="RFC4385"/>. DetNet OAM, like PW OAM, uses the PW Associated Channel Header defined in <xref target="RFC4385"/>.
At the same time, a DetNet PW can be viewed as a Multi-Segment PW, where DetNet service At the same time, a DetNet PW can be viewed as a Multi-Segment PW, where DetNet service
sub-layer functions are at the segment endpoints. However, DetNet service sub-la yer functions operate per packet level (not per segment). sub-layer functions are at the segment endpoints. However, DetNet service sub-la yer functions operate per packet level (not per segment).
These per-packet level characteristics of PREOF require additional fields for pr These per-packet level characteristics of PREOF require additional fields for pr
oper OAM packet processing. oper OAM packet processing. MPLS encapsulation <xref target="RFC8964"/> of a Det
Encapsulation of a DetNet MPLS <xref target="RFC8964"/> active OAM packet is sho Net active OAM packet is shown in <xref target="detnet-mpls-oam-format"/>.
wn in <xref target="detnet-mpls-oam-format"/>.
</t> </t>
<figure anchor="detnet-mpls-oam-format"> <figure anchor="detnet-mpls-oam-format">
<name>DetNet Active OAM Packet Encapsulation in MPLS Data Plane</name> <name>DetNet Active OAM Packet Encapsulation in the MPLS Data Plane</n
<artwork name="" type="" align="left" alt=""><![CDATA[ ame>
<artwork name="" type="" align="left" alt=""><![CDATA[
+---------------------------------+ +---------------------------------+
| | | |
| DetNet OAM Packet | | DetNet OAM Packet |
| | | |
+---------------------------------+ <--\ +---------------------------------+ <--\
| DetNet Associated Channel Header| | | DetNet Associated Channel Header| |
+---------------------------------+ +--> DetNet active OAM +---------------------------------+ +--> DetNet active OAM
| S-Label | | MPLS encapsulation | S-Label | | MPLS encapsulation
+---------------------------------+ | +---------------------------------+ |
| [ F-Label(s) ] | | | [ F-Label(s) ] | |
skipping to change at line 212 skipping to change at line 202
| DetNet Associated Channel Header| | | DetNet Associated Channel Header| |
+---------------------------------+ +--> DetNet active OAM +---------------------------------+ +--> DetNet active OAM
| S-Label | | MPLS encapsulation | S-Label | | MPLS encapsulation
+---------------------------------+ | +---------------------------------+ |
| [ F-Label(s) ] | | | [ F-Label(s) ] | |
+---------------------------------+ <--/ +---------------------------------+ <--/
| Data-Link | | Data-Link |
+---------------------------------+ +---------------------------------+
| Physical | | Physical |
+---------------------------------+ +---------------------------------+
]]></artwork> ]]></artwork>
</figure> </figure>
<t> <t>
<xref target="detnet-mpls-oam-over-ip-format" format="default"/> displays en <xref target="detnet-mpls-oam-over-ip-format" format="default"/> displays en
capsulation of a test packet of an active DetNet OAM protocol capsulation of a test packet for a DetNet active OAM protocol in case of MPLS ov
in case of MPLS-over-UDP/IP <xref target="RFC9025" format="default"/>. er UDP/IP <xref target="RFC9025" format="default"/>.
</t> </t>
<figure anchor="detnet-mpls-oam-over-ip-format"> <figure anchor="detnet-mpls-oam-over-ip-format">
<name>DetNet Active OAM Packet Encapsulation in MPLS-over-UDP/IP</name <name>DetNet Active OAM Packet Encapsulation in MPLS over UDP/IP</name
> >
<artwork name="" type="" align="left" alt=""><![CDATA[ <artwork name="" type="" align="left" alt=""><![CDATA[
+---------------------------------+ +---------------------------------+
| | | |
| DetNet OAM Packet | | DetNet OAM Packet |
| | | |
+---------------------------------+ <--\ +---------------------------------+ <--\
| DetNet Associated Channel Header| | | DetNet Associated Channel Header| |
+---------------------------------+ +--> DetNet active OAM +---------------------------------+ +--> DetNet active OAM
| S-Label | | MPLS encapsulation | S-Label | | MPLS encapsulation
+---------------------------------+ | +---------------------------------+ |
| [ F-label(s) ] | | | [ F-label(s) ] | |
skipping to change at line 241 skipping to change at line 229
| [ F-label(s) ] | | | [ F-label(s) ] | |
+---------------------------------+ <--+ +---------------------------------+ <--+
| UDP Header | | | UDP Header | |
+---------------------------------+ +--> DetNet data plane +---------------------------------+ +--> DetNet data plane
| IP Header | | IP encapsulation | IP Header | | IP encapsulation
+---------------------------------+ <--/ +---------------------------------+ <--/
| Data-Link | | Data-Link |
+---------------------------------+ +---------------------------------+
| Physical | | Physical |
+---------------------------------+ +---------------------------------+
]]></artwork> ]]></artwork>
</figure> </figure>
<t> <t>
<xref target="detnet-ach-oam" format="default"/> displays the format of the D etNet Associated Channel Header (d-ACH). <xref target="detnet-ach-oam" format="default"/> displays the format of the D etNet Associated Channel Header (d-ACH).
</t> </t>
<figure anchor="detnet-ach-oam"> <figure anchor="detnet-ach-oam">
<name>d-ACH Format</name> <name>d-ACH Format</name>
<artwork name="" type="" align="left" alt=""><![CDATA[ <artwork name="" type="" align="left" alt=""><![CDATA[
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Node ID |Level| Flags |Session| | Node ID |Level| Flags |Session|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork> ]]></artwork>
</figure> </figure>
<t> <dl newline="true" spacing="normal">
The d-ACH encodes the following fields: <dt>The d-ACH encodes the following fields:</dt>
</t> <dd><dl newline="false">
<ul empty="true" spacing="normal"> <dt>Bits 0..3:</dt><dd>These <bcp14>MUST</bcp14> be 0b0001. This allows the
<li> packet to be distinguished
Bits 0..3 MUST be 0b0001. This allows the packet to be distinguished
from an IP packet <xref target="RFC4928"/> and from a DetNet data packet <xref t arget="RFC8964"/>. from an IP packet <xref target="RFC4928"/> and from a DetNet data packet <xref t arget="RFC8964"/>.
</li> </dd>
<li> <dt>Version:</dt><dd>A 4-bit field. This document specifies version 0.
Version - a 4-bit field. This document specifies version 0. </dd>
</li> <dt>Sequence Number:</dt><dd>An unsigned circular 8-bit field. Because
<li> a DetNet active OAM test packet includes d-ACH, <xref target="RFC8964" sectionFo
Sequence Number - is an unsigned circular 8-bit field. Because rmat="of" section="4.2.1"/>
a test packet of DetNet active OAM includes d-ACH, Section 4.2.1 of <xref target
="RFC8964"/>
does not apply to handling the Sequence Number field in DetNet OAM over the MPLS data plane. does not apply to handling the Sequence Number field in DetNet OAM over the MPLS data plane.
The sequence number space is circular with no restriction on the The sequence number space is circular with no restriction on the
initial value. The originator DetNet node MUST set the value of initial value. The originator DetNet node <bcp14>MUST</bcp14> set the valu e of
the Sequence Number field before the transmission of a packet. the Sequence Number field before the transmission of a packet.
the initial value SHOULD be random (unpredictable). The initial value <bcp14>SHOULD</bcp14> be random (unpredictable).
The originator node SHOULD increase the value of the Sequence Number The originator node <bcp14>SHOULD</bcp14> increase the value of the Sequen
ce Number
field by 1 for each active OAM packet. field by 1 for each active OAM packet.
The originator MAY use other strategies, e.g., for negative testing of Pac The originator <bcp14>MAY</bcp14> use other strategies, e.g., for negative
ket Ordering Functions. testing of Packet Ordering Functions.
</li> </dd>
<li> <dt>Channel Type:</dt><dd>A 16-bit field and the value of the DetNet Associa
Channel Type - is a 16-bit field, and the value of DetNet Associated Channel Typ ted Channel Type.
e. It <bcp14>MUST</bcp14> be one of the values listed in the IANA "MPLS Generalized
It MUST be one of the values listed in the IANA MPLS Generalized Associated Associated
Channel Types (including Pseudowire Associated Channel Types) registry <xref tar Channel (G-ACh) Types (including Pseudowire Associated Channel Types)" registry
get="IANA-G-ACh-Types"/>. <xref target="IANA-G-ACh-Types"/>.
</li> </dd>
<li> <dt>Node ID:</dt><dd>An unsigned 20-bit field.
Node ID - is an unsigned 20-bit field.
The value of the Node ID field identifies the DetNet node that originated the pa cket. The value of the Node ID field identifies the DetNet node that originated the pa cket.
A DetNet node MUST be provisioned with a Node ID that is unique in the DetNet do A DetNet node <bcp14>MUST</bcp14> be provisioned with a Node ID that is unique i
main. n the DetNet domain.
Methods of distributing Node ID are outside the scope of this specification. Methods for distributing Node ID are outside the scope of this specification.
</li> </dd>
<li>Level - is a 3-bit field. Semantically, the Level field is anlogous to the M <dt>Level:</dt><dd>A 3-bit field. Semantically, the Level field is analogous to
aintenance Domain Level in <xref target="IEEE.802.1Q"/>. the Maintenance Domain Level in <xref target="IEEE.802.1Q"/>.
The Level field is used to cope with the "all active path forwarding" (defined b y the TSN Task Group of the IEEE 802.1 WG <xref target="IEEE802.1TSNTG"/>) The Level field is used to cope with the "all active path forwarding" (defined b y the TSN Task Group of the IEEE 802.1 WG <xref target="IEEE802.1TSNTG"/>)
characteristics of the PREOF concept. A hierarchical relationship between OAM do mains characteristics of the PREOF concept. A hierarchical relationship between OAM do mains
can be created using the Level field value, illustrated by Figure 18.7 in <xref can be created using the Level field value, as illustrated by Figure 18.7 in <xr
target="IEEE.802.1Q"/>.</li> ef target="IEEE.802.1Q"/>.</dd>
<li> <dt>Flags:</dt><dd>A 5-bit field. The Flags field contains five 1-bit flags. <xr
Flags - is a 5-bit field. The Flags field contains five 1-bit flags. <xref targe ef target="iana-mpls-oam-flags"/>
t="iana-mpls-oam-flags"/> creates the IANA "DetNet Associated Channel Header (d-ACH) Flags" registry for n
creates the IANA d-ACH Flags registry for new flags to be defined. ew flags to be defined.
The flags defined in this specification are presented in <xref target="dach-flag The flags defined in this specification are presented in <xref target="dach-flag
s-fig"/>. s-fig"/>.</dd>
</li> <dt>Session ID:</dt><dd><t>A 4-bit field. The Session field distinguishes OAM se
</ul> ssions originating from the same node
(a given Maintenance End Point may have multiple simultaneously active OAM sessi
<figure anchor="dach-flags-fig"> ons) at the given Level.
</t>
<figure anchor="dach-flags-fig">
<name>DetNet Associated Channel Header Flags Field Format</name> <name>DetNet Associated Channel Header Flags Field Format</name>
<artwork name="" type="" align="left" alt=""><![CDATA[ <artwork name="" type="" align="left" alt=""><![CDATA[
0 1 2 3 4 0 1 2 3 4
+-+-+-+-+-+ +-+-+-+-+-+
|U|U|U|U|U| |U|U|U|U|U|
+-+-+-+-+-+ +-+-+-+-+-+
]]></artwork> ]]></artwork>
-+-+-+-+-+
</figure> </figure>
<t> U: Unused and for future use. MUST be 0 on transmission and ignored on rece </dd>
ipt.</t> </dl>
<ul empty="true" spacing="normal"> </dd>
<li>Session ID is a 4-bit field. The Session field distinguishes OAM sessions or </dl>
iginating from the same node <dl spacing="normal">
(a given Maintenance End Point may have multiple simultaneously active OAM sessi <dt>U:</dt><dd>Unused and for future use. <bcp14>MUST</bcp14> be 0 on transmiss
ons) at the given Level.</li> ion and ignored on receipt.
</ul> </dd></dl>
<t> <t>
A DetNet flow, according to <xref target="RFC8964" format="default"/>, is identi According to <xref target="RFC8964" format="default"/>, a DetNet flow is identif
fied by the S-Label that MUST be at the bottom ied by the S-Label that <bcp14>MUST</bcp14> be at the bottom
of the stack. An Active OAM packet MUST include d-ACH immediately following the of the stack. An active OAM packet <bcp14>MUST</bcp14> include d-ACH immediately
S-Label. following the S-Label.
</t> </t>
</section> </section>
<section anchor="oam-preof-sec" numbered="true" toc="default"> <section anchor="oam-preof-sec" numbered="true" toc="default">
<name>DetNet Packet Replication, Elimination, and Ordering Functions Int eraction with Active OAM</name> <name>DetNet PREOF Interaction with Active OAM</name>
<t> <t>
At the DetNet service sub-layer, special functions (notably PREOF) MAY be applie d to the particular At the DetNet service sub-layer, special functions (notably PREOF) <bcp14>MAY</b cp14> be applied to the particular
DetNet flow to potentially reduce packet loss, improve the probability of on-tim e packet delivery, DetNet flow to potentially reduce packet loss, improve the probability of on-tim e packet delivery,
and ensure in-order packet delivery. PREOF relies on sequencing information in t he and ensure in-order packet delivery. PREOF relies on sequencing information in t he
DetNet service sub-layer. For a DetNet active OAM packet, PREOF MUST DetNet service sub-layer. For a DetNet active OAM packet, PREOF <bcp14>MUST</bcp 14>
use the Sequence Number field value as the source of this sequencing information . use the Sequence Number field value as the source of this sequencing information .
App-flow and OAM use different sequence number spaces. PREOF algorithms App-flow and OAM use different sequence number spaces. PREOF algorithms
are executed with respect to the sequence number space identified by the flow's characteristic information. are executed with respect to the sequence number space identified by the flow's characteristic information.
Although the Sequence Number field in d-ACH has a range from 0 through 255, it p rovides sufficient space because Although the Sequence Number field in d-ACH has a range from 0 through 255, it p rovides sufficient space because
the rate of DetNet active OAM packet is significantly lower compared to the rate of DetNet packets the rate of DetNet active OAM packets is significantly lower compared to the rat e of DetNet packets
in an App-flow; therefore, wrapping around is not an issue. in an App-flow; therefore, wrapping around is not an issue.
</t> </t>
</section> </section>
</section> </section>
<!--
<section anchor="hybrid-oam" numbered="true" toc="default">
<name>Use of Hybrid OAM in DetNet</name>
<t>Hybrid OAM methods are used in performance monitoring; they are defined
in <xref target="RFC7799"/> as:
</t>
<ul empty="true" spacing="normal">
<li>Hybrid Methods are Methods of Measurement that use a combination of
Active Methods and Passive Methods.</li>
</ul>
<t>
A hybrid measurement method may produce metrics with results that are close t
o the results of passive measurement,
but it inevitably alters something in a data packet even if it is only the va
lue of a designated field in the packet encapsulation.
One example of such a hybrid measurement method is the Alternate Marking meth
od described in <xref target="RFC8321"/>.
Reserving a field in the DetNet Header for Alternate Marking can be useful in pr
oviding additional options to the operator-provided set of DetNet OAM tools.
</t>
</section>
-->
<section anchor="oam-interworking-sec" numbered="true" toc="default"> <section anchor="oam-interworking-sec" numbered="true" toc="default">
<name>OAM Interworking Models</name> <name>OAM Interworking Models</name>
<t> <t>
Interworking of two OAM domains that utilize different networking technology can be realized either by a peering or a tunneling model. Interworking of two OAM domains that utilize different networking technology can be realized by either a peering model or a tunneling model.
In a peering model, OAM domains are within the corresponding network domain. In a peering model, OAM domains are within the corresponding network domain.
When using the peering model, state changes that are detected by a Fault Managem ent OAM protocol When using the peering model, state changes that are detected by a Fault Managem ent OAM protocol
can be mapped from one OAM domain into another or a notification, e.g., an alarm can be mapped from one OAM domain into another or a notification, e.g., an alarm
, can be sent to a central controller. can be sent to a central controller.
In the tunneling model of OAM interworking, usually, only one active OAM protoco In the tunneling model of OAM interworking, usually only one active OAM protocol
l is used. Its test packets is used. Its test packets
are tunneled through another domain along with the data flow, thus ensuring the are tunneled through another domain along with the data flow, thus ensuring fate
fate sharing among test and data packets. sharing among test and data packets.
</t> </t>
<section anchor="ip-over-tsn-sec" numbered="true" toc="default"> <section anchor="ip-over-tsn-sec" numbered="true" toc="default">
<name>OAM of DetNet MPLS Interworking with OAM of TSN</name> <name>OAM of DetNet MPLS Interworking with OAM of TSN</name>
<t> <t>
Active DetNet OAM can provide the end-to-end (E2E) fault management and performa nce monitoring for DetNet active OAM can provide end-to-end (E2E) fault management and performance monitoring for
a DetNet flow. In the case of DetNet with an MPLS data plane and an IEEE 802.1 T ime-Sensitive Networking (TSN) <!--<xref target=""/>--> sub-network, a DetNet flow. In the case of DetNet with an MPLS data plane and an IEEE 802.1 T ime-Sensitive Networking (TSN) <!--<xref target=""/>--> sub-network,
this implies the interworking of DetNet active OAM with TSN OAM, which data plan e aspects are specified in <xref target="RFC9037"/>. it implies the interworking of DetNet active OAM with TSN OAM, of which the data plane aspects are specified in <xref target="RFC9037"/>.
</t> </t>
<t> <t>
When the peering model (<xref target="oam-interworking-sec"/>) is used in When the peering model (<xref target="oam-interworking-sec"/>) is used in the
Connectivity Fault Management (CFM) OAM protocol <xref target="IEEE.802.1Q"/> , Connectivity Fault Management (CFM) OAM protocol <xref target="IEEE.802.1Q"/> ,
then the node that borders both TSN and DetNet MPLS domains MUST the node that borders both TSN and DetNet MPLS domains <bcp14>MUST</bcp14>
support <xref target="RFC7023" format="default"/>. support <xref target="RFC7023" format="default"/>.
<xref target="RFC7023" format="default"/> specifies the mapping of defect sta tes <xref target="RFC7023" format="default"/> specifies the mapping of defect sta tes
between Ethernet Attachment Circuits and associated Ethernet between Ethernet Attachment Circuits and associated Ethernet
PWs that are part of an E2E emulated Ethernet service, and are also applicabl PWs that are part of an E2E emulated Ethernet service and are also applicable
e to E2E OAM across DetNet MPLS and TSN domains. to E2E OAM across DetNet MPLS and TSN domains.
The CFM <xref target="IEEE.802.1Q"/> or The CFM <xref target="IEEE.802.1Q"/> <xref target="ITU.Y1731"/> can provide f
in <xref target="ITU.Y1731"/> can provide fast detection of a failure in the ast detection of a failure in the TSN segment of the DetNet service.
TSN segment of the DetNet service. In the DetNet MPLS domain, Bidirectional Forwarding Detection (BFD), as speci
In the DetNet MPLS domain BFD (Bidirectional Forwarding Detection), specified fied in <xref target="RFC5880"/> and <xref target="RFC5885"/>,
in <xref target="RFC5880"/> and <xref target="RFC5885"/>,
can be used. To provide E2E failure detection, the TSN and DetNet MPLS segmen ts could be treated as concatenated such that the diagnostic codes can be used. To provide E2E failure detection, the TSN and DetNet MPLS segmen ts could be treated as concatenated such that the diagnostic codes
(see Section 6.8.17 of <xref target="RFC5880"/>) MAY be used to inform the up (see <xref target="RFC5880" sectionFormat="of" section="6.8.17"/>) <bcp14>MAY
stream DetNet MPLS node of a failure of the TSN segment. </bcp14> be used to inform the upstream DetNet MPLS node of a TSN segment failur
Performance monitoring can be supported by <xref target="RFC6374"/> in the De e.
tNet MPLS and <xref target="ITU.Y1731"/> in the TSN domains, respectively. Performance monitoring can be supported by <xref target="RFC6374"/> in the De
Performance objectives for each domain should refer to metrics that is compos tNet MPLS and by <xref target="ITU.Y1731"/> in TSN domains, respectively.
able <xref target="RFC6049"/> or be defined for each domain separately. Performance objectives for each domain should refer to metrics that are compo
sable <xref target="RFC6049"/> or are defined for each domain separately.
</t> </t>
<t> <t>
The following considerations apply when using the tunneling model of OAM interwo rking between DetNet MPLS and TSN domains The following considerations apply when using the tunneling model of OAM interwo rking between DetNet MPLS and TSN domains
based on general principles described in Section 4 of <xref target="RFC9037"/>: based on general principles described in <xref target="RFC9037" sectionFormat="o f" section="4"/>:
</t> </t>
<ul spacing="normal"> <ul spacing="normal">
<li>Active OAM test packets MUST be mapped to the same TSN Stream ID a <li>Active OAM test packets <bcp14>MUST</bcp14> be mapped to the same
s the monitored DetNet flow.</li> TSN Stream ID as the monitored DetNet flow.</li>
<li>Active OAM test packets MUST be treated in the TSN domain based on <li>Active OAM test packets <bcp14>MUST</bcp14> be processed in the TS
its S-Label and N domain based on their S-Label and
Class of Service marking (the Traffic Class field value).</li> Class of Service marking (the Traffic Class field value).</li>
</ul> </ul>
<t> <t>
Mapping between a DetNet flow and TSN Stream in the TSN sub-network is d escribed in Section 4.1 of <xref target="RFC9037"/>. Mapping between a DetNet flow and TSN Stream in the TSN sub-network is d escribed in <xref target="RFC9037" sectionFormat="of" section="4.1"/>.
The mapping has to be done only on the edge node of the TSN sub-network, and intermediate TSN nodes do not need to recognize the S-Label. The mapping has to be done only on the edge node of the TSN sub-network, and intermediate TSN nodes do not need to recognize the S-Label.
An edge node has two components: An edge node has two components:
</t> </t>
<ol> <ol>
<li>A passive Stream identification function.</li> <li>A passive Stream identification function.</li>
<li>An active Stream identification function.</li> <li>An active Stream identification function.</li>
</ol> </ol>
<t>The first component identifies the DetNet flow (using Clause 6.8 of < xref target="IEEE.802.1CBdb"/>), <t>The first component identifies the DetNet flow (using Clause 6.8 of < xref target="IEEE.802.1CBdb"/>),
and the second component creates the TSN Stream by manipulating the Ethe rnet header. and the second component creates the TSN Stream by manipulating the Ethe rnet header.
That manipulation simplifies the identification of the TSN Stream in the intermediate TSN nodes That manipulation simplifies the identification of the TSN Stream in the intermediate TSN nodes
by avoiding the need for them to look outside of the Ethernet header. by avoiding the need for them to look outside of the Ethernet header.
DetNet MPLS OAM packets use the same S-Label as the DetNet flow data pac kets. The above-described mapping DetNet MPLS OAM packets use the same S-Label as the DetNet flow data pac kets. The above-described mapping
function treats these OAM packets as data packets of the DetNet flow. As a resul t, function treats these OAM packets as data packets of the DetNet flow. As a resul t,
DetNet MPLS OAM packets are fate-sharing within the TSN sub-network. DetNet MPLS OAM packets are fate sharing within the TSN sub-network.
As an example of the mapping between DetNet MPLS and TSN, As an example of the mapping between DetNet MPLS and TSN,
see Annex C.1 of <xref target="IEEE.802.1CBdb"/> that, in support of <xref targe t="RFC9037"/>, see Annex C.1 of <xref target="IEEE.802.1CBdb"/> that, in support of <xref targe t="RFC9037"/>,
describes how to match MPLS DetNet flows and TSN Streams can be achieved. describes how to match MPLS DetNet flows and achieve TSN Streams.
</t> </t>
<t> <t>
Note that the tunneling model of the OAM interworking requires that the remote p eer of Note that the tunneling model of the OAM interworking requires that the remote p eer of
the E2E OAM domain supports the active OAM protocol selected on the ingress endp oint. the E2E OAM domain supports the active OAM protocol selected on the ingress endp oint.
For example, if BFD is used for proactive path continuity monitoring in the D etNet MPLS For example, if BFD is used for proactive path continuity monitoring in the D etNet MPLS
domain, BFD support (as defined in <xref target="RFC5885"/>) is necessary at any domain, BFD support (as defined in <xref target="RFC5885"/>) is necessary at any
TSN endpoint of the DetNet service. TSN endpoint of the DetNet service.
</t> </t>
</section> </section>
<section anchor="ip-over-ip-sec" numbered="true" toc="default"> <section anchor="ip-over-ip-sec" numbered="true" toc="default">
<name>OAM of DetNet MPLS Interworking with OAM of DetNet IP</name> <name>OAM of DetNet MPLS Interworking with OAM of DetNet IP</name>
<t> <t>
Interworking between active OAM segments in DetNet MPLS and DetNet IP domains ca n also be realized Interworking between active OAM segments in DetNet MPLS and DetNet IP domains ca n also be realized
using either the peering or the tunneling model, as discussed in <xref target="i p-over-tsn-sec" format="default"/>. Using the same protocol, e.g., BFD, using either the peering model or the tunneling model, as discussed in <xref tar get="ip-over-tsn-sec" format="default"/>. Using the same protocol, e.g., BFD
over both segments, simplifies the mapping of errors in the peering model. For e xample, respective BFD sessions over both segments, simplifies the mapping of errors in the peering model. For e xample, respective BFD sessions
in DetNet MPLS and DetNet IP domains can be in a concatenated relationship as de in DetNet MPLS and DetNet IP domains can be in a concatenated relationship as de
scribed in Section 6.8.17 of <xref target="RFC5880"/>. scribed in <xref target="RFC5880" sectionFormat="of" section="6.8.17"/>.
To provide performance monitoring over a DetNet IP domain, To provide performance monitoring over a DetNet IP domain, the
STAMP <xref target="RFC8762"/> and its extensions <xref target="RFC8972"/> can b Simple Two-way Active Measurement Protocol (STAMP) <xref target="RFC8762"/> and
e used to measure packet loss and packet delay metrics. its extensions <xref target="RFC8972"/> can be used to measure packet loss and p
acket delay metrics.
Such performance metrics can be used to calculate composable metrics <xref targe t="RFC6049"/> Such performance metrics can be used to calculate composable metrics <xref targe t="RFC6049"/>
within DetNet MPLS and DetNet IP domains to reflect the end-to-end DetNet servic e performance. within DetNet MPLS and DetNet IP domains to reflect the end-to-end DetNet servic e performance.
</t> </t>
</section> </section>
</section> </section>
<section anchor="iana-considerations" numbered="true" toc="default"> <section anchor="iana-considerations" numbered="true" toc="default">
<name>IANA Considerations</name> <name>IANA Considerations</name>
<section anchor="iana-mpls-oam-flags" numbered="true" toc="default"> <section anchor="iana-mpls-oam-flags" numbered="true" toc="default">
<name>DetNet Associated Channel Header Flags Registry</name> <name>DetNet Associated Channel Header (d-ACH) Flags Registry</name>
<t> <t>IANA has created the "DetNet Associated Channel Header (d-ACH) Fla
This document describes a new IANA-managed registry to identify d-ACH Flags bits gs" registry within the "DetNet Associated Channel Header (d-ACH) Flags" registr
. The y group. The registration procedure is "IETF Review" <xref target="RFC8126"/>. T
registration procedure is "IETF Review" <xref target="RFC8126"/>. here are five flags in the 5-bit Flags field, as defined in <xref target="iana-d
The registry name is "DetNet Associated Channel Header (d-ACH) Flags". ach-flags-tbl"/>.
IANA should treat "DetNet Associated Channel Header (d-ACH) Flags" as the name o
f the registry group.
There are five flags in the five-bit Flags field, defined as in <xref target="ia
na-dach-flags-tbl"/>.
</t> </t>
<table anchor="iana-dach-flags-tbl" align="center"> <table anchor="iana-dach-flags-tbl" align="center">
<name>DetNet Associated Channel Header (d-ACH) Flags</name> <name>DetNet Associated Channel Header (d-ACH) Flags Registry</name>
<thead> <thead>
<tr> <tr>
<th align="left">Bit</th> <th align="left">Bit</th>
<th align="center">Description</th> <th align="center">Description</th>
<th align="left">Reference</th>
</tr> </tr>
</thead> </thead>
<tbody> <tbody>
<tr> <tr>
<td align="left">0-4</td> <td align="left">0-4</td>
<td align="center">Unassigned</td> <td align="center">Unassigned</td>
<td align="left">This&nbsp;document</td>
</tr> </tr>
</tbody> </tbody>
</table> </table>
</section> </section>
</section> </section>
<section anchor="security-considerations" numbered="true" toc="default"> <section anchor="security-considerations" numbered="true" toc="default">
<name>Security Considerations</name> <name>Security Considerations</name>
<t> <t>
Security considerations discussed in DetNet specifications <xref target="RFC8 655"/>, Security considerations discussed in DetNet specifications <xref target="RFC8 655"/>,
<xref target="RFC9055"/>, <xref target="RFC8964"/>, and <xref target="I-D.iet <xref target="RFC8964"/>, <xref target="RFC9055"/>, and <xref target="I-D.iet
f-detnet-oam-framework"/> are applicable to this document. f-detnet-oam-framework"/> are applicable to this document.
Security concerns and issues related to MPLS OAM tools like LSP Ping <xref ta Security concerns and issues related to MPLS OAM tools like LSP Ping <xref ta
rget="RFC8029"/>, rget="RFC8029"/>
and BFD over PW <xref target="RFC5885"/> also apply to this specification. and BFD over PW <xref target="RFC5885"/> also apply to this specification.
</t> </t>
</section> </section>
<section anchor="ack" numbered="true" toc="default">
<name>Acknowledgment</name>
<t>
Authors extend their appreciation to Pascal Thubert for his insightful comment
s and productive discussion
that helped to improve the document. The authors are enormously grateful to Ja
nos Farkas for his detailed
comments and the inspiring discussion that made this document clearer and stro
nger. The authors recognize
helpful reviews and suggestions from Andrew Malis, David Black, Tianran Zhou,
and Kiran Makhijani. And special thanks
are addressed to Ethan Grossman for his fantastic help in improving the docume
nt.
</t>
</section>
</middle> </middle>
<back> <back>
<!-- References split into informative and normative --> <displayreference target="I-D.ietf-detnet-oam-framework" to="OAM-FRAMEWORK"/ >
<references> <references>
<name>References</name> <name>References</name>
<references> <references>
<name>Normative References</name> <name>Normative References</name>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2
FC.2119.xml"/> 119.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
FC.8174.xml"/> 174.xml"/>
<!-- <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7
<?rfc include="reference.RFC.5586"?> 023.xml"/>
<?rfc include="reference.RFC.6423"?> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
--> 655.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7 <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
023.xml"/> 964.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9
FC.8655.xml"/> 025.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8964.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.9025.xml"/>
</references> </references>
<references> <references>
<name>Informational References</name> <name>Informative References</name>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7
FC.7799.xml"/> 799.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6
FC.6374.xml"/> 374.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3
FC.3985.xml"/> 985.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4
FC.4385.xml"/> 385.xml"/>
<!-- <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4
C.8321.xml"/> --> 928.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5
FC.4928.xml"/> 880.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5
FC.5880.xml"/> 885.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
FC.5885.xml"/> 029.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
FC.8029.xml"/> 762.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
FC.8762.xml"/> 972.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9
FC.8972.xml"/> 055.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9
FC.9055.xml"/> 037.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R 126.xml"/>
FC.9037.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R 049.xml"/>
FC.8126.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.6049.xml"/>
<xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-ietf-de <!-- [I-D.ietf-detnet-oam-framework] IESG State: RFC Ed Queue as of 2/21/24. Ent
tnet-oam-framework.xml"/> ered long way to get the correct initials-->
<reference anchor="I-D.ietf-detnet-oam-framework" target="https://datatracker.ie
tf.org/doc/html/draft-ietf-detnet-oam-framework-11">
<front>
<title>Framework of Operations, Administration and Maintenance (OAM) for Det
erministic Networking (DetNet)</title>
<author fullname="Greg Mirsky" initials="G." surname="Mirsky">
<organization>Ericsson</organization>
</author>
<author fullname="Fabrice Theoleyre" initials="F." surname="Theoleyre">
<organization>CNRS</organization>
</author>
<author fullname="Georgios Z. Papadopoulos" initials="G. Z." surname="Papado
poulos">
<organization>IMT Atlantique</organization>
</author>
<author fullname="Carlos J. Bernardos" initials="CJ." surname="Bernardos">
<organization>Universidad Carlos III de Madrid</organization>
</author>
<author fullname="Balazs Varga" initials="B." surname="Varga">
<organization>Ericsson</organization>
</author>
<author fullname="János Farkas" initials="J." surname="Farkas">
<organization>Ericsson</organization>
</author>
<date day="8" month="January" year="2024"/>
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-detnet-oam-framework-11"/>
</reference>
<reference anchor="IEEE.802.1CBdb"> <reference anchor="IEEE.802.1CBdb">
<front> <front>
<title>IEEE Standard for Local and metropolitan area networks--Frame Replication and Elimination for Reliability Amendment 2: Extended Stream Identi fication Functions</title> <title>IEEE Standard for Local and metropolitan area networks--Frame Replication and Elimination for Reliability--Amendment 2: Extended Stream Ident ification Functions</title>
<author> <author>
<organization>IEEE</organization> <organization>IEEE</organization>
</author> </author>
<date year="2021"/> <date month="December" year="2021"/>
</front> </front>
<seriesInfo name="IEEE" value="802.1CBdb"/> <seriesInfo name="IEEE Std" value="802.1CBdb-2021"/>
</reference> </reference>
<reference anchor="IEEE.802.1Q"> <reference anchor="IEEE.802.1Q">
<front> <front>
<title>Bridges and Bridged Networks</title> <title>IEEE Standard for Local and Metropolitan Area Network--Bridge s and Bridged Networks</title>
<author> <author>
<organization>IEEE</organization> <organization>IEEE</organization>
</author> </author>
<date year="2014"/> <date month="July" year="2018"/>
</front> </front>
<seriesInfo name="IEEE" value="802.1Q"/> <seriesInfo name="IEEE Std" value="802.1Q-2018"/>
<seriesInfo name="DOI" value="10.1109/IEEESTD.2018.8403927"/>
</reference> </reference>
<reference anchor="IEEE802.1TSNTG" target="https://1.ieee802.org/tsn/" q uoteTitle="true" derivedAnchor="IEEE802.1TSNTG"> <reference anchor="IEEE802.1TSNTG" target="https://1.ieee802.org/tsn/" q uoteTitle="true" derivedAnchor="IEEE802.1TSNTG">
<front> <front>
<title>Time-Sensitive Networking (TSN) Task Group</title> <title>Time-Sensitive Networking (TSN) Task Group</title>
<author> <author>
<organization showOnFrontPage="true">IEEE</organization> <organization>IEEE 802.1</organization>
</author> </author>
</front> </front>
<seriesInfo name="IEEE" value="802.1Q"/> <refcontent>TSN Standards</refcontent>
</reference> </reference>
<reference anchor="ITU.Y1731"> <reference anchor="ITU.Y1731">
<front> <front>
<title>OAM functions and mechanisms for Ethernet based Networks</tit le> <title>Operation, administration and maintenance (OAM) functions and mechanisms for Ethernet-based networks</title>
<author> <author>
<organization>ITU-T</organization> <organization>ITU-T</organization>
</author> </author>
<date month="November" year="2013"/> <date month="June" year="2023"/>
</front> </front>
<seriesInfo name="ITU-T Recommendation" value="G.8013/Y.1731"/> <seriesInfo name="ITU-T Recommendation" value="G.8013/Y.1731"/>
</reference> </reference>
<reference anchor="IANA-G-ACh-Types" target="https://www.iana.org/assign ments/g-ach-parameters/g-ach-parameters.xhtml#mpls-g-ach-types"> <reference anchor="IANA-G-ACh-Types" target="https://www.iana.org/assign ments/g-ach-parameters/">
<front> <front>
<title>MPLS Generalized Associated Channel (G-ACh) Types (including Pseudowire Associated Channel Types)</title> <title>MPLS Generalized Associated Channel (G-ACh) Types (including Pseudowire Associated Channel Types)</title>
<author> <author>
<organization>IANA</organization> <organization>IANA</organization>
</author> </author>
</front> </front>
</reference> </reference>
</references> </references>
</references> </references>
<section anchor="ack" numbered="false" toc="default">
<name>Acknowledgments</name>
<t>
The authors extend their appreciation to <contact fullname="Pascal Thubert"/>
for his insightful comments and productive discussion
that helped to improve the document. The authors are enormously grateful to <
contact fullname="János Farkas"/> for his detailed
comments and the inspiring discussion that made this document clearer and stro
nger. The authors recognize
helpful reviews and suggestions from <contact fullname="Andrew Malis"/>, <cont
act fullname="David Black"/>, <contact fullname="Tianran Zhou"/>, and <contact f
ullname="Kiran Makhijani"/>. And special thanks
to <contact fullname="Ethan Grossman"/> for his fantastic help in improving th
e document.
</t>
</section>
</back> </back>
</rfc> </rfc>
 End of changes. 86 change blocks. 
339 lines changed or deleted 326 lines changed or added

This html diff was produced by rfcdiff 1.48.