RE: VPN Identifiers
richard.spencer@bt.com Wed, 13 August 2003 06:24 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 CAA04507 for <l2vpn-archive@odin.ietf.org>; Wed, 13 Aug 2003 02:24:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mp3J-00006v-LW for l2vpn-archive@odin.ietf.org; Wed, 13 Aug 2003 02:24:10 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7D6O98Z000424 for l2vpn-archive@odin.ietf.org; Wed, 13 Aug 2003 02:24:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mp3J-00006l-As for l2vpn-web-archive@optimus.ietf.org; Wed, 13 Aug 2003 02:24:09 -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 CAA03935 for <l2vpn-web-archive@ietf.org>; Wed, 13 Aug 2003 02:24:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mp3C-00071f-00 for l2vpn-web-archive@ietf.org; Wed, 13 Aug 2003 02:24:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19mp3B-00071b-00 for l2vpn-web-archive@ietf.org; Wed, 13 Aug 2003 02:24:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mp3C-00005N-Iy; Wed, 13 Aug 2003 02:24:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mp2F-0008Ux-6P for l2vpn@optimus.ietf.org; Wed, 13 Aug 2003 02:23: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 CAA02876 for <l2vpn@ietf.org>; Wed, 13 Aug 2003 02:22:58 -0400 (EDT)
From: richard.spencer@bt.com
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mp2B-00071H-00 for l2vpn@ietf.org; Wed, 13 Aug 2003 02:22:59 -0400
Received: from saturn.bt.com ([193.113.57.20] helo=cbibipnt08.hc.bt.com) by ietf-mx with esmtp (Exim 4.12) id 19mp2A-00070z-00 for l2vpn@ietf.org; Wed, 13 Aug 2003 02:22:58 -0400
Received: by cbibipnt08.hc.bt.com with Internet Mail Service (5.5.2654.89) id <QXM4KV21>; Wed, 13 Aug 2003 07:22:49 +0100
Message-ID: <B5E87B043D4C514389141E2661D255EC08B657@i2km41-ukdy.nat.bt.com>
To: hbrahim@nortelnetworks.com, erosen@cisco.com
Cc: l2vpn@ietf.org
Subject: RE: VPN Identifiers
Date: Wed, 13 Aug 2003 07:22:23 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.89)
content-class: urn:content-classes:message
Content-Type: text/plain; charset="iso-8859-1"
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>
Hamid, I understand that your GID draft is not intended to solve the problem of defining a unique VPN-ID format and I agree that RFC2685 meets the requirements for a VPN-ID. If there is consensus that this is the best VPN ID to use then I would like to see all the drafts support its use. Richard > -----Original Message----- > From: Hamid Ould-Brahim [mailto:hbrahim@nortelnetworks.com] > Sent: 12 August 2003 19:16 > To: Spencer,R,Richard,XGH5 R; erosen@cisco.com > Cc: l2vpn@ietf.org > Subject: RE: VPN Identifiers > > > 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