From exim@www1.ietf.org  Mon Nov  3 11:26: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 LAA09097
	for <l3vpn-archive@odin.ietf.org>; Mon, 3 Nov 2003 11:26:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGhWr-00077b-Ja
	for l3vpn-archive@odin.ietf.org; Mon, 03 Nov 2003 11:26:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA3GQ9ll027369
	for l3vpn-archive@odin.ietf.org; Mon, 3 Nov 2003 11:26:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGhWr-00077M-EV
	for l3vpn-web-archive@optimus.ietf.org; Mon, 03 Nov 2003 11:26:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09083
	for <l3vpn-web-archive@ietf.org>; Mon, 3 Nov 2003 11:25:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AGhWq-0000II-00
	for l3vpn-web-archive@ietf.org; Mon, 03 Nov 2003 11:26:08 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AGhWq-0000IE-00
	for l3vpn-web-archive@ietf.org; Mon, 03 Nov 2003 11:26:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGhWj-00076d-87; Mon, 03 Nov 2003 11:26:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGhWN-00076E-VA
	for l3vpn@optimus.ietf.org; Mon, 03 Nov 2003 11:25:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09070
	for <l3vpn@ietf.org>; Mon, 3 Nov 2003 11:25:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AGhWN-0000Hw-00
	for l3vpn@ietf.org; Mon, 03 Nov 2003 11:25:39 -0500
