randy/draft-8210bis
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

edits from Luigi Iannone <ggx@gigix.net> review

Browse source
This commit is contained in:
Randy Bush 2025-06-05 16:24:19 -07:00
parent 9461a09b73
commit 4179601bf0
1 changed files with 25 additions and 23 deletions
Download patch file Download diff file Expand all files Collapse all files

48
draft-ietf-sidrops-8210bis.xml
View file

@ -8,7 +8,7 @@
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" docName="draft-ietf-sidrops-8210bis-20"
<rfc category="std" docName="draft-ietf-sidrops-8210bis-21"
submissionType="IETF" ipr="trust200902" version="2" consensus="yes">
<front>
@ -1517,7 +1517,7 @@ Cache Router
Caches and routers MAY use Transport Layer Security (TLS)
transport <xref target="RFC8446"/> using port rpki-rtr-tls
(324); see <xref target="IANA"/>. Conformance to <xref
target="RFC7525"/> modern cipher suites is REQUIRED.
target="BCP195"/> modern cipher suites is REQUIRED.
</t>
</list></t>
@ -1747,9 +1747,9 @@ Cache Router
described.
</t>
<t>
<xref target="order"/> describes an optional but RECOMMENDED
ordering of all PDUs which allows mitigation of the race
conditions described in <xref target="races"/>.
<xref target="order"/> describes a RECOMMENDED ordering of all
PDUs which allows mitigation of the race conditions described in
<xref target="races"/>.
</t>
<t>
<xref target="trans"/> describes how a router MAY process
@ -1759,7 +1759,7 @@ Cache Router
<section anchor="races" title="ROA PDU Race Minimization">
<t>
When a cache is sending ROA (IPv4 or IPv6) VRPs to a router
When a cache is sending ROA (IPv4 or IPv6) VRPs to a router,
undesirable race conditions are possible:
<list style="hanging">
<t hangText="Make Before Break:">
@ -1804,27 +1804,29 @@ Cache Router
exceptions in <xref target="races"/> above, ordering MUST be,
as follows:
</t>
<list style="symbols">
<t>
<ol type="%d">
<li>
PDUs are first ordered by PDU Type,
</t>
<t>
</li>
<li>
IPv4 and IPv6 Prefix VRPs are ordered by: first IPvX Prefix,
second Prefix Length, third Max Length, and fourth Autonomous
System Number. Treating announcements of VPUs with AS 0 as
sorting last, and withdrawals as sorting first, fulfills the "AS
0" requirement of <xref target="races"/>. Treating
announcements of sub-prefixes as sorting first fulfills the
"Longest Prefix Match" requirement of <xref target="races"/>.
</t>
<t>
second Prefix Length (largest value first for announcements,
lowest value first for withdrawals), third Max Length, and
fourth Autonomous System Number. Treating announcements of
VPUs with AS 0 as sorting last, and withdrawals as sorting
first, fulfills the "AS 0" requirement of <xref
target="races"/>. Treating announcements of sub-prefixes as
sorting first fulfills the "Longest Prefix Match"
requirement of <xref target="races"/>.
</li>
<li>
Router Key PDUs are ordered by AS Number and then Subject Public
Key Info.
</t>
<t>
</li>
<li>
And ASPA PDUs ordered by Customer AS.
</t>
</list>
</li>
</ol>
<t>
Unless specifically configured for a particular cache, a
router MUST NOT depend on payload PDU ordering.
@ -2139,12 +2141,12 @@ Cache Router
<?rfc include="reference.RFC.6487.xml"?>
<?rfc include="reference.RFC.6810.xml"?>
<?rfc include="reference.RFC.6811.xml"?>
<?rfc include="reference.RFC.7525.xml"?>
<?rfc include="reference.RFC.8174.xml"?>
<?rfc include="reference.RFC.8210.xml"?>
<?rfc include="reference.RFC.8446.xml"?>
<?rfc include="reference.RFC.8608.xml"?>
<?rfc include="reference.RFC.8635.xml"?>
<?rfc include="reference.BCP.195.xml"?>
</references>
<references title="Informative References">