From exim@www1.ietf.org  Tue Sep  2 09:38:40 2003
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 JAA24127
	for <l3vpn-archive@odin.ietf.org>; Tue, 2 Sep 2003 09:38:40 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19uBMM-00025P-UO
	for l3vpn-archive@odin.ietf.org; Tue, 02 Sep 2003 09:38:15 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h82DcEbc008012
	for l3vpn-archive@odin.ietf.org; Tue, 2 Sep 2003 09:38:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19uBMM-00024o-0G
	for l3vpn-web-archive@optimus.ietf.org; Tue, 02 Sep 2003 09:38:14 -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 JAA23980
	for <l3vpn-web-archive@ietf.org>; Tue, 2 Sep 2003 09:38:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19uBMK-0007cn-00
	for l3vpn-web-archive@ietf.org; Tue, 02 Sep 2003 09:38:12 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19uBMJ-0007ck-00
	for l3vpn-web-archive@ietf.org; Tue, 02 Sep 2003 09:38:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19uB8b-0006gI-3M; Tue, 02 Sep 2003 09:24:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19uAnz-00049c-Pf
	for l3vpn@optimus.ietf.org; Tue, 02 Sep 2003 09:02:44 -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 JAA19470
	for <l3vpn@ietf.org>; Tue, 2 Sep 2003 09:02:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19uAny-0004Yw-00
	for l3vpn@ietf.org; Tue, 02 Sep 2003 09:02:42 -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 19uAnx-0004VF-00
	for l3vpn@ietf.org; Tue, 02 Sep 2003 09:02:41 -0400
Received: from cisco.com (171.71.177.238)
  by sj-iport-2.cisco.com with ESMTP; 02 Sep 2003 06:13:53 -0700
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h82D27Cb025284;
	Tue, 2 Sep 2003 06:02:08 -0700 (PDT)
Received: from cisco.com (ams-rraszuk-vpn5.cisco.com [10.61.160.6])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id ALA74705;
	Tue, 2 Sep 2003 05:52:12 -0700 (PDT)
Message-ID: <3F5494CB.F0EB1C13@cisco.com>
Date: Tue, 02 Sep 2003 15:02:03 +0200
From: Robert Raszuk <raszuk@cisco.com>
Reply-To: raszuk@cisco.com
Organization: Signature: http://www.employees.org/~raszuk/sig/
X-Mailer: Mozilla 4.79 [en]C-CCK-MCD   (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Vincent Parfait <vinceparfait@yahoo.com>
CC: Thomas Narten <narten@us.ibm.com>, l3vpn@ietf.org, rick@rhwilder.net,
        rcallon@juniper.net, ronald.p.bonica@mci.com, jguichar@cisco.com
Subject: Re: Address Allocation for PE-CE links
References: <20030901135401.51405.qmail@web20504.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Vincent,

The draft does addresses a real need - I must admit so. But since the
very early days of this draft I am not sure if the approach sugested has
a possibility to work. The draft is based on assumption that there is a
solid line on the definition of "Service Provider" as such entity. 

From my experience with all practical reason there is no such solid
line. I know a lot of global enterprises with dedicated network
departments who provide services to their own branches or to other
smaller enterprises and may in turn use Tear-1 providers for their POPs
connectivty. So if they would start using defined here address ranges I
think the draft's main benefit is out. The same applies to smaller SPs
offerering 2547bis and yet using global SPs for connectivity. 

So at minimum I would like to see a clearly added definition who the
"Service Provider" is to the draft. Example: "Service Provider is an
entity who does not use any other provider for L3 connectvity" (if such
a definition will be accepted by L3VPN community ;). 

Rgs,
R.




From exim@www1.ietf.org  Tue Sep  2 09:40:28 2003
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 JAA24815
	for <l3vpn-archive@odin.ietf.org>; Tue, 2 Sep 2003 09:40:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19uB4d-000627-4i
	for l3vpn-archive@odin.ietf.org; Tue, 02 Sep 2003 09:20:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h82DJtPr023190
	for l3vpn-archive@odin.ietf.org; Tue, 2 Sep 2003 09:19:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19u991-000777-O3
	for l3vpn-web-archive@optimus.ietf.org; Tue, 02 Sep 2003 07:16:20 -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 HAA11435
	for <l3vpn-web-archive@ietf.org>; Tue, 2 Sep 2003 07:16:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19u991-0004RJ-00
	for l3vpn-web-archive@ietf.org; Tue, 02 Sep 2003 07:16:19 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19u990-0004R9-00
	for l3vpn-web-archive@ietf.org; Tue, 02 Sep 2003 07:16:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19u57G-00060a-Is; Tue, 02 Sep 2003 02:58:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19u1Fz-0002Sx-Cx
	for l3vpn@optimus.ietf.org; Mon, 01 Sep 2003 22:50:59 -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 WAA02000
	for <l3vpn@ietf.org>; Mon, 1 Sep 2003 22:50:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19u1Fu-0002lW-00
	for l3vpn@ietf.org; Mon, 01 Sep 2003 22:50:54 -0400
Received: from web20504.mail.yahoo.com ([216.136.226.139])
	by ietf-mx with smtp (Exim 4.12)
	id 19tp86-0007Yp-00
	for l3vpn@ietf.org; Mon, 01 Sep 2003 09:54:02 -0400
Message-ID: <20030901135401.51405.qmail@web20504.mail.yahoo.com>
Received: from [57.250.229.136] by web20504.mail.yahoo.com via HTTP; Mon, 01 Sep 2003 06:54:01 PDT
Date: Mon, 1 Sep 2003 06:54:01 -0700 (PDT)
From: Vincent Parfait <vinceparfait@yahoo.com>
Subject: Re: Address Allocation for PE-CE links 
To: Thomas Narten <narten@us.ibm.com>
Cc: l3vpn@ietf.org, rick@rhwilder.net, rcallon@juniper.net,
        ronald.p.bonica@mci.com, jguichar@cisco.com
In-Reply-To: <200308281514.h7SFEnT3021527@rotala.raleigh.ibm.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1993448076-1062424441=:50314"
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>

--0-1993448076-1062424441=:50314
Content-Type: text/plain; charset=us-ascii


Thanks for your reply and comments.

Regarding your point 2 - size of the address block - the /12 should be sufficient for most SPs (allowing for more than 250K CEs). If ever one SP needs more addresses, then a new address allocation request could be issued. However, when reaching such number of CEs, an SP will likely face other scaling issues requiring the partitioning of the management system. 

As you pointed out in 3, the most important is then to prove that this /12 would provide a real benefit wrt the conservation of the global address space. Unfortunately nobody will be able to produce tangible evidence like listing all SP's addressing requirements ... However simple calculation show there is a case. There are currently tens of SPs deploying 2547-like VPNs. If let say only 30 of them will manage 80K connections, then 150 class B will be needed to addess these connections, ie almost 10 times more than the requested range !

Regarding point 4, let say this proposal does not pretend to do any better than private addressing based on RFC1918 addressing 

Discussions on this draft always converged to the fact that it would be too difficult, and not justified, to request a /8. Today the draft defines a pragmatic approach in order to move forward. Shouldn't IANA be contacted at this stage to discuss with them the type of consensus needed ? Any idea on the people to contact ? 

Vincent


Thomas Narten <narten@us.ibm.com> wrote:This document has come up within some informal IESG discussions. There
may well be some serious difficulty in convincing the IESG, IANA,
etc. that this is a good idea. Note also the comment from the Yokohama
meeting:

> Scott - The likelihood of setting aside a /8 for VPN providers is
> close to zero.

Bottom line: this document will not be an easy sell, and needs careful
and rigorous justification, as well as strong community consensus.

I think I understand the problem this document is trying to
solve. Namely, rather than use global/public address space to number
certain links, they can all be numbered out of a single SP-reserved
prefix.

Main Benefits: conserve global address space, don't need to get it
from RIRs.

Having said that, I'll note:

1) There are very few address blocks that are reserved for a
particular purpose (e.g., net 10, etc.). Thus, _any_ proposal to
reserve a chunk of space for some special purpose (other than
normal global numbering) will be viewed skeptically. The bar for
such allocations is high. So even if this WG thinks this makes
sense, the larger IETF community may not.

2) The document makes no serious attempt to quantify why /12 is the
right amount. Can't it be made smaller? (and note, the smaller the
size, the easier it will be to justify I suspect). On the other
hand, how do we know whether the size is large enough? If it isn't,
then what happens? Does the allocation in fact then not really
solve the problem and/or are we back where we started?

3) I don't see right off why these can't just be numbered out of
global space. Sure, conserving addresses is goodness, but the real
question is whether the cost of the proposal justifies the
benefits. If no allocation were given for this purpose, just how
much global space would be "wasted"? Is this amount worth trying to
conserve when looking at the big picture? (In my mind, this is the
critical question.)

4) Finally, what happens with SPs merge through acquisitions and such?
Using this scheme, one immediately has collisions among the
addresses used by the merged orgnizations, which is presumably not
a feature. Indeed, this may make the end result rather painful when
compared with just using global space. So, this scheme _does_ have
potentially serious drawbacks compared with just using public
addresses.

Thomas 





---------------------------------
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
--0-1993448076-1062424441=:50314
Content-Type: text/html; charset=us-ascii

<DIV><FONT face=Helv size=2>
<P>Thanks for your reply and comments.</P>
<P>Regarding your point 2 - size of the address block - the /12 should be sufficient for most SPs (allowing for more than 250K CEs). If ever one SP needs more addresses, then a new address allocation request could be issued. However, when reaching such number of CEs, an SP will likely face other scaling issues requiring the partitioning of the management system. </P>
<P>As you pointed out in 3, the most important is then to prove that this /12 would provide a real benefit wrt the conservation of the global address space. Unfortunately nobody will be able to produce tangible evidence like listing all SP's addressing requirements ... However simple calculation show there is a case. There are currently tens of SPs deploying 2547-like VPNs. If let say only 30 of them will manage 80K connections, then 150 class B will be needed to addess these connections, ie almost 10 times more than the requested range !</P>
<P>Regarding point 4, let say this proposal does not pretend to do any better than private addressing based on RFC1918 addressing </P>
<P>Discussions on this draft always converged to the fact that it would be too difficult, and not justified, to request a /8. Today the draft defines a pragmatic approach in order to move forward. Shouldn't IANA be contacted at this stage to&nbsp;discuss with them the type of consensus needed ? Any idea on the&nbsp;people to contact&nbsp;?&nbsp;</P></FONT></DIV>
<DIV>Vincent</DIV>
<DIV><BR><BR><B><I>Thomas Narten &lt;narten@us.ibm.com&gt;</I></B> wrote:
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">This document has come up within some informal IESG discussions. There<BR>may well be some serious difficulty in convincing the IESG, IANA,<BR>etc. that this is a good idea. Note also the comment from the Yokohama<BR>meeting:<BR><BR>&gt; Scott - The likelihood of setting aside a /8 for VPN providers is<BR>&gt; close to zero.<BR><BR>Bottom line: this document will not be an easy sell, and needs careful<BR>and rigorous justification, as well as strong community consensus.<BR><BR>I think I understand the problem this document is trying to<BR>solve. Namely, rather than use global/public address space to number<BR>certain links, they can all be numbered out of a single SP-reserved<BR>prefix.<BR><BR>Main Benefits: conserve global address space, don't need to get it<BR>from RIRs.<BR><BR>Having said that, I'll note:<BR><BR>1) There are very few address blocks that are reserved for
 a<BR>particular purpose (e.g., net 10, etc.). Thus, _any_ proposal to<BR>reserve a chunk of space for some special purpose (other than<BR>normal global numbering) will be viewed skeptically. The bar for<BR>such allocations is high. So even if this WG thinks this makes<BR>sense, the larger IETF community may not.<BR><BR>2) The document makes no serious attempt to quantify why /12 is the<BR>right amount. Can't it be made smaller? (and note, the smaller the<BR>size, the easier it will be to justify I suspect). On the other<BR>hand, how do we know whether the size is large enough? If it isn't,<BR>then what happens? Does the allocation in fact then not really<BR>solve the problem and/or are we back where we started?<BR><BR>3) I don't see right off why these can't just be numbered out of<BR>global space. Sure, conserving addresses is goodness, but the real<BR>question is whether the cost of the proposal justifies the<BR>benefits. If no allocation were given for this purpose, just
 how<BR>much global space would be "wasted"? Is this amount worth trying to<BR>conserve when looking at the big picture? (In my mind, this is the<BR>critical question.)<BR><BR>4) Finally, what happens with SPs merge through acquisitions and such?<BR>Using this scheme, one immediately has collisions among the<BR>addresses used by the merged orgnizations, which is presumably not<BR>a feature. Indeed, this may make the end result rather painful when<BR>compared with just using global space. So, this scheme _does_ have<BR>potentially serious drawbacks compared with just using public<BR>addresses.<BR><BR>Thomas <BR><BR><BR></BLOCKQUOTE></DIV><p><hr SIZE=1>
Do you Yahoo!?<br>
<a href="http://us.rd.yahoo.com/evt=10469/*http://sitebuilder.yahoo.com">Yahoo! SiteBuilder</a> - Free, easy-to-use web site design software
--0-1993448076-1062424441=:50314--




From exim@www1.ietf.org  Mon Sep  8 12:05:30 2003
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 MAA04716
	for <l3vpn-archive@odin.ietf.org>; Mon, 8 Sep 2003 12:05: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 19wOVn-0002D0-1W
	for l3vpn-archive@odin.ietf.org; Mon, 08 Sep 2003 12:05:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h88G565f008433
	for l3vpn-archive@odin.ietf.org; Mon, 8 Sep 2003 12:05:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19wOVm-0002BG-Ow
	for l3vpn-web-archive@optimus.ietf.org; Mon, 08 Sep 2003 12:05:06 -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 MAA04679
	for <l3vpn-web-archive@ietf.org>; Mon, 8 Sep 2003 12:04:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19wOVl-00028q-00
	for l3vpn-web-archive@ietf.org; Mon, 08 Sep 2003 12:05:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19wOVl-00028m-00
	for l3vpn-web-archive@ietf.org; Mon, 08 Sep 2003 12:05:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19wOVi-0002AQ-IU; Mon, 08 Sep 2003 12:05:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19wOVP-00029i-P1
	for l3vpn@optimus.ietf.org; Mon, 08 Sep 2003 12:04:43 -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 MAA04640
	for <l3vpn@ietf.org>; Mon, 8 Sep 2003 12:04:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19wOVO-00028A-00
	for l3vpn@ietf.org; Mon, 08 Sep 2003 12:04:42 -0400
