[Idr] draft-keyupate-idr-bgp-prefix-sid-00 & VPN

<bruno.decraene@orange.com> Tue, 18 November 2014 16:54 UTC

Return-Path: <bruno.decraene@orange.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0A821A1AC1 for <idr@ietfa.amsl.com>; Tue, 18 Nov 2014 08:54:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jYHe0mTZ-Iq4 for <idr@ietfa.amsl.com>; Tue, 18 Nov 2014 08:54:33 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AFAA1A1AB4 for <idr@ietf.org>; Tue, 18 Nov 2014 08:54:32 -0800 (PST)
Received: from omfeda05.si.francetelecom.fr (unknown [xx.xx.xx.198]) by omfeda11.si.francetelecom.fr (ESMTP service) with ESMTP id 843C21B873B for <idr@ietf.org>; Tue, 18 Nov 2014 17:54:30 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfeda05.si.francetelecom.fr (ESMTP service) with ESMTP id 6F95318008C for <idr@ietf.org>; Tue, 18 Nov 2014 17:54:30 +0100 (CET)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0210.002; Tue, 18 Nov 2014 17:54:30 +0100
From: bruno.decraene@orange.com
To: "idr@ietf. org" <idr@ietf.org>
Thread-Topic: draft-keyupate-idr-bgp-prefix-sid-00 & VPN
Thread-Index: AdACL5FIvYbC7/pPRc2aItnmUWFA2w==
Date: Tue, 18 Nov 2014 16:54:29 +0000
Message-ID: <19096_1416329670_546B79C6_19096_14311_1_53C29892C857584299CBF5D05346208A072659FF@PEXCVZYM11.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.197.38.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.11.18.122121
Archived-At: http://mailarchive.ietf.org/arch/msg/idr/rwSJwYTWEDsKwSk_pcKV9BiL2oU
Subject: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 & VPN
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2014 16:54:36 -0000

Hi authors,

Please find below 2 questions/comments regarding VPN applicability

1) Carrier's Carrier (CsC)
In IP VPN CsC, both the customer/CEs and the Service Provider/PE use labelled BGP routes (respectively 3107, 2547) for the same IP NLRI.
How does the draft handle this? as both usage of the SID attribute are likely to interfere (especially since both ASes will likely start their SID number from 1, hence collision is very likely).

May be adding, in the attribute, the AFI/SAFI of the SID may help.

2) SID allocation
Would SID be allocated per AS or per PE?
The former would waste the SRGB space (as 1 VPN prefix would burn a SRGB/label entry on _all_ PEs).
The latter would create SID/label collision on option B ASBR (SID 1 allocated on PE1 would collide with SID 1 allocated on PE2)

Thanks,
Regards,
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.