rfc9274xml2.original.xml   rfc9274.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="4"?> <!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" submissionType="IETF" category="
<?rfc compact="yes"?> std" consensus="true" docName="draft-ietf-alto-cost-mode-05" number="9274" ipr="
<?rfc subcompact="no"?> trust200902" updates="7285" obsoletes="" tocInclude="true" tocDepth="4" symRefs=
<rfc category="std" docName="draft-ietf-alto-cost-mode-05" ipr="trust200902" "true" sortRefs="true" xml:lang="en" version="3">
updates="7285">
<front> <front>
<title abbrev="ALTO Cost Mode">A Cost Mode Registry for the <title abbrev="ALTO Cost Mode">A Cost Mode Registry for the
Application-Layer Traffic Optimization (ALTO) Protocol</title> Application-Layer Traffic Optimization (ALTO) Protocol</title>
<seriesInfo name="RFC" value="9274"/>
<author fullname="Mohamed Boucadair" initials="M." surname="Boucadair"> <author fullname="Mohamed Boucadair" initials="M." surname="Boucadair">
<organization>Orange</organization> <organization>Orange</organization>
<address> <address>
<postal> <postal>
<street></street> <street/>
<city>Rennes</city> <city>Rennes</city>
<region/>
<region></region>
<code>35000</code> <code>35000</code>
<country>France</country> <country>France</country>
</postal> </postal>
<email>mohamed.boucadair@orange.com</email> <email>mohamed.boucadair@orange.com</email>
</address> </address>
</author> </author>
<author fullname="Qin Wu" initials="Q." surname="Wu"> <author fullname="Qin Wu" initials="Q." surname="Wu">
<organization>Huawei</organization> <organization>Huawei</organization>
<address> <address>
<postal> <postal>
<street>101 Software Avenue, Yuhua District</street> <extaddr>Yuhua District</extaddr>
<street>101 Software Avenue</street>
<city>Nanjing</city> <city>Nanjing</city>
<region>Jiangsu</region> <region>Jiangsu</region>
<code>210012</code> <code>210012</code>
<country>China</country> <country>China</country>
</postal> </postal>
<email>bill.wu@huawei.com</email> <email>bill.wu@huawei.com</email>
</address> </address>
</author> </author>
<date year="2022" month="July" />
<date /> <area>tsv</area>
<workgroup>alto</workgroup> <workgroup>alto</workgroup>
<keyword>Optimization</keyword> <keyword>Optimization</keyword>
<keyword>service performance</keyword> <keyword>service performance</keyword>
<keyword>cost metric</keyword> <keyword>cost metric</keyword>
<keyword>routing</keyword> <keyword>routing</keyword>
<keyword>computation</keyword> <keyword>computation</keyword>
<keyword>networks</keyword> <keyword>networks</keyword>
<keyword>service-network interaction</keyword> <keyword>service-network interaction</keyword>
<keyword>network programming</keyword> <keyword>network programming</keyword>
<abstract> <abstract>
<t>This document creates a new IANA registry for tracking cost modes <t>This document creates a new IANA registry for tracking cost modes
supported by the Application-Layer Traffic Optimization (ALTO) Protocol. supported by the Application-Layer Traffic Optimization (ALTO) Protocol.
Also, this document relaxes a constraint that was imposed by the ALTO Also, this document relaxes a constraint that was imposed by the ALTO
specification on allowed cost mode values.</t> specification on allowed cost mode values.</t>
<t>This document updates RFC 7285.</t> <t>This document updates RFC 7285.</t>
</abstract> </abstract>
<note title="Editorial Note (To be removed by RFC Editor)">
<t>Please update RFC XXXX statements within the document with the RFC
number to be assigned to this document.</t>
</note>
</front> </front>
<middle> <middle>
<section anchor="introduction" title="Introduction"> <section anchor="introduction" numbered="true" toc="default">
<name>Introduction</name>
<t>The cost mode attribute indicates how costs should be interpreted <t>The cost mode attribute indicates how costs should be interpreted
when communicated in the Application-Layer Traffic Optimization (ALTO) when communicated as described in "Application-Layer Traffic Optimization
Protocol <xref target="RFC7285"></xref>. The base ALTO specification (ALTO)
includes a provision for only two modes: <list style="hanging"> Protocol" <xref target="RFC7285"/>, which
<t hangText="&quot;numerical&quot;:">Indicates that numerical includes a provision for only two modes: </t>
<dl newline="false" spacing="normal">
<dt>"numerical":</dt>
<dd>Indicates that numerical
operations can be performed (e.g., normalization) on the returned operations can be performed (e.g., normalization) on the returned
costs (Section 6.1.2.1 of <xref target="RFC7285"></xref>).</t> costs (<xref target="RFC7285" sectionFormat="of" section="6.1.2.1"/>).
</dd>
<t hangText="&quot;ordinal&quot;:">Indicates that the cost values in <dt>"ordinal":</dt>
<dd>Indicates that the cost values in
a cost map represent ranking (relative to all other values in a cost a cost map represent ranking (relative to all other values in a cost
map), not actual costs (Section 6.1.2.2 of <xref map), not actual costs (<xref target="RFC7285" sectionFormat="of" sect
target="RFC7285"></xref>).</t> ion="6.1.2.2"/>).</dd>
</list></t> </dl>
<t>Additional cost modes are required for specific ALTO deployment cases <t>Additional cost modes are required for specific ALTO deployment cases
(e.g., <xref target="I-D.ietf-alto-path-vector"></xref>). In order to (e.g., <xref target="I-D.ietf-alto-path-vector"/>). In order to
allow for such use cases, this document relaxes the constraint imposed allow for such use cases, this document relaxes the constraint imposed
by the base ALTO specification on allowed cost modes (<xref by the base ALTO specification on allowed cost modes (<xref target="anupda
target="anupdate"></xref>) and creates a new ALTO registry to track new te"/>) and creates a new ALTO registry to track new
cost modes (<xref target="IANA"></xref>).</t> cost modes (<xref target="IANA"/>).</t>
<t>The mechanisms defined in <xref target="RFC7285"/> are used to
<t>The mechanisms defined in <xref target="RFC7285"></xref> are used to
advertise the support of new cost modes for specific cost metrics. Refer advertise the support of new cost modes for specific cost metrics. Refer
to <xref target="bc"></xref> for more details.</t> to <xref target="bc"/> for more details.</t>
</section> </section>
<section anchor="notation" numbered="true" toc="default">
<section anchor="notation" title="Terminology"> <name>Terminology</name>
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", <t>
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQU
"OPTIONAL" in this document are to be interpreted as described in BCP 14 IRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
<xref target="RFC2119"></xref><xref target="RFC8174"></xref> when, and NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>
only when, they appear in all capitals, as shown here.</t> RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to
<t>This document makes use of the terms defined in <xref be interpreted as
target="RFC7285"></xref>.</t> 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>This document makes use of the terms defined in <xref target="RFC7285"/
>.</t>
</section> </section>
<section anchor="anupdate" numbered="true" toc="default">
<section anchor="anupdate" title="Updates to RFC7285"> <name>Updates to RFC 7285</name>
<t></t> <t/>
<section>
<section title="Updates to Section 6.1.2 of RFC7285"> <name>Updates to Section 6.1.2 of RFC 7285</name>
<t>This document updates Section 6.1.2 of <xref <t>This document updates <xref target="RFC7285" sectionFormat="of" secti
target="RFC7285"></xref> as follows:</t> on="6.1.2"/> as follows:</t>
<t>OLD:</t>
<t>OLD:<list style="empty"> <ul empty="true" spacing="normal">
<t>The cost mode attribute indicates how costs should be <li>The cost mode attribute indicates how costs should be
interpreted. Specifically, the cost mode attribute indicates interpreted. Specifically, the cost mode attribute indicates
whether returned costs should be interpreted as numerical values whether returned costs should be interpreted as numerical values
or ordinal rankings.</t> or ordinal rankings.</li>
<li>It is important to communicate such information to ALTO
<t>It is important to communicate such information to ALTO
clients, as certain operations may not be valid on certain costs clients, as certain operations may not be valid on certain costs
returned by an ALTO server. For example, it is possible for an returned by an ALTO server. For example, it is possible for an
ALTO server to return a set of IP addresses with costs indicating ALTO server to return a set of IP addresses with costs indicating
a ranking of the IP addresses. Arithmetic operations that would a ranking of the IP addresses. Arithmetic operations that would
make sense for numerical values, do not make sense for ordinal make sense for numerical values, do not make sense for ordinal
rankings. ALTO clients may handle such costs differently.</t> rankings. ALTO clients may handle such costs differently.</li>
<li>Cost modes are indicated in protocol messages as strings.</li>
<t>Cost modes are indicated in protocol messages as strings.</t> </ul>
</list></t> <t>NEW:</t>
<ul empty="true" spacing="normal">
<t>NEW:<list style="empty"> <li>The cost mode attribute indicates how costs should be
<t>The cost mode attribute indicates how costs should be
interpreted. Two cost modes (numerical values and ordinal interpreted. Two cost modes (numerical values and ordinal
rankings) are defined, but additional cost modes can be defined in rankings) are defined, but additional cost modes can be defined in
the future.</t> the future.</li>
<li>It is important to communicate such information to ALTO
<t>It is important to communicate such information to ALTO
clients, as certain operations may not be valid on certain costs clients, as certain operations may not be valid on certain costs
returned by an ALTO server. For example, it is possible for an returned by an ALTO server. For example, it is possible for an
ALTO server to return a set of IP addresses with costs indicating ALTO server to return a set of IP addresses with costs indicating
a ranking of the IP addresses. Arithmetic operations that would a ranking of the IP addresses. Arithmetic operations that would
make sense for numerical values, do not make sense for ordinal make sense for numerical values, do not make sense for ordinal
rankings. ALTO clients may handle such costs differently.</t> rankings. ALTO clients may handle such costs differently.</li>
<li>Cost modes are indicated in protocol messages as strings.</li>
<t>Cost modes are indicated in protocol messages as strings.</t> <li>For any future documents that defines a new cost mode, indicating
whether that new cost mode applies to all
<t>Future documents that define a new cost mode are strongly or a subset of cost metrics is strongly recommended. This recommenda
recommended to indicate whether that new cost mode applies to all tion is meant to
or a subset of cost metrics. This recommendation is meant to prevent nondeterministic behaviors that may result in presenting
prevent non-deterministic behaviors that may result in presenting
a cost mode with a specific metric, while such an association does a cost mode with a specific metric, while such an association does
not make sense or can't be unambiguously interpreted by ALTO not make sense or can't be unambiguously interpreted by ALTO
implementations. </t> implementations. </li>
<li>If the definition of a cost mode does not indicate whether that
<t>If the definition of a cost mode does not indicate whether that
cost mode applies to a subset of cost metrics, ALTO cost mode applies to a subset of cost metrics, ALTO
implementations MUST be prepared to accept that cost mode for any implementations <bcp14>MUST</bcp14> be prepared to accept that cost
cost metric. </t> mode for any
</list></t> cost metric. </li>
</ul>
<t></t> <t/>
</section> </section>
<section anchor="up2" numbered="true" toc="default">
<name>Updates to Section 10.5 of RFC 7285</name>
<t>This document updates <xref target="RFC7285" sectionFormat="of" secti
on="10.5"/> as follows:</t>
<t>OLD:</t>
<ul empty="true" spacing="normal">
<li>A cost mode is encoded as a string. The string <bcp14>MUST</bcp14>
have a
value of either "numerical" or "ordinal".</li>
</ul>
<section anchor="up2" title="Updates to Section 10.5 of RFC7285"> <t>NEW:</t>
<t>This document updates Section 10.5 of <xref <ul empty="true" spacing="normal">
target="RFC7285"></xref> as follows:</t> <li>A cost mode is encoded as a string. The string <bcp14>MUST</bcp14>
be no more
<t>OLD:<list style="empty"> than 32 characters, and it <bcp14>MUST NOT</bcp14> contain character
<t>A cost mode is encoded as a string. The string MUST have a s other than
value of either "numerical" or "ordinal".</t>
</list></t>
<t>NEW:<list style="empty">
<t>A cost mode is encoded as a string. The string MUST be no more
than 32 characters, and it MUST NOT contain characters other than
US-ASCII alphanumeric characters (U+0030-U+0039, U+0041-U+005A, US-ASCII alphanumeric characters (U+0030-U+0039, U+0041-U+005A,
and U+0061-U+007A), the hyphen-minus ('-', U+002D), the colon and U+0061-U+007A), the hyphen-minus ('-', U+002D), the colon
(':', U+003A), or the low line ('_', U+005F). Cost modes reserved (':', U+003A), or the low line ('_', U+005F). Cost modes reserved
for Private Use are prefixed with "priv:" (<xref for Private Use are prefixed with "priv:" (<xref target="IANA"/>). O
target="IANA"></xref>). Otherwise, the cost mode MUST have a value therwise, the cost mode <bcp14>MUST</bcp14> have a value
that is listed in the registry created in <xref that is listed in the registry created in <xref target="IANA"/> of [
target="IANA"></xref> of RFCXXXX.</t> RFC9274].</li>
</list></t> </ul>
<t/>
<t></t>
</section> </section>
</section> </section>
<section anchor="bc" numbered="true" toc="default">
<section anchor="bc" title="Backward Compatibility Considerations"> <name>Backward Compatibility Considerations</name>
<t>ALTO servers that support new cost modes for specific cost metrics <t>ALTO servers that support new cost modes for specific cost metrics
will use the mechanism specified in Section 9.2 of <xref will use the mechanism specified in <xref target="RFC7285" sectionFormat="
target="RFC7285"></xref> to advertise their capabilities. ALTO clients of" section="9.2"/> to advertise their capabilities. ALTO clients
(including legacy) will use that information to specify cost constraints (including legacy) will use that information to specify cost constraints
in their requests (e.g., indicate a cost metric and a cost mode). An in their requests (e.g., indicate a cost metric and a cost mode). An
example of such a behavior is depicted in Section 9.2.3 of <xref example of such a behavior is depicted in <xref target="RFC7285" sectionFo
target="RFC7285"></xref>.</t> rmat="of" section="9.2.3"/>.</t>
<t>If an ALTO client includes a cost mode that is not supported by an <t>If an ALTO client includes a cost mode that is not supported by an
ALTO server, the server indicates such an error with the error code ALTO server, the server indicates such an error with the error code
E_INVALID_FIELD_VALUE as per Section 8.5.2 of <xref E_INVALID_FIELD_VALUE as per <xref target="RFC7285" sectionFormat="of" sec
target="RFC7285"></xref>. In practice, legacy ALTO servers will reply tion="8.5.2"/>. In practice, legacy ALTO servers will reply
with the error code E_INVALID_FIELD_VALUE to requests that include a with the error code E_INVALID_FIELD_VALUE to requests that include a
cost type other than "numerical" or "ordinal" for the "routingcost" cost cost type other than "numerical" or "ordinal" for the "routingcost" cost
metric.</t> metric.</t>
<t>The encoding constraints in <xref target="up2"/> do not
<t>The encoding constraints in <xref target="up2"></xref> do not
introduce any interoperability issue given that currently implemented introduce any interoperability issue given that currently implemented
cost modes adhere to these constrains (mainly, those in <xref cost modes adhere to these constrains (mainly, those in <xref target="RFC7
target="RFC7285"></xref> and <xref 285"/> and <xref target="I-D.ietf-alto-path-vector"/>).</t>
target="I-D.ietf-alto-path-vector"></xref>).</t>
</section> </section>
<section anchor="IANA" numbered="true" toc="default">
<section anchor="IANA" title="IANA Considerations"> <name>IANA Considerations</name>
<t>This document requests IANA to create a new subregistry entitled <t>IANA has created the new "ALTO Cost Modes" subregistry
"ALTO Cost Modes" under the "Application-Layer Traffic Optimization within the "Application-Layer Traffic Optimization
(ALTO) Protocol" registry available at <xref target="ALTO"></xref>.</t> (ALTO) Protocol" registry available at <xref target="ALTO"/>.</t>
<t>The assignment policy for this subregistry is "IETF Review" (<xref targ
<t>The assignment policy for this subregistry is "IETF Review" (Section et="RFC8126" sectionFormat="of" section="4.8"/>).</t>
4.8 of <xref target="RFC8126"></xref>).</t>
<t>Requests to register a new ALTO cost mode must include the following <t>Requests to register a new ALTO cost mode must include the following
information:<list style="hanging"> information:</t>
<t hangText="Identifier:">The name of the ALTO cost mode. Refer to <dl newline="false" spacing="normal">
<xref target="up2"></xref> for more details on allowed encoding.</t> <dt>Identifier:</dt>
<dd>The name of the ALTO cost mode. Refer to
<t hangText="Description:">A short description of the requested ALTO <xref target="up2"/> for more details on allowed encoding.</dd>
cost mode.</t> <dt>Description:</dt>
<dd>A short description of the requested ALTO
<t hangText="Intended Semantics:">A reference to where the semantic cost mode.</dd>
of the requested cost mode is defined.</t> <dt>Intended Semantics:</dt>
<dd>A reference to where the semantic
<t hangText="Reference:">A reference to the document that registers of the requested cost mode is defined.</dd>
the requested cost mode.</t> <dt>Reference:</dt>
</list></t> <dd>A reference to the document that registers
the requested cost mode.</dd>
</dl>
<t>Cost modes prefixed with "priv:" are reserved for Private Use <t>Cost modes prefixed with "priv:" are reserved for Private Use
(Section 4.1 of <xref target="RFC8126"></xref>). This document requests (<xref target="RFC8126" sectionFormat="of" section="4.1"/>).
IANA to add the following note to the new subregistry:</t> IANA has added the following note to the new subregistry:</t>
<blockquote>
Identifiers prefixed with "priv:" are reserved
for Private Use (RFC 9274, <xref target="IANA"/>).</blockquote>
<t>The subregistry is initially populated with the following values:</t>
<table anchor="subregistry" align="center">
<name>ALTO Cost Modes</name>
<thead>
<tr>
<th rowspan="1" colspan="1">Identifier</th>
<th rowspan="1" colspan="1">Description</th>
<th rowspan="1" colspan="1">Intended Semantics</th>
<th rowspan="1" colspan="1">Reference</th>
</tr>
</thead>
<t><list style="hanging"> <tbody>
<t hangText="Note:">Identifiers prefixed with 'priv:' are reserved
for Private Use (see [RFCXXXX], <xref target="IANA"></xref>).</t>
</list></t>
<t></t> <tr>
<td>numerical</td>
<td>Indicates that numerical operations can be performed on the returned costs
</td>
<td><xref target="RFC7285" sectionFormat="of" section="6.1.2.1"/></td>
<td>RFC 9274</td>
</tr>
<t>The subregistry is initially populated with the following values:</t> <tr>
<td>ordinal</td>
<td>Indicates that the cost values in a cost map represent ranking</td>
<td><xref target="RFC7285" sectionFormat="of" section="6.1.2.2"/></td>
<td>RFC 9274</td>
</tr>
<t><figure> </tbody>
<artwork><![CDATA[ +============+=============================+===== </table>
=======+===========+
| Identifier | Description | Intended | Reference |
| | | Semantics | |
+============+=============================+============+===========+
| numerical | Indicates that numerical | Section | RFCXXXX |
| | operations can be performed | 6.1.2.1 of | |
| | on the returned costs | RFC7285 | |
+------------+-----------------------------+------------+-----------+
| ordinal | Indicates that the cost | Section | RFCXXXX |
| | values in a cost map | 6.1.2.2 of | |
| | represent ranking | RFC7285 | |
+------------+-----------------------------+------------+-----------+]]></art
work>
</figure></t>
</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 new concerns other than those <t>This document does not introduce new concerns other than those
already discussed in Section 15 of <xref target="RFC7285"></xref>.</t> already discussed in <xref target="RFC7285" sectionFormat="of" section="15
</section> "/>.</t>
<section anchor="ack" title="Acknowledgements">
<t>Many thanks to Benjamin Kaduk for spotting the issue during the
review of <xref target="I-D.ietf-alto-path-vector"></xref>.</t>
<t>Thanks to Adrian Farrel, Dhruv Dhody, Luis Miguel Contreras Murillo,
Sabine Randriamasy, and Qiao Xiang for the review and comments.</t>
<t>Special thanks to Kai Gao for Shepherding the document.</t>
<t>Thanks to Martin Duke for the AD review.</t>
<t>Thanks to Roni Even for the gen-art review, Jaime Jimenez for the
artart review, and Stephen Farrell for the secdir review.</t>
<t>Thanks to Robert Wilton, Lars Eggert, Francesca Palombini, Roman
Danyliw, Paul Wouters, and Murray Kucherawy for the IESG review.</t>
</section> </section>
</middle> </middle>
<back> <back>
<references title="Normative References">
<?rfc include='reference.RFC.2119'?>
<?rfc include='reference.RFC.8174'?> <displayreference target="I-D.ietf-alto-path-vector" to="ALTO-PV"/>
<references>
<name>References</name>
<references>
<name>Normative References</name>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.2119.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8174.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.7285.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8126.xml"/>
</references>
<references>
<name>Informative References</name>
<?rfc include='reference.RFC.7285'?> <!-- [I-D.ietf-alto-path-vector] companion document in queue-->
<?rfc include='reference.RFC.8126'?> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-ietf-alto-path-
</references> vector.xml"/>
<references title="Informative References"> <!--
<?rfc include='reference.I-D.ietf-alto-path-vector'?> <reference anchor='RFCYYY1' target="https://www.rfc-editor.org/info/rfcYYY1">
<front>
<title>An Extension for Application-Layer Traffic Optimization (ALTO): Path Vect
or</title>
<author initials='K' surname='Gao' fullname='Kai Gao'>
<organization />
</author>
<author initials='Y' surname='Lee' fullname='Young Lee'>
<organization />
</author>
<author initials='S' surname='Randriamasy' fullname='Sabine Randriamasy'>
<organization />
</author>
<author initials='Y' surname='Yang' fullname='Y. Yang'>
<organization />
</author>
<author initials='J' surname='Zhang' fullname='Jingxuan Zhang'>
<organization />
</author>
<date year='2021' month='February' day='22' />
</front>
<seriesInfo name="RFC" value="YYY1"/>
<seriesInfo name="DOI" value="10.17487/RFCYYY1"/>
</reference>
-->
<reference anchor="ALTO" <reference anchor="ALTO" target="https://www.iana.org/assignments/alto-pr
target="https://www.iana.org/assignments/alto-protocol/alto-pro otocol/">
tocol.xhtml"> <front>
<front> <title>Application-Layer Traffic Optimization (ALTO)
<title>Application-Layer Traffic Optimization (ALTO)
Protocol</title> Protocol</title>
<author>
<organization>IANA</organization>
</author>
</front>
</reference>
</references>
</references>
<author> <!-- [rfced] Please review the "Inclusive Language" portion of the online
<organization></organization> Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language>
</author> and let us know if any changes are needed. Note that our script did not flag any
words or phrases.
-->
<section anchor="ack" numbered="false" toc="default">
<name>Acknowledgements</name>
<t>Many thanks to <contact fullname="Benjamin Kaduk"/> for spotting the
issue during the review of <xref target="I-D.ietf-alto-path-vector"/>.</t>
<t>Thanks to <contact fullname="Adrian Farrel"/>,
<contact fullname="Dhruv Dhody"/>,
<contact fullname="Luis Miguel Contreras Murillo"/>,
<contact fullname="Sabine Randriamasy"/>, and
<contact fullname="Qiao Xiang"/> for the review and comments.</t>
<t>Special thanks to <contact fullname="Kai Gao"/> for Shepherding the doc
ument.</t>
<t>Thanks to <contact fullname="Martin Duke"/> for the AD review.</t>
<t>Thanks to <contact fullname="Roni Even"/> for the gen-art review, <cont
act fullname="Jaime Jimenez"/> for the
artart review, and <contact fullname="Stephen Farrell"/> for the secdir re
view.</t>
<t>Thanks to <contact fullname="Robert Wilton"/>, <contact fullname="Lars
Eggert"/>, <contact fullname="Francesca Palombini"/>, <contact fullname="Roman
Danyliw"/>, <contact fullname="Paul Wouters"/>, and <contact fullname="Mur
ray Kucherawy"/> for the IESG review.</t>
</section>
<date day="02" month="March" year="2022" />
</front>
</reference>
</references>
</back> </back>
</rfc> </rfc>
 End of changes. 70 change blocks. 
240 lines changed or deleted 266 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/