Received: from pmesmtp01.wcom.com ([199.249.20.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19wOVN-00027F-00
	for l3vpn@ietf.org; Mon, 08 Sep 2003 12:04:41 -0400
Received: from dgismtp01.wcomnet.com ([166.38.58.141])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0HKW00H4CKGCLU@firewall.wcom.com> for l3vpn@ietf.org; Mon,
 08 Sep 2003 16:00:12 +0000 (GMT)
Received: from dgismtp01.wcomnet.com by dgismtp01.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HKW00I01KF3WF@dgismtp01.wcomnet.com> for l3vpn@ietf.org; Mon,
 08 Sep 2003 16:00:12 +0000 (GMT)
Received: from rbonica ([166.32.199.163])
 by dgismtp01.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with SMTP id <0HKW00HOKKG19M@dgismtp01.wcomnet.com> for l3vpn@ietf.org;
 Mon, 08 Sep 2003 16:00:02 +0000 (GMT)
Date: Mon, 08 Sep 2003 12:00:41 -0400
From: Ron Bonica <Ronald.P.Bonica@mci.com>
Subject: RE: I-D ACTION:draft-ietf-l3vpn-l3vpn-auth-00.txt
In-reply-to: <200309081407.KAA21779@ietf.org>
To: l3vpn@ietf.org
Message-id: <DKEJJCOCJMHEFFNMLKMPKENLKDAA.Ronald.P.Bonica@mci.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

This is a refresh of draft-ietf-ppvpn-l3vpn-auth. The filename has been
changed to reflect the new WG name.

                                              Ron


> -----Original Message-----
> From: l3vpn-admin@ietf.org [mailto:l3vpn-admin@ietf.org]On Behalf Of
> Internet-Drafts@ietf.org
> Sent: Monday, September 08, 2003 10:07 AM
> To: IETF-Announce:
> Cc: l3vpn@ietf.org
> Subject: I-D ACTION:draft-ietf-l3vpn-l3vpn-auth-00.txt
>
>
> A New Internet-Draft is available from the on-line
> Internet-Drafts directories.
> This draft is a work item of the Layer 3 Virtual Private Networks
> Working Group of the IETF.
>
> 	Title		: CE-to-CE Member Verification for Layer 3 VPNs
> 	Author(s)	: R. Bonica et al.
> 	Filename	: draft-ietf-l3vpn-l3vpn-auth-00.txt
> 	Pages		: 9
> 	Date		: 2003-9-8
>
> This document describes a CE-based verification mechanism that PPVPN
> customers can use to detect security breaches caused by
> misconfiguration of the provider network.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-l3vpn-auth-00.txt
>
> To remove yourself from the IETF Announcement list, send a message to
> ietf-announce-request with the word unsubscribe in the body of
> the message.
>
> Internet-Drafts are also available by anonymous FTP. Login with
> the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-l3vpn-l3vpn-auth-00.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-l3vpn-l3vpn-auth-00.txt".
>
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>





From exim@www1.ietf.org  Tue Sep  9 09:52:03 2003
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 JAA07722
	for <l3vpn-archive@odin.ietf.org>; Tue, 9 Sep 2003 09:52:03 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19wiu9-0006BQ-AM
	for l3vpn-archive@odin.ietf.org; Tue, 09 Sep 2003 09:51:37 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h89DpbZd023764
	for l3vpn-archive@odin.ietf.org; Tue, 9 Sep 2003 09:51:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19wiu9-0006BD-6t
	for l3vpn-web-archive@optimus.ietf.org; Tue, 09 Sep 2003 09:51:37 -0400
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 JAA07603
	for <l3vpn-web-archive@ietf.org>; Tue, 9 Sep 2003 09:51: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 19wita-00061Y-BH; Tue, 09 Sep 2003 09:51:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19witW-00060j-Pi
	for l3vpn@optimus.ietf.org; Tue, 09 Sep 2003 09:50:58 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07478;
	Tue, 9 Sep 2003 09:50:50 -0400 (EDT)
Message-Id: <200309091350.JAA07478@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: l3vpn@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-l3vpn-security-framework-00.txt
Date: Tue, 09 Sep 2003 09:50:50 -0400
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Layer 3 Virtual Private Networks Working Group of the IETF.

	Title		: Security Framework for Provider Provisioned Virtual 
                          Private Networks
	Author(s)	: L. Fang et al.
	Filename	: draft-ietf-l3vpn-security-framework-00.txt
	Pages		: 35
	Date		: 2003-9-9
	
This draft addresses security aspects pertaining to Provider 
Provisioned Virtual Private Networks (PPVPNs). We first describe 
the security threats that are relevant in the context of PPVPNs, 
and the defensive techniques that can be used to combat those 
threats. We consider security issues deriving both from malicious 
behavior of anyone and from negligent or incorrect behavior of the 
providers. We also describe how these security attacks should be 
detected and reported. We then discuss the possible user 
requirements in terms of security in a PPVPN service. These user 
requirements translate into corresponding requirements for the 
providers. In addition, the provider may have additional 
requirements to make its network infrastructure secure to a level 
that can meet the PPVPN customer's expectations. Finally, we define 
a template that may be used to analyze the security characteristics 
of a specific PPVPN technology and describe them in a manner 
consistent with this framework.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-security-framework-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-l3vpn-security-framework-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-l3vpn-security-framework-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-9-9092220.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l3vpn-security-framework-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-l3vpn-security-framework-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-9-9092220.I-D@ietf.org>

--OtherAccess--

--NextPart--






From exim@www1.ietf.org  Tue Sep  9 10:12:00 2003
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 KAA10916
	for <l3vpn-archive@odin.ietf.org>; Tue, 9 Sep 2003 10:12:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19wjDR-0008Fs-Tp
	for l3vpn-archive@odin.ietf.org; Tue, 09 Sep 2003 10:11:34 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h89EBXnm031725
	for l3vpn-archive@odin.ietf.org; Tue, 9 Sep 2003 10:11:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19wjDR-0008Fc-PK
	for l3vpn-web-archive@optimus.ietf.org; Tue, 09 Sep 2003 10:11:33 -0400
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 KAA10818
	for <l3vpn-web-archive@ietf.org>; Tue, 9 Sep 2003 10:11:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19wjCv-0008DA-P1; Tue, 09 Sep 2003 10:11:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19wjCk-0008CY-55
	for l3vpn@optimus.ietf.org; Tue, 09 Sep 2003 10:10:50 -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 KAA10629
	for <l3vpn@ietf.org>; Tue, 9 Sep 2003 10:10:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19wjCh-0003fq-00
	for l3vpn@ietf.org; Tue, 09 Sep 2003 10:10:48 -0400
Received: from dgesmtp01.wcom.com ([199.249.16.16])
	by ietf-mx with esmtp (Exim 4.12)
	id 19wjCh-0003dL-00
	for l3vpn@ietf.org; Tue, 09 Sep 2003 10:10:47 -0400
Received: from pmismtp06.wcomnet.com ([166.38.62.54])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0HKY00MF39TJOF@firewall.wcom.com> for l3vpn@ietf.org; Tue,
 09 Sep 2003 14:05:43 +0000 (GMT)
Received: from pmismtp06.wcomnet.com by pmismtp06.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HKY00K019S4VS@pmismtp06.wcomnet.com> for l3vpn@ietf.org; Tue,
 09 Sep 2003 14:05:43 +0000 (GMT)
Received: from rbonica ([166.32.199.163])
 by pmismtp06.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with SMTP id <0HKY00JCP9TITX@pmismtp06.wcomnet.com> for l3vpn@ietf.org;
 Tue, 09 Sep 2003 14:05:42 +0000 (GMT)
Date: Tue, 09 Sep 2003 10:06:22 -0400
From: Ron Bonica <Ronald.P.Bonica@mci.com>
Subject: WG Last call: draft-ietf-l3vpn-security-framework-00.txt
To: l3vpn@ietf.org
Message-id: <DKEJJCOCJMHEFFNMLKMPKEABKEAA.Ronald.P.Bonica@mci.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

This begins a WG last call on draft-ietf-l3vpn-security-framework-00. The
last call is to end at COB on September 23.

                                        Ron


> -----Original Message-----
> From: l3vpn-admin@ietf.org [mailto:l3vpn-admin@ietf.org]On Behalf Of
> Internet-Drafts@ietf.org
> Sent: Tuesday, September 09, 2003 9:51 AM
> To: IETF-Announce:
> Cc: l3vpn@ietf.org
> Subject: I-D ACTION:draft-ietf-l3vpn-security-framework-00.txt
>
>
> A New Internet-Draft is available from the on-line
> Internet-Drafts directories.
> This draft is a work item of the Layer 3 Virtual Private Networks
> Working Group of the IETF.
>
> 	Title		: Security Framework for Provider
> Provisioned Virtual
>                           Private Networks
> 	Author(s)	: L. Fang et al.
> 	Filename	: draft-ietf-l3vpn-security-framework-00.txt
> 	Pages		: 35
> 	Date		: 2003-9-9
>
> This draft addresses security aspects pertaining to Provider
> Provisioned Virtual Private Networks (PPVPNs). We first describe
> the security threats that are relevant in the context of PPVPNs,
> and the defensive techniques that can be used to combat those
> threats. We consider security issues deriving both from malicious
> behavior of anyone and from negligent or incorrect behavior of the
> providers. We also describe how these security attacks should be
> detected and reported. We then discuss the possible user
> requirements in terms of security in a PPVPN service. These user
> requirements translate into corresponding requirements for the
> providers. In addition, the provider may have additional
> requirements to make its network infrastructure secure to a level
> that can meet the PPVPN customer's expectations. Finally, we define
> a template that may be used to analyze the security characteristics
> of a specific PPVPN technology and describe them in a manner
> consistent with this framework.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-security-fram
ework-00.txt

To remove yourself from the IETF Announcement list, send a message to
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-l3vpn-security-framework-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-l3vpn-security-framework-00.txt".

NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.





From exim@www1.ietf.org  Mon Sep 15 14:30:32 2003
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 OAA17317
	for <l3vpn-archive@odin.ietf.org>; Mon, 15 Sep 2003 14:30:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19yy6y-0004SI-UP
	for l3vpn-archive@odin.ietf.org; Mon, 15 Sep 2003 14:30:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8FIU8rO017083
	for l3vpn-archive@odin.ietf.org; Mon, 15 Sep 2003 14:30:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19yy6y-0004RN-Mn
	for l3vpn-web-archive@optimus.ietf.org; Mon, 15 Sep 2003 14:30:08 -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 OAA17196
	for <l3vpn-web-archive@ietf.org>; Mon, 15 Sep 2003 14:30:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19yy6v-0003kW-00
	for l3vpn-web-archive@ietf.org; Mon, 15 Sep 2003 14:30:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19yy6v-0003kO-00
	for l3vpn-web-archive@ietf.org; Mon, 15 Sep 2003 14:30:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19yy6u-0004QS-55; Mon, 15 Sep 2003 14:30:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19yy6b-0004PY-LG
	for l3vpn@optimus.ietf.org; Mon, 15 Sep 2003 14:29:45 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17130;
	Mon, 15 Sep 2003 14:29:35 -0400 (EDT)
Message-Id: <200309151829.OAA17130@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: l3vpn@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-l3vpn-as2547-02.txt
Date: Mon, 15 Sep 2003 14:29:35 -0400
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Layer 3 Virtual Private Networks Working Group of the IETF.

	Title		: Applicability Statement for BGP/MPLS IP VPNs
	Author(s)	: E. Rosen
	Filename	: draft-ietf-l3vpn-as2547-02.txt
	Pages		: 24
	Date		: 2003-9-15
	
This document provides an Applicability Statement for the VPN
solution described in [2547bis] and other documents listed in the
References section.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-as2547-02.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-l3vpn-as2547-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-l3vpn-as2547-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-9-15131511.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l3vpn-as2547-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-l3vpn-as2547-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-9-15131511.I-D@ietf.org>

--OtherAccess--

--NextPart--






From exim@www1.ietf.org  Mon Sep 15 14:30:32 2003
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 OAA17314
	for <l3vpn-archive@odin.ietf.org>; Mon, 15 Sep 2003 14:30:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19yy6y-0004Rl-S2
	for l3vpn-archive@odin.ietf.org; Mon, 15 Sep 2003 14:30:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8FIU8wJ017085
	for l3vpn-archive@odin.ietf.org; Mon, 15 Sep 2003 14:30:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19yy6y-0004RO-N8
	for l3vpn-web-archive@optimus.ietf.org; Mon, 15 Sep 2003 14:30:08 -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 OAA17194
	for <l3vpn-web-archive@ietf.org>; Mon, 15 Sep 2003 14:30:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19yy6v-0003kX-00
	for l3vpn-web-archive@ietf.org; Mon, 15 Sep 2003 14:30:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19yy6v-0003kN-00
	for l3vpn-web-archive@ietf.org; Mon, 15 Sep 2003 14:30:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19yy6t-0004QF-M6; Mon, 15 Sep 2003 14:30:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19yy6V-0004PT-1P
	for l3vpn@optimus.ietf.org; Mon, 15 Sep 2003 14:29:39 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17114;
	Mon, 15 Sep 2003 14:29:30 -0400 (EDT)
Message-Id: <200309151829.OAA17114@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: l3vpn@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-l3vpn-rfc2547bis-01.txt
Date: Mon, 15 Sep 2003 14:29:30 -0400
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Layer 3 Virtual Private Networks Working Group of the IETF.

	Title		: BGP/MPLS IP VPNs
	Author(s)	: E. Rosen
	Filename	: draft-ietf-l3vpn-rfc2547bis-01.txt
	Pages		: 47
	Date		: 2003-9-15
	
This document describes a method by which a Service Provider may use
an IP backbone to provide VPNs (Virtual Private Networks) for its
customers.  This method uses a 'peer model', in which the customers'
edge routers ('CE routers') send their routes to the Service
Provider's edge routers ('PE routers').  BGP is then used by the
Service Provider to exchange the routes of a particular VPN among the
PE routers that are attached to that VPN.  This is done in a way
which ensures that routes from different VPNs remain distinct and
separate, even if two VPNs have an overlapping address space.  The PE
routers distribute, to the CE routers in a particular VPN, the routes
from other the CE routers in that VPN.  The CE routers do not peer
with each other, hence there is no 'overlay' visible to the VPN's
routing algorithm.
Each route within a VPN is assigned an MPLS label; when BGP
distributes a VPN route, it also distributes an MPLS label for that
route.  Before a customer data packet travels across the Service
Provider's backbone, it is encapsulated with the MPLS label that
corresponds, in the customer's VPN, to the route that is the best
match to the packet's destination address.  This MPLS packet is
further encapsulated (e.g., with another MPLS label, or with an IP or
GRE tunnel header) so that it gets tunneled across the backbone to
the proper PE router.  Thus the backbone core routers do not need to
know the VPN routes.
The primary goal of this method is to support the case in which a
client obtains IP backbone services from a Service Provider or
Service Providers with which it maintains contractual relationships.
The client may be an enterprise, a group of enterprises which need an
extranet, an Internet Service Provider, an application service
provider, another VPN Service Provider which uses this same method to
offer VPNs to clients of its own, etc.  The method makes it very
simple for the client to use the backbone services.  It is also very
scalable and flexible for the Service Provider, and allows the
Service Provider to add value.
This document obsoletes RFC 2547.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-rfc2547bis-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-l3vpn-rfc2547bis-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-l3vpn-rfc2547bis-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-9-15131451.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l3vpn-rfc2547bis-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-l3vpn-rfc2547bis-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-9-15131451.I-D@ietf.org>

--OtherAccess--

--NextPart--






From exim@www1.ietf.org  Tue Sep 16 08:55:29 2003
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 IAA10325
	for <l3vpn-archive@odin.ietf.org>; Tue, 16 Sep 2003 08:55: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 19zFMH-0004JU-Ls
	for l3vpn-archive@odin.ietf.org; Tue, 16 Sep 2003 08:55:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8GCt5nj016573
	for l3vpn-archive@odin.ietf.org; Tue, 16 Sep 2003 08:55:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zFMH-0004JE-Fa
	for l3vpn-web-archive@optimus.ietf.org; Tue, 16 Sep 2003 08:55:05 -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 IAA10297
	for <l3vpn-web-archive@ietf.org>; Tue, 16 Sep 2003 08:54:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19zFMG-0000uW-00
	for l3vpn-web-archive@ietf.org; Tue, 16 Sep 2003 08:55:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19zFMF-0000uS-00
	for l3vpn-web-archive@ietf.org; Tue, 16 Sep 2003 08:55:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zFME-0004I4-PG; Tue, 16 Sep 2003 08:55:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zFLm-0004H3-Oc
	for l3vpn@optimus.ietf.org; Tue, 16 Sep 2003 08:54:34 -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 IAA10272
	for <l3vpn@ietf.org>; Tue, 16 Sep 2003 08:54:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19zFLl-0000tk-00
	for l3vpn@ietf.org; Tue, 16 Sep 2003 08:54:33 -0400
Received: from [202.54.124.153] (helo=rediffmail.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19zFLk-0000tI-00
	for l3vpn@ietf.org; Tue, 16 Sep 2003 08:54:32 -0400
Received: (qmail 12934 invoked by uid 510); 16 Sep 2003 12:52:09 -0000
Date: 16 Sep 2003 12:52:09 -0000
Message-ID: <20030916125209.12931.qmail@webmail8.rediffmail.com>
Received: from unknown (203.197.138.199) by rediffmail.com via HTTP; 16 sep 2003 12:52:08 -0000
MIME-Version: 1.0
From: "naresh  paliwal" <paliwalnaresh@rediffmail.com>
Reply-To: "naresh  paliwal" <paliwalnaresh@rediffmail.com>
To: l3vpn@ietf.org
Subject: export RTs
Content-type: text/plain;
	format=flowed
Content-Disposition: inline
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>

What if I add/delete a export RT of a VPN?

As far as i know, Its not discussed in the latest BGP/MPLS VPNs 
draft. The draft discusses about import RT (VPN join and prune) 
only.

"How the change in export RT should be handled" is my problem 
basically.
Readvertsing all the routes belong to the VPN doesnot help, I have 
analysed it very carefully. It has problems while deleting export 
RT.

Can it be possible to handle change of export RT without 
disrupting the bgp session??

Regards
Naresh Paliwal
___________________________________________________
Meet your old school or college friends from
1 Million + database...
Click here to reunite www.batchmates.com/rediff.asp






From exim@www1.ietf.org  Tue Sep 16 09:42:40 2003
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 IAA10324
	for <l3vpn-archive@odin.ietf.org>; Tue, 16 Sep 2003 08:55: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 19zFMH-0004Jj-Op
	for l3vpn-archive@odin.ietf.org; Tue, 16 Sep 2003 08:55:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8GCt5F2016589
	for l3vpn-archive@odin.ietf.org; Tue, 16 Sep 2003 08:55:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zFMH-0004JR-Jh
	for l3vpn-web-archive@optimus.ietf.org; Tue, 16 Sep 2003 08:55:05 -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 IAA10299
	for <l3vpn-web-archive@ietf.org>; Tue, 16 Sep 2003 08:54:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19zFMG-0000uZ-00
	for l3vpn-web-archive@ietf.org; Tue, 16 Sep 2003 08:55:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19zFMF-0000uT-00
	for l3vpn-web-archive@ietf.org; Tue, 16 Sep 2003 08:55:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zFMF-0004IH-5J; Tue, 16 Sep 2003 08:55:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zFLp-0004H9-7l
	for l3vpn@optimus.ietf.org; Tue, 16 Sep 2003 08:54:37 -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 IAA10275
	for <l3vpn@ietf.org>; Tue, 16 Sep 2003 08:54:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19zFLn-0000tp-00
	for l3vpn@ietf.org; Tue, 16 Sep 2003 08:54:35 -0400
Received: from [202.54.124.152] (helo=rediffmail.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19zFLi-0000tC-00
	for l3vpn@ietf.org; Tue, 16 Sep 2003 08:54:35 -0400
Received: (qmail 31589 invoked by uid 510); 16 Sep 2003 12:51:58 -0000
Date: 16 Sep 2003 12:51:58 -0000
Message-ID: <20030916125158.31588.qmail@webmail7.rediffmail.com>
Received: from unknown (203.197.138.199) by rediffmail.com via HTTP; 16 sep 2003 12:51:56 -0000
MIME-Version: 1.0
From: "naresh  paliwal" <paliwalnaresh@rediffmail.com>
Reply-To: "naresh  paliwal" <paliwalnaresh@rediffmail.com>
To: l3vpn@ietf.org
Subject: export RTs
Content-type: text/plain;
	format=flowed
Content-Disposition: inline
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>

What if I add/delete a export RT of a VPN?

As far as i know, Its not discussed in the latest BGP/MPLS VPNs 
draft. The draft discusses about import RT (VPN join and prune) 
only.

"How the change in export RT should be handled" is my problem 
basically.
Readvertsing all the routes belong to the VPN doesnot help, I have 
analysed it very carefully. It has problems while deleting export 
RT.

Can it be possible to handle change of export RT without 
disrupting the bgp session??

Regards
Naresh Paliwal
___________________________________________________
Meet your old school or college friends from
1 Million + database...
Click here to reunite www.batchmates.com/rediff.asp






From exim@www1.ietf.org  Tue Sep 16 14:16:28 2003
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 OAA29958
	for <l3vpn-archive@odin.ietf.org>; Tue, 16 Sep 2003 14:16:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zKMv-0002Tj-9L
	for l3vpn-archive@odin.ietf.org; Tue, 16 Sep 2003 14:16:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8GIG5xN009517
	for l3vpn-archive@odin.ietf.org; Tue, 16 Sep 2003 14:16:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zKMv-0002TI-25
	for l3vpn-web-archive@optimus.ietf.org; Tue, 16 Sep 2003 14:16:05 -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 OAA29943
	for <l3vpn-web-archive@ietf.org>; Tue, 16 Sep 2003 14:15:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19zKMs-00075B-00
	for l3vpn-web-archive@ietf.org; Tue, 16 Sep 2003 14:16:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19zKMs-000758-00
	for l3vpn-web-archive@ietf.org; Tue, 16 Sep 2003 14:16:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zKMs-0002RX-Kb; Tue, 16 Sep 2003 14:16:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zKLw-0002PW-SZ
	for l3vpn@optimus.ietf.org; Tue, 16 Sep 2003 14:15:04 -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 OAA29927
	for <l3vpn@ietf.org>; Tue, 16 Sep 2003 14:14:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19zKLu-00074p-00
	for l3vpn@ietf.org; Tue, 16 Sep 2003 14:15:02 -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 19zKLs-00074M-00
	for l3vpn@ietf.org; Tue, 16 Sep 2003 14:15:02 -0400
Received: from cisco.com (171.71.177.238)
  by sj-iport-2.cisco.com with ESMTP; 16 Sep 2003 11:10:57 -0700
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h8GIESt5023565;
	Tue, 16 Sep 2003 11:14:28 -0700 (PDT)
Received: from cisco.com (komorow.cisco.com [10.61.160.50])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id ALP78443;
	Tue, 16 Sep 2003 11:02:31 -0700 (PDT)
Message-ID: <3F675300.2080800@cisco.com>
Date: Tue, 16 Sep 2003 20:14:24 +0200
From: Robert Raszuk <raszuk@cisco.com>
Reply-To: raszuk@cisco.com
Organization: Signature: http://www.employees.org/~raszuk/sig/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: naresh paliwal <paliwalnaresh@rediffmail.com>
CC: l3vpn@ietf.org
Subject: Re: export RTs
References: <20030916125158.31588.qmail@webmail7.rediffmail.com>
In-Reply-To: <20030916125158.31588.qmail@webmail7.rediffmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Naresh,

Why would it be any different for RTs then for any other deletion and 
readdition of some other attribute or for that matter other std or ext 
community ?

Neither of those above should disrupt your BGP session. As new 
advertisment is an implict withdraw of previosuly advertised NLRIs so I 
don't really see any issues.

 > "How the change in export RT should be handled" is my
 > problem basically.

So to answer this question my take would be that prefixes should be 
readvertised with new RTs.

Thx,
R.

 > naresh paliwal wrote:

> What if I add/delete a export RT of a VPN?
> 
> As far as i know, Its not discussed in the latest BGP/MPLS VPNs draft. 
> The draft discusses about import RT (VPN join and prune) only.
> 
> "How the change in export RT should be handled" is my problem basically.
> Readvertsing all the routes belong to the VPN doesnot help, I have 
> analysed it very carefully. It has problems while deleting export RT.
> 
> Can it be possible to handle change of export RT without disrupting the 
> bgp session??
> 
> Regards
> Naresh Paliwal
> ___________________________________________________
> Meet your old school or college friends from
> 1 Million + database...
> Click here to reunite www.batchmates.com/rediff.asp
> 
> 
> 
> 





From exim@www1.ietf.org  Wed Sep 17 02:13:33 2003
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 CAA13306
	for <l3vpn-archive@odin.ietf.org>; Wed, 17 Sep 2003 02:13:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zVYt-0004Jz-NY
	for l3vpn-archive@odin.ietf.org; Wed, 17 Sep 2003 02:13:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8H6DBTk016610
	for l3vpn-archive@odin.ietf.org; Wed, 17 Sep 2003 02:13:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zVYs-0004Jp-0I
	for l3vpn-web-archive@optimus.ietf.org; Wed, 17 Sep 2003 02:13:10 -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 CAA13243
	for <l3vpn-web-archive@ietf.org>; Wed, 17 Sep 2003 02:13:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19zVYo-0001QR-00
	for l3vpn-web-archive@ietf.org; Wed, 17 Sep 2003 02:13:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19zVYo-0001QN-00
	for l3vpn-web-archive@ietf.org; Wed, 17 Sep 2003 02:13:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zVYk-0004J4-5j; Wed, 17 Sep 2003 02:13:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zVXt-0004CU-A3
	for l3vpn@optimus.ietf.org; Wed, 17 Sep 2003 02:12: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 CAA13123
	for <l3vpn@ietf.org>; Wed, 17 Sep 2003 02:12:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19zVXp-0001Pi-00
	for l3vpn@ietf.org; Wed, 17 Sep 2003 02:12:05 -0400
Received: from [202.54.124.151] (helo=rediffmail.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19zVXo-0001PF-00
	for l3vpn@ietf.org; Wed, 17 Sep 2003 02:12:05 -0400
Received: (qmail 5597 invoked by uid 510); 17 Sep 2003 06:10:44 -0000
Date: 17 Sep 2003 06:10:44 -0000
Message-ID: <20030917061044.5596.qmail@webmail6.rediffmail.com>
Received: from unknown (203.197.138.199) by rediffmail.com via HTTP; 17 sep 2003 06:10:44 -0000
MIME-Version: 1.0
From: "naresh  paliwal" <paliwalnaresh@rediffmail.com>
Reply-To: "naresh  paliwal" <paliwalnaresh@rediffmail.com>
To: "Robert Raszuk" <raszuk@cisco.com>
Cc: l3vpn@ietf.org
Subject: Re: Re: export RTs
Content-type: text/plain;
	format=flowed
Content-Disposition: inline
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>

Robert!!

Advertising with new path attr. doesnot help.
Consider a case, where PE1 advertizes VPN_xy route ROUTE1 with RTs 
X & Y to PE2, which installs the route at PE2, coz it has a VRF 
with import RT Y.
Now if i delete export RT Y at PE1,
it readvertises the route with only X RT,
and its not processed at PE2 as it cant pass the Import route 
target policy of PE2.
And the route remains at PE2's VRF, which shud have been deleted 
as per new export RT policy of PE1.

The solution I see is first send it as an withdrawn route with 
same (OLD) RTs and readvertise with new RTs.

The other solution is resatrting the session..

But both doesnt seems good to me.

any thoughts on this..

-Naresh

On Tue, 16 Sep 2003 Robert Raszuk wrote :
>Naresh,
>
>Why would it be any different for RTs then for any other deletion 
>and readdition of some other attribute or for that matter other 
>std or ext community ?
>
>Neither of those above should disrupt your BGP session. As new 
>advertisment is an implict withdraw of previosuly advertised 
>NLRIs so I don't really see any issues.
>
> > "How the change in export RT should be handled" is my
> > problem basically.
>
>So to answer this question my take would be that prefixes should 
>be readvertised with new RTs.
>
>Thx,
>R.
>
> > naresh paliwal wrote:
>
>>What if I add/delete a export RT of a VPN?
>>
>>As far as i know, Its not discussed in the latest BGP/MPLS VPNs 
>>draft. The draft discusses about import RT (VPN join and prune) 
>>only.
>>
>>"How the change in export RT should be handled" is my problem 
>>basically.
>>Readvertsing all the routes belong to the VPN doesnot help, I 
>>have analysed it very carefully. It has problems while deleting 
>>export RT.
>>
>>Can it be possible to handle change of export RT without 
>>disrupting the bgp session??
>>
>>Regards
>>Naresh Paliwal
>>___________________________________________________
>>Meet your old school or college friends from
>>1 Million + database...
>>Click here to reunite www.batchmates.com/rediff.asp
>>
>>
>>
>>
>

___________________________________________________
Meet your old school or college friends from
1 Million + database...
Click here to reunite www.batchmates.com/rediff.asp






From exim@www1.ietf.org  Wed Sep 17 06:58:50 2003
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 GAA05179
	for <l3vpn-archive@odin.ietf.org>; Wed, 17 Sep 2003 06:58:50 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19za10-0006wT-AK
	for l3vpn-archive@odin.ietf.org; Wed, 17 Sep 2003 06:58:31 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8HAwUaB026679
	for l3vpn-archive@odin.ietf.org; Wed, 17 Sep 2003 06:58:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19za10-0006wE-2y
	for l3vpn-web-archive@optimus.ietf.org; Wed, 17 Sep 2003 06:58: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 GAA05164
	for <l3vpn-web-archive@ietf.org>; Wed, 17 Sep 2003 06:58:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19za0v-00047l-00
	for l3vpn-web-archive@ietf.org; Wed, 17 Sep 2003 06:58:25 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19za0v-00047i-00
	for l3vpn-web-archive@ietf.org; Wed, 17 Sep 2003 06:58:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19za0Y-0006vM-77; Wed, 17 Sep 2003 06:58:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zZzb-0006sh-Py
	for l3vpn@optimus.ietf.org; Wed, 17 Sep 2003 06:57: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 GAA05121
	for <l3vpn@ietf.org>; Wed, 17 Sep 2003 06:56:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19zZzX-00045w-00
	for l3vpn@ietf.org; Wed, 17 Sep 2003 06:56:59 -0400
Received: from [203.197.140.35] (helo=fsnt.future.futsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19zZzW-00043l-00
	for l3vpn@ietf.org; Wed, 17 Sep 2003 06:56:58 -0400
Received: from kailash1.future.futsoft.com (unverified [203.197.140.36]) by 
    fsnt.future.futsoft.com (Content Technologies SMTPRS 4.3.6) with ESMTP id 
    <T64bcac3a40cbc58c23330@fsnt.future.futsoft.com> for <l3vpn@ietf.org>; 
    Wed, 17 Sep 2003 15:55:33 +0530
Received: from sakthivss (sakthivss.future.futsoft.com [10.6.4.130]) by 
    kailash1.future.futsoft.com (8.11.0/8.11.0) with SMTP id h8HAKfj11193 for 
    <l3vpn@ietf.org>; Wed, 17 Sep 2003 15:50:41 +0530
Reply-To: <sakthivss@future.futsoft.com>
From: "Sakthivadivu.S.S" <sakthivss@future.futsoft.com>
To: <l3vpn@ietf.org>
Subject: Route distribution among VRF's in a single PE
Date: Wed, 17 Sep 2003 15:57:33 +0530
Message-ID: <000a01c37d06$4f01ce20$8204060a@future.futsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

   BGP/MPLS VPN draft talks about route distribution among VRF's in a single
PE in section 4.3.6.
   Can you please tell when will this situation occur.?

Thanks,
Sakthi



***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************





From exim@www1.ietf.org  Thu Sep 18 04:41:36 2003
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 EAA02436
	for <l3vpn-archive@odin.ietf.org>; Thu, 18 Sep 2003 04:41:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zuLg-0004HF-Lw
	for l3vpn-archive@odin.ietf.org; Thu, 18 Sep 2003 04:41:13 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8I8fCM2016434
	for l3vpn-archive@odin.ietf.org; Thu, 18 Sep 2003 04:41:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zuLe-0004Gz-AN
	for l3vpn-web-archive@optimus.ietf.org; Thu, 18 Sep 2003 04:41:10 -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 EAA02431
	for <l3vpn-web-archive@ietf.org>; Thu, 18 Sep 2003 04:41:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19zuLb-0002hv-00
	for l3vpn-web-archive@ietf.org; Thu, 18 Sep 2003 04:41:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19zuLb-0002hr-00
	for l3vpn-web-archive@ietf.org; Thu, 18 Sep 2003 04:41:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zuLa-0004GL-Rq; Thu, 18 Sep 2003 04:41:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zuKV-0004Cf-56
	for l3vpn@optimus.ietf.org; Thu, 18 Sep 2003 04:39:59 -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 EAA02377
	for <l3vpn@ietf.org>; Thu, 18 Sep 2003 04:39:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19zuKR-0002gr-00
	for l3vpn@ietf.org; Thu, 18 Sep 2003 04:39:55 -0400
Received: from web41807.mail.yahoo.com ([66.218.93.141])
	by ietf-mx with smtp (Exim 4.12)
	id 19zuKR-0002gh-00
	for l3vpn@ietf.org; Thu, 18 Sep 2003 04:39:55 -0400
Message-ID: <20030918083926.91637.qmail@web41807.mail.yahoo.com>
Received: from [203.200.20.226] by web41807.mail.yahoo.com via HTTP; Thu, 18 Sep 2003 09:39:26 BST
Date: Thu, 18 Sep 2003 09:39:26 +0100 (BST)
From: =?iso-8859-1?q?John=20Smith?= <jsmith4112003@yahoo.co.uk>
Subject: Re: Route distribution among VRF's in a single PE
To: sakthivss@future.futsoft.com
Cc: l3vpn@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Sakthivadivu,

This is applicable when a PE router has two VRFs A and B defined as:

VRF A:
Import RT - 100:100
Export RT - 100:100 200:200

VRF B:
Import RT - 200:200
Export RT - 200:200

Now when VRF A learns a route from its CE peer (either through redistribution/static/etc)
then the route is redistributed to VRF B also.

This happens as the export RTs of VRF A match with that of VRF B's import RT.

Regards,
John
----- Original Message ----- 
From: "Sakthivadivu.S.S" <sakthivss@future.futsoft.com>
To: <l3vpn@ietf.org>
Sent: Wednesday, September 17, 2003 3:57 PM
Subject: Route distribution among VRF's in a single PE


> Hi,
> 
>    BGP/MPLS VPN draft talks about route distribution among VRF's in a single
> PE in section 4.3.6.
>    Can you please tell when will this situation occur.?
> 
> Thanks,
> Sakthi


________________________________________________________________________
Want to chat instantly with your online friends?  Get the FREE Yahoo!
Messenger http://mail.messenger.yahoo.co.uk




From exim@www1.ietf.org  Thu Sep 18 07:24:33 2003
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 HAA07512
	for <l3vpn-archive@odin.ietf.org>; Thu, 18 Sep 2003 07:24:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zwtM-0000xT-5F
	for l3vpn-archive@odin.ietf.org; Thu, 18 Sep 2003 07:24:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8IBO8Yb003684
	for l3vpn-archive@odin.ietf.org; Thu, 18 Sep 2003 07:24:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zwtK-0000xL-9d
	for l3vpn-web-archive@optimus.ietf.org; Thu, 18 Sep 2003 07:24:06 -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 HAB07496
	for <l3vpn-web-archive@ietf.org>; Thu, 18 Sep 2003 07:24:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19zwtJ-0004b9-00
	for l3vpn-web-archive@ietf.org; Thu, 18 Sep 2003 07:24:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19zwtJ-0004b6-00
	for l3vpn-web-archive@ietf.org; Thu, 18 Sep 2003 07:24:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zwtG-0000wp-Q6; Thu, 18 Sep 2003 07: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 19zwsq-0000wR-H7
	for l3vpn@optimus.ietf.org; Thu, 18 Sep 2003 07:23:36 -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 HAA07483
	for <l3vpn@ietf.org>; Thu, 18 Sep 2003 07:23:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19zwsp-0004ax-00
	for l3vpn@ietf.org; Thu, 18 Sep 2003 07:23:35 -0400
Received: from [203.197.140.35] (helo=fsnt.future.futsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19zwso-0004aM-00
	for l3vpn@ietf.org; Thu, 18 Sep 2003 07:23:35 -0400
Received: from kailash1.future.futsoft.com (unverified [203.197.140.36]) by 
    fsnt.future.futsoft.com (Content Technologies SMTPRS 4.3.6) with ESMTP id 
    <T64c2041063cbc58c23338@fsnt.future.futsoft.com>; Thu, 18 Sep 2003 
    16:49:35 +0530
Received: from sakthivss (sakthivss.future.futsoft.com [10.6.4.130]) by 
    kailash1.future.futsoft.com (8.11.0/8.11.0) with SMTP id h8IBEbj01392; 
    Thu, 18 Sep 2003 16:44:37 +0530
Reply-To: <sakthivss@future.futsoft.com>
From: "Sakthivadivu.S.S" <sakthivss@future.futsoft.com>
To: "'John Smith'" <jsmith4112003@yahoo.co.uk>
Cc: <l3vpn@ietf.org>
Subject: RE: Route distribution among VRF's in a single PE
Date: Thu, 18 Sep 2003 16:51:34 +0530
Message-ID: <000701c37dd7$055e1b80$8204060a@future.futsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <20030918083926.91637.qmail@web41807.mail.yahoo.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Hi John,
  Thanks for your inputs.

Consider the following scenario.

  CE1 -----------PE1----------CE2

  CE1 is associated with VRF-A and CE2 is associated with VRF-B.
  Site1 is connected to CE1 and site2 is connected to CE2.
   VRF A:
     Import RT - 100:100
     Export RT - 100:100 200:200

   VRF B:
     Import RT - 200:200
     Export RT - 200:200

  If CE1 learns route 10.10/8, it will be installed in VRF-A. Since export
policy of VRF-A and
  import policy of VRF-B are same, 10.10/8 will be installed in VRF-B
also.My doubt is what will be
  the nexthop for 10.10/8 in VRF-B. How will be the IP packet forwarded from
CE2 to CE1.
  Is it through IP or MPLS.If it through MPLS what will be the bottom label
and top label.
   If it is through IP, what will be the nexthop for 10.10/8.

 Thanks in advance,
  Sakthi

-----Original Message-----
From: l3vpn-admin@ietf.org [mailto:l3vpn-admin@ietf.org]On Behalf Of
John Smith
Sent: Thursday, 18 September 2003 2:09 PM
To: sakthivss@future.futsoft.com
Cc: l3vpn@ietf.org
Subject: Re: Route distribution among VRF's in a single PE


Sakthivadivu,

This is applicable when a PE router has two VRFs A and B defined as:

VRF A:
Import RT - 100:100
Export RT - 100:100 200:200

VRF B:
Import RT - 200:200
Export RT - 200:200

Now when VRF A learns a route from its CE peer (either through
redistribution/static/etc)
then the route is redistributed to VRF B also.

This happens as the export RTs of VRF A match with that of VRF B's import
RT.

Regards,
John
----- Original Message -----
From: "Sakthivadivu.S.S" <sakthivss@future.futsoft.com>
To: <l3vpn@ietf.org>
Sent: Wednesday, September 17, 2003 3:57 PM
Subject: Route distribution among VRF's in a single PE


> Hi,
>
>    BGP/MPLS VPN draft talks about route distribution among VRF's in a
single
> PE in section 4.3.6.
>    Can you please tell when will this situation occur.?
>
> Thanks,
> Sakthi


________________________________________________________________________
Want to chat instantly with your online friends?  Get the FREE Yahoo!
Messenger http://mail.messenger.yahoo.co.uk



***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************





From exim@www1.ietf.org  Fri Sep 19 21:36:33 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00066
	for <l3vpn-archive@odin.ietf.org>; Fri, 19 Sep 2003 21:36:32 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.12.8/8.12.8) with ESMTP id h8K1Vh9L020140
	for <l3vpn-archive@odin.ietf.org>; Fri, 19 Sep 2003 21:36:12 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h88EB4MD018348
	for l3vpn-archive@odin.ietf.org; Mon, 8 Sep 2003 10:11:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19wMjO-0004lh-RV
	for l3vpn-web-archive@optimus.ietf.org; Mon, 08 Sep 2003 10:11:02 -0400
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 KAA22644
	for <l3vpn-web-archive@ietf.org>; Mon, 8 Sep 2003 10:10:54 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19wMip-0004cb-10; Mon, 08 Sep 2003 10:10:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19wMfn-0003XV-Us
	for l3vpn@optimus.ietf.org; Mon, 08 Sep 2003 10:07:19 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21779;
	Mon, 8 Sep 2003 10:07:11 -0400 (EDT)
Message-Id: <200309081407.KAA21779@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: l3vpn@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-l3vpn-l3vpn-auth-00.txt
Date: Mon, 08 Sep 2003 10:07:10 -0400
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Layer 3 Virtual Private Networks Working Group of the IETF.

	Title		: CE-to-CE Member Verification for Layer 3 VPNs
	Author(s)	: R. Bonica et al.
	Filename	: draft-ietf-l3vpn-l3vpn-auth-00.txt
	Pages		: 9
	Date		: 2003-9-8
	
This document describes a CE-based verification mechanism that PPVPN
customers can use to detect security breaches caused by
misconfiguration of the provider network.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-l3vpn-auth-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-l3vpn-l3vpn-auth-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-l3vpn-l3vpn-auth-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-9-8083145.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l3vpn-l3vpn-auth-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-l3vpn-l3vpn-auth-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-9-8083145.I-D@ietf.org>

--OtherAccess--

--NextPart--






From exim@www1.ietf.org  Sat Sep 20 09:52:06 2003
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 JAA03881
	for <l3vpn-archive@odin.ietf.org>; Sat, 20 Sep 2003 09:52:03 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0Q37-0000qX-HC
	for l3vpn-archive@odin.ietf.org; Fri, 19 Sep 2003 14:32:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8JIW9rr003247
	for l3vpn-archive@odin.ietf.org; Fri, 19 Sep 2003 14:32:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0Q37-0000qI-CP
	for l3vpn-web-archive@optimus.ietf.org; Fri, 19 Sep 2003 14:32: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 OAA18868
	for <l3vpn-web-archive@ietf.org>; Fri, 19 Sep 2003 14:31:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A0Q34-000020-00
	for l3vpn-web-archive@ietf.org; Fri, 19 Sep 2003 14:32:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A0Q2z-00001x-00
	for l3vpn-web-archive@ietf.org; Fri, 19 Sep 2003 14:32:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0Q2z-0000o8-Mn; Fri, 19 Sep 2003 14:32:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0Q2G-0000ju-9g
	for l3vpn@optimus.ietf.org; Fri, 19 Sep 2003 14:31:16 -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 OAA18750
	for <l3vpn@ietf.org>; Fri, 19 Sep 2003 14:31:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A0Q28-0007nj-00
	for l3vpn@ietf.org; Fri, 19 Sep 2003 14:31:08 -0400
Received: from pmesmtp01.wcom.com ([199.249.20.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A0Q1y-0007mz-00
	for l3vpn@ietf.org; Fri, 19 Sep 2003 14:30:58 -0400
Received: from dgismtp02.wcomnet.com ([166.38.58.142])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0HLH00E114AEDQ@firewall.wcom.com> for l3vpn@ietf.org; Fri,
 19 Sep 2003 18:20:39 +0000 (GMT)
Received: from dgismtp02.wcomnet.com by dgismtp02.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HLH00A0149MHA@dgismtp02.wcomnet.com> for l3vpn@ietf.org; Fri,
 19 Sep 2003 18:20:39 +0000 (GMT)
Received: from rbonica ([166.32.199.163])
 by dgismtp02.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with SMTP id <0HLH005ZN49RTO@dgismtp02.wcomnet.com> for l3vpn@ietf.org;
 Fri, 19 Sep 2003 18:20:16 +0000 (GMT)
Date: Fri, 19 Sep 2003 14:20:53 -0400
From: Ron Bonica <Ronald.P.Bonica@mci.com>
Subject: RE: draft-ietf-l3vpn-l3vpn-auth-00 and
 draft-behringer-mpls-vpn-auth-02.txt
To: l3vpn@ietf.org
Message-id: <DKEJJCOCJMHEFFNMLKMPMEKDKFAA.Ronald.P.Bonica@mci.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

These two drafts are similar in that the both protect against VPN breaches
caused by misconfiguration of the SP network. They differ in the following
respects:

Draft-ietf-l3vpn-l3vpn-auth assumes that the SP network cannot be trusted to
protect against its own misconfiguration. After all, a well intentioned
misunderstanding on the part of the SP might have caused the SP to
misconfigure the VPN. If such a misunderstanding exists, it might also drive
the SP to misconfigure the authentication mechanism as well.

Since the SP network cannot be trusted to protect against its own
misconfiguration, customer equipment must provide checks and balances. In
order to provide these checks and balances, draft-ietf-l3vpn-l3vpn-auth
passes VPN membership information transparently through the SP network.
Customer devices originate VPN membership information and verify VPN
membership at the remote end. Therefore, additional intelligence is required
on customer equipment.

Draft-behringer-mpls-vpn-auth attempts to achieve the same goal without
changing customer equipment. It does this by associating the authentication
key from the PE-CE routing protocol with VPN membership information. This
association raises three issues:

- Many VPN sites to not use a PE-CE routing protocol

- Customer security policy may require each VPN site to use a different
authentication key on the PE-CE routing protocol. In this case, the SP would
need to configure the mapping of VPN information to authentication keys on
the PE. This mapping, itself, would be subject to misconfiguration by the
SP.

- Customer security policy may require each VPN site to change its PE-CE
authentication key periodically. During the key migration period, the SP
would need to configure the mapping of VPN information to authentication
keys on the PE. This mapping, itself, would be subject to misconfiguration
by the SP.

                                                   Ron
                                                  \individual contributor





===========================================
Ronald P. Bonica       Ph: 703 886 1681
vBNS Engineering       page: 1 888 268 8021
Ashburn, Va.
===========================================
"An eye for an eye only ends up making
the whole world blind."
            -- Gandhi





From exim@www1.ietf.org  Sat Sep 20 09:53:49 2003
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 JAA04339
	for <l3vpn-archive@odin.ietf.org>; Sat, 20 Sep 2003 09:53:48 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0Oxm-0003sG-LL
	for l3vpn-archive@odin.ietf.org; Fri, 19 Sep 2003 13:22:34 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8JHMYfX014886
	for l3vpn-archive@odin.ietf.org; Fri, 19 Sep 2003 13:22:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0Oxm-0003s1-GT
	for l3vpn-web-archive@optimus.ietf.org; Fri, 19 Sep 2003 13:22:34 -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 NAA15813
	for <l3vpn-web-archive@ietf.org>; Fri, 19 Sep 2003 13:22:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A0Oxk-0006dV-00
	for l3vpn-web-archive@ietf.org; Fri, 19 Sep 2003 13:22:32 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A0Olm-0006OZ-00
	for l3vpn-web-archive@ietf.org; Fri, 19 Sep 2003 13:10:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0Np7-0002pd-RT; Fri, 19 Sep 2003 12:09:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0NnU-00021k-FX
	for l3vpn@optimus.ietf.org; Fri, 19 Sep 2003 12:07:52 -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 MAA08038
	for <l3vpn@ietf.org>; Fri, 19 Sep 2003 12:07:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A06Cg-0002V0-00
	for l3vpn@ietf.org; Thu, 18 Sep 2003 17:20:42 -0400
Received: from natint2.juniper.net ([207.17.136.150] helo=merlot.juniper.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A05pA-0007it-00
	for l3vpn@ietf.org; Thu, 18 Sep 2003 16:56:24 -0400
Received: from rcallon-lt.juniper.net (securepptp147.static.jnpr.net [172.24.253.147])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id h8IKtrj72562
	for <l3vpn@ietf.org>; Thu, 18 Sep 2003 13:55:53 -0700 (PDT)
	(envelope-from rcallon@juniper.net)
Message-Id: <4.3.2.20030918165030.02b7ad58@zircon.juniper.net>
X-Sender: rcallon@zircon.juniper.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Thu, 18 Sep 2003 16:54:54 -0400
To: l3vpn@ietf.org
From: Ross Callon <rcallon@juniper.net>
Subject: draft-ietf-l3vpn-l3vpn-auth-00 and
  draft-behringer-mpls-vpn-auth-02.txt
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_22683256==_.ALT"
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>

--=====================_22683256==_.ALT
Content-Type: text/plain; charset="us-ascii"

The L3vpn chairs would like to solicit comments on the two drafts: 
         draft-ietf-l3vpn-l3vpn-auth-00; and 
         draft-behringer-mpls-vpn-auth-02.txt 

The first of these was first discussed March 2002 at the 53rd 
IETF Meeting in Minneapolis, (see 
http://www.ietf.org/proceedings/02mar/index.html) and was 
accepted as a working group document sometime after this. 
  
The second was discussed at the 56th IETF in San Francisco this 
past March (see http://www.ietf.org/proceedings/03mar/index.html). 
  
Both of these drafts address the problem of a SP provisioning 
a VPN site into the wrong VPN. The two drafts differ in approach. 
  
The most obvious question is whether we want to progress both 
drafts separately. In other words, do the approaches differ 
sufficiently in terms of how they work, what they accomplish, 
what mistakes they prevent, and what they require from operators 
(both VPN users and service providers) that it makes sense to 
progress both? 

Comments? 

thanks, Ross (and Rick) 

[PS: As Ron is author of one of the documents, for the purposes 
of this discussion Ron will take on the role of document author, 
and let Rick and I co-chair the discussion.]

--=====================_22683256==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
The L3vpn chairs would like to solicit comments on the two drafts: <br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>draft-ietf-l3vpn-l3vpn-auth-00;
and <br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>draft-behringer-mpls-vpn-auth-02.txt
<br>
<br>
The first of these was first discussed March 2002 at the 53rd <br>
IETF Meeting in Minneapolis, (see <br>
<font color="#0000FF"><u><a href="http://www.ietf.org/proceedings/02mar/index.html" eudora="autourl">http://www.ietf.org/proceedings/02mar/index.html</a></u></font>)
and was <br>
accepted as a working group document sometime after this. <br>
&nbsp;<br>
The second was discussed at the 56th IETF in San Francisco this <br>
past March (see
<a href="http://www.ietf.org/proceedings/03mar/index.html" eudora="autourl"><font color="#0000FF"><u>http://www.ietf.org/proceedings/03mar/index.html</a></u></font>).
<br>
&nbsp;<br>
Both of these drafts address the problem of a SP provisioning <br>
a VPN site into the wrong VPN. The two drafts differ in approach. <br>
&nbsp;<br>
The most obvious question is whether we want to progress both <br>
drafts separately. In other words, do the approaches differ <br>
sufficiently in terms of how they work, what they accomplish, <br>
what mistakes they prevent, and what they require from operators <br>
(both VPN users and service providers) that it makes sense to <br>
progress both? <br>
<br>
Comments? <br>
<br>
thanks, Ross (and Rick) <br>
<br>
[PS: As Ron is author of one of the documents, for the purposes <br>
of this discussion Ron will take on the role of document author, <br>
and let Rick and I co-chair the discussion.]<br>
</html>

--=====================_22683256==_.ALT--





From exim@www1.ietf.org  Sat Sep 20 11:23:04 2003
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 LAA11530
	for <l3vpn-archive@odin.ietf.org>; Sat, 20 Sep 2003 11:23:04 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0jZH-0004NG-7u
	for l3vpn-archive@odin.ietf.org; Sat, 20 Sep 2003 11:22:41 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8KFMd0L016808
	for l3vpn-archive@odin.ietf.org; Sat, 20 Sep 2003 11:22:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0jZC-0004LT-2t
	for l3vpn-web-archive@optimus.ietf.org; Sat, 20 Sep 2003 11:22:39 -0400
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 LAA11334
	for <l3vpn-web-archive@ietf.org>; Sat, 20 Sep 2003 11:22:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0jYf-00043s-Nb; Sat, 20 Sep 2003 11: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 1A0ifo-0006f7-0K
	for l3vpn@optimus.ietf.org; Sat, 20 Sep 2003 10:25: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 RAA21966
	for <l3vpn@ietf.org>; Fri, 19 Sep 2003 17:08:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A0SUa-0001Y2-00
	for l3vpn@ietf.org; Fri, 19 Sep 2003 17:08:40 -0400
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A0SUQ-0001Xe-00
	for l3vpn@ietf.org; Fri, 19 Sep 2003 17:08:30 -0400
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 19 Sep 2003 23:06:21 +0200
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h8JL7cHF015852;
	Fri, 19 Sep 2003 23:07:38 +0200 (MET DST)
Received: from JGUICHARW2K (che-vpn-cluster-1-122.cisco.com [10.86.240.122])
	by cisco.com (8.8.8+Sun/8.8.8) with SMTP id XAA18937;
	Fri, 19 Sep 2003 23:07:37 +0200 (MET DST)
From: "Jim Guichard" <jguichar@cisco.com>
To: "Ron Bonica" <Ronald.P.Bonica@mci.com>, <l3vpn@ietf.org>
Subject: RE: draft-ietf-l3vpn-l3vpn-auth-00 and draft-behringer-mpls-vpn-auth-02.txt
Date: Fri, 19 Sep 2003 17:01:41 -0400
Message-ID: <GBEOKAHINPNKJKNAELODAECLFLAA.jguichar@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200
Importance: Normal
In-Reply-To: <DKEJJCOCJMHEFFNMLKMPMEKDKFAA.Ronald.P.Bonica@mci.com>
Content-Transfer-Encoding: 7bit
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Ron,

the intention of draft-behringer-mpls-vpn-auth is not to stop the SP from
misconfiguration but rather prevent VPN route leakage in the event of such a
misconfiguration. The draft allows an end customer to verify that the
appropriate configuration has been established at the PE-router, as
otherwise the authentication will fail locally and no routes will be
installed/exported to other sites.

Jim

> >-----Original Message-----
> >From: l3vpn-admin@ietf.org [mailto:l3vpn-admin@ietf.org]On Behalf Of Ron
> >Bonica
> >Sent: Friday, September 19, 2003 2:21 PM
> >To: l3vpn@ietf.org
> >Subject: RE: draft-ietf-l3vpn-l3vpn-auth-00 and
> >draft-behringer-mpls-vpn-auth-02.txt
> >
> >
> >Folks,
> >
> >These two drafts are similar in that the both protect against
> >VPN breaches
> >caused by misconfiguration of the SP network. They differ in the
> >following
> >respects:
> >
> >Draft-ietf-l3vpn-l3vpn-auth assumes that the SP network cannot
> >be trusted to
> >protect against its own misconfiguration. After all, a well intentioned
> >misunderstanding on the part of the SP might have caused the SP to
> >misconfigure the VPN. If such a misunderstanding exists, it
> >might also drive
> >the SP to misconfigure the authentication mechanism as well.
> >
> >Since the SP network cannot be trusted to protect against its own
> >misconfiguration, customer equipment must provide checks and balances. In
> >order to provide these checks and balances, draft-ietf-l3vpn-l3vpn-auth
> >passes VPN membership information transparently through the SP network.
> >Customer devices originate VPN membership information and verify VPN
> >membership at the remote end. Therefore, additional intelligence
> >is required
> >on customer equipment.
> >
> >Draft-behringer-mpls-vpn-auth attempts to achieve the same goal without
> >changing customer equipment. It does this by associating the
> >authentication
> >key from the PE-CE routing protocol with VPN membership information. This
> >association raises three issues:
> >
> >- Many VPN sites to not use a PE-CE routing protocol
> >
> >- Customer security policy may require each VPN site to use a different
> >authentication key on the PE-CE routing protocol. In this case,
> >the SP would
> >need to configure the mapping of VPN information to
> >authentication keys on
> >the PE. This mapping, itself, would be subject to misconfiguration by the
> >SP.
> >
> >- Customer security policy may require each VPN site to change its PE-CE
> >authentication key periodically. During the key migration period, the SP
> >would need to configure the mapping of VPN information to authentication
> >keys on the PE. This mapping, itself, would be subject to
> >misconfiguration
> >by the SP.
> >
> >                                                   Ron
> >                                                  \individual contributor
> >
> >
> >
> >
> >
> >===========================================
> >Ronald P. Bonica       Ph: 703 886 1681
> >vBNS Engineering       page: 1 888 268 8021
> >Ashburn, Va.
> >===========================================
> >"An eye for an eye only ends up making
> >the whole world blind."
> >            -- Gandhi
> >





From exim@www1.ietf.org  Sun Sep 21 00:14:35 2003
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 AAA03887
	for <l3vpn-archive@odin.ietf.org>; Sun, 21 Sep 2003 00:14: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 1A0vby-0008JW-0t
	for l3vpn-archive@odin.ietf.org; Sun, 21 Sep 2003 00:14:14 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8L4EDR5031954
	for l3vpn-archive@odin.ietf.org; Sun, 21 Sep 2003 00:14:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0vbx-0008JJ-TM
	for l3vpn-web-archive@optimus.ietf.org; Sun, 21 Sep 2003 00:14:13 -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 AAA03879
	for <l3vpn-web-archive@ietf.org>; Sun, 21 Sep 2003 00:14:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A0vbv-0005eK-00
	for l3vpn-web-archive@ietf.org; Sun, 21 Sep 2003 00:14:11 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A0vbq-0005e6-00
	for l3vpn-web-archive@ietf.org; Sun, 21 Sep 2003 00:14:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0vbl-0008Hx-K3; Sun, 21 Sep 2003 00:14:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0vbE-0008Hj-VV
	for l3vpn@optimus.ietf.org; Sun, 21 Sep 2003 00:13:28 -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 AAA03860
	for <l3vpn@ietf.org>; Sun, 21 Sep 2003 00:13:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A0vb7-0005dr-00
	for l3vpn@ietf.org; Sun, 21 Sep 2003 00:13:21 -0400
Received: from dgesmtp02.wcom.com ([199.249.16.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A0vax-0005dG-00
	for l3vpn@ietf.org; Sun, 21 Sep 2003 00:13:11 -0400
Received: from dgismtp05.wcomnet.com ([166.38.58.88])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0HLJ00JHQPQO4R@firewall.wcom.com> for l3vpn@ietf.org; Sun,
 21 Sep 2003 03:59:12 +0000 (GMT)
Received: from dgismtp05.wcomnet.com by dgismtp05.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HLJ00601PQOY8@dgismtp05.wcomnet.com>; Sun,
 21 Sep 2003 03:59:12 +0000 (GMT)
Received: from rbonica ([166.60.19.195])
 by dgismtp05.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with SMTP id <0HLJ0035EPPM1M@dgismtp05.wcomnet.com>; Sun,
 21 Sep 2003 03:59:12 +0000 (GMT)
Date: Sat, 20 Sep 2003 23:59:48 -0400
From: Ron Bonica <Ronald.P.Bonica@mci.com>
Subject: RE: draft-ietf-l3vpn-l3vpn-auth-00 and
 draft-behringer-mpls-vpn-auth-02.txt
In-reply-to: <GBEOKAHINPNKJKNAELODAECLFLAA.jguichar@cisco.com>
To: Jim Guichard <jguichar@cisco.com>, l3vpn@ietf.org
Message-id: <DKEJJCOCJMHEFFNMLKMPAEMHKFAA.Ronald.P.Bonica@mci.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Jim,

Draft-behringer prevents VPN compromise when caused by many types of
misconfiguration. In this respect, draft-behringer is superior to
draft-ietf-l3vpn. (Draft-ietf-l3vpn doesn't prevent the VPN from being
compromised; it merely provides a mechanism by which the customer can detect
compromise, after it has occurred.)

Draft-behringer, however, cannot prevent VPN compromise when caused by some
types of misconfiguration. Specifically, when the SP misconfigures the VPN
authentication mechanism itself, draft-behringer cannot prevent VPN
compromise. In this case, the customer has a false sense of security, which
is worse than no protection at all.

There are several ways in which the SP might misconfigure the authentication
mechanism. The most obvious is to forget to enable it. Less obvious
opportunities for misconfiguration arise under the following conditions:

- the customer uses a unique key to authenticate the routing protocol on
each PE-CE interface
- the customer changes authentication keys on PE-CE routing protocols
periodically, but does not want to change all keys in one night
- the customer participates in extranets

                                             Ron


> -----Original Message-----
> From: Jim Guichard [mailto:jguichar@cisco.com]
> Sent: Friday, September 19, 2003 5:02 PM
> To: Ron Bonica; l3vpn@ietf.org
> Subject: RE: draft-ietf-l3vpn-l3vpn-auth-00 and
> draft-behringer-mpls-vpn-auth-02.txt
>
>
> Hi Ron,
>
> the intention of draft-behringer-mpls-vpn-auth is not to stop the SP from
> misconfiguration but rather prevent VPN route leakage in the
> event of such a
> misconfiguration. The draft allows an end customer to verify that the
> appropriate configuration has been established at the PE-router, as
> otherwise the authentication will fail locally and no routes will be
> installed/exported to other sites.
>
> Jim
>
> > >-----Original Message-----
> > >From: l3vpn-admin@ietf.org [mailto:l3vpn-admin@ietf.org]On
> Behalf Of Ron
> > >Bonica
> > >Sent: Friday, September 19, 2003 2:21 PM
> > >To: l3vpn@ietf.org
> > >Subject: RE: draft-ietf-l3vpn-l3vpn-auth-00 and
> > >draft-behringer-mpls-vpn-auth-02.txt
> > >
> > >
> > >Folks,
> > >
> > >These two drafts are similar in that the both protect against
> > >VPN breaches
> > >caused by misconfiguration of the SP network. They differ in the
> > >following
> > >respects:
> > >
> > >Draft-ietf-l3vpn-l3vpn-auth assumes that the SP network cannot
> > >be trusted to
> > >protect against its own misconfiguration. After all, a well intentioned
> > >misunderstanding on the part of the SP might have caused the SP to
> > >misconfigure the VPN. If such a misunderstanding exists, it
> > >might also drive
> > >the SP to misconfigure the authentication mechanism as well.
> > >
> > >Since the SP network cannot be trusted to protect against its own
> > >misconfiguration, customer equipment must provide checks and
> balances. In
> > >order to provide these checks and balances, draft-ietf-l3vpn-l3vpn-auth
> > >passes VPN membership information transparently through the SP network.
> > >Customer devices originate VPN membership information and verify VPN
> > >membership at the remote end. Therefore, additional intelligence
> > >is required
> > >on customer equipment.
> > >
> > >Draft-behringer-mpls-vpn-auth attempts to achieve the same goal without
> > >changing customer equipment. It does this by associating the
> > >authentication
> > >key from the PE-CE routing protocol with VPN membership
> information. This
> > >association raises three issues:
> > >
> > >- Many VPN sites to not use a PE-CE routing protocol
> > >
> > >- Customer security policy may require each VPN site to use a different
> > >authentication key on the PE-CE routing protocol. In this case,
> > >the SP would
> > >need to configure the mapping of VPN information to
> > >authentication keys on
> > >the PE. This mapping, itself, would be subject to
> misconfiguration by the
> > >SP.
> > >
> > >- Customer security policy may require each VPN site to change
> its PE-CE
> > >authentication key periodically. During the key migration
> period, the SP
> > >would need to configure the mapping of VPN information to
> authentication
> > >keys on the PE. This mapping, itself, would be subject to
> > >misconfiguration
> > >by the SP.
> > >
> > >                                                   Ron
> > >                                                  \individual
> contributor
> > >
> > >
> > >
> > >
> > >
> > >===========================================
> > >Ronald P. Bonica       Ph: 703 886 1681
> > >vBNS Engineering       page: 1 888 268 8021
> > >Ashburn, Va.
> > >===========================================
> > >"An eye for an eye only ends up making
> > >the whole world blind."
> > >            -- Gandhi
> > >
>





From exim@www1.ietf.org  Sun Sep 21 08:22:32 2003
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 IAA24348
	for <l3vpn-archive@odin.ietf.org>; Sun, 21 Sep 2003 08:22:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A13E9-0003kN-37
	for l3vpn-archive@odin.ietf.org; Sun, 21 Sep 2003 08:22:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8LCM9IH014400
	for l3vpn-archive@odin.ietf.org; Sun, 21 Sep 2003 08:22:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A13E8-0003kB-US
	for l3vpn-web-archive@optimus.ietf.org; Sun, 21 Sep 2003 08:22:08 -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 IAA24338
	for <l3vpn-web-archive@ietf.org>; Sun, 21 Sep 2003 08:22:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A13E7-0001zD-00
	for l3vpn-web-archive@ietf.org; Sun, 21 Sep 2003 08:22:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A13E2-0001zA-00
	for l3vpn-web-archive@ietf.org; Sun, 21 Sep 2003 08:22:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A13E1-0003jX-8q; Sun, 21 Sep 2003 08: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 1A13DG-0003is-Bp
	for l3vpn@optimus.ietf.org; Sun, 21 Sep 2003 08:21:17 -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 IAA24292
	for <l3vpn@ietf.org>; Sun, 21 Sep 2003 08:21:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A13DF-0001yJ-00
	for l3vpn@ietf.org; Sun, 21 Sep 2003 08:21:13 -0400
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A13D4-0001wy-00
	for l3vpn@ietf.org; Sun, 21 Sep 2003 08:21:02 -0400
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 21 Sep 2003 14:18:27 +0200
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h8LCJjf8027102;
	Sun, 21 Sep 2003 14:19:45 +0200 (MET DST)
Received: from JGUICHARW2K (che-vpn-cluster-1-57.cisco.com [10.86.240.57])
	by cisco.com (8.8.8+Sun/8.8.8) with SMTP id OAA24237;
	Sun, 21 Sep 2003 14:19:45 +0200 (MET DST)
From: "Jim Guichard" <jguichar@cisco.com>
To: "Ron Bonica" <Ronald.P.Bonica@mci.com>, <l3vpn@ietf.org>
Subject: RE: draft-ietf-l3vpn-l3vpn-auth-00 and draft-behringer-mpls-vpn-auth-02.txt
Date: Sun, 21 Sep 2003 08:13:47 -0400
Message-ID: <GBEOKAHINPNKJKNAELODOEDPFLAA.jguichar@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <DKEJJCOCJMHEFFNMLKMPAEMHKFAA.Ronald.P.Bonica@mci.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Ron,

> >-----Original Message-----
> >From: Ron Bonica [mailto:Ronald.P.Bonica@mci.com]
> >Sent: Sunday, September 21, 2003 12:00 AM
> >To: Jim Guichard; l3vpn@ietf.org
> >Subject: RE: draft-ietf-l3vpn-l3vpn-auth-00 and
> >draft-behringer-mpls-vpn-auth-02.txt
> >
> >
> >Jim,
> >
> >Draft-behringer prevents VPN compromise when caused by many types of
> >misconfiguration. In this respect, draft-behringer is superior to
> >draft-ietf-l3vpn. (Draft-ietf-l3vpn doesn't prevent the VPN from being
> >compromised; it merely provides a mechanism by which the
> >customer can detect
> >compromise, after it has occurred.)
> >
> >Draft-behringer, however, cannot prevent VPN compromise when
> >caused by some
> >types of misconfiguration. Specifically, when the SP
> >misconfigures the VPN
> >authentication mechanism itself, draft-behringer cannot prevent VPN
> >compromise. In this case, the customer has a false sense of
> >security, which
> >is worse than no protection at all.

If the SP misconfigures the authentication mechanism then the PE-router will
reject routing updates from the CE-router as the MD5 key will not match and
therefore local authentication will fail. Likewise, if a remote PE-router is
misconfigured then a PE-router that receives an update from this router will
fail authentication because of the key mismatch.

Jim

> >
> >There are several ways in which the SP might misconfigure the
> >authentication
> >mechanism. The most obvious is to forget to enable it. Less obvious
> >opportunities for misconfiguration arise under the following conditions:
> >
> >- the customer uses a unique key to authenticate the routing protocol on
> >each PE-CE interface
> >- the customer changes authentication keys on PE-CE routing protocols
> >periodically, but does not want to change all keys in one night
> >- the customer participates in extranets
> >
> >                                             Ron
> >
> >
> >> -----Original Message-----
> >> From: Jim Guichard [mailto:jguichar@cisco.com]
> >> Sent: Friday, September 19, 2003 5:02 PM
> >> To: Ron Bonica; l3vpn@ietf.org
> >> Subject: RE: draft-ietf-l3vpn-l3vpn-auth-00 and
> >> draft-behringer-mpls-vpn-auth-02.txt
> >>
> >>
> >> Hi Ron,
> >>
> >> the intention of draft-behringer-mpls-vpn-auth is not to stop
> >the SP from
> >> misconfiguration but rather prevent VPN route leakage in the
> >> event of such a
> >> misconfiguration. The draft allows an end customer to verify that the
> >> appropriate configuration has been established at the PE-router, as
> >> otherwise the authentication will fail locally and no routes will be
> >> installed/exported to other sites.
> >>
> >> Jim
> >>
> >> > >-----Original Message-----
> >> > >From: l3vpn-admin@ietf.org [mailto:l3vpn-admin@ietf.org]On
> >> Behalf Of Ron
> >> > >Bonica
> >> > >Sent: Friday, September 19, 2003 2:21 PM
> >> > >To: l3vpn@ietf.org
> >> > >Subject: RE: draft-ietf-l3vpn-l3vpn-auth-00 and
> >> > >draft-behringer-mpls-vpn-auth-02.txt
> >> > >
> >> > >
> >> > >Folks,
> >> > >
> >> > >These two drafts are similar in that the both protect against
> >> > >VPN breaches
> >> > >caused by misconfiguration of the SP network. They differ in the
> >> > >following
> >> > >respects:
> >> > >
> >> > >Draft-ietf-l3vpn-l3vpn-auth assumes that the SP network cannot
> >> > >be trusted to
> >> > >protect against its own misconfiguration. After all, a well
> >intentioned
> >> > >misunderstanding on the part of the SP might have caused the SP to
> >> > >misconfigure the VPN. If such a misunderstanding exists, it
> >> > >might also drive
> >> > >the SP to misconfigure the authentication mechanism as well.
> >> > >
> >> > >Since the SP network cannot be trusted to protect against its own
> >> > >misconfiguration, customer equipment must provide checks and
> >> balances. In
> >> > >order to provide these checks and balances,
> >draft-ietf-l3vpn-l3vpn-auth
> >> > >passes VPN membership information transparently through the
> >SP network.
> >> > >Customer devices originate VPN membership information and verify VPN
> >> > >membership at the remote end. Therefore, additional intelligence
> >> > >is required
> >> > >on customer equipment.
> >> > >
> >> > >Draft-behringer-mpls-vpn-auth attempts to achieve the same
> >goal without
> >> > >changing customer equipment. It does this by associating the
> >> > >authentication
> >> > >key from the PE-CE routing protocol with VPN membership
> >> information. This
> >> > >association raises three issues:
> >> > >
> >> > >- Many VPN sites to not use a PE-CE routing protocol
> >> > >
> >> > >- Customer security policy may require each VPN site to use
> >a different
> >> > >authentication key on the PE-CE routing protocol. In this case,
> >> > >the SP would
> >> > >need to configure the mapping of VPN information to
> >> > >authentication keys on
> >> > >the PE. This mapping, itself, would be subject to
> >> misconfiguration by the
> >> > >SP.
> >> > >
> >> > >- Customer security policy may require each VPN site to change
> >> its PE-CE
> >> > >authentication key periodically. During the key migration
> >> period, the SP
> >> > >would need to configure the mapping of VPN information to
> >> authentication
> >> > >keys on the PE. This mapping, itself, would be subject to
> >> > >misconfiguration
> >> > >by the SP.
> >> > >
> >> > >                                                   Ron
> >> > >                                                  \individual
> >> contributor
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >===========================================
> >> > >Ronald P. Bonica       Ph: 703 886 1681
> >> > >vBNS Engineering       page: 1 888 268 8021
> >> > >Ashburn, Va.
> >> > >===========================================
> >> > >"An eye for an eye only ends up making
> >> > >the whole world blind."
> >> > >            -- Gandhi
> >> > >
> >>





From exim@www1.ietf.org  Sun Sep 21 12:22:31 2003
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 MAA00898
	for <l3vpn-archive@odin.ietf.org>; Sun, 21 Sep 2003 12:22:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A16yP-0007rn-9c
	for l3vpn-archive@odin.ietf.org; Sun, 21 Sep 2003 12:22:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8LGM9A1030240
	for l3vpn-archive@odin.ietf.org; Sun, 21 Sep 2003 12:22:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A16yP-0007rf-3p
	for l3vpn-web-archive@optimus.ietf.org; Sun, 21 Sep 2003 12:22: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 MAA00874
	for <l3vpn-web-archive@ietf.org>; Sun, 21 Sep 2003 12:22:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A16yN-0004KW-00
	for l3vpn-web-archive@ietf.org; Sun, 21 Sep 2003 12:22:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A16yI-0004KT-00
	for l3vpn-web-archive@ietf.org; Sun, 21 Sep 2003 12:22:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A16yH-0007r7-4l; Sun, 21 Sep 2003 12: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 1A16y4-0007qh-TE
	for l3vpn@optimus.ietf.org; Sun, 21 Sep 2003 12:21:48 -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 MAA00853
	for <l3vpn@ietf.org>; Sun, 21 Sep 2003 12:21:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A16xy-0004Jx-00
	for l3vpn@ietf.org; Sun, 21 Sep 2003 12:21:42 -0400
Received: from dgesmtp02.wcom.com ([199.249.16.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A16xo-0004JS-00
	for l3vpn@ietf.org; Sun, 21 Sep 2003 12:21:32 -0400
Received: from pmismtp02.wcomnet.com ([166.38.62.37])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0HLK00JDKNRTIF@firewall.wcom.com> for l3vpn@ietf.org; Sun,
 21 Sep 2003 16:14:17 +0000 (GMT)
Received: from pmismtp02.wcomnet.com by pmismtp02.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HLK00901NRTZO@pmismtp02.wcomnet.com>; Sun,
 21 Sep 2003 16:14:17 +0000 (GMT)
Received: from rbonica ([166.50.112.209])
 by pmismtp02.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with SMTP id <0HLK0077INRN0G@pmismtp02.wcomnet.com>; Sun,
 21 Sep 2003 16:14:16 +0000 (GMT)
Date: Sun, 21 Sep 2003 12:14:50 -0400
From: Ron Bonica <Ronald.P.Bonica@mci.com>
Subject: RE: draft-ietf-l3vpn-l3vpn-auth-00 and
 draft-behringer-mpls-vpn-auth-02.txt
In-reply-to: <GBEOKAHINPNKJKNAELODOEDPFLAA.jguichar@cisco.com>
To: Jim Guichard <jguichar@cisco.com>, l3vpn@ietf.org
Message-id: <DKEJJCOCJMHEFFNMLKMPKENHKFAA.Ronald.P.Bonica@mci.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>
> If the SP misconfigures the authentication mechanism then the
> PE-router will
> reject routing updates from the CE-router as the MD5 key will not
> match and
> therefore local authentication will fail. Likewise, if a remote
> PE-router is
> misconfigured then a PE-router that receives an update from this
> router will
> fail authentication because of the key mismatch.
>
> Jim
>
>

Hi Jim,

Is this always the case? Consider the following scenario:

Draft-behringer has been working nicely in a network for months. While
working another issue, the SP deactivates draft-behringer, network-wide. The
SP is unaware of this misconfiguration and the network runs unprotected for
weeks. The customer is also unaware that the network is running unprotected.
During this period, more misconfigurations follow.

This is the worst example of authentication mechanism misconfiguration that
I can think of. There are more subtle misconfigurations that can come into
play when the customer uses a different authentication key on each PE-CE
interface.

                                   Ron









From exim@www1.ietf.org  Sun Sep 21 16:41:01 2003
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 QAA07566
	for <l3vpn-archive@odin.ietf.org>; Sun, 21 Sep 2003 16:41:01 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1B0Y-0001pV-US
	for l3vpn-archive@odin.ietf.org; Sun, 21 Sep 2003 16:40:39 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8LKecJn007027
	for l3vpn-archive@odin.ietf.org; Sun, 21 Sep 2003 16:40:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1B0Y-0001pG-2H
	for l3vpn-web-archive@optimus.ietf.org; Sun, 21 Sep 2003 16:40:38 -0400
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 QAA07558
	for <l3vpn-web-archive@ietf.org>; Sun, 21 Sep 2003 16:40:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1Azy-0001mU-Ut; Sun, 21 Sep 2003 16: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 1A1AzL-0001jF-B2
	for l3vpn@optimus.ietf.org; Sun, 21 Sep 2003 16:39:23 -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 QAA07520
	for <l3vpn@ietf.org>; Sun, 21 Sep 2003 16:39:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1AzC-0006SC-00
	for l3vpn@ietf.org; Sun, 21 Sep 2003 16:39:14 -0400
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1Ayy-0006S8-00
	for l3vpn@ietf.org; Sun, 21 Sep 2003 16:39:00 -0400
Received: from [63.202.92.152] (adsl-63-202-92-152.dsl.snfc21.pacbell.net [63.202.92.152])
	(authenticated bits=0)
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h8LKcpKQ089818
	for <l3vpn@ietf.org>; Sun, 21 Sep 2003 13:38:51 -0700 (PDT)
	(envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
X-Sender: phoffvpnc@mail.vpnc.org
Message-Id: <p0600203bbb93bbe82884@[63.202.92.152]>
In-Reply-To: <DKEJJCOCJMHEFFNMLKMPAEMHKFAA.Ronald.P.Bonica@mci.com>
References: <DKEJJCOCJMHEFFNMLKMPAEMHKFAA.Ronald.P.Bonica@mci.com>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Sun, 21 Sep 2003 13:41:00 -0700
To: l3vpn@ietf.org
From: Paul Hoffman / VPNC <paul.hoffman@vpnc.org>
Subject: RE: draft-ietf-l3vpn-l3vpn-auth-00 and 
 draft-behringer-mpls-vpn-auth-02.txt
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>

At 11:59 PM -0400 9/20/03, Ron Bonica wrote:
>Draft-behringer, however, cannot prevent VPN compromise when caused by some
>types of misconfiguration. Specifically, when the SP misconfigures the VPN
>authentication mechanism itself, draft-behringer cannot prevent VPN
>compromise. In this case, the customer has a false sense of security, which
>is worse than no protection at all.

That is a strong assertion, one that I have made in the past in other 
security contexts. I now believe that it is wrong in any protocol 
that, when properly implemented, gives actual security. 
Draft-behringer gives some real security, and determining if it is 
implemented is easy for many of the cases.

There are almost no security protocols that cannot be misconfigured. 
The "false sense of security" argument cannot be held against them.

--Paul Hoffman, Director
--VPN Consortium




From exim@www1.ietf.org  Mon Sep 22 14:21:35 2003
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 OAA28681
	for <l3vpn-archive@odin.ietf.org>; Mon, 22 Sep 2003 14:21: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 1A1VJB-0003Pl-Qd
	for l3vpn-archive@odin.ietf.org; Mon, 22 Sep 2003 14:21:13 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8MILDsH013123
	for l3vpn-archive@odin.ietf.org; Mon, 22 Sep 2003 14:21:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1VJB-0003Pa-Ma
	for l3vpn-web-archive@optimus.ietf.org; Mon, 22 Sep 2003 14:21:13 -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 OAA28659
	for <l3vpn-web-archive@ietf.org>; Mon, 22 Sep 2003 14:21:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1VJ9-0003sB-00
	for l3vpn-web-archive@ietf.org; Mon, 22 Sep 2003 14:21:11 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1VJ3-0003rk-00
	for l3vpn-web-archive@ietf.org; Mon, 22 Sep 2003 14:21:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1VIy-0003NH-Pz; Mon, 22 Sep 2003 14:21:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1VIT-0003Jp-T3
	for l3vpn@optimus.ietf.org; Mon, 22 Sep 2003 14:20:34 -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 OAA28625
	for <l3vpn@ietf.org>; Mon, 22 Sep 2003 14:20:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1VIR-0003o6-00
	for l3vpn@ietf.org; Mon, 22 Sep 2003 14:20:27 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1VIF-0003hL-00
	for l3vpn@ietf.org; Mon, 22 Sep 2003 14:20:15 -0400
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h8MIIq01019066;
	Mon, 22 Sep 2003 14:18:52 -0400 (EDT)
Message-Id: <200309221818.h8MIIq01019066@rtp-core-1.cisco.com>
To: Ross Callon <rcallon@juniper.net>
cc: l3vpn@ietf.org
Subject: Re: draft-ietf-l3vpn-l3vpn-auth-00 and draft-behringer-mpls-vpn-auth-02.txt 
In-reply-to: Your message of Thu, 18 Sep 2003 16:54:54 -0400.
             <4.3.2.20030918165030.02b7ad58@zircon.juniper.net> 
Reply-To: erosen@cisco.com
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
 (=?ISO-8859-4?Q?Unebigory=F2mae?=) 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: Mon, 22 Sep 2003 14:18:51 -0400
From: Eric Rosen <erosen@cisco.com>
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>


Ross> The most obvious question is whether we want to progress both 
Ross> drafts separately. In other words, do the approaches differ 
Ross> sufficiently in terms of how they work, what they accomplish, 
Ross> what mistakes they prevent, and what they require from operators 
Ross> (both VPN users and service providers) that it makes sense to 
Ross> progress both? 

I don't think it  makes any sense to progress both drafts.   In fact, as far
as I can tell they are virtually identical from a functional perspective. 

Both of them  seem to protect only against  accidental SP misconfigurations,
neither seems to offer significant protection against active attacks.  

Both work by attaching a new  attribute to the VPN-IP routes.  Actually, one
uses  a  particular  Extended   Community  attribute,  one  proposes  a  new
attribute, but that's hardly a significant difference. 

In both drafts,  the basic method of detecting  misconfiguration is to pass,
with each VPN-IP route, some item (or a function of some item) that is known
to the CE routers.

In draft-ietf-l3vpn-l3vpn-auth,  the item that  is passed around is  a token
that is obtained from a CE router.  This item is passed to other CE routers,
who then verify it.   The token is passed "in the clear";  it is in effect a
cleartext password for the VPN.

In  draft-behringer-mpls-vpn-auth, the  item  that is  passed  around is  an
ordered pair consisting of (a) a random number that has been assigned to the
source VRF of  the route, and (b)  the MD5 hash of that  number, as computed
with the MD5  secret key used in authenticating  the PE-CE routing protocol.
It  seems to me  that this  ordered pair  is pretty  much equivalent  to the
"token" of the  other draft.  That is, it is in  effect a cleartext password
for the VPN.  

In  draft-ietf-l3vpn-l3vpn-auth,  the  cleartext  password that  is  carried
across  the backbone  is  explicitly provided  by  a CE,  and is  explicitly
verified by the other CEs. 

In  draft-behringer-mpls-vpn-auth, the  cleartext password  that  is carried
across the backbone is computed from the secret key known to the CEs and PEs
of a particular VPN (with the assumption  that the secret key is the same at
both ends).

So I think the only real differences are: 

- The token  method requires the CEs to have new  procedures for sending and
  receiving the token. 

- The  token method does  not require  the CEs to  all send the  same token,
  though it does require each CE to be able to verify all of the tokens used
  in its VPN.

- The  MD5 method  doesn't require the  CEs to  have any new  procedures for
  token handling, as long as the CE is already using MD5 to authenticate its
  PE-CE routing exchange.  This is an advantage, but one which disappears if
  there is no MD5-authenticated PE-CE routing exchange. 

- The  MD5 method seems to require  that all CE-PE routing  adjacencies in a
  VPN be keyed the same.  This seems like potentially a large difficulty. 

If seems to  me that even if the  WG wanted to allow both  methods, a single
draft should be  produced, with the PE-PE mechanisms being  the same in both
cases.  I tend to prefer the token method, but this merits more discussion. 









From exim@www1.ietf.org  Wed Sep 24 07:11:28 2003
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 HAA06965
	for <l3vpn-archive@odin.ietf.org>; Wed, 24 Sep 2003 07:11:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A27Y0-00079x-6P
	for l3vpn-archive@odin.ietf.org; Wed, 24 Sep 2003 07:11:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8OBB4Rk027515
	for l3vpn-archive@odin.ietf.org; Wed, 24 Sep 2003 07:11:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A27Y0-00079i-1W
	for l3vpn-web-archive@optimus.ietf.org; Wed, 24 Sep 2003 07:11:04 -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 HAA06948
	for <l3vpn-web-archive@ietf.org>; Wed, 24 Sep 2003 07:10:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A27Xv-0001rM-00
	for l3vpn-web-archive@ietf.org; Wed, 24 Sep 2003 07:10:59 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A27Xv-0001rI-00
	for l3vpn-web-archive@ietf.org; Wed, 24 Sep 2003 07:10:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A27Xx-000799-KK; Wed, 24 Sep 2003 07:11:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A27XW-0006yV-Lv
	for l3vpn@optimus.ietf.org; Wed, 24 Sep 2003 07:10:34 -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 HAA06916
	for <l3vpn@ietf.org>; Wed, 24 Sep 2003 07:10:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A27XS-0001qy-00
	for l3vpn@ietf.org; Wed, 24 Sep 2003 07:10:30 -0400
Received: from web41813.mail.yahoo.com ([66.218.93.147])
	by ietf-mx with smtp (Exim 4.12)
	id 1A27XR-0001qj-00
	for l3vpn@ietf.org; Wed, 24 Sep 2003 07:10:29 -0400
Message-ID: <20030924110956.60933.qmail@web41813.mail.yahoo.com>
Received: from [203.200.20.226] by web41813.mail.yahoo.com via HTTP; Wed, 24 Sep 2003 12:09:56 BST
Date: Wed, 24 Sep 2003 12:09:56 +0100 (BST)
From: =?iso-8859-1?q?John=20Smith?= <jsmith4112003@yahoo.co.uk>
Subject: Re: Route distribution among VRF's in a single PE
To: sakthivss@future.futsoft.com
Cc: l3vpn@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Sakthivadivu,

>   If CE1 learns route 10.10/8, it will be installed in VRF-A. Since export
> policy of VRF-A and
>   import policy of VRF-B are same, 10.10/8 will be installed in VRF-B

Very True.

> also.My doubt is what will be
>   the nexthop for 10.10/8 in VRF-B. How will be the IP packet forwarded from
> CE2 to CE1.
>   Is it through IP or MPLS.If it through MPLS what will be the bottom label
> and top label.

It will be through IP and not MPLS.

>    If it is through IP, what will be the nexthop for 10.10/8.

The next hop will be the same as that of the one which is in VRF A. The interface index
used is the same which is required for reaching this preix. YOu need to configure the FTN
for VRF B to use IP to deliver the packets.

NOTE: Redistribution across the VRFs only happens for the routes learnt locally by a CE
router. We do not redistribute routes learnt from a remote PE peer to other VRFs even if
the RTs overlap.

John



________________________________________________________________________
Want to chat instantly with your online friends?  Get the FREE Yahoo!
Messenger http://mail.messenger.yahoo.co.uk




From exim@www1.ietf.org  Wed Sep 24 07:57:27 2003
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 HAA09035
	for <l3vpn-archive@odin.ietf.org>; Wed, 24 Sep 2003 07:57: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 1A28GV-00047S-F0
	for l3vpn-archive@odin.ietf.org; Wed, 24 Sep 2003 07:57:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8OBv3X7015828
	for l3vpn-archive@odin.ietf.org; Wed, 24 Sep 2003 07:57:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A28GV-00046t-A8
	for l3vpn-web-archive@optimus.ietf.org; Wed, 24 Sep 2003 07:57: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 HAA09003
	for <l3vpn-web-archive@ietf.org>; Wed, 24 Sep 2003 07:56:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A28GU-0002YM-00
	for l3vpn-web-archive@ietf.org; Wed, 24 Sep 2003 07:57:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A28GU-0002YI-00
	for l3vpn-web-archive@ietf.org; Wed, 24 Sep 2003 07:57:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A28GT-00045S-Im; Wed, 24 Sep 2003 07:57:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A28Fk-00041K-Dd
	for l3vpn@optimus.ietf.org; Wed, 24 Sep 2003 07:56:16 -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 HAA08951
	for <l3vpn@ietf.org>; Wed, 24 Sep 2003 07:56:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A28Fj-0002XN-00
	for l3vpn@ietf.org; Wed, 24 Sep 2003 07:56:15 -0400
Received: from web41811.mail.yahoo.com ([66.218.93.145])
	by ietf-mx with smtp (Exim 4.12)
	id 1A28Fi-0002WK-00
	for l3vpn@ietf.org; Wed, 24 Sep 2003 07:56:14 -0400
Message-ID: <20030924115535.88208.qmail@web41811.mail.yahoo.com>
Received: from [203.200.20.226] by web41811.mail.yahoo.com via HTTP; Wed, 24 Sep 2003 12:55:35 BST
Date: Wed, 24 Sep 2003 12:55:35 +0100 (BST)
From: =?iso-8859-1?q?John=20Smith?= <jsmith4112003@yahoo.co.uk>
Subject: PE Route Reflectors
To: l3vpn@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi,

I want to setup RRs in my SP topology. This RR will be catering 3 VRFs, say A, B and C -
each with its own RD and RTs.

I need to only configure the VRFs on this RR. I dont need to bind any interfaces to any
of the VRFs that i define .. Right? This is assuming that i have no CE routers attached
on this router. I want to use the RR for the sole purpose of reducing my IBBP mesh.

Moreover, would this RR advertise the same BGP Label to its client PE router , the one
which it recieves from its other client PE router? I think Yes. The label is left
untouched in RRs.

Regards,
John

________________________________________________________________________
Want to chat instantly with your online friends?  Get the FREE Yahoo!
Messenger http://mail.messenger.yahoo.co.uk




From exim@www1.ietf.org  Wed Sep 24 08:42:26 2003
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 IAA11218
	for <l3vpn-archive@odin.ietf.org>; Wed, 24 Sep 2003 08:42:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A28y2-0007x4-Ry
	for l3vpn-archive@odin.ietf.org; Wed, 24 Sep 2003 08:42:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8OCg2Rk030565
	for l3vpn-archive@odin.ietf.org; Wed, 24 Sep 2003 08:42:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A28y2-0007wu-Mf
	for l3vpn-web-archive@optimus.ietf.org; Wed, 24 Sep 2003 08:42: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 IAA11192
	for <l3vpn-web-archive@ietf.org>; Wed, 24 Sep 2003 08:41:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A28y1-0003KL-00
	for l3vpn-web-archive@ietf.org; Wed, 24 Sep 2003 08:42:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A28y1-0003KI-00
	for l3vpn-web-archive@ietf.org; Wed, 24 Sep 2003 08:42:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A28y0-0007wG-HK; Wed, 24 Sep 2003 08:42:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A28xt-0007vx-UC
	for l3vpn@optimus.ietf.org; Wed, 24 Sep 2003 08:41:53 -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 IAA11182
	for <l3vpn@ietf.org>; Wed, 24 Sep 2003 08:41:46 -0400 (EDT)
From: jeremy.de_clercq@alcatel.be
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A28xs-0003K0-00
	for l3vpn@ietf.org; Wed, 24 Sep 2003 08:41:52 -0400
Received: from alc240.alcatel.be ([195.207.101.240] helo=relay1.alcatel.be)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A28xr-0003Jj-00
	for l3vpn@ietf.org; Wed, 24 Sep 2003 08:41:52 -0400
Received: from bemail04.net.alcatel.be (bemail04.net.alcatel.be [138.203.144.6])
	by relay1.alcatel.be (8.12.10/8.12.9) with ESMTP id h8OCfKhj020672;
	Wed, 24 Sep 2003 14:41:20 +0200 (MEST)
Received: from alcatel.be ([138.203.67.106])
          by bemail04.net.alcatel.be (Lotus Domino Release 5.0.11)
          with ESMTP id 2003092414411851:4916 ;
          Wed, 24 Sep 2003 14:41:18 +0200 
Message-ID: <3F7190ED.BE22C8BE@alcatel.be>
Date: Wed, 24 Sep 2003 14:41:17 +0200
Organization: Alcatel
X-Mailer: Mozilla 4.72 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: John Smith <jsmith4112003@yahoo.co.uk>
CC: l3vpn@ietf.org
Subject: Re: PE Route Reflectors
References: <20030924115535.88208.qmail@web41811.mail.yahoo.com>
X-MIMETrack: Itemize by SMTP Server on BEMAIL04/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 09/24/2003 14:41:18,
	Serialize by Router on BEMAIL04/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 09/24/2003 14:41:19,
	Serialize complete at 09/24/2003 14:41:19
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
Content-Transfer-Encoding: 7bit
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi John,

> I want to setup RRs in my SP topology. This RR will be catering 3 VRFs, say A, B and C -
> each with its own RD and RTs.
> 
> I need to only configure the VRFs on this RR. I dont need to bind any interfaces to any
> of the VRFs that i define .. Right? This is assuming that i have no CE routers attached
> on this router. I want to use the RR for the sole purpose of reducing my IBBP mesh.

why would you configure VRFs on the RR if you don't bind interfaces to
them ? Your RR will only need to deal with VPN routes (RD+IPv4), right ?
 
> Moreover, would this RR advertise the same BGP Label to its client PE router , the one
> which it recieves from its other client PE router? I think Yes. The label is left
> untouched in RRs.

Correct.




From exim@www1.ietf.org  Wed Sep 24 18:38:41 2003
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 SAA13316
	for <l3vpn-archive@odin.ietf.org>; Wed, 24 Sep 2003 18:38:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2IH6-0007yL-Rt
	for l3vpn-archive@odin.ietf.org; Wed, 24 Sep 2003 18:38:21 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8OMcKqJ030639
	for l3vpn-archive@odin.ietf.org; Wed, 24 Sep 2003 18:38:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2IH6-0007w6-Gj
	for l3vpn-web-archive@optimus.ietf.org; Wed, 24 Sep 2003 18:38:20 -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 SAA13292
	for <l3vpn-web-archive@ietf.org>; Wed, 24 Sep 2003 18:38:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2IH3-00044i-00
	for l3vpn-web-archive@ietf.org; Wed, 24 Sep 2003 18:38:17 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2IH3-00044f-00
	for l3vpn-web-archive@ietf.org; Wed, 24 Sep 2003 18:38:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2IGn-0007qH-Fw; Wed, 24 Sep 2003 18:38:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2IG6-0007fq-Jp
	for l3vpn@optimus.ietf.org; Wed, 24 Sep 2003 18:37:18 -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 SAA13260
	for <l3vpn@ietf.org>; Wed, 24 Sep 2003 18:37:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2IG3-00043a-00
	for l3vpn@ietf.org; Wed, 24 Sep 2003 18:37:15 -0400
Received: from web20512.mail.yahoo.com ([216.136.175.20])
	by ietf-mx with smtp (Exim 4.12)
	id 1A2IG2-00043X-00
	for l3vpn@ietf.org; Wed, 24 Sep 2003 18:37:15 -0400
Message-ID: <20030924223715.45185.qmail@web20512.mail.yahoo.com>
Received: from [64.221.212.131] by web20512.mail.yahoo.com via HTTP; Wed, 24 Sep 2003 15:37:15 PDT
Date: Wed, 24 Sep 2003 15:37:15 -0700 (PDT)
From: rahul v <rahulgothem@yahoo.com>
Subject: ospf router-id extended community
To: l3vpn@ietf.org
In-Reply-To: <20030924222200.26166.5582.Mailman@www1.ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1908589213-1064443035=:43477"
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>

--0-1908589213-1064443035=:43477
Content-Type: text/plain; charset=us-ascii

"draft-ietf-l3vpn-ospf-2547-00.txt", specifies that MP-BGP creates VPN-IPV4 route for a route learnt from CE where PE-CE link uses OSPF.
VPN-IPV4 route attaches "OSPF router ID", "OSPF route type " and "OSPF domain ID" extended communities.This is to allow this route to be converted back into OSPF route transperantly.
Why does one need to attach "OSPF router id" ?Is this attribute  used by the remote PE?
 
thanks.
Rahul
 


---------------------------------
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
--0-1908589213-1064443035=:43477
Content-Type: text/html; charset=us-ascii

<DIV>"draft-ietf-l3vpn-ospf-2547-00.txt", specifies that MP-BGP creates VPN-IPV4 route for a route learnt from CE where PE-CE link uses OSPF.</DIV>
<DIV>VPN-IPV4 route attaches "OSPF router ID", "OSPF route type " and "OSPF domain ID" extended communities.This is to allow this route to be converted back into OSPF route transperantly.</DIV>
<DIV>Why does one need to attach "OSPF router id" ?Is this attribute&nbsp; used by the remote PE?</DIV>
<DIV>&nbsp;</DIV>
<DIV>thanks.</DIV>
<DIV>Rahul</DIV>
<DIV>&nbsp;</DIV><p><hr SIZE=1>
Do you Yahoo!?<br>
<a href="http://us.rd.yahoo.com/evt=10469/*http://sitebuilder.yahoo.com">Yahoo! SiteBuilder</a> - Free, easy-to-use web site design software
--0-1908589213-1064443035=:43477--




From exim@www1.ietf.org  Thu Sep 25 14:16:32 2003
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 OAA11776
	for <l3vpn-archive@odin.ietf.org>; Thu, 25 Sep 2003 14:16:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2aes-0003he-ST
	for l3vpn-archive@odin.ietf.org; Thu, 25 Sep 2003 14:16:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8PIG6Su014230
	for l3vpn-archive@odin.ietf.org; Thu, 25 Sep 2003 14:16:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2aes-0003hR-P5
	for l3vpn-web-archive@optimus.ietf.org; Thu, 25 Sep 2003 14:16:06 -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 OAA11662
	for <l3vpn-web-archive@ietf.org>; Thu, 25 Sep 2003 14:15:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2aeq-0003OB-00
	for l3vpn-web-archive@ietf.org; Thu, 25 Sep 2003 14:16:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2aep-0003O6-00
	for l3vpn-web-archive@ietf.org; Thu, 25 Sep 2003 14:16:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2aen-0003em-AA; Thu, 25 Sep 2003 14:16:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2aeF-0003bg-5O
	for l3vpn@optimus.ietf.org; Thu, 25 Sep 2003 14:15:27 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11507;
	Thu, 25 Sep 2003 14:15:18 -0400 (EDT)
Message-Id: <200309251815.OAA11507@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: l3vpn@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-l3vpn-vpn-vr-01.txt
Date: Thu, 25 Sep 2003 14:15:18 -0400
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Layer 3 Virtual Private Networks Working Group of the IETF.

	Title		: Network based IP VPN Architecture using Virtual Routers
	Author(s)	: P. Knight, H. Ould-Brahim, B. Gleeson
	Filename	: draft-ietf-l3vpn-vpn-vr-01.txt
	Pages		: 22
	Date		: 2003-9-25
	
This draft describes a network-based Virtual Private Network (VPN) 
architecture using the virtual router (VR) concept. Multiple VRs can 
exist in a single physical device. A VR emulates all the 
functionality of a physical router, and therefore inherits all 
existing mechanisms and tools for configuration, operation, 
accounting, and maintenance. Any routing protocol can be used to 
distribute VPN reachability information among VRs, and no VPN-
related modifications or extensions are needed to the routing 
protocol for achieving VPN reachability. Direct VR-to-VR 
connectivity may be configured through layer-2 links or through IP- 
or MPLS-based tunnels. Traffic from VRs belonging to different VPNs 
may be aggregated over a 'backbone VR' network, which greatly 
simplifies VPN provisioning. This architecture accommodates various 
backbone deployment scenarios, both where the VPN service provider 
owns the backbone, and where the VPN service provider obtains 
backbone service from one or more other service providers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-vpn-vr-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-l3vpn-vpn-vr-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-l3vpn-vpn-vr-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-9-25121106.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l3vpn-vpn-vr-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-l3vpn-vpn-vr-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-9-25121106.I-D@ietf.org>

--OtherAccess--

--NextPart--






From exim@www1.ietf.org  Fri Sep 26 15:07:40 2003
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 PAA19126
	for <l3vpn-archive@odin.ietf.org>; Fri, 26 Sep 2003 15:07:40 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2xvo-0004mP-SR
	for l3vpn-archive@odin.ietf.org; Fri, 26 Sep 2003 15:07:17 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8QJ77Ss018367
	for l3vpn-archive@odin.ietf.org; Fri, 26 Sep 2003 15:07:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2xvm-0004mA-Bk
	for l3vpn-web-archive@optimus.ietf.org; Fri, 26 Sep 2003 15:07:06 -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 PAA19037
	for <l3vpn-web-archive@ietf.org>; Fri, 26 Sep 2003 15:06:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2xvj-0004fc-00
	for l3vpn-web-archive@ietf.org; Fri, 26 Sep 2003 15:07:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2xvi-0004fY-00
	for l3vpn-web-archive@ietf.org; Fri, 26 Sep 2003 15:07:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2xvi-0004km-Tr; Fri, 26 Sep 2003 15:07:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2xvf-0004k6-S4
	for l3vpn@optimus.ietf.org; Fri, 26 Sep 2003 15:06:59 -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 PAA19014
	for <l3vpn@ietf.org>; Fri, 26 Sep 2003 15:06:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2xvc-0004fH-00
	for l3vpn@ietf.org; Fri, 26 Sep 2003 15:06:56 -0400
Received: from pmesmtp02.wcom.com ([199.249.20.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2xvc-0004ey-00
	for l3vpn@ietf.org; Fri, 26 Sep 2003 15:06:56 -0400
Received: from pmismtp04.wcomnet.com ([166.38.62.39])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0HLU00DEL4SJFP@firewall.wcom.com> for l3vpn@ietf.org; Fri,
 26 Sep 2003 19:00:19 +0000 (GMT)
Received: from pmismtp04.wcomnet.com by pmismtp04.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HLU000014MYO4@pmismtp04.wcomnet.com> for l3vpn@ietf.org; Fri,
 26 Sep 2003 19:00:19 +0000 (GMT)
Received: from rbonica ([166.32.199.163])
 by pmismtp04.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with SMTP id <0HLU000A14S7EZ@pmismtp04.wcomnet.com> for l3vpn@ietf.org;
 Fri, 26 Sep 2003 19:00:07 +0000 (GMT)
Date: Fri, 26 Sep 2003 15:00:47 -0400
From: Ron Bonica <Ronald.P.Bonica@mci.com>
Subject: RE: WG Last call: draft-ietf-l3vpn-security-framework-00.txt
In-reply-to: <DKEJJCOCJMHEFFNMLKMPKEABKEAA.Ronald.P.Bonica@mci.com>
To: l3vpn@ietf.org
Message-id: <DKEJJCOCJMHEFFNMLKMPCEHHKGAA.Ronald.P.Bonica@mci.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

This last call has been extended until September 30 to allow for additional
comments. If you have comments, please send them to the list ASAP.

                                        Ron

> -----Original Message-----
> From: Ron Bonica [mailto:Ronald.P.Bonica@mci.com]
> Sent: Tuesday, September 09, 2003 10:06 AM
> To: l3vpn@ietf.org
> Subject: WG Last call: draft-ietf-l3vpn-security-framework-00.txt
>
>
> Folks,
>
> This begins a WG last call on
> draft-ietf-l3vpn-security-framework-00. The last call is to end
> at COB on September 23.
>
>                                         Ron
>
>





From exim@www1.ietf.org  Tue Sep 30 12:29:29 2003
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 MAA00410
	for <l3vpn-archive@odin.ietf.org>; Tue, 30 Sep 2003 12:29: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 1A4NN5-0000qH-Gh
	for l3vpn-archive@odin.ietf.org; Tue, 30 Sep 2003 12:29:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8UGT7H4003231
	for l3vpn-archive@odin.ietf.org; Tue, 30 Sep 2003 12:29:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4NN5-0000q2-AX
	for l3vpn-web-archive@optimus.ietf.org; Tue, 30 Sep 2003 12:29:07 -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 MAA00404
	for <l3vpn-web-archive@ietf.org>; Tue, 30 Sep 2003 12:28:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4NN3-0001Hd-00
	for l3vpn-web-archive@ietf.org; Tue, 30 Sep 2003 12:29:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4NN3-0001HZ-00
	for l3vpn-web-archive@ietf.org; Tue, 30 Sep 2003 12:29:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4NMy-0000pU-Tp; Tue, 30 Sep 2003 12:29:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4M2J-0003aY-To
	for l3vpn@optimus.ietf.org; Tue, 30 Sep 2003 11:03:35 -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 LAA25420
	for <l3vpn@ietf.org>; Tue, 30 Sep 2003 11:03:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4M2H-0007hb-00
	for l3vpn@ietf.org; Tue, 30 Sep 2003 11:03:33 -0400
Received: from weird-brew.cisco.com ([144.254.15.118] helo=strange-brew.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4M2G-0007hK-00
	for l3vpn@ietf.org; Tue, 30 Sep 2003 11:03:32 -0400
Received: from cisco.com (ppsenak--isdn-home4.cisco.com [10.49.2.221])
	by strange-brew.cisco.com (8.11.7+Sun/8.8.8) with ESMTP id h8UF31U01765
	for <l3vpn@ietf.org>; Tue, 30 Sep 2003 17:03:01 +0200 (CEST)
Message-ID: <3F799B25.9030903@cisco.com>
Date: Tue, 30 Sep 2003 17:03:01 +0200
From: Peter Psenak <ppsenak@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: l3vpn@ietf.org
Subject: Re: FWD (rahul v): ospf router-id extended community
References: <200309291629.h8TGTm5g016862@rtp-core-2.cisco.com> <3F786472.7080608@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Rahul,

>>
>>
>> "draft-ietf-l3vpn-ospf-2547-00.txt", specifies that MP-BGP creates 
>> VPN-IPV4 route for a route learnt from CE where PE-CE link uses OSPF.
>> VPN-IPV4 route attaches "OSPF router ID", "OSPF route type " and 
>> "OSPF domain ID" extended communities.This is to allow this route to 
>> be converted back into OSPF route transperantly.
>> Why does one need to attach "OSPF router id" ?Is this attribute  used 
>> by the remote PE? 
>

Router-ID extended community is optional. We use it to optimize the 
redistribution from BGP to OSPF when sham-links are in use.

thanks,
Peter

>>
>>  
>> thanks.
>> Rahul
>>  
>> ------------------------------------------------------------------------
>> Do you Yahoo!?
>> Yahoo! SiteBuilder 
>> <http://us.rd.yahoo.com/evt=10469/*http://sitebuilder.yahoo.com> - 
>> Free, easy-to-use web site design software 
>
>
>
>






From exim@www1.ietf.org  Tue Sep 30 14:20:41 2003
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 OAA05787
	for <l3vpn-archive@odin.ietf.org>; Tue, 30 Sep 2003 14:20:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4P6Z-0000Mw-3q
	for l3vpn-archive@odin.ietf.org; Tue, 30 Sep 2003 14:20:19 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8UIKA0s001237
	for l3vpn-archive@odin.ietf.org; Tue, 30 Sep 2003 14:20:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4P6W-0000Jq-6I
	for l3vpn-web-archive@optimus.ietf.org; Tue, 30 Sep 2003 14:20:08 -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 OAA05756
	for <l3vpn-web-archive@ietf.org>; Tue, 30 Sep 2003 14:19:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4P6T-0002gN-00
	for l3vpn-web-archive@ietf.org; Tue, 30 Sep 2003 14:20:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4P6T-0002gJ-00
	for l3vpn-web-archive@ietf.org; Tue, 30 Sep 2003 14:20:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4P6R-0000IS-KQ; Tue, 30 Sep 2003 14:20:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4P5c-0000Gn-Ra
	for l3vpn@optimus.ietf.org; Tue, 30 Sep 2003 14:19:12 -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 OAA05694
	for <l3vpn@ietf.org>; Tue, 30 Sep 2003 14:19:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4P5a-0002fF-00
	for l3vpn@ietf.org; Tue, 30 Sep 2003 14:19:10 -0400
Received: from mta8.wss.scd.yahoo.com ([66.218.85.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4P5Z-0002f4-00
	for l3vpn@ietf.org; Tue, 30 Sep 2003 14:19:10 -0400
Received: from [63.159.68.40] by mta8.wss.scd.yahoo.com with HTTP; Tue, 30 Sep 2003 11:18:38 -0700
Date: Tue, 30 Sep 2003 14:18:38 -0400
Message-ID: <3F615C4A0000B4F7@mta8.wss.scd.yahoo.com>
From: "Kavita Khanna" <kkhanna@isocore.com>
Subject: MPLS 2003 (Washington D.C., Oct 26-28) - Special Rate Deadline ends Sept 30
To: l3vpn@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Apologies if you receive multiple copies of this call for participation..=
.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
MPLS 2003 International Conference
Omni Shoreham Hotel, Washington D.C.
October 26-28, 2003
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
    http://www.mpls2003.com 
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

You are cordially invited to attend the MPLS 2003 International
Conference to be held in Washington D.C. October 26-28, 2003. The 3-day
event consists of highly technical sessions, tutorials, panel
discussions, and exhibits.

Registration for the conference is now open. Early registration
discounts are extremely lucrative and are valid for a limited time only.
To register, go to:

 http://www.mpls2003.com/registration.htm

Important Dates:
---------------------
- Early Registration Rates Cut-Off Date: September 30
- Tutorials: October 26, 9:00am - 5:30 pm
- Conference sessions: October 27-28, 8:45am-6:30pm
- Exhibits: October 27-28, 8:45am-6:30pm

Program (visit http://mpls2003.com/sessions.htm for details):

Sunday October 26
------------------
 Tutorial 1: Introduction to MPLS
 Tutorial 2: VPNs
 Tutorial 3: Layer 2 VPNs/VPLS
 Tutorial 4: MPLS Security

Monday October 27
------------------
 Opening remarks - Peter Hill (BellSouth Telecommunications) & Dr. Hamid
Ahmadi (AT&T Labs) 
 Introduction - Luca Martini (Level3 Communications)
 Keynote 
 
 Session: Convergence (Service Provider's Perspective) 
  - What is the Role of MPLS in Network Convergence? - R. Spencer, BT 
  - MPLS Convergence Strategies - R. Moignard, France Telecom 
  - MPLS: The Catalyst of Convergence? - C. Masiero, Equant 
 
 Session: OAM 
  - New Developments in MPLS and IP OAM - G. Swallow, Cisco Systems 
  - Network Management of MPLS-based VPNs - K. Melden, Juniper Networks
  - MPLS Convergence, Control and OAM Implications - D. Allan, Nortel
Networks
  - Service OA&M for MPLS VPNs - V. Kompella, Alcatel 
 
 Session: Layer 2 Transport & Interworking over MPLS 
  - VPLS - Remember LANE? - A. Sayeed, Cisco Systems 
  - VPLS - K. Kompella, Juniper Networks 
  - Transitioning a Profitable Service Portfolio to an MPLS Core Network
- M. Nielsen, Lucent Technologies 
  - VPLS Provisioning, Performance and Scalability: Problems and
Solutions - V. Radoaca, Nortel Networks 
 
 Session: L2/L3 VPNs 
  - BGP-VPN Services: Lessons Learned - R. Bonica, MCI 
  - Design and Deploy Scalable Inter-AS MPLS VPNs - L. Fang, AT&T 
  - L2-MPLS Networks - Y. Sato, NTT Communications 
  - MPLS in Multi-AS Networks - R. Doukov, Flag Telecom 
 
 PANEL: MPLS as a Fusing Technology 
  - Chair: P. Hill, VP Technology Planning & Deployment, BellSouth
Telecommunications

 In this panel session, service providers will discuss issues
surrounding convergence and will present their views and experience on
MPLS as a way to fuse multiple networks together. Specifically, are
there favorable economics; do the technical approaches work, when might
they be standardized and what are the limitations.

Tuesday, October 28
-------------------
 Keynote 
 Lessons Learned - Yakov Rekhter (Juniper Networks) 
 Critical Issues for Network Consolidation - Daniel Awduche (MCI) 
 
 Session: Reliability 
  - Next Generation Core Routers: Defining IP Reliability and Resiliency
- L. Mamakos, Hyperchip 
  - High Resiliency MPLS Network Design - S. Poretsky, Quarry
Technologies 
  - Hardening MPLS-based Networks - S. Vogelsang, Laurel Networks 
 
 Session: IP Optical Integration 
  - Optical Market Forces on GMPLS - K. Sage, Cisco Systems 
  - Multiservice Metro Networks in Sweden and Their Plans to Go GMPLS -
L. Andersson 
  - Photonic Internet Laboratory: New Challenges for Future Photonic
Network- N. Yamanaka, NTT 
  - Generalized VPNs (GVPNs) - H. Ould-Brahim, Nortel Networks 
 
 Session: New MPLS Features 
  - Scalable Multicast MPLS Technology for Next Generation Broadband
Services Network - S. Yasukawa, NTT 
  - Multicast Traffic Engineering with MPLS - R. Aggarwal, Juniper
Networks
  - LDP Fast Convergence - A. Atlas, Avici Systems 
  - How to secure an MPLS/VPN network - M. Behringer, Cisco Systems 
  - Integration of IPv6 and IPv6 VPN Services over MPLS - F. Le
Faucheur, Cisco Systems 
 
 Session: Traffic Engineering 
  - Inter-area and Inter-AS MPLS Traffic Engineering - JP Vasseur, Cisco
Systems 
  - Traffic Engineering in Hierarchical Multiprovider Networks - G.
Apostolopoulos, Redback Networks 
  - Multi-Region (multiarea/multiAS) Traffic Engineering - A. Ayyangar,
Juniper Networks 
  - Advanced MPLS Application Testing - B. Miller, IXIA 
 
 Session: Service & Provisioning Issues 
  - MPLS Network Management: Enterprise Deployment Management - T.
Nadeau, Cisco Systems 
  - Attracting New Enterprise Customers with MPLS VPN Services - D.
Christophe, Lucent Technologies 
  - MPLS Beyond Service Provider Cores - A. Malis, Tellabs 
  - Critical Quality of Service Issues in MPLS Networks - J. Brayley,
Laurel Networks 
  - Practical Implementation of Tools Allied to the Network Management
of IP/MPLS-based Networks - P. Beaumont, WANDL 






From exim@www1.ietf.org  Tue Sep 30 21:40:29 2003
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 VAA24676
	for <l3vpn-archive@odin.ietf.org>; Tue, 30 Sep 2003 21:40: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 1A4VyJ-0003ar-4n
	for l3vpn-archive@odin.ietf.org; Tue, 30 Sep 2003 21:40:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h911e6s1013809
	for l3vpn-archive@odin.ietf.org; Tue, 30 Sep 2003 21:40:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4VyI-0003aU-9p
	for l3vpn-web-archive@optimus.ietf.org; Tue, 30 Sep 2003 21:40:06 -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 VAA24642
	for <l3vpn-web-archive@ietf.org>; Tue, 30 Sep 2003 21:39:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4VyF-0000GD-00
	for l3vpn-web-archive@ietf.org; Tue, 30 Sep 2003 21:40:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4VyF-0000GA-00
	for l3vpn-web-archive@ietf.org; Tue, 30 Sep 2003 21:40:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4VyF-0003Zw-CV; Tue, 30 Sep 2003 21:40:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4Vxs-0003Y1-Ja
	for l3vpn@optimus.ietf.org; Tue, 30 Sep 2003 21:39:40 -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 VAA24620
	for <l3vpn@ietf.org>; Tue, 30 Sep 2003 21:39:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4Vxp-0000Fh-00
	for l3vpn@ietf.org; Tue, 30 Sep 2003 21:39:37 -0400
Received: from pmesmtp02.wcom.com ([199.249.20.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4Vxp-0000FZ-00
	for l3vpn@ietf.org; Tue, 30 Sep 2003 21:39:37 -0400
Received: from pmismtp04.wcomnet.com ([166.38.62.39])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0HM200E6C1MWK8@firewall.wcom.com> for l3vpn@ietf.org; Wed,
 01 Oct 2003 01:32:56 +0000 (GMT)
Received: from pmismtp04.wcomnet.com by pmismtp04.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HM200M011MVSI@pmismtp04.wcomnet.com> for l3vpn@ietf.org; Wed,
 01 Oct 2003 01:32:56 +0000 (GMT)
Received: from rbonica ([166.50.96.138])
 by pmismtp04.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with SMTP id <0HM200KDE1MUDU@pmismtp04.wcomnet.com> for l3vpn@ietf.org;
 Wed, 01 Oct 2003 01:32:55 +0000 (GMT)
Date: Tue, 30 Sep 2003 21:33:33 -0400
From: Ron Bonica <Ronald.P.Bonica@mci.com>
Subject: RE: WG Last call: draft-ietf-l3vpn-security-framework-00.txt
In-reply-to: <DKEJJCOCJMHEFFNMLKMPCEHHKGAA.Ronald.P.Bonica@mci.com>
To: l3vpn@ietf.org
Message-id: <DKEJJCOCJMHEFFNMLKMPGEAGKHAA.Ronald.P.Bonica@mci.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: l3vpn-admin@ietf.org
Errors-To: l3vpn-admin@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Id: <l3vpn.ietf.org>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

This ends the last call. I will send this document on to the IESG with a
proposal to publish as an Informational RFC.

                                                       Ron

> -----Original Message-----
> From: Ron Bonica [mailto:Ronald.P.Bonica@mci.com]
> Sent: Friday, September 26, 2003 3:01 PM
> To: l3vpn@ietf.org
> Subject: RE: WG Last call: draft-ietf-l3vpn-security-framework-00.txt
>
>
> Folks,
>
> This last call has been extended until September 30 to allow for
> additional comments. If you have comments, please send them to
> the list ASAP.
>
>                                         Ron
>
> > -----Original Message-----
> > From: Ron Bonica [mailto:Ronald.P.Bonica@mci.com]
> > Sent: Tuesday, September 09, 2003 10:06 AM
> > To: l3vpn@ietf.org
> > Subject: WG Last call: draft-ietf-l3vpn-security-framework-00.txt
> >
> >
> > Folks,
> >
> > This begins a WG last call on
> > draft-ietf-l3vpn-security-framework-00. The last call is to end
> > at COB on September 23.
> >
> >                                         Ron
> >
> >





