IETF Logo Mail Archive

RE: Supporting 4-octet AS Number for L2VPN Auto-Discovery

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Wed, 03 September 2014 07:57 UTC

Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: l2vpn@ietfa.amsl.com
Delivered-To: l2vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEE1E1A00F1 for <l2vpn@ietfa.amsl.com>; Wed, 3 Sep 2014 00:57:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-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 9tjXXlFXiEns for <l2vpn@ietfa.amsl.com>; Wed, 3 Sep 2014 00:57:24 -0700 (PDT)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3lrp0078.outbound.protection.outlook.com [213.199.154.78]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B3631A6F97 for <l2vpn@ietf.org>; Wed, 3 Sep 2014 00:57:21 -0700 (PDT)
Received: from AM3PR03MB612.eurprd03.prod.outlook.com (10.242.110.144) by AM3PR03MB609.eurprd03.prod.outlook.com (10.242.109.149) with Microsoft SMTP Server (TLS) id 15.0.1015.19; Wed, 3 Sep 2014 07:57:19 +0000
Received: from AM3PR03MB612.eurprd03.prod.outlook.com ([10.242.110.144]) by AM3PR03MB612.eurprd03.prod.outlook.com ([10.242.110.144]) with mapi id 15.00.1015.018; Wed, 3 Sep 2014 07:57:19 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "giheron@cisco.com" <giheron@cisco.com>, "nabil.n.bitar@verizon.com" <nabil.n.bitar@verizon.com>
Subject: RE: Supporting 4-octet AS Number for L2VPN Auto-Discovery
Thread-Topic: Supporting 4-octet AS Number for L2VPN Auto-Discovery
Thread-Index: Ac/GtKtkjsOcP4ETSmKPZMvTH+Vk7gAl1Mjw
Date: Wed, 3 Sep 2014 07:57:19 +0000
Message-ID: <e62848580c84421994a85ee79320e740@AM3PR03MB612.eurprd03.prod.outlook.com>
References: <666a7f613fd548b494b58db657241699@AM3PR03MB612.eurprd03.prod.outlook.com>
In-Reply-To: <666a7f613fd548b494b58db657241699@AM3PR03MB612.eurprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [147.234.56.21]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;UriScan:;
x-forefront-prvs: 032334F434
x-forefront-antispam-report: SFV:NSPM; SFS:(53754006)(189002)(51694002)(377454003)(199003)(51874003)(252514010)(85852003)(50986999)(19580395003)(105586002)(83072002)(21056001)(16236675004)(19625215002)(107046002)(74316001)(80022001)(76482001)(33646002)(76576001)(74662001)(81342001)(81542001)(76176999)(83322001)(15975445006)(4396001)(86362001)(108616004)(15202345003)(90102001)(19300405004)(19617315012)(31966008)(20776003)(74502001)(19609705001)(54356999)(106356001)(77982001)(85306004)(95666004)(87936001)(64706001)(101416001)(92566001)(66066001)(46102001)(19580405001)(2656002)(99396002)(2501002)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:AM3PR03MB609; H:AM3PR03MB612.eurprd03.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
Content-Type: multipart/alternative; boundary="_000_e62848580c84421994a85ee79320e740AM3PR03MB612eurprd03pro_"
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/M4-X9cArDFiPsd_MqT0DOgumhcI
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "erosen@cisco.com" <erosen@cisco.com>
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer 2 Virtual Private Networks <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn/>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Sep 2014 07:57:26 -0000

Just wanted to add that RFC 5668<http://tools.ietf.org/html/rfc5668> has defined the 4-octet AS-specific Extended Community attribute for BGP.
However, there is no sub-type for this Extended community type that could be used as an L2VPN Identifier.

And my apologies to Bruce and Vasile: they (and Eric) are co-authors of 6074, but I do not have their current email addresses.
Regards,
       Sasha
Email: Alexander.Vainshtein@ecitele.com
Mobile: 054-9266302

From: L2vpn [mailto:l2vpn-bounces@ietf.org] On Behalf Of Alexander Vainshtein
Sent: Tuesday, September 02, 2014 4:49 PM
To: giheron@cisco.com; nabil.n.bitar@verizon.com
Cc: l2vpn@ietf.org; erosen@cisco.com; bsd@cisco.com
Subject: Supporting 4-octet AS Number for L2VPN Auto-Discovery

Hi all,
Section 3.2.2.1 of RFC 6074<http://tools.ietf.org/html/rfc6074> requires encoding of VPN IDs for auto-discovery purposes as Extended BGP Community attribute of BGP.
It further specifies that the following subtypes of extended community can be used for this purpose:

*         2-octet AS specific extended community. To the best of my understanding, if this subtype is used for encoding a L2VPN ID, the provide should use the 2-octet AS number assigned to it as part

*         IP address-specific extended community.

It seems that RFC 6074 does not provide any way to use 4-octet AS numbers for encoding L2VPN IDs. Is this correct?
If yes, are there any plans to augment RFC 6074 in such a way as to facilitate usage of 4-octet AS numbers in l2VPN ID encoding?

Regards, and lots of thanks in advance
       Sasha
Email: Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>
Mobile: 054-9266302

v2.8.7 | Report a Bug | By Email