rfc8736xml2.original.xml   rfc8736.xml 
<?xml version="1.0" encoding="US-ASCII"?> <?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd"> <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<rfc category="std" docName="draft-ietf-pim-reserved-bits-04" <rfc number="8736" consensus="true" xmlns:xi="http://www.w3.org/2001/XInclude"
category="std" docName="draft-ietf-pim-reserved-bits-04"
ipr="trust200902" obsoletes="6166" ipr="trust200902" obsoletes="6166"
updates="3973, 5015, 5059, 6754, 7761, 8364"> updates="3973, 5015, 5059, 6754, 7761, 8364"
<?rfc toc="yes"?> submissionType="IETF"
xml:lang="en" tocInclude="true" sortRefs="true" symRefs="true" version="3">
<?rfc compact="yes"?> <!-- xml2rfc v2v3 conversion 2.36.0 -->
<?rfc subcompact="no"?>
<?rfc symrefs="yes"?>
<front> <front>
<title abbrev="PIM Type Extension and Reserved Bits">PIM Message Type <title abbrev="PIM Type Extension and Reserved Bits">PIM Message Type
Space Extension and Reserved Bits</title> Space Extension and Reserved Bits</title>
<seriesInfo name="RFC" value="8736"/>
<author fullname="Stig Venaas" initials="S." surname="Venaas"> <author fullname="Stig Venaas" initials="S." surname="Venaas">
<organization>Cisco Systems, Inc.</organization> <organization>Cisco Systems, Inc.</organization>
<address> <address>
<postal> <postal>
<street>Tasman Drive</street> <street>Tasman Drive</street>
<city>San Jose</city> <city>San Jose</city>
<region>CA</region>
<code>CA 95134</code> <code>95134</code>
<country>United States of America</country>
<country>USA</country>
</postal> </postal>
<email>stig@cisco.com</email> <email>stig@cisco.com</email>
</address> </address>
</author> </author>
<author fullname="Alvaro Retana" initials="A." surname="Retana"> <author fullname="Alvaro Retana" initials="A." surname="Retana">
<organization>Futurewei Technologies, Inc.</organization> <organization>Futurewei Technologies, Inc.</organization>
<address> <address>
<postal> <postal>
<street>2330 Central Expressway</street> <street>2330 Central Expressway</street>
<city>Santa Clara</city> <city>Santa Clara</city>
<region>CA</region>
<region/> <code>95050</code>
<country>United States of America</country>
<code>CA 95050</code>
<country>USA</country>
</postal> </postal>
<phone/> <phone/>
<facsimile/>
<email>alvaro.retana@futurewei.com</email> <email>alvaro.retana@futurewei.com</email>
<uri/> <uri/>
</address> </address>
</author> </author>
<date month="February" year="2020"/>
<date day="19" month="September" year="2019"/>
<area>Routing</area> <area>Routing</area>
<keyword>Multicast</keyword> <keyword>Multicast</keyword>
<abstract> <abstract>
<t>The PIM version 2 messages share a common message header format. The <t>The PIM version 2 messages share a common message header format. The
common header definition contains eight reserved bits. This document common header definition contains eight reserved bits. This document
specifies how these bits may be used by individual message types, and specifies how these bits may be used by individual message types and
creates a registry containing the per-message-type usage. This document creates a registry containing the per-message-type usage. This document
also extends the PIM type space by defining three new message types. For also extends the PIM type space by defining three new message types. For
each of the new types, four of the previously reserved bits are used to each of the new types, four of the previously reserved bits are used to
form an extended type range.</t> form an extended type range.</t>
<t>This document Updates RFC 7761 and RFC 3973 by defining the use of <t>This document updates RFCs 7761 and 3973 by defining the use of
the currently Reserved field in the PIM common header. This document the currently Reserved field in the PIM common header. This document
further updates RFC 7761 and RFC 3973, along with RFC 5015, RFC 5059, further updates RFCs 7761 and 3973, along with RFCs 5015, 5059,
RFC 6754 and RFC 8364, by specifying the use of the currently Reserved 6754, and 8364, by specifying the use of the currently reserved
bits for each PIM message.</t> bits for each PIM message.</t>
<t>This document obsoletes RFC 6166.</t> <t>This document obsoletes RFC 6166.</t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section title="Introduction"> <section numbered="true" toc="default">
<name>Introduction</name>
<t>The PIM version 2 messages share a common message header format <t>The PIM version 2 messages share a common message header format
defined in the PIM Sparse Mode <xref target="RFC7761"/> specification. defined in the PIM Sparse Mode specification <xref target="RFC7761" format
The common header definition contains eight Reserved bits. While all ="default"/>.
The common header definition contains eight reserved bits. While all
message types use this common header, there is no document formally message types use this common header, there is no document formally
specifying that these bits are to be used per message type.</t> specifying that these bits are to be used per message type.</t>
<t>This document refers to the bits specified as "reserved" in the common
<t>This document refers to the bits specified as Reserved in the common PIM header <xref target="RFC7761" format="default"/> as "PIM message type
PIM header <xref target="RFC7761"/> as PIM message type Flag Bits, or Flag Bits" or,
simply Flag Bits, and it specifies that they are to be separately used simply, "Flag Bits", and it specifies that they are to be separately used
on a per-message-type basis. It creates a registry containing the on a per-message-type basis. It creates a registry containing the
per-message-type usage. </t> per-message-type usage. </t>
<t>This document updates <xref target="RFC7761" format="default"/> and
<t>This document Updates <xref target="RFC7761"/> and <xref <xref target="RFC3973" format="default"/> by defining the use of the
target="RFC3973"/> by defining the use of the currently Reserved field currently Reserved field
in the PIM common header. This document further updates <xref in the PIM common header. This document further updates <xref
target="RFC7761"/> and <xref target="RFC3973"/>, along with <xref target="RFC7761" format="default"/> and <xref target="RFC3973"
target="RFC5015"/>, <xref target="RFC5059"/>, <xref target="RFC6754"/> format="default"/>, along with <xref target="RFC5015"
and <xref target="RFC8364"/>, by specifying the use of the currently format="default"/>, <xref target="RFC5059" format="default"/>, <xref
Reserved bits for each PIM message.</t> target="RFC6754" format="default"/>,
and <xref target="RFC8364" format="default"/>, by specifying the use of th
e currently
reserved bits for each PIM message.</t>
<t>The currently defined PIM message types are in the range from 0 to <t>The currently defined PIM message types are in the range from 0 to
15. That type space is almost exhausted. Message type 15 was reserved by 15. That type space is almost exhausted. Message type 15 was reserved by
<xref target="RFC6166"/> for type space extension. In <xref <xref target="RFC6166" format="default"/> for type space extension. In
target="ext"/>, this document specifies the use of the Flag Bits for <xref target="ext" format="default"/>, this document specifies the use
message types 13, 14 and 15 in order to extend the PIM type space. This of the Flag Bits for
document Obsoletes <xref target="RFC6166"/>.</t> message types 13, 14, and 15 in order to extend the PIM type space. This
document obsoletes <xref target="RFC6166" format="default"/>.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="Conventions used in this document"> <name>Conventions Used in This Document</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>",
"OPTIONAL" in this document are to be interpreted as described in BCP 14 "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
<xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
they appear in all capitals, as shown here.</t> "<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 numbered="true" toc="default">
<section title="PIM header common format"> <name>PIM Header Common Format</name>
<t>The common PIM header is defined in section 4.9 of <xref <t>The common PIM header is defined in <xref
target="RFC7761"/>. This document updates the definition of the Reserved target="RFC7761" sectionFormat="of" section="4.9"/>. This document
field and refers to that field as PIM message type Flag Bits, or simply updates the definition of the Reserved
Flag Bits. The new common header format is as below. <figure field and refers to that field as "PIM message type Flag Bits" or, simply,
title="Figure 1: New Common Header"> "Flag Bits". The new common header format is as below. </t>
<artwork><![CDATA[ <figure>
<name>New Common Header</name>
<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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|PIM Ver| Type | Flag Bits | Checksum | |PIM Ver| Type | Flag Bits | Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork> ]]></artwork>
</figure></t> </figure>
<t>The Flag Bits field is defined in <xref target="flagbits" format="defau
<t>The Flag Bits field is defined in <xref target="flagbits"/>. All lt"/>. All
other fields remain unchanged.</t> other fields remain unchanged.</t>
</section> </section>
<section anchor="flagbits" numbered="true" toc="default">
<section anchor="flagbits" title="Flag Bit definitions"> <name>Flag Bit Definitions</name>
<t>Unless otherwise specified, all the Flag Bits for each PIM type are <t>Unless otherwise specified, all the flag bits for each PIM type are
Reserved <xref target="RFC8126"/>. They MUST be set to zero on Reserved <xref target="RFC8126" format="default"/>.
transmission, and they MUST be ignored upon receipt. The specification They <bcp14>MUST</bcp14> be set to zero on
of a new PIM type MUST indicate whether the bits should be treated transmission, and they <bcp14>MUST</bcp14> be ignored upon receipt. The sp
ecification
of a new PIM type <bcp14>MUST</bcp14> indicate whether the bits should be
treated
differently.</t> differently.</t>
<t>When defining flag bits, it is helpful to have a well-defined way of
<t>When defining Flag Bits, it is helpful to have a well-defined way of referring to a particular bit. The most significant of the flag bits,
referring to a particular bit. The most significant of the Flag Bits, the bit immediately following the Type field, is referred to as bit 7.
the bit immediately following the type field is referred to as bit 7. The least significant, the bit right in front of the Checksum field, is
The least significant, the bit right in front of the checksum field is
referred to as bit 0. This is shown in the diagram below.</t> referred to as bit 0. This is shown in the diagram below.</t>
<figure>
<t><figure title="Figure 2: Flag Bits"> <name>Flag Bits</name>
<artwork><![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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|PIM Ver| Type |7 6 5 4 3 2 1 0| Checksum | |PIM Ver| Type |7 6 5 4 3 2 1 0| Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork> ]]></artwork>
</figure></t> </figure>
<section numbered="true" toc="default">
<section title="Flag Bits for Type 4 (Bootstrap)"> <name>Flag Bits for Type 4 (Bootstrap)</name>
<t>PIM message type 4 (Bootstrap) <xref target="RFC5059"/> defines <t>PIM message type 4 (Bootstrap) <xref target="RFC5059" format="default
Flag Bit 7 as No-Forward. The usage of the bit is defined in that "/> defines
document. The remaining Flag Bits are Reserved.</t> flag bit 7 as No-Forward. The usage of the bit is defined in that
document. The remaining flag bits are reserved.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="Flag Bits for Type 10 (DF Election)"> <name>Flag Bits for Type 10 (DF Election)</name>
<t>PIM message type 10 (DF Election) <xref target="RFC5015"/> <t>PIM message type 10 (DF Election) <xref
specifies that the four most significant Flag Bits (bits 4-7) are to target="RFC5015" format="default"/>
be used as a Subtype. The usage of those bits is defined in that specifies that the four most significant flag bits (bits 4-7) are to
document. The remaining Flag Bits are Reserved.</t> be used as a subtype. The usage of those bits is defined in that
document. The remaining flag bits are reserved.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="Flag Bits for Type 12 (PFM)"> <name>Flag Bits for Type 12 (PFM)</name>
<t>PIM message type 12 (PFM) <xref target="RFC8364"/> defines Flag Bit <t>PIM message type 12 (PIM Flooding Mechanism) <xref
target="RFC8364" format="default"/> defines flag bit
7 as No-Forward. The usage of the bit is defined in that document. The 7 as No-Forward. The usage of the bit is defined in that document. The
remaining Flag Bits are Reserved.</t> remaining flag bits are reserved.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="Flag Bits for Types 13, 14 and 15 (Type Space Extension)"> <name>Flag Bits for Types 13, 14, and 15 (Type Space Extension)</name>
<t>These types and the corresponding Flag Bits are defined in <xref <t>These types and the corresponding flag bits are defined in <xref
target="ext"/>.</t> target="ext" format="default"/>.</t>
</section> </section>
</section> </section>
<section anchor="ext" numbered="true" toc="default">
<section anchor="ext" title="PIM Type Space Extension"> <name>PIM Type Space Extension</name>
<t>This document defines types 13, 14 and 15, such that each of these <t>This document defines types 13, 14, and 15, such that each of these
types has 16 subtypes, providing a total of 48 subtypes available for types has 16 subtypes, providing a total of 48 subtypes available for
future PIM extensions. This is achieved by defining a new SubType field future PIM extensions. This is achieved by defining a new Subtype field
(see Figure 3) using the four most significant Flag Bits (bits 4-7). The (see Figure 3) using the four most significant flag bits (bits 4-7). The
notation type.subtype is used to reference these new extended types. The notation type.subtype is used to reference these new extended types. The
remaining four Flag Bits (bits 0-3) are Reserved to be used by each remaining four flag bits (bits 0-3) are reserved to be used by each
extended type (abbreviated as FB below). </t> extended type (abbreviated as FB below). </t>
<figure>
<t><figure title="Figure 3: Sub-Types"> <name>Subtypes</name>
<artwork><![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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|PIM Ver| Type |SubType| FB | Checksum | |PIM Ver| Type |Subtype| FB | Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork> ]]></artwork>
</figure></t> </figure>
</section> </section>
<section numbered="true" toc="default">
<section title="Security Considerations"> <name>Security Considerations</name>
<t>This document clarifies the use of the Flag Bits in the common PIM <t>This document clarifies the use of the flag bits in the common PIM
header and it extends the PIM type space. As such, there is no impact on header, and it extends the PIM type space. As such, there is no impact on
security or changes to the considerations in <xref target="RFC7761"/> security or changes to the considerations in <xref target="RFC7761" format
and <xref target="RFC3973"/>.</t> ="default"/>
and <xref target="RFC3973" format="default"/>.</t>
</section> </section>
<section anchor="IANA" numbered="true" toc="default">
<name>IANA Considerations</name>
<section anchor="IANA" title="IANA Considerations"> <t>This document updates the "PIM Message Types" registry to indicate
<t>This document updates the PIM Message Types registry to indicate which flag bits are defined for use by each of the PIM message types.
which Flag Bits are defined for use by each of the PIM message types. The registry now references this document. The registration policy remains
The Registry should now reference this document instead of <xref IETF Review <xref target="RFC8126" format="default"/>. Assignments into
target="RFC6166"/>. The Registration Policy remains IETF Review <xref this registry <bcp14>MUST</bcp14> define any
target="RFC8126"/>. Assignments into this registry MUST define any non-default usage (see <xref target="flagbits" format="default"/>) of
non-default usage (see <xref target="flagbits"/>) of the Flag Bits in the flag bits in addition to the type.</t>
addition to defining the Type.</t>
<t>The updated PIM Message Types registry is shown below.</t>
<t><figure title="Table 1: Updated PIM Message Types Registry">
<artwork><![CDATA[
Type Name Flag Bits Reference
0 Hello 0-7: Reserved [RFC3973][RFC7761]
1 Register 0-7: Reserved [RFC7761]
2 Register Stop 0-7: Reserved [RFC7761]
3 Join/Prune 0-7: Reserved [RFC3973][RFC7761]
4 Bootstrap 0-6: Reserved [RFC5059][RFC7761]
7: No-Forward [RFC5059]
5 Assert 0-7: Reserved [RFC3973][RFC7761]
6 Graft 0-7: Reserved [RFC3973]
7 Graft-Ack 0-7: Reserved [RFC3973]
8 Candidate RP 0-7: Reserved [RFC7761]
Advertisement
9 State Refresh 0-7: Reserved [RFC3973]
10 DF Election 0-3: Reserved [RFC5015]
4-7: Subtype [RFC5015]
11 ECMP Redirect 0-7: Reserved [RFC6754]
12 PIM Flooding Mechanism 0-6: Reserved [RFC8364]
7: No-Forward [RFC8364]
13.0-15.15 Unassigned 0-3: Unassigned [this document] <t>The updated "PIM Message Types" registry is shown below.</t>
]]></artwork> <table anchor="PIM-registry">
</figure>The Unassigned types above, as explained in <xref <name>Updated PIM Message Types Registry</name>
target="ext"/>, use the extended type notation of type.subtype. Each <thead>
extended type only has 4 Flag Bits available. New extended message types <tr>
should be assigned conscutively, starting with 13.0, then 13.1, etc.</t> <th>Type</th>
<th>Name</th>
<th>Flag Bits</th>
<th>Reference</th>
</tr>
</thead>
<tbody>
<tr>
<td>0</td>
<td>Hello</td>
<td>0-7: Reserved</td>
<td><xref target="RFC3973" format="default"/><xref target="RFC7761" format
="default"/></td>
</tr>
<tr>
<td>1</td>
<td>Register</td>
<td>0-7: Reserved</td>
<td><xref target="RFC7761" format="default"/></td>
</tr>
<tr>
<td>2</td>
<td>Register Stop</td>
<td>0-7: Reserved</td>
<td><xref target="RFC7761" format="default"/></td>
</tr>
<tr>
<td>3</td>
<td>Join/Prune</td>
<td>0-7: Reserved</td>
<td><xref target="RFC3973" format="default"/><xref target="RFC7761" format
="default"/></td>
</tr>
<tr>
<td rowspan="2">4</td>
<td rowspan="2">Bootstrap</td>
<td>0-6: Reserved</td>
<td><xref target="RFC5059" format="default"/><xref target="RFC7761"
format="default"/></td>
</tr>
<tr>
<td>7: No-Forward</td>
<td><xref target="RFC5059" format="default"/></td>
</tr>
<tr>
<td>5</td>
<td>Assert</td>
<td>0-7: Reserved</td>
<td><xref target="RFC3973" format="default"/><xref target="RFC7761" format
="default"/></td>
</tr>
<tr>
<td>6</td>
<td>Graft</td>
<td>0-7: Reserved</td>
<td><xref target="RFC3973" format="default"/></td>
</tr>
<tr>
<td>7</td>
<td>Graft-Ack</td>
<td>0-7: Reserved</td>
<td><xref target="RFC3973" format="default"/></td>
</tr>
<tr>
<td>8</td>
<td>Candidate RP Advertisement</td>
<td>0-7: Reserved</td>
<td><xref target="RFC7761" format="default"/></td>
</tr>
<tr>
<td>9</td>
<td>State Refresh</td>
<td>0-7: Reserved</td>
<td><xref target="RFC3973" format="default"/></td>
</tr>
<tr>
<td rowspan="2">10</td>
<td rowspan="2">DF Election</td>
<td>0-3: Reserved</td>
<td><xref target="RFC5015" format="default"/></td>
</tr>
<tr>
<td>4-7: Subtype</td>
<td><xref target="RFC5015" format="default"/></td>
</tr>
<tr>
<td>11</td>
<td>ECMP Redirect</td>
<td>0-7: Reserved</td>
<td><xref target="RFC6754" format="default"/></td>
</tr>
<tr>
<td rowspan="2">12</td>
<td rowspan="2">PIM Flooding Mechanism</td>
<td>0-6: Reserved</td>
<td><xref target="RFC8364" format="default"/></td>
</tr>
<tr>
<td>7: No-Forward</td>
<td><xref target="RFC8364" format="default"/></td>
</tr>
<tr>
<td>13.0-15.15</td>
<td>Unassigned</td>
<td>0-3: Unassigned</td>
<td>RFC 8736</td>
</tr>
</tbody>
</table>
<t>The unassigned types above, as explained in <xref target="ext"
format="default"/>, use the extended type notation of type.subtype. Each
extended type only has 4 flag bits available. New extended message types
should be assigned consecutively, starting with 13.0, then 13.1, etc.</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.7761' ?> <name>Normative References</name>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
<?rfc include='reference.RFC.8126'?> ence.RFC.2119.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
<?rfc include='reference.RFC.8174'?> ence.RFC.7761.xml"/>
</references> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.8126.xml"/>
<references title="Informative References"> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
<?rfc include='reference.RFC.6166'?> ence.RFC.8174.xml"/>
</references>
<?rfc include='reference.RFC.3973' ?> <references>
<name>Informative References</name>
<?rfc include='reference.RFC.6754' ?> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.6166.xml"/>
<?rfc include='reference.RFC.8364' ?> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.3973.xml"/>
<?rfc include='reference.RFC.5059' ?> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.6754.xml"/>
<?rfc include='reference.RFC.5015' ?> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.8364.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.5059.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.5015.xml"/>
</references>
</references> </references>
</back> </back>
</rfc> </rfc>
 End of changes. 51 change blocks. 
208 lines changed or deleted 283 lines changed or added

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