IETF Logo Mail Archive

Re: VPN Identifiers

Eric Rosen <erosen@cisco.com> Tue, 12 August 2003 18:40 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 OAA23945 for <l2vpn-archive@odin.ietf.org>; Tue, 12 Aug 2003 14:40:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19me3u-0005z6-Tb for l2vpn-archive@odin.ietf.org; Tue, 12 Aug 2003 14:40:03 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7CIe2fk022998 for l2vpn-archive@odin.ietf.org; Tue, 12 Aug 2003 14:40:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19me3u-0005yr-Mr for l2vpn-web-archive@optimus.ietf.org; Tue, 12 Aug 2003 14:40:02 -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 OAA23938 for <l2vpn-web-archive@ietf.org>; Tue, 12 Aug 2003 14:39:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19me3s-00031p-00 for l2vpn-web-archive@ietf.org; Tue, 12 Aug 2003 14:40:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19me3r-00031m-00 for l2vpn-web-archive@ietf.org; Tue, 12 Aug 2003 14:39:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19me3t-0005xl-KX; Tue, 12 Aug 2003 14:40:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19me3O-0005wZ-Ix for l2vpn@optimus.ietf.org; Tue, 12 Aug 2003 14:39:30 -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 OAA23914 for <l2vpn@ietf.org>; Tue, 12 Aug 2003 14:39:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19me3L-00031c-00 for l2vpn@ietf.org; Tue, 12 Aug 2003 14:39:27 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 19me3L-00031G-00 for l2vpn@ietf.org; Tue, 12 Aug 2003 14:39:27 -0400
Received: from cisco.com (64.102.124.13) by sj-iport-2.cisco.com with ESMTP; 12 Aug 2003 11:45:08 -0700
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36]) by rtp-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h7CIcsxc029096; Tue, 12 Aug 2003 14:38:55 -0400 (EDT)
Message-Id: <200308121838.h7CIcsxc029096@rtp-core-2.cisco.com>
To: richard.spencer@bt.com
cc: l2vpn@ietf.org
Subject: Re: VPN Identifiers
In-reply-to: Your message of Tue, 12 Aug 2003 17:33:09 +0100. <B5E87B043D4C514389141E2661D255EC019C0FEE@i2km41-ukdy.nat.bt.com>
Reply-To: erosen@cisco.com
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (Unebigoryōmae) APEL/10.3 Emacs/21.3 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset="US-ASCII"
Date: Tue, 12 Aug 2003 14:38:54 -0400
From: Eric Rosen <erosen@cisco.com>
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> If it is decided that draft-ouldbrahim-ppvpn-gid-03.txt is the best
Richard> VPN ID format to use then that's fine, but for inter-dependency and
Richard> interoperability  reasons   it  should  be  used   across  all  VPN
Richard> mechanisms. 

I have no  problem with this, but if  there is anyone who still  wants to be
able to use domain names as VPN-ids, I don't imagine they will go along with
this ;-)

Richard> Looking at draft-ouldbrahim-ppvpn-gid-03.txt,  do we really need 4+
Richard> different naming methods for a  VPN? I think two options for global
Richard> identifiers at  the most  should be sufficient,  i.e. AS#,  or OUI,
Richard> although obviously one global ID would be preferable.

With regard to the requirements you've  stated, I don't think it matters how
many different methods there are for  producing VPN-ids, as long as there is
no ambiguity introduced into the encodings.

v2.23.0 | Report a Bug | By Email