From l3vpn-bounces@ietf.org Mon Jun 12 14:06:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fpqni-0007Rj-J9; Mon, 12 Jun 2006 14:06:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fpqnh-0007RZ-V2
	for l3vpn@ietf.org; Mon, 12 Jun 2006 14:06:09 -0400
Received: from borg.juniper.net ([207.17.137.119])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fpqng-0002R8-Mq
	for l3vpn@ietf.org; Mon, 12 Jun 2006 14:06:09 -0400
Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37])
	by borg.juniper.net with ESMTP; 12 Jun 2006 11:06:09 -0700
X-IronPort-AV: i="4.05,228,1146466800"; 
	d="scan'208"; a="558641180:sNHT26960768"
Received: from [172.25.42.216] ([172.25.42.216] RDNS failed) by
	proton.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Jun 2006 14:06:07 -0400
Message-ID: <448DAD0C.9010900@juniper.net>
Date: Mon, 12 Jun 2006 14:06:04 -0400
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: l3vpn@ietf.org
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Jun 2006 18:06:07.0859 (UTC)
	FILETIME=[E0E6E430:01C68E4A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Subject: Delivering MPLS Services over L3VPN
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
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>
Errors-To: l3vpn-bounces@ietf.org

Folks,

Please review a draft at the following URL:

http://www.ietf.org/internet-drafts/draft-bonica-mplsvpn-00.txt

                                  /as individual contributor
                                  Ron



Abstract

   This document describes procedures that can be used to deliver MPLS
   services over Layer 3 Virtual Private Networks (L3VPN).  Using these
   procedures, a VPN customer can signal MPLS Label Switched Paths (LSP)
   from Customer Edge (CE) router to CE router.  Although a Service
   Provider (SP) network carries the Customer LSP (C-LSP) from one CE
   router to another, the C-LSP does not interact with the SP network's
   routing or signaling infrastructure.




From l3vpn-bounces@ietf.org Wed Jun 14 10:42:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FqWZ8-0001oU-Nn; Wed, 14 Jun 2006 10:41:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fp078-00073Y-2W; Sat, 10 Jun 2006 05:50:42 -0400
Received: from szxga02-in.huawei.com ([61.144.161.54] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fp076-0006FY-6P; Sat, 10 Jun 2006 05:50:42 -0400
Received: from huawei.com (szxga02-in [172.24.2.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J0N00H2G2P4U5@szxga02-in.huawei.com>; Sat,
	10 Jun 2006 18:05:28 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J0N00EZY2P3ZU@szxga02-in.huawei.com>; Sat,
	10 Jun 2006 18:05:27 +0800 (CST)
Received: from z52048 ([10.164.5.62])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0J0N00I5M20P51@szxml03-in.huawei.com>; Sat,
	10 Jun 2006 17:50:57 +0800 (CST)
Date: Sat, 10 Jun 2006 17:49:37 +0800
From: Zheng Hewen <hwzheng@huawei.com>
To: mpls@ietf.org
Message-id: <000001c68c73$32b72970$3e05a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: TEXT/PLAIN
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
X-Mailman-Approved-At: Wed, 14 Jun 2006 10:41:53 -0400
Cc: ccamp@ops.ietf.org, l3vpn@ietf.org
Subject: [MPLS]Suggestion to discover and distribute multicast membership for
 P2MP automatically and dynamically
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
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>
Errors-To: l3vpn-bounces@ietf.org


Hi,

The signaling solution for the construction of P2MP MPLS-TE LSPs defined in draft-ietf-mpls-rsvp-te-p2mp-05.txt assumes that 
the ingress node for any P2MP LSP knows the identities of all of the receivers. No mechanism in that document is provided by 
which it can discover the identities of those receivers.

In multicast LDP (mLDP) defined in draft-ietf-mpls-ldp-p2mp-00.txt it is assumed that each receiver knows the identity of 
the source of the distribution tree, but no mechanism is provided whereby the receivers can discover that information.

In order to successfully operate P2MP MPLS, and to consider extending MPLS to support MP2MP it is necessary to examine
the requirements for exchanging and learning the identities of P2MP roots and leaves. One mechanism is desired to discover 
and distribute multicast membership information dynamically.

Currently some work is in progress. For L3VPN applications, it is one choice to carry and distribute multicast membership 
information through auto-discovery mechanism based on extended BGP defined in the 
draft-raggarwa-l3vpn-2547bis-mcast-bgp-01.txt. For P2MP MPLS-TE applications, one effort is to extend IGP-TE for such 
purpose using one analogous mechanism defined in draft-ietf-ccamp-te-node-cap-01.txt. For connection-oriented transport 
network basing on MPLS, one mechanism defined in RFC2022 may be referred. Extension to MSDP is another choice to satisfy 
those requirements directly if possible.

It is desired to clear the requirements for that mechanism. Is there any interest for this? I want to do something about it 
and hope to receive advices.


Best Regards,
Heaven







From l3vpn-bounces@ietf.org Tue Jun 20 12:08:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fsim4-0005am-QO; Tue, 20 Jun 2006 12:08:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fsim1-0005Za-K3
	for l3vpn@ietf.org; Tue, 20 Jun 2006 12:08:17 -0400
Received: from borg.juniper.net ([207.17.137.119])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsihU-0001vl-7w
	for l3vpn@ietf.org; Tue, 20 Jun 2006 12:03:37 -0400
Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37])
	by borg.juniper.net with ESMTP; 20 Jun 2006 09:03:36 -0700
X-IronPort-AV: i="4.06,156,1149490800"; 
	d="scan'208"; a="561094983:sNHT25998748"
Received: from [172.25.51.53] ([172.25.51.53] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 20 Jun 2006 12:03:35 -0400
Message-ID: <44981C54.7030309@juniper.net>
Date: Tue, 20 Jun 2006 12:03:32 -0400
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: l3vpn@ietf.org
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Jun 2006 16:03:35.0151 (UTC)
	FILETIME=[15A6AFF0:01C69483]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Subject: IETF 66
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
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>
Errors-To: l3vpn-bounces@ietf.org

Folks,

So far, we have three requests for agenda time at IETF 66. These are:

- Rahul Aggarwal and Eric Rosen (Multicast)
- Kenji Kumaki (MPLS over L3VPN Reqts)
- Ron Bonica (MPLS over L3VPN Arch)

If there are any other requests for agenda time, please send them to
Rick and I ASAP.

                            Ron




From l3vpn-bounces@ietf.org Wed Jun 21 09:35:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ft2rW-0004Xg-3K; Wed, 21 Jun 2006 09:35:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ft1rh-00068H-2F
	for l3vpn@ietf.org; Wed, 21 Jun 2006 08:31:25 -0400
Received: from webmail-outgoing.us4.outblaze.com ([205.158.62.67])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ft1rf-0006eP-LW
	for l3vpn@ietf.org; Wed, 21 Jun 2006 08:31:25 -0400
Received: from unknown (unknown [192.168.9.180])
	by webmail-outgoing.us4.outblaze.com (Postfix) with QMQP id
	65DE11801115
	for <l3vpn@ietf.org>; Wed, 21 Jun 2006 12:31:22 +0000 (GMT)
X-OB-Received: from unknown (205.158.62.81)
	by wfilter.us4.outblaze.com; 21 Jun 2006 12:30:40 -0000
Received: by ws1-2.us4.outblaze.com (Postfix, from userid 1001)
	id ADA9A1F50B1; Wed, 21 Jun 2006 12:31:19 +0000 (GMT)
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary="_----------=_115089307912010"
MIME-Version: 1.0
From: "Arut Selvan" <arut@techie.com>
To: l3vpn@ietf.org
Date: Wed, 21 Jun 2006 07:31:19 -0500
Received: from [203.126.136.220] by ws1-2.us4.outblaze.com with http for
	arut@techie.com; Wed, 21 Jun 2006 07:31:19 -0500
X-Originating-Ip: 203.126.136.220
X-Originating-Server: ws1-2.us4.outblaze.com
Message-Id: <20060621123119.ADA9A1F50B1@ws1-2.us4.outblaze.com>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
X-Mailman-Approved-At: Wed, 21 Jun 2006 09:35:17 -0400
Subject: PIMv2 changes for multicast vpn
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
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>
Errors-To: l3vpn-bounces@ietf.org

This is a multi-part message in MIME format.

--_----------=_115089307912010
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

Hi,

I would like to know the changes that may be required to existing PIMv2
protocol to
adapt to a multicast VPN. Kindly comment...

I went thru draft-rosen-vpn-mcast-08.txt, but couldn't figure out the PIM
protocol changes

needed

asm

--=20
___________________________________________________
Play 100s of games for FREE! http://games.mail.com/


--_----------=_115089307912010
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="iso-8859-1"

<P>Hi,</P>
<P>I would like to know the changes that may be required to existing PIMv2 =
protocol to<BR>adapt to a multicast VPN. Kindly comment... </P>
<P>I went thru draft-rosen-vpn-mcast-08.txt, but couldn't figure out the PI=
M protocol changes</P>
<P>needed</P>
<P>asm</P><BR>

--=20
<p>___________________________________________________<br>Play 100s of game=
s for FREE! <a href=3D"http://games.mail.com/" target=3D"_blank">http://gam=
es.mail.com/</a></p>

--_----------=_115089307912010--





From l3vpn-bounces@ietf.org Wed Jun 21 14:33:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ft7Vv-0000GC-66; Wed, 21 Jun 2006 14:33:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ft7Vu-0000G7-7T
	for l3vpn@ietf.org; Wed, 21 Jun 2006 14:33:18 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ft7Vs-0002CL-S4
	for l3vpn@ietf.org; Wed, 21 Jun 2006 14:33:18 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-5.cisco.com with ESMTP; 21 Jun 2006 11:33:16 -0700
X-IronPort-AV: i="4.06,163,1149490800"; 
	d="scan'208,217"; a="298682140:sNHT45449416"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id k5LIXGLq005687; 
	Wed, 21 Jun 2006 11:33:16 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k5LIXFke018485;
	Wed, 21 Jun 2006 11:33:16 -0700 (PDT)
Received: from xmb-sjc-216.amer.cisco.com ([171.70.151.184]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Wed, 21 Jun 2006 11:33:15 -0700
Received: from [128.107.163.78] ([128.107.163.78]) by
	xmb-sjc-216.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Wed, 21 Jun 2006 11:33:15 -0700
In-Reply-To: <20060621123119.ADA9A1F50B1@ws1-2.us4.outblaze.com>
References: <20060621123119.ADA9A1F50B1@ws1-2.us4.outblaze.com>
Mime-Version: 1.0 (Apple Message framework v750)
Content-Type: multipart/alternative; boundary=Apple-Mail-2-808861159
Message-Id: <6CE006A6-47DD-48DA-9476-DBCBAB57DC61@cisco.com>
From: Yiqun Cai <ycai@cisco.com>
Date: Wed, 21 Jun 2006 11:32:32 -0700
To: Arut Selvan <arut@techie.com>
X-Mailer: Apple Mail (2.750)
X-OriginalArrivalTime: 21 Jun 2006 18:33:15.0519 (UTC)
	FILETIME=[28C7D8F0:01C69561]
DKIM-Signature: a=rsa-sha1; q=dns; l=2365; t=1150914796; x=1151778796;
	c=relaxed/simple; s=sjdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=ycai@cisco.com; z=From:Yiqun=20Cai=20<ycai@cisco.com>
	|Subject:Re=3A=20PIMv2=20changes=20for=20multicast=20vpn;
	X=v=3Dcisco.com=3B=20h=3DO9WcaAGnamakSr3K86nxarvA/Ak=3D;
	b=Wpm9Nt0yIqxo8gaFzK/3TfEuI1ZGJGO7WDyElcgMV2cubm9oc/mq2O1AKzQiSsQdfzs2rSoI
	GCpMzE7bgQl3wTaX7+4tcZtvnTUpZP/Lg3m+KUNakjOKqwURktrxkLYw;
Authentication-Results: sj-dkim-2.cisco.com; header.From=ycai@cisco.com;
	dkim=pass (
	28 extraneous bytes; sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: l3vpn@ietf.org
Subject: Re: PIMv2 changes for multicast vpn
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
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>
Errors-To: l3vpn-bounces@ietf.org


--Apple-Mail-2-808861159
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

This draft does not require any change in the PIM protocol.


On Jun 21, 2006, at 5:31 AM, Arut Selvan wrote:

> Hi,
>
> I would like to know the changes that may be required to existing  
> PIMv2 protocol to
> adapt to a multicast VPN. Kindly comment...
>
> I went thru draft-rosen-vpn-mcast-08.txt, but couldn't figure out  
> the PIM protocol changes
>
> needed
>
> asm
>
>
> --
> ___________________________________________________
> Play 100s of games for FREE! http://games.mail.com/


--
Yiqun




--Apple-Mail-2-808861159
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=US-ASCII

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">This draft does not require any =
change in the PIM protocol.<DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV><BR><DIV><DIV>On Jun 21, =
2006, at 5:31 AM, Arut Selvan wrote:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE =
type=3D"cite"><P>Hi,</P><P>I would like to know the changes that may be =
required to existing PIMv2 protocol to<BR>adapt to a multicast VPN. =
Kindly comment... </P><P>I went thru draft-rosen-vpn-mcast-08.txt, but =
couldn't figure out the PIM protocol =
changes</P><P>needed</P><P>asm</P><BR> -- =
<P>___________________________________________________<BR>Play 100s of =
games for FREE! <A href=3D"http://games.mail.com/" =
target=3D"_blank">http://games.mail.com/</A></P></BLOCKQUOTE></DIV><BR><DI=
V> <SPAN class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Lucida =
Grande; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: =
0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>--</DIV><DIV>Yiqun</DIV><DIV>=
<BR class=3D"khtml-block-placeholder"></DIV><BR =
class=3D"Apple-interchange-newline"></SPAN> =
</DIV><BR></DIV></BODY></HTML>=

--Apple-Mail-2-808861159--




From l3vpn-bounces@ietf.org Thu Jun 22 13:15:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtSmB-0005eM-7n; Thu, 22 Jun 2006 13:15:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtSmA-0005eG-7W
	for l3vpn@ietf.org; Thu, 22 Jun 2006 13:15:30 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtSm8-0001Wz-UJ
	for l3vpn@ietf.org; Thu, 22 Jun 2006 13:15:30 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-5.cisco.com with ESMTP; 22 Jun 2006 10:15:28 -0700
X-IronPort-AV: i="4.06,166,1149490800"; 
	d="scan'208"; a="299311674:sNHT32466264"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id k5MHFSMO004907; 
	Thu, 22 Jun 2006 10:15:28 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k5MHFR9u009345;
	Thu, 22 Jun 2006 10:15:28 -0700 (PDT)
Received: from xmb-sjc-216.amer.cisco.com ([171.70.151.184]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Thu, 22 Jun 2006 10:15:27 -0700
Received: from [128.107.163.78] ([128.107.163.78]) by
	xmb-sjc-216.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Thu, 22 Jun 2006 10:15:27 -0700
In-Reply-To: <20060622053739.ED8181642C6@ws1-4.us4.outblaze.com>
References: <20060622053739.ED8181642C6@ws1-4.us4.outblaze.com>
Mime-Version: 1.0 (Apple Message framework v750)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <719ED7AF-85AF-4E21-92E7-575B19CB575B@cisco.com>
Content-Transfer-Encoding: 7bit
From: Yiqun Cai <ycai@cisco.com>
Date: Thu, 22 Jun 2006 10:14:43 -0700
To: Arut Selvan <arut@techie.com>
X-Mailer: Apple Mail (2.750)
X-OriginalArrivalTime: 22 Jun 2006 17:15:27.0568 (UTC)
	FILETIME=[74E0CD00:01C6961F]
DKIM-Signature: a=rsa-sha1; q=dns; l=623; t=1150996528; x=1151860528;
	c=relaxed/simple; s=sjdkim1001; h=From:Subject;
	d=cisco.com; i=ycai@cisco.com; z=From:Yiqun=20Cai=20<ycai@cisco.com>
	|Subject:Re=3A=20PIMv2=20changes=20for=20multicast=20vpn;
	X=v=3Dcisco.com=3B=20h=3DcSf3ru2JWJaBgMCCC3r5z6+AG9s=3D;
	b=vJ4RTnXl4TJPd/nXuMbaJSygbHhLI+PIR5OpFcRria3/wCHrZKmT9ti29ksgC38S7Z+ioqUG
	siL4DuBgy4eNyWaLnhf+1HLeYxotRG35EkX5OdQhN8zBcvLDZ5Fv1rlb;
Authentication-Results: sj-dkim-1.cisco.com; header.From=ycai@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: l3vpn@ietf.org
Subject: Re: PIMv2 changes for multicast vpn
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
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>
Errors-To: l3vpn-bounces@ietf.org

The draft you referred to doesn't require any change in the PIM  
protocol to carry information about which VPN (or VRF) a Join/Prune  
is intended for.

The implementation on a PE router is responsible to populate the  
multicast routing table upon receiving and processing the PIM packets.

On Jun 21, 2006, at 10:37 PM, Arut Selvan wrote:

> Hello Yiqun,
>
> I was referring to the changes required to PIM-SM if operating in a  
> VPN environment.
>
> Shouldn't PIM be VPN aware bcos the multicast routes would be  
> populated based on
>
> a the VPN the route belongs to ?
>
> -- asm


--
Yiqun






From l3vpn-bounces@ietf.org Mon Jun 26 15:18:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fuwb7-0002Po-6F; Mon, 26 Jun 2006 15:18:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fuwb0-00026W-7W; Mon, 26 Jun 2006 15:18:06 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fuwb0-0004bz-59; Mon, 26 Jun 2006 15:18:06 -0400
Received: from nit.isi.edu ([128.9.160.116])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1FuwaS-00038e-IK; Mon, 26 Jun 2006 15:17:35 -0400
Received: from nit.isi.edu (loopback [127.0.0.1])
	by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k5QJHTsb023341; 
	Mon, 26 Jun 2006 12:17:29 -0700
Received: (from apache@localhost)
	by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k5QJHTFq023340;
	Mon, 26 Jun 2006 12:17:29 -0700
Date: Mon, 26 Jun 2006 12:17:29 -0700
Message-Id: <200606261917.k5QJHTFq023340@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -17.6 (-----------------)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: l3vpn@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4577 on OSPF as the Provider/Customer Edge Protocol for
	BGP/MPLS IP Virtual Private Networks (VPNs)
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
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>
Errors-To: l3vpn-bounces@ietf.org


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4577

        Title:      OSPF as the Provider/Customer Edge 
                    Protocol for BGP/MPLS IP Virtual Private 
                    Networks (VPNs) 
        Author:     E. Rosen, P. Psenak,
                    P. Pillay-Esnault
        Status:     Standards Track
        Date:       June 2006
        Mailbox:    erosen@cisco.com, 
                    ppsenak@cisco.com, 
                    ppe@cisco.com
        Pages:      25
        Characters: 61515
        Updates:    RFC4364
        See-Also:   

        I-D Tag:    draft-ietf-l3vpn-ospf-2547-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4577.txt

Many Service Providers offer Virtual Private Network (VPN) services
to their customers, using a technique in which customer edge routers
(CE routers) are routing peers of provider edge routers (PE
routers).  The Border Gateway Protocol (BGP) is used to distribute
the customer's routes across the provider's IP backbone network, and
Multiprotocol Label Switching (MPLS) is used to tunnel customer
packets across the provider's backbone.  This is known as a "BGP/MPLS
IP VPN".  The base specification for BGP/MPLS IP VPNs presumes that
the routing protocol on the interface between a PE router and a CE
router is BGP.  This document extends that specification by allowing
the routing protocol on the PE/CE interface to be the Open Shortest
Path First (OSPF) protocol.

This document updates RFC 4364.  [STANDARDS TRACK]

This document is a product of the Layer 3 Virtual Private Networks
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of 
the Internet Official Protocol Standards (STD 1) for the standardization 
state and status of this protocol.  Distribution of this memo is 
unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...






From l3vpn-bounces@ietf.org Mon Jun 26 23:39:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fv4Pf-0002K5-C5; Mon, 26 Jun 2006 23:38:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fv4Pd-0002GV-5j; Mon, 26 Jun 2006 23:38:53 -0400
Received: from ns.ft.solteria.net ([210.142.173.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fv4Pb-00033E-OE; Mon, 26 Jun 2006 23:38:53 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by ns.ft.solteria.net (Postfix) with ESMTP
	id 372CB38712; Tue, 27 Jun 2006 12:38:50 +0900 (JST)
Message-ID: <44A0A7EE.8060602@ft.solteria.net>
Date: Tue, 27 Jun 2006 12:37:18 +0900
From: "S.Matsushima" <satoru@ft.solteria.net>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Zheng Hewen <hwzheng@huawei.com>
References: <000001c68c73$32b72970$3e05a40a@china.huawei.com>
In-Reply-To: <000001c68c73$32b72970$3e05a40a@china.huawei.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: ccamp@ops.ietf.org, mpls@ietf.org, l3vpn@ietf.org
Subject: Re: [MPLS]Suggestion to discover and distribute multicast membership
 for P2MP automatically and dynamically
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
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>
Errors-To: l3vpn-bounces@ietf.org

Hi,


Agreed.
I think that it is good point.
Dynamic discover and membership distribution of p2mp LSP will be needed
to operate p2mp LSP in real networks.

Also, I would say that policy-based mechanism to establish p2mp LSP in per
LSP basis is needed.

In BGP P2MP solution, you can see some ideas to achieve
above requirements. Your interest and comment are welcome.


http://www3.ietf.org/proceedings/05nov/slides/mpls-3/sld1.htm


-03 version of this draft will appear soon.

--
Satoru Matsushima


Zheng Hewen wrote:
> Hi,
> 
> The signaling solution for the construction of P2MP MPLS-TE LSPs defined in draft-ietf-mpls-rsvp-te-p2mp-05.txt assumes that 
> the ingress node for any P2MP LSP knows the identities of all of the receivers. No mechanism in that document is provided by 
> which it can discover the identities of those receivers.
> 
> In multicast LDP (mLDP) defined in draft-ietf-mpls-ldp-p2mp-00.txt it is assumed that each receiver knows the identity of 
> the source of the distribution tree, but no mechanism is provided whereby the receivers can discover that information.
> 
> In order to successfully operate P2MP MPLS, and to consider extending MPLS to support MP2MP it is necessary to examine
> the requirements for exchanging and learning the identities of P2MP roots and leaves. One mechanism is desired to discover 
> and distribute multicast membership information dynamically.
> 
> Currently some work is in progress. For L3VPN applications, it is one choice to carry and distribute multicast membership 
> information through auto-discovery mechanism based on extended BGP defined in the 
> draft-raggarwa-l3vpn-2547bis-mcast-bgp-01.txt. For P2MP MPLS-TE applications, one effort is to extend IGP-TE for such 
> purpose using one analogous mechanism defined in draft-ietf-ccamp-te-node-cap-01.txt. For connection-oriented transport 
> network basing on MPLS, one mechanism defined in RFC2022 may be referred. Extension to MSDP is another choice to satisfy 
> those requirements directly if possible.
> 
> It is desired to clear the requirements for that mechanism. Is there any interest for this? I want to do something about it 
> and hope to receive advices.
> 
> 
> Best Regards,
> Heaven
> 
> 
> 
> 
> 
> 
> 





From l3vpn-bounces@ietf.org Tue Jun 27 16:01:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FvJk3-0003kt-0b; Tue, 27 Jun 2006 16:00:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FvJa3-0007Qt-0t; Tue, 27 Jun 2006 15:50:39 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=pine.neustar.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FvJa2-0001Qy-Ir; Tue, 27 Jun 2006 15:50:38 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by pine.neustar.com (8.12.8/8.12.8) with ESMTP id k5RJo3UA002956
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Tue, 27 Jun 2006 19:50:04 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FvJZT-0005JP-3n; Tue, 27 Jun 2006 15:50:03 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1FvJZT-0005JP-3n@stiedprstage1.ietf.org>
Date: Tue, 27 Jun 2006 15:50:03 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: l3vpn@ietf.org
Subject: I-D ACTION:draft-ietf-l3vpn-2547bis-mcast-02.txt 
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
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>
Errors-To: l3vpn-bounces@ietf.org

--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		: Multicast in MPLS/BGP IP VPNs
	Author(s)	: E. Rosen, R. Aggarwal
	Filename	: draft-ietf-l3vpn-2547bis-mcast-02.txt
	Pages		: 71
	Date		: 2006-6-27
	
In order for IP multicast traffic within a BGP/MPLS IP VPN (Virtual
   Private Network) to travel from one VPN site to another, special
   protocols and procedures must be implemented by the VPN Service
   Provider.  These protocols and procedures are specified in this
   document.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-2547bis-mcast-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-2547bis-mcast-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: <2006-6-27145334.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l3vpn-2547bis-mcast-02.txt

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

Content-Type: text/plain
Content-ID: <2006-6-27145334.I-D@ietf.org>


--OtherAccess--

--NextPart--





