From l3vpn-bounces@ietf.org Mon Jul 03 04:29:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FxJoA-0000I2-P8; Mon, 03 Jul 2006 04:29:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FxJoA-0000Hx-DI
	for l3vpn@ietf.org; Mon, 03 Jul 2006 04:29:30 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FxJo9-0003Sk-0M
	for l3vpn@ietf.org; Mon, 03 Jul 2006 04:29:30 -0400
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 3 Jul 2006 10:29:24 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 3 Jul 2006 10:29:22 +0200
Message-ID: <5A0FF108221C7C4E85738678804B567C0379FEFA@ftrdmel3.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Delivering MPLS Services over L3VPN
Thread-Index: AcaOSvnR5JGMDvoQRcGlAfs1AyW51gQLjqmA
From: "DECRAENE Bruno RD-CORE-ISS" <bruno.decraene@orange-ft.com>
To: "Ron Bonica" <rbonica@juniper.net>
X-OriginalArrivalTime: 03 Jul 2006 08:29:24.0822 (UTC)
	FILETIME=[CA8F3760:01C69E7A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: l3vpn@ietf.org
Subject: RE: 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

Ron,

That seems indeed a good idea.

Would you also consider an option where addresses of the VPN sites
(addresses of C0, C3...) would be distributed directly between CE though
iBGP sessions, without passing through PE?

I would see two advantages:
- This reduces the number of VPN routes on the PE, as this becomes a
significant scaling consideration in VPN networks. Both in the MP-BGP
control plane (on PE and RR) and in the PE forwarding plane (FIB
memory).
- The C-next-hop attribute is no more necessary.
(-it also reduces the number of MP-BGP updates since "Link-bandwidth"
updates are not anymore carried by the SP)


It does have disadvantages as:
- It requires additional iBGP sessions on the CE
- It requires a full mesh of iBGP sessions between CE (or the use of RR
by the customer). However the use of an iBGP full mesh as its advantage
as it increase route diversity which is useful for TE. (C3 could be
reached by CE2 and CE3 and it would be better if CE1 has the choice).

However, regarding the need for iBGP full mesh:
- The number of iBGP sessions would probably be significantly smaller
than the number of RSVP-TE sessions so it does no add that much load on
the CE
- The configuration burden (when adding a new VPN site) could be
addressed though auto-discovery (For example by adding a newly defined
BGP extended community ("BGP RR group A") attached to CE loopback
addresses advertised in BGP)


Would you consider both options in the draft?

Thanks,
Best regards,
Bruno

> -----Original Message-----
> From: Ron Bonica [mailto:rbonica@juniper.net]
> Sent: Monday, June 12, 2006 8:06 PM
> To: l3vpn@ietf.org
> Subject: Delivering MPLS Services over L3VPN
>=20
> Folks,
>=20
> Please review a draft at the following URL:
>=20
> http://www.ietf.org/internet-drafts/draft-bonica-mplsvpn-00.txt
>=20
>                                   /as individual contributor
>                                   Ron
>=20
>=20
>=20
> Abstract
>=20
>    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 Mon Jul 03 23:16:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FxbOb-0002Jc-Sg; Mon, 03 Jul 2006 23:16:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FxbOa-0002JT-PT
	for l3vpn@ietf.org; Mon, 03 Jul 2006 23:16:16 -0400
Received: from borg.juniper.net ([207.17.137.119])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FxbOW-00069N-H3
	for l3vpn@ietf.org; Mon, 03 Jul 2006 23:16:16 -0400
Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37])
	by borg.juniper.net with ESMTP; 03 Jul 2006 20:16:11 -0700
X-IronPort-AV: i="4.06,201,1149490800"; 
	d="scan'208"; a="564984591:sNHT26687574"
Received: from [172.23.1.77] ([172.23.1.77] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 3 Jul 2006 23:16:11 -0400
Message-ID: <44A9DD76.5010500@juniper.net>
Date: Mon, 03 Jul 2006 23:16:06 -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: 04 Jul 2006 03:16:11.0313 (UTC)
	FILETIME=[332B1210:01C69F18]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Subject: IETF 66 agenda
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,

A draft agenda for IETF 66 has been posted. If anyone else would like
time on the agenda, please send an email to the chairs privately.

                                Ron and Rick




From l3vpn-bounces@ietf.org Tue Jul 11 09:25:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G0IEq-0006yX-0d; Tue, 11 Jul 2006 09:25:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G0IEo-0006t0-8M
	for l3vpn@ietf.org; Tue, 11 Jul 2006 09:25:18 -0400
Received: from borg.juniper.net ([207.17.137.119])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0IEn-00062v-0w
	for l3vpn@ietf.org; Tue, 11 Jul 2006 09:25:18 -0400
Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37])
	by borg.juniper.net with ESMTP; 11 Jul 2006 06:25:16 -0700
X-IronPort-AV: i="4.06,227,1149490800"; 
	d="scan'208"; a="566928711:sNHT27459120"
