no. it is telling the edge site, your paying customer, that they can secure their prefix without upgrading hardware.
Can anyone in IDR or SIDR demystify for us here what securing BGP really requires (certificates, signatures, attestations you name it) if to secure a single prefix originated by customer site requires more then 4K of BGP message size ?
We already know that update packing is gone and that there is going to be single NLRI per update. OK or NOK but a different debate for different time.
But if securing 1 prefix really requires more then 4K of data attached to it I think we should question the entire approach rather then waist time to argue about draft-ymbk-bgp-extended-messages. Well unless this secure BGP is the only reason for this draft ;-).
Thx, R. _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
