From 37817df455806d9460e1bac78a60de10638adc72 Mon Sep 17 00:00:00 2001 From: Randy Bush Date: Wed, 22 Dec 2021 17:34:51 -0800 Subject: [PATCH] -05 published, revives Flags.[ann|del] --- draft-ietf-sidrops-8210bis.xml | 46 +++++++++++++++++++--------------- 1 file changed, 26 insertions(+), 20 deletions(-) diff --git a/draft-ietf-sidrops-8210bis.xml b/draft-ietf-sidrops-8210bis.xml index 54e7f79..7902207 100644 --- a/draft-ietf-sidrops-8210bis.xml +++ b/draft-ietf-sidrops-8210bis.xml @@ -10,7 +10,7 @@ - + @@ -973,13 +973,13 @@ target="I-D.ietf-sidrops-aspa-profile"/>. An ASPA PDU represents one single customer AS and its provider ASs for a particular Address Family. Receipt of an ASPA PDU - announcement when the router already has an ASPA PDU with the - same Customer Autonomous System Number and the same Address - Family (see Flags field), replaces the previous one. This is - to avoid a race condition when a BGP announcement is received - between an withdrawn PDU and a new announced PDU. Therefore, - the cache MUST deliver entire data of an ASPA record in a - single ASPA PDU. + announcement (Flag.Announce == 1) when the router already has + an ASPA PDU with the same Customer Autonomous System Number + and the same Address Family (see Flags field), replaces the + previous one. This is to avoid a race condition when a BGP + announcement is received between an withdrawn PDU and a new + announced PDU. Therefore, the cache MUST deliver the complete + data of an ASPA record in a single ASPA PDU. @@ -987,9 +987,9 @@ particular Customer Autonomous System Number active at any time. As a number of conditions in the global RPKI may present multiple valid ASPA objects for a single customer to a - particular RP cache, this places a burden on the cache to - merge multiple ASPA records it has received from the global - RPKI into one ASPA PDU. + 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. @@ -999,7 +999,8 @@ Bit Bit Name ---- ------------------- 0 AFI (IPv4 == 0, IPv6 == 1) - 1-7 Reserved, must be zero + 1 Announce == 1, Delete == 0 + 2-7 Reserved, must be zero @@ -1010,20 +1011,25 @@ The Customer Autonomous System Number is the 32-bit Autonomous - System Number of the customer which signed the PDU. There - MUST be one and only one ASPA for a Customer Autonomous System - Number active in the router at any time. + System Number of the customer which authenticated the PDU. + There MUST be one and only one ASPA for a Customer Autonomous + System Number active in the router at any time. - There are one or more 32-bit Provider Autonomous System Number - fields; see . + There are zero or more 32-bit Provider Autonomous System + Number fields as indicated in the Provider AS Count; see . - Receipt of an ASPA PDU with zero providers is an implicit - withdraw of the entire ASPA data for that customer AS from - that cache. + Receipt of an ASPA PDU with the Flags field indicating Delete + is an explicit withdraw from the router of the entire ASPA + data for that customer AS. While the Provider AS Count and + the Provider AS Numbers MUST BE ignored by the router when the + Flags field indicates a Delete, the cache SHOULD set the + Provider AS Count to zero, and have a null Provider AS Numbers + list.