From l2vpn-bounces@ietf.org Tue Jan 02 17:19:18 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H1ry0-0001vk-Sz; Tue, 02 Jan 2007 17:18:44 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H1rxy-0001vL-7L; Tue, 02 Jan 2007 17:18:42 -0500 Received: from out001.atlarge.net ([129.41.63.69]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H1rxt-0004oX-W9; Tue, 02 Jan 2007 17:18:42 -0500 Received: from nemertes-01-ex.atlarge.net ([10.100.50.167]) by out001.atlarge.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 2 Jan 2007 16:16:51 -0600 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Tue, 2 Jan 2007 16:18:53 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: FutureNet 2007 Call For Presentations Thread-Index: AccukSytZr2ld2u9RvuHPF7uXbxFTwAA4FRQAAkWooAAAF48cA== From: "Irwin Lazar" To: , , , , X-OriginalArrivalTime: 02 Jan 2007 22:16:51.0794 (UTC) FILETIME=[B40E3320:01C72EBB] X-Spam-Score: 0.0 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Cc: mpls-ops@mplsrc.com Subject: FutureNet 2007 Call For Presentations X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org Greetings, The "Call for Presentations" for "FutureNet 2007: MPLS, VPLS and Beyond" is now available at http://www.futurenetexpo.com/speaker/submit_pres.html FutureNet will be held at the Grand Hyatt Hotel on April 30 - May 3, 2007 in New York City. FutureNet represents the evolution of MPLScon, which for the last six years has been the premier industry conference focusing on MPLS, VPN and WAN technologies from both enterprise and service provider perspectives. =20 With this year's event we'll expand our focus to cover next generation network technologies including emerging Ethernet services, fixed/mobile convergence, rich-media service delivery, optical networking and more. As has been the tradition from past events, FutureNet will focus on end-user case studies from both enterprises and service providers providing real-world insight into challenges and lessons learned. =20 We invite you to review the Call For Presentations and submit an abstract. Please note that abstracts are due by February 2nd, 2007. Please feel free to contact me with any questions. My contact information is below. =20 Sincerely, Irwin Lazar Conference Director, FutureNet: MPLS, VPLS, and Beyond (Formerly MPLScon) http://www.futurenetexpo.com/ irwin.lazar@nemertes.com 703-468-4361 AIM/Google/Yahoo/Skype: imlazar =20 From l2vpn-bounces@ietf.org Sun Jan 14 23:46:14 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6JiS-0000ue-Vh; Sun, 14 Jan 2007 23:45:04 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6JiQ-0000uW-9C for l2vpn@ietf.org; Sun, 14 Jan 2007 23:45:02 -0500 Received: from cat.tcb.net ([64.78.150.134] helo=dog.tcb.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6JiO-0007wQ-An for l2vpn@ietf.org; Sun, 14 Jan 2007 23:45:01 -0500 Received: from [172.16.15.25] (dsl081-098-224.den1.dsl.speakeasy.net [64.81.98.224]) by dog.tcb.net (Postfix) with ESMTP id 2EF4F64365 for ; Sun, 14 Jan 2007 21:44:53 -0700 (MST) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: <011CF647-EF43-4B5E-8198-EC655B51178C@castlepoint.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: l2vpn@ietf.org From: Shane Amante Date: Sun, 14 Jan 2007 21:44:52 -0700 X-Mailer: Apple Mail (2.752.2) X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Subject: WG Last Call: draft-ietf-l2vpn-vpls-mcast-reqts-03 X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org Hi Folks, This is the start of a WG Last Call for: http://tools.ietf.org/html/draft-ietf-l2vpn-vpls-mcast-reqts-03 Please e-mail the list with any comments, concerns or corrections, in addition to whether or not you support forwarding this I-D on to the IESG. Last Call on this draft will end in two weeks, on Friday, January 26, 2007, at 17:00 MST (UTC -7). Thanks! -shane & Vach From l2vpn-bounces@ietf.org Mon Jan 15 10:48:19 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6U3r-00034G-64; Mon, 15 Jan 2007 10:47:51 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6U3q-00030e-A0 for l2vpn@ietf.org; Mon, 15 Jan 2007 10:47:50 -0500 Received: from omr8.networksolutionsemail.com ([205.178.146.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6U3o-0007mB-75 for l2vpn@ietf.org; Mon, 15 Jan 2007 10:47:49 -0500 Received: from mail.networksolutionsemail.com (ns-omr8.mgt.netsol.com [10.49.6.71]) by omr8.networksolutionsemail.com (8.13.6/8.13.6) with SMTP id l0FFljrp032710 for ; Mon, 15 Jan 2007 10:47:45 -0500 Message-Id: <200701151547.l0FFljrp032710@omr8.networksolutionsemail.com> Received: (qmail 15001 invoked by uid 78); 15 Jan 2007 15:47:44 -0000 Received: from unknown (HELO PC556411137441) (william.zayas@fibercrossing.net@66.231.171.5) by ns-omr8.lb.hosting.dc2.netsol.com with SMTP; 15 Jan 2007 15:47:44 -0000 From: "William Zayas" To: "'Shane Amante'" , Date: Mon, 15 Jan 2007 11:47:46 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0000_01C7389A.F9EEE310" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: Acc4YBcqmLhVvcTjTe+/5Fw2O+dGfQAWujNg In-Reply-To: <011CF647-EF43-4B5E-8198-EC655B51178C@castlepoint.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.1 (/) X-Scan-Signature: 4515df9441674711565101d9d5c4f63f Cc: Subject: RE: WG Last Call: draft-ietf-l2vpn-vpls-mcast-reqts-03 X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org This is a multi-part message in MIME format. ------=_NextPart_000_0000_01C7389A.F9EEE310 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Shane, On the Intruduction part of the Definition of VPLS goes as follow: VPLS (Virtual Private LAN Service) is a provider service that emulates the full functionality of a traditional Local Area Network (LAN). VPLS interconnects several customer LAN segments over a packet switched network (PSN) backbone, creating a multipoint-to- multipoint Ethernet VPN. For customers, their remote LAN segments behave as one single LAN. My concern is the term emulates on a PSN Backbone. What about of all new IP-MPLS backbones? Regards, William Zayas Fiber Crossing Corp. -----Original Message----- From: Shane Amante [mailto:shane@castlepoint.net] Sent: Monday, January 15, 2007 12:45 AM To: l2vpn@ietf.org Subject: WG Last Call: draft-ietf-l2vpn-vpls-mcast-reqts-03 Hi Folks, This is the start of a WG Last Call for: http://tools.ietf.org/html/draft-ietf-l2vpn-vpls-mcast-reqts-03 Please e-mail the list with any comments, concerns or corrections, in addition to whether or not you support forwarding this I-D on to the IESG. Last Call on this draft will end in two weeks, on Friday, January 26, 2007, at 17:00 MST (UTC -7). Thanks! -shane & Vach ------=_NextPart_000_0000_01C7389A.F9EEE310 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Shane,

 

On the Intruduction part of the Definition of VPLS goes as = follow: VPLS (Virtual Private LAN Service) is a provider service = that

   emulates = the full functionality of a traditional Local Area Network

   (LAN).  VPLS interconnects several customer = LAN segments over = a

   packet switched = network (PSN) backbone, creating a multipoint-to-

   multipoint Ethernet VPN.  For customers, their = remote LAN segments

   behave as one single = LAN.

 

My concern is the term emulates on a PSN Backbone. What about of = all new IP-MPLS backbones?

 

Regards,

 

William Zayas

 

Fiber Crossing Corp.

 

-----Original Message-----
From: Shane Amante [mailto:shane@castlepoint.net]
Sent: Monday, January 15, 2007 12:45 AM
To: l2vpn@ietf.org
Subject: WG Last Call: = draft-ietf-l2vpn-vpls-mcast-reqts-03

 

Hi Folks,

 

This is the start of a WG Last Call = for:

http://tools.ietf.org/html/draft-ietf-l2vpn-vp= ls-mcast-reqts-03

 

Please e-mail the list with any comments, = concerns or corrections, in 

addition to whether or not you support = forwarding this I-D on to the 

IESG.  Last Call on this draft will end = in two weeks, on Friday, 

January 26, 2007, at 17:00 MST (UTC = -7).

 

Thanks!

 

-shane & = Vach

 

 

------=_NextPart_000_0000_01C7389A.F9EEE310-- From l2vpn-bounces@ietf.org Mon Jan 15 18:19:27 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6b62-0006lb-Tb; Mon, 15 Jan 2007 18:18:34 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6b61-0006lW-OF for l2vpn@ietf.org; Mon, 15 Jan 2007 18:18:33 -0500 Received: from audl751.usa.alcatel.com ([143.209.238.164]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6b60-0004w5-EM for l2vpn@ietf.org; Mon, 15 Jan 2007 18:18:33 -0500 Received: from usdalsbhs01.ad3.ad.alcatel.com (usdalsbhs01.usa.alcatel.com [172.22.216.19]) by audl751.usa.alcatel.com (ALCANET) with ESMTP id l0FNISVS015093 for ; Mon, 15 Jan 2007 17:18:28 -0600 Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by usdalsbhs01.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Mon, 15 Jan 2007 17:18:27 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C738FB.7663CA61" Date: Mon, 15 Jan 2007 17:18:27 -0600 Message-ID: <4A5028372622294A99B8FFF6BD06EB7B0B1728@USDALSMBS03.ad3.ad.alcatel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: clarification required on draft-ietf-l2vpn-signaling-08.txt Thread-Index: Acc4+3ZT9OOq4zvyRgiDOWcC3oIgRg== From: "BALUS Florin" To: X-OriginalArrivalTime: 15 Jan 2007 23:18:27.0900 (UTC) FILETIME=[7679F7C0:01C738FB] X-Scanned-By: MIMEDefang 2.51 on 143.209.238.34 X-Spam-Score: 0.1 (/) X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17 Subject: clarification required on draft-ietf-l2vpn-signaling-08.txt X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C738FB.7663CA61 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =20 I need some clarification on the text in = draft-ietf-l2vpn-signaling-08.txt. =20 Section 3.2.2.1 states "[..] this VPLS-id must be encodable as a BGP = Extended Community[RFC4360]." Next section 3.2.3 states, (re: FEC 129 components used for signaling): = "[..] We encode the VPLS-id in the AGI field". So the BGP Extended = Community attribute gets copied in the AGI. =20 Subsequently section 6 (IANA considerations) states that AGI type 1 = should be used as per ietf-pwe3-iana-allocation (now RFC 4447). The text = in the RFC gives the following description for the AGI type 1: " 0x01 8 AGI encoded as Route Distinguisher [SIG]".=20 Are the two documents out of sync or does the text missing some = information?=20 Thanks, Florin =20 ------_=_NextPart_001_01C738FB.7663CA61 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =0A= =0A= =0A= =0A=
 
=0A=
I need some = clarification on the text in = draft-ietf-l2vpn-signaling-08.txt.
=0A=
 
=0A=
Section 3.2.2.1 states "[..] this VPLS-id must be = encodable as a BGP Extended Community[RFC4360]."
=0A=
Next = section 3.2.3 states, (re: FEC 129 components used for signaling): "[..] = We encode the VPLS-id in the AGI field". So the BGP = Extended Community attribute gets copied in the = AGI.
=0A=
 
=0A=
Subsequently section 6 (IANA considerations) states that AGI = type 1 should be used as per ietf-pwe3-iana-allocation (now RFC 4447). The text = in the RFC gives the following description for the AGI type = 1:
=0A=
=0A=

" 0x01 8 AGI encoded as Route Distinguisher = [SIG]".

=0A=

Are the two documents out of sync or does the text = missing some information?

=0A=

Thanks,

=0A=

Florin

=0A=
 
------_=_NextPart_001_01C738FB.7663CA61-- From l2vpn-bounces@ietf.org Mon Jan 15 21:05:46 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6dgu-0000J8-8Q; Mon, 15 Jan 2007 21:04:48 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6dgs-0000IX-8G for l2vpn@ietf.org; Mon, 15 Jan 2007 21:04:46 -0500 Received: from cat.tcb.net ([64.78.150.134] helo=dog.tcb.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6dgq-0004Ak-VU for l2vpn@ietf.org; Mon, 15 Jan 2007 21:04:46 -0500 Received: from [172.16.15.25] (dsl081-098-224.den1.dsl.speakeasy.net [64.81.98.224]) by dog.tcb.net (Postfix) with ESMTP id A894F64362; Mon, 15 Jan 2007 19:04:43 -0700 (MST) In-Reply-To: <200701151547.l0FFljwO032711@omr8.networksolutionsemail.com> References: <200701151547.l0FFljwO032711@omr8.networksolutionsemail.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <54A5325F-93E3-4797-91E2-604F1756CAB8@castlepoint.net> Content-Transfer-Encoding: 7bit From: Shane Amante Date: Mon, 15 Jan 2007 19:04:43 -0700 To: "William Zayas" X-Mailer: Apple Mail (2.752.2) X-Spam-Score: 0.0 (/) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 Cc: l2vpn@ietf.org Subject: Re: WG Last Call: draft-ietf-l2vpn-vpls-mcast-reqts-03 X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org Hi William, On Jan 15, 2007, at 8:47 AM, William Zayas wrote: > Shane, > > > > On the Intruduction part of the Definition of VPLS goes as follow: > VPLS (Virtual Private LAN Service) is a provider service that > > emulates the full functionality of a traditional Local Area Network > > (LAN). VPLS interconnects several customer LAN segments over a > > packet switched network (PSN) backbone, creating a multipoint-to- > > multipoint Ethernet VPN. For customers, their remote LAN segments > > behave as one single LAN. > > > > My concern is the term emulates on a PSN Backbone. What about of > all new IP-MPLS backbones? I may not understand your question; however, VPLS relies on transport and encapsulation mechanisms defined by the PWE3 Working Group of the IETF. As such, if you look at Section 1.4 of RFC 3985, "PWE3 Architecture", the definition of a PSN is as follows: Packet Switched Within the context of PWE3, this is a Network (PSN) network using IP or MPLS as the mechanism for packet forwarding. Therefore, VPLS is reliant upon an IP or MPLS Backbone for transport of an emulated service between PE devices. I hope this answers your question. -shane > Regards, > > > > William Zayas > > > > Fiber Crossing Corp. > > > > -----Original Message----- > From: Shane Amante [mailto:shane@castlepoint.net] > Sent: Monday, January 15, 2007 12:45 AM > To: l2vpn@ietf.org > Subject: WG Last Call: draft-ietf-l2vpn-vpls-mcast-reqts-03 > > > > Hi Folks, > > > > This is the start of a WG Last Call for: > > http://tools.ietf.org/html/draft-ietf-l2vpn-vpls-mcast-reqts-03 > > > > Please e-mail the list with any comments, concerns or corrections, in > > addition to whether or not you support forwarding this I-D on to the > > IESG. Last Call on this draft will end in two weeks, on Friday, > > January 26, 2007, at 17:00 MST (UTC -7). > > > > Thanks! > > > > -shane & Vach > > > > > > From l2vpn-bounces@ietf.org Tue Jan 16 19:50:24 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6yzv-0002hM-MX; Tue, 16 Jan 2007 19:49:51 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6yzq-0002bG-Rg; Tue, 16 Jan 2007 19:49:47 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6yzp-0002g8-EC; Tue, 16 Jan 2007 19:49:46 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id l0H0nidx017798; Tue, 16 Jan 2007 16:49:44 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id l0H0niWn017797; Tue, 16 Jan 2007 16:49:44 -0800 Date: Tue, 16 Jan 2007 16:49:44 -0800 Message-Id: <200701170049.l0H0niWn017797@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8 Cc: l2vpn@ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4762 on Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4762 Title: Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling Author: M. Lasserre, Ed., V. Kompella, Ed. Status: Standards Track Date: January 2007 Mailbox: mlasserre@alcatel-lucent.com, vach.kompella@alcatel-lucent.com Pages: 31 Characters: 82778 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-l2vpn-vpls-ldp-09.txt URL: http://www.rfc-editor.org/rfc/rfc4762.txt This document describes a Virtual Private LAN Service (VPLS) solution using pseudowires, a service previously implemented over other tunneling technologies and known as Transparent LAN Services (TLS). A VPLS creates an emulated LAN segment for a given set of users; i.e., it creates a Layer 2 broadcast domain that is fully capable of learning and forwarding on Ethernet MAC addresses and that is closed to a given set of users. Multiple VPLS services can be supported from a single Provider Edge (PE) node. This document describes the control plane functions of signaling pseudowire labels using Label Distribution Protocol (LDP), extending RFC 4447. It is agnostic to discovery protocols. The data plane functions of forwarding are also described, focusing in particular on the learning of MAC addresses. The encapsulation of VPLS packets is described by RFC 4448. [STANDARDS TRACK] This document is a product of the Layer 2 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 obtaineFrom l2vpn-bounces@ietf.org Tue Jan 16 19:50:24 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6yzv-0002hM-MX; Tue, 16 Jan 2007 19:49:51 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6yzq-0002bG-Rg; Tue, 16 Jan 2007 19:49:47 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6yzp-0002g8-EC; Tue, 16 Jan 2007 19:49:46 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id l0H0nidx017798; Tue, 16 Jan 2007 16:49:44 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id l0H0niWn017797; Tue, 16 Jan 2007 16:49:44 -0800 Date: Tue, 16 Jan 2007 16:49:44 -0800 Message-Id: <200701170049.l0H0niWn017797@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8 Cc: l2vpn@ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4762 on Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4762 Title: Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling Author: M. Lasserre, Ed., V. Kompella, Ed. Status: Standards Track Date: January 2007 Mailbox: mlasserre@alcatel-lucent.com, vach.kompella@alcatel-lucent.com Pages: 31 Characters: 82778 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-l2vpn-vpls-ldp-09.txt URL: http://www.rfc-editor.org/rfc/rfc4762.txt This document describes a Virtual Private LAN Service (VPLS) solution using pseudowires, a service previously implemented over other tunneling technologies and known as Transparent LAN Services (TLS). A VPLS creates an emulated LAN segment for a given set of users; i.e., it creates a Layer 2 broadcast domain that is fully capable of learning and forwarding on Ethernet MAC addresses and that is closed to a given set of users. Multiple VPLS services can be supported from a single Provider Edge (PE) node. This document describes the control plane functions of signaling pseudowire labels using Label Distribution Protocol (LDP), extending RFC 4447. It is agnostic to discovery protocols. The data plane functions of forwarding are also described, focusing in particular on the learning of MAC addresses. The encapsulation of VPLS packets is described by RFC 4448. [STANDARDS TRACK] This document is a product of the Layer 2 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. The RFC Editor Team USC/Information Sciences Institute ... From l2vpn-bounces@ietf.org Tue Jan 16 19:50:24 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6yzl-0002VU-82; Tue, 16 Jan 2007 19:49:41 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6yzh-0002Hr-K6; Tue, 16 Jan 2007 19:49:37 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6yzf-0002f7-Rq; Tue, 16 Jan 2007 19:49:37 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id l0H0nZOa017788; Tue, 16 Jan 2007 16:49:35 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id l0H0nZOI017787; Tue, 16 Jan 2007 16:49:35 -0800 Date: Tue, 16 Jan 2007 16:49:35 -0800 Message-Id: <200701170049.l0H0nZOI017787@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Cc: l2vpn@ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4761 on Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4761 Title: Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling Author: K. Kompella, Ed., Y. Rekhter, Ed. Status: Standards Track Date: January 2007 Mailbox: kireeti@juniper.net, yakov@juniper.net Pages: 28 Characters: 65219 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-l2vpn-vpls-bgp-08.txt URL: http://www.rfc-editor.org/rfc/rfc4761.txt Virtual Private LAN Service (VPLS), also known as Transparent LAN Service and Virtual Private Switched Network service, is a useful Service Provider offering. The service offers a Layer 2 Virtual Private Network (VPN); however, in the case of VPLS, the customers in the VPN are connected by a multipoint Ethernet LAN, in contrast to the usual Layer 2 VPNs, which are point-to-point in nature. This document describes the functions required to offer VPLS, a mechanism for signaling a VPLS, and rules for forwarding VPLS frames across a packet switched network. [STANDARDS TRACK] This document is a product of the Layer 2 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 sentd 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. The RFC Editor Team USC/Information Sciences Institute ... From l2vpn-bounces@ietf.org Tue Jan 16 19:50:24 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6yzl-0002VU-82; Tue, 16 Jan 2007 19:49:41 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6yzh-0002Hr-K6; Tue, 16 Jan 2007 19:49:37 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6yzf-0002f7-Rq; Tue, 16 Jan 2007 19:49:37 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id l0H0nZOa017788; Tue, 16 Jan 2007 16:49:35 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id l0H0nZOI017787; Tue, 16 Jan 2007 16:49:35 -0800 Date: Tue, 16 Jan 2007 16:49:35 -0800 Message-Id: <200701170049.l0H0nZOI017787@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Cc: l2vpn@ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4761 on Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4761 Title: Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling Author: K. Kompella, Ed., Y. Rekhter, Ed. Status: Standards Track Date: January 2007 Mailbox: kireeti@juniper.net, yakov@juniper.net Pages: 28 Characters: 65219 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-l2vpn-vpls-bgp-08.txt URL: http://www.rfc-editor.org/rfc/rfc4761.txt Virtual Private LAN Service (VPLS), also known as Transparent LAN Service and Virtual Private Switched Network service, is a useful Service Provider offering. The service offers a Layer 2 Virtual Private Network (VPN); however, in the case of VPLS, the customers in the VPN are connected by a multipoint Ethernet LAN, in contrast to the usual Layer 2 VPNs, which are point-to-point in nature. This document describes the functions required to offer VPLS, a mechanism for signaling a VPLS, and rules for forwarding VPLS frames across a packet switched network. [STANDARDS TRACK] This document is a product of the Layer 2 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. The RFC Editor Team USC/Information Sciences Institute ... 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. The RFC Editor Team USC/Information Sciences Institute ... From l2vpn-bounces@ietf.org Fri Jan 26 18:44:59 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HAajQ-0007eN-Ab; Fri, 26 Jan 2007 18:43:44 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HAajP-0007eE-8f for l2vpn@ietf.org; Fri, 26 Jan 2007 18:43:43 -0500 Received: from audl951.usa.alcatel.com ([143.209.238.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HAajN-0006i6-UW for l2vpn@ietf.org; Fri, 26 Jan 2007 18:43:43 -0500 Received: from usdalsbhs02.ad3.ad.alcatel.com (usdalsbhs02.usa.alcatel.com [172.22.216.13]) by audl951.usa.alcatel.com (ALCANET) with ESMTP id l0QNheRh001869; Fri, 26 Jan 2007 17:43:40 -0600 Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by usdalsbhs02.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Fri, 26 Jan 2007 17:43:40 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 26 Jan 2007 17:41:46 -0600 Message-ID: <67FBA6A55FF15B46B8B572062529D26A29B07B@USDALSMBS03.ad3.ad.alcatel.com> In-Reply-To: <011CF647-EF43-4B5E-8198-EC655B51178C@castlepoint.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: WG Last Call: draft-ietf-l2vpn-vpls-mcast-reqts-03 Thread-Index: Acc4YR/ZwrlcYiiGSc2JM4qjuBTYpgJQlQWA From: "HEMIGE Venu" To: "Shane Amante" , X-OriginalArrivalTime: 26 Jan 2007 23:43:40.0571 (UTC) FILETIME=[CEA47EB0:01C741A3] X-Scanned-By: MIMEDefang 2.51 on 143.209.238.34 X-Spam-Score: 0.0 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 Cc: Subject: RE: WG Last Call: draft-ietf-l2vpn-vpls-mcast-reqts-03 X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org Hi Shane, I just have a couple of minor comments. Otherwise, I think it is a very well written draft. In section 5.1.1, it says that a layer 2 frame (whether data or control) SHOULD NOT be altered for transparency. If the frame happens to be a L3 control frame (IGMP/PIM), then it may be completely consumed by a switch and an entirely new packet generated by the switch. So the switch may be injecting frames with its own mac as source address for the packets it generates. It would be better to clarify that this is allowed. Section 5.9: It says a solution SHOULD prevent frame reordering. Delivery of out-of-order frames is not avoidable in certain cases (when switching from one aggregate tree to another). The draft also talks about use of trees as one of the options to optimize data delivery in the core. Section 6.5.1: It appears that multicast service activation at a MAC address granularity is preferred over activation at a customer multicast IP address granularity. Is that what was intended? Clearly, activation at MAC address granularity is not very optimal. Regards, -Venu > -----Original Message----- > From: Shane Amante [mailto:shane@castlepoint.net]=20 > Sent: Sunday, January 14, 2007 8:45 PM > To: l2vpn@ietf.org > Subject: WG Last Call: draft-ietf-l2vpn-vpls-mcast-reqts-03 >=20 > Hi Folks, >=20 > This is the start of a WG Last Call for: > http://tools.ietf.org/html/draft-ietf-l2vpn-vpls-mcast-reqts-03 >=20 > Please e-mail the list with any comments, concerns or=20 > corrections, in =20 > addition to whether or not you support forwarding this I-D on to the =20 > IESG. Last Call on this draft will end in two weeks, on Friday, =20 > January 26, 2007, at 17:00 MST (UTC -7). >=20 > Thanks! >=20 > -shane & Vach >=20 >=20 >=20 From l2vpn-bounces@ietf.org Sun Jan 28 23:00:19 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBNea-0000mi-1J; Sun, 28 Jan 2007 22:58:00 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBNeW-0000az-Jl for l2vpn@ietf.org; Sun, 28 Jan 2007 22:57:56 -0500 Received: from cat.tcb.net ([64.78.150.134] helo=dog.tcb.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBNab-0004vF-Vt for l2vpn@ietf.org; Sun, 28 Jan 2007 22:53:55 -0500 Received: from [172.16.15.25] (dsl081-098-224.den1.dsl.speakeasy.net [64.81.98.224]) by dog.tcb.net (Postfix) with ESMTP id D797364508 for ; Sun, 28 Jan 2007 20:53:45 -0700 (MST) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: <0C775DEF-91AA-417A-8870-1C8DA7FA9136@castlepoint.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: l2vpn@ietf.org From: Shane Amante Date: Sun, 28 Jan 2007 20:53:46 -0700 X-Mailer: Apple Mail (2.752.2) X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed Subject: WG Last Call Ended: draft-ietf-l2vpn-vpls-mcast-reqts-03 X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org This ends the WG Last Call for: http://tools.ietf.org/html/draft-ietf-l2vpn-vpls-mcast-reqts-03 Would the authors please address and, potentially, incorporate the comments sent to the list by Venu, before we pass it along to the IESG? -shane