Received: from [172.23.1.105] ([172.23.1.105] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 11 Jul 2006 09:25:15 -0400
Message-ID: <44B3A6B4.8070803@juniper.net>
Date: Tue, 11 Jul 2006 09:25:08 -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: 11 Jul 2006 13:25:15.0963 (UTC)
	FILETIME=[725E60B0:01C6A4ED]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Subject: looking for scribes
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,

We are looking for two people to volunteer as scribes at Monday's
meeting. We are also looking for a jabber scribe.

Any takers? Please....

                         Ron




From l3vpn-bounces@ietf.org Wed Jul 12 17:33:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G0mL4-0004zP-Lx; Wed, 12 Jul 2006 17:33:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G0mL3-0004zJ-DY
	for l3vpn@ietf.org; Wed, 12 Jul 2006 17:33:45 -0400
Received: from athena.kddi.com ([210.141.112.39] helo=UTMC1101.kddi.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0mL1-0005Pz-0Y
	for l3vpn@ietf.org; Wed, 12 Jul 2006 17:33:45 -0400
Received: from usjk1037 (unknown [10.5.16.67])
	by UTMC1101.kddi.com (Postfix) with SMTP id F0BD4229E
	for <l3vpn@ietf.org>; Thu, 13 Jul 2006 06:33:40 +0900 (JST)
Received: from localhost (localhost [127.0.0.1])
	by localhost.kddi.com (Postfix) with SMTP id 2432E1AFB
	for <l3vpn@ietf.org>; Thu, 13 Jul 2006 06:33:38 +0900 (JST)
Received: from UTMC1118.kddi.com (unknown [10.5.16.33])
	by UTMC1122.kddi.com (Postfix) with ESMTP id D53A11AE7;
	Thu, 13 Jul 2006 06:33:31 +0900 (JST)
Received: from [127.0.0.1] ([133.128.75.150] [133.128.75.150]) by
	post-ims.kddi.com with ESMTP; Thu, 13 Jul 2006 06:33:31 +0900
Date: Thu, 13 Jul 2006 06:33:27 +0900
From: Kenji Kumaki <ke-kumaki@kddi.com>
To: l3vpn@ietf.org
Message-Id: <20060713063210.6E2D.KE-KUMAKI@kddi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.21.03 [ja]
X-WAuditID: 0607130633380000026126
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: ke-kumaki@kddi.com
Subject: draft-kumaki-l3vpn-e2e-rsvp-te-reqts-01
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,

Please consider this I-D as a WG item.

http://www.ietf.org/internet-drafts/draft-kumaki-l3vpn-e2e-rsvp-te-reqts-01.txt

Thanks,
Kenji







From l3vpn-bounces@ietf.org Thu Jul 13 22:09:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G1D7T-0002uF-Et; Thu, 13 Jul 2006 22:09:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G0iM9-00066I-8K
	for l3vpn@ietf.org; Wed, 12 Jul 2006 13:18:37 -0400
Received: from [2001:200:601:12:230:48ff:fe22:3a84] (helo=mandala.kddilabs.jp)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0iDz-0006nL-1t
	for l3vpn@ietf.org; Wed, 12 Jul 2006 13:10:11 -0400
Received: from localhost (localhost [127.0.0.1])
	by mandala.kddilabs.jp (Postfix) with ESMTP id D618CEC8AF
	for <l3vpn@ietf.org>; Thu, 13 Jul 2006 02:10:08 +0900 (JST)
Received: from mail.cn.kddilabs.jp (yellow.lan.kddilabs.jp
	[2001:200:601:1a00::10])
	by mandala.kddilabs.jp (Postfix) with ESMTP id AE7A3EC88A
	for <l3vpn@ietf.org>; Thu, 13 Jul 2006 02:10:08 +0900 (JST)
Received: from [127.0.0.1] (c014.vpn.kddilabs.jp [172.19.87.14])
	by mail.cn.kddilabs.jp (Postfix) with ESMTP id BB9DD1E0002
	for <l3vpn@ietf.org>; Thu, 13 Jul 2006 02:10:07 +0900 (JST)
Message-ID: <44B52CD3.6040202@kddilabs.jp>
Date: Thu, 13 Jul 2006 02:09:39 +0900
From: Kenji Kumaki <ke-kumaki@kddilabs.jp>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: l3vpn@ietf.org
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
X-Mailman-Approved-At: Thu, 13 Jul 2006 22:09:29 -0400
Subject: draft-kumaki-l3vpn-e2e-rsvp-te-reqts-01
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,

Please consider this I-D as a WG item.

http://www.ietf.org/internet-drafts/draft-kumaki-l3vpn-e2e-rsvp-te-reqts-01.txt

Thanks,
Kenji





From l3vpn-bounces@ietf.org Sat Jul 15 21:35:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G1vXo-00034G-BS; Sat, 15 Jul 2006 21:35:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G1vXm-00033q-M3
	for l3vpn@ietf.org; Sat, 15 Jul 2006 21:35:38 -0400
Received: from borg.juniper.net ([207.17.137.119])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G1vXm-0003sk-2p
	for l3vpn@ietf.org; Sat, 15 Jul 2006 21:35:38 -0400
Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37])
	by borg.juniper.net with ESMTP; 15 Jul 2006 18:35:37 -0700
X-IronPort-AV: i="4.06,246,1149490800"; 
	d="txt'?scan'208"; a="568257548:sNHT60613996"
