rfc9436.original.xml   rfc9436.xml 
<?xml version='1.0' encoding='utf-8'?> <?xml version="1.0" encoding="UTF-8"?>
<?xml-model href="rfc7991bis.rnc"?> <?xml-model href="rfc7991bis.rnc"?>
<!DOCTYPE rfc [ <!DOCTYPE rfc [
<!ENTITY nbsp "&#160;"> <!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;"> <!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;"> <!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;"> <!ENTITY wj "&#8288;">
]> ]>
<rfc <rfc
xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xi="http://www.w3.org/2001/XInclude"
submissionType="IETF"
category="std" category="std"
consensus="true"
docName="draft-ietf-pim-rfc8736bis-04" docName="draft-ietf-pim-rfc8736bis-04"
number="9436"
ipr="trust200902" ipr="trust200902"
obsoletes="8736" obsoletes="8736"
updates="3973, 5015, 5059, 6754, 7761, 8364" updates="3973, 5015, 5059, 6754, 7761, 8364"
submissionType="IETF"
xml:lang="en" xml:lang="en"
version="3" tocInclude="true"
consensus="true"> symRefs="true" sortRefs="true"
version="3">
<front> <front>
<title abbrev="PIM Type Extension and Reserved Bits">PIM Message Type Space <title abbrev="PIM Type Extension and Reserved Bits">PIM Message Type
Extension and Reserved Bits</title> Space Extension and Reserved Bits</title>
<seriesInfo name="Internet-Draft" value="draft-ietf-pim-rfc8736bis-04"/> <seriesInfo name="RFC" value="9436"/>
<author fullname="Stig Venaas" initials="S." surname="Venaas"> <author fullname="Stig Venaas" initials="S." surname="Venaas">
<organization showOnFrontPage="true">Cisco Systems, Inc.</organization> <organization showOnFrontPage="true">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> <region>CA</region>
<code>95134</code> <code>95134</code>
<country>United States of America</country> <country>United States of America</country>
</postal> </postal>
skipping to change at line 52 skipping to change at line 59
<city>Santa Clara</city> <city>Santa Clara</city>
<region>CA</region> <region>CA</region>
<code>95050</code> <code>95050</code>
<country>United States of America</country> <country>United States of America</country>
</postal> </postal>
<phone/> <phone/>
<email>alvaro.retana@futurewei.com</email> <email>alvaro.retana@futurewei.com</email>
<uri/> <uri/>
</address> </address>
</author> </author>
<date year="2023"/> <date year="2023" month="August" />
<area>Routing</area> <area>rtg</area>
<workgroup>PIM</workgroup> <workgroup>pim</workgroup>
<keyword>Multicast PIM</keyword> <keyword>Multicast PIM</keyword>
<abstract> <abstract>
<t> <t>
The PIM version 2 messages share a common message header format. The 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
extends the PIM type space. extends the PIM type space.
</t> </t>
<t> <t>
This document updates RFC7761 and RFC3973 by defining the use of the This document updates RFCs 7761 and 3973 by defining the use of the
currently Reserved field in the PIM common header. This document Reserved field in the PIM common header. This document
further updates RFC7761 and RFC3973, along with RFC5015, RFC5059, further updates RFCs 7761 and 3973, along with RFCs 5015, 5059, 6754,
RFC6754, and RFC8364, by specifying the use of the currently reserved and 8364, by specifying the use of the bits for each PIM message.
bits for each PIM message.
</t> </t>
<t> <t>
This document obsoletes RFC8736. This document obsoletes RFC 8736.
</t> </t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section numbered="true" toc="include" removeInRFC="false" anchor="intro"> <section numbered="true" toc="include" removeInRFC="false" anchor="intro">
<name>Introduction</name> <name>Introduction</name>
<t> <t>
The PIM version 2 messages share a common message header format defined The PIM version 2 messages share a common message header format defined
in the PIM Sparse Mode specification <xref target="RFC7761"/>. The in the PIM Sparse Mode specification <xref target="RFC7761"/>. The
common header definition contains eight reserved bits. While all 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. specifying that these bits are to be used per message type.
</t> </t>
<t> <t>This document updates the definition of the Reserved field and refers
This document refers to the bits in the Reserved field of the common to it as the "Flag Bits field". It specifies that the flag bits are to
PIM header <xref target="RFC7761"/> as "PIM message type Flag Bits" or, be separately used on a per-message-type basis. It updates the "PIM
simply, "Flag Bits", and it specifies that they are to be separately Message Types" registry to indicate the per-message-type usage.
used on a per-message-type basis. It updates the "PIM Message Types"
registry to indicate the per-message-type usage.
</t> </t>
<t> <t>
This document updates <xref target="RFC7761"/> and This document updates <xref target="RFC7761"/> and <xref
<xref target="RFC3973"/> by defining the use of the currently Reserved target="RFC3973"/> by defining the use of the Reserved field in the
field in the PIM common header. This document further updates PIM common header. This document further updates <xref
<xref target="RFC7761"/> and <xref target="RFC3973"/>, along with target="RFC7761"/> and <xref target="RFC3973"/>, along with <xref
<xref target="RFC5015"/>, <xref target="RFC5059"/>, target="RFC5015"/>, <xref target="RFC5059"/>, <xref
<xref target="RFC6754"/>, and <xref target="RFC8364"/>, by specifying target="RFC6754"/>, and <xref target="RFC8364"/>, by specifying the
the use of the currently reserved bits for each PIM message. use of the bits for each PIM message.</t>
</t>
<t> <t>
The originally defined PIM message types were in the range from 0 to The originally defined PIM message types were in the range from 0 to
15. Message type 15 had been reserved by <xref target="RFC6166"/> for 15. Message type 15 had been reserved by <xref target="RFC6166"/> for
type space extension. In <xref target="ext"/>, this document specifies type space extension. In <xref target="ext"/>, this document specifies
the use of the Flag Bits for message types 13, 14, and 15 in order to the use of the Flag Bits field for message types 13, 14, and 15 in
extend the PIM type space. The type space extension in order to extend the PIM type space. The type space extension in <xref
<xref target="RFC6166"/> was made obsolete by target="RFC6166"/> was made obsolete by <xref target="RFC8736"/>.
<xref target="RFC8736"/>. This document obsoletes <xref target="RFC8736 This document obsoletes <xref target="RFC8736"/>.
"/>.
</t> </t>
</section> </section>
<section numbered="true" toc="include" removeInRFC="false"> <section numbered="true" toc="include" removeInRFC="false">
<name>Conventions Used in This Document</name> <name>Conventions Used in This Document</name>
<t> <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
"<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
"<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document
"<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and are to be interpreted as described in BCP&nbsp;14 <xref
"<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> appear in all capitals, as shown here.
when, and only when, they appear in all capitals, as shown here. </t>
</t>
</section> </section>
<section numbered="true" toc="include" removeInRFC="false"> <section numbered="true" toc="include" removeInRFC="false">
<name>PIM Header Common Format</name> <name>PIM Header Common Format</name>
<t> <t>
The common PIM header is defined in The common PIM header is defined in <xref target="RFC7761"
<xref target="RFC7761" sectionFormat="of" section="4.9" derivedLink="htt sectionFormat="of" section="4.9"/>. This document updates the
ps://rfc-editor.org/rfc/rfc7761#section-4.9"/>. definition of the Reserved field and refers to it as the "Flag Bits
This document updates the definition of the Reserved field and refers field". The updated common header format is as below.
to that field as "PIM message type Flag Bits" or, simply, "Flag Bits".
The updated common header format is as below.
</t> </t>
<figure align="left" suppress-title="false"> <figure align="left" suppress-title="false">
<name>Updated Common Header</name> <name>Updated Common Header</name>
<artwork name="" type="" align="left" alt=""> <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> </figure>
<t> <t>
The Flag Bits field is defined in <xref target="flagbits"/>. All other f ields remain unchanged. The Flag Bits field is defined in <xref target="flagbits"/>. All other f ields remain unchanged.
</t> </t>
</section> </section>
<section anchor="flagbits" numbered="true" toc="include" removeInRFC="false" > <section anchor="flagbits" numbered="true" toc="include" removeInRFC="false" >
<name>Flag Bit Definitions</name> <name>Flag Bit Definitions</name>
<t> <t>
Unless otherwise specified, all the flag bits for each PIM type are Unless otherwise specified, all the flag bits for each PIM type are
Unassigned <xref target="RFC8126"/>. They <bcp14>MUST</bcp14> be set to Unassigned <xref target="RFC8126"/>. They <bcp14>MUST</bcp14> be set to
zero on transmission, and they <bcp14>MUST</bcp14> be ignored upon zero on transmission, and they <bcp14>MUST</bcp14> be ignored upon
receipt. The specification of a new PIM type <bcp14>MUST</bcp14> receipt. The specification of a new PIM type <bcp14>MUST</bcp14>
indicate whether the bits should be treated differently. indicate whether the bits should be treated differently.
</t> </t>
<t> <t>
When defining flag bits, it is helpful to have a well-defined way of ref erring to a particular bit. The most significant of the flag bits, the bit immed iately following the Type field, is referred to as bit 7. 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. When defining flag bits, it is helpful to have a well-defined way of ref erring to a particular bit. The most significant of the flag bits, the bit immed iately following the Type field, is referred to as bit 7. 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> </t>
<figure align="left" suppress-title="false"> <figure align="left" suppress-title="false">
<name>Flag Bits</name> <name>Flag Bits</name>
<artwork name="" type="" align="left" alt=""> <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> </figure>
<section numbered="true" toc="include" removeInRFC="false"> <section numbered="true" toc="include" removeInRFC="false">
<name>Flag Bits for Type 4 (Bootstrap)</name> <name>Flag Bits for Type 4 (Bootstrap)</name>
<t> <t>
PIM message type 4 (Bootstrap) <xref target="RFC5059"/> defines flag PIM message type 4 (Bootstrap) <xref target="RFC5059"/> defines flag
bit 7 as No-Forward. The usage of the bit is defined in that document. The remaining flag bits are unassigned. bit 7 as No-Forward. The usage of the bit is defined in that document. The remaining flag bits are unassigned.
</t> </t>
</section> </section>
<section numbered="true" toc="include" removeInRFC="false"> <section numbered="true" toc="include" removeInRFC="false">
<name>Flag Bits for Type 10 (DF Election)</name> <name>Flag Bits for Type 10 (DF Election)</name>
skipping to change at line 186 skipping to change at line 188
</section> </section>
<section numbered="true" toc="include" removeInRFC="false"> <section numbered="true" toc="include" removeInRFC="false">
<name>Flag Bits for Type 10 (DF Election)</name> <name>Flag Bits for Type 10 (DF Election)</name>
<t> <t>
PIM message type 10 (DF Election) <xref target="RFC5015"/> specifies PIM message type 10 (DF Election) <xref target="RFC5015"/> specifies
that the four most significant flag bits (bits 4-7) are to be used as that the four most significant flag bits (bits 4-7) are to be used as
a subtype. The usage of those bits is defined in that document. The a subtype. The usage of those bits is defined in that document. The
remaining flag bits are unassigned. remaining flag bits are unassigned.
</t> </t>
</section> </section>
<section numbered="true" toc="include" removeInRFC="false"> <section numbered="true" toc="include" removeInRFC="false">
<name>Flag Bits for Type 12 (PFM)</name> <name>Flag Bits for Type 12 (PIM Flooding Mechanism)</name>
<t> <t>
PIM message type 12 (PIM Flooding Mechanism) <xref target="RFC8364"/> PIM message type 12 (PIM Flooding Mechanism) <xref target="RFC8364"/>
defines flag bit 7 as No-Forward. The usage of the bit is defined in defines flag bit 7 as No-Forward. The usage of the bit is defined in
that document. The remaining flag bits are unsassigned. that document. The remaining flag bits are unassigned.
</t> </t>
</section> </section>
<section numbered="true" toc="include" removeInRFC="false"> <section numbered="true" toc="include" removeInRFC="false">
<name>Flag Bits for Types 13, 14, and 15 (Type Space Extension)</name> <name>Flag Bits for Types 13, 14, and 15 (Type Space Extension)</name>
<t> <t>
These types and the corresponding flag bits are defined in These types and the corresponding flag bits are defined in
<xref target="ext"/>. <xref target="ext"/>.
</t> </t>
</section> </section>
</section> </section>
skipping to change at line 221 skipping to change at line 224
FB below) are to be defined by each extended type. FB below) are to be defined by each extended type.
</t> </t>
<t> <t>
Each of the extended types is represented by the eight bits Each of the extended types is represented by the eight bits
resulting from the concatenation of the Type and Subtype fields. No resulting from the concatenation of the Type and Subtype fields. No
relationship is expected or implied between extended type messages with relationship is expected or implied between extended type messages with
a common Type field. a common Type field.
</t> </t>
<figure anchor="subtypes" align="left" suppress-title="false"> <figure anchor="subtypes" align="left" suppress-title="false">
<name>Subtypes</name> <name>Subtypes</name>
<artwork name="" type="" align="left" alt=""> <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> </figure>
</section> </section>
<section numbered="true" toc="include" removeInRFC="false"> <section numbered="true" toc="include" removeInRFC="false">
<name>Security Considerations</name> <name>Security Considerations</name>
<t> <t>
This document clarifies the use of the flag bits in the common PIM 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 header, and it extends the PIM type space. As such, there is no impact
on security or changes to the considerations in on security or changes to the considerations in
<xref target="RFC7761"/> and <xref target="RFC3973"/>. <xref target="RFC7761"/> and <xref target="RFC3973"/>.
</t> </t>
skipping to change at line 239 skipping to change at line 242
</section> </section>
<section numbered="true" toc="include" removeInRFC="false"> <section numbered="true" toc="include" removeInRFC="false">
<name>Security Considerations</name> <name>Security Considerations</name>
<t> <t>
This document clarifies the use of the flag bits in the common PIM 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 header, and it extends the PIM type space. As such, there is no impact
on security or changes to the considerations in on security or changes to the considerations in
<xref target="RFC7761"/> and <xref target="RFC3973"/>. <xref target="RFC7761"/> and <xref target="RFC3973"/>.
</t> </t>
</section> </section>
<section anchor="IANA" numbered="true" toc="include" removeInRFC="false"> <section anchor="IANA" numbered="true" toc="include" removeInRFC="false">
<name>IANA Considerations</name> <name>IANA Considerations</name>
<t> <t>
This document updates the "PIM Message Types" registry to indicate 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
and changes their registration status to Unassigned, as shown in and changes their registration status to Unassigned except where the
<xref target="PIM-registry"/>. The registration policy remains IETF bits have already been specified, as shown in Table 1. The
Review <xref target="RFC8126"/>. Assignments to this registry registration policy remains IETF Review <xref
<bcp14>MUST</bcp14> define any non-default usage (see target="RFC8126"/>. Assignments to this registry <bcp14>MUST</bcp14>
<xref target="flagbits"/>) of the flag bits in addition to the type. define any non-default usage (see <xref target="flagbits"/>) of the
flag bits in addition to the type.
</t> </t>
<t> <t>
Extended type 15.15 is Reserved <xref target="RFC8126"/> for future Extended type 15.15 is Reserved <xref target="RFC8126"/> for future
extensions. extensions.
</t> </t>
<t> <t>
Because this document obsoletes RFC 8736, IANA is asked to change all Because this document obsoletes <xref target="RFC8736"/>, IANA has
registration information that references <xref target="RFC8736"/> to changed the references to <xref
instead reference [this document]. target="RFC8736"/> in the registry to point to this document instead.
</t> </t>
<t> <t>
The updated "PIM Message Types" registry is shown below. The updated "PIM Message Types" registry is shown below.
</t> </t>
<table anchor="PIM-registry" align="center"> <table anchor="PIM-registry" align="center">
<name>Updated PIM Message Types Registry</name> <name>Updated PIM Message Types Registry</name>
<thead> <thead>
<tr> <tr>
<th align="left" colspan="1" rowspan="1">Type</th> <th align="left" colspan="1" rowspan="1">Type</th>
<th align="left" colspan="1" rowspan="1">Name</th> <th align="left" colspan="1" rowspan="1">Name</th>
<th align="left" colspan="1" rowspan="1">Flag Bits</th> <th align="left" colspan="1" rowspan="1">Flag Bits</th>
<th align="left" colspan="1" rowspan="1">Reference</th> <th align="left" colspan="1" rowspan="1">Reference</th>
</tr> </tr>
</thead> </thead>
<tbody> <tbody>
<tr> <tr>
<td align="left" colspan="1" rowspan="1">0</td> <td align="left" colspan="1" rowspan="1">0</td>
<td align="left" colspan="1" rowspan="1">Hello</td> <td align="left" colspan="1" rowspan="1">Hello</td>
<td align="left" colspan="1" rowspan="1">0-7: Unassigned</td> <td align="left" colspan="1" rowspan="1">0-7: Unassigned</td>
<td align="left" colspan="1" rowspan="1"> <td align="left" colspan="1" rowspan="1">
<xref target="RFC3973"/><xref target="RFC7761"/></td> <xref target="RFC3973"/> <xref target="RFC7761"/></td>
</tr> </tr>
<tr> <tr>
<td align="left" colspan="1" rowspan="1">1</td> <td align="left" colspan="1" rowspan="1">1</td>
<td align="left" colspan="1" rowspan="1">Register</td> <td align="left" colspan="1" rowspan="1">Register</td>
<td align="left" colspan="1" rowspan="1">0-7: Unassigned</td> <td align="left" colspan="1" rowspan="1">0-7: Unassigned</td>
<td align="left" colspan="1" rowspan="1"> <td align="left" colspan="1" rowspan="1">
<xref target="RFC7761"/></td> <xref target="RFC7761"/></td>
</tr> </tr>
<tr> <tr>
<td align="left" colspan="1" rowspan="1">2</td> <td align="left" colspan="1" rowspan="1">2</td>
<td align="left" colspan="1" rowspan="1">Register Stop</td> <td align="left" colspan="1" rowspan="1">Register Stop</td>
<td align="left" colspan="1" rowspan="1">0-7: Unassigned</td> <td align="left" colspan="1" rowspan="1">0-7: Unassigned</td>
<td align="left" colspan="1" rowspan="1"> <td align="left" colspan="1" rowspan="1">
<xref target="RFC7761"/></td> <xref target="RFC7761"/></td>
</tr> </tr>
<tr> <tr>
<td align="left" colspan="1" rowspan="1">3</td> <td align="left" colspan="1" rowspan="1">3</td>
<td align="left" colspan="1" rowspan="1">Join/Prune</td> <td align="left" colspan="1" rowspan="1">Join/Prune</td>
<td align="left" colspan="1" rowspan="1">0-7: Unassigned</td> <td align="left" colspan="1" rowspan="1">0-7: Unassigned</td>
<td align="left" colspan="1" rowspan="1"> <td align="left" colspan="1" rowspan="1">
<xref target="RFC3973"/><xref target="RFC7761"/></td> <xref target="RFC3973"/> <xref target="RFC7761"/></td>
</tr> </tr>
<tr> <tr>
<td rowspan="2" align="left" colspan="1">4</td> <td rowspan="2" align="left" colspan="1">4</td>
<td rowspan="2" align="left" colspan="1">Bootstrap</td> <td rowspan="2" align="left" colspan="1">Bootstrap</td>
<td align="left" colspan="1" rowspan="1">0-6: Unassigned</td> <td align="left" colspan="1" rowspan="1">0-6: Unassigned</td>
<td align="left" colspan="1" rowspan="1"> <td align="left" colspan="1" rowspan="1">
<xref target="RFC5059"/><xref target="RFC7761"/></td> <xref target="RFC5059"/> <xref target="RFC7761"/></td>
</tr> </tr>
<tr> <tr>
<td align="left" colspan="1" rowspan="1">7: No-Forward</td> <td align="left" colspan="1" rowspan="1">7: No-Forward</td>
<td align="left" colspan="1" rowspan="1"> <td align="left" colspan="1" rowspan="1">
<xref target="RFC5059"/></td> <xref target="RFC5059"/></td>
</tr> </tr>
<tr> <tr>
<td align="left" colspan="1" rowspan="1">5</td> <td align="left" colspan="1" rowspan="1">5</td>
<td align="left" colspan="1" rowspan="1">Assert</td> <td align="left" colspan="1" rowspan="1">Assert</td>
<td align="left" colspan="1" rowspan="1">0-7: Unassigned</td> <td align="left" colspan="1" rowspan="1">0-7: Unassigned</td>
<td align="left" colspan="1" rowspan="1"> <td align="left" colspan="1" rowspan="1">
<xref target="RFC3973"/><xref target="RFC7761"/></td> <xref target="RFC3973"/> <xref target="RFC7761"/></td>
</tr> </tr>
<tr> <tr>
<td align="left" colspan="1" rowspan="1">6</td> <td align="left" colspan="1" rowspan="1">6</td>
<td align="left" colspan="1" rowspan="1">Graft</td> <td align="left" colspan="1" rowspan="1">Graft</td>
<td align="left" colspan="1" rowspan="1">0-7: Unassigned</td> <td align="left" colspan="1" rowspan="1">0-7: Unassigned</td>
<td align="left" colspan="1" rowspan="1"> <td align="left" colspan="1" rowspan="1">
<xref target="RFC3973"/></td> <xref target="RFC3973"/></td>
</tr> </tr>
<tr> <tr>
<td align="left" colspan="1" rowspan="1">7</td> <td align="left" colspan="1" rowspan="1">7</td>
skipping to change at line 383 skipping to change at line 388
</tr> </tr>
<tr> <tr>
<td align="left" colspan="1" rowspan="1">7: No-Forward</td> <td align="left" colspan="1" rowspan="1">7: No-Forward</td>
<td align="left" colspan="1" rowspan="1"> <td align="left" colspan="1" rowspan="1">
<xref target="RFC8364"/></td> <xref target="RFC8364"/></td>
</tr> </tr>
<tr> <tr>
<td align="left" colspan="1" rowspan="1">13.0-15.14</td> <td align="left" colspan="1" rowspan="1">13.0-15.14</td>
<td align="left" colspan="1" rowspan="1">Unassigned</td> <td align="left" colspan="1" rowspan="1">Unassigned</td>
<td align="left" colspan="1" rowspan="1">0-3: Unassigned</td> <td align="left" colspan="1" rowspan="1">0-3: Unassigned</td>
<td align="left" colspan="1" rowspan="1">[This document]</td> <td align="left" colspan="1" rowspan="1"></td>
</tr> </tr>
<tr> <tr>
<td align="left" colspan="1" rowspan="1">15.15</td> <td align="left" colspan="1" rowspan="1">15.15</td>
<td align="left" colspan="1" rowspan="1">Reserved</td> <td align="left" colspan="1" rowspan="1">Reserved</td>
<td align="left" colspan="1" rowspan="1">0-3: Reserved</td> <td align="left" colspan="1" rowspan="1">0-3: Reserved</td>
<td align="left" colspan="1" rowspan="1">[This document]</td> <td align="left" colspan="1" rowspan="1">RFC 9436</td>
</tr> </tr>
</tbody> </tbody>
</table> </table>
<t> <t>
The unassigned types above, as explained in <xref target="ext"/>, use The unassigned types above, as explained in <xref target="ext"/>, use
the extended type notation of type.subtype. Each extended type only has the extended type notation of type.subtype. Each extended type only has
4 flag bits available. New extended message types should be assigned 4 flag bits available. New extended message types should be assigned
consecutively, starting with 13.0, then 13.1, etc. consecutively, starting with 13.0, then 13.1, etc.
</t> </t>
</section> </section>
 End of changes. 32 change blocks. 
89 lines changed or deleted 91 lines changed or added

This html diff was produced by rfcdiff 1.48.