Re: [Sidrops] WGLC = draft-ietf-sidrops-aspa-verification - ENDS 03/22/2023 (Mar 22 2023)

[Martin Hoffmann <[e-mail]>]

Claudio Jeker wrote:
> On Thu, Mar 23, 2023 at 04:20:51PM +0100, Martin Hoffmann wrote:
> > Claudio Jeker wrote:  
> > > On Thu, Mar 23, 2023 at 01:22:32PM +0000, Amreesh Phokeer wrote:  
> 
> Please check how the profile is specified. The AFI is per provider
> AS. So there is no real concept of "only use ASPA for IPv4 or IPv6 but
> not for both" (only RTR 8210bis does that).

Oh, my bad. I must have missed the AFI moving from the attestation to
the provider AS in -08.

> > > >   2.  VAP: it is unclear whether how the VAP will be merged but
> > > > grouped by AFI in the case of multiple ASPAs?    
> > 
> > That the sets of provider AS of multiple ASPA objects for the same
> > customer AS should be merged is only mentioned in 8210bis but at no
> > point in either the profile or verification drafts. One of them
> > should probably spell out how the (on or two) VAPs for a customer
> > AS are to be created from a the set of ASPA objects.  
> 
> In draft-ietf-sidrops-aspa-verification-12 Section 3:
> If a CAS has a single ASPA, then the SPAS for the CAS are the Provider
> ASes listed in that ASPA. In case a CAS has multiple ASPAs, then the
> SPAS is the union of the Provider ASes listed in all ASPAs of the CAS.

I had to read the section three times to find that sentence. That’s
probably because it is hidden at the end of a paragraph that purports to
define a notation used in the document.

  -- Martin