pushed ancient edit buffer with afi hack

This commit is contained in:
Randy Bush 2023-09-21 13:31:13 -07:00
parent ac2c675d32
commit f2855cf0ce

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-10" submissionType="IETF" ipr="trust200902" consensus="yes"> <rfc category="std" docName="draft-ietf-sidrops-8210bis-11" submissionType="IETF" ipr="trust200902" consensus="yes">
<front> <front>
@ -481,9 +481,10 @@
subsequent cache poll. See <xref target="timing"/>. subsequent cache poll. See <xref target="timing"/>.
</t> </t>
<t hangText="AFI Flags:"> <t hangText="AFI Flags:">
An 8-bit field of the ASPA PDU where the low order bit An 8-bit field of the ASPA PDU where the low order bit is
denotes whether the AS relationships are for IPv4 (0) or set if the AS relationships are for IPv4 (AFI 1), and the
IPv6 (1) AFI. second lowest bit is set for IPv6 (AFI 2). Currently,
both bits MUST be set.
</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
@ -1035,23 +1036,22 @@
<t> <t>
The ASPA PDU supports <xref The ASPA PDU supports <xref
target="I-D.ietf-sidrops-aspa-profile"/>. An ASPA PDU target="I-D.ietf-sidrops-aspa-profile"/>. An ASPA PDU
represents one single customer AS and its provider ASes for a represents one single customer AS and its provider ASes.
particular Address Family. Receipt of an ASPA PDU Receipt of an ASPA PDU announcement (announce/withdraw flag ==
announcement (announce/withdraw flag == 1) when the router 1) when the router already has an ASPA PDU with the same
already has an ASPA PDU with the same Customer Autonomous Customer Autonomous System Number replaces the previous one.
System Number and the same Address Family (see AFI Flags The cache MUST deliver the complete data of an ASPA record in
field), replaces the previous one. The cache MUST deliver the a single ASPA PDU.
complete data of an ASPA record in a single ASPA PDU.
</t> </t>
<t> <t>
The router MUST see at most one ASPA for a given AFI from a The router MUST see at most one ASPA from a cache for a
cache for a particular Customer Autonomous System Number particular Customer Autonomous System Number active at any
active at any time. As a number of conditions in the global time. As a number of conditions in the global RPKI may
RPKI may present multiple valid ASPA RPKI records for a single present multiple valid ASPA RPKI records for a single customer
customer to a particular RP cache, this places a burden on the to a particular RP cache, this places a burden on the cache to
cache to form the union of multiple ASPA records it has form the union of multiple ASPA records it has received from
received from the global RPKI into one ASPA PDU. the global RPKI into one ASPA PDU.
</t> </t>
<t> <t>
@ -1062,19 +1062,23 @@
For the ASPA PDU, the announce/withdraw Flag is set to 1 to For the ASPA PDU, the announce/withdraw Flag is set to 1 to
indicate either the announcement of a new ASPA record or a indicate either the announcement of a new ASPA record or a
replacement for a previously announced record with the same replacement for a previously announced record with the same
Customer Autonomous System Number and AFI. Customer Autonomous System Number.
</t> </t>
<t> <t>
If the announce/withdraw flag is set to 0, it indicates If the announce/withdraw flag is set to 0, it indicates
removal of the entire ASPA record for the specified AFI and removal of the entire ASPA record for that Customer AS. Here,
Customer AS. Here, the AFI and the customer AS of the ASPA the customer AS of the ASPA record MUST be provided, the
record MUST be provided, the Provider AS Count must be zero, Provider AS Count must be zero, the Provider AS Numbers list
the Provider AS Numbers list MUST be null, and these last two MUST be null, and these last two fields MUST be ignored by the
fields MUST be ignored by the router. router.
</t> </t>
<t> <t>
The AFI Flags field is defined in <xref target="IANA"/>. The AFI Flags field is defined in <xref target="IANA"/>
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
for less change should the AFIs be separated in a future
version.
</t> </t>
<t> <t>
@ -1085,9 +1089,8 @@
<t> <t>
The Customer Autonomous System Number is the 32-bit Autonomous The Customer Autonomous System Number is the 32-bit Autonomous
System Number of the customer which authenticated the ASPA System Number of the customer which authenticated the ASPA
RPKI data. For a given AFI, there MUST be one and only one RPKI data. There MUST be one and only one ASPA for a Customer
ASPA for a Customer Autonomous System Number active in the Autonomous System Number active in the router at any time.
router at any time.
</t> </t>
<t> <t>
@ -1979,8 +1982,9 @@ Cache Router
<artwork> <artwork>
Bit Bit Name Bit Bit Name
---- ------------------- ---- -------------------
0 AFI (IPv4 == 0, IPv6 == 1) 0 IPv4 AFI 1, currently MUST be set
1-7 Reserved, MUST be zero 1 IPv6 AFI 2, currently MUST be set
2-7 Reserved, MUST be zero
</artwork> </artwork>
</figure> </figure>
</t> </t>