Received: from natint2.juniper.net ([207.17.136.150] helo=merlot.juniper.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AGhWM-0000Hd-00
	for l3vpn@ietf.org; Mon, 03 Nov 2003 11:25:38 -0500
Received: from rcallon-lt.juniper.net (securepptp045.static.jnpr.net [172.24.253.45])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id hA3GP7i14456;
	Mon, 3 Nov 2003 08:25:07 -0800 (PST)
	(envelope-from rcallon@juniper.net)
Message-Id: <4.3.2.20031103112152.0139b9e0@zircon.juniper.net>
X-Sender: rcallon@zircon.juniper.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Mon, 03 Nov 2003 11:23:23 -0500
To: l3vpn@ietf.org
From: Ross Callon <rcallon@juniper.net>
Subject: Agenda items for l3vpn in Minneapolis
Cc: Ronald.P.Bonica@mci.com, rick@rhwilder.net, rcallon@juniper.net
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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>

If anyone has items which they would like added to the
l3vpn working group agenda at the upcoming IETF in
Minneapolis then please send email to Ron, Rick, and
I.

Thanks, Ross





From exim@www1.ietf.org  Wed Nov  5 10:47:23 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 KAA10746
	for <l3vpn-archive@odin.ietf.org>; Wed, 5 Nov 2003 10:47:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHPs8-0000sd-Ik
	for l3vpn-archive@odin.ietf.org; Wed, 05 Nov 2003 10:47:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA5Fl4Lh003377
	for l3vpn-archive@odin.ietf.org; Wed, 5 Nov 2003 10:47:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHPs8-0000sO-De
	for l3vpn-web-archive@optimus.ietf.org; Wed, 05 Nov 2003 10:47:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10715
	for <l3vpn-web-archive@ietf.org>; Wed, 5 Nov 2003 10:46:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHPs6-00061L-00
	for l3vpn-web-archive@ietf.org; Wed, 05 Nov 2003 10:47:02 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHPs5-00061H-00
	for l3vpn-web-archive@ietf.org; Wed, 05 Nov 2003 10:47:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHPs6-0000rm-4D; Wed, 05 Nov 2003 10:47:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHPrW-0000oa-Hx
	for l3vpn@optimus.ietf.org; Wed, 05 Nov 2003 10:46:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10669
	for <l3vpn@ietf.org>; Wed, 5 Nov 2003 10:46:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHPrU-000615-00
	for l3vpn@ietf.org; Wed, 05 Nov 2003 10:46:24 -0500
Received: from dns1.marketweb.net.tr ([212.45.64.20] helo=kheops.marketweb.net.tr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHPrR-000612-00
	for l3vpn@ietf.org; Wed, 05 Nov 2003 10:46:22 -0500
Received: from mert ([212.45.75.17])
	by kheops.marketweb.net.tr (8.12.8/8.12.8) with SMTP id hA5G0hXQ003498
	for <l3vpn@ietf.org>; Wed, 5 Nov 2003 18:00:48 +0200
Message-ID: <001201c3a3b3$ec591380$11f28ec3@mert>
From: "Mertay" <mert@mw.net.tr>
To: <l3vpn@ietf.org>
Subject: EIGRP for MPLS VPN Protocol
Date: Wed, 5 Nov 2003 17:45:59 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000F_01C3A3C4.AC4275A0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300
X-RAVMilter-Version: 8.4.4(snapshot 20030410) (kheops.marketweb.net.tr)
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>

This is a multi-part message in MIME format.

------=_NextPart_000_000F_01C3A3C4.AC4275A0
Content-Type: text/plain;
	charset="iso-8859-9"
Content-Transfer-Encoding: quoted-printable

Folks:

I am cheif technology architect for regional IP service provider. We =
have been getting requests from customer to use EIGRP as peering =
protocol for MPLS VPN service. As far as I know this is Propritary =
protocol. What is the position of this "Standard" group? This is getting =
alot of market in L3 VPN space.



thanks

Mertay Basekim


------=_NextPart_000_000F_01C3A3C4.AC4275A0
Content-Type: text/html;
	charset="iso-8859-9"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-9">
<META content=3D"MSHTML 6.00.2733.1800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><FONT size=3D2>
<P>Folks:</P>
<P>I am cheif technology architect for regional IP service provider. We =
have=20
been getting requests from customer to use EIGRP as peering protocol for =
MPLS=20
VPN service. As far as I know this is Propritary protocol. What is the =
position=20
of this "Standard" group? This is getting alot of market in L3 VPN =
space.</P>
<P>&nbsp;</P>
<P>thanks</P>
<P>Mertay Basekim</P></FONT></FONT></DIV></BODY></HTML>

------=_NextPart_000_000F_01C3A3C4.AC4275A0--






From exim@www1.ietf.org  Tue Nov 11 10:51:29 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06676
	for <l3vpn-archive@odin.ietf.org>; Tue, 11 Nov 2003 10:51:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJanO-0000tn-K3
	for l3vpn-archive@odin.ietf.org; Tue, 11 Nov 2003 10:51:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hABFpAxK003449
	for l3vpn-archive@odin.ietf.org; Tue, 11 Nov 2003 10:51:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJanO-0000tU-GQ
	for l3vpn-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 10:51:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06645
	for <l3vpn-web-archive@ietf.org>; Tue, 11 Nov 2003 10:50:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJanL-0004y5-00
	for l3vpn-web-archive@ietf.org; Tue, 11 Nov 2003 10:51:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJanL-0004xw-00
	for l3vpn-web-archive@ietf.org; Tue, 11 Nov 2003 10:51:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJanG-0000oC-DS; Tue, 11 Nov 2003 10:51:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJamc-0000me-Qs
	for l3vpn@optimus.ietf.org; Tue, 11 Nov 2003 10:50:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06606
	for <l3vpn@ietf.org>; Tue, 11 Nov 2003 10:50:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJama-0004xJ-00
	for l3vpn@ietf.org; Tue, 11 Nov 2003 10:50:20 -0500
Received: from natint2.juniper.net ([207.17.136.150] helo=merlot.juniper.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJamZ-0004wv-00
	for l3vpn@ietf.org; Tue, 11 Nov 2003 10:50:19 -0500
Received: from rcallon-lt.juniper.net (securepptp094.static.jnpr.net [172.24.253.94])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id hABFnki32768
	for <l3vpn@ietf.org>; Tue, 11 Nov 2003 07:49:47 -0800 (PST)
	(envelope-from rcallon@juniper.net)
Message-Id: <4.3.2.20031111103740.02e62218@zircon.juniper.net>
X-Sender: rcallon@zircon.juniper.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Tue, 11 Nov 2003 10:43:00 -0500
To: l3vpn@ietf.org
From: Ross Callon <rcallon@juniper.net>
Subject: FYI: Working Group Last Call for
  draft-ietf-ospf-2547-dnbit-01.txt to both lists
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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>

This is the last call in the OSPF working group for the 
document draft-ietf-ospf-2547-dnbit-01.txt. This document
describes an extension to OSPF for the purpose of 
supporting L3 VPNs.

Note that this last call has been extended to 11/21/2003
(5pm eastern time), so there is still plenty of time to respond. 

In order to send to the OSPF mailing list you have to be a 
member of the OSPF mailing list. If anyone wants to comment 
but is not on the list, there are two options: (i) Get added to 
the OSPF list; or (ii) Send comments to the ospf  chairs and 
document authors.

Thanks, Ross


>X-JNPR-Received-From: outside
>To: OSPF@PEACH.EASE.LSOFT.COM
>cc: ronald.p.bonica@mci.com, rick@rhwilder.net, rcallon@juniper.net,
>    erosen@cisco.com
>Subject: Working Group Last Call for draft-ietf-ospf-2547-dnbit-01.txt to both lists
>Date: Tue, 28 Oct 2003 20:31:49 -0500
>From: Rohit Dube <rohit@utstar.com>
>X-OriginalArrivalTime: 29 Oct 2003 01:31:51.0340 (UTC) FILETIME=[6D85BEC0:01C39DBC]
>X-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang)
>
>
>This is the start of a Working Group last call for
>"Using an LSA Options Bit to Prevent Looping in BGP/MPLS IP VPNs"
>(draft-ietf-ospf-2547-dnbit-01.txt)
>All comments should be received by 5PM (US Eastern), 11/14/2003.
>Please send your comments to the OSPF list.
>
>The draft can be found at
>http://www.ietf.org/internet-drafts/draft-ietf-ospf-2547-dnbit-01.txt
>This is a companion document to draft-ietf-l3vpn-ospf-2547-00.txt
>which is also in Last Call. Both of these documents are being Last Called
>in OSPF WG as well as the L3VPN WG.
>
>--rohit.





From exim@www1.ietf.org  Tue Nov 11 10:51:29 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06675
	for <l3vpn-archive@odin.ietf.org>; Tue, 11 Nov 2003 10:51:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJanO-0000tY-GU
	for l3vpn-archive@odin.ietf.org; Tue, 11 Nov 2003 10:51:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hABFpAgM003432
	for l3vpn-archive@odin.ietf.org; Tue, 11 Nov 2003 10:51:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJanO-0000tH-CP
	for l3vpn-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 10:51:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06647
	for <l3vpn-web-archive@ietf.org>; Tue, 11 Nov 2003 10:50:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJanL-0004y6-00
	for l3vpn-web-archive@ietf.org; Tue, 11 Nov 2003 10:51:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJanL-0004xv-00
	for l3vpn-web-archive@ietf.org; Tue, 11 Nov 2003 10:51:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJanG-0000o1-0e; Tue, 11 Nov 2003 10:51:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJamY-0000mY-9J
	for l3vpn@optimus.ietf.org; Tue, 11 Nov 2003 10:50:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06600
	for <l3vpn@ietf.org>; Tue, 11 Nov 2003 10:50:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJamV-0004x9-00
	for l3vpn@ietf.org; Tue, 11 Nov 2003 10:50:15 -0500
Received: from natint2.juniper.net ([207.17.136.150] helo=merlot.juniper.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJamU-0004wr-00
	for l3vpn@ietf.org; Tue, 11 Nov 2003 10:50:15 -0500
Received: from rcallon-lt.juniper.net (securepptp094.static.jnpr.net [172.24.253.94])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id hABFnei32762
	for <l3vpn@ietf.org>; Tue, 11 Nov 2003 07:49:40 -0800 (PST)
	(envelope-from rcallon@juniper.net)
Message-Id: <4.3.2.20031111102509.0138b410@zircon.juniper.net>
X-Sender: rcallon@zircon.juniper.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Tue, 11 Nov 2003 10:45:01 -0500
To: l3vpn@ietf.org
From: Ross Callon <rcallon@juniper.net>
Subject: Draft Agenda for Working Group meeting
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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>


			Draft Agenda for L3VPN

Agenda Bashing 			(5 minutes -- chairs)

Status of Working Group Documents 	(15 minutes -- Ross Callon)

Ongoing / Future work in L3VPN 	(15 minutes -- Ron Bonica)

MPLS over L2TP			(15 minutes -- Mark Townsley)

CE member authentication 		(20 minutes -- Ron Bonica and Michael Behringer)





From exim@www1.ietf.org  Tue Nov 11 10:51:35 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06708
	for <l3vpn-archive@odin.ietf.org>; Tue, 11 Nov 2003 10:51:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJanS-0000vl-Tz
	for l3vpn-archive@odin.ietf.org; Tue, 11 Nov 2003 10:51:18 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hABFpEBQ003571
	for l3vpn-archive@odin.ietf.org; Tue, 11 Nov 2003 10:51:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJanO-0000tX-HK
	for l3vpn-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 10:51:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06649
	for <l3vpn-web-archive@ietf.org>; Tue, 11 Nov 2003 10:50:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJanL-0004y9-00
	for l3vpn-web-archive@ietf.org; Tue, 11 Nov 2003 10:51:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJanL-0004xz-00
	for l3vpn-web-archive@ietf.org; Tue, 11 Nov 2003 10:51:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJanG-0000oW-QD; Tue, 11 Nov 2003 10:51:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJamd-0000md-1O
	for l3vpn@optimus.ietf.org; Tue, 11 Nov 2003 10:50:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06603
	for <l3vpn@ietf.org>; Tue, 11 Nov 2003 10:50:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJamX-0004xE-00
	for l3vpn@ietf.org; Tue, 11 Nov 2003 10:50:17 -0500
Received: from natint2.juniper.net ([207.17.136.150] helo=merlot.juniper.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJamX-0004wu-00
	for l3vpn@ietf.org; Tue, 11 Nov 2003 10:50:17 -0500
Received: from rcallon-lt.juniper.net (securepptp094.static.jnpr.net [172.24.253.94])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id hABFnii32765;
	Tue, 11 Nov 2003 07:49:45 -0800 (PST)
	(envelope-from rcallon@juniper.net)
Message-Id: <4.3.2.20031111103244.02cc8ce0@zircon.juniper.net>
X-Sender: rcallon@zircon.juniper.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Tue, 11 Nov 2003 10:37:29 -0500
To: l3vpn@ietf.org
From: Ross Callon <rcallon@juniper.net>
Subject: Extended last call draft-ietf-l3vpn-ospf-2547-00.txt 
Cc: acee@redback.com, rohit@utstar.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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>

The last call deadline on draft-ietf-l3vpn-ospf-2547-00.txt 
is extended to 11/21/2003 5PM Eastern.

This is partly due to the IETF (people are pretty busy this 
week), and partly to correspond to the last call on the 
companion document draft-ietf-ospf-2547-dnbit-01.txt 
whose last call in the OSPF working group has also been 
extended to 11/21/2003. 

thanks, Ross


>Date: Tue, 28 Oct 2003 08:57:53 -0500
>To: l3vpn@ietf.org, ospf@peach.ease.lsoft.com
>From: Ross Callon <rcallon@juniper.net>
>Subject: last call draft-ietf-l3vpn-ospf-2547-00.txt 
>Sender: l3vpn-admin@ietf.org
>
>This begins the working group last call on:
>
>         OSPF as the PE/CE Protocol in BGP/MPLS VPNs 
>         draft-ietf-l3vpn-ospf-2547-00.txt 
>
>While this document is an l3vpn working group document,
>the last call will take place on both the l3vpn and ospf working
>group mailing lists. The last call will terminate at the end of the 
>day on Friday November 14th.
>
>Thanks, Ross 
>





From exim@www1.ietf.org  Fri Nov 14 01:51:38 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15366
	for <l3vpn-archive@odin.ietf.org>; Fri, 14 Nov 2003 01:51:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKXnc-00054y-HY
	for l3vpn-archive@odin.ietf.org; Fri, 14 Nov 2003 01:51:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAE6pKpI019518
	for l3vpn-archive@odin.ietf.org; Fri, 14 Nov 2003 01:51:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKXnc-00054j-Dj
	for l3vpn-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 01:51:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15360
	for <l3vpn-web-archive@ietf.org>; Fri, 14 Nov 2003 01:51:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKXnZ-0007LO-00
	for l3vpn-web-archive@ietf.org; Fri, 14 Nov 2003 01:51:17 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKXnY-0007LK-00
	for l3vpn-web-archive@ietf.org; Fri, 14 Nov 2003 01:51:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKXnJ-00052r-Gf; Fri, 14 Nov 2003 01:51:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKXmg-00051k-EE
	for l3vpn@optimus.ietf.org; Fri, 14 Nov 2003 01:50:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15328
	for <l3vpn@ietf.org>; Fri, 14 Nov 2003 01:50:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKXmd-0007KU-00
	for l3vpn@ietf.org; Fri, 14 Nov 2003 01:50:19 -0500
Received: from [203.197.140.35] (helo=fsnt.future.futsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKXmb-0007KM-00
	for l3vpn@ietf.org; Fri, 14 Nov 2003 01:50:18 -0500
Received: from kailash.future.futsoft.com (unverified [203.197.140.36]) by 
    fsnt.future.futsoft.com (Content Technologies SMTPRS 4.3.6) with ESMTP id 
    <T65e69c30fecbc58c2364c@fsnt.future.futsoft.com> for <l3vpn@ietf.org>; 
    Fri, 14 Nov 2003 12:24:52 +0530
Received: from sakthivss (sakthivss.future.futsoft.com [10.6.4.130]) by 
    kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id hAE6mu326238 for 
    <l3vpn@ietf.org>; Fri, 14 Nov 2003 12:18:56 +0530
Reply-To: <sakthivss@future.futsoft.com>
From: "Sakthivadivu.S.S" <sakthivss@future.futsoft.com>
To: <l3vpn@ietf.org>
Subject: Carrying Label
Date: Fri, 14 Nov 2003 12:21:46 +0530
Message-ID: <001101c3aa7b$c62022c0$8204060a@future.futsoft.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
    boundary="----=_NextPart_000_0012_01C3AAA9.DFD85EC0"
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 V6.00.2800.1106
Importance: Normal
In-Reply-To: 
    <8B888AAAAB0FD31189590008C791844310DE9958@zbl6c002.corpeast.baynetworks.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>

This is a multi-part message in MIME format.

------=_NextPart_000_0012_01C3AAA9.DFD85EC0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

MessageHi,
   The Carrying Label Infomation in BGP4  (RFC 3107) says in section 3 under
heading b) Label


    "  The Label field carries one or more labels (that corresponds to
         the stack of labels [MPLS-ENCAPS]).  Each label is encoded as 3
         octets, where the high-order 20 bits contain the label value,
         and the low order bit contains "Bottom of Stack" (as defined in
         [MPLS-ENCAPS]). "

   Can you please tell me when will more than one label be distributed in
BGP upadte message.

   Only LDP distributes two labels in the ATM scenario.

   Since the label in the BGP update message is associated with BGP
nexthop,i feel that only one label will be carried in BGP
   update message  always.

    Please correct me if i am wrong.

Regards,
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.
***************************************************************************


------=_NextPart_000_0012_01C3AAA9.DFD85EC0
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-8859-=
1">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D040414206-14112003>Hi,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D040414206-14112003>&nbsp;&nbsp; The Carrying Label Infomation in=20
BGP4&nbsp; (RFC 3107) says in section 3 under heading b)=20
Label</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D040414206-14112003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D040414206-14112003>&nbsp;&nbsp; </SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D040414206-14112003>&nbsp;&nbsp;&nbsp; "&nbsp; <FONT color=3D#000000=
 size=3D3>The Label field carries one or more labels (that corresponds=20
to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the stack of labels=
 [MPLS-ENCAPS]).&nbsp; Each label is encoded as=20
3<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; octets, where the=20
high-order 20 bits contain the label=20
value,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and the low orde=
r bit=20
contains "Bottom of Stack" (as defined=20
in<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [MPLS-ENCAPS]).=20
"<BR><BR>&nbsp;&nbsp; <FONT color=3D#0000ff>Can you please tell me when wil=
l more=20
than one label be distributed in BGP upadte=20
message.</FONT></FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D3><SPAN=20
class=3D040414206-14112003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D3><SPAN=20
class=3D040414206-14112003>&nbsp;&nbsp; Only LDP distributes two labels in =
the ATM=20
scenario.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#000000 size=3D3><SPAN=20
class=3D040414206-14112003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#000000 size=3D3><SPAN=20
class=3D040414206-14112003>&nbsp;<FONT color=3D#0000ff size=3D2>&nbsp; <FON=
T=20
size=3D3>Since the label in the BGP update message is associated with BGP=
 nexthop,i feel that only one label will be&nbsp;carried in BGP=20
</FONT></FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#000000><SPAN class=3D040414206-14112003><F=
ONT=20
color=3D#0000ff>&nbsp;&nbsp; update message&nbsp; always.=20
</FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D040414206-14112003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D040414206-14112003>&nbsp;&nbsp;&nbsp; Please&nbsp;correct me if i a=
m=20
wrong.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D040414206-14112003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff><SPAN=20
class=3D040414206-14112003>Regards,<BR>Sakthi</SPAN></FONT></DIV><FONT SIZE=
=3D3><BR>
<BR>
***************************************************************************=
<BR>
This message is proprietary to Future Software Limited (FSL)<BR>
and is intended solely for the use of the individual to whom it<BR>
is addressed. It may contain  privileged or confidential information<BR>
and should not be circulated or used for any purpose other than for<BR>
what it is intended.<BR>
<BR>
If you have received this message in error, please notify the<BR>
originator immediately. If you are not the intended recipient,<BR>
you are notified that you are strictly prohibited from using,<BR>
copying, altering, or disclosing the contents of this message.<BR>
FSL accepts no responsibility for loss or damage arising from<BR>
the use of the information transmitted by this email including<BR>
damage from virus.<BR>
***************************************************************************=
<BR>
</FONT>
</BODY></HTML>

------=_NextPart_000_0012_01C3AAA9.DFD85EC0--




From exim@www1.ietf.org  Fri Nov 14 04:18:23 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02743
	for <l3vpn-archive@odin.ietf.org>; Fri, 14 Nov 2003 04:18:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKa5e-0007zi-4P
	for l3vpn-archive@odin.ietf.org; Fri, 14 Nov 2003 04:18:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAE9I65e030730
	for l3vpn-archive@odin.ietf.org; Fri, 14 Nov 2003 04:18:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKa5d-0007zZ-HF
	for l3vpn-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 04:18:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02736
	for <l3vpn-web-archive@ietf.org>; Fri, 14 Nov 2003 04:17:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKa5a-0001eh-00
	for l3vpn-web-archive@ietf.org; Fri, 14 Nov 2003 04:18:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKa5a-0001ee-00
	for l3vpn-web-archive@ietf.org; Fri, 14 Nov 2003 04:18:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKa5a-0007z0-IO; Fri, 14 Nov 2003 04:18:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKa59-0007uy-5V
	for l3vpn@optimus.ietf.org; Fri, 14 Nov 2003 04:17:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02733
	for <l3vpn@ietf.org>; Fri, 14 Nov 2003 04:17:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKa56-0001eb-00
	for l3vpn@ietf.org; Fri, 14 Nov 2003 04:17:32 -0500
Received: from web25101.mail.ukl.yahoo.com ([217.12.10.49])
	by ietf-mx with smtp (Exim 4.12)
	id 1AKa55-0001eG-00
	for l3vpn@ietf.org; Fri, 14 Nov 2003 04:17:31 -0500
Message-ID: <20031114091701.73627.qmail@web25101.mail.ukl.yahoo.com>
Received: from [165.213.1.1] by web25101.mail.ukl.yahoo.com via HTTP; Fri, 14 Nov 2003 09:17:01 GMT
Date: Fri, 14 Nov 2003 09:17:01 +0000 (GMT)
From: =?iso-8859-1?q?John=20Smith?= <jsmith4112003@yahoo.co.uk>
Subject: AW: Carrying Label
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 Sakthivadivu,

Yes you are right. There is only one label always carried in BGP for the BGP/MPLS VPN
which maps to the BGP NEXT_HOP.

Cheers,
John

P.S.
And please try not to use HTML in public mailing lists !! :-)

----- Original Message ----- 
From: Sakthivadivu.S.S 
To: l3vpn@ietf.org 
Sent: Friday, November 14, 2003 3:51 PM
Subject: Carrying Label


Hi,
   The Carrying Label Infomation in BGP4  (RFC 3107) says in section 3 under heading b)
