[mpls] draft-rosen-mpls-rfc3107bis-00

<bruno.decraene@orange.com> Wed, 13 April 2016 11:33 UTC

Return-Path: <bruno.decraene@orange.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 5457412DF51; Wed, 13 Apr 2016 04:33:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.915
X-Spam-Status: No, score=-2.915 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 3r0uo0qeZSud; Wed, 13 Apr 2016 04:32:59 -0700 (PDT)
Received: from relais-inet.orange.com (relais-nor34.orange.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E30E12DEDB; Wed, 13 Apr 2016 04:32:48 -0700 (PDT)
Received: from opfednr02.francetelecom.fr (unknown [xx.xx.xx.66]) by opfednr26.francetelecom.fr (ESMTP service) with ESMTP id E4FE22033B; Wed, 13 Apr 2016 13:32:46 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.58]) by opfednr02.francetelecom.fr (ESMTP service) with ESMTP id ADE37120055; Wed, 13 Apr 2016 13:32:46 +0200 (CEST)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM33.corporate.adroot.infra.ftgroup ([fe80::3881:fc15:b4b2:9017%19]) with mapi id 14.03.0279.002; Wed, 13 Apr 2016 13:32:46 +0200
From: bruno.decraene@orange.com
To: "Eric C Rosen (erosen@juniper.net)" <erosen@juniper.net>
Thread-Topic: draft-rosen-mpls-rfc3107bis-00
Thread-Index: AdGVaWAVw1/+shVVQDGYCBeSt0ROWg==
Date: Wed, 13 Apr 2016 11:32:45 +0000
Message-ID: <12391_1460547166_570E2E5E_12391_13123_1_53C29892C857584299CBF5D05346208A0F86D11B@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/fsq7uYE5Szp2XjfQ3eUNTITaz3M>
Cc: "mpls@ietf.org" <mpls@ietf.org>, BESS <bess@ietf.org>, "idr@ietf.org" <idr@ietf.org>
Subject: [mpls] draft-rosen-mpls-rfc3107bis-00
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Apr 2016 11:33:09 -0000

Hi Eric,

- Do you think that it may be useful to have a sentence about Carrier's Carrier IP VPN? I fear that some implementation may allow multiple labels for SAFI 4 (labelled IP) but not for SAFI 128 (VPN) and would not be capable of translating/swapping from N labels on the PE-CE (SAFI 4) side, toward 1 label to the PE-PE (SAFI 128) side. In such case, it may be preferable to advertise this non-capability on the PE-CE side (e.g. by sending the multiple label capability with a max label of 1)

- The current BGP capability encoding does not allow for the sending a different number of accepted labels on a per SAFI basis. I don't know whether this could be useful (in the future) but I do note that, as indicated in the draft, it's already useful to be able to advertise N>1 for some SAFI and N=1 for some others. So may be the flexibility could be useful. I'll leave the cost/benefit choice up to you.



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.