Please see 1 comment inline [Bruno]
From: Eric C Rosen [mailto:ero...@juniper.net] On 4/4/2016 5:28 PM, bruno.decra...@orange.com<mailto:bruno.decra...@orange.com> wrote: > My issue is how do we prove that_nobody_ is using it? Proving the negative > is hard, and silence is not part of the proof. To prove the negative, we > would need explicit statement from everyone, which looks impossible. I think you're exaggerating a little ;-) I'm having trouble believing that you are unable to determine whether the 3107 "multiple labels" feature is in use in any of your company's deployments. [Bruno] Indeed, we had a different perspective. On my side, I was assuming that the IETF would not introduce a non-backward compatible specification change, without first checking that none of the deployment would be affected. My point was that this is hard to prove. On your side, you were assuming that the responsibility would be on each network operator to check whether they would have an issue. This is breaking the big problem into N smaller ones. --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.
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