Label
 
   
    "  The Label field carries one or more labels (that corresponds to
         the stack of labels [MPLS-ENCAPS]).  Each label is encoded as 3
         octets, where the high-order 20 bits contain the label value,
         and the low order bit contains "Bottom of Stack" (as defined in
         [MPLS-ENCAPS]). "

   Can you please tell me when will more than one label be distributed in BGP upadte
message.
 
   Only LDP distributes two labels in the ATM scenario.
 
   Since the label in the BGP update message is associated with BGP nexthop,i feel that
only one label will be carried in BGP 
   update message  always. 
 
    Please correct me if i am wrong.
 
Regards,
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.
***************************************************************************


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




From exim@www1.ietf.org  Mon Nov 17 09:08:31 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12118
	for <l3vpn-archive@odin.ietf.org>; Mon, 17 Nov 2003 09:08:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALk32-0008SQ-GG
	for l3vpn-archive@odin.ietf.org; Mon, 17 Nov 2003 09:08:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAHE8C3J032504
	for l3vpn-archive@odin.ietf.org; Mon, 17 Nov 2003 09:08:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALk32-0008SB-Cc
	for l3vpn-web-archive@optimus.ietf.org; Mon, 17 Nov 2003 09:08:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12109
	for <l3vpn-web-archive@ietf.org>; Mon, 17 Nov 2003 09:08:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALk30-0006xi-00
	for l3vpn-web-archive@ietf.org; Mon, 17 Nov 2003 09:08:11 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALk30-0006xd-00
	for l3vpn-web-archive@ietf.org; Mon, 17 Nov 2003 09:08:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALk2q-0008QH-Ot; Mon, 17 Nov 2003 09:08:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALk2O-0008IR-1C
	for l3vpn@optimus.ietf.org; Mon, 17 Nov 2003 09:07:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12097
	for <l3vpn@ietf.org>; Mon, 17 Nov 2003 09:07:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALk2M-0006xJ-00
	for l3vpn@ietf.org; Mon, 17 Nov 2003 09:07:30 -0500
