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

[Job Snijders <[e-mail]>]

Hi Martin,

On Thu, Apr 20, 2023 at 11:52:48AM +0200, Martin Hoffmann wrote:
> Consequently, when transforming the provider set from an ASPA object
> into its RTR payload, an AS0-only PDU should probably be added for a
> customer AS that if the provider set for an address family turns out to
> be empty. Otherwise a router keeping separate tables has to consult the
> table for the other family any time there is no entry for a given
> customer AS and that rather defeats the purpose.

This is an accurate observation.

I've added an Appendix to the aspa-profile internet-draft showcasing
various eContent payloads and how they transform into RTR PDUs.

I also explicitly noted that a single eContent payload always results in
two RTR PDUs, and how multiple eContents payloads for the same Customer
ASID also result in exactly two RTR ASPA PDUs.

Please see: https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-aspa-profile#name-transforming-aspa-econtent-

Thanks for bringing this up and I hope the new appendix helps provide
some clarity.

Kind regards,

Job