RE: VPN Identifiers
"Hamid Ould-Brahim" <hbrahim@nortelnetworks.com> Tue, 12 August 2003 18:22 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23499 for <l2vpn-archive@odin.ietf.org>; Tue, 12 Aug 2003 14:22:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mdmW-0005GU-4a for l2vpn-archive@odin.ietf.org; Tue, 12 Aug 2003 14:22:04 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7CIM4bI020232 for l2vpn-archive@odin.ietf.org; Tue, 12 Aug 2003 14:22:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mdmV-0005GF-US for l2vpn-web-archive@optimus.ietf.org; Tue, 12 Aug 2003 14:22:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23484 for <l2vpn-web-archive@ietf.org>; Tue, 12 Aug 2003 14:21:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mdmT-0002uO-00 for l2vpn-web-archive@ietf.org; Tue, 12 Aug 2003 14:22:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19mdmS-0002uL-00 for l2vpn-web-archive@ietf.org; Tue, 12 Aug 2003 14:22:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mdmT-0005Fg-Lz; Tue, 12 Aug 2003 14:22:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mdmE-0005FJ-Vj for l2vpn@optimus.ietf.org; Tue, 12 Aug 2003 14:21:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23474 for <l2vpn@ietf.org>; Tue, 12 Aug 2003 14:21:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mdmC-0002u2-00 for l2vpn@ietf.org; Tue, 12 Aug 2003 14:21:44 -0400
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157]) by ietf-mx with esmtp (Exim 4.12) id 19mdmB-0002tc-00 for l2vpn@ietf.org; Tue, 12 Aug 2003 14:21:43 -0400
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h7CIL4018120; Tue, 12 Aug 2003 14:21:04 -0400 (EDT)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19) id <QYKXGDRR>; Tue, 12 Aug 2003 14:21:04 -0400
Message-ID: <D38D073716F2D411BEE400508BCF62960871BEF7@zcard04k.ca.nortel.com>
From: Hamid Ould-Brahim <hbrahim@nortelnetworks.com>
To: richard.spencer@bt.com, erosen@cisco.com
Cc: l2vpn@ietf.org
Subject: RE: VPN Identifiers
Date: Tue, 12 Aug 2003 14:15:33 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: l2vpn-admin@ietf.org
Errors-To: l2vpn-admin@ietf.org
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l2vpn.ietf.org>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
Richard, [clipped...] > > The point is that currently different mechanisms use different VPN ID > formats. I would say instead "different mechanisms use different global unique identifiers some of them are intended to uniquely identify a VPN." >If it is decided that > draft-ouldbrahim-ppvpn-gid-03.txt is the best > VPN ID format to use then that's fine, but for inter-dependency and > interoperability reasons it should be used across all VPN mechanisms. > Looking at draft-ouldbrahim-ppvpn-gid-03.txt, do we really > need 4+ different > naming methods for a VPN? I think two options for global > identifiers at the > most should be sufficient, i.e. AS#, or OUI, although > obviously one global > ID would be preferable. draft-ouldbrahim-ppvpn-gid-03.txt tries to define formats for supporting global unique identifiers mainly intended for VPN solutions and mostly targeting control planes, and among these formats it supports the route target and RFC2685 formats within an 8 octets length field. These ids are required to be unique only within a given solution and they do not necessarily identify a VPN. A particular solution may decide to assign a gid to uniquely identify a VPN if it wants to, and may want to use gids for other purposes as well. The draft does not solve the problem of defining a unique VPN-ID format intended to be used everywhere across all solutions including management. In my view if one wants to solve this problem and enforce that id on all solutions and on all the components of a given solution then there is already rfc2685 standard which pretty much meets the definition you mentioned below. Whether solutions within l2vpns will be using it everywhere is obviously another thing. Hamid. > > Richard > > > -----Original Message----- > > From: Eric Rosen [mailto:erosen@cisco.com] > > Sent: 11 August 2003 18:26 > > To: Spencer,R,Richard,XGH5 R > > Cc: Sasha@AXERRA.com; l2vpn@ietf.org > > Subject: Re: VPN Identifiers > > > > > > > > We already have an 8-byte VPN-Id format which can be > > based either on AS > > numbers or on OUIs, and is extensible to other possibilities > > as well. Have > > you looked at draft-ouldbrahim-ppvpn-gid-03.txt? > > > >
- RE: VPN Identifiers Sasha Vainshtein
- RE: VPN Identifiers richard.spencer
- RE: VPN Identifiers neil.2.harrison
- VPN Identifiers richard.spencer
- RE: VPN Identifiers Sasha Vainshtein
- RE: VPN Identifiers richard.spencer
- Re: VPN Identifiers Eric Rosen
- RE: VPN Identifiers Hamid Ould-Brahim
- RE: VPN Identifiers richard.spencer
- RE: VPN Identifiers Hamid Ould-Brahim
- Re: VPN Identifiers Eric Rosen
- RE: VPN Identifiers richard.spencer
- RE: VPN Identifiers richard.spencer
- RE: VPN Identifiers Giles Heron
- Re: VPN Identifiers W. Mark Townsley
- Re: VPN Identifiers Eric Rosen
- RE: VPN Identifiers Hamid Ould-Brahim