Received: from [203.197.140.35] (helo=fsnt.future.futsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALk2K-0006wl-00
	for l3vpn@ietf.org; Mon, 17 Nov 2003 09:07:29 -0500
Received: from kailash.future.futsoft.com (unverified [203.197.140.36]) by 
    fsnt.future.futsoft.com (Content Technologies SMTPRS 4.3.6) with ESMTP id 
    <T65f796427fcbc58c235a8@fsnt.future.futsoft.com> for <l3vpn@ietf.org>; 
    Mon, 17 Nov 2003 19:31:56 +0530
Received: from sakthivss (sakthivss.future.futsoft.com [10.6.4.130]) by 
    kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id hAHDth320155 for 
    <l3vpn@ietf.org>; Mon, 17 Nov 2003 19:25:43 +0530
Reply-To: <sakthivss@future.futsoft.com>
From: "Sakthivadivu.S.S" <sakthivss@future.futsoft.com>
To: <l3vpn@ietf.org>
Subject: Route Targets from CE
Date: Mon, 17 Nov 2003 19:28:51 +0530
Message-ID: <000d01c3ad12$eec350a0$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 V6.00.2800.1106
Importance: Normal
In-Reply-To: <20031114091701.73627.qmail@web25101.mail.ukl.yahoo.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,

   Section 4.3.1 of BGP/MPLS 2547.draft says that

  " If the PE and the CE are themselves BGP peers (see section 7), then
   the SP may allow the customer, within limits, to specify how its
   routes are to be distributed.  The SP and the customer would need to
   agree in advance on the set of RTs which are allowed to be attached
   to the customer's VPN routes.  The CE could then attach one or more
   of those RTs to each IP route which it distributes to the PE.  This
   gives the customer the freedom to specify in real time, within agreed
   upon limits, its route distribution policies.  If the CE is allowed
   to attach RTs to its routes, the PE MUST filter out all routes which
   contain RTs that the customer is not allowed to use.  If the CE is
   not allowed to attach RTs to its routes, but does so anyway, the PE
   MUST remove the RT before converting the customer's route to a VPN-
   IPv4 route. "


   Can you please temm me how can SP and customer agrree for some Route
Target's.?

   Is there any configuration of Route targets in PE and CE for this.?

Regards,
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  Mon Nov 17 15:39:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03881
	for <l3vpn-archive@odin.ietf.org>; Mon, 17 Nov 2003 15:39:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALq9H-0004br-VZ
	for l3vpn-archive@odin.ietf.org; Mon, 17 Nov 2003 15:39:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAHKd3b8017713
	for l3vpn-archive@odin.ietf.org; Mon, 17 Nov 2003 15:39:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALq9H-0004bc-Ra
	for l3vpn-web-archive@optimus.ietf.org; Mon, 17 Nov 2003 15:39:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03855
	for <l3vpn-web-archive@ietf.org>; Mon, 17 Nov 2003 15:38:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALq9G-0005nh-00
	for l3vpn-web-archive@ietf.org; Mon, 17 Nov 2003 15:39:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALq9G-0005ne-00
	for l3vpn-web-archive@ietf.org; Mon, 17 Nov 2003 15:39:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALq9E-0004b1-Td; Mon, 17 Nov 2003 15:39:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALq8x-0004ad-UF
	for l3vpn@optimus.ietf.org; Mon, 17 Nov 2003 15:38:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03831
	for <l3vpn@ietf.org>; Mon, 17 Nov 2003 15:38:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALq8w-0005n5-00
	for l3vpn@ietf.org; Mon, 17 Nov 2003 15:38:42 -0500
Received: from web109.biz.mail.yahoo.com ([216.136.174.219])
	by ietf-mx with smtp (Exim 4.12)
	id 1ALq8v-0005n2-00
	for l3vpn@ietf.org; Mon, 17 Nov 2003 15:38:41 -0500
Message-ID: <20031117203841.73230.qmail@web109.biz.mail.yahoo.com>
Received: from [128.251.97.195] by web109.biz.mail.yahoo.com via HTTP; Mon, 17 Nov 2003 12:38:41 PST
Date: Mon, 17 Nov 2003 12:38:41 -0800 (PST)
From: Rick Wilder <rick@rhwilder.net>
Subject: minutes from the nov-12-03 L3VPN meeting 
To: l3vpn@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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>


Below are the minutes from the meeting in Minneapolis last week. Many thanks to Sue Hares
for taking notes at the meeting.

The presentation slides will appear in the proceedings.

Rick, Ron, and Ross

----------------------------------------------------------------------------------------

L3VPN Working Group
Wed 11/12/03 9:00am - 10:00am

Agenda:
	Agenda Bashing			(5 minutes - chairs)
	Working Group Document Status	(15 minutes -- Ross Callon)
	Charter: Ongoing/Future Work	(15 minutes - Ron Bonica)
	MPLS over L2TP			(15 minutes - mark Townsley)
	CE member authentication	(20 minutes)


1) Document status (Ross Callon) 

	L3 Framework <draft-ietf-l3vpn-framework-00.txt> 

		IESG has approved for publication

	L3 Service req'ts <draft-ietf-l3vpn-requirements-00.txt 

		IESG Review and/or update based on comments

	Generic req'ts <draft-ietf-ppvpn-generic-reqts-03.txt>

		IESG Review and/or update based on comments

	Security Framework

		Passed WG last call; 
		Being updated based on security directorate comments

	BGP/MPLS IP VPNs  and  AS 

		<draft-ietf-l3vpn-rfc2547bis-01.txt>,
		<draft-ietf-l3vpn-as2547-03.txt> 
		Passed l3vpn working group last call
		Is currently in IDR working group last call

	VR Architecture  and  AS

		<draft-ietf-l3vpn-vpn-vr-01.txt>  & <draft-ietf-l3vpn-as-vr-00.txt >
		Base document is ready for WG last call
		AS update expected soon after IETF
		Both should go to WG last call as soon as AS is ready

	CE/IPSec Architecture  and  AS 

		<draft-ietf-l3vpn-ce-based-01.txt> & 
		<draft-declercq-l3vpn-ce-based-as-00.txt>

		Recent update to address mailing list comments:

			Clarify CE operation in two distinct routing spaces and 
				management spaces
			More description of tunnel establishment 
			More description of Internet connectivity
			Awaiting update to AS

			Security considerations and template

		WG Last call expected soon

	Guidelines of Applicability Statements for PPVPNs

		<draft-ietf-l3vpn-applicability-guidelines-00.txt>
			
		Long term disposition is still tbd

	MPLS/BGP MIB  <draft-ietf-ppvpn-mpls-vpn-mib-05.txt> 

		Needs update & MIB Doctor review
		WG last call should occur relatively soon thereafter


	Virtual Router MIB  <draft-ietf-ppvpn-vr-mib-05.txt>

		same status as MPLS/BGP MIB

	CE MIB 
		TBD (do we need a MIB? - question to be addressed on mail list)

	Req'ts for MPLS MIBs <draft-lai-mpls-mib-rqmts-00.txt>   
		
		L3vpn issues have been resolved. 

	Framework for PPVPN Op. & Man.  <draft-ietf-l3vpn-mgt-fwk-00.txt> 

		Accepted as working group document at last IETF
		Comments to l3vpn mailing list


	Textual Conventions <draft-ietf-ppvpn-tc-mib-02.txt>

		"Very Stable". 


	2547 for IPv6 <draft-ietf-ppvpn-bgp-ipv6-vpn-03.txt>

		Charter is being updated to include IPv6
		
	PE-PE IPsec for 2547 <draft-ietf-ppvpn-ipsec-2547-03.txt>
	PE-PE GRE or IP for 2547 <draft-ietf-ppvpn-gre-ip-2547-02.txt> 
	BGP as Auto-Discovery  <draft-ietf-ppvpn-bgpvpn-auto-05.txt>

		All of above are stable, no significant recent updates

	CE-to-CE Member Verif'n 
		<draft-ietf-ppvpn-l3vpn-auth-03.txt> and 
		<draft-ietf-Behringer-mpls-vpn-auth>
	
		Possibility to reconcile the two approaches in a 
                single document - see below.

	OSPF as PE/CE Protocol in BGP/MPLS VPNs
		<draft-ietf-l3vpn-ospf-2547-00.txt> 

		Currently in WG last call
		Last call extended to 11/21/2003 (5pm EST)
	
		Related document <draft-ietf-ospf-2547-dnbit-01.txt> 
		in last call in the OSPF working group


