From l2vpn-bounces@ietf.org Sat Sep 01 09:33:03 2007
Return-path: <l2vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IRT46-00068N-Hh; Sat, 01 Sep 2007 09:31:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IRT45-00068C-7W
	for l2vpn@ietf.org; Sat, 01 Sep 2007 09:31:05 -0400
Received: from rv-out-0910.google.com ([209.85.198.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IRT44-0007VK-0z
	for l2vpn@ietf.org; Sat, 01 Sep 2007 09:31:05 -0400
Received: by rv-out-0910.google.com with SMTP id l15so567864rvb
	for <l2vpn@ietf.org>; Sat, 01 Sep 2007 06:31:03 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;
	b=Kh4Hj1udUMrGg4uk58zmr6eGfGUuqWWKmmsPjL0jZ4w9ZCZXKNOAvzaihaes+oJZWcSUPy/mHuKef1dI19QycpXWtX7IietUBxGyMK4VSbwtcsRqPq6RcpqnmSwT33B2yjVIqOU+UyABaHypZRFKsGJRpiL8DGIC30X47i7PgMM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=oHHXCGasURrY323dkwV41pVFdmsr+6EhRbAWWls+oYlGHUncj3qyN1H5exImidX6HicQwATMmpDTSeVyJM76QEHung2D/eo6sr0BwF1aDGXvLLkVFV+jxl2YXSDGsr60DXOG0Fujhk9IiHuSqEBOf52XPwfuXrpNdTpkwUC1Uzc=
Received: by 10.141.211.13 with SMTP id n13mr1152275rvq.1188653463359;
	Sat, 01 Sep 2007 06:31:03 -0700 (PDT)
Received: by 10.141.209.21 with HTTP; Sat, 1 Sep 2007 06:31:03 -0700 (PDT)
Message-ID: <37d984260709010631g24204fcbk8b4ceba233342890@mail.gmail.com>
Date: Sat, 1 Sep 2007 08:31:03 -0500
From: "Alireza salem" <salem.iust@gmail.com>
To: l2vpn@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_1421_7404098.1188653463340"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Subject: a question about VPLS
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l2vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=subscribe>
Errors-To: l2vpn-bounces@ietf.org

------=_Part_1421_7404098.1188653463340
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Dears
In general cases for a VPLS base VPN, Which method is better?
Autodiscovery with BGP or with LDP? If a SP(Service Provider) want to run
VPLS base VPNs in its network, what's suggessions about aotodiscovery?

Best Regards

------=_Part_1421_7404098.1188653463340
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>Dears</div>
<div>In general cases for a VPLS base VPN, Which method is better? </div>
<div>Autodiscovery with BGP or with LDP? If&nbsp;a SP(Service Provider)&nbsp;want to run VPLS base VPNs in its network, what&#39;s suggessions about aotodiscovery?</div>
<div>&nbsp;</div>
<div>Best Regards</div>

------=_Part_1421_7404098.1188653463340--




From l2vpn-bounces@ietf.org Wed Sep 05 14:52:51 2007
Return-path: <l2vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ISzxu-00020A-Ib; Wed, 05 Sep 2007 14:51:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ISp6j-0001td-CM
	for l2vpn@ietf.org; Wed, 05 Sep 2007 03:15:25 -0400
Received: from nf-out-0910.google.com ([64.233.182.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ISp6i-00020a-3B
	for l2vpn@ietf.org; Wed, 05 Sep 2007 03:15:25 -0400
Received: by nf-out-0910.google.com with SMTP id d3so1831300nfc
	for <l2vpn@ietf.org>; Wed, 05 Sep 2007 00:15:23 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;
	b=gW7PGCOXxbFpO9LVVX+TjCBQPyJrOoeOIX1RH506Q3nLw1/IneiuCMkKVQP70nQOf/tqJMO6AtxUOyGzg2+W/mpN481CpYh926QRXILL5I6gooDowC1/fEmqnrkX1fPnTb9H6YpojjPb0eZahoQUXuigYjhhyf8KP5ePGizYGFQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=Tv6x2vex2Wl7h7bO0moI3cIdqg9Mn+aomkZb02xOI4ANhipN4+roUPvC3nK0Rzxuug0VWDT9blUvwEgB58R78YdwZdoP3wKJ9iHL4EECwGAOsiL5DtbMRycye8h+umSQhpDVEn3JKCEMIpvzgWqoiGkOd0tsSCmCsCTuvp59D7s=
Received: by 10.78.171.13 with SMTP id t13mr4884807hue.1188976522755;
	Wed, 05 Sep 2007 00:15:22 -0700 (PDT)
Received: by 10.78.121.6 with HTTP; Wed, 5 Sep 2007 00:15:22 -0700 (PDT)
Message-ID: <d6d16f9c0709050015v7362c0c9p10e601e798e15b54@mail.gmail.com>
Date: Wed, 5 Sep 2007 12:45:22 +0530
From: "harish T" <harish0611@gmail.com>
To: l2vpn@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_27376_32183129.1188976522671"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
X-Mailman-Approved-At: Wed, 05 Sep 2007 14:51:00 -0400
Subject: VPN links
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l2vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=subscribe>
Errors-To: l2vpn-bounces@ietf.org

------=_Part_27376_32183129.1188976522671
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,

can anyone please let me know material which explains VRF,RT,RD concepts wrt
VPN.

-- 
------------------------------------------------------
To accomplish great things, we must not only act, but also dream; not only
plan, but also believe.



With regards
Harish.T

------=_Part_27376_32183129.1188976522671
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div><font face="Arial" size="2"><span class="953591207-05092007">Hi,</span></font></div>
<div><font face="Arial" size="2"><span class="953591207-05092007"></span></font>&nbsp;</div>
<div><font face="Arial" size="2"><span class="953591207-05092007">can anyone please 
let me know material which explains VRF,RT,RD concepts wrt VPN. <br></span></font></div><br>-- <br>------------------------------------------------------<br>To accomplish great things, we must not only act, but also dream; not only plan, but also believe.
<br><br><br><br>With regards<br>Harish.T

------=_Part_27376_32183129.1188976522671--




From l2vpn-bounces@ietf.org Thu Sep 06 22:04:16 2007
Return-path: <l2vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ITTAw-0002mm-1T; Thu, 06 Sep 2007 22:02:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ITTAv-0002gL-2f
	for l2vpn@ietf.org; Thu, 06 Sep 2007 22:02:25 -0400
Received: from dog.tcb.net ([64.78.150.133])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ITTAt-00035c-RM
	for l2vpn@ietf.org; Thu, 06 Sep 2007 22:02:25 -0400
Received: by dog.tcb.net (Postfix, from userid 0)
	id 9365F26870B; Thu,  6 Sep 2007 20:02:23 -0600 (MDT)
Received: from [172.16.15.25] (71-215-72-187.hlrn.qwest.net [71.215.72.187])
	(authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128)
	by dog.tcb.net with SMTP; for l2vpn@ietf.org;
	Thu, 06 Sep 2007 20:02:23 -0600 (MDT)
	(envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.72.187;
	client-port=4499; syn-fingerprint=65535:55:1:64:M1460,N,W0,N,N,T,S MacOS
	10.4.8; data-bytes=0
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: 7bit
Message-Id: <DC594520-76C5-487B-A233-0E7B94D8C007@castlepoint.net>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: l2vpn@ietf.org
From: Shane Amante <shane@castlepoint.net>
Date: Thu, 6 Sep 2007 20:01:50 -0600
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Subject: IETF 69: L2VPN WG Meeting Minutes
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l2vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=subscribe>
Errors-To: l2vpn-bounces@ietf.org

The following are meeting minutes of the IETF 69 L2VPN WG Meeting in  
Chicago, IL, USA:
http://www3.ietf.org/proceedings/07jul/minutes/l2vpn.txt

It appears the note-takers missed the name of a person, (currently  
noted as "Rashal"), asking questions at the mic during Florin's  
talk.  If anyone remembers who that was, please mail us so we can  
update the minutes accordingly.  Also, if you have other changes,  
please mail the chairs directly.

Thanks to Giles Heron & Ping Pan for taking minutes.

-shane & Vach






From l2vpn-bounces@ietf.org Sat Sep 08 12:29:54 2007
Return-path: <l2vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IU3A8-00031k-DO; Sat, 08 Sep 2007 12:28:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IU3A7-00031e-HG; Sat, 08 Sep 2007 12:27:59 -0400
Received: from dog.tcb.net ([64.78.150.133])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IU3A6-0000z0-5A; Sat, 08 Sep 2007 12:27:59 -0400
Received: by dog.tcb.net (Postfix, from userid 0)
	id E53D526879C; Sat,  8 Sep 2007 10:27:57 -0600 (MDT)
Received: from [172.16.15.25] (71-215-91-242.hlrn.qwest.net [71.215.91.242])
	(authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128)
	by dog.tcb.net with SMTP; Sat, 08 Sep 2007 10:27:57 -0600 (MDT)
	(envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.91.242;
	client-port=2992; syn-fingerprint=65535:55:1:64:M1460,N,W0,N,N,T,S MacOS
	10.4.8; data-bytes=0
Mime-Version: 1.0 (Apple Message framework v752.2)
To: Townsley Mark <townsley@cisco.com>,
	WG Milestone Tracker <iesg-secretary@ietf.org>
Message-Id: <237485CB-F304-419F-B1DD-D33E05A036E1@castlepoint.net>
Content-Type: multipart/mixed; boundary=Apple-Mail-9-508264324
From: Shane Amante <shane@castlepoint.net>
Date: Sat, 8 Sep 2007 10:27:41 -0600
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 325b777e1a3a618c889460b612a65510
Cc: l2vpn@ietf.org, jari.arkko@piuha.net,
	Vach Kompella <vach.kompella@alcatel.com>
Subject: Please publish draft-ietf-l2vpn-vpls-mcast-reqts-04.txt
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l2vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=subscribe>
Errors-To: l2vpn-bounces@ietf.org


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

Please publish draft-ietf-l2vpn-vpls-mcast-reqts-04.txt as an  
Informational RFC.

Attached is the Document Shepherd write-up.

Thanks,

-shane


--Apple-Mail-9-508264324
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; x-unix-mode=0644;
	name=draft-ietf-l2vpn-vpls-mcast-reqts-04-proto.txt
Content-Disposition: attachment;
	filename=draft-ietf-l2vpn-vpls-mcast-reqts-04-proto.txt

PROTO Statement: draft-ietf-l2vpn-vpls-mcast-reqts-04=0D
=0D
The L2VPN Chairs would like to request publication of this document as =
Informational.=0D
=0D
   (1.a)  Who is the Document Shepherd for this document?  Has the=0D
          Document Shepherd personally reviewed this version of the=0D
          document and, in particular, does he or she believe this=0D
          version is ready for forwarding to the IESG for publication?=0D=

=0D
Shane Amante (shane@castlepoint.net) is the Document Shepherd.  I have =
reviewed the document and it is ready for publication.=0D
=0D
=0D
   (1.b)  Has the document had adequate review both from key WG members=0D=

          and from key non-WG members?  Does the Document Shepherd have=0D=

          any concerns about the depth or breadth of the reviews that=0D
          have been performed?=0D
=0D
The document has been reviewed by the WG, during the WG Last Call, and =
through IETF L2VPN WG meetings.  There were some comments received =
during WG Last Call with respect to allowing: proxying certain multicast =
control protocols, circumstances under which frame reordering cannot be =
prevented (when switching over from one tree to another) and allowing =
multicast service activation at a customer IP address level (in addition =
to a MAC address level).  All of these comments have been addressed =
satisfactorily by the authors in the current, published version of this =
document.=0D
=0D
I have no concerns about the state of readiness of this document.=0D
=0D
=0D
   (1.c)  Does the Document Shepherd have concerns that the document=0D
          needs more review from a particular or broader perspective,=0D
          e.g., security, operational complexity, someone familiar with=0D=

          AAA, internationalization, or XML?=0D
=0D
Several Service Providers and Vendors have contributed to and reviewed =
the requirements contained in this document.  I have no concerns about =
this document, and believe it does not require further reviews from a =
broader perspective.=0D
=0D
=0D
   (1.d)  Does the Document Shepherd have any specific concerns or=0D
          issues with this document that the Responsible Area Director=0D=

          and/or the IESG should be aware of?  For example, perhaps he=0D=

          or she is uncomfortable with certain parts of the document, or=0D=

          has concerns whether there really is a need for it.  In any=0D
          event, if the WG has discussed those issues and has indicated=0D=

          that it still wishes to advance the document, detail those=0D
          concerns here.  Has an IPR disclosure related to this document=0D=

          been filed?  If so, please include a reference to the=0D
          disclosure and summarize the WG discussion and conclusion on=0D=

          this issue.=0D
=0D
I have no specific concerns about this document, nor are there any =
concerns that should be conveyed to the IESG or the Responsible AD.=0D
=0D
=0D
   (1.e)  How solid is the WG consensus behind this document?  Does it=0D=

          represent the strong concurrence of a few individuals, with=0D
          others being silent, or does the WG as a whole understand and=0D=

          agree with it?=0D
=0D
This document is well understood and has broad support by the L2VPN WG.  =
This document is widely recognized by the WG as a valuable contribution =
intended to shape L2VPN WG mutlicast solutions.=0D
=0D
=0D
   (1.f)  Has anyone threatened an appeal or otherwise indicated extreme=0D=

          discontent?  If so, please summarize the areas of conflict in=0D=

          separate email messages to the Responsible Area Director.  (It=0D=

          should be in a separate email because this questionnaire is=0D
          entered into the ID Tracker.)=0D
=0D
No one has indicated to the WG Chairs or to the WG Mailing List any =
intention to appeal the publication of this document.=0D
=0D
=0D
   (1.g)  Has the Document Shepherd personally verified that the=0D
          document satisfies all ID nits?  (See=0D
          http://www.ietf.org/ID-Checklist.html and=0D
          http://tools.ietf.org/tools/idnits/.)  Boilerplate checks are=0D=

          not enough; this check needs to be thorough.  Has the document=0D=

          met all formal review criteria it needs to, such as the MIB=0D
          Doctor, media type, and URI type reviews?  If the document=0D
          does not already indicate its intended status at the top of=0D
          the first page, please indicate the intended status here.=0D
=0D
Yes.  There are two outdated references and one obsolete reference in =
the current version (-04) of the document.  The authors will correct =
these references during the Author Review period, given by the =
RFC-Editor.=0D
=0D
=0D
   (1.h)  Has the document split its references into normative and=0D
          informative?=0D
=0D
Yes.=0D
=0D
          Are there normative references to documents that=0D
          are not ready for advancement or are otherwise in an unclear=0D=

          state?  If such normative references exist, what is the=0D
          strategy for their completion?  Are there normative references=0D=

          that are downward references, as described in [RFC3967]?  If=0D=

          so, list these downward references to support the Area=0D
          Director in the Last Call procedure for them [RFC3967].=0D
=0D
No.=0D
=0D
=0D
   (1.i)  Has the Document Shepherd verified that the document's IANA=0D
          Considerations section exists and is consistent with the body=0D=

          of the document?=0D
=0D
Yes.  There are no IANA Considerations for this document, which is =
reasonable given its intended purpose.=0D
=0D
=0D
          If the document specifies protocol=0D
          extensions, are reservations requested in appropriate IANA=0D
          registries?  Are the IANA registries clearly identified?  If=0D=

          the document creates a new registry, does it define the=0D
          proposed initial contents of the registry and an allocation=0D
          procedure for future registrations?  Does it suggest a=0D
          reasonable name for the new registry?  See [RFC2434].  If the=0D=

          document describes an Expert Review process, has the Document=0D=

          Shepherd conferred with the Responsible Area Director so that=0D=

          the IESG can appoint the needed Expert during IESG Evaluation?=0D=

=0D
   (1.j)  Has the Document Shepherd verified that sections of the=0D
          document that are written in a formal language, such as XML=0D
          code, BNF rules, MIB definitions, etc., validate correctly in=0D=

          an automated checker?=0D
=0D
Yes.=0D
=0D
=0D
   (1.k)  The IESG approval announcement includes a Document=0D
          Announcement Write-Up.  Please provide such a Document=0D
          Announcement Write-Up.  Recent examples can be found in the=0D
          "Action" announcements for approved documents.  The approval=0D=

          announcement contains the following sections:=0D
=0D
          Technical Summary=0D
This document provides functional requirements for network solutions=0D
that support multicast over Virtual Private LAN Service (VPLS).  It=0D
specifies requirements both from the end user and service provider=0D
standpoints.  It is intended that potential solutions will use these=0D
requirements as guidelines.=0D
=0D
=0D
          Working Group Summary=0D
This document has been reviewed by carriers and experts in the L2VPN WG =
and there are no outstanding issues.=0D
=0D
=0D
          Document Quality=0D
This memo is straightforward and well written.  No issues are =
anticipated.=0D
=0D
=0D
          Personnel=0D
             Who is the Document Shepherd for this document?=0D
Shane Amante (shane@castlepoint.net)=0D
=0D
             Who is the Responsible Area Director?=0D
Mark Townsley (townsley@cisco.com)=

--Apple-Mail-9-508264324
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed




--Apple-Mail-9-508264324--




From l2vpn-bounces@ietf.org Sat Sep 08 12:33:51 2007
Return-path: <l2vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IU3E5-0003gR-Dt; Sat, 08 Sep 2007 12:32:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IU3E4-0003gK-IS; Sat, 08 Sep 2007 12:32:04 -0400
Received: from dog.tcb.net ([64.78.150.133])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IU3E3-00017V-8e; Sat, 08 Sep 2007 12:32:04 -0400
Received: by dog.tcb.net (Postfix, from userid 0)
	id D5D302687A0; Sat,  8 Sep 2007 10:32:02 -0600 (MDT)
Received: from [172.16.15.25] (71-215-91-242.hlrn.qwest.net [71.215.91.242])
	(authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128)
	by dog.tcb.net with SMTP; Sat, 08 Sep 2007 10:32:02 -0600 (MDT)
	(envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.91.242;
	client-port=4826; syn-fingerprint=65535:55:1:64:M1460,N,W0,N,N,T,S MacOS
	10.4.8; data-bytes=0
Mime-Version: 1.0 (Apple Message framework v752.2)
To: Townsley Mark <townsley@cisco.com>,
	WG Milestone Tracker <iesg-secretary@ietf.org>
Message-Id: <EA7A3314-1A67-4BFE-8662-CCD3AFE00F2C@castlepoint.net>
Content-Type: multipart/mixed; boundary=Apple-Mail-12-508509382
From: Shane Amante <shane@castlepoint.net>
Date: Sat, 8 Sep 2007 10:31:46 -0600
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a4a24b484706be629f915bfb1a3e4771
Cc: Vach Kompella <vach.kompella@alcatel-lucent.com>, l2vpn@ietf.org,
	jari.arkko@piuha.net
Subject: Please publish draft-ietf-l2vpn-vpls-bridge-interop-01.txt
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l2vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=subscribe>
Errors-To: l2vpn-bounces@ietf.org


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

Please publish draft-ietf-l2vpn-vpls-bridge-interop-01.txt as an  
Informational RFC.

Attached is the Document Shepherd write-up.

Thanks,

-shane


--Apple-Mail-12-508509382
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; x-unix-mode=0644;
	name=draft-ietf-l2vpn-vpls-bridge-interop-01-proto.txt
Content-Disposition: attachment;
	filename=draft-ietf-l2vpn-vpls-bridge-interop-01-proto.txt

PROTO Statement: draft-ietf-l2vpn-vpls-bridge-interop-01=0D
=0D
The L2VPN Chairs would like to request publication of this document as =
an Informational RFC.=0D
=0D
   (1.a)  Who is the Document Shepherd for this document?  Has the=0D
          Document Shepherd personally reviewed this version of the=0D
          document and, in particular, does he or she believe this=0D
          version is ready for forwarding to the IESG for publication?=0D=

=0D
Shane Amante (shane@castlepoint.net) is the Document Shepherd.  I have =
reviewed the document and it is ready for publication.=0D
=0D
=0D
   (1.b)  Has the document had adequate review both from key WG members=0D=

          and from key non-WG members?  Does the Document Shepherd have=0D=

          any concerns about the depth or breadth of the reviews that=0D
          have been performed?=0D
=0D
The document has been reviewed by the WG, during the WG Last Call, and =
through IETF L2VPN WG meetings.  There were no concerns raised during WG =
Last Call.=0D
=0D
I have no concerns about the state of readiness of this document.=0D
=0D
=0D
   (1.c)  Does the Document Shepherd have concerns that the document=0D
          needs more review from a particular or broader perspective,=0D
          e.g., security, operational complexity, someone familiar with=0D=

          AAA, internationalization, or XML?=0D
=0D
A large Service Provider, several Vendors and others have contributed to =
and reviewed the requirements contained in this document.  I have no =
concerns about this document, and believe it does not require further =
reviews from a broader perspective.=0D
=0D
=0D
   (1.d)  Does the Document Shepherd have any specific concerns or=0D
          issues with this document that the Responsible Area Director=0D=

          and/or the IESG should be aware of?  For example, perhaps he=0D=

          or she is uncomfortable with certain parts of the document, or=0D=

          has concerns whether there really is a need for it.  In any=0D
          event, if the WG has discussed those issues and has indicated=0D=

          that it still wishes to advance the document, detail those=0D
          concerns here.  Has an IPR disclosure related to this document=0D=

          been filed?  If so, please include a reference to the=0D
          disclosure and summarize the WG discussion and conclusion on=0D=

          this issue.=0D
=0D
I have no specific concerns about this document, nor are there any =
concerns that should be conveyed to the IESG or the Responsible AD.=0D
=0D
=0D
   (1.e)  How solid is the WG consensus behind this document?  Does it=0D=

          represent the strong concurrence of a few individuals, with=0D
          others being silent, or does the WG as a whole understand and=0D=

          agree with it?=0D
=0D
This document is well understood and has broad support by the L2VPN WG.  =
This document is widely recognized by the WG as a valuable contribution =
intended to assist implementers, and Service Providers, understand not =
only the issues that may be encountered, but also (in some cases) =
potential solutions, when deploying VPLS with IEEE bridges as CE =
devices.=0D
=0D
=0D
   (1.f)  Has anyone threatened an appeal or otherwise indicated extreme=0D=

          discontent?  If so, please summarize the areas of conflict in=0D=

          separate email messages to the Responsible Area Director.  (It=0D=

          should be in a separate email because this questionnaire is=0D
          entered into the ID Tracker.)=0D
=0D
No one has indicated to the WG Chairs or to the WG Mailing List any =
intention to appeal the publication of this document.=0D
=0D
=0D
   (1.g)  Has the Document Shepherd personally verified that the=0D
          document satisfies all ID nits?  (See=0D
          http://www.ietf.org/ID-Checklist.html and=0D
          http://tools.ietf.org/tools/idnits/.)  Boilerplate checks are=0D=

          not enough; this check needs to be thorough.  Has the document=0D=

          met all formal review criteria it needs to, such as the MIB=0D
          Doctor, media type, and URI type reviews?  If the document=0D
          does not already indicate its intended status at the top of=0D
          the first page, please indicate the intended status here.=0D
=0D
Yes.  There are 7 errors, 4 warnings and 3 comments.  The boilerplates =
need to be updated, non-ASCII characters removed, IANA considerations =
added, add a reference to RFC 2119, update the 'Intended Status' to =
Informational and, finally, update the Normative References to =
correspond to (recently) published RFC's.  The authors will correct =
these references during the Author Review period, given by the =
RFC-Editor.=0D
=0D
=0D
   (1.h)  Has the document split its references into normative and=0D
          informative?=0D
=0D
Yes.=0D
=0D
          Are there normative references to documents that=0D
          are not ready for advancement or are otherwise in an unclear=0D=

          state?  If such normative references exist, what is the=0D
          strategy for their completion?  Are there normative references=0D=

          that are downward references, as described in [RFC3967]?  If=0D=

          so, list these downward references to support the Area=0D
          Director in the Last Call procedure for them [RFC3967].=0D
=0D
No.=0D
=0D
=0D
   (1.i)  Has the Document Shepherd verified that the document's IANA=0D
          Considerations section exists and is consistent with the body=0D=

          of the document?=0D
=0D
Yes.  There is no IANA Considerations for this document, which is =
reasonable given its intended purpose.=0D
=0D
=0D
          If the document specifies protocol=0D
          extensions, are reservations requested in appropriate IANA=0D
          registries?  Are the IANA registries clearly identified?  If=0D=

          the document creates a new registry, does it define the=0D
          proposed initial contents of the registry and an allocation=0D
          procedure for future registrations?  Does it suggest a=0D
          reasonable name for the new registry?  See [RFC2434].  If the=0D=

          document describes an Expert Review process, has the Document=0D=

          Shepherd conferred with the Responsible Area Director so that=0D=

          the IESG can appoint the needed Expert during IESG Evaluation?=0D=

=0D
   (1.j)  Has the Document Shepherd verified that sections of the=0D
          document that are written in a formal language, such as XML=0D
          code, BNF rules, MIB definitions, etc., validate correctly in=0D=

          an automated checker?=0D
=0D
Yes.=0D
=0D
=0D
   (1.k)  The IESG approval announcement includes a Document=0D
          Announcement Write-Up.  Please provide such a Document=0D
          Announcement Write-Up.  Recent examples can be found in the=0D
          "Action" announcements for approved documents.  The approval=0D=

          announcement contains the following sections:=0D
=0D
          Technical Summary=0D
When CE devices are IEEE bridges, then there are certain issues and=0D
challenges that need to be accounted for in a VPLS network. The majority=0D=

of these issues have currently been addressed in the IEEE 802.1ad=0D
standard for provider bridges and they need to be addressed for VPLS=0D
networks as well. This draft discusses these issues and wherever =
possible,=0D
the recommended solutions to these issues.=0D
=0D
=0D
          Working Group Summary=0D
This document has been reviewed by carriers and experts in the L2VPN WG =
and there are no outstanding issues.=0D
=0D
=0D
          Document Quality=0D
This memo is straightforward and well written.  No issues are =
anticipated.=0D
=0D
=0D
          Personnel=0D
             Who is the Document Shepherd for this document?=0D
Shane Amante (shane@castlepoint.net)=0D
=0D
             Who is the Responsible Area Director?=0D
Mark Townsley (townsley@cisco.com)=

--Apple-Mail-12-508509382--




From l2vpn-bounces@ietf.org Wed Sep 12 12:16:54 2007
Return-path: <l2vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IVUrq-0002jC-PO; Wed, 12 Sep 2007 12:15:06 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IVUrn-0002iO-96; Wed, 12 Sep 2007 12:15:03 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IVUrm-0008V1-TN; Wed, 12 Sep 2007 12:15:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 88451175A4;
	Wed, 12 Sep 2007 16:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IVUrm-0007wu-2p; Wed, 12 Sep 2007 12:15:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IVUrm-0007wu-2p@stiedprstage1.ietf.org>
Date: Wed, 12 Sep 2007 12:15:02 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: l2vpn@ietf.org
Subject: I-D ACTION:draft-ietf-l2vpn-vpls-mcast-reqts-05.txt 
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l2vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=subscribe>
Errors-To: l2vpn-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 2 Virtual Private Networks Working Group of the IETF.

	Title		: Requirements for Multicast Support in Virtual Private LAN Services
	Author(s)	: Y. Kamite, et al.
	Filename	: draft-ietf-l2vpn-vpls-mcast-reqts-05.txt
	Pages		: 29
	Date		: 2007-9-12
	
This document provides functional requirements for network solutions
   that support multicast over Virtual Private LAN Service (VPLS).  It
   specifies requirements both from the end user and service provider
   standpoints.  It is intended that potential solutions will use these
   requirements as guidelines.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-mcast-reqts-05.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-l2vpn-vpls-mcast-reqts-05.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-l2vpn-vpls-mcast-reqts-05.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: <2007-9-12113032.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l2vpn-vpls-mcast-reqts-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-l2vpn-vpls-mcast-reqts-05.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

--NextPart--




From l2vpn-bounces@ietf.org Wed Sep 12 21:51:04 2007
Return-path: <l2vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IVdpS-0003uK-LG; Wed, 12 Sep 2007 21:49:14 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IVdpR-0003u6-BE; Wed, 12 Sep 2007 21:49:13 -0400
Received: from dog.tcb.net ([64.78.150.133])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IVdpQ-0005QH-FZ; Wed, 12 Sep 2007 21:49:13 -0400
Received: by dog.tcb.net (Postfix, from userid 0)
	id EA38926883C; Wed, 12 Sep 2007 19:49:11 -0600 (MDT)
Received: from [172.16.15.25] (71-215-91-242.hlrn.qwest.net [71.215.91.242])
	(authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128)
	by dog.tcb.net with SMTP; Wed, 12 Sep 2007 19:49:11 -0600 (MDT)
	(envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.91.242;
	client-port=4897; syn-fingerprint=65535:55:1:64:M1460,N,W0,N,N,T,S MacOS
	10.4.8; data-bytes=0
Mime-Version: 1.0 (Apple Message framework v752.2)
To: Townsley Mark <townsley@cisco.com>,
	WG Milestone Tracker <iesg-secretary@ietf.org>
Message-Id: <C963483B-5631-4796-8FC5-F5BB4F437875@castlepoint.net>
Content-Type: multipart/mixed; boundary=Apple-Mail-3-887537975
From: Shane Amante <shane@castlepoint.net>
Date: Wed, 12 Sep 2007 19:48:55 -0600
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 76c7db407a166e4c39f35d8215d8dd32
Cc: Vach Kompella <vach.kompella@alcatel-lucent.com>, l2vpn@ietf.org,
	jari.arkko@piuha.net
Subject: Please publish draft-ietf-l2vpn-vpls-mcast-reqts-05.txt 
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l2vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=subscribe>
Errors-To: l2vpn-bounces@ietf.org


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

Please publish draft-ietf-l2vpn-vpls-mcast-reqts-05.txt as an  
Informational RFC.

Attached is the Document Shepherd write-up.

Thanks,

-shane


--Apple-Mail-3-887537975
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; x-unix-mode=0644;
	name=draft-ietf-l2vpn-vpls-mcast-reqts-05-proto.txt
Content-Disposition: attachment;
	filename=draft-ietf-l2vpn-vpls-mcast-reqts-05-proto.txt

PROTO Statement: draft-ietf-l2vpn-vpls-mcast-reqts-05=0D
=0D
The L2VPN Chairs would like to request publication of this document as =
Informational.=0D
=0D
   (1.a)  Who is the Document Shepherd for this document?  Has the=0D
          Document Shepherd personally reviewed this version of the=0D
          document and, in particular, does he or she believe this=0D
          version is ready for forwarding to the IESG for publication?=0D=

=0D
Shane Amante (shane@castlepoint.net) is the Document Shepherd.  I have =
reviewed the document and it is ready for publication.=0D
=0D
=0D
   (1.b)  Has the document had adequate review both from key WG members=0D=

          and from key non-WG members?  Does the Document Shepherd have=0D=

          any concerns about the depth or breadth of the reviews that=0D
          have been performed?=0D
=0D
The document has been reviewed by the WG, during the WG Last Call, and =
through IETF L2VPN WG meetings.  There were some comments received =
during WG Last Call with respect to allowing: proxying certain multicast =
control protocols, circumstances under which frame reordering cannot be =
prevented (when switching over from one tree to another) and allowing =
multicast service activation at a customer IP address level (in addition =
to a MAC address level).  All of these comments have been addressed =
satisfactorily by the authors in the current, published version of this =
document.=0D
=0D
I have no concerns about the state of readiness of this document.=0D
=0D
=0D
   (1.c)  Does the Document Shepherd have concerns that the document=0D
          needs more review from a particular or broader perspective,=0D
          e.g., security, operational complexity, someone familiar with=0D=

          AAA, internationalization, or XML?=0D
=0D
Several Service Providers and Vendors have contributed to and reviewed =
the requirements contained in this document.  I have no concerns about =
this document, and believe it does not require further reviews from a =
broader perspective.=0D
=0D
=0D
   (1.d)  Does the Document Shepherd have any specific concerns or=0D
          issues with this document that the Responsible Area Director=0D=

          and/or the IESG should be aware of?  For example, perhaps he=0D=

          or she is uncomfortable with certain parts of the document, or=0D=

          has concerns whether there really is a need for it.  In any=0D
          event, if the WG has discussed those issues and has indicated=0D=

          that it still wishes to advance the document, detail those=0D
          concerns here.  Has an IPR disclosure related to this document=0D=

          been filed?  If so, please include a reference to the=0D
          disclosure and summarize the WG discussion and conclusion on=0D=

          this issue.=0D
=0D
I have no specific concerns about this document, nor are there any =
concerns that should be conveyed to the IESG or the Responsible AD.=0D
=0D
=0D
   (1.e)  How solid is the WG consensus behind this document?  Does it=0D=

          represent the strong concurrence of a few individuals, with=0D
          others being silent, or does the WG as a whole understand and=0D=

          agree with it?=0D
=0D
This document is well understood and has broad support by the L2VPN WG.  =
This document is widely recognized by the WG as a valuable contribution =
intended to shape L2VPN WG mutlicast solutions.=0D
=0D
=0D
   (1.f)  Has anyone threatened an appeal or otherwise indicated extreme=0D=

          discontent?  If so, please summarize the areas of conflict in=0D=

          separate email messages to the Responsible Area Director.  (It=0D=

          should be in a separate email because this questionnaire is=0D
          entered into the ID Tracker.)=0D
=0D
No one has indicated to the WG Chairs or to the WG Mailing List any =
intention to appeal the publication of this document.=0D
=0D
=0D
   (1.g)  Has the Document Shepherd personally verified that the=0D
          document satisfies all ID nits?  (See=0D
          http://www.ietf.org/ID-Checklist.html and=0D
          http://tools.ietf.org/tools/idnits/.)  Boilerplate checks are=0D=

          not enough; this check needs to be thorough.  Has the document=0D=

          met all formal review criteria it needs to, such as the MIB=0D
          Doctor, media type, and URI type reviews?  If the document=0D
          does not already indicate its intended status at the top of=0D
          the first page, please indicate the intended status here.=0D
=0D
Yes.  There are two outdated references and one obsolete reference in =
the current version (-04) of the document.  The authors will correct =
these references during the Author Review period, given by the =
RFC-Editor.=0D
=0D
=0D
   (1.h)  Has the document split its references into normative and=0D
          informative?=0D
=0D
Yes.=0D
=0D
          Are there normative references to documents that=0D
          are not ready for advancement or are otherwise in an unclear=0D=

          state?  If such normative references exist, what is the=0D
          strategy for their completion?  Are there normative references=0D=

          that are downward references, as described in [RFC3967]?  If=0D=

          so, list these downward references to support the Area=0D
          Director in the Last Call procedure for them [RFC3967].=0D
=0D
No.=0D
=0D
=0D
   (1.i)  Has the Document Shepherd verified that the document's IANA=0D
          Considerations section exists and is consistent with the body=0D=

          of the document?=0D
=0D
Yes.  There are no IANA Considerations for this document, which is =
reasonable given its intended purpose.=0D
=0D
=0D
          If the document specifies protocol=0D
          extensions, are reservations requested in appropriate IANA=0D
          registries?  Are the IANA registries clearly identified?  If=0D=

          the document creates a new registry, does it define the=0D
          proposed initial contents of the registry and an allocation=0D
          procedure for future registrations?  Does it suggest a=0D
          reasonable name for the new registry?  See [RFC2434].  If the=0D=

          document describes an Expert Review process, has the Document=0D=

          Shepherd conferred with the Responsible Area Director so that=0D=

          the IESG can appoint the needed Expert during IESG Evaluation?=0D=

=0D
   (1.j)  Has the Document Shepherd verified that sections of the=0D
          document that are written in a formal language, such as XML=0D
          code, BNF rules, MIB definitions, etc., validate correctly in=0D=

          an automated checker?=0D
=0D
Yes.=0D
=0D
=0D
   (1.k)  The IESG approval announcement includes a Document=0D
          Announcement Write-Up.  Please provide such a Document=0D
          Announcement Write-Up.  Recent examples can be found in the=0D
          "Action" announcements for approved documents.  The approval=0D=

          announcement contains the following sections:=0D
=0D
          Technical Summary=0D
This document provides functional requirements for network solutions=0D
that support multicast over Virtual Private LAN Service (VPLS).  It=0D
specifies requirements both from the end user and service provider=0D
standpoints.  It is intended that potential solutions will use these=0D
requirements as guidelines.=0D
=0D
=0D
          Working Group Summary=0D
This document has been reviewed by carriers and experts in the L2VPN WG =
and there are no outstanding issues.=0D
=0D
=0D
          Document Quality=0D
This memo is straightforward and well written.  No issues are =
anticipated.=0D
=0D
=0D
          Personnel=0D
             Who is the Document Shepherd for this document?=0D
Shane Amante (shane@castlepoint.net)=0D
=0D
             Who is the Responsible Area Director?=0D
Mark Townsley (townsley@cisco.com)=

--Apple-Mail-3-887537975--




From l2vpn-bounces@ietf.org Fri Sep 21 12:18:12 2007
Return-path: <l2vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYlA5-0004vl-B1; Fri, 21 Sep 2007 12:15:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYl9k-0004QC-O1; Fri, 21 Sep 2007 12:15:04 -0400
Received: from ns1.neustar.com ([156.154.16.138])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IYl9i-0005Wb-JH; Fri, 21 Sep 2007 12:15:04 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 67CA726E78;
	Fri, 21 Sep 2007 16:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IYl9i-0004Gy-4C; Fri, 21 Sep 2007 12:15:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IYl9i-0004Gy-4C@stiedprstage1.ietf.org>
Date: Fri, 21 Sep 2007 12:15:02 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: l2vpn@ietf.org
Subject: I-D ACTION:draft-ietf-l2vpn-oam-req-frmk-09.txt 
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l2vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=subscribe>
Errors-To: l2vpn-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 2 Virtual Private Networks Working Group of the IETF.

	Title		: L2VPN OAM Requirements and Framework
	Author(s)	: D. Mohan, A. Sajassi
	Filename	: draft-ietf-l2vpn-oam-req-frmk-09.txt
	Pages		: 35
	Date		: 2007-9-21
	
This draft provides framework and requirements for Layer 2 Virtual
Private Networks (L2VPN) Operation, Administration and Maintenance
(OAM). The OAM framework is intended to provide OAM layering across
L2VPN services, Pseudo Wires (PWs) and Packet Switched Network (PSN)
tunnels. The requirements are intended to identify OAM requirement
for L2VPN services (i.e. VPLS, VPWS, and IPLS). Furthermore, if
L2VPN services OAM requirements impose specific requirements on PW
OAM and/or PSN OAM, those specific PW and/or PSN OAM requirements
are also identified.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-oam-req-frmk-09.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-l2vpn-oam-req-frmk-09.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-l2vpn-oam-req-frmk-09.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 From l2vpn-bounces@ietf.org Fri Sep 21 12:18:12 2007
Return-path: <l2vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYlA5-0004vl-B1; Fri, 21 Sep 2007 12:15:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYl9k-0004QC-O1; Fri, 21 Sep 2007 12:15:04 -0400
Received: from ns1.neustar.com ([156.154.16.138])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IYl9i-0005Wb-JH; Fri, 21 Sep 2007 12:15:04 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 67CA726E78;
	Fri, 21 Sep 2007 16:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IYl9i-0004Gy-4C; Fri, 21 Sep 2007 12:15:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IYl9i-0004Gy-4C@stiedprstage1.ietf.org>
Date: Fri, 21 Sep 2007 12:15:02 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: l2vpn@ietf.org
Subject: I-D ACTION:draft-ietf-l2vpn-oam-req-frmk-09.txt 
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l2vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=subscribe>
Errors-To: l2vpn-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 2 Virtual Private Networks Working Group of the IETF.

	Title		: L2VPN OAM Requirements and Framework
	Author(s)	: D. Mohan, A. Sajassi
	Filename	: draft-ietf-l2vpn-oam-req-frmk-09.txt
	Pages		: 35
	Date		: 2007-9-21
	
This draft provides framework and requirements for Layer 2 Virtual
Private Networks (L2VPN) Operation, Administration and Maintenance
(OAM). The OAM framework is intended to provide OAM layering across
L2VPN services, Pseudo Wires (PWs) and Packet Switched Network (PSN)
tunnels. The requirements are intended to identify OAM requirement
for L2VPN services (i.e. VPLS, VPWS, and IPLS). Furthermore, if
L2VPN services OAM requirements impose specific requirements on PW
OAM and/or PSN OAM, those specific PW and/or PSN OAM requirements
are also identified.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-oam-req-frmk-09.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-l2vpn-oam-req-frmk-09.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-l2vpn-oam-req-frmk-09.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: <2007-9-21115738.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l2vpn-oam-req-frmk-09.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-l2vpn-oam-req-frmk-09.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

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


--OtherAccess--

--NextPart--





From l2vpn-bounces@ietf.org Fri Sep 21 12:18:12 2007
Return-path: <l2vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYl9z-0004ev-To; Fri, 21 Sep 2007 12:15:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYl9k-0004MF-59; Fri, 21 Sep 2007 12:15:04 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IYl9i-0005Wa-Ag; Fri, 21 Sep 2007 12:15:04 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 0FA2B26E73;
	Fri, 21 Sep 2007 16:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IYl9h-0004GT-TF; Fri, 21 Sep 2007 12:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IYl9h-0004GT-TF@stiedprstage1.ietf.org>
Date: Fri, 21 Sep 2007 12:15:01 -0400
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: l2vpn@ietf.org
Subject: I-D ACTION:draft-ietf-l2vpn-vpls-mcast-02.txt 
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l2vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=subscribe>
Errors-To: l2vpn-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 2 Virtual Private Networks Working Group of the IETF.

	Title		: Multicast in VPLS
	Author(s)	: R. Aggarwal, et al.
	Filename	: draft-ietf-l2vpn-vpls-mcast-02.txt
	Pages		: 30
	Date		: 2007-9-21
	
This document describes a solution for overcoming a subset of the
   limitations of existing VPLS multicast solutions. It describes
   procedures for VPLS multicast that utilize multicast trees in the
   sevice provider (SP) network.  One such multicast tree can be shared
   between multiple VPLS instances.  Procedures by which a single
   multicast tree in the backbone can be used to carry traffic belonging
   only to a specified set of one or more IP multicast streams from one
   or more VPLSs are also described.

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

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

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

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

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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draftreader
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: <2007-9-21115738.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l2vpn-oam-req-frmk-09.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-l2vpn-oam-req-frmk-09.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

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


--OtherAccess--

--NextPart--





From l2vpn-bounces@ietf.org Fri Sep 21 12:18:12 2007
Return-path: <l2vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYl9z-0004ev-To; Fri, 21 Sep 2007 12:15:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYl9k-0004MF-59; Fri, 21 Sep 2007 12:15:04 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IYl9i-0005Wa-Ag; Fri, 21 Sep 2007 12:15:04 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 0FA2B26E73;
	Fri, 21 Sep 2007 16:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IYl9h-0004GT-TF; Fri, 21 Sep 2007 12:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IYl9h-0004GT-TF@stiedprstage1.ietf.org>
Date: Fri, 21 Sep 2007 12:15:01 -0400
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: l2vpn@ietf.org
Subject: I-D ACTION:draft-ietf-l2vpn-vpls-mcast-02.txt 
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l2vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=subscribe>
Errors-To: l2vpn-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 2 Virtual Private Networks Working Group of the IETF.

	Title		: Multicast in VPLS
	Author(s)	: R. Aggarwal, et al.
	Filename	: draft-ietf-l2vpn-vpls-mcast-02.txt
	Pages		: 30
	Date		: 2007-9-21
	
This document describes a solution for overcoming a subset of the
   limitations of existing VPLS multicast solutions. It describes
   procedures for VPLS multicast that utilize multicast trees in the
   sevice provider (SP) network.  One such multicast tree can be shared
   between multiple VPLS instances.  Procedures by which a single
   multicast tree in the backbone can be used to carry traffic belonging
   only to a specified set of one or more IP multicast streams from one
   or more VPLSs are also described.

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

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

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

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

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

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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-l2vpn-vpls-mcast-02.txt

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

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


--OtherAccess--

--NextPart--




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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-l2vpn-vpls-mcast-02.txt

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

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


--OtherAccess--

--NextPart--




