rfc9533xml2.original.xml   rfc9533.xml 
<?xml version="1.0" encoding="US-ASCII"?> <?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?> <!DOCTYPE rfc [
<?rfc tocompact="yes"?> <!ENTITY nbsp "&#160;">
<?rfc tocdepth="3"?> <!ENTITY zwsp "&#8203;">
<?rfc tocindent="yes"?> <!ENTITY nbhy "&#8209;">
<?rfc symrefs="yes"?> <!ENTITY wj "&#8288;">
<?rfc sortrefs="yes"?> ]>
<?rfc comments="yes"?>
<?rfc inline="yes"?> <rfc xmlns:xi="http://www.w3.org/2001/XInclude"
<?rfc compact="yes"?> category="std"
<?rfc subcompact="no"?> consensus="true"
<rfc category="std" consensus="true" docName="draft-ietf-ippm-otwamp-on-lag-08"
docName="draft-ietf-ippm-otwamp-on-lag-08" ipr="trust200902" number="9533"
sortRefs="true" submissionType="IETF" tocInclude="true"> ipr="trust200902"
<front> sortRefs="true"
<title abbrev="O/TWAMP PM on LAG">One-way/Two-way Active Measurement submissionType="IETF"
Protocol Extensions for Performance Measurement on LAG</title> tocInclude="true"
obsoletes=""
updates=""
xml:lang="en"
tocDepth="3"
symRefs="true"
version="3">
<front>
<title abbrev="OWAMP/TWAMP PM on LAG">One-Way and Two-Way Active Measurement
Protocol Extensions for Performance Measurement on a Link Aggregation Group<
/title>
<seriesInfo name="RFC" value="9533"/>
<author fullname="Zhenqiang Li" initials="Z." surname="Li"> <author fullname="Zhenqiang Li" initials="Z." surname="Li">
<organization>China Mobile</organization> <organization>China Mobile</organization>
<address> <address>
<postal> <postal>
<street>No. 29 Finance Avenue, Xicheng District</street> <street>No. 29 Finance Avenue</street>
<cityarea>Xicheng District</cityarea>
<city>Beijing</city> <city>Beijing</city>
<code/> <code/>
<country>China</country> <country>China</country>
</postal> </postal>
<email>li_zhenqiang@hotmail.com</email> <email>li_zhenqiang@hotmail.com</email>
</address> </address>
</author> </author>
<author fullname="Tianran Zhou" initials="T." surname="Zhou"> <author fullname="Tianran Zhou" initials="T." surname="Zhou">
<organization>Huawei</organization> <organization>Huawei</organization>
<address> <address>
<postal> <postal>
<street/>
<country>China</country> <country>China</country>
</postal> </postal>
<email>zhoutianran@huawei.com</email> <email>zhoutianran@huawei.com</email>
</address> </address>
</author> </author>
<author fullname="Jun Guo" initials="J." surname="Guo"> <author fullname="Jun Guo" initials="J." surname="Guo">
<organization>ZTE Corp.</organization> <organization>ZTE Corp.</organization>
<address> <address>
<postal> <postal>
<street/>
<city/>
<region/>
<code/>
<country>China</country> <country>China</country>
</postal> </postal>
<phone/> <phone/>
<facsimile/>
<email>guo.jun2@zte.com.cn</email> <email>guo.jun2@zte.com.cn</email>
<uri/> <uri/>
</address> </address>
</author> </author>
<author fullname="Greg Mirsky" initials="G." surname="Mirsky"> <author fullname="Greg Mirsky" initials="G." surname="Mirsky">
<organization>Ericsson</organization> <organization>Ericsson</organization>
<address> <address>
<postal> <postal>
<street/> <street/>
<country>United States of America</country> <country>United States of America</country>
</postal> </postal>
<email>gregimirsky@gmail.com</email> <email>gregimirsky@gmail.com</email>
</address> </address>
</author> </author>
<author fullname="Rakesh Gandhi" initials="R." surname="Gandhi"> <author fullname="Rakesh Gandhi" initials="R." surname="Gandhi">
<organization>Cisco</organization> <organization>Cisco Systems, Inc.</organization>
<address> <address>
<postal> <postal>
<street/>
<city/>
<region/>
<code/>
<country>Canada</country> <country>Canada</country>
</postal> </postal>
<phone/> <phone/>
<facsimile/>
<email>rgandhi@cisco.com</email> <email>rgandhi@cisco.com</email>
<uri/> <uri/>
</address> </address>
</author> </author>
<date day="11" month="December" year="2023"/> <date month="January" year="2024"/>
<area>Operation and Management Area</area>
<area>Transport Area</area>
<workgroup>IPPM</workgroup> <workgroup>IPPM</workgroup>
<abstract> <abstract>
<t>This document defines extensions to One-way Active Measurement <t>This document defines extensions to the One-Way Active Measurement
Protocol (OWAMP), and Two-way Active Measurement Protocol (TWAMP) to Protocol (OWAMP) and the Two-Way Active Measurement Protocol (TWAMP) to
implement performance measurement on every member link of a Link implement performance measurement on every member link of a Link
Aggregation Group (LAG). Knowing the measured metrics of each member Aggregation Group (LAG). Knowing the measured metrics of each member
link of a LAG enables operators to enforce the performance based traffic link of a LAG enables operators to enforce the performance-based traffic
steering policy across the member links.</t> steering policy across the member links.</t>
</abstract> </abstract>
<note title="Requirements Language">
<t>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
<xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when,
they appear in all capitals, as shown here.</t>
</note>
</front> </front>
<middle> <middle>
<section title="Introduction"> <section numbered="true" toc="default">
<t>Link Aggregation Group (LAG), as defined in <xref <name>Introduction</name>
target="IEEE802.1AX"/>, provides mechanisms to combine multiple physical <t>A Link Aggregation Group (LAG), as defined in <xref target="IEEE802.1AX
" format="default"/>, provides mechanisms to combine multiple physical
links into a single logical link. This logical link offers higher links into a single logical link. This logical link offers higher
bandwidth and better resiliency, because if one of the physical member bandwidth and better resiliency because, if one of the physical member
links fails, the aggregate logical link can continue to forward traffic links fails, the aggregate logical link can continue to forward traffic
over the remaining operational physical member links.</t> over the remaining operational physical member links.</t>
<t>Usually, when forwarding traffic over a LAG, a hash-based mechanism is
<t>Usually, when forwarding traffic over LAG, a hash-based mechanism is
used to load balance the traffic across the LAG member links. The link used to load balance the traffic across the LAG member links. The link
delay might vary between member links because of different transport delay might vary between member links because of different transport
paths, especially when LAG is used in wide area network. To provide low paths, especially when a LAG is used in a wide area network. To provide lo
latency service for time sensitive traffic, we need to explicitly steer w-latency service for time-sensitive traffic, we need to explicitly steer
the traffic across the LAG member links based on the link delay, loss the traffic across the LAG member links based on the link delay, loss,
and so on. That requires a solution to measure the performance metrics and so on. That requires a solution to measure the performance metrics
of every member link of a LAG. Hence, the measured performance metrics of every member link of a LAG. Hence, the measured performance metrics
can work together with <xref target="RFC8668">layer 2 bundle member link can work together with Layer 2 bundle member link
attributes advertisement</xref> for traffic steering.</t> attributes advertisement <xref target="RFC8668" format="default"></xref> f
or traffic steering.</t>
<t>According to the classifications in <xref target="RFC7799"/>, <xref <t>According to the classifications in <xref target="RFC7799" format="defa
target="RFC4656">OWAMP</xref> and <xref target="RFC5357">TWAMP</xref> ult"/>, OWAMP <xref target="RFC4656" format="default"></xref> and TWAMP <xref ta
rget="RFC5357" format="default"></xref>
are active measurement methods, and they can complement passive and are active measurement methods, and they can complement passive and
hybrid methods. With either method, one test session over the LAG can hybrid methods. With either method, one test session over the LAG can be
measure the performance of a member link with fixed five tuples. Or it used to measure the performance of a member link using a specially constructed 5
can measure an average of some/all member links of the LAG by varying -tuple. The session can be used to measure an average of some or all member link
the five tuples. However, without the knowledge of each member link, a s of the LAG by varying one or more elements of that 5-tuple. However, without
the knowledge of each member link, a
test session cannot measure the performance of every physical member test session cannot measure the performance of every physical member
link.</t> link.</t>
<t>This document extends OWAMP and TWAMP to implement performance <t>This document extends OWAMP and TWAMP to implement performance
measurement on every member link of a LAG. It can provide the same measurement on every member link of a LAG. It can provide the same
metrics as OWAMP and TWAMP can measure, such as delay, jitter and packet metrics as OWAMP and TWAMP can measure, such as delay, jitter, and packet
loss.</t> loss.</t>
<section numbered="true" toc="default">
<name>Requirements Language</name>
<t>
The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
"<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>
",
"<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
"<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<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>
</section>
</section> </section>
<section numbered="true" toc="default">
<section title="Micro Session on LAG"> <name>Micro Sessions on a LAG</name>
<t>This document addresses the scenario where a LAG directly connects <t>This document addresses the scenario where a LAG directly connects
two nodes. An example of this is in Figure 1, where the LAG consisting two nodes. An example of this is in <xref target="PMonLAG" format="default "/>, where the LAG consisting
of four links connects nodes A and B. The goal is to measure the of four links connects nodes A and B. The goal is to measure the
performance of each link of the LAG.</t> performance of each link of the LAG.</t>
<figure anchor="PMonLAG">
<figure align="center" anchor="PMonLAG" <name>Performance Measurement on a LAG</name>
title="Performance Measurement on LAG"> <artwork name="" type="" align="left" alt=""><![CDATA[
<artwork><![CDATA[ +---+ +---+ +---+ +---+
| |-----------------------| | | |-----------------------| |
---+ +---+
| A |-----------------------| B | | A |-----------------------| B |
| |-----------------------| | | |-----------------------| |
| |-----------------------| | | |-----------------------| |
+---+ +---+ +---+ +---+
]]></artwork> ]]></artwork>
</figure> </figure>
<t>To measure the performance metrics of every member link of a LAG, <t>To measure the performance metrics of every member link of a LAG,
multiple sessions (one session for each member link) need to be multiple sessions (one session for each member link) need to be
established between the two end points that are connected by the LAG. established between the two endpoints that are connected by the LAG.
These sessions are called micro sessions in the remainder of this These sessions are called "micro sessions" in the remainder of this
document. Although micro sessions are in fact OWAMP or TWAMP sessions document. Although micro sessions are in fact OWAMP or TWAMP sessions
established on member links of a LAG, test packets of micro TWAMP established on member links of a LAG, test packets of micro TWAMP
sessions MUST carry member link information for validation.</t> sessions <bcp14>MUST</bcp14> carry member link information for validation. </t>
<t>All micro sessions of a LAG share the same Sender IP Address and <t>All micro sessions of a LAG share the same Sender IP Address and
Receiver IP Address of the LAG. As for the UDP layer, the micro sessions Receiver IP Address. As for the UDP port, the micro sessions
may share the same Sender Port and Receiver Port pair, or each micro may share the same Sender Port and Receiver Port pair or each micro
session is configured with a different Sender Port and Receiver Port session may be configured with a different Sender Port and Receiver Port
pair. But from the operational point of view, the former is simpler and pair. From the operational point of view, the former is simpler and
is RECOMMENDED.</t> is <bcp14>RECOMMENDED</bcp14>.</t>
<t>Test packets of a micro session <bcp14>MUST</bcp14> carry the member li
<t>Test packets of a micro session MUST carry the member link nk
information for validation check. For example, when a micro TWAMP information for validation checks. For example, when a micro TWAMP
Session-Sender receives a reflected test packet, it checks whether the Session-Sender receives a reflected test packet, it checks whether the
test packet is from the expected member link.</t> test packet is from the expected member link.</t>
</section> </section>
<section numbered="true" toc="default">
<name>Micro OWAMP Session</name>
<section numbered="true" toc="default" anchor="micro">
<name>Micro OWAMP-Control</name>
<section title="Micro OWAMP Session">
<section title="Micro OWAMP-Control">
<t>To support the micro OWAMP session, a new command, <t>To support the micro OWAMP session, a new command,
Request-OW-Micro-Sessions (TBD1), is defined in this document. The Request-OW-Micro-Sessions (5), is defined in this document. The
Request-OW-Micro-Sessions command is based on the OWAMP Request-OW-Micro-Sessions command is based on the OWAMP
Request-Session command, and uses the message format as described in Request-Session command and uses the message format as described in
Section 3.5 of <xref target="RFC4656">OWAMP</xref>. Test session <xref target="RFC4656" sectionFormat="of" section="3.5"></xref>. Test se
creation of micro OWAMP session follows the same procedure as defined ssion
in Section 3.5 of <xref target="RFC4656">OWAMP</xref> with the creation of micro OWAMP sessions follows the same procedure as defined
in <xref target="RFC4656" sectionFormat="of" section="3.5"></xref> with
the
following additions:</t> following additions:</t>
<t>When an OWAMP Server receives a Request-OW-Micro-Sessions command, <t>When an OWAMP Server receives a Request-OW-Micro-Sessions command,
if the request is accepted, the OWAMP Server MUST build a set of micro if the request is accepted, the OWAMP Server <bcp14>MUST</bcp14> build a set of micro
sessions for all the member links of the LAG from which the sessions for all the member links of the LAG from which the
Request-OW-Micro-Sessions message is received.</t> Request-OW-Micro-Sessions message is received.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="Micro OWAMP-Test"> <name>Micro OWAMP-Test</name>
<t>Micro OWAMP-Test reuses the OWAMP-Test packet format and procedures <t>Micro OWAMP-Test reuses the OWAMP-Test packet format and procedures
as defined in Section 4 of <xref target="RFC4656">OWAMP</xref> with as defined in <xref target="RFC4656" sectionFormat="of" section="4"></xr ef> with
the following additions:</t> the following additions:</t>
<t>The micro OWAMP Session-Sender <bcp14>MUST</bcp14> send the micro OWA
<t>The micro OWAMP Session-Sender MUST send the micro OWAMP-Test MP-Test
packets over the member link with which the session is associated. packets over the member link with which the session is associated.
When it receives a test packet, the micro OWAMP Session-Receiver MUST When it receives a test packet, the micro OWAMP Session-Receiver <bcp14> MUST</bcp14>
use the member link from which the test packet is received to use the member link from which the test packet is received to
correlate the micro OWAMP session. If there is no such a session, the correlate the micro OWAMP session. If there is no such session, the
Test packet MUST be discarded.</t> test packet <bcp14>MUST</bcp14> be discarded.</t>
</section> </section>
</section> </section>
<section numbered="true" toc="default">
<section title="Micro TWAMP Session"> <name>Micro TWAMP Session</name>
<section title="Micro TWAMP-Control"> <section numbered="true" toc="default" anchor="micro2">
<name>Micro TWAMP-Control</name>
<t>To support the micro TWAMP session, a new command, <t>To support the micro TWAMP session, a new command,
Request-TW-Micro-Sessions (TBD2), is defined in this document. The Request-TW-Micro-Sessions (11), is defined in this document. The
Request-TW-Micro-Sessions command is based on the TWAMP Request-TW-Micro-Sessions command is based on the TWAMP
Request-Session command, and uses the message format as described in Request-Session command and uses the message format as described in
Section 3.5 of <xref target="RFC5357">TWAMP</xref>. Test session <xref target="RFC5357" sectionFormat="of" section="3.5"></xref>. Test se
creation of micro TWAMP session follows the same procedure as defined ssion
in Section 3.5 of <xref target="RFC5357">TWAMP</xref> with the creation of micro TWAMP sessions follows the same procedure as defined
in <xref target="RFC5357" sectionFormat="of" section="3.5"></xref> with
the
following additions:</t> following additions:</t>
<t>When a TWAMP Server receives a Request-TW-Micro-Sessions command, <t>When a TWAMP Server receives a Request-TW-Micro-Sessions command,
if the request is accepted, the TWAMP Server MUST build a set of micro if the request is accepted, the TWAMP Server <bcp14>MUST</bcp14> build a set of micro
sessions for all the member links of the LAG from which the sessions for all the member links of the LAG from which the
Request-TW-Micro-Sessions message is received.</t> Request-TW-Micro-Sessions message is received.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="Micro TWAMP-Test"> <name>Micro TWAMP-Test</name>
<t>The micro TWAMP-Test protocol is based on the TWAMP-Test protocol <t>The micro TWAMP-Test protocol is based on the TWAMP-Test protocol
<xref target="RFC5357"/> with the following extensions.</t> <xref target="RFC5357" format="default"/> with the extensions described
in the following subsections.</t>
<section title="Sender Packet Format and Content"> <section numbered="true" toc="default">
<name>Sender Packet Format and Content</name>
<t>The micro TWAMP Session-Sender packet format is based on the <t>The micro TWAMP Session-Sender packet format is based on the
TWAMP Session-Sender packet format as defined in Section 4.1.2 of TWAMP Session-Sender packet format as defined in
<xref target="RFC5357"/>. Two new fields (Sender Micro-session ID <xref target="RFC5357" sectionFormat="of" section="4.1.2"/>. Two new f
ields (Sender Micro-session ID
and Reflector Micro-session ID) are added to carry the LAG member and Reflector Micro-session ID) are added to carry the LAG member
link identifiers.</t> link identifiers.</t>
<t>For unauthenticated mode, the format is as below:</t> <t>For unauthenticated mode, the format is as below:</t>
<figure anchor="TWAMPSender">
<t> <name>Micro Session-Sender Packet Format in Unauthenticated Mode</na
<figure align="center" anchor="TWAMPSender" me>
title="Micro Session-Sender Packet Format in Unauthenticated <artwork name="" type="" align="left" alt=""><![CDATA[ 0
Mode"> 1 2 3
<artwork><![CDATA[ 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number | | Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp | | Timestamp |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Estimate | MBZ | | Error Estimate | MBZ |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender Micro-session ID | Reflector Micro-session ID | | Sender Micro-session ID | Reflector Micro-session ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
. Packet Padding . . Packet Padding .
. . . .
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork> ]]></artwork>
</figure> </figure>
</t> <t>For authenticated and encrypted mode, the format is as below:</t>
<figure anchor="TWAMPSenderA">
<t>For authenticated mode, the format is as below:<figure <name>Micro Session-Sender Packet Format in Authenticated Mode</name
align="center" anchor="TWAMPSenderA" >
title="Micro Session-Sender Packet Format in Authenticated Mode"> <artwork name="" type="" align="left" alt=""><![CDATA[ 0
<artwork><![CDATA[ 0 1 2 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number | | Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| MBZ (12 octets) | | MBZ (12 octets) |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp | | Timestamp |
| | | |
skipping to change at line 331 skipping to change at line 286
| HMAC (16 octets) | | HMAC (16 octets) |
| | | |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
. Packet Padding . . Packet Padding .
. . . .
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork> ]]></artwork>
</figure></t> </figure>
<t>Except for the Sender/Reflector Micro-session ID field, all the <t>Except for the Sender Micro-session ID field and the Reflector Micr
other fields are the same as defined in Section 4.1.2 of <xref o-session ID field, all the
target="RFC5357">TWAMP</xref>, which is defined in Section 4.1.2 of other fields are the same as defined in <xref target="RFC5357" section
<xref target="RFC4656">OWAMP</xref>. Therefore, it follows the same Format="of" section="4.1.2"></xref> and follow the procedure and guidelines defi
procedure and guidelines as defined in Section 4.1.2 of <xref ned therein.</t>
target="RFC5357">TWAMP</xref>.</t> <dl spacing="normal">
<t> <dt>Sender Micro-session ID (2 octets in length):</dt><dd>This fie
<list style="symbols"> ld is defined to carry the LAG member link identifier of the Sender
<t>Sender Micro-session ID (2-octets in length): It is now
defined to carry the LAG member link identifier of the Sender
side. In the future, it may be used generically to cover side. In the future, it may be used generically to cover
use-cases beyond LAG. The value of this field MUST be unique use cases beyond LAGs. The value of this field <bcp14>MUST</bcp14>
within a TWAMP session at the Session-Sender.</t> be unique
within a TWAMP session at the Session-Sender.</dd>
<t>Reflector Micro-session ID (2-octets in length): It is now <dt>Reflector Micro-session ID (2 octets in length):</dt> <dd>This field is
defined to carry the LAG member link identifier of the Reflector defined to carry the LAG member link identifier of the Reflector
side. In the future, it may be used generically to cover side. In the future, it may be used generically to cover
use-cases beyond LAG. The value of this field MUST be unique use cases beyond LAGs. The value of this field <bcp14>MUST</bcp14>
within a TWAMP session at the Session-Reflector.</t> be unique
</list> within a TWAMP session at the Session-Reflector.</dd>
</t>
<t/> </dl>
</section>
<section title="Sender Behavior"> </section>
<section numbered="true" toc="default">
<name>Sender Behavior</name>
<t>The micro TWAMP Session-Sender inherits the behaviors of the <t>The micro TWAMP Session-Sender inherits the behaviors of the
TWAMP Session-Sender as defined in Section 4.1 of <xref TWAMP Session-Sender as defined in <xref target="RFC5357" sectionForma
target="RFC5357"/>. In addition, the micro TWAMP Session-Sender MUST t="of" section="4.1"/>. In addition, the micro TWAMP Session-Sender <bcp14>MUST<
/bcp14>
send the micro Session-Sender test packets over the member link with send the micro Session-Sender test packets over the member link with
which the session is associated.</t> which the session is associated.</t>
<t>When sending the test packet, the micro TWAMP Session-Sender <bcp14
<t>When sending the test packet, the micro TWAMP Session-Sender MUST >MUST</bcp14>
put the Sender member link identifier that is associated with the put the Sender member link identifier that is associated with the
micro TWAMP session in the Sender Micro-session ID. If the micro TWAMP session in the Sender Micro-session ID. If the
Session-Sender knows the Reflector member link identifier, the Session-Sender knows the Reflector member link identifier, the
Reflector Micro-session ID field (see <xref target="TWAMPSender"/> Reflector Micro-session ID field (see Figures <xref target="TWAMPSende
and <xref target="TWAMPSenderA"/>) MUST be set. Otherwise, the r" format="counter"/>
Reflector Micro-session ID field MUST be zero.</t> and <xref target="TWAMPSenderA" format="counter"/>) <bcp14>MUST</bcp14
> be set. Otherwise, the
<t>A test packet with Sender member link identifier is sent to the Reflector Micro-session ID field <bcp14>MUST</bcp14> be zero.</t>
Session-Reflector, and then is reflected with the same Sender member <t>A test packet with a Sender member link identifier is sent to the
Session-Reflector and then is reflected with the same Sender member
link identifier. So the Session-Sender can use the Sender member link identifier. So the Session-Sender can use the Sender member
link identifier to check whether a reflected test packet is received link identifier to check whether a reflected test packet is received
from the member link associated with the correct micro TWAMP from the member link associated with the correct micro TWAMP
session.</t> session.</t>
<t>The Reflector member link identifier carried in the Reflector <t>The Reflector member link identifier carried in the Reflector
Micro-session ID field is used by the Session-Reflector to check Micro-session ID field is used by the Session-Reflector to check
whether a test packet is received from the member link associated whether a test packet is received from the member link associated
with the correct micro TWAMP session. It means that the with the correct micro TWAMP session. It means that the
Session-Sender has to learn the Reflector member link identifier. Session-Sender has to learn the Reflector member link identifier.
Once the Session-Sender knows the Reflector member link identifier, Once the Session-Sender knows the Reflector member link identifier,
it MUST put the identifier in the Reflector Micro-session ID field it <bcp14>MUST</bcp14> put the identifier in the Reflector Micro-sessi
(see <xref target="TWAMPSender"/> or <xref target="TWAMPSenderA"/>) on ID field
(see Figures <xref target="TWAMPSender" format="counter"/> or <xref ta
rget="TWAMPSenderA" format="counter"/>)
of the test packets that will be sent to the Session-Reflector. The of the test packets that will be sent to the Session-Reflector. The
Reflector member link identifier can be obtained from Reflector member link identifier can be obtained from
pre-configuration or learned from the data plane (e.g., the preconfiguration or learned from the data plane (e.g., the
reflected test packet). This document does not specify the way to reflected test packet). This document does not specify the way to
obtain the Reflector member link identifier.</t> obtain the Reflector member link identifier.</t>
<t>When receiving a reflected test packet, the micro TWAMP <t>When receiving a reflected test packet, the micro TWAMP
Session-Sender MUST use the receiving member link to correlate the Session-Sender <bcp14>MUST</bcp14> use the receiving member link to co rrelate the
reflected test packet to a micro TWAMP session. If there is no such reflected test packet to a micro TWAMP session. If there is no such
a session, the reflected test packet MUST be discarded. If a matched session, the reflected test packet <bcp14>MUST</bcp14> be discarded. I
session exists, the micro Session-Sender MUST use the Sender f a matched
session exists, the micro Session-Sender <bcp14>MUST</bcp14> use the S
ender
Micro-session ID to validate whether the reflected test packet is Micro-session ID to validate whether the reflected test packet is
correctly received from the expected member link. If the validation correctly received from the expected member link. If the validation
fails, the test packet MUST be discarded. The micro Session-Sender fails, the test packet <bcp14>MUST</bcp14> be discarded. The micro Ses
MUST use the Reflector Micro-session ID to validate the Reflector's sion-Sender
behavior. If the validation fails, the test packet MUST be <bcp14>MUST</bcp14> use the Reflector Micro-session ID to validate the
Reflector's
behavior. If the validation fails, the test packet <bcp14>MUST</bcp14>
be
discarded.</t> discarded.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="Reflector Packet Format and Content"> <name>Reflector Packet Format and Content</name>
<t>The micro TWAMP Session-Reflector packet format is based on the <t>The micro TWAMP Session-Reflector packet format is based on the
TWAMP Session-Reflector packet format as defined in Section 4.2.1 of TWAMP Session-Reflector packet format as defined in
<xref target="RFC5357"/>. Two new fields (Sender and Reflector <xref target="RFC5357" sectionFormat="of" section="4.2.1"/>. Two new f
ields (Sender and Reflector
Micro-session ID) are added to carry the LAG member link Micro-session ID) are added to carry the LAG member link
identifiers.</t> identifiers.</t>
<t>For unauthenticated mode, the format is as below:</t> <t>For unauthenticated mode, the format is as below:</t>
<t> <figure anchor="TWAMPReflector">
<figure align="center" anchor="TWAMPReflector" <name>Micro Session-Reflector Packet Format in Unauthenticated Mode<
title="Micro Session-Reflector Packet Format in Unauthentica /name>
ted Mode"> <artwork name="" type="" align="left" alt=""><![CDATA[
<artwork><![CDATA[ 0 1 2 0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number | | Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp | | Timestamp |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Estimate | MBZ | | Error Estimate | MBZ |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Receive Timestamp | | Receive Timestamp |
| | | |
skipping to change at line 449 skipping to change at line 391
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender TTL | MBZ | Reflector Micro-session ID | | Sender TTL | MBZ | Reflector Micro-session ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
. . . .
. Packet Padding . . Packet Padding .
. . . .
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork> ]]></artwork>
</figure> </figure>
</t> <t>For authenticated and encrypted mode, the format is as below:</t>
<t>For authenticated mode, the format is as below:</t> <figure anchor="TWAMPReflectorA">
<name>Micro Session-Reflector Packet Format in Authenticated Mode</n
ame>
<artwork name="" type="" align="left" alt=""><![CDATA[
<t> 0 1 2 3
<figure align="center" anchor="TWAMPReflectorA" 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
title="Micro Session-Reflector Packet Format in Authenticate
d Mode">
<artwork><![CDATA[ 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number | | Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MBZ (12 octets) | | MBZ (12 octets) |
| | | |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp | | Timestamp |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at line 509 skipping to change at line 450
| | | |
| | | |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
. Packet Padding . . Packet Padding .
. . . .
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork> ]]></artwork>
</figure> </figure>
</t> <t>Except for the Sender Micro-session ID field and the Reflector Micr
o-session ID field, all the
<t>Except for the Sender/Reflector Micro-session ID field, all the other fields are the same as defined in <xref target="RFC5357" section
other fields are the same as defined in Section 4.2.1 of TWAMP <xref Format="of" section="4.2.1"/> and follow the same procedure and guidelines defin
target="RFC5357"/>. Therefore, it follows the same procedure and ed therein.</t>
guidelines as defined in Section 4.2.1 of TWAMP <xref <dl spacing="normal">
target="RFC5357"/>.</t>
<t> <dt>Sender Micro-session ID (2 octets in length):</dt><dd>This fie
<list style="symbols"> ld is
<t>Sender Micro-session ID (2-octets in length): It is now
defined to carry the LAG member link identifier of the Sender defined to carry the LAG member link identifier of the Sender
side. In the future, it may be used generically to cover side. In the future, it may be used generically to cover
use-cases beyond LAG. The value of this field MUST be unique use cases beyond LAGs. The value of this field <bcp14>MUST</bcp14>
within a TWAMP session at the Session-Sender.</t> be unique
within a TWAMP session at the Session-Sender.</dd>
<t>Reflector Micro-session ID (2-octets in length): It is now <dt>Reflector Micro-session ID (2 octets in length):</dt><dd>This field is
defined to carry the LAG member link identifier of the Reflector defined to carry the LAG member link identifier of the Reflector
side. In the future, it may be used generically to cover side. In the future, it may be used generically to cover
use-cases beyond LAG. The value of this field MUST be unique use cases beyond LAGs. The value of this field <bcp14>MUST</bcp14>
within a TWAMP session at the Session-Reflector.</t> be unique
</list> within a TWAMP session at the Session-Reflector.</dd>
</t>
</section>
<section title="Reflector Behavior"> </dl>
</section>
<section numbered="true" toc="default">
<name>Reflector Behavior</name>
<t>The micro TWAMP Session-Reflector inherits the behaviors of a <t>The micro TWAMP Session-Reflector inherits the behaviors of a
TWAMP Session-Reflector as defined in Section 4.2 of <xref TWAMP Session-Reflector as defined in <xref target="RFC5357" sectionFo
target="RFC5357"/>.</t> rmat="of" section="4.2"/>.</t>
<t>In addition, when receiving a test packet, the micro TWAMP <t>In addition, when receiving a test packet, the micro TWAMP
Session-Reflector MUST use the receiving member link to correlate Session-Reflector <bcp14>MUST</bcp14> use the receiving member link to correlate
the test packet to a micro TWAMP session. If there is no such a the test packet to a micro TWAMP session. If there is no such a
session, the test packet MUST be discarded. If the Reflector session, the test packet <bcp14>MUST</bcp14> be discarded. If the Refl
Micro-session ID is not zero, the Reflector MUST use the Reflector ector
Micro-session ID is not zero, the Reflector <bcp14>MUST</bcp14> use th
e Reflector
Micro-session ID to validate whether it associates with the Micro-session ID to validate whether it associates with the
receiving member link. If the Reflector Micro-session ID is zero, it receiving member link. If the Reflector Micro-session ID is zero, it
will not be verified. If the validation fails, the test packet MUST will not be verified. If the validation fails, the test packet <bcp14> MUST</bcp14>
be discarded.</t> be discarded.</t>
<t>When sending a response to the received test packet, the micro <t>When sending a response to the received test packet, the micro
TWAMP Session-Reflector MUST copy the Sender member link identifier TWAMP Session-Reflector <bcp14>MUST</bcp14> copy the Sender member lin k identifier
from the received test packet and put it in the Sender Micro-session from the received test packet and put it in the Sender Micro-session
ID field of the reflected test packet (see <xref ID field of the reflected test packet (see Figures <xref target="TWAMP
target="TWAMPReflector"/> and <xref target="TWAMPReflectorA"/>). In Reflector" format="counter"/> and <xref target="TWAMPReflectorA" format="counter
addition, the micro TWAMP Session-Reflector MUST fill the Reflector "/>). In
Micro-session ID field (see <xref target="TWAMPReflector"/> and addition, the micro TWAMP Session-Reflector <bcp14>MUST</bcp14> fill t
<xref target="TWAMPReflectorA"/>) of the reflected test packet with he Reflector
Micro-session ID field (see Figures <xref target="TWAMPReflector" form
at="counter"/> and
<xref target="TWAMPReflectorA" format="counter"/>) of the reflected te
st packet with
the member link identifier that is associated with the micro TWAMP the member link identifier that is associated with the micro TWAMP
session.</t> session.</t>
</section> </section>
</section> </section>
</section> </section>
<section numbered="true" toc="default">
<section title="Applicability"> <name>Applicability</name>
<t>To set up the micro OWAMP sessions, the Control-Client firstly sends <t>To set up the micro OWAMP sessions, the Control-Client sends
the Request-OW-Micro-Sessions command to the OWAMP Server. The OWAMP the Request-OW-Micro-Sessions command to the OWAMP Server. The OWAMP
Server accepts the request, and builds a set of micro sessions for all Server accepts the request and builds a set of micro sessions for all
the member links of the LAG.</t> the member links of the LAG.</t>
<t>For micro TWAMP sessions, a similar set up procedure is used. Then, the
<t>For micro TWAMP sessions, the similar set up procedure as micro OWAMP micro TWAMP Session-Sender sends micro
sessions is used. Then the micro TWAMP Session-Sender sends micro
Session-Sender packets with the Sender Micro-session ID and the Session-Sender packets with the Sender Micro-session ID and the
Reflector Micro-session ID. The micro Session-Reflector checks whether a Reflector Micro-session ID. If the Reflector Micro-session ID field is set , the micro Session-Reflector checks whether a
test packet is received from the member link associated with the correct test packet is received from the member link associated with the correct
micro TWAMP session, if the Reflector Micro-session ID field is set. micro TWAMP session.
When reflecting, the micro TWAMP Session-Reflector copies the Sender When reflecting, the micro TWAMP Session-Reflector copies the Sender
Micro-session ID from the received micro Session-Sender packet to the Micro-session ID from the received micro Session-Sender packet to the
micro Session-Reflector packet, and sets the Reflector Micro-session ID micro Session-Reflector packet; then, it sets the Reflector Micro-session ID
field with the member link identifier that is associated with the micro field with the member link identifier that is associated with the micro
TWAMP session. When receiving the micro TWAMP Session-Reflector packet, TWAMP session. When receiving the micro TWAMP Session-Reflector packet,
the micro Session-Sender uses the Sender Micro-session ID to check the micro Session-Sender uses the Sender Micro-session ID to check
whether the packet is received from the member link associated with the whether the packet is received from the member link associated with the
correct micro TWAMP session. The micro Session-Sender also uses the correct micro TWAMP session. The micro Session-Sender also uses the
Reflector Micro-session ID to validate the Reflector's behavior.</t> Reflector Micro-session ID to validate the Reflector's behavior.</t>
</section> </section>
<section anchor="IANA" numbered="true" toc="default">
<name>IANA Considerations</name>
<section numbered="true" toc="default">
<name>Micro OWAMP-Control Command</name>
<t>IANA has allocated the following command
type from the "OWAMP-Control Command Numbers" registry.</t>
<section anchor="IANA" title="IANA Considerations"> <table anchor="micro_OWAMP" align="left">
<section title="Micro OWAMP-Control Command"> <name>Request-OW-Micro-Sessions Command Number</name>
<t>This document requires the IANA to allocate the following command <thead>
type from OWAMP-Control Command Number Registry.</t> <tr>
<th align="left">Value</th>
<th align="left">Description</th>
<th align="left">Reference</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left">5</td>
<td align="left">Request-OW-Micro-Sessions</td>
<td align="left">This document</td>
</tr>
</tbody>
</table>
<t>
<figure>
<artwork><![CDATA[Value Description Semantics Def
inition
TBD1 Request-OW-Micro-Sessions This document, Section 3.1
]]></artwork>
</figure>
</t>
</section> </section>
<section numbered="true" toc="default">
<name>Micro TWAMP-Control Command</name>
<t>IANA has allocated the following command
type from the "TWAMP-Control Command Numbers" registry.</t>
<section title="Micro TWAMP-Control Command"> <table anchor="micro_TWAMP" align="left">
<t>This document requires the IANA to allocate the following command <name>Request-TW-Micro-Sessions Command Number</name>
type from TWAMP-Control Command Number Registry.</t> <thead>
<tr>
<t> <th align="left">Value</th>
<figure> <th align="left">Description</th>
<artwork><![CDATA[Value Description Semantics Def <th align="left">Reference</th>
inition </tr>
TBD2 Request-TW-Micro-Sessions This document, Section 4.1 </thead>
]]></artwork> <tbody>
</figure> <tr>
</t> <td align="left">11</td>
<td align="left">Request-TW-Micro-Sessions</td>
<td align="left">This document</td>
</tr>
</tbody>
</table>
</section> </section>
</section> </section>
<section anchor="Security" numbered="true" toc="default">
<section anchor="Security" title="Security Considerations"> <name>Security Considerations</name>
<t>This document does not introduce additional security requirements and <t>This document does not introduce additional security requirements and
mechanisms other than those described in <xref target="RFC4656"/>, and mechanisms other than those described in <xref target="RFC4656" format="de
<xref target="RFC5357"/>.</t> fault"/> and
</section> <xref target="RFC5357" format="default"/>.</t>
<section anchor="Acknowledgements" title="Acknowledgements">
<t>The authors would like to thank Fang Xin, Henrik Nydell, Mach Chen,
Min Xiao, Jeff Tantsura, Marcus Ihlar, Richard Foote for the valuable
comments to this work.</t>
</section> </section>
</middle> </middle>
<back> <back>
<references title="Normative References"> <references>
<?rfc include="reference.RFC.2119"?> <name>References</name>
<references>
<?rfc include='reference.RFC.8174'?> <name>Normative References</name>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2
<?rfc include='reference.RFC.8668'?> 119.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
174.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
668.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4
656.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5
357.xml"/>
</references>
<references>
<name>Informative References</name>
<?rfc include='reference.RFC.4656'?> <reference anchor="IEEE802.1AX" target="https://ieeexplore.ieee.org/document/910
5034">
<front>
<title>
IEEE Standard for Local and Metropolitan Area Networks -- Link Aggregation
</title>
<author>
<organization>IEEE</organization>
</author>
<date month="May" year="2020"/>
</front>
<seriesInfo name="IEEE Std" value="802.1AX-2020"/>
<seriesInfo name="DOI" value="10.1109/IEEESTD.2020.9105034"/>
</reference>
<?rfc include='reference.RFC.5357'?> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7799.xml"
/>
</references>
</references> </references>
<references title="Informative References"> <section anchor="Acknowledgements" numbered="false" toc="default">
<reference anchor="IEEE802.1AX"> <name>Acknowledgements</name>
<front> <t>The authors would like to thank <contact fullname="Fang Xin"/>, <contac
<title>IEEE Standard for Local and metropolitan area networks - Link t fullname="Henrik Nydell"/>, <contact fullname="Mach Chen"/>,
Aggregation</title> <contact fullname="Min Xiao"/>, <contact fullname="Jeff Tantsura"/>, <cont
act fullname="Marcus Ihlar"/>, and <contact fullname="Richard Foote"/> for the v
<author> aluable
<organization>IEEE Std. 802.1AX</organization> comments to this work.</t>
</author> </section>
<date month="November" year="2008"/>
</front>
</reference>
<?rfc include='reference.RFC.7799'?>
<?rfc include='reference.RFC.9256'?>
</references>
</back> </back>
</rfc> </rfc>
 End of changes. 128 change blocks. 
337 lines changed or deleted 352 lines changed or added

This html diff was produced by rfcdiff 1.48.