2)  Charter (Ron Bonica) 
	
	We have made progress and are nearing completion of many of our
	original tasks (eg, Framework and Requirements Documents completed,
	Security Frameworks passed WG last call, BGP/MPLS base spec and AS
	passed l3vpn last call and are in IDR last call, ...). It is 	
	therefore a good time to think about future work. 

	We propose updating the Charter for additional work items. We have
	proposed to the IESG an update which adds support for IPv6. As the
	current set of documents is completed, we will propose to also add
	charter support for Multicast.


3) MPLS over L2TPv3 with BGP L3VPNs (Mark Townsley) 

	(see presentation)

	Proposal:  Edit current contribution to include BGP signaling along
	with L2TP formats. Use this to create a new document which could
	become draft-ietf-l3vpn-l2tpv3-2547-00.txt (if accepted as a working
	group document). 
		
	Note that this would be in addition to existing documents:

			draft-ietf-l3vnp-ipsec-2547-03.txt
			draft-ietf-l3vpn-gre-ip2547-00

	Discussion:
		1) Yakov: There were some comments in opposition to this when 	
		it was presented in MPLS. Security is an issue
			a) Security review is needed (by security directorate)
			b) Solution presented was not specific to L2TP.
                        c) justification needed for not using L2TP signaling
	
		2) Ross: Why do we need another encapsulation? We already have
		encapsulation over MPLS, GRE, and IPsec. Does this have an 
		advantage that these other encapsulations don't?
		
	   	(response) There are already 4 encapsulations
				MPLS over MPLS
				MPLS over IPsec
				MPLS over GRE
				MPLS over IP 
			
		(Eric Rosen) We already have many many different tunnel types
		in use in network. Service providers have preferences. We need
		a specification for each. 

		Agreement, we should include the reasons why the
		choices are being made.

	Mark: The intention is to update the document before it would be
	a working group document. 

   	Ross:  We can't accept a document as a working group document until 
	we have the document. Can you send an outline to the mailing list 
	with a description of what would be in the extended draft with the 
	articulation of the issues? 

	Mark: Yes, this makes sense.

	Agreement: Will be discussed on the list. 