Received: from [172.23.1.85] ([172.23.1.85] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 15 Jul 2006 21:35:36 -0400
Message-ID: <44B997E3.2010709@juniper.net>
Date: Sat, 15 Jul 2006 21:35:31 -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: multipart/mixed; boundary="------------020700060000020907010002"
X-OriginalArrivalTime: 16 Jul 2006 01:35:36.0594 (UTC)
	FILETIME=[23270720:01C6A878]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5fb88b8381f3896aeacc5a021513237b
Subject: [Fwd: IETF66 L3VPN meeting minutes]
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.
--------------020700060000020907010002
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Folks,

Please review these minutes. If there are no objections, I will post
them on Friday.

                                    Ron


--------------020700060000020907010002
Content-Type: text/plain;
 name="l3vpn-minutes.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="l3vpn-minutes.txt"

Layer 3 Virtual Private Networks (Internet Area)

Friday, July 14, 2006
=======================

Chairs:
Rick Wilder <rick@rhwilder.net>
Ron Bonica  <rbonica@juniper.net>

Agenda:

Minutes: Steven Blake (slblake@petri-meat.com)
Chair (Ron) presents agenda

/* Note: didn't catch names of Y and W. */

09:00-09:10  Working Group Status - R. Bonica

Document status

Question on a document's desired track (which document?)
- Eric Rosen: informational
Proposal for MVPN MIB, went on back burner.  Authors have asked to make
it a wg draft (placeholder).  Consensus call on draft-sidea (sp)
Rahul ?: MIB is way off from the solution.

09:10-10:00  Multicast Solutions - E. Rosen
		draft-ietf-l3vpn-2547bis-mcast-02.txt
		draft-raggarwa-l3vpn-2547bis-mcast-bgp-02.txt

MVPN update
- progressing
- some sites receive-only, some transmit-only
Issues to discuss today
- Eliminating (S,G,R) prunes from BGP control plane
  - reduces state and complexity
  - two alternatives:
    - 1. MSDP-based
      - each C-RP talke MSDP to a PE
Comment Toerless Eckert: MSDP is only experimental
    - 2. Coordinated switch
      - CE switches to (S,G)
Comment Toerless: reemphasize that we shouldn't depend on MSDP (took five 
                  years to realize it wouldn't work).
Comment Yakov R: would it be better to use PIM register messages to get 
                 active sources?
Comment Rahul Aggarwal: proposal uses MSDP from CE-PE, and BGP source actives
                        from PE-P & PE-PE
    - both methods use BGP-based source active messages
Comment Eric R: PIM was experimental for 10 years
- Support for C-bidir trees (from enterprise)
  - assume unidirectional P-tunnels
  - PIM bi-dir has complex forwarding rules
  - choose one ingress PE for bidir tree
  - multi-AS C-bidir
- Use of MP2MP P-LSPs
  - intra-AS tunnels
    - for every mcast flow
      - single ingress PE designated transmitter (have procedure for this)
      - really a matter of aggregating p2mp tunnels into an mp2mp tunnel
      - dependency on work-in-progress in MPLS wg
Toerless: why do you need to identify where it is coming from?
Eric R: which is downstream, which is upstream?  If you don't, and there is
        not complete agreement as to the designated forwarder
	Toerless: sure, like LAN, not doing any strong RPF check in PIM, 
	don't need to know the "l2 identify" of the device.
Eric: PIM has 40 pages on selecting designated forwarder
Toerless: Only matters during DF election.  If this makes sense, it shouldn't 
          only apply to MVPN.
Eric: that was the original design choice, but there might be some period of
      time (during convergence) where two routers might think they are the
      DF.  BGP procedures might not converge fast enough.
Toerless: goes against IETF's decision for PIM standard
Thomas ?: we are not relying on dataplane procedures to prevent multiple
senders to sending downstream.  Only works as soon as all downstream PEs have
the same view of unicast routing.  Definitely a need to identify the sender
of the mcast traffic.
Toerless: what about bidir PIM?
Eric: Mcast tunnel?  Will work that out.
Y: PIM-SSM has check there already.  Don't know why you have to do this in 
PIM-SSM case.
Rahul: If you are using undir trees in the backbone, you already know the
       sender.
Toerless: if using GRE tunnels, you already know the sender.
  - MP2MP LSPs aggregating segments of inter-AS tunnels
    - inter-AS tunnels always p2mp
    - inter-AS segments of inter-AS tunnels are therefore inherently p2mp.
    - would like to aggregate these within an AS

Rahul Aggarwal presents:
- New auto-discovery (AD) route types
  - S-PMSI AD route
- Source Active AD route
  - used to advertise active source
- C-Multicast routing protocol
  - C-multicast route dampening described (prunes, joins, leaf AD routes)
  - C-mcast route aggregation (via RR and ASBR)
- Next steps 
  - procedures for MSDP or PIM Anycast RP between C-RP and PE based scheme
  - procedures for using BGP or RSVP-TE as the PE-CE protocol for Carrier's
    Carrier model (for future study)

10:00-10:15  Reqs for MPLS Services Over L3VPN - Kenji Kumaki (KDDI)
		draft-kumaki-l3vpn-e2e-rsvp-te-reqts-01
- Motivation
  - robust MPLS services to customers
    - can offer e2e paths using LDP
      - can't offer e2e paths using RSVP extensions
    - offer CE-CE TE LSPs with guaranteed BW
    - want VRF instances per-customer to avoid security issues
      - customer can't join SP's routing/MPLS signaling domain
- Reference model diagram
  - C-TE LSPs
  - P-TE LSPs (encapsulates C-TE LSPs)
- Reqs
  - C-TE LSPs over BGP/MPLS IP-VPN (carrier's carrier & basic BGP/MPLS IP-VPN)
- Changes from -00
  - added author Raymond Zhang
  - changed problem statement
  - changed terminology
  - added admission control support
- Other requirements?
- Next actions
  - need wg feedback
  - request wg accept ID
Andy Malis: premature to accept as wg document, need to discuss mor on the
            list
Mark Townsley: engage L1VPN as well
Kenji: motivation is l3vpn (already deployed)
Mark: question of review, see overlap, don't want to step on toes (because
      CEs are setting up LSPs), want to make sure not solving problem in two
      places.  PWE3 also talking about generic PW.  Several areas are reacting
      to this motivation (CE-originated LSPs).  Add "work with other wgs"
      in next-actions.
Yakov: L1VPN is optical LSPs only.  Should you recharter L1VPN to work on
       packet environment.
Mark: understand, but same control plane
Yakov: please recharter L1VPN
JP Vassur: Mark is right.  Is this part of the discussion in l3vpn?
Chair Rick: yes
Adrian Farrel: circulate this in other wgs
Kireeti: important that the mechanisms used be common (l3 service & l1 service)o
         can use common mechanisms.
Eric: Want a PW, need to find out CE router to peer with
Rahul: You want RSVP-TE for carrier's carrier, right?  carrier's carrier fits
       within scope of this wg.

10:15-10:30  Proposal for MPLS Services Over L3VPN - R. Bonica
		draft-bonica-mplsvpn-00

- Imagine L3VPN service provider
- Customer wants to purchase a customer LSP from C0 to C3.
- Problem: customer wants to use RSVP-TE to signal the LSP, but that
  won't work.
- Solution:
  - Carrier's carrier nearly solves the problem.  Build SP-LSP between
    PE1 and PE2, use BGP to advertise labeled paths between CE1 and CE2
  - Need to build LSP between C0-CE1 and CE2-C3, CE1-CE2 is a virtual path
- Challenges:
  - RSVP signal C0-CE1-CE2-C3
  - Make CE1 beleive that next-hop to C3 is CE2
    - not PE1
    - three proposed solutions
      - BGP next-hop attribute
      - iBGP
      - policy manipulation
  - Partial ERO calculation
    - C0-CE2
    - CE2-C3
  - TE considerations
    - C0 and C3 need to see CE1-CE2 LSP for TE purposes
- Questions?
Rahul: Think this is carrier's carrier.  Why doesn't it fit in the wg's
       charter?
Chair Rick: Think it does.  Packet-based CE-CE LSPs are in charter
Yakov: what new is required to implement this (on top of 2547)
Ron: from customers pov, nothing.  From SP's pov, need a few things (missed
them).
Yakov: policy doesn't require standards work.  Is it correct to say that the
only thing needed is a TE attribute, why do we need to recharter wg.
JP: Where do we do the work?
Yakov: in the bar
Kireeti: someone needs to provide the napkin
Eric: Does this depend on carrier's carrier.  Might not want carrier's carrier
      service.  Need to find the CE endpoint if not using carrier's carrier,
      need a mechanism.  Have you thought about multihoming?
Ron: Yes, but not presented here.
Kireeti: please show slide with two PE1s
         Emphasize that CE LSPs takes C0-CE1-CE2-C3, don't drop state in
	 PEs.
Ron: required that CEs cannot create RSVP state in PE routers
Kireeti: this is different from l1vpn, where they are dropping state in PEs.
         CE1-CE2 is a pseudo-TE path, depends on accuracy of TE info
	 propogated from PEs; PE1-PE2 LSP could be oversubscribed.
Ron: right
Kireeti: not a req that provider actually runs RSVP-TE
Rajeev Sari (sp?): might be missing the CE-PE link BW reservation
Ron: agreed
Lee Ann Phang (sp?): does this force provider to implement certain TE
                     mechanisms?
