Re: [Sidrops] Format of ASPA RTR PDU

[Claudio Jeker <[e-mail]>]

On Wed, Nov 08, 2023 at 10:38:38AM +0100, Martin Hoffmann wrote:
> Claudio Jeker wrote:
> > On Tue, Nov 07, 2023 at 04:00:49PM +0100, Maria Matejka wrote:
> > > 
> > > While trying to implement ASPA in RTR, we got confused by § 5.12,
> > > ASPA PDU, as of draft-ietf-sidrops-8210bis-11. Bytes 2 and 3 are
> > > set to zero and bytes 10 and 11 are encoding Provider AS Count
> > > which can be inferred from the overall PDU length easily. Is there
> > > any good reason to have this redundant information inside the PDU?
> > > We are suggesting to move the Flags and AFI Flags to bytes 2 and 3
> > > and to drop Provider AS Count completely. The Customer ASN would
> > > then start at byte 8 and Provider ASNs would start at byte 12.  
> > 
> > To be honest, the RTR bits are nowhere close to be ready. Especially
> > these questions have been raised numerous times by various developers
> > implementing this draft but the authors seem to not listen.
> > Right now draft-ietf-sidrops-8210bis is holding up all of ASPA.
> 
> Ironically, all of ASPA is holding up publishing 8210bis. Maybe it is
> time to admit that moving it forward was a mistake and use the
> opportunity to get it back and fix the issues properly?

That happened a few weeks ago. There is now draft-ietf-sidrops-8210bis-11
pulished on 2023-09-21. I sent my feedback on 2023-09-22 see
https://mailarchive.ietf.org/arch/msg/sidrops/qOygwqeF8PGZeSMCt5Hjq8_jGU4/

I would love to see your feedback to the -11 update. 
-- 
:wq Claudio