3) Reconciling the L3VPN authentication Drafts
(also known as "Singing Kumbaya"),  M Behringer, M. Bonica
	
We currently have two drafts related to authentication (one a working 
group document, one an individual contribution):

		1) Draft-ietf-l3vpn-l3vpn-auth
			- provides the method through which the customers
			  can detect SP misconfiguration 
			- Does nothing to prevent misconfiguration
			- delegates authentication task to the CE
                        - requires new functionality on the CE

		2) Draft Behringer-mpls-vpn-auth
			- reduces the probabilty of SP misconfiguration
			- Does not allow customer to detect misconfiguration if 
			  it does occur
			- delegates the authentication task to the PE
                        - requires nothing new on the CE

		We have two drafts. Option are: merge, let them both live, kill one.
		We propose to merge the drafts. 
	
		Opportunity: 
			1) PE obtains the token from CE

			   original draft: BGP extended community received from CE
			   new protocol with CE
			   Hashed authentication key from CE-PE routing protocol
			
			2) PE distributes token throughout SP network

			3) PE 
				- Distribute to CE using BGP community or 
				  new protocol
				- User decides whether or not to authenticate

		Convergence:
			1) Converge on a common mechanisms for distribution
				- Use a new BGP attribute

			2) Add a third mechanism for obtaining token to 
			draft-ietf-l3vpn-l3vpn-auth
				= Drive the token from the PE-CE MD5 key

			3) Add a third application for the key at the egress PE
				- Use it to decide whether to install the route


	Discussion:  (Ross Callon) Reasonable to update document. Comments on 
		      the list. 
		    (Ron Bonica)  We would appreciate comments from Carrier's and
					   Service providers. 


