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