Rajeev: (missed comment)
Eric: why focus on TE?  could use LSP for anything.  Are the reqs focused on
      TE?
Ron: could expand reqs
Rajeev: has something like multi-hop RSVP been considered?
Ron: no
Rahul: it works today
Rajeev: has it been considered
Ron: no
Lee Ann: req needs to be more clear, what is the req for the SP.  SP must
         also promise to offer TE.
Yakov: 2547 allows customer to originate RSVP-TE request from CE1-PE1,
       will be propogated to PE2
Loa: security issues with running LSP across customer-SP border
Ron: traffic restricted to VPN sites of the same customer; cannot install
     state in SP network
Loa: not convinced, some malicious party in customer net could launch DoS,
     need to address this in security considerations
Lee Ann: if I offer carrier's carrier, then I am basically done.  If customer
         wants a TE LSP, then somthing additional needs to be done (protocol
	 change)
Ron: need to leak TE info
Yakov: been implemented by Cisco, part of communities, can spec different
       attribute
Ron: need to keak info in BGP
Rajeev: could be running IGP & LDP on PE-CE
Ron: must use BGP for carrier's carrier
Rajeev: no; works today
Ron: you're right
W: ask previous authors if the services discussed are the same (IP over LSP)
Kenji: provide both cases


Mark Townsley: WG charter needs updating in general.  Carrier's carrier not
  in charter, TE (QoS) is excluded.  AD will recharter.

Consensus call on this work item: do in this wg?
- favorable; confirm on mailing list, updating of charter

Meeting adjourned


--------------020700060000020907010002--




From l3vpn-bounces@ietf.org Tue Jul 25 10:17:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5NjM-0001hy-6W; Tue, 25 Jul 2006 10:17:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5NjK-0001hs-Aq
	for l3vpn@ietf.org; Tue, 25 Jul 2006 10:17:50 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5NjJ-0004Qs-4A
	for l3vpn@ietf.org; Tue, 25 Jul 2006 10:17:50 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 25 Jul 2006 10:17:49 -0400
X-IronPort-AV: i="4.07,179,1151899200"; 
	d="scan'208"; a="93819999:sNHT21444794"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k6PEHmmA031404; Tue, 25 Jul 2006 10:17:48 -0400
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k6PEHmdU016989; 
	Tue, 25 Jul 2006 10:17:48 -0400 (EDT)
Message-Id: <200607251417.k6PEHmdU016989@rtp-core-2.cisco.com>
To: l3vpn@ietf.org
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Tue, 25 Jul 2006 10:17:48 -0400
From: Eric Rosen <erosen@cisco.com>
DKIM-Signature: a=rsa-sha1; q=dns; l=435; t=1153837069; x=1154701069;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=erosen@cisco.com;
	z=From:Eric=20Rosen=20<erosen@cisco.com>
	|Subject:=22BGP=20Encodings=20for=20Multicast=20in=20MPLS/BGP=20IP=20VPNs=22
	|To:l3vpn@ietf.org;
	X=v=3Dcisco.com=3B=20h=3DoVcCeGvIf3SWzeZANm7kloahRPA=3D;
	b=IwwDRWW4LEDqv013Iaim+e8C0cPDAoujJ9b36DjpYHeiQqYY1jH9ykTnDkcm8L2EYO69DP1g
	PVIs0DFcmJh8gEE/NHDcfrCoeQmAt5vE85eMSlhCMWGhXbsuQcR1Z1yJ;
Authentication-Results: rtp-dkim-1.cisco.com; header.From=erosen@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Subject: "BGP Encodings for Multicast in MPLS/BGP IP VPNs"
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: erosen@cisco.com
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 internet  draft (draft-raggarwa-l3vpn-2548bis-mcast-bgp-02.txt) has now
been discussed  at several IETF meetings,  and is proceeding  well.  I think
it's time  to officially recognize it  as the basis for  the WG's continuing
work in this area by adopting it as a WG draft. 

I'd like to reqeust the WG chairs  to open a "last call" period to determine
whether there is WG consensus for adopting this draft as a WG draft. 




From l3vpn-bounces@ietf.org Tue Jul 25 10:20:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5NmM-0002SL-Iq; Tue, 25 Jul 2006 10:20:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5NmL-0002SG-DL
	for l3vpn@ietf.org; Tue, 25 Jul 2006 10:20:57 -0400
Received: from borg.juniper.net ([207.17.137.119])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5NmK-0005Ks-5S
	for l3vpn@ietf.org; Tue, 25 Jul 2006 10:20:57 -0400
Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37])
	by borg.juniper.net with ESMTP; 25 Jul 2006 07:20:56 -0700
X-IronPort-AV: i="4.07,179,1151910000"; 
	d="scan'208"; a="570974221:sNHT27703528"