4) Michael Beringer: <draft-behringer-mpls-security-04.txt>

He wants to know what the disposition will be of his document
"Analysis of the Security of BGP/MPLS IP VPNs". He requests
that people send comments on the draft to the mailing list. 

Ross: This makes sense. Please review the document to determine whether 
it should become a working group document with the intention of being 
published as Information. Send comments to the list. Requested that 
Michael send a message to the mail list requesting feedback on the 
beringer security draft. Michael agrees. 





From exim@www1.ietf.org  Mon Nov 17 15:53:24 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04294
	for <l3vpn-archive@odin.ietf.org>; Mon, 17 Nov 2003 15:53:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALqMr-00058Q-MB
	for l3vpn-archive@odin.ietf.org; Mon, 17 Nov 2003 15:53:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAHKr58c019738
	for l3vpn-archive@odin.ietf.org; Mon, 17 Nov 2003 15:53:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALqMr-00058H-EC
	for l3vpn-web-archive@optimus.ietf.org; Mon, 17 Nov 2003 15:53:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04282
	for <l3vpn-web-archive@ietf.org>; Mon, 17 Nov 2003 15:52:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALqMp-0005z4-00
	for l3vpn-web-archive@ietf.org; Mon, 17 Nov 2003 15:53:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALqMp-0005z1-00
	for l3vpn-web-archive@ietf.org; Mon, 17 Nov 2003 15:53:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALqMm-00057f-Mc; Mon, 17 Nov 2003 15:53:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALqM8-000577-UJ
	for l3vpn@optimus.ietf.org; Mon, 17 Nov 2003 15:52:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04258
	for <l3vpn@ietf.org>; Mon, 17 Nov 2003 15:52:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALqM7-0005yT-00
	for l3vpn@ietf.org; Mon, 17 Nov 2003 15:52:19 -0500
Received: from colo-dns-ext2.juniper.net ([207.17.137.64])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALqM6-0005xS-00
	for l3vpn@ietf.org; Mon, 17 Nov 2003 15:52:18 -0500
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext2.juniper.net (8.11.5/8.9.3) with ESMTP id hAHKowF99985;
	Mon, 17 Nov 2003 12:51:08 -0800 (PST)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id hAHKort06973;
	Mon, 17 Nov 2003 12:50:53 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200311172050.hAHKort06973@merlot.juniper.net>
To: Rick Wilder <rick@rhwilder.net>
cc: l3vpn@ietf.org
Subject: Re: minutes from the nov-12-03 L3VPN meeting 
In-Reply-To: Your message of "Mon, 17 Nov 2003 12:38:41 PST."
             <20031117203841.73230.qmail@web109.biz.mail.yahoo.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <37138.1069102253.1@juniper.net>
Date: Mon, 17 Nov 2003 12:50:53 -0800
From: Yakov Rekhter <yakov@juniper.net>
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>

Rick,

> Below are the minutes from the meeting in Minneapolis last week. Many thanks 
> to Sue Hares for taking notes at the meeting.

couple of corrections in-line...

> 3) MPLS over L2TPv3 with BGP L3VPNs (Mark Townsley) 
> 
> 	(see presentation)
> 
> 	Proposal:  Edit current contribution to include BGP signaling along
> 	with L2TP formats. Use this to create a new document which could
> 	become draft-ietf-l3vpn-l2tpv3-2547-00.txt (if accepted as a working
> 	group document). 
> 		
> 	Note that this would be in addition to existing documents:
> 
> 			draft-ietf-l3vnp-ipsec-2547-03.txt
> 			draft-ietf-l3vpn-gre-ip2547-00
> 
> 	Discussion:
> 		1) Yakov: There were some comments in opposition to this when 
> 		it was presented in MPLS. Security is an issue
> 			a) Security review is needed (by security directorate)
> 			b) Solution presented was not specific to L2TP.

What I said is that the solution is by no means specific to 2547 - 
it is applicable to any multipoint-to-point application.

>                       c) justification needed for not using L2TP signaling

What I said is that the document needs to explain why extending BGP 
for multipoint-to-point L2TP signaling is preferred to the existing L2TP 
signaling (or extending L2TP to provide multipoint-to-point signaling) ?

Yakov.




From exim@www1.ietf.org  Mon Nov 17 16:02:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04603
	for <l3vpn-archive@odin.ietf.org>; Mon, 17 Nov 2003 16:02:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALqVX-0005RV-GT
	for l3vpn-archive@odin.ietf.org; Mon, 17 Nov 2003 16:02:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAHL23ix020915
	for l3vpn-archive@odin.ietf.org; Mon, 17 Nov 2003 16:02:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALqVX-0005RG-Ac
	for l3vpn-web-archive@optimus.ietf.org; Mon, 17 Nov 2003 16:02:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04582
	for <l3vpn-web-archive@ietf.org>; Mon, 17 Nov 2003 16:01:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALqVV-00065F-00
	for l3vpn-web-archive@ietf.org; Mon, 17 Nov 2003 16:02:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALqVV-00065C-00
	for l3vpn-web-archive@ietf.org; Mon, 17 Nov 2003 16:02:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALqVV-0005Po-AK; Mon, 17 Nov 2003 16:02:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALqUo-0005P0-Hk
	for l3vpn@optimus.ietf.org; Mon, 17 Nov 2003 16:01:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04561
	for <l3vpn@ietf.org>; Mon, 17 Nov 2003 16:01:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALqUm-00064k-00
	for l3vpn@ietf.org; Mon, 17 Nov 2003 16:01:16 -0500
