Re: [mpls] draft-decraene-mpls-slid-encoded-entropy-label-id (was RE: Please review the PALS/MPLS/DetNet Joint Session minutes)
<[email protected]> Fri, 1 Apr 2022 17:07:33 +0000
| Newsgroups | gmane.ietf.pwe3,gmane.ietf.mpls |
|---|---|
| Message-ID | <13430_1648832854_62473156_13430_430_1_7c2586975b3d4fea945a3fa52ee6ab9d@orange.com> |
Tony > From: Tony Li <[email protected]> On Behalf Of Tony Li > > > Bruno, > > > However, this is not a guarantee. Any design that attempts to reuse this TTL field > does run a non-zero risk of being impacted by designs that do check and reject > such entries. > [Bruno] RFC 6790 also says that on the Egress LSR “The EL's TTL MUST be > ignored.” > https://datatracker.ietf.org/doc/html/rfc6790#section-4.1 > > > Thank you, that’s a good point. Thank you for acknowledging. > However, that’s still not a guarantee (i.e. 100% > mathematical certainty). There is still risk involved. Small, but non-zero. Indeed. Exactly like any other reserved field that an IETF WG had defined and then use to extend the protocol. In the WGs that I'm following (mostly routing), I don't recall that extending (actually even defining) a reserved field had raised that amount of discussion about this mathematically non-zero probability. Discussions -if any- are mostly whether we should say MUST/MUST, SHOULD/SHOULD, MUST/SHOULD or SHOULD/MUST for the sender and receiver behaviors. And even with SHOULD, I don't recall that anyone express that non-zero probability. Plus obviously, non-zero probability is everywhere. Including in much more live critical aspects. E.g. landing is mandatory 😉. And we all live with that. (or die occasionally) --Bruno > T Orange Restricted _________________________________________________________________________________________________________________________ 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. _______________________________________________ Pals mailing list [email protected] https://www.ietf.org/mailman/listinfo/pals