Received: from [172.25.51.51] ([172.25.51.51] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 25 Jul 2006 10:20:59 -0400
Message-ID: <44C628C8.70006@juniper.net>
Date: Tue, 25 Jul 2006 10:20:56 -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: erosen@cisco.com
References: <200607251417.k6PEHmdU016989@rtp-core-2.cisco.com>
In-Reply-To: <200607251417.k6PEHmdU016989@rtp-core-2.cisco.com>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Jul 2006 14:20:59.0950 (UTC)
	FILETIME=[8D52CCE0:01C6AFF5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: l3vpn@ietf.org
Subject: Re: "BGP Encodings for Multicast in MPLS/BGP IP 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

Hi Eric,

I guess this is more of a first call than a last call ;-)

Anyway, does anyone have any strong opinions regarding whether this
draft should be accepted as a WG item?

                             -ron


Eric Rosen wrote:
> This internet  draft (draft-raggarwa-l3vpn-2548bis-mcast-bgp-02.txt) has now
> been discussed  at several IETF meetings,  and is proceeding  well.  I think
> it's time  to officially recognize it  as the basis for  the WG's continuing
> work in this area by adopting it as a WG draft. 
> 
> I'd like to reqeust the WG chairs  to open a "last call" period to determine
> whether there is WG consensus for adopting this draft as a WG draft. 
> 




From l3vpn-bounces@ietf.org Tue Jul 25 10:36:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5O1l-0000kk-Hl; Tue, 25 Jul 2006 10:36:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5O1j-0000ke-Pb
	for l3vpn@ietf.org; Tue, 25 Jul 2006 10:36:51 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5O1h-00052t-Ej
	for l3vpn@ietf.org; Tue, 25 Jul 2006 10:36:51 -0400
Received: from ams-core-1.cisco.com ([144.254.224.150])
	by ams-iport-1.cisco.com with ESMTP; 25 Jul 2006 16:36:49 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k6PEakUO013705; 
	Tue, 25 Jul 2006 16:36:48 +0200 (MEST)
Received: from xmb-ams-33a.cisco.com ([144.254.231.85]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.0); 
	Tue, 25 Jul 2006 16:36:46 +0200
Received: from 10.21.82.115 ([10.21.82.115]) by xmb-ams-33a.emea.cisco.com
	([144.254.231.85]) via Exchange Front-End Server
	email.cisco.com ([171.70.151.187]) with Microsoft Exchange
	Server HTTP-DAV ; Tue, 25 Jul 2006 14:36:45 +0000
User-Agent: Microsoft-Entourage/11.2.4.060510
Date: Tue, 25 Jul 2006 10:34:22 -0400
From: Monique Morrow <mmorrow@cisco.com>
To: Ron Bonica <rbonica@juniper.net>, <erosen@cisco.com>
Message-ID: <C0EBA42E.297AC%mmorrow@cisco.com>
Thread-Topic: "BGP Encodings for Multicast in MPLS/BGP IP VPNs"
Thread-Index: Acav92thqablxhvqEdu52AANk8LkKg==
In-Reply-To: <44C628C8.70006@juniper.net>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 25 Jul 2006 14:36:46.0317 (UTC)
	FILETIME=[C166F1D0:01C6AFF7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: l3vpn@ietf.org
Subject: Re: "BGP Encodings for Multicast in MPLS/BGP IP 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

Support as WG draft.

/Monique


On 25/7/06 10:20 am, "Ron Bonica" <rbonica@juniper.net> wrote:

> Hi Eric,
> 
> I guess this is more of a first call than a last call ;-)
> 
> Anyway, does anyone have any strong opinions regarding whether this
> draft should be accepted as a WG item?
> 
>                              -ron
> 
> 
> Eric Rosen wrote:
>> This internet  draft (draft-raggarwa-l3vpn-2548bis-mcast-bgp-02.txt) has now
>> been discussed  at several IETF meetings,  and is proceeding  well.  I think
>> it's time  to officially recognize it  as the basis for  the WG's continuing
>> work in this area by adopting it as a WG draft.
>> 
>> I'd like to reqeust the WG chairs  to open a "last call" period to determine
>> whether there is WG consensus for adopting this draft as a WG draft.
>> 




From l3vpn-bounces@ietf.org Tue Jul 25 10:37:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5O2U-0000z5-6D; Tue, 25 Jul 2006 10:37:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5O2S-0000yz-QR
	for l3vpn@ietf.org; Tue, 25 Jul 2006 10:37:36 -0400
Received: from slb-smtpout-01.boeing.com ([130.76.64.48]
	helo=slb-smtpout-01.ns.cs.boeing.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5O2N-0005RN-Hr
	for l3vpn@ietf.org; Tue, 25 Jul 2006 10:37:36 -0400
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by slb-smtpout-01.ns.cs.boeing.com (8.13.6/8.13.6/TEST_SMTPIN) with
	ESMTP id k6PEb7dv025861
	for <l3vpn@ietf.org>; Tue, 25 Jul 2006 07:37:12 -0700 (PDT)
Received: from XCH-SWBH-04.sw.nos.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id
	k6PEbP303399
	for <l3vpn@ietf.org>; Tue, 25 Jul 2006 09:37:25 -0500 (CDT)
Received: from XCH-SW-42.sw.nos.boeing.com ([192.79.11.43]) by
	XCH-SWBH-04.sw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 25 Jul 2006 07:37:24 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 25 Jul 2006 07:37:24 -0700
Message-ID: <626FC7C6A97381468FB872072AB5DDC8C2DC1D@XCH-SW-42.sw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: "BGP Encodings for Multicast in MPLS/BGP IP VPNs"
Thread-Index: Acav9i2cQ2HnajgsTM2ciKLPh9/hoAAAZiWQ
From: "Drake, John E" <John.E.Drake2@boeing.com>
To: <l3vpn@ietf.org>
X-OriginalArrivalTime: 25 Jul 2006 14:37:24.0790 (UTC)
	FILETIME=[D8557560:01C6AFF7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Subject: RE: "BGP Encodings for Multicast in MPLS/BGP IP 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

Yes

> -----Original Message-----
> From: Ron Bonica [mailto:rbonica@juniper.net]=20
> Sent: Tuesday, July 25, 2006 7:21 AM
> To: erosen@cisco.com
> Cc: l3vpn@ietf.org
> Subject: Re: "BGP Encodings for Multicast in MPLS/BGP IP VPNs"
>=20
>=20
> Hi Eric,
>=20
> I guess this is more of a first call than a last call ;-)
>=20
> Anyway, does anyone have any strong opinions regarding=20
> whether this draft should be accepted as a WG item?
>=20
>                              -ron
>=20
>=20
> Eric Rosen wrote:
> > This internet  draft=20
> (draft-raggarwa-l3vpn-2548bis-mcast-bgp-02.txt)=20
> > has now been discussed  at several IETF meetings,  and is=20
> proceeding =20
> > well.  I think it's time  to officially recognize it  as=20
> the basis for =20
> > the WG's continuing work in this area by adopting it as a WG draft.
> >=20
> > I'd like to reqeust the WG chairs  to open a "last call" period to=20
> > determine whether there is WG consensus for adopting this=20
> draft as a=20
> > WG draft.
> >=20
>=20
>=20




From l3vpn-bounces@ietf.org Tue Jul 25 11:20:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5Ohk-0008LQ-W6; Tue, 25 Jul 2006 11:20:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5Ohj-0008KJ-QZ
	for l3vpn@ietf.org; Tue, 25 Jul 2006 11:20:15 -0400
Received: from omr5.networksolutionsemail.com ([205.178.146.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5Ohi-000154-JS
	for l3vpn@ietf.org; Tue, 25 Jul 2006 11:20:15 -0400
Received: from mail.networksolutionsemail.com (ns-omr5.mgt.netsol.com
	[10.49.6.68])
	by omr5.networksolutionsemail.com (8.13.6/8.13.6) with SMTP id
	k6PFJtfd026275 for <l3vpn@ietf.org>; Tue, 25 Jul 2006 11:20:00 -0400
Received: (qmail 16183 invoked by uid 78); 25 Jul 2006 15:19:55 -0000
Received: from unknown (HELO webmail14) (205.178.146.50)
	by 10.49.36.68 with SMTP; 25 Jul 2006 15:19:55 -0000
Received: from 199.67.203.140 (mark@mjlnet.com [199.67.203.140])
	by webmail14 (EdgeDesk 4.02) with WEBMAIL id 6927;
	Tue, 25 Jul 2006 15:19:55 +0000
From: "Mark Lewis" <mark@mjlnet.com>
To: erosen@cisco.com, l3vpn@ietf.org
Importance: Normal
Sensitivity: Normal
Message-ID: <W40756880769271153840795@webmail14>
X-Mailer: Mintersoft EdgeDesk, Build 4.03.0105
X-Originating-IP: [199.67.203.140]
X-Forwarded-For: [(null)]
Date: Tue, 25 Jul 2006 15:19:55 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: 
Subject: Re: 
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mark@mjlnet.com
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

I support making this a WG draft.

Mark


>-----Original Message-----
>From: Eric Rosen [mailto:erosen@cisco.com]
>Sent: Tuesday, July 25, 2006 03:17 PM
>To: l3vpn@ietf.org
>Subject: "BGP Encodings for Multicast in MPLS/BGP IP VPNs"
>
>This internet  draft (draft-raggarwa-l3vpn-2548bis-mcast-bgp-02.txt) has now
>been discussed  at several IETF meetings,  and is proceeding  well.  I think
>it's time  to officially recognize it  as the basis for  the WG's continuing
>work in this area by adopting it as a WG draft. 
>
>I'd like to reqeust the WG chairs  to open a "last call" period to determine
>whether there is WG consensus for adopting this draft as a WG draft. 
>
>






From l3vpn-bounces@ietf.org Wed Jul 26 11:14:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5l5P-0001VV-Dj; Wed, 26 Jul 2006 11:14:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5l5N-0001VQ-Ld
	for l3vpn@ietf.org; Wed, 26 Jul 2006 11:14:09 -0400
Received: from ug-out-1314.google.com ([66.249.92.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5l5L-0002KT-B8
	for l3vpn@ietf.org; Wed, 26 Jul 2006 11:14:09 -0400
Received: by ug-out-1314.google.com with SMTP id m2so3367804uge
	for <l3vpn@ietf.org>; Wed, 26 Jul 2006 08:14:06 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=O9ZALFacstDI+wA4UY3L6KFWuhQQTHmP2tBkeoIqEo1Pq2/4kNsuHYSUsdgVkEGNaOwdVKTRML/86T0pqBzWn1fKEjU3TQ+81P3adKbRdBACpPxDDDG93f8q+icjqvbCR+t1jRPMYsGBTwev9ylgxHpBjKsuN5a84pvwdmJJxGg=
Received: by 10.78.117.10 with SMTP id p10mr3187256huc;
	Wed, 26 Jul 2006 08:14:06 -0700 (PDT)
Received: by 10.78.150.5 with HTTP; Wed, 26 Jul 2006 08:14:06 -0700 (PDT)
Message-ID: <dcad22d80607260814o4ce5be07r66e4fb28e2c66e72@mail.gmail.com>
Date: Wed, 26 Jul 2006 11:14:06 -0400
From: "Marshall Eubanks" <marshall.eubanks@gmail.com>
To: erosen@cisco.com
In-Reply-To: <200607251417.k6PEHmdU016989@rtp-core-2.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <200607251417.k6PEHmdU016989@rtp-core-2.cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: l3vpn@ietf.org
Subject: Re: "BGP Encodings for Multicast in MPLS/BGP IP 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

Where is it ? Both

http://www.ietf.org/internet-drafts/draft-raggarwa-l3vpn-2548bis-mcast-bgp-02.txt

and a full search

https://datatracker.ietf.org/public/idindex.cgi?command=do_search_id&filename=draft-raggarwa-l3vpn-2548bis-mcast-bgp&id_tracker_state_id=-1&wg_id=0&other_group=&status_id=0&last_name=&first_name=

come up with nothing.

Has it just expired or is there a typo ?

Regards
Marshall


---------- Forwarded message ----------
From: Eric Rosen <erosen@cisco.com>
Date: Jul 25, 2006 10:17 AM
Subject: "BGP Encodings for Multicast in MPLS/BGP IP VPNs"
To: l3vpn@ietf.org


This internet  draft (draft-raggarwa-l3vpn-2548bis-mcast-bgp-02.txt) has now
been discussed  at several IETF meetings,  and is proceeding  well.  I think
it's time  to officially recognize it  as the basis for  the WG's continuing
work in this area by adopting it as a WG draft.

I'd like to reqeust the WG chairs  to open a "last call" period to determine
whether there is WG consensus for adopting this draft as a WG draft.




From l3vpn-bounces@ietf.org Wed Jul 26 12:36:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5mMo-000789-Jg; Wed, 26 Jul 2006 12:36:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5mMn-00077z-AC
	for l3vpn@ietf.org; Wed, 26 Jul 2006 12:36:13 -0400
Received: from mail1.noc.data.net.uk ([80.68.34.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5mMl-0000EU-TL
	for l3vpn@ietf.org; Wed, 26 Jul 2006 12:36:13 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail1.noc.data.net.uk with esmtp (Exim 3.36 #2)
	id 1G5mN1-00009H-00
	for l3vpn@ietf.org; Wed, 26 Jul 2006 17:36:27 +0100
Received: from your029b8cecfe ([217.158.132.40] RDNS failed) by
	cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 26 Jul 2006 17:36:09 +0100
Message-ID: <02dd01c6b0d1$92cade60$0a23fea9@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Ron Bonica" <rbonica@juniper.net>,
	<erosen@cisco.com>
References: <200607251417.k6PEHmdU016989@rtp-core-2.cisco.com>
	<44C628C8.70006@juniper.net>
Date: Wed, 26 Jul 2006 15:09:59 +0100
Organization: Old Dog Consulting
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-OriginalArrivalTime: 26 Jul 2006 16:36:10.0556 (UTC)
	FILETIME=[9A08CFC0:01C6B0D1]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: l3vpn@ietf.org
Subject: Re: "BGP Encodings for Multicast in MPLS/BGP IP VPNs"
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
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

Support.
A
----- Original Message ----- 
From: "Ron Bonica" <rbonica@juniper.net>
To: <erosen@cisco.com>
Cc: <l3vpn@ietf.org>
Sent: Tuesday, July 25, 2006 3:20 PM
Subject: Re: "BGP Encodings for Multicast in MPLS/BGP IP VPNs"


> Hi Eric,
>
> I guess this is more of a first call than a last call ;-)
>
> Anyway, does anyone have any strong opinions regarding whether this
> draft should be accepted as a WG item?
>
>                             -ron
>
>
> Eric Rosen wrote:
>> This internet  draft (draft-raggarwa-l3vpn-2548bis-mcast-bgp-02.txt) has 
>> now
>> been discussed  at several IETF meetings,  and is proceeding  well.  I 
>> think
>> it's time  to officially recognize it  as the basis for  the WG's 
>> continuing
>> work in this area by adopting it as a WG draft.
>>
>> I'd like to reqeust the WG chairs  to open a "last call" period to 
>> determine
>> whether there is WG consensus for adopting this draft as a WG draft.
>>
>
>
>
> 






From l3vpn-bounces@ietf.org Wed Jul 26 12:45:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5mVn-0005CP-SM; Wed, 26 Jul 2006 12:45:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5mVn-0005CK-1P
	for l3vpn@ietf.org; Wed, 26 Jul 2006 12:45:31 -0400
Received: from borg.juniper.net ([207.17.137.119])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5mVl-0000xV-OQ
	for l3vpn@ietf.org; Wed, 26 Jul 2006 12:45:31 -0400
Received: from unknown (HELO alpha.jnpr.net) ([172.24.18.126])
	by borg.juniper.net with ESMTP; 26 Jul 2006 09:45:31 -0700
X-IronPort-AV: i="4.07,185,1151910000"; 
	d="scan'208"; a="571368268:sNHT28121248"
Received: from sapphire.juniper.net ([172.17.28.108]) by alpha.jnpr.net over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 26 Jul 2006 09:45:34 -0700
Date: Wed, 26 Jul 2006 09:45:28 -0700 (PDT)
From: Rahul Aggarwal <rahul@juniper.net>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
In-Reply-To: <dcad22d80607260814o4ce5be07r66e4fb28e2c66e72@mail.gmail.com>
Message-ID: <20060726094415.H98080@sapphire.juniper.net>
References: <200607251417.k6PEHmdU016989@rtp-core-2.cisco.com>
	<dcad22d80607260814o4ce5be07r66e4fb28e2c66e72@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-OriginalArrivalTime: 26 Jul 2006 16:45:34.0807 (UTC)
	FILETIME=[EA5AAE70:01C6B0D2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: erosen@cisco.com, l3vpn@ietf.org
Subject: Re: "BGP Encodings for Multicast in MPLS/BGP IP 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


Hi Marshall,

There is a typo. The draft is:
draft-raggarwa-l3vpn-2547bis-mcast-bgp-02.txt, at:

http://www.ietf.org/internet-drafts/draft-raggarwa-l3vpn-2547bis-mcast-bgp-02.txt

rahul

On Wed, 26 Jul 2006, Marshall Eubanks wrote:

> Where is it ? Both
>
> http://www.ietf.org/internet-drafts/draft-raggarwa-l3vpn-2548bis-mcast-bgp-02.txt
>
> and a full search
>
> https://datatracker.ietf.org/public/idindex.cgi?command=do_search_id&filename=draft-raggarwa-l3vpn-2548bis-mcast-bgp&id_tracker_state_id=-1&wg_id=0&other_group=&status_id=0&last_name=&first_name=
>
> come up with nothing.
>
> Has it just expired or is there a typo ?
>
> Regards
> Marshall
>
>
> ---------- Forwarded message ----------
> From: Eric Rosen <erosen@cisco.com>
> Date: Jul 25, 2006 10:17 AM
> Subject: "BGP Encodings for Multicast in MPLS/BGP IP VPNs"
> To: l3vpn@ietf.org
>
>
> This internet  draft (draft-raggarwa-l3vpn-2548bis-mcast-bgp-02.txt) has now
> been discussed  at several IETF meetings,  and is proceeding  well.  I think
> it's time  to officially recognize it  as the basis for  the WG's continuing
> work in this area by adopting it as a WG draft.
>
> I'd like to reqeust the WG chairs  to open a "last call" period to determine
> whether there is WG consensus for adopting this draft as a WG draft.
>




From l3vpn-bounces@ietf.org Thu Jul 27 09:30:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G65wb-0003zL-M7; Thu, 27 Jul 2006 09:30:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G65wa-0003zB-Ji
	for l3vpn@ietf.org; Thu, 27 Jul 2006 09:30:28 -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 1G63yO-00014e-BT
	for l3vpn@ietf.org; Thu, 27 Jul 2006 07:24:12 -0400
Received: from smtp2.dataconnection.com ([192.91.191.8])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G63nM-0000Al-Gg
	for l3vpn@ietf.org; Thu, 27 Jul 2006 07:12:50 -0400
Received: from enfimail2.datcon.co.uk ([172.19.14.250]) by
	smtp2.dataconnection.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 27 Jul 2006 12:12:40 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 27 Jul 2006 12:12:39 +0100
Message-ID: <8AC1AD08D396174DBC4E6D44EFACCFB1DB49CF@enfimail2.datcon.co.uk>
In-Reply-To: <dcad22d80607260814o4ce5be07r66e4fb28e2c66e72@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: "BGP Encodings for Multicast in MPLS/BGP IP VPNs"
Thread-Index: AcawxlxOvLCxN2s7Qg++2KLOvDUhLgApqu5g
From: "David McWalter" <DMcW@dataconnection.com>
To: "Marshall Eubanks" <marshall.eubanks@gmail.com>
X-OriginalArrivalTime: 27 Jul 2006 11:12:40.0007 (UTC)
	FILETIME=[92DBD570:01C6B16D]
X-Spam-Score: -1.9 (-)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: erosen@cisco.com, l3vpn@ietf.org
Subject: RE: "BGP Encodings for Multicast in MPLS/BGP IP 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

Just a typo.  It's 2547bis not 2548bis.
http://www.ietf.org/internet-drafts/draft-raggarwa-l3vpn-2547bis-mcast-bg=
p-02.txt

DMcW.

-----Original Message-----
From: Marshall Eubanks [mailto:marshall.eubanks@gmail.com]
Sent: 26 July 2006 16:14
To: erosen@cisco.com
Cc: l3vpn@ietf.org
Subject: Re: "BGP Encodings for Multicast in MPLS/BGP IP VPNs"


Where is it ? Both

http://www.ietf.org/internet-drafts/draft-raggarwa-l3vpn-2548bis-mcast-bg=
p-02.txt

and a full search

https://datatracker.ietf.org/public/idindex.cgi?command=3Ddo_search_id&fi=
lename=3Ddraft-raggarwa-l3vpn-2548bis-mcast-bgp&id_tracker_state_id=3D-1&=
wg_id=3D0&other_group=3D&status_id=3D0&last_name=3D&first_name=3D

come up with nothing.

Has it just expired or is there a typo ?

Regards
Marshall


---------- Forwarded message ----------
From: Eric Rosen <erosen@cisco.com>
Date: Jul 25, 2006 10:17 AM
Subject: "BGP Encodings for Multicast in MPLS/BGP IP VPNs"
To: l3vpn@ietf.org


This internet  draft (draft-raggarwa-l3vpn-2548bis-mcast-bgp-02.txt) has =
now
been discussed  at several IETF meetings,  and is proceeding  well.  I =
think
it's time  to officially recognize it  as the basis for  the WG's =
continuing
work in this area by adopting it as a WG draft.

I'd like to reqeust the WG chairs  to open a "last call" period to =
determine
whether there is WG consensus for adopting this draft as a WG draft.





From l3vpn-bounces@ietf.org Thu Jul 27 14:23:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G6AWL-0002Dy-Ck; Thu, 27 Jul 2006 14:23:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G6AWJ-00026B-IP
	for l3vpn@ietf.org; Thu, 27 Jul 2006 14:23:39 -0400
Received: from mail121.messagelabs.com ([216.82.241.195])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G6AWI-0000ZY-7d
	for l3vpn@ietf.org; Thu, 27 Jul 2006 14:23:39 -0400
X-VirusChecked: Checked
X-Env-Sender: luyuanfang@att.com
X-Msg-Ref: server-10.tower-121.messagelabs.com!1154024608!13301378!6
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 17866 invoked from network); 27 Jul 2006 18:23:36 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-10.tower-121.messagelabs.com with SMTP;
	27 Jul 2006 18:23:36 -0000
Received: from kcclust06evs1.ugd.att.com (135.38.164.89) by
	attrh3i.attrh.att.com (7.2.052)
	id 44C39E85000A3645 for l3vpn@ietf.org; Thu, 27 Jul 2006 14:23:36 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 27 Jul 2006 13:23:34 -0500
Message-ID: <A1F50CB516D211409DFD05D6B3CE6D3008E1363D@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <E1G5PKZ-0007ky-RK@megatron.ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: L3vpn Digest, Vol 27, Issue 7
Thread-Index: AcawA3lkBCly+oqXT62sF03zPI4GYwBpdPzA
From: "Fang, Luyuan, ALABS" <luyuanfang@att.com>
To: <l3vpn@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Subject: RE: L3vpn Digest, Vol 27, Issue 7
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

Support as a WG draft.

- Luyuan

> -----Original Message-----
> From: Ron Bonica [mailto:rbonica@juniper.net]
> Sent: Tuesday, July 25, 2006 7:21 AM
> To: erosen@cisco.com
> Cc: l3vpn@ietf.org
> Subject: Re: "BGP Encodings for Multicast in MPLS/BGP IP VPNs"
>=20
>=20
> Hi Eric,
>=20
> I guess this is more of a first call than a last call ;-)
>=20
> Anyway, does anyone have any strong opinions regarding whether this=20
> draft should be accepted as a WG item?
>=20
>                              -ron
>=20
>=20
> Eric Rosen wrote:
> > This internet  draft
> (draft-raggarwa-l3vpn-2548bis-mcast-bgp-02.txt)
> > has now been discussed  at several IETF meetings,  and is
> proceeding
> > well.  I think it's time  to officially recognize it  as
> the basis for
> > the WG's continuing work in this area by adopting it as a WG draft.
> >=20
> > I'd like to reqeust the WG chairs  to open a "last call" period to=20
> > determine whether there is WG consensus for adopting this
> draft as a
> > WG draft.
> >=20
>=20
>=20



>-----Original Message-----
>From: Eric Rosen [mailto:erosen@cisco.com]
>Sent: Tuesday, July 25, 2006 03:17 PM
>To: l3vpn@ietf.org
>Subject: "BGP Encodings for Multicast in MPLS/BGP IP VPNs"
>
>This internet  draft (draft-raggarwa-l3vpn-2548bis-mcast-bgp-02.txt)=20
>has now been discussed  at several IETF meetings,  and is proceeding =20
>well.  I think it's time  to officially recognize it  as the basis for

>the WG's continuing work in this area by adopting it as a WG draft.
>
>I'd like to reqeust the WG chairs  to open a "last call" period to=20
>determine whether there is WG consensus for adopting this draft as a WG
draft.
>
>





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

_______________________________________________
L3vpn mailing list
L3vpn@ietf.org
https://www1.ietf.org/mailman/listinfo/l3vpn


End of L3vpn Digest, Vol 27, Issue 7
************************************




From l3vpn-bounces@ietf.org Fri Jul 28 16:51:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G6ZIg-0002Ql-H6; Fri, 28 Jul 2006 16:51:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G6ZIf-0002Qg-DZ
	for l3vpn@ietf.org; Fri, 28 Jul 2006 16:51:13 -0400
Received: from borg.juniper.net ([207.17.137.119])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G6ZId-0008E5-4w
	for l3vpn@ietf.org; Fri, 28 Jul 2006 16:51:13 -0400
Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37])
	by borg.juniper.net with ESMTP; 28 Jul 2006 13:51:13 -0700
X-IronPort-AV: i="4.07,192,1151910000"; 
	d="scan'208"; a="572086324:sNHT28411712"
Received: from [172.25.51.51] ([172.25.51.51] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 28 Jul 2006 16:51:18 -0400
Message-ID: <44CA78C2.6070309@juniper.net>
Date: Fri, 28 Jul 2006 16:51:14 -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: erosen@cisco.com
References: <200607251417.k6PEHmdU016989@rtp-core-2.cisco.com>
	<44C628C8.70006@juniper.net>
In-Reply-To: <44C628C8.70006@juniper.net>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 Jul 2006 20:51:18.0099 (UTC)
	FILETIME=[92DE0230:01C6B287]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: l3vpn@ietf.org
Subject: Re: "BGP Encodings for Multicast in MPLS/BGP IP 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

Folks,

I have heard no objections, so lets make this draft a WG item.

                                 Ron


Ron Bonica wrote:
> Hi Eric,
> 
> I guess this is more of a first call than a last call ;-)
> 
> Anyway, does anyone have any strong opinions regarding whether this
> draft should be accepted as a WG item?
> 
>                              -ron
> 
> 
> Eric Rosen wrote:
> 
>>This internet  draft (draft-raggarwa-l3vpn-2548bis-mcast-bgp-02.txt) has now
>>been discussed  at several IETF meetings,  and is proceeding  well.  I think
>>it's time  to officially recognize it  as the basis for  the WG's continuing
>>work in this area by adopting it as a WG draft. 
>>
>>I'd like to reqeust the WG chairs  to open a "last call" period to determine
>>whether there is WG consensus for adopting this draft as a WG draft. 
>>
> 
> 




