Re: [Idr] [bess] draft-rosen-mpls-rfc3107bis

[<[e-mail]>]

From: Eric C Rosen [mailto:[e-mail]]
> the "day 1" bugs do exist


Do we really have implementation not setting the S bit on the sending side??
I don't see how this could be per design, as I fail to see a reason:
- sending with S=1 or S=0 has the same cost from an implementation perspective, so this is not a "simplification" issue
- sending with S=0 is a clear violation of RFC 3107 and will trigger a BGP session shutdown from a peer compliant with 3107, so this does not seem like a desirable goal from an implementation standpoint.

Now, that could be a bug, but that bug would be detected with the first interoperability test with a compliant RFC 3107 implementation...

So, how have we got into this situation? How can we be there 15 years after the publication of RFC 3107?

Thanks
-- Bruno





_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.