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

<> Wed, 13 April 2016 11:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8E66212DD17; Wed, 13 Apr 2016 04:32:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id S3TtBNp5e2yU; Wed, 13 Apr 2016 04:32:35 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4970012DC58; Wed, 13 Apr 2016 04:32:35 -0700 (PDT)
Received: from (unknown [xx.xx.xx.1]) by (ESMTP service) with ESMTP id A63752640C2; Wed, 13 Apr 2016 13:32:33 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown []) by (ESMTP service) with ESMTP id 7FD6935C04E; Wed, 13 Apr 2016 13:32:33 +0200 (CEST)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541%19]) with mapi id 14.03.0279.002; Wed, 13 Apr 2016 13:32:33 +0200
To: Eric C Rosen <>
Thread-Topic: [bess] draft-rosen-mpls-rfc3107bis
Thread-Index: AQHRhfj1qHf38G7z/0eG06bIad1uvp9p2nRAgBygCdA=
Date: Wed, 13 Apr 2016 11:32:32 +0000
Message-ID: <7059_1460547153_570E2E51_7059_19177_1_53C29892C857584299CBF5D05346208A0F86D0FF@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <3515_1458832652_56F4050B_3515_774_1_53C29892C857584299CBF5D05346208A0F819B1E@OPEXCLILM21.corporate.adroot.infra.ftgroup> <> <9656_1458905159_56F52047_9656_7014_1_53C29892C857584299CBF5D05346208A0F81AAA7@OPEXCLILM21.corporate.adroot.infra.ftgroup>
In-Reply-To: <9656_1458905159_56F52047_9656_7014_1_53C29892C857584299CBF5D05346208A0F81AAA7@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A0F86D0FFOPEXCLILM21corp_"
MIME-Version: 1.0
X-PMX-Version:, Antispam-Engine:, Antispam-Data: 2016.4.13.110317
Archived-At: <>
Cc: "" <>, BESS <>, "" <>
Subject: Re: [mpls] [bess] draft-rosen-mpls-rfc3107bis
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 13 Apr 2016 11:32:37 -0000

Please see 1 comment inline [Bruno]

From: Eric C Rosen []

On 4/4/2016 5:28 PM,<> 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.



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.