From l3vpn-bounces@ietf.org Wed Feb 01 09:09:56 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F4IgG-0002Y1-Cx; Wed, 01 Feb 2006 09:09:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F4IgD-0002TH-HT
	for l3vpn@megatron.ietf.org; Wed, 01 Feb 2006 09:09:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02264
	for <l3vpn@ietf.org>; Wed, 1 Feb 2006 09:08:16 -0500 (EST)
From: benjamin.niven-jenkins@bt.com
Received: from smtp4.smtp.bt.com ([217.32.164.151])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F4IrO-0007AY-Tm
	for l3vpn@ietf.org; Wed, 01 Feb 2006 09:21:27 -0500
Received: from i2km98-ukbr.domain1.systemhost.net ([193.113.197.85]) by
	smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 1 Feb 2006 14:09:38 +0000
Received: from i2km86-ukdy.domain1.systemhost.net ([193.113.30.79]) by
	i2km98-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(5.0.2195.6713); Wed, 1 Feb 2006 14:09:38 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 1 Feb 2006 14:09:36 -0000
Message-ID: <F5AAFD21F2034349BF638211B5F27B0F0693DCFE@i2km86-ukdy.domain1.systemhost.net>
Thread-Topic: Review: draft-ietf-l3vpn-ppvpn-mcast-reqts
Thread-Index: AcYnOSIlny+vHo9BTSqRQQTTaGw8JQ==
To: <thomas.morin@francetelecom.com>
X-OriginalArrivalTime: 01 Feb 2006 14:09:38.0019 (UTC)
	FILETIME=[22FBE330:01C62739]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Content-Transfer-Encoding: quoted-printable
Cc: l3vpn@ietf.org
Subject: Review: draft-ietf-l3vpn-ppvpn-mcast-reqts
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>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Thomas,
Cc Colleagues,

I've finally found time to read the second half of
draft-ietf-l3vpn-ppvpn-mcast-reqts and have the following
comments/corrections.  These are based on the -04 version of the draft.

Ben


Section 5.1.7, 4th paragraph states:
"Moreover, a solution MUST allow to control an extranet multicast
connectivity independently from the extranet unicast connectivity."

MUST allow who? to control this.

Suggest "Moreover, a solution MUST allow service providers to control an
extranet's multicast connectivity independently from the extranet's
unicast connectivity."

Section 5.2.1 - remove extraneous 'possibly' so "impact on possibly
existing deployments" becomes "impact on existing deployments".

Section 5.2.2 8th bullet, change "required on PE and P to add or remove
a customer site" to "required on PE and P routers to add or remove a
customer site".

Section 5.2.2 last paragraph: "but a multicast in VPNs solution" should
this be "but a multicast VPN solution"?

Section 5.2.3.1 2nd paragraph: change "(when same data travels twice or
more on a same link, e.g. when doing ingress PE replication)" to "(when
the same data travels twice or more on the same link, e.g. when doing
ingress PE replication)".

Section 5.2.3.3 2nd paragraph: change "Thus a multicast VPN solution
SHOULD offer the service providers appropriate" to "Thus a multicast VPN
solution SHOULD offer service providers appropriate".  Also on the 4th
line of this paragraph I don't think you mean 'peculiar' but rather you
mean 'particular'?

Section 5.2.3.3 3rd paragraph: change "a NP-hard" to "an NP-hard"

Section 5.2.4.1 2nd paragraph states "In a multicast VPN solution
extending a unicast L3 PPVPN solution, consistency in the tunneling
technology has to be privileged" I don't understand what this means
especially your use of the word privileged in this context.

Section 5.2.4.1 4th paragraph states "and may help improve bandwidth
efficiency in our multicast VPN context." I don't know what you mean by
"our multicast VPN context", do you really mean "a multicast VPN
context"?

Section 5.2.4.2 1st paragraph: change "e.g., to discover MTU, to tell
MTU with signaling," to "e.g., to discover MTU, to communicate MTU via
signaling,".

Section 5.2.4.2 2nd bullet: change "if packets too big for" to "if
packets that are too big for".

Section 5.2.6 last paragraph: change "penalty" to "penalties"?

Section 5.2.8 5th paragraph: change "In a such perspective," to "In such
cases,"

Section 5.2.8 6th paragraph: change "Last" to "Lastly".

Section 5.2.10 2nd paragraph: change "VPN" to "VPNs" and change
"operation" to "operational".

Section 5.2.11 2nd paragraph: change "participate to the deployment" to
"participate in the deployment".

Section 5.2.11 4th paragraph: change "Ideally a solution would have be
the ability to offer multicast VPN services across a network containing
some legacy routers not supporting any multicast VPN specific features."
to "Ideally a solution would have the ability to offer multicast VPN
services across a network containing some legacy routers that do not
support any multicast VPN specific features."

Section 5.2.11 5th paragraph: replace "from possibly" with "for".

Section 5.2.12 2nd paragraph: change "a solution MAY usefully provide
some mechanism letting network operators check that all VPN sites" to "a
solution MAY usefully provide some mechanism to allow network operators
to check that all VPN sites" and change "Providing the operators with
means" to "Providing operators with means".

--=20
Ben Niven-Jenkins
Network Architect, BT Exact
 =20
E-mail: benjamin.niven-jenkins@bt.com=20
Office: +44 (0)1473 648225
Mobile: +44 (0)7918 077205
   Fax: +44 (0)1332 578827




From l3vpn-bounces@ietf.org Thu Feb 02 08:40:23 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F4ehD-0004Ri-ID; Thu, 02 Feb 2006 08:40:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F4eh9-0004Pk-SG
	for l3vpn@megatron.ietf.org; Thu, 02 Feb 2006 08:40:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03729
	for <l3vpn@ietf.org>; Thu, 2 Feb 2006 08:38:32 -0500 (EST)
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F4esM-0003Ys-M8
	for l3vpn@ietf.org; Thu, 02 Feb 2006 08:51:56 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 2 Feb 2006 12:11:31 +0100
