-12 published

This commit is contained in:
Randy Bush 2024-03-04 10:56:56 -08:00
parent f60f7a55ed
commit e4533b9613

View file

@ -8,7 +8,7 @@
<?rfc compact="yes"?> <?rfc compact="yes"?>
<?rfc subcompact="no"?> <?rfc subcompact="no"?>
<rfc category="std" docName="draft-ietf-sidrops-8210bis-11" <rfc category="std" docName="draft-ietf-sidrops-8210bis-12"
submissionType="IETF" ipr="trust200902" version="2" consensus="yes"> submissionType="IETF" ipr="trust200902" version="2" consensus="yes">
<front> <front>
@ -485,7 +485,7 @@
An 8-bit field of the ASPA PDU where the low order bit is An 8-bit field of the ASPA PDU where the low order bit is
set if the AS relationships are for IPv4 (AFI 1), and the set if the AS relationships are for IPv4 (AFI 1), and the
second lowest bit is set for IPv6 (AFI 2). Currently, second lowest bit is set for IPv6 (AFI 2). Currently,
both bits MUST be set. both bits MUST be set. This field may be removed soon.
</t> </t>
<t hangText="Provider AS Count:"> <t hangText="Provider AS Count:">
A 16-bit count of Provider Autonomous System Numbers in A 16-bit count of Provider Autonomous System Numbers in
@ -499,8 +499,7 @@
</t> </t>
<t hangText="Provider Autonomous System Numbers:"> <t hangText="Provider Autonomous System Numbers:">
The set of 32-bit AS numbers authorized to propagate The set of 32-bit AS numbers authorized to propagate
prefixes of the specified AFI which were received from the prefixes which were received from the customer AS.
customer AS.
</t> </t>
</list> </list>
</t> </t>
@ -1079,7 +1078,8 @@
Currently, the two low order bits MUST always be set, i.e. 1, Currently, the two low order bits MUST always be set, i.e. 1,
and the rest unset, i.e. 0. This allows the router to prepare and the rest unset, i.e. 0. This allows the router to prepare
for less change should the AFIs be separated in a future for less change should the AFIs be separated in a future
version. version. This field is likely to be removed before
publication.
</t> </t>
<t> <t>
@ -1253,19 +1253,18 @@
</t> </t>
<t> <t>
Once the cache and router have agreed upon a Protocol Version Once the cache and router have agreed upon a Protocol Version
via the negotiation process above, that version is stable for via the negotiation process above, that version is fixed for the
the life of the session. See <xref target="fields"/> for a life of the session. See <xref target="fields"/> for a
discussion of the interaction between Protocol Version and discussion of the interaction between Protocol Version and
Session ID. Session ID.
</t> </t>
<t> <t>
The configured transport security, the negotiated RPKI-Rtr The configured transport security, the negotiated RPKI-Rtr
version, etc. may not be changed once a session has been version, etc. MAY NOT be changed once a session has been
established. If one side or the other wishes to try a different established. If one side or the other wishes to try a different
transport, protocol version, etc. they MUST terminate the transport, protocol version, etc. they MUST terminate the
transport and restart the entire transport and version transport and restart the entire transport and version
negotiation process, <xref target="Transport"/> and <xref negotiation process.
target="version"/>.
</t> </t>
<t> <t>
If either party receives a PDU for a different Protocol If either party receives a PDU for a different Protocol
@ -1841,9 +1840,10 @@ Cache Router
The cache server believes the client's request to be The cache server believes the client's request to be
invalid. invalid.
</t> </t>
<t hangText="4: Unsupported Protocol Version (fatal):"> <t hangText="4: Unsupported Protocol Version (non-fatal):">
The Protocol Version is not known by the receiver of the The Protocol Version is not known by the receiver of the
PDU. PDU. A session is not [re-]established, but data learned
need not be deleted.
</t> </t>
<t hangText="5: Unsupported PDU Type (fatal):"> <t hangText="5: Unsupported PDU Type (fatal):">
The PDU Type is not known by the receiver of the PDU. The PDU Type is not known by the receiver of the PDU.