Received: from web108.biz.mail.yahoo.com ([216.136.174.218])
	by ietf-mx with smtp (Exim 4.12)
	id 1ALqUm-00064h-00
	for l3vpn@ietf.org; Mon, 17 Nov 2003 16:01:16 -0500
Message-ID: <20031117210115.26176.qmail@web108.biz.mail.yahoo.com>
Received: from [128.251.97.195] by web108.biz.mail.yahoo.com via HTTP; Mon, 17 Nov 2003 13:01:15 PST
Date: Mon, 17 Nov 2003 13:01:15 -0800 (PST)
From: Rick Wilder <rick@rhwilder.net>
Subject: Re: minutes from the nov-12-03 L3VPN meeting 
To: Yakov Rekhter <yakov@juniper.net>, Rick Wilder <rick@rhwilder.net>
Cc: l3vpn@ietf.org
In-Reply-To: <200311172050.hAHKort06973@merlot.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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>


Yakov,

OK. I will make those updates for the proceedings.

Rick

--- Yakov Rekhter <yakov@juniper.net> wrote:
> Rick,
> 
> > Below are the minutes from the meeting in Minneapolis last week. Many thanks 
> > to Sue Hares for taking notes at the meeting.
> 
> couple of corrections in-line...
> 
> > 3) MPLS over L2TPv3 with BGP L3VPNs (Mark Townsley) 
> > 
> > 	(see presentation)
> > 
> > 	Proposal:  Edit current contribution to include BGP signaling along
> > 	with L2TP formats. Use this to create a new document which could
> > 	become draft-ietf-l3vpn-l2tpv3-2547-00.txt (if accepted as a working
> > 	group document). 
> > 		
> > 	Note that this would be in addition to existing documents:
> > 
> > 			draft-ietf-l3vnp-ipsec-2547-03.txt
> > 			draft-ietf-l3vpn-gre-ip2547-00
> > 
> > 	Discussion:
> > 		1) Yakov: There were some comments in opposition to this when 
> > 		it was presented in MPLS. Security is an issue
> > 			a) Security review is needed (by security directorate)
> > 			b) Solution presented was not specific to L2TP.
> 
> What I said is that the solution is by no means specific to 2547 - 
> it is applicable to any multipoint-to-point application.
> 
> >                       c) justification needed for not using L2TP signaling
> 
> What I said is that the document needs to explain why extending BGP 
> for multipoint-to-point L2TP signaling is preferred to the existing L2TP 
> signaling (or extending L2TP to provide multipoint-to-point signaling) ?
> 
> Yakov.
> 





From exim@www1.ietf.org  Wed Nov 26 14:20:24 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22598
	for <l3vpn-archive@odin.ietf.org>; Wed, 26 Nov 2003 14:20:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP5Cp-0002LQ-2X
	for l3vpn-archive@odin.ietf.org; Wed, 26 Nov 2003 14:20:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAQJK6rj009006
	for l3vpn-archive@odin.ietf.org; Wed, 26 Nov 2003 14:20:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP5Cn-0002LB-Vo
	for l3vpn-web-archive@optimus.ietf.org; Wed, 26 Nov 2003 14:20:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22576
	for <l3vpn-web-archive@ietf.org>; Wed, 26 Nov 2003 14:19:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP5Cl-0003AO-00
	for l3vpn-web-archive@ietf.org; Wed, 26 Nov 2003 14:20:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP5Cl-0003AJ-00
	for l3vpn-web-archive@ietf.org; Wed, 26 Nov 2003 14:20:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP5Cj-0002KL-Sh; Wed, 26 Nov 2003 14:20:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOjf8-0005Yf-He
	for l3vpn@optimus.ietf.org; Tue, 25 Nov 2003 15:19:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07319
	for <l3vpn@ietf.org>; Tue, 25 Nov 2003 15:19:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOjf7-0004pJ-00
	for l3vpn@ietf.org; Tue, 25 Nov 2003 15:19:53 -0500
Received: from gwnj8.utstar.com ([65.200.123.8] helo=lxmail.xebeo.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1AOjf6-0004oh-00
	for l3vpn@ietf.org; Tue, 25 Nov 2003 15:19:52 -0500
Received: (qmail 15071 invoked by uid 404); 25 Nov 2003 20:19:23 -0000
Received: from rohit@utstar.com by lxmail by uid 401 with qmail-scanner-1.20rc1 
 (clamscan: 0.60. spamassassin: 2.55.  Clear:RC:1:. 
 Processed in 0.390092 secs); 25 Nov 2003 20:19:23 -0000
Received: from bigbird.nj.us.utstar.com (172.16.36.21)
  by lxmail.nj.us.utstar.com with SMTP; 25 Nov 2003 20:19:22 -0000
Received: from utstar.com (localhost.localdomain [127.0.0.1])
	by bigbird.nj.us.utstar.com (8.9.3/8.9.3) with ESMTP id PAA18654;
	Tue, 25 Nov 2003 15:19:22 -0500
Message-Id: <200311252019.PAA18654@bigbird.nj.us.utstar.com>
To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>, l3vpn@ietf.org
cc: rcallon@juniper.net, erosen@CISCO.COM
Subject: Re: Working Group Last Call for draft-ietf-ospf-2547-dnbit-01.txt to both lists 
In-Reply-To: Your message of "Wed, 29 Oct 2003 13:50:05 EST."
             <200310291850.NAA25555@bigbird.nj.us.utstar.com> 
Date: Tue, 25 Nov 2003 15:19:22 -0500
From: Rohit Dube <rohit@utstar.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>


The last call for this draft has ended. Comments received on the list
will be incorporated into the next rev., before it goes to the ADs for
review.

--rohit.