Received: from l-at8613.rd.francetelecom.fr ([10.193.15.65]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 2 Feb 2006 12:11:31 +0100
From: Thomas Morin <thomas.morin@rd.francetelecom.com>
To: benjamin.niven-jenkins@bt.com
In-Reply-To: <F5AAFD21F2034349BF638211B5F27B0F0693DCFE@i2km86-ukdy.domain1.systemhost.net>
References: <F5AAFD21F2034349BF638211B5F27B0F0693DCFE@i2km86-ukdy.domain1.systemhost.net>
Content-Type: text/plain
Organization: France Telecom R&D
Date: Thu, 02 Feb 2006 12:11:30 +0100
Message-Id: <1138878690.5235.38.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Feb 2006 11:11:31.0523 (UTC)
	FILETIME=[6BBFC130:01C627E9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
Cc: l3vpn@ietf.org
Subject: Re: Review: draft-ietf-l3vpn-ppvpn-mcast-reqts
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>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hi Ben, folks,

I integrated most of your suggested editorial changes.
Thank you for your careful review.

benjamin.niven-jenkins@bt.com:
> Section 5.2.3.3 2nd paragraph: change "Thus a multicast VPN solution
> SHOULD offer the service providers appropriate" to "Thus a multicast VPN
> solution SHOULD offer service providers appropriate".  Also on the 4th
> line of this paragraph I don't think you mean 'peculiar' but rather you
> mean 'particular'?

Well, "peculiar" is indeed what I meant (and seems to be in the
dictionary).  Anyway I changed to "particular" which I agree is more
common.

> Section 5.2.4.1 2nd paragraph states "In a multicast VPN solution
> extending a unicast L3 PPVPN solution, consistency in the tunneling
> technology has to be privileged" I don't understand what this means
> especially your use of the word privileged in this context.

I changed to "favored".

> Section 5.2.11 5th paragraph: replace "from possibly" with "for".
> 

Why should the 'possibly' be removed ?
Its important to keep in mind no standardized solution exist yet for
multicast in 2547 VPNs or VR.

Cheers,

-Thomas





From l3vpn-bounces@ietf.org Thu Feb 02 09:10:46 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F4fAb-000191-VW; Thu, 02 Feb 2006 09:10:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F4f6V-0007iE-D5
	for l3vpn@megatron.ietf.org; Thu, 02 Feb 2006 09:06:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05297
	for <l3vpn@ietf.org>; Thu, 2 Feb 2006 09:04:52 -0500 (EST)
From: benjamin.niven-jenkins@bt.com
Received: from smtp2.smtp.bt.com ([217.32.164.150])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F4fBk-0004HT-VT
	for l3vpn@ietf.org; Thu, 02 Feb 2006 09:11:58 -0500
Received: from i2kc07-ukbr.domain1.systemhost.net ([193.113.197.14]) by
	smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 2 Feb 2006 14:00:01 +0000
Received: from i2km86-ukdy.domain1.systemhost.net ([193.113.30.79]) by
	i2kc07-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.211); Thu, 2 Feb 2006 14:00:00 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 2 Feb 2006 13:59:57 -0000
Message-ID: <F5AAFD21F2034349BF638211B5F27B0F0698DF61@i2km86-ukdy.domain1.systemhost.net>
Thread-Topic: Review: draft-ietf-l3vpn-ppvpn-mcast-reqts
Thread-Index: AcYn/jDPt9O4c0AoSK6KhC71w8e18gAAP72w
To: <thomas.morin@rd.francetelecom.com>
X-OriginalArrivalTime: 02 Feb 2006 14:00:00.0107 (UTC)
	FILETIME=[F4EF43B0:01C62800]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: quoted-printable
Cc: l3vpn@ietf.org
Subject: RE: Review: draft-ietf-l3vpn-ppvpn-mcast-reqts
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>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Thomas Morin <mailto:thomas.morin@rd.francetelecom.com> wrote:
>> Section 5.2.11 5th paragraph: replace "from possibly" with "for".
>=20
> Why should the 'possibly' be removed ?
> Its important to keep in mind no standardized solution exist
> yet for multicast in 2547 VPNs or VR.

Because IMO it is superfluous and irrelevant.  The original sentence is
"In any case a solution SHOULD state a migration policy from possibly
existing deployments."

A solution should provide a migration policy for existing deployemnts.
Whether such a migration policy is for an actual deployment as opposed
to a possible deployment is not relevant, by catering for actual
deployments you automatically cater for possible deployments.  Changing
"from possibly" to "for" doesn't change the meaning of the sentence IMO
but makes it read a bit better.

Unless you mean that a solution should state a migration policy for
current solutions that are not currently deployed but which may be
deployed in the future?

Ben





From l3vpn-bounces@ietf.org Fri Feb 03 19:26:22 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F5BFu-0000ng-UX; Fri, 03 Feb 2006 19:26:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F5BFp-0000m2-A4; Fri, 03 Feb 2006 19:26:17 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02267;
	Fri, 3 Feb 2006 19:24:25 -0500 (EST)
Received: from nit.isi.edu ([128.9.160.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F5BRI-0006Sv-79; Fri, 03 Feb 2006 19:38:08 -0500
Received: from nit.isi.edu (loopback [127.0.0.1])
	by nit.isi.edu (8.12.8/8.12.8) with ESMTP id k140Q155009698;
	Fri, 3 Feb 2006 16:26:01 -0800
Received: (from apache@localhost)
	by nit.isi.edu (8.12.8/8.12.8/Submit) id k140Q1s9009697;
	Fri, 3 Feb 2006 16:26:01 -0800
Date: Fri, 3 Feb 2006 16:26:01 -0800
Message-Id: <200602040026.k140Q1s9009697@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=225932eedf3363b050647cc78b7ea76b
X-Spam-Score: -13.9 (-------------)
X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f
Cc: l3vpn@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4364 on 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>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

--225932eedf3363b050647cc78b7ea76b
Content-Type: text/plain
Content-Transfer-Encoding: 8bit

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

        
        RFC 4364

        Title:      BGP/MPLS IP Virtual Private Networks 
                    (VPNs) 
        Author:     E. Rosen,  Y. Rekhter
        Status:     Standards Track
        Date:       February 2006
        Mailbox:    erosen@cisco.com, 
                    yakov@juniper.net
        Pages:      47
        Characters: 116446
        Obsoletes:  RFC2547
        See-Also:   

        I-D Tag:    draft-ietf-l3vpn-rfc2547bis-03.txt

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

This document describes a method by which a Service Provider may use
an IP backbone to provide IP Virtual Private Networks (VPNs) for its
customers.  This method uses a \"peer model\", in which the customers\'
edge routers (CE routers) send their routes to the Service
Provider\'s edge routers (PE routers); there is no \"overlay\" visible
to the customer\'s routing algorithm, and CE routers at different
sites do not peer with each other.  Data packets are tunneled through
the backbone, so that the core routers do not need to know the VPN
routes.  [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

...


--225932eedf3363b050647cc78b7ea76b


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

        
        RFC 4364

        Title:      BGP/MPLS IP Virtual Private Networks 
                    (VPNs) 
        Author:     E. Rosen,  Y. Rekhter
        Status:     Standards Track
        Date:       February 2006
        Mailbox:    erosen@cisco.com, 
                    yakov@juniper.net
        Pages:      47
        Characters: 116446
        Obsoletes:  RFC2547
        See-Also:   

        I-D Tag:    draft-ietf-l3vpn-rfc2547bis-03.txt

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

This document describes a method by which a Service Provider may use
an IP backbone to provide IP Virtual Private Networks (VPNs) for its
customers.  This method uses a \"peer model\", in which the customers\'
edge routers (CE routers) send their routes to the Service
Provider\'s edge routers (PE routers); there is no \"overlay\" visible
to the customer\'s routing algorithm, and CE routers at different
sites do not peer with each other.  Data packets are tunneled through
the backbone, so that the core routers do not need to know the VPN
routes.  [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

...


--225932eedf3363b050647cc78b7ea76b--




From l3vpn-bounces@ietf.org Fri Feb 03 19:27:32 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F5BH2-0000z0-CL; Fri, 03 Feb 2006 19:27:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F5BGx-0000ws-Sz; Fri, 03 Feb 2006 19:27:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02484;
	Fri, 3 Feb 2006 19:25:32 -0500 (EST)
Received: from nit.isi.edu ([128.9.160.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F5BSN-0006Wl-Vt; Fri, 03 Feb 2006 19:39:16 -0500
Received: from nit.isi.edu (loopback [127.0.0.1])
	by nit.isi.edu (8.12.8/8.12.8) with ESMTP id k140RA55009705;
	Fri, 3 Feb 2006 16:27:10 -0800
Received: (from apache@localhost)
	by nit.isi.edu (8.12.8/8.12.8/Submit) id k140RADD009704;
	Fri, 3 Feb 2006 16:27:10 -0800
Date: Fri, 3 Feb 2006 16:27:10 -0800
Message-Id: <200602040027.k140RADD009704@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=19f9bcac8770d2066f22c43e7af4c8fc
X-Spam-Score: -13.9 (-------------)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Cc: l3vpn@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4365 on Applicability Statement 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>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

--19f9bcac8770d2066f22c43e7af4c8fc
Content-Type: text/plain
Content-Transfer-Encoding: 8bit

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

        
        RFC 4365

        Title:      Applicability Statement for BGP/MPLS IP 
                    Virtual Private Networks (VPNs) 
        Author:     E. Rosen
        Status:     Informational
        Date:       February 2006
        Mailbox:    erosen@cisco.com
        Pages:      32
        Characters: 77924
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l3vpn-as2547-07.txt

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

This document provides an Applicability Statement for the
Virtual Private Network (VPN) solution described in RFC 4364
and other documents listed in the References section.  This memo provides information for the Internet community.

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

INFORMATIONAL: This memo provides information for the Internet community. 
It does not specify an Internet standard of any kind. 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

...


--19f9bcac8770d2066f22c43e7af4c8fc


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

        
        RFC 4365

        Title:      Applicability Statement for BGP/MPLS IP 
                    Virtual Private Networks (VPNs) 
        Author:     E. Rosen
        Status:     Informational
        Date:       February 2006
        Mailbox:    erosen@cisco.com
        Pages:      32
        Characters: 77924
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l3vpn-as2547-07.txt

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

This document provides an Applicability Statement for the
Virtual Private Network (VPN) solution described in RFC 4364
and other documents listed in the References section.  This memo provides information for the Internet community.

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

INFORMATIONAL: This memo provides information for the Internet community. 
It does not specify an Internet standard of any kind. 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

...


--19f9bcac8770d2066f22c43e7af4c8fc--




From l3vpn-bounces@ietf.org Fri Feb 10 18:04:23 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F7hJP-0006QW-EV; Fri, 10 Feb 2006 18:04:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F7hJK-0006OP-UB; Fri, 10 Feb 2006 18:04:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09590;
	Fri, 10 Feb 2006 18:02:18 -0500 (EST)
Received: from nit.isi.edu ([128.9.160.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F7hWA-0004xQ-D5; Fri, 10 Feb 2006 18:17:34 -0500
Received: from nit.isi.edu (loopback [127.0.0.1])
	by nit.isi.edu (8.12.8/8.12.8) with ESMTP id k1AN41WV031712;
	Fri, 10 Feb 2006 15:04:01 -0800
Received: (from apache@localhost)
	by nit.isi.edu (8.12.8/8.12.8/Submit) id k1AN41Wf031711;
	Fri, 10 Feb 2006 15:04:01 -0800
Date: Fri, 10 Feb 2006 15:04:01 -0800
Message-Id: <200602102304.k1AN41Wf031711@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
X-Spam-Score: -14.7 (--------------)
X-Scan-Signature: 29dc808194f5fb921c09d0040806d6eb
Content-Transfer-Encoding: 8bit
Cc: l3vpn@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4382 on MPLS/BGP Layer 3 Virtual Private Network (VPN)
	Management Information Base
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>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

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

        
        RFC 4382

        Title:      MPLS/BGP Layer 3 Virtual Private 
                    Network (VPN) Management Information Base 
        Author:     T. Nadeau,  Ed., 
                    H. van der Linde,  Ed.
        Status:     Standards Track
        Date:       February 2006
        Mailbox:    tnadeau@cisco.com, 
                    havander@cisco.com
        Pages:      44
        Characters: 85594
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l3vpn-mpls-vpn-mib-07.txt

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

This memo defines a portion of the Management
Information Base (MIB) for use with network management protocols
in the Internet community.  In particular, it describes managed
objects to configure and/or monitor Multiprotocol Label
Switching Layer-3 Virtual Private Networks on a
Multiprotocol Label Switching (MPLS) Label Switching Router
(LSR) supporting this feature.  [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

...


--9ecf615818949b21384462a8702d22cd


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

        
        RFC 4382

        Title:      MPLS/BGP Layer 3 Virtual Private 
                    Network (VPN) Management Information Base 
        Author:     T. Nadeau,  Ed., 
                    H. van der Linde,  Ed.
        Status:     Standards Track
        Date:       February 2006
        Mailbox:    tnadeau@cisco.com, 
                    havander@cisco.com
        Pages:      44
        Characters: 85594
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l3vpn-mpls-vpn-mib-07.txt

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

This memo defines a portion of the Management
Information Base (MIB) for use with network management protocols
in the Internet community.  In particular, it describes managed
objects to configure and/or monitor Multiprotocol Label
Switching Layer-3 Virtual Private Networks on a
Multiprotocol Label Switching (MPLS) Label Switching Router
(LSR) supporting this feature.  [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 Sat Feb 11 05:01:17 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F7rZ7-0004nV-Ep; Sat, 11 Feb 2006 05:01:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F7rZ5-0004lC-GP
	for l3vpn@megatron.ietf.org; Sat, 11 Feb 2006 05:01:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22881
	for <l3vpn@ietf.org>; Sat, 11 Feb 2006 04:59:16 -0500 (EST)
Received: from zproxy.gmail.com ([64.233.162.198])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F7rm0-0008Rn-Qe
	for l3vpn@ietf.org; Sat, 11 Feb 2006 05:14:38 -0500
Received: by zproxy.gmail.com with SMTP id n1so640900nzf
	for <l3vpn@ietf.org>; Sat, 11 Feb 2006 02:00:53 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=EUbr4FoiDpXV4V04Jo+A26NATg/ws7eV8NMt8SRQNXss1IAioJSAdhBUM4I7epc8TfIr6+mPwyLhWsfr7fEPfv3N32X8vFR/zfJpI5gZtv2INiX4iMk1L75XxNPtKIpG+ymN45P2dGhRNUyrRQUIuLpHtJI/bbloM6KvgEufOz8=
Received: by 10.36.36.9 with SMTP id j9mr413186nzj;
	Sat, 11 Feb 2006 02:00:52 -0800 (PST)
Received: by 10.36.32.15 with HTTP; Sat, 11 Feb 2006 02:00:51 -0800 (PST)
Message-ID: <255a24600602110200t6b8fa7b8x6eefbfa13842acdb@mail.gmail.com>
Date: Sat, 11 Feb 2006 15:30:51 +0530
From: Roopa Hegde <roopavb@gmail.com>
To: l3vpn@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_3555_28368460.1139652051759"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Subject: Info regarding Management 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>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

------=_Part_3555_28368460.1139652051759
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,
This is regarding rules for configuring management VPNs in l3vpns. Accordin=
g
to rfc2547bis, it just suggests a hub-and-spoke with the management station
being the hub and the managed PE's as the spoke. Is this a rule everyone
MUST follow? Can a service provider configure them as a mesh? Are there
rules for the number of route targets to be used for this? A hub-and-spoke
can be created with just 1,2 or any number of route targets. Can the VRF
containing managment route targets also contain traffic route targets?

Does anyone know what is the most popular configuration followed?

Thanks in advance,
Roopa.

------=_Part_3555_28368460.1139652051759
Content-Type: text/html; charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

<div>Hi,&nbsp;&nbsp; </div>
<div>This is regarding rules for configuring management VPNs in l3vpns. Acc=
ording to rfc2547bis, it just suggests a hub-and-spoke with the management =
station being the hub and the managed PE's as the spoke. Is this a rule eve=
ryone MUST follow? Can a service provider configure them as a mesh? Are the=
re rules for the number of route targets to be used for this? A hub-and-spo=
ke can be created with just 1,2 or any number of route targets.&nbsp;Can th=
e VRF containing managment route targets also contain traffic route targets=
?
</div>
<div>&nbsp;</div>
<div>Does anyone know what is&nbsp;the most popular&nbsp;configuration foll=
owed?</div>
<div>&nbsp;</div>
<div>Thanks in advance,</div>
<div>Roopa.</div><span class=3D"sg">
<div>&nbsp;</div></span>

------=_Part_3555_28368460.1139652051759--




From l3vpn-bounces@ietf.org Wed Feb 15 08:35:44 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F9Mop-0006R6-SO; Wed, 15 Feb 2006 08:35:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F9Moo-0006R1-BY
	for l3vpn@megatron.ietf.org; Wed, 15 Feb 2006 08:35:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09454
	for <l3vpn@ietf.org>; Wed, 15 Feb 2006 08:33:55 -0500 (EST)
Received: from szxga02-in.huawei.com ([61.144.161.54] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F9N2k-00020O-5U
	for l3vpn@ietf.org; Wed, 15 Feb 2006 08:50:12 -0500
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 <0IUQ00M04DXPQW@szxga02-in.huawei.com> for
	l3vpn@ietf.org; Wed, 15 Feb 2006 21:39:25 +0800 (CST)
Received: from lotus9jxeof3f7 ([219.236.78.49])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0IUQ00B8ZDXHP9@szxga02-in.huawei.com> for
	l3vpn@ietf.org; Wed, 15 Feb 2006 21:39:25 +0800 (CST)
Date: Thu, 06 Oct 2005 21:29:30 +0800
From: Xiaohu Xu <xuxh@huawei.com>
To: "Thomas D. Nadeau" <tnadeau@cisco.com>
Message-id: <003e01c63233$81f0ca40$314eecdb@lotus9jxeof3f7>
Organization: Huawei Technology Co.,Ltd.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
Content-type: text/plain; charset=Windows-1252
Content-transfer-encoding: base64
X-Priority: 3
X-MSMail-priority: Normal
References: <4e0fe54dd5d8.4dd5d84e0fe5@huawei.com>
	<6413EC4C-2984-467B-9494-042BD95E2B88@cisco.com>
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Content-Transfer-Encoding: base64
Cc: cli@futurewei.com, l3vpn@ietf.org, sdawkins@futurewei.com
Subject: Re: Multicast in BGP/MPLS VPN with pseudo wires technology
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>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

SGksIFRob21hcw0KDQpUaGFua3MgYSBsb3QgZm9yIHlvdXIgcmVzcG9uc2UuDQoNClRFIHR1bm5l
bHMgZXN0YWJsaXNoZWQgYmV0d2VlbiBhIHBhaXIgb2YgIFBFcyBkZXN0aW5lZCB0byBlYWNoIG90
aGVyIGFyZSB1bmlkaXJlY3Rpb25hbCBhbmQgZGlzcmVsYXRlZC4gQXMgcGFja2V0cyBhcmUgcmVj
ZWl2ZWQgb3ZlciBURSB0dW5uZWwgYnkgZWdyZXNzIExTUiwgIGl0IGNhbiBub3QgYmUgZGV0ZXJt
aW5lZCBmcm9tIHdoaWNoIFZQTiBhbmQgZnJvbSB3aGljaCBQRSB0aGVzZSBwYWNrZXRzIGFyZSB0
cmFuc2ltaXR0ZWQuIFBXcyBhcmUgYmlkaXJlY3Rpb25hbCB2aXJ0dWFsIGxpbmsgIGJldHdlZW4g
ZWFjaCBwYWlyIG9mIFBFcyBhbmQgYXJlIGJvdW5kIHRvIGEgcGFydGljdWxhciBWUkYsICBBcyBw
YWNrZXRzIGFyZSByZWNlaXZlZCBvdmVyIFBXIGJ5IGVncmVzcyBMU1IsICBpdCBjYW4gbm90IGJl
IGRldGVybWluZWQgZnJvbSB3aGljaCBWUE4gYW5kIGZyb20gd2hpY2ggaW5ncmVzcyBQRSB0aGVz
ZSBwYWNrZXRzIGFyZSB0cmFuc2ltaXR0ZWQgYWNjb3JkaW5nIHRvIHRoZSBWUE4gbGFiZWwgaW5m
by4gIE9mIGNvdXJjZSwgYmlkaXJlY3Rpb25hbCBSU1ZQLVRFIHR1bm5lbCAgZGVzY3JpYmVkIGlu
IG15IHByZXZpb3VzIGVtYWlsIGNhbiBhbHNvIGJlIHVzZWQgdG8gcmVhbGl6ZSB0aGUgYWJvdmUg
Z29hbC4NCg0KICAgIA0KLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCkZyb206ICJUaG9t
YXMgRC4gTmFkZWF1IiA8dG5hZGVhdUBjaXNjby5jb20+DQpUbzogInh1eGlhb2h1IDQxMjA4IiA8
eHV4aEBodWF3ZWkuY29tPg0KQ2M6IDxsM3ZwbkBpZXRmLm9yZz47IDxjbGlAZnV0dXJld2VpLmNv
bT47IDxzZGF3a2luc0BmdXR1cmV3ZWkuY29tPg0KU2VudDogVGh1cnNkYXksIE9jdG9iZXIgMDYs
IDIwMDUgODozMiBQTQ0KU3ViamVjdDogUmU6IE11bHRpY2FzdCBpbiBCR1AvTVBMUyBWUE4gd2l0
aCBwc2V1ZG8gd2lyZXMgdGVjaG5vbG9neQ0KDQoNCg0KDQo+IERlYXIgbWVtYmVycyBvZiB0aGUg
bDN2cG4gZGlzdHJpYnV0aW9uIGxpc3Q6DQo+DQo+IEkgd2FudCB0byBpbnRyb2R1Y2UgYSBuZXcg
bWV0aG9kIG9mIGltcGxlbWVudGluZyBNVlBOIGluIDI1NDdiaXMgIA0KPiBWUE4gd2l0aCBwc2V1
ZG8gd2lyZXMgdGVjaG5vbG9neSwgYW55IGNvbW1lbnQgZnJvbSB5b3Ugd2lsbCBiZSAgDQo+IGV4
cGVjdGVkLg0KPg0KPiBUaGUgYmFzaWMgcHJvY2VkdXJlcyBhcmUgYXMgZm9sbG93czogZmlyc3Qs
IGRpc2NvdmVyIGFsbCB0aGUgUEVzICANCj4gd2hpY2ggaXMgYXR0YWNoZWQgdG8gYSBwYXJ0aWN1
bGFyIE1WUE4gdmlhIEJHUDsNCg0KICAgICBDYW4geW91IGV4cGxhaW4gd2h5IHRoaXMgaXMgZGlm
ZmVyZW50IGZyb20gdGhlIGFscmVhZHkNCmRlcGxveWVkIGFwcHJvYWNoIHdoZXJlIFRFIHR1bm5l
bHMgYXJlIGVzdGFibGlzaGVkIGJldHdlZW4NClBFcz8NCg0KPiBzZWNvbmQsIEZ1bGwtbWVzaGVk
IHBzZXVkbyB3aXJlcyAoUFcpIGFyZSBlc3RhYmxpc2hlZCBhbW9uZyB0aGUgIA0KPiBhYm92ZSBQ
RXMsIGFuZCB0aGVzZSBQV3MgYXJlIGJvdW5kIHRvIGEgcGFydGljdWxhciBNVlJGIHJlbGF0ZWQg
dG8gIA0KPiB0aGUgYWJvdmUgTVZQTjsNCg0KICAgICBJIGFtIGludGVyZXN0ZWQgdG8gaGVhciBm
cm9tIG9wZXJhdG9ycyB3aGV0aGVyIHRoZXkgdGhpbmsNCm9mIHRoaXMgYXBwcm9hY2ggaW4gdGhl
IGNvbnRleHQgb2Ygb3BlcmF0aW9uYWwgaXNzdWVzLg0KDQogICAgIC0tVG9tDQoNCj4gbGFzdGx5
LCBtdWx0aWNhc3QgY29udHJvbCBtZXNzYWdlcyBhbmQgbXVsdGljYXN0IGRhdGEgdHJhZmZpY2Vz
IGNhbiAgDQo+IGJlIHRyYW5zbWl0dGVkIHRocm91Z2ggdGhvc2UgUFdzLg0KPg0KPiBUaGUgbWFp
biBhZHZhbnRhZ2VzIG9mIHRoaXMgbWV0aG9kIGlzIGFzIGZvbGxvd3M6DQo+IEZpcnN0LGl0IGlz
IGluZGVwZW5kYW50IHdpdGggbXVsdGljYXN0IHJvdXRpbmcgcHJvdG9jb2xzIGFuZCBhbnkgIA0K
PiBraW5kIG9mIGN1cnJlbnQgbXVsdGljYXN0IHJvdXRpbmcgcHJvdG9jb2xzLCBpbmNsdWRpbmcg
UElNLVNNLCBQSU0tIA0KPiBTU00gYW5kIFBJTS1ETSBjYW4gcnVuIG92ZXIgc3VjaCBNVlBOLg0K
PiBTZWNvbmQsIG11bHRpY2FzdCBpcyBub3QgcmVxdWlyZWQgaW4gUCBkZXZpY2VzLiBJdCdzIGVh
c3kgdG8gIA0KPiBtYWludGFpbiBzdWNoIE1WUE4gYW5kIGl0IGlzIGdvb2QgZm9yIHByb3RlY3Rp
bmcgb3JpZ2luYWwgaW52ZXN0bWVudC4NCj4gVGhpcmQsIHJlcGxpY2F0aW9uIG9uIFBFIGNhbiBz
aGFyZSB0aGUgYnVyZGVuIG9uIFAgcm91dGVyIHdoaWNoIGlzICANCj4gYSBodWIgaW4gaHViLXNw
b2tlIG5ldHdvcmsgdG9wb2xvZ3kuDQo+DQo+DQo+IFRoZSBtYWluIGRpZmZlcm5lY2Ugd2l0aCBk
cmFmdC1pZXRmLWwzdnBuLTI1NDdiaXMtbWNhc3QtMDAudHh0IChNYXkgIA0KPiAyMDA1KSBsaWVz
IGluIHRoZSBkZW11bHRpcGxleG9yLg0KPg0KPiBUaGUgZGVzY3JpcHRpb24gYWJvdXQgZGVtdWx0
aXBsZXhvciBpbiBkcmFmdC1pZXRmLWwzdnBuLTI1NDdiaXMtIA0KPiBtY2FzdC0wMC50eHQgaXMg
YXMgZm9sbG93czoNCj4NCj4gIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIw0KPg0K
PiBJZiBtdWx0aWNhc3QgY29udHJvbCBpbmZvcm1hdGlvbiBpcyB0byBiZSB1bmljYXN0LCByYXRo
ZXINCj4NCj4gdGhhbiBzZW50IG9uIGFuIE1JLVBNU0ksIHRoZW4gYSBkZW11bHRpcGxleG9yIHZh
bHVlIG11c3QNCj4NCj4gYmUgY2FycmllZCBieSB0aGUgY29udHJvbCBtZXNzYWdlcyBpbiBvcmRl
ciB0byBpZGVudGlmeQ0KPg0KPiB0aGUgcGFydGljdWxhciBNVlBOIHRvIHdoaWNoIHRoZSBjb250
cm9sIG1lc3NhZ2UgYmVsb25ncy4NCj4NCj4gVGhlIGZvcm0gb2YgdGhpcyBkZW11bHRpcGxleG9y
IGlzIG5vdCB5ZXQgYWdyZWVkIHVwb24sDQo+DQo+IGJ1dCBvbmUgcG9zc2liaWxpdHkgaXMgYSBk
b3duc3RyZWFtLWFzc2lnbmVkIE1QTFMgbGFiZWwuDQo+DQo+IElmIHRoaXMgcHJvY2VkdXJlIGlz
IGFkb3B0ZWQsIHRoaXMgbGFiZWwgd291bGQgYmUgY2FycmllZA0KPg0KPiBpbiB0aGUgQkdQIHVw
ZGF0ZSBtZXNzYWdlLiBUaGUgUEUgb3JpZ2luYXRpbmcgdGhlIEJHUA0KPg0KPiB1cGRhdGUgbWVz
c2FnZSB3b3VsZCBzcGVjaWZ5IHRoZSBsYWJlbCB3aGljaCBpdCBleHBlY3RzDQo+DQo+IHRvIHNl
ZSBvbiByZWNlaXZlZCBjb250cm9sIHBhY2tldHMgZm9yIHRoZSBzcGVjaWZpZWQgTVZQTi4NCj4N
Cj4gIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIw0KPg0KPg0KPiBJbiB0aGUgYWJv
dmUgZGVzY3JpcHRpb24sIGEgZGVtdWx0aXBsZXhvciBpcyB1c2VkIHRvIGRpc3Rpbmd1aXNoICAN
Cj4gZGlmZmVyZW50IE1WUE4gc3RyZWFtcyBvZiB0cmFmZmljIGNhcnJpZWQgb3ZlciBhIHR1bm5l
bC4gQnV0IGluIG15ICANCj4gaW1wbGVtZW50aW9uIG9mIE1WUE4sIHRoZSBkZW11bHRpcGxleG9y
IG5vdCBvbmx5IHNheXMgdG8gd2hpY2ggIA0KPiBzcGVjaWZpYyBNVlBOIGEgcGFja2V0IGJlbG9u
Z3MsIGJ1dCBhbHNvIGlkZW50aWZpZXMgdGhlIGluZ3Jlc3MgUEUuICANCj4gRm9yIHRoaXMgcmVh
c29uLCB0aGVyZSBpcyBubyBuZWVkIHRvIGNhcnJ5IGluZ3Jlc3MgUEWScyBhZGRyZXNzIGluICAN
Cj4gbXVsdGljYXN0IHRyYWZmaWMgd2l0aCBhIHNwZWNpYWwgZW5jYXBzdWxhdGlvbiBzdWNoIGFz
IEdSRSBmb3IgdGhlICANCj4gcHVycG9zZSBvZiBSUEYgY2hlY2tpbmcgYW5kIG90aGVyIHVzZXMu
IFRoZSBkZXQNCj4gYWlscyBhYm91dCBlbmNhcHN1bGF0aW9uIGFyZSBzcGVjaWFmaWVkIGluIHNl
Y3Rpb24gMTEgb2YgdGhlIGRyYWZ0ICANCj4gbWVudGlvbmVkIGFib3ZlLg0KPg0KPiBUaGF0IGlz
IHRvIHNheSxpbiBteSBpbXBsZW1lbnRpb24gb2YgTVZQTiwgZWFjaCBQRSB3aWxsIGFzc2lnbiBh
ICANCj4gdW5pcXVlIGxhYmVsIHRvIGV2ZXJ5IG9uZSBvZiB0aGUgb3RoZXIgUEVzIHdpdGhpbiB0
aGUgYWJvdmUgTVZQTiwgIA0KPiBhbmQgdGhvc2UgdW5pcXVlIGxhYmVscyBhcmUgYXNzb2NpYXRl
ZCB0byBhIHBhcnRpY3VsYXIgTVZSRiByZWxhdGVkICANCj4gdG8gdGhlIGFib3ZlIE1WUE4uIFRo
ZXNlIFBXcyBjYW4gYmUgbG9va2VkIGFzIHZpcnR1YWwgaW50ZXJmYWNlcyAgDQo+IGJldHdlZW4g
ZWFjaCBwYWlyIG9mIHRoZSBhYm92ZSBQRXMsIHdoaWNoIGFyZSBib3VuZCB0byBhIHBhcnRpY3Vs
YXIgIA0KPiBNVlJGLg0KPg0KPiBUaGVzZSBQV3MgbWVudGlvbmVkIGFib3ZlIGNvdWxkIGJlIGVz
dGFibGlzaGVkIHZpYSBCR1Agb3IgdGFyZ2V0ZWQgIA0KPiBMRFAgLg0KPg0KPiBPZiBjb3Vyc2Us
IEJHUCBpcyBzdGlsbCBjYW4gYmUgdXNlZCB0byBjYXJyeSBQSU0gQy1pbnN0YW5jZSBjb250cm9s
ICANCj4gbWVzc2FnZSBhZnRlciB0aGUgUFdzIGFyZSBlYXRhYmxpc2hlZCBiZXR3ZWVuIGVhY2gg
cGFpciBvZiBQRXMgIA0KPiB3aXRoaW4gdGhlIHNhbWUgTVZQTi4gVGhhdCBpcyB0byBzYXksIFBJ
TSBDLWluc3RhbmNlIGNvbnRyb2wgIA0KPiBtZXNzYWdlcyBjYW4gYmUgY2FycmllZCBpbiBCR1Ag
dXBkYXRlcyBhbmQgbXVsdGljYXN0IHRyYWZmaWNzIGNhbiAgDQo+IHRyYXZlbCBvdmVyIFBXcy4N
Cj4NCj4NCj4gU2luY2VyZWx5DQo+DQo+IFN0ZXZlbiBKb2UNCj4NCj4gSHVhd2VpIFRlY2hub2xv
Z2llcyBDby4sTHRkLg0KPg0KPiBFbWFpbDogeHV4aEBodWF3ZWkuY29tDQo+DQo+DQo+DQo+





From l3vpn-bounces@ietf.org Thu Feb 16 00:09:07 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F9bO5-0000Ss-AF; Thu, 16 Feb 2006 00:09:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F9bO2-0000SN-SS
	for l3vpn@megatron.ietf.org; Thu, 16 Feb 2006 00:09:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14866
	for <l3vpn@ietf.org>; Thu, 16 Feb 2006 00:06:38 -0500 (EST)
Received: from usjk1001.kddi.com ([211.4.169.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F9bbV-0003cG-1j
	for l3vpn@ietf.org; Thu, 16 Feb 2006 00:23:03 -0500
Received: from usjk1035.kddi.com ([10.96.2.25])
	by usjk1001.kddi.com  with ESMTP id k1G56l803539
	for <l3vpn@ietf.org>; Thu, 16 Feb 2006 14:06:47 +0900 (JST)
Received: from usjk1039 (localhost [127.0.0.1])
	by usjk1035.kddi.com  with SMTP id k1G56kD06826
	for <l3vpn@ietf.org>; Thu, 16 Feb 2006 14:06:47 +0900 (JST)
Received: from [127.0.0.1] ([133.128.75.50]) by usjk1009.kddi.com
	(InterMail vM.5.01.02.00 201-253-116-121-20001201) with ESMTP
	id <20060216050634.NVYH23807.usjk1009.kddi.com@[127.0.0.1]>
	for <l3vpn@ietf.org>; Thu, 16 Feb 2006 14:06:34 +0900
Date: Thu, 16 Feb 2006 14:06:25 +0900
From: Kenji Kumaki <ke-kumaki@kddi.com>
To: l3vpn@ietf.org
Message-Id: <20060216140303.CD35.KE-KUMAKI@kddi.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="------_43F40787CD32010CEF68_MULTIPART_MIXED_"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.21.03 [ja]
X-WAuditID: 0602161406340000218564
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 72dbfff5c6b8ad2b1b727c13be042129
Subject: Fw: I-D ACTION:draft-kumaki-l3vpn-e2e-rsvp-te-reqts-00.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>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

--------_43F40787CD32010CEF68_MULTIPART_MIXED_
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Hi,

I submitted the following draft to L3VPN WG.
I welcome your comments and feedbacks on this list.

Thanks,
Kenji

Forwarded by Kenji Kumaki <ke-kumaki@kddi.com>
----------------------- Original Message -----------------------
 From:    Internet-Drafts@ietf.org
 To:      i-d-announce@ietf.org
 Date:    Wed, 15 Feb 2006 15:50:02 -0500
 Subject: I-D ACTION:draft-kumaki-l3vpn-e2e-rsvp-te-reqts-00.txt 
----

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Requirements for delivering MPLS Services Over L3VPN 

	Author(s)	: K. Kumaki
	Filename	: draft-kumaki-l3vpn-e2e-rsvp-te-reqts-00.txt
	Pages		: 12
	Date		: 2006-2-15
	
This document describes Service Provider requirements for providing 
end-to-end MPLS TE LSPs over L3VPN. 
    
The main objective is to present a set of requirements which result 
in general guidelines for the definition, selection and specification 
of a technical solution addressing these requirements. 
Specification for this solution itself is out of scope in this 
document. 


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-kumaki-l3vpn-e2e-rsvp-te-reqts-00.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-kumaki-l3vpn-e2e-rsvp-te-reqts-00.txt".

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


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

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

--------------------- Original Message Ends --------------------

-- 
Kenji Kumaki <ke-kumaki@kddi.com>


--------_43F40787CD32010CEF68_MULTIPART_MIXED_
Content-Type: message/rfc822
Content-Description: I-D ACTION:draft-kumaki-l3vpn-e2e-rsvp-te-reqts-00.txt 

Return-Path: <i-d-announce-bounces@ietf.org>
Received: from usjk1039 ([10.96.2.28]) by usjk1009.kddi.com (InterMail
	vM.5.01.02.00 201-253-116-121-20001201) with SMTP id
	<20060215210626.JVZC23807.usjk1009.kddi.com@usjk1039>;
	Thu, 16 Feb 2006 06:06:26 +0900
Received: from usjk1004.kddi.com (localhost [127.0.0.1]) by usjk1006.kddi.com
	with ESMTP id k1FL6MP23532; Thu, 16 Feb 2006 06:06:22 +0900 (JST)
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by
	usjk1004.kddi.com with ESMTP id k1FL6Ip20889;
	Thu, 16 Feb 2006 06:06:19 +0900 (JST)
Received: from localhost.cnri.reston.va.us ([127.0.0.1]
	helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim
	4.32) id 1F9TbO-0000Kf-Jt; Wed, 15 Feb 2006 15:50:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by
	megatron.ietf.org with esmtp (Exim 4.32) id 1F9TbH-0000Ir-JN
	for i-d-announce@megatron.ietf.org; Wed, 15 Feb 2006 15:50:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org
	(8.9.1a/8.9.1a) with ESMTP id PAA00193 for
	<i-d-announce@ietf.org>; Wed, 15 Feb 2006 15:48:23 -0500 (EST)
Received: from pine.neustar.com ([209.173.57.70]) by ietf-mx.ietf.org with
	esmtp (Exim 4.43) id 1F9TpM-00083M-VE for i-d-announce@ietf.org;
	Wed, 15 Feb 2006 16:04:45 -0500
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 k1FKo2vP008262 (version=TLSv1/SSLv3
	cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for
	<i-d-announce@ietf.org>; Wed, 15 Feb 2006 20:50:02 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id
	1F9Tb8-0005lu-1R for i-d-announce@ietf.org;
	Wed, 15 Feb 2006 15:50:02 -0500
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1F9Tb8-0005lu-1R@stiedprstage1.ietf.org>
Date: Wed, 15 Feb 2006 15:50:02 -0500
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Subject: I-D ACTION:draft-kumaki-l3vpn-e2e-rsvp-te-reqts-00.txt 
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: i-d-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
Sender: i-d-announce-bounces@ietf.org
Errors-To: i-d-announce-bounces@ietf.org
X-WAuditID: 0602160606220000209943
Content-Type: Multipart/Mixed; Boundary="NextPart"

--NextPart
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Requirements for delivering MPLS Services Over L3VPN 

	Author(s)	: K. Kumaki
	Filename	: draft-kumaki-l3vpn-e2e-rsvp-te-reqts-00.txt
	Pages		: 12
	Date		: 2006-2-15
	
This document describes Service Provider requirements for providing 
end-to-end MPLS TE LSPs over L3VPN. 
    
The main objective is to present a set of requirements which result 
in general guidelines for the definition, selection and specification 
of a technical solution addressing these requirements. 
Specification for this solution itself is out of scope in this 
document. 


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-kumaki-l3vpn-e2e-rsvp-te-reqts-00.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-kumaki-l3vpn-e2e-rsvp-te-reqts-00.txt".

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-kumaki-l3vpn-e2e-rsvp-te-reqts-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-kumaki-l3vpn-e2e-rsvp-te-reqts-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"
Content-Disposition: attachment;
	filename="draft-kumaki-l3vpn-e2e-rsvp-te-reqts-00.txt"
Content-Transfer-Encoding: 7bit

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


--OtherAccess--

--NextPart
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

--NextPart--

--------_43F40787CD32010CEF68_MULTIPART_MIXED_--






From l3vpn-bounces@ietf.org Thu Feb 16 10:58:05 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F9lW9-0005Uu-0h; Thu, 16 Feb 2006 10:58:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F9lW5-0005Rx-Rv; Thu, 16 Feb 2006 10:58:01 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06926;
	Thu, 16 Feb 2006 10:56:11 -0500 (EST)
Received: from bgslc11.burtongroup.com ([63.99.125.13])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F9lkF-0002xF-B7; Thu, 16 Feb 2006 11:12:43 -0500
Received: bgslc11.burtongroup.com 63.99.125.13 from 216.151.229.244
	216.151.229.244 via HTTP with MS-WebStorage 6.0.6249
User-Agent: Microsoft-Entourage/11.2.1.051004
Date: Thu, 16 Feb 2006 10:57:44 -0500
From: Irwin Lazar <ilazar@burtongroup.com>
To: <ccamp@ops.ietf.org>, L2VPN <l2vpn@ietf.org>, <mpls@ietf.org>,
	<l3vpn@ietf.org>, <pwe3@ietf.org>
Message-ID: <C01A0B28.1D0F9%ilazar@burtongroup.com>
Thread-Topic: MPLScon 2006 Program
Thread-Index: AcYzEbkg99xz9p8EEdqUmAAKlZoW5A==
Mime-version: 1.0
Content-type: multipart/alternative;
	boundary="B_3222932264_1089758"
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: 
Subject: MPLScon 2006 Program
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>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3222932264_1089758
Content-type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

The program for MPLScon 2006 is now available at
http://www.mplscon.com/attend/conf_at_a_glance.html

MPLScon 2006 takes place May 22-26 at the Marriott Financial Center in NYC,
NY.

Please let me know if you have any questions.

Irwin


-- 
Irwin Lazar, Conference Director, MPLScon
http://www.mplscon.com
ilazar@burtongroup.com
Phone: 703-742-9659
AIM/iChat/Google/MSN/Gizmo/Skype/Yahoo: imlazar



--B_3222932264_1089758
Content-type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>MPLScon 2006 Program</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:12.0px'>The p=
rogram for MPLScon 2006 is now available at <a href=3D"http://www.mplscon.com/=
attend/conf_at_a_glance.html">http://www.mplscon.com/attend/conf_at_a_glance=
.html</a><BR>
<BR>
MPLScon 2006 takes place May 22-26 at the Marriott Financial Center in NYC,=
 NY.<BR>
<BR>
Please let me know if you have any questions.<BR>
<BR>
Irwin<BR>
<BR>
<BR>
-- <BR>
Irwin Lazar, Conference Director, MPLScon<BR>
<a href=3D"http://www.mplscon.com">http://www.mplscon.com</a><BR>
ilazar@burtongroup.com<BR>
Phone: 703-742-9659<BR>
AIM/iChat/Google/MSN/Gizmo/Skype/Yahoo: imlazar<BR>
<BR>
</SPAN></FONT>
</BODY>
</HTML>


--B_3222932264_1089758--





From l3vpn-bounces@ietf.org Fri Feb 17 18:50:33 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1FAFMv-0002Br-18; Fri, 17 Feb 2006 18:50:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1FAFMb-0001xe-Qx; Fri, 17 Feb 2006 18:50:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25549;
	Fri, 17 Feb 2006 18:48:25 -0500 (EST)
Received: from cypress.neustar.com ([209.173.57.84])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FAFb6-0001JK-Hk; Fri, 17 Feb 2006 19:05:13 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by cypress.neustar.com (8.12.8/8.12.8) with ESMTP id k1HNo20e011035
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 17 Feb 2006 23:50:02 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FAFMQ-0004Oq-64; Fri, 17 Feb 2006 18:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1FAFMQ-0004Oq-64@stiedprstage1.ietf.org>
Date: Fri, 17 Feb 2006 18:50:02 -0500
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: l3vpn@ietf.org
Subject: I-D ACTION:draft-ietf-l3vpn-ospf-2547-06.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>
Sender: l3vpn-bounces@ietf.org
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		: OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP VPNs
	Author(s)	: E. Rosen
	Filename	: draft-ietf-l3vpn-ospf-2547-06.txt
	Pages		: 26
	Date		: 2006-2-17
	
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 draft-ietf-l3vpn-rfc2547bis-03.txt.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-ospf-2547-06.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-ospf-2547-06.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-ospf-2547-06.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-2-17151829.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l3vpn-ospf-2547-06.txt

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

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


--OtherAccess--

--NextPart--





From l3vpn-bounces@ietf.org Mon Feb 20 07:48:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FBASn-0005pC-G6; Mon, 20 Feb 2006 07:48:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FBASm-0005p7-67
	for l3vpn@ietf.org; Mon, 20 Feb 2006 07:48:24 -0500
Received: from lhrga01-in.huawei.com ([57.66.76.5] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBASl-0005ss-Mp
	for l3vpn@ietf.org; Mon, 20 Feb 2006 07:48:24 -0500
Received: from huawei.com ([172.24.2.3])
	by lhrga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IUZ00F6TJKY5M@lhrga01-in.huawei.com> for
	l3vpn@ietf.org; Mon, 20 Feb 2006 12:19:46 +0000 (GMT)
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IUZ00MOAKRITQ@szxga01-in.huawei.com> for
	l3vpn@ietf.org; Mon, 20 Feb 2006 20:45:18 +0800 (CST)
Received: from x41208b ([10.110.100.41])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0IUZ00GQ4KRGT4@szxga01-in.huawei.com> for
	l3vpn@ietf.org; Mon, 20 Feb 2006 20:45:18 +0800 (CST)
Date: Mon, 20 Feb 2006 20:35:02 +0800
From: Xiaohu Xu <xuxh@huawei.com>
To: erosen@cisco.com
Message-id: <007c01c6361a$128f7940$29646e0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
Content-type: multipart/alternative;
	boundary="Boundary_(ID_9gKBYnrW4o7lw2Mg2fygBQ)"
X-Priority: 3
X-MSMail-priority: Normal
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: l3vpn@ietf.org
Subject: RPF checking for fast convergence of MVPN
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.

--Boundary_(ID_9gKBYnrW4o7lw2Mg2fygBQ)
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT

Dear Eric,
 
In your last email to me, you said,
> When the upstream PE for an SPT changes, I am told that current practice is
> to immediately send a Join(S,G) toward the new PE and a Prune(S,G) toward
> the old PE. That is, the Prune(S,G) for the old tree is not delayed while
> waiting for data to be received on the new tree. Therefore one doesn't
> really have to know whether any given data packet came on the old SPT or the
> new one. 


The following is a digest from RFC2362 [PIM-SM]: 

   The router must send a Join/Prune message with S in the Join list out
   any new incoming interfaces to inform upstream routers that it
   expects multicast datagrams over the interface.  It may also send a
   Join/Prune message with S in the Prune list out the old incoming
   interface, if the link is operational, to inform upstream routers
   that this part of the distribution tree is going away.[on page 12 of RFC2362]

In the above description, it is not required to send a (S,G)prune to the old upstream as soon as a (S,G)join is sent to the new upstream. In addition, to reduce interruption duration and avoid duplicated packets during the switchover, special process should be taken just like what has be done for the smooth switchover from RPT to SPT.

As I had known, some Chinese telecom carriers had already put forward higher requirements for fast convergence of PIM-SM during some admittance testing in order to provide high-performance IPTV service to public.For example, no interruption is allowed during the switchover from the second best path to the best path. 

As MVPN is just used for enterprise business, fast convergence may be a small issue which can be neglected, but as it is being used for providing IPTV service to public, I think, fast convergence becomes a big issue. If the latter is true, RPF checking is needed for MVPN in case of ingress replication, that is to say, the egress PE should distinguish from which upstream PE the received data packet is transmitted.

More comments are expected from yourself and anybody else.

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


Best regards,

Xiaohu Xu

Email: xuxh@huawei.com

--Boundary_(ID_9gKBYnrW4o7lw2Mg2fygBQ)
Content-type: text/html; charset=gb2312
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=gb2312">
<META content="MSHTML 6.00.2800.1522" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>
<DIV><FONT size=2>Dear Eric,<BR>&nbsp;<BR>In your last email to me, you 
said,<BR>&gt; When the upstream PE for an SPT changes, I am told that current 
practice is<BR>&gt; to immediately send a Join(S,G) toward the new PE and a 
Prune(S,G) toward<BR>&gt; the old PE. That is, the Prune(S,G) for the old tree 
is not delayed while<BR>&gt; waiting for data to be received on the new tree. 
Therefore one doesn't<BR>&gt; really have to know whether any given data packet 
came on the old SPT or the<BR>&gt; new one. </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=2><BR>The following is&nbsp;a digest from RFC2362 [PIM-SM]: 
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=2>&nbsp;&nbsp; The router must send a Join/Prune message with S 
in the Join list out<BR>&nbsp;&nbsp; any new incoming interfaces to inform 
upstream routers that it<BR>&nbsp;&nbsp; expects multicast datagrams over the 
interface.&nbsp; It may also send a<BR>&nbsp;&nbsp; Join/Prune message with S in 
the Prune list out the old incoming<BR>&nbsp;&nbsp; interface, if the link is 
operational, to inform upstream routers<BR>&nbsp;&nbsp; that this part of the 
distribution tree is going away.[on page 12 of RFC2362]</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=2>In the above description, it is not required to send a 
(S,G)prune to the old upstream as soon as a (S,G)join is sent to the new 
upstream. In addition, to reduce interruption duration and avoid duplicated 
packets during the switchover, special process should be taken just like what 
has be done for the smooth switchover from RPT to SPT.</FONT></DIV>
<DIV><FONT size=2></FONT>&nbsp;</DIV>
<DIV><FONT size=2>As I&nbsp;had known, some Chinese telecom carriers had 
already&nbsp;put forward higher requirements for fast convergence of PIM-SM 
during some admittance testing in order to provide high-performance IPTV service 
to public.For example,&nbsp;no interruption&nbsp;is allowed&nbsp;during the 
switchover from the second best path to the best path. </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=2>As MVPN is just used for enterprise business, fast convergence 
may be a small issue which can be neglected, but as it is being used for 
providing IPTV service to public, I think, fast convergence becomes a big issue. 
If the latter is true, RPF checking is&nbsp;needed for MVPN in case of ingress 
replication, that is to say, the egress PE should distinguish from which 
upstream PE the received data packet is transmitted.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=2>More comments&nbsp;are expected from yourself&nbsp;and anybody 
else.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>A URL for&nbsp;my Internet-Draft is:<BR><A 
href="http://www.ietf.org/internet-drafts/draft-xu-l3vpn-2547bis-mcast-01.txt ">http://www.ietf.org/internet-drafts/draft-xu-l3vpn-2547bis-mcast-01.txt 
</A><BR></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=2>Best regards,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=2>Xiaohu Xu</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=2>Email: <A 
href="mailto:xuxh@huawei.com">xuxh@huawei.com</A></FONT></DIV></FONT></DIV></BODY></HTML>

--Boundary_(ID_9gKBYnrW4o7lw2Mg2fygBQ)--




From l3vpn-bounces@ietf.org Tue Feb 21 10:37:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FBZZY-0004sP-UI; Tue, 21 Feb 2006 10:37:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FBZZX-0004sH-4w; Tue, 21 Feb 2006 10:37:03 -0500
Received: from oak.neustar.com ([209.173.53.70])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FBZZV-0000JH-To; Tue, 21 Feb 2006 10:37:03 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k1LFb1BX019092
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 21 Feb 2006 15:37:01 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FBZZV-0007sb-Mp; Tue, 21 Feb 2006 10:37:01 -0500
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1FBZZV-0007sb-Mp@stiedprstage1.ietf.org>
Date: Tue, 21 Feb 2006 10:37:01 -0500
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: l3vpn@ietf.org
Subject: Last Call: 'Using BGP as an Auto-Discovery Mechanism for Layer-3
 and Layer-2 VPNs' to Proposed Standard 
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org
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 IESG has received a request from the Layer 3 Virtual Private Networks WG to 
consider the following document:

- 'Using BGP as an Auto-Discovery Mechanism for Layer-3 and Layer-2 VPNs '
   <draft-ietf-l3vpn-bgpvpn-auto-06.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2006-03-07.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-bgpvpn-auto-06.txt





