MPLScon 2006 Program

From l2vpn-bounces@ietf.org Thu Feb 16 10:58:03 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F9lW7-0005TI-2p; Thu, 16 Feb 2006 10:58:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F9lW5-0005Rx-Rv; Thu, 16 Feb 2006 10:58:01 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06926; Thu, 16 Feb 2006 10:56:11 -0500 (EST) Received: from bgslc11.burtongroup.com ([63.99.125.13]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F9lkF-0002xF-B7; Thu, 16 Feb 2006 11:12:43 -0500 Received: bgslc11.burtongroup.com 63.99.125.13 from 216.151.229.244 216.151.229.244 via HTTP with MS-WebStorage 6.0.6249 User-Agent: Microsoft-Entourage/11.2.1.051004 Date: Thu, 16 Feb 2006 10:57:44 -0500 From: Irwin Lazar To: , L2VPN , , , Message-ID: Thread-Topic: MPLScon 2006 Program Thread-Index: AcYzEbkg99xz9p8EEdqUmAAKlZoW5A== Mime-version: 1.0 Content-type: multipart/alternative; boundary="B_3222932264_1089758" X-Spam-Score: 0.5 (/) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da Cc: Subject: MPLScon 2006 Program X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: l2vpn-bounces@ietf.org Errors-To: l2vpn-bounces@ietf.org > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --B_3222932264_1089758 Content-type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit The program for MPLScon 2006 is now available at http://www.mplscon.com/attend/conf_at_a_glance.html MPLScon 2006 takes place May 22-26 at the Marriott Financial Center in NYC, NY. Please let me know if you have any questions. Irwin -- Irwin Lazar, Conference Director, MPLScon http://www.mplscon.com ilazar@burtongroup.com Phone: 703-742-9659 AIM/iChat/Google/MSN/Gizmo/Skype/Yahoo: imlazar --B_3222932264_1089758 Content-type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable MPLScon 2006 Program The p= rogram for MPLScon 2006 is now available at http://www.mplscon.com/attend/conf_at_a_glance= .html

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

Please let me know if you have any questions.

Irwin

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

--B_3222932264_1089758-- From l2vpn-bounces@ietf.org Mon Feb 20 00:28:04 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FB3aU-0004Ku-1D; Mon, 20 Feb 2006 00:27:54 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FB3aS-0004Kl-TV for l2vpn@ietf.org; Mon, 20 Feb 2006 00:27:52 -0500 Received: from imo-d01.mx.aol.com ([205.188.157.33]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FB3aR-0002VO-NL for l2vpn@ietf.org; Mon, 20 Feb 2006 00:27:52 -0500 Received: from balavenkata@netscape.net by imo-d01.mx.aol.com (mail_out_v38_r7.3.) id l.1ae.10eb729f (22680) for ; Mon, 20 Feb 2006 00:27:44 -0500 (EST) Received: from [192.168.0.31] (sjc-cust-208.57.179.114.mpowercom.net [208.57.179.114]) by air-in04.mx.aol.com (vx) with ESMTP id MAILININ41-589843f9534d3bd; Mon, 20 Feb 2006 00:27:44 -0500 Message-ID: <43F9537C.7090609@netscape.net> Date: Sun, 19 Feb 2006 21:28:28 -0800 From: "Bala S. Venkata" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: l2vpn@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AOL-IP: 208.57.179.114 X-Mailer: Unknown (No Version) X-Spam-Flag: NO X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Subject: Vlan translation 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, A ldp-vpls newbie question: I have two customer sites which use different vlan's (say ids 601 and 602). Suppose I want to connect them should I necessarily set up a vpls between them ? If so the PE access ports should be access port ? What would be the FEC VC type of the vpls (ethernet/ethernet-vlan) ? +-------+ +------+ +------+ +-------+ | CE |-----| PE |----..mpls..---| PE |------| CE | |site1 | |dev A | core |dev B | | site2 | |vid:601| | | | | |vid:602| +-------+ +------+ +------+ +-------+ Can I add a third site to participate in such a vlan translation ? Thanks ! /bala From l2vpn-bounces@ietf.org Mon Feb 20 06:19:27 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FB94a-00025Q-R0; Mon, 20 Feb 2006 06:19:20 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FB94Y-00025I-Vl for l2vpn@ietf.org; Mon, 20 Feb 2006 06:19:18 -0500 Received: from nproxy.gmail.com ([64.233.182.200]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FB94Y-0003CK-Hf for l2vpn@ietf.org; Mon, 20 Feb 2006 06:19:18 -0500 Received: by nproxy.gmail.com with SMTP id l23so607290nfc for ; Mon, 20 Feb 2006 03:19:17 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=aEaMZBB1+D5naflvxXwXMpWwLKpthmeJ3Moqyj5OeefJoRwMn0ZEFUiQq0dnw4gGSVJ/TFf44IlU6LEqaa02NyW+X6i6krT8P3YSBLrt3QIJCPEvw65P+ehqIQY9T6kjcxAXeWl5qv3yM5e2r3zUDBpLJwdawIaFEYoNsP/+8MQ= Received: by 10.48.237.6 with SMTP id k6mr1202140nfh; Mon, 20 Feb 2006 03:19:17 -0800 (PST) Received: by 10.48.30.6 with HTTP; Mon, 20 Feb 2006 03:19:17 -0800 (PST) Message-ID: Date: Mon, 20 Feb 2006 16:49:17 +0530 From: "Rajesh Pandey" To: "Bala S. Venkata" In-Reply-To: <43F9537C.7090609@netscape.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2726_20898578.1140434357104" References: <43F9537C.7090609@netscape.net> X-Spam-Score: 0.1 (/) X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78 Cc: l2vpn@ietf.org Subject: Re: Vlan translation 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 ------=_Part_2726_20898578.1140434357104 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Bala, Find my answers inline: On 2/20/06, Bala S. Venkata wrote: > > HI, > > A ldp-vpls newbie question: > > I have two customer sites which use different vlan's (say ids 601 and > 602). > Suppose I want to connect them should I necessarily set up a vpls between > them ? >> As far as VLAN translation is concerned, you do not need to have VPLS fo= r that. It can be implemented simply on top of layer 2. But, if you are talking about VPLS CEs, where multiple customer sites talking in different VLAN to the MPLS core; you need to have VPLS between them. The VLAN information may typically be sent in the FEC-TLV for VLAN translation and L= 2 rules can applied at CE-PE. If so the PE access ports should be access port ? >> Need not be. What would be the FEC VC type > of the vpls (ethernet/ethernet-vlan) ? > > +-------+ +------+ +------+ +-------+ > | CE |-----| PE |----..mpls..---| PE |------| CE | > |site1 | |dev A | core |dev B | | site2 | > |vid:601| | | | | |vid:602| > +-------+ +------+ +------+ +-------+ >> I think using the PW type depends upon the kind of VPLS instance (type port<->port, port-vlan<->port-vlan) and not on you want to do the VLAN translation or not. Typically, if you want to carry the .1Q tag across the MPLS core you would likely to use Ethernet VC-type and vice-a-versa. Can I add a third site to participate in such a vlan translation ? >> Yes. Provided, you do the same thing for the newly connected site (makin= g PW to the new site from other two sites.) Regards, Rajesh Thanks ! > > /bala > > > > > ------=_Part_2726_20898578.1140434357104 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Hi Bala,

Find my answers inline:

On 2/20/06, Bala S. Venkata <= balavenkata@netscape.net> wrote:

HI,
A ldp-vpls newbie question:

I have two customer sites which use dif= ferent vlan's (say ids 601 and 602).
Suppose I want to connect them should I necessarily set up a vpls betwe= en them ?

>> As far as VLAN t= ranslation is concerned, you do not need to have VPLS for that. It can be i= mplemented simply on top of layer 2. But, if you are talking about VPLS CEs= , where multiple customer sites talking in different VLAN to the MPLS core;= you need to have VPLS between them. The VLAN information may typically be = sent in the FEC-TLV for VLAN translation and L2 rules can applied at CE-PE.= =20

If so the PE access ports should be access port ?

=
>> Need not be.=20

Wha= t would be the FEC VC type
of the vpls (ethernet/ethernet-vlan) ?
    = ;  +-------+     +------+   &n= bsp;           +------+&n= bsp;     +-------+
  &nb= sp;   |site1  |     |dev A |&n= bsp;      core    |dev B |&nbs= p;     | site2 |
      |vid:= 601|     |      | &n= bsp;            = ; |      |      = ;|vid:602|
    = ;  +-------+     +------+   &n= bsp;           +------+&n= bsp;     +-------+

>> I think using the PW type depends upon the kind of VPLS instance = (type port<->port, port-vlan<->port-vlan) and not on you want t= o do the VLAN translation or not. Typically, if you want to carry the .1Q t= ag across the MPLS core you would likely to use Ethernet VC-type and vice-a= -versa.=20

Can= I add a third site to participate in such a vlan translation ?

>> Yes. Provided, you do the same thing for the newly connec= ted site (making PW to the new site from other two sites.)

Regards,=
Rajesh

Thanks !

/bala

------=_Part_2726_20898578.1140434357104-- From l2vpn-bounces@ietf.org Tue Feb 21 00:22:13 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FBPyO-00082V-3w; Tue, 21 Feb 2006 00:22:04 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FBPyN-00082Q-7a for l2vpn@ietf.org; Tue, 21 Feb 2006 00:22:03 -0500 Received: from imo-d02.mx.aol.com ([205.188.157.34]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBPyM-0003GF-11 for l2vpn@ietf.org; Tue, 21 Feb 2006 00:22:03 -0500 Received: from balavenkata@netscape.net by imo-d02.mx.aol.com (mail_out_v38_r7.3.) id l.c7.1335a95b (22681) for ; Tue, 21 Feb 2006 00:21:54 -0500 (EST) Received: from [192.168.0.31] (sjc-cust-208.57.179.114.mpowercom.net [208.57.179.114]) by air-in04.mx.aol.com (vx) with ESMTP id MAILININ42-589943faa3713e1; Tue, 21 Feb 2006 00:21:54 -0500 Message-ID: <43FAA3A0.20104@netscape.net> Date: Mon, 20 Feb 2006 21:22:40 -0800 From: "Bala S. Venkata" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: l2vpn@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-AOL-IP: 208.57.179.114 X-Mailer: Unknown (No Version) X-Spam-Flag: NO X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Subject: VC label assignment in LDP-VPLS 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 Per LDP-VPLS draft Section 4.2 ("Address Learning"), "..reachability information is not advertised and distributed via a control plane". Now, how is the VC label (or the inner label) then decided (I assumed this much be exchanged in the control plane over the targeted ldp session) ? In a BGP_MPLS VPN each PE sends [:, VPNLabel] to the remote in the control plane so that any traffic in the data plane to that site route would use that VPNLabel. Is there a mechanism similar to that for the two PW types (ethernet and ethernet-tagged)....but a PE cannot send [.] because Port1 won't make sense to the remote PE ? In section 4 the draft mentions that the AC could be "..an ATM PVC carrying Ethernet frames, etc., or even an Ethernet PW" besides an ethernet port. How can the remote PEs learn MAC addresses if the AC sends a non-ethernet frame ? Thanks ! /bala From l2vpn-bounces@ietf.org Tue Feb 21 01:39:35 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FBRAd-0001pf-1F; Tue, 21 Feb 2006 01:38:47 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FBRAa-0001pa-VK for l2vpn@ietf.org; Tue, 21 Feb 2006 01:38:44 -0500 Received: from nproxy.gmail.com ([64.233.182.207]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBRAa-00057z-EU for l2vpn@ietf.org; Tue, 21 Feb 2006 01:38:44 -0500 Received: by nproxy.gmail.com with SMTP id l23so749452nfc for ; Mon, 20 Feb 2006 22:38:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=rJ2P00SQ73abnJP5lu1GJlCmaIe2A/evOFEglgHOLKDzbVQlIKtwWvqpIZaquQs3QRHvKj4R0dvR7yUhnz4OSvzUakLAIt81Cd16TbsgB1CNLod8EeHylKwgxebAEMAeBaxx2c4QFFh0Zf/b6wIevYoVBXW6Y1+Q3jhyK1nUbss= Received: by 10.48.226.13 with SMTP id y13mr1418543nfg; Mon, 20 Feb 2006 22:38:37 -0800 (PST) Received: by 10.49.2.8 with HTTP; Mon, 20 Feb 2006 22:38:37 -0800 (PST) Message-ID: Date: Tue, 21 Feb 2006 12:08:37 +0530 From: "Rajesh Pandey" To: "Bala S. Venkata" In-Reply-To: <43FAA3A0.20104@netscape.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1197_23930492.1140503917238" References: <43FAA3A0.20104@netscape.net> X-Spam-Score: 0.5 (/) X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1 Cc: l2vpn@ietf.org Subject: Re: VC label assignment in LDP-VPLS 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 ------=_Part_1197_23930492.1140503917238 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Bala, Find my answers inline: On 2/21/06, Bala S. Venkata wrote: > > Per LDP-VPLS draft Section 4.2 ("Address Learning"), "..reachability > information is not advertised and distributed via a control plane". Now, > how is the VC label (or the inner label) then decided (I assumed this > much be exchanged in the control plane over the targeted ldp session) ? >> These are two different questions. For reachability information answer lies in next line itself. Excerpt from draft-ietf-l2vpn-vpls-ldp-08.txt: "reachability information is not advertised and distributed via a control plane. Reachability is obtained by standard learning bridge functions in the data plane." Actually VPLS creates an emulated LAN segment for a given set of users and performs the transparent bridging operations like a normal bridge: flooding= , learning, filtering, forwarding and aging. For more info regarding transparent bridging operations you might be interested in reading 802.1D o= r some similar doc. >> For PW exchange related info you can go through draft-ietf-pwe3-control-protocol-17.txt. This draft talks in detail about these things. In a BGP_MPLS VPN each PE sends [:, VPNLabel] to the > remote in the control plane so that any traffic in the data plane to > that site route would use that VPNLabel. Is there a mechanism similar to > that for the two PW types (ethernet and ethernet-tagged)....but a PE > cannot send [.] because Port1 won't make sense to the > remote PE ? > > In section 4 the draft mentions that the AC could be "..an ATM PVC > carrying Ethernet frames, etc., or even an Ethernet PW" besides an > ethernet port. How can the remote PEs learn MAC addresses if the AC > sends a non-ethernet frame ? > > >> First thing to be noticed, MAC address learning/aging is done on a per > pseudo-wire basis. The scope of the VPLS lies within the PEs in the servi= ce > provider network not beyond. The PE performs forwarding of user data pack= ets > based on information in the Layer-2 header, such as a MAC destination > address. What CE sees a is just a bridge. Further, you cann't preclude > customer access connections to be something specific, it may be different= at > different CE devices (e.g., Frame Relay, ATM, 802.1d, MPLS). You might be > interested in going through draft-ietf-l2vpn-requirements-04.txt > Hope this helps. Regards, Rajesh Thanks ! > > /bala > > > ------=_Part_1197_23930492.1140503917238 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Hi Bala,

Find my answers inline:

On 2/21/06, Bala S. Venkata <= balavenkata@netscape.net>= ; wrote:

Per LDP-VP= LS draft Section 4.2 ("Address Learning"), "..reachability information is not advertised and distributed via a control plane". No= w,
how is the VC label (or the inner label) then decided (I assumed this=
much be exchanged in the control plane over the targeted ldp session) ?

>> These are two different questions.
For r= eachability information answer lies in next line itself. Excerpt from draft= -ietf-l2vpn-vpls-ldp-08.txt:
"reachability information is not adve= rtised and distributed via a control plane. Reachability is obtained = by standard learning bridge functions in the data plane."=20
Actually VPLS creates an emulated LAN segment for a given set of users = and performs the transparent bridging operations like a normal bridge: floo= ding, learning, filtering, forwarding and aging. For more info regarding tr= ansparent bridging operations you might be interested in reading=20 802.1D or some similar doc.

>> For PW exchange relate= d info you can go through draft-ietf-pwe3-control-protocol-17.txt. This dra= ft talks in detail about these things.

In a BGP_MPLS VPN each PE sends [<RD>:<SiteRoutes>, VPNLabel] t= o the
remote in the control plane so that any traffic in the data plane = to
that site route would use that VPNLabel. Is there a mechanism similar= to
that for the two PW types (ethernet and ethernet-tagged)....but a PEcannot send [<Port1>.<VCLabel1>] because Port1 won't make sens= e to the
remote PE ?

In section 4 the draft mentions that the AC = could be "..an ATM PVC
carrying Ethernet frames, etc., or even an Ethernet PW" besides an=
ethernet port. How can the remote PEs learn MAC addresses if the AC
= sends a non-ethernet frame ?

>> First thing to be noticed, MAC= address learning/aging is done on a per pseudo-wire basis. The scope of th= e VPLS lies within the PEs in the service provider network not beyond. The = PE performs forwarding of user data packets based on information in the Lay= er-2 header, such as a MAC destination address. What CE sees a is jus= t a bridge. Further, you cann't preclude customer access connections to be = something specific, it may be different at different CE devices ( e.g., Frame Relay, ATM, 802.1d, MPLS). You might be interested in going thr= ough draft-ietf-l2vpn-requirements-04.txt

Hope thi= s helps.

Regards,
Rajesh

Thanks !

/bala

------=_Part_1197_23930492.1140503917238-- From l2vpn-bounces@ietf.org Wed Feb 22 18:54:00 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FC3o0-0008Vd-Rw; Wed, 22 Feb 2006 18:54:00 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FC3ny-0008VS-Og for l2vpn@ietf.org; Wed, 22 Feb 2006 18:53:58 -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 1FC3nx-00026p-HP for l2vpn@ietf.org; Wed, 22 Feb 2006 18:53:58 -0500 Received: from [127.0.0.1] (dog.tcb.net [64.78.150.133]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by dog.tcb.net (Postfix) with ESMTP id ACE836451E for ; Wed, 22 Feb 2006 16:53:50 -0700 (MST) Message-ID: <43FCF992.4020200@castlepoint.net> Date: Wed, 22 Feb 2006 16:53:54 -0700 From: Shane Amante User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: l2vpn@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Subject: draft-ietf-l2tpext-l2vpn-06.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 Folks, This begins a 1 week WG LC on draft-ietf-l2tpext-l2vpn-06.txt: http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-l2vpn-06.txt Please raise any comments to the list. Last Call will end on 3/1/2006 at 17:00 MST (GMT -7). -shane & Vach From l2vpn-bounces@ietf.org Wed Feb 22 18:58:02 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FC3ru-0000HE-L0; Wed, 22 Feb 2006 18:58:02 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FC3rt-0000H5-9y for l2vpn@ietf.org; Wed, 22 Feb 2006 18:58:01 -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 1FC3rs-0002CD-2y for l2vpn@ietf.org; Wed, 22 Feb 2006 18:58:01 -0500 Received: from [127.0.0.1] (dog.tcb.net [64.78.150.133]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by dog.tcb.net (Postfix) with ESMTP id 909B96451D for ; Wed, 22 Feb 2006 16:57:53 -0700 (MST) Message-ID: <43FCFA85.40403@castlepoint.net> Date: Wed, 22 Feb 2006 16:57:57 -0700 From: Shane Amante User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: l2vpn@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Subject: IETF 65: Tentative L2VPN Timeslot 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 FYI. It looks like we are tentatively schedule to meet on Thursday, 3/23/2006 at 1300: THURSDAY, March 23, 2006 [--snip--] 1130-1300 Break 1300-1500 Afternoon Session I APP widex Widget Description Exchange Service WG GEN techspec Requirements for IETF Technical Specification Publication BOF INT autoconf Ad-Hoc Network Autoconfiguration WG INT l2vpn Layer 2 Virtual Private Networks WG RAI geopriv Geographic Location/Privacy WG SEC saag Security Area Directorate Open Meeting TSV behave Behavior Engineering for Hindrance Avoidance WG TSV nfsv4 Network File System Version 4 WG Just a reminder that if you have items to discuss at the meeting, please forward them to Vach & I ASAP. -shane & Vach From l2vpn-bounces@ietf.org Thu Feb 23 16:53:10 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCOOZ-0006Pq-W1; Thu, 23 Feb 2006 16:53:07 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCOOZ-0006Pl-JQ for l2vpn@ietf.org; Thu, 23 Feb 2006 16:53:07 -0500 Received: from mailz.wwp.com ([65.107.175.7]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCOOX-0006nP-Vo for l2vpn@ietf.org; Thu, 23 Feb 2006 16:53:07 -0500 Received: from localhost (localhost.filter.com [127.0.0.1]) by mailz.wwp.com (Postfix) with ESMTP id 833995805 for ; Thu, 23 Feb 2006 13:53:02 -0800 (PST) Received: from mailz.wwp.com ([127.0.0.1]) by localhost (mailz.wwp.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12581-10 for ; Thu, 23 Feb 2006 13:52:51 -0800 (PST) Received: from mail.wwp.com (thorondor [192.168.6.15]) by mailz.wwp.com (Postfix) with ESMTP id 75F2A57F9 for ; Thu, 23 Feb 2006 13:52:51 -0800 (PST) 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_01C638C3.7F8A8D48" Date: Thu, 23 Feb 2006 13:52:53 -0800 Message-ID: <38954906F76F354DBEBDB8B5DA4CD29C2F5E43@thorondor.wwp.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: supporting both Ethernet PW and Ethernet VLAN PW on the same VSI on the same PE Thread-Index: AcY4w391SFQuvg2gQpSBxxO7noAwfQ== From: "Asheesh Jadav" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 3be09dac38eaa50f02d21c7fcee1128c Subject: Re: supporting both Ethernet PW and Ethernet VLAN PW on the same VSI on the same PE 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_01C638C3.7F8A8D48 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Can there also be a case where you need both these types of PWs to the same peer simultaneously for the same VSI? If so, when would this scenario arise? TIA, Asheesh =20 ----- Original Message ----- From: "Tao Gu" To: Sent: Wednesday, January 11, 2006 8:11 AM Subject: supporting both Ethernet PW and Ethernet VLAN PW on the same VSI on the same PE Hi folks, =20 According to section 8 in draft-ietf-l2vpn-vpls-ldp-08.txt, A VPLS MAY have both Ethernet and Ethernet VLAN PWs. However, if a PE is not able to support both PWs simultaneously, it SHOULD send a Label Release on the PW messages that it cannot support with a status code "Unknown FEC" as given in [RFC3036]. My understanding is that a VSI on the same PE (say PE1) can support both types of PWs, i.e., using a Ethernet PW to connect to PE2 while using a Ethernet VLAN PW to connect to PE3. Can anyone confirm this?=20 Tao, =20 This is correct as long as peer PEs support the corresponding PW types. =20 Marc =20 Thanks a lot in advance. =20 Best regards, =20 Tao Gu =20 -- Tao Gu =20 Centec Networks Inc. www.centecnetworks.com =20 tgu at centecnetworks.com Tel (0512) 62885358 ext 815 Fax (0512) 62885870 Cell 136-4621-3957 =20 ------_=_NextPart_001_01C638C3.7F8A8D48 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

Can there = also be a case where you need both these types of PWs to the same peer = simultaneously for the same VSI? If so, when would this scenario = arise?

TIA,

Asheesh

----- Original = Message ----- From: "Tao Gu" <gu at = centecnetworks.com>
To: <l2vpn at = ietf.org>
Sent: Wednesday, January 11, 2006 8:11 = AM
Subject: supporting both Ethernet PW and = Ethernet VLAN PW on the same VSI on the same PE

Hi folks,

According to section 8 in =
draft-ietf-l2vpn-vpls-ldp-08.txt,

A VPLS MAY have both Ethernet and Ethernet VLAN PWs. However, if a PE is = not able to support both PWs simultaneously, it SHOULD send a Label Release on = the PW messages that it cannot support with a status code "Unknown = FEC" as given in [RFC3036].
My understanding is that a VSI on the = same PE (say PE1) can support both types of PWs, i.e., using a Ethernet PW to connect = to PE2 while using a Ethernet VLAN PW to connect to PE3. Can anyone confirm = this?



Tao,

This is correct as long as peer PEs support =
the corresponding PW types.

Marc



Thanks a lot in advance.

Best regards,

Tao Gu

--

Tao =
Gu



Centec Networks Inc.

www.centecnetworks.com

tgu at =
centecnetworks.com

Tel =
(0512) 62885358 ext 815

Fax =
(0512) 62885870

Cell =
136-4621-3957

------_=_NextPart_001_01C638C3.7F8A8D48-- From l2vpn-bounces@ietf.org Thu Feb 23 16:58:58 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCOUA-0001Vz-Pa; Thu, 23 Feb 2006 16:58:54 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCOU9-0001Vl-VI for l2vpn@ietf.org; Thu, 23 Feb 2006 16:58:53 -0500 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCOU9-000723-D3 for l2vpn@ietf.org; Thu, 23 Feb 2006 16:58:53 -0500 Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-3.cisco.com with ESMTP; 23 Feb 2006 13:58:53 -0800 X-IronPort-AV: i="4.02,141,1139212800"; d="scan'208,217"; a="409276308:sNHT125901138" Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k1NLwqtD012336; Thu, 23 Feb 2006 13:58:52 -0800 (PST) Received: from xmb-sjc-21e.amer.cisco.com ([171.70.151.156]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 23 Feb 2006 13:58:52 -0800 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_01C638C4.554CC0AE" Date: Thu, 23 Feb 2006 13:58:51 -0800 Message-ID: <75B2A84D9323BC4CA3977CF378CE75EB012E9DA8@xmb-sjc-21e.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE Thread-Index: AcY4w391SFQuvg2gQpSBxxO7noAwfQAAH/Cg From: "Ali Sajassi \(sajassi\)" To: "Asheesh Jadav" , X-OriginalArrivalTime: 23 Feb 2006 21:58:52.0560 (UTC) FILETIME=[557C6900:01C638C4] X-Spam-Score: 0.0 (/) X-Scan-Signature: 4515df9441674711565101d9d5c4f63f Cc: Subject: RE: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE 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_01C638C4.554CC0AE Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable =20 ________________________________ From: Asheesh Jadav [mailto:asheeshj@wwp.com]=20 Sent: Thursday, February 23, 2006 1:53 PM To: l2vpn@ietf.org Subject: Re: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE =09 =09 Hi, Can there also be a case where you need both these types of PWs to the same peer simultaneously for the same VSI? If so, when would this scenario arise? [AS] No, by definition, there is only one PW per pair of PEs per VPLS instance (per VSI/PE). -Ali=20 TIA, Asheesh =20 ----- Original Message ----- From: "Tao Gu" To: Sent: Wednesday, January 11, 2006 8:11 AM Subject: supporting both Ethernet PW and Ethernet VLAN PW on the same VSI on the same PE =09 =09 Hi folks, =20 According to section 8 in draft-ietf-l2vpn-vpls-ldp-08.txt, =09 A VPLS MAY have both Ethernet and Ethernet VLAN PWs. However, if a PE is not able to support both PWs simultaneously, it SHOULD send a Label Release on the PW messages that it cannot support with a status code "Unknown FEC" as given in [RFC3036]. My understanding is that a VSI on the same PE (say PE1) can support both types of PWs, i.e., using a Ethernet PW to connect to PE2 while using a Ethernet VLAN PW to connect to PE3. Can anyone confirm this?=20 =09 =09 Tao, =20 This is correct as long as peer PEs support the corresponding PW types. =20 Marc =20 =09 =09 Thanks a lot in advance. =20 Best regards, =20 Tao Gu =20 -- Tao Gu =20 =09 =09 Centec Networks Inc. www.centecnetworks.com =20 tgu at centecnetworks.com Tel (0512) 62885358 ext 815 Fax (0512) 62885870 Cell 136-4621-3957 =20 ------_=_NextPart_001_01C638C4.554CC0AE Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

From: Asheesh Jadav = [mailto:asheeshj@wwp.com]=20
Sent: Thursday, February 23, 2006 1:53 PM
To:=20 l2vpn@ietf.org
Subject: Re: supporting both Ethernet PW and = Ethernet=20 VLAN PW on the sameVSI on the same PE

Hi,

Can there = also be a=20 case where you need both these types of PWs to the same peer = simultaneously=20 for the same VSI? If so, when would this scenario arise? [AS] No, by=20 definition, there is only one PW per pair of PEs per VPLS instance = (per=20 VSI/PE).

-Ali

TIA,

Asheesh

----- Original Message ----- = From: "Tao=20 Gu" <gu at centecnetworks.com>
To: <l2vpn at = ietf.org>
Sent: Wednesday, January 11, 2006 8:11=20 AM
Subject: supporting = both=20 Ethernet PW and Ethernet VLAN PW on the same VSI on the same=20 PE

Hi = folks,

According to section 8 in = draft-ietf-l2vpn-vpls-ldp-08.txt,

A VPLS MAY have both Ethernet = and=20 Ethernet VLAN PWs. However, if a PE is not able to support both PWs=20 simultaneously, it SHOULD send a Label Release on the PW messages that = it=20 cannot support with a status code "Unknown FEC" as given in=20 [RFC3036].
My understanding is that a VSI on the same PE = (say PE1) can=20 support both types of PWs, i.e., using a Ethernet PW to connect to PE2 = while=20 using a Ethernet VLAN PW to connect to PE3. Can anyone confirm this?=20

Tao,

This is correct as long as peer = PEs support the corresponding PW types.

Marc

Thanks a lot in advance.

Best = regards,

Tao = Gu

--
Tao = Gu

Centec Networks Inc.
www.centecnetworks.com

tgu at = centecnetworks.com
Tel (0512) = 62885358 ext 815
Fax (0512) = 62885870
Cell = 136-4621-3957

------_=_NextPart_001_01C638C4.554CC0AE-- From l2vpn-bounces@ietf.org Thu Feb 23 17:18:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCOn7-0006pj-4F; Thu, 23 Feb 2006 17:18:29 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCOn5-0006oF-Sh for l2vpn@ietf.org; Thu, 23 Feb 2006 17:18:27 -0500 Received: from mailz.wwp.com ([65.107.175.7]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCOn4-0007aj-6o for l2vpn@ietf.org; Thu, 23 Feb 2006 17:18:27 -0500 Received: from localhost (localhost.filter.com [127.0.0.1]) by mailz.wwp.com (Postfix) with ESMTP id DFF285830; Thu, 23 Feb 2006 14:18:22 -0800 (PST) Received: from mailz.wwp.com ([127.0.0.1]) by localhost (mailz.wwp.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12988-02; Thu, 23 Feb 2006 14:18:11 -0800 (PST) Received: from mail.wwp.com (thorondor [192.168.6.15]) by mailz.wwp.com (Postfix) with ESMTP id BB4B35805; Thu, 23 Feb 2006 14:18:11 -0800 (PST) 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_01C638C7.09C7EEE8" Date: Thu, 23 Feb 2006 14:18:14 -0800 Message-ID: <38954906F76F354DBEBDB8B5DA4CD29C2F5E44@thorondor.wwp.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE Thread-Index: AcY4w391SFQuvg2gQpSBxxO7noAwfQAAH/CgAACVZZA= From: "Asheesh Jadav" To: "Ali Sajassi (sajassi)" , X-Spam-Score: 0.0 (/) X-Scan-Signature: 439b8e44c906b144bce6744ebb966e60 Cc: Subject: RE: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE 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_01C638C7.09C7EEE8 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable So is it possible to have a mix-and-match of VLAN tagged and untagged services on a pair of PEs per VSI or is there never a need for this case?=20 =20 =20 Thanks, Asheesh ________________________________ From: Ali Sajassi (sajassi) [mailto:sajassi@cisco.com]=20 Sent: Thursday, February 23, 2006 1:59 PM To: Asheesh Jadav; l2vpn@ietf.org Subject: RE: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE =20 =20 =20 =09 ________________________________ From: Asheesh Jadav [mailto:asheeshj@wwp.com]=20 Sent: Thursday, February 23, 2006 1:53 PM To: l2vpn@ietf.org Subject: Re: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE Hi, Can there also be a case where you need both these types of PWs to the same peer simultaneously for the same VSI? If so, when would this scenario arise? [AS] No, by definition, there is only one PW per pair of PEs per VPLS instance (per VSI/PE). -Ali=20 TIA, Asheesh =20 ----- Original Message ----- From: "Tao Gu" To: Sent: Wednesday, January 11, 2006 8:11 AM Subject: supporting both Ethernet PW and Ethernet VLAN PW on the same VSI on the same PE Hi folks, =20 According to section 8 in draft-ietf-l2vpn-vpls-ldp-08.txt, =09 A VPLS MAY have both Ethernet and Ethernet VLAN PWs. However, if a PE is not able to support both PWs simultaneously, it SHOULD send a Label Release on the PW messages that it cannot support with a status code "Unknown FEC" as given in [RFC3036]. My understanding is that a VSI on the same PE (say PE1) can support both types of PWs, i.e., using a Ethernet PW to connect to PE2 while using a Ethernet VLAN PW to connect to PE3. Can anyone confirm this?=20 =09 =09 =09 =09 =09 Tao, =20 This is correct as long as peer PEs support the corresponding PW types. =20 Marc =20 =09 =09 =09 =09 =09 Thanks a lot in advance. =20 Best regards, =20 Tao Gu =20 -- Tao Gu =20 =09 =09 =09 =09 =09 Centec Networks Inc. www.centecnetworks.com =20 tgu at centecnetworks.com Tel (0512) 62885358 ext 815 Fax (0512) 62885870 Cell 136-4621-3957 =20 ------_=_NextPart_001_01C638C7.09C7EEE8 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

So is it possible to have a = mix-and-match of VLAN tagged and untagged services on a pair of PEs per VSI or is = there never a need for this case?

Thanks,

Asheesh

From: Ali = Sajassi (sajassi) [mailto:sajassi@cisco.com]
Sent: Thursday, February = 23, 2006 1:59 PM
To: Asheesh Jadav; l2vpn@ietf.org
Subject: RE: supporting = both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same = PE

=

From: Asheesh Jadav [mailto:asheeshj@wwp.com] =
Sent: Thursday, February = 23, 2006 1:53 PM
To: l2vpn@ietf.org
Subject: Re: supporting = both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same = PE

Hi,

Can there = also be a case where you need both these types of PWs to the same peer = simultaneously for the same VSI? If so, when would this scenario = arise?
[AS] No, by definition, there is = only one PW per pair of PEs per VPLS instance (per = VSI/PE).

-Ali

TIA,

Asheesh

----- Original = Message ----- From: "Tao Gu" <gu at = centecnetworks.com>
To: <l2vpn at = ietf.org>
Sent: Wednesday, January 11, 2006 8:11 = AM
Subject: supporting both Ethernet PW and = Ethernet VLAN PW on the same VSI on the same = PE
Hi folks,
According to section 8 in =
draft-ietf-l2vpn-vpls-ldp-08.txt,
A VPLS MAY have both Ethernet and Ethernet VLAN PWs. However, if a PE is = not able to support both PWs simultaneously, it SHOULD send a Label Release on = the PW messages that it cannot support with a status code "Unknown = FEC" as given in [RFC3036].
My understanding is that a VSI on the = same PE (say PE1) can support both types of PWs, i.e., using a Ethernet PW to connect = to PE2 while using a Ethernet VLAN PW to connect to PE3. Can anyone confirm = this?
Tao,
This is correct as long as peer PEs support =
the corresponding PW types.
Marc
Thanks a lot in =
advance.
Best regards,
Tao Gu
--
Tao =
Gu
Centec Networks =
Inc.
www.centecnetworks.com
tgu at = centecnetworks.com
Tel = (0512) 62885358 ext 815
Fax = (0512) 62885870
Cell = 136-4621-3957

------_=_NextPart_001_01C638C7.09C7EEE8-- From l2vpn-bounces@ietf.org Thu Feb 23 17:25:10 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCOtW-0004SS-Ux; Thu, 23 Feb 2006 17:25:06 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCOtV-0004QV-Ld for l2vpn@ietf.org; Thu, 23 Feb 2006 17:25:05 -0500 Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCOtU-0007h4-TL for l2vpn@ietf.org; Thu, 23 Feb 2006 17:25:05 -0500 Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-1.cisco.com with ESMTP; 23 Feb 2006 14:25:05 -0800 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k1NMP4Vb003154; Thu, 23 Feb 2006 14:25:04 -0800 (PST) Received: from xmb-sjc-21e.amer.cisco.com ([171.70.151.156]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 23 Feb 2006 14:25:04 -0800 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_01C638C7.FE2A15F1" Date: Thu, 23 Feb 2006 14:25:03 -0800 Message-ID: <75B2A84D9323BC4CA3977CF378CE75EB012E9DC6@xmb-sjc-21e.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE Thread-Index: AcY4w391SFQuvg2gQpSBxxO7noAwfQAAH/CgAACVZZAAAElZgA== From: "Ali Sajassi \(sajassi\)" To: "Asheesh Jadav" , X-OriginalArrivalTime: 23 Feb 2006 22:25:04.0242 (UTC) FILETIME=[FE480D20:01C638C7] X-Spam-Score: 0.0 (/) X-Scan-Signature: 4de5d7f989d6c039c8b887f1940f36ab Cc: Subject: RE: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE 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_01C638C7.FE2A15F1 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable =20 VPLS instance is defined as a single broadcast domain (e.g., analogous to a VLAN in IEEE 802.1ad). So, you can have a mix of tagged and untagged frames within a VSI but that would imply that all those tagged and untagged frames share the same broadcast domain which further imply they need to have a unique MAC addresses across them (no overlapping of MAC addresses are allowed in this case). =20 -Ali ________________________________ From: Asheesh Jadav [mailto:asheeshj@wwp.com]=20 Sent: Thursday, February 23, 2006 2:18 PM To: Ali Sajassi (sajassi); l2vpn@ietf.org Subject: RE: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE =09 =09 So is it possible to have a mix-and-match of VLAN tagged and untagged services on a pair of PEs per VSI or is there never a need for this case?=20 =20 =20 Thanks, Asheesh =09 ________________________________ From: Ali Sajassi (sajassi) [mailto:sajassi@cisco.com]=20 Sent: Thursday, February 23, 2006 1:59 PM To: Asheesh Jadav; l2vpn@ietf.org Subject: RE: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE =20 =20 =20 =09 ________________________________ From: Asheesh Jadav [mailto:asheeshj@wwp.com]=20 Sent: Thursday, February 23, 2006 1:53 PM To: l2vpn@ietf.org Subject: Re: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE Hi, Can there also be a case where you need both these types of PWs to the same peer simultaneously for the same VSI? If so, when would this scenario arise? [AS] No, by definition, there is only one PW per pair of PEs per VPLS instance (per VSI/PE). -Ali=20 TIA, Asheesh =20 ----- Original Message ----- From: "Tao Gu" To: Sent: Wednesday, January 11, 2006 8:11 AM Subject: supporting both Ethernet PW and Ethernet VLAN PW on the same VSI on the same PE Hi folks, =20 According to section 8 in draft-ietf-l2vpn-vpls-ldp-08.txt, =09 A VPLS MAY have both Ethernet and Ethernet VLAN PWs. However, if a PE is not able to support both PWs simultaneously, it SHOULD send a Label Release on the PW messages that it cannot support with a status code "Unknown FEC" as given in [RFC3036]. My understanding is that a VSI on the same PE (say PE1) can support both types of PWs, i.e., using a Ethernet PW to connect to PE2 while using a Ethernet VLAN PW to connect to PE3. Can anyone confirm this?=20 =09 =09 =09 =09 =09 Tao, =20 This is correct as long as peer PEs support the corresponding PW types. =20 Marc =20 =09 =09 =09 =09 =09 Thanks a lot in advance. =20 Best regards, =20 Tao Gu =20 -- Tao Gu =20 =09 =09 =09 =09 =09 Centec Networks Inc. www.centecnetworks.com =20 tgu at centecnetworks.com Tel (0512) 62885358 ext 815 Fax (0512) 62885870 Cell 136-4621-3957 =20 ------_=_NextPart_001_01C638C7.FE2A15F1 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

VPLS instance is defined as a single broadcast = domain=20 (e.g., analogous to a VLAN in IEEE 802.1ad). So, you can have a mix of = tagged=20 and untagged frames within a VSI but that would imply that all those = tagged and=20 untagged frames share the same broadcast domain which further imply = they=20 need to have a unique MAC addresses across them (no overlapping of MAC = addresses=20 are allowed in this case).

-Ali

From: Asheesh Jadav = [mailto:asheeshj@wwp.com]=20
Sent: Thursday, February 23, 2006 2:18 PM
To: Ali = Sajassi=20 (sajassi); l2vpn@ietf.org
Subject: RE: supporting both = Ethernet PW=20 and Ethernet VLAN PW on the sameVSI on the same = PE

So is it = possible to=20 have a mix-and-match of VLAN tagged and untagged services on a pair of = PEs per=20 VSI or is there never a need for this case? =

Thanks,

Asheesh

From: Ali=20 Sajassi (sajassi) [mailto:sajassi@cisco.com]
Sent: Thursday, February 23, = 2006 1:59=20 PM
To: = Asheesh Jadav;=20 l2vpn@ietf.org
Subject: RE:=20 supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the = same=20 PE

From:=20 Asheesh Jadav=20 [mailto:asheeshj@wwp.com]
Sent: Thursday, February 23, = 2006 1:53=20 PM
To:=20 l2vpn@ietf.org
Subject: Re:=20 supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on = the same=20 PE

Hi,

Can there also be a = case where=20 you need both these types of PWs to the same peer simultaneously for = the=20 same VSI? If so, when would this scenario = arise?
[AS] No, = by=20 definition, there is only one PW per pair of PEs per VPLS instance = (per=20 VSI/PE).

-Ali

TIA,

Asheesh

----- Original Message = ----- From: "Tao=20 Gu" <gu at centecnetworks.com>
To: <l2vpn at = ietf.org>
Sent: Wednesday, January 11, 2006 8:11=20 AM
Subject: supporting = both=20 Ethernet PW and Ethernet VLAN PW on the same VSI on the same=20 PE
Hi = folks,

According to section 8 in = draft-ietf-l2vpn-vpls-ldp-08.txt,

A VPLS MAY have both = Ethernet and=20 Ethernet VLAN PWs. However, if a PE is not able to support both PWs=20 simultaneously, it SHOULD send a Label Release on the PW messages = that it=20 cannot support with a status code "Unknown FEC" as given in=20 [RFC3036].
My understanding is that a VSI on the same PE = (say PE1)=20 can support both types of PWs, i.e., using a Ethernet PW to connect = to PE2=20 while using a Ethernet VLAN PW to connect to PE3. Can anyone confirm = this?=20

Tao,

This is correct as long as peer = PEs support the corresponding PW types.

Marc

Thanks a lot in = advance.

Best = regards,

Tao = Gu

--
Tao = Gu

Centec Networks = Inc.
www.centecnetworks.com

tgu at = centecnetworks.com
Tel (0512) = 62885358 ext 815
Fax (0512) = 62885870
Cell = 136-4621-3957

------_=_NextPart_001_01C638C7.FE2A15F1-- From l2vpn-bounces@ietf.org Thu Feb 23 17:37:49 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCP5l-0003QK-SX; Thu, 23 Feb 2006 17:37:45 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCP5k-0003Q6-FF for l2vpn@ietf.org; Thu, 23 Feb 2006 17:37:44 -0500 Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCP5j-00087S-LB for l2vpn@ietf.org; Thu, 23 Feb 2006 17:37:44 -0500 Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-2.cisco.com with ESMTP; 23 Feb 2006 14:37:43 -0800 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k1NMbhtD024104; Thu, 23 Feb 2006 14:37:43 -0800 (PST) Received: from xmb-sjc-21e.amer.cisco.com ([171.70.151.156]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 23 Feb 2006 14:37:43 -0800 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_01C638C9.C2573C60" Date: Thu, 23 Feb 2006 14:37:42 -0800 Message-ID: <75B2A84D9323BC4CA3977CF378CE75EB012E9DD6@xmb-sjc-21e.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE Thread-Index: AcY4w391SFQuvg2gQpSBxxO7noAwfQAAH/CgAACVZZAAAElZgAAAbSAQAAAfj9A= From: "Ali Sajassi \(sajassi\)" To: "Asheesh Jadav" , X-OriginalArrivalTime: 23 Feb 2006 22:37:43.0071 (UTC) FILETIME=[C2942AF0:01C638C9] X-Spam-Score: 0.0 (/) X-Scan-Signature: cb592aae7f4601895f35714165597859 Cc: Subject: RE: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE 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_01C638C9.C2573C60 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable raw mode. =20 -Ali ________________________________ From: Asheesh Jadav [mailto:asheeshj@wwp.com]=20 Sent: Thursday, February 23, 2006 2:36 PM To: Ali Sajassi (sajassi); l2vpn@ietf.org Subject: RE: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE =09 =09 But in such a case how would one decide the PW type between the PEs for this VSI?=20 =20 Thanks, Asheesh =20 =09 ________________________________ From: Ali Sajassi (sajassi) [mailto:sajassi@cisco.com]=20 Sent: Thursday, February 23, 2006 2:25 PM To: Asheesh Jadav; l2vpn@ietf.org Subject: RE: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE =20 =20 VPLS instance is defined as a single broadcast domain (e.g., analogous to a VLAN in IEEE 802.1ad). So, you can have a mix of tagged and untagged frames within a VSI but that would imply that all those tagged and untagged frames share the same broadcast domain which further imply they need to have a unique MAC addresses across them (no overlapping of MAC addresses are allowed in this case). =20 -Ali =20 =09 ________________________________ From: Asheesh Jadav [mailto:asheeshj@wwp.com]=20 Sent: Thursday, February 23, 2006 2:18 PM To: Ali Sajassi (sajassi); l2vpn@ietf.org Subject: RE: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE So is it possible to have a mix-and-match of VLAN tagged and untagged services on a pair of PEs per VSI or is there never a need for this case?=20 =20 =20 Thanks, Asheesh =09 ________________________________ From: Ali Sajassi (sajassi) [mailto:sajassi@cisco.com]=20 Sent: Thursday, February 23, 2006 1:59 PM To: Asheesh Jadav; l2vpn@ietf.org Subject: RE: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE =20 =20 =20 =09 ________________________________ From: Asheesh Jadav [mailto:asheeshj@wwp.com]=20 Sent: Thursday, February 23, 2006 1:53 PM To: l2vpn@ietf.org Subject: Re: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE Hi, Can there also be a case where you need both these types of PWs to the same peer simultaneously for the same VSI? If so, when would this scenario arise? [AS] No, by definition, there is only one PW per pair of PEs per VPLS instance (per VSI/PE). -Ali=20 TIA, Asheesh =20 ----- Original Message ----- From: "Tao Gu" To: Sent: Wednesday, January 11, 2006 8:11 AM Subject: supporting both Ethernet PW and Ethernet VLAN PW on the same VSI on the same PE Hi folks, =20 According to section 8 in draft-ietf-l2vpn-vpls-ldp-08.txt, =09 A VPLS MAY have both Ethernet and Ethernet VLAN PWs. However, if a PE is not able to support both PWs simultaneously, it SHOULD send a Label Release on the PW messages that it cannot support with a status code "Unknown FEC" as given in [RFC3036]. My understanding is that a VSI on the same PE (say PE1) can support both types of PWs, i.e., using a Ethernet PW to connect to PE2 while using a Ethernet VLAN PW to connect to PE3. Can anyone confirm this?=20 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =20 Tao, =20 This is correct as long as peer PEs support the corresponding PW types. =20 Marc =20 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =20 Thanks a lot in advance. =20 Best regards, =20 Tao Gu =20 -- Tao Gu =20 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =20 Centec Networks Inc. www.centecnetworks.com =20 tgu at centecnetworks.com Tel (0512) 62885358 ext 815 Fax (0512) 62885870 Cell 136-4621-3957 =20 ------_=_NextPart_001_01C638C9.C2573C60 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

raw mode.

-Ali

From: Asheesh Jadav = [mailto:asheeshj@wwp.com]=20
Sent: Thursday, February 23, 2006 2:36 PM
To: Ali = Sajassi=20 (sajassi); l2vpn@ietf.org
Subject: RE: supporting both = Ethernet PW=20 and Ethernet VLAN PW on the sameVSI on the same = PE
But in such = a case=20 how would one decide the PW type between the PEs for this VSI?=20

Thanks,

Asheesh

From: Ali=20 Sajassi (sajassi) [mailto:sajassi@cisco.com]
Sent: Thursday, February 23, = 2006 2:25=20 PM
To: = Asheesh Jadav;=20 l2vpn@ietf.org
Subject: RE:=20 supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the = same=20 PE

VPLS = instance is=20 defined as a single broadcast domain (e.g., analogous to a VLAN in = IEEE=20 802.1ad). So, you can have a mix of tagged and untagged frames within = a VSI=20 but that would imply that all those tagged and untagged frames share = the same=20 broadcast domain which further imply they need to have a unique = MAC=20 addresses across them (no overlapping of MAC addresses are allowed in = this=20 case).

-Ali

From:=20 Asheesh Jadav=20 [mailto:asheeshj@wwp.com]
Sent: Thursday, February 23, = 2006 2:18=20 PM
To: Ali = Sajassi=20 (sajassi); l2vpn@ietf.org
Subject: RE: supporting both = Ethernet=20 PW and Ethernet VLAN PW on the sameVSI on the same=20 PE

So is it = possible=20 to have a mix-and-match of VLAN tagged and untagged services on a = pair of=20 PEs per VSI or is there never a need for this case?=20

Thanks,

Asheesh

From: Ali=20 Sajassi (sajassi) [mailto:sajassi@cisco.com]
Sent: Thursday, February 23, = 2006 1:59=20 PM
To: = Asheesh Jadav;=20 l2vpn@ietf.org
Subject: RE:=20 supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on = the same=20 PE

From:=20 Asheesh Jadav=20 [mailto:asheeshj@wwp.com]
Sent: Thursday, February = 23, 2006=20 1:53 PM
To:=20 l2vpn@ietf.org
Subject:=20 Re: supporting both Ethernet PW and Ethernet VLAN PW on the = sameVSI on the=20 same PE

Hi,

Can there=20 also be a case where you need both these types of PWs to the same = peer=20 simultaneously for the same VSI? If so, when would this scenario=20 arise?
[AS] = No, by=20 definition, there is only one PW per pair of PEs per VPLS instance = (per=20 VSI/PE).

-Ali

TIA,

Asheesh

----- Original=20 Message ----- From: "Tao Gu" <gu at=20 centecnetworks.com>
To: <l2vpn at = ietf.org>
Sent: Wednesday, January 11, 2006 8:11=20 AM
Subject: = supporting both=20 Ethernet PW and Ethernet VLAN PW on the same VSI on the same=20 PE
Hi = folks,

According to section 8 in = draft-ietf-l2vpn-vpls-ldp-08.txt,

A VPLS MAY have both = Ethernet and=20 Ethernet VLAN PWs. However, if a PE is not able to support both = PWs=20 simultaneously, it SHOULD send a Label Release on the PW messages = that it=20 cannot support with a status code "Unknown FEC" as given in=20 [RFC3036].
My understanding is that a VSI on the same PE = (say PE1)=20 can support both types of PWs, i.e., using a Ethernet PW to = connect to PE2=20 while using a Ethernet VLAN PW to connect to PE3. Can anyone = confirm this?=20

Tao,

This is correct as long as peer = PEs support the corresponding PW types.

Marc

Thanks a lot in = advance.

Best = regards,

Tao = Gu

--
Tao = Gu

Centec Networks = Inc.
www.centecnetworks.com

tgu at = centecnetworks.com
Tel (0512) = 62885358 ext 815
Fax (0512) = 62885870
Cell = 136-4621-3957

------_=_NextPart_001_01C638C9.C2573C60-- From l2vpn-bounces@ietf.org Thu Feb 23 17:38:46 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCP4Z-0003CX-1B; Thu, 23 Feb 2006 17:36:31 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCP4X-0003BZ-Pj for l2vpn@ietf.org; Thu, 23 Feb 2006 17:36:29 -0500 Received: from mailz.wwp.com ([65.107.175.7]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCP4V-00086F-TP for l2vpn@ietf.org; Thu, 23 Feb 2006 17:36:29 -0500 Received: from localhost (localhost.filter.com [127.0.0.1]) by mailz.wwp.com (Postfix) with ESMTP id BCC8F5836; Thu, 23 Feb 2006 14:36:24 -0800 (PST) Received: from mailz.wwp.com ([127.0.0.1]) by localhost (mailz.wwp.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12988-10; Thu, 23 Feb 2006 14:36:13 -0800 (PST) Received: from mail.wwp.com (thorondor [192.168.6.15]) by mailz.wwp.com (Postfix) with ESMTP id 797295831; Thu, 23 Feb 2006 14:36:13 -0800 (PST) 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_01C638C9.8E908A18" Date: Thu, 23 Feb 2006 14:36:15 -0800 Message-ID: <38954906F76F354DBEBDB8B5DA4CD29C2F5E45@thorondor.wwp.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE Thread-Index: AcY4w391SFQuvg2gQpSBxxO7noAwfQAAH/CgAACVZZAAAElZgAAAbSAQ From: "Asheesh Jadav" To: "Ali Sajassi (sajassi)" , X-Spam-Score: 0.0 (/) X-Scan-Signature: ff8f6fb66123e35ba88156f838266c1a Cc: Subject: RE: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE 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_01C638C9.8E908A18 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable But in such a case how would one decide the PW type between the PEs for this VSI?=20 =20 Thanks, Asheesh =20 ________________________________ From: Ali Sajassi (sajassi) [mailto:sajassi@cisco.com]=20 Sent: Thursday, February 23, 2006 2:25 PM To: Asheesh Jadav; l2vpn@ietf.org Subject: RE: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE =20 =20 VPLS instance is defined as a single broadcast domain (e.g., analogous to a VLAN in IEEE 802.1ad). So, you can have a mix of tagged and untagged frames within a VSI but that would imply that all those tagged and untagged frames share the same broadcast domain which further imply they need to have a unique MAC addresses across them (no overlapping of MAC addresses are allowed in this case). =20 -Ali =20 =09 ________________________________ From: Asheesh Jadav [mailto:asheeshj@wwp.com]=20 Sent: Thursday, February 23, 2006 2:18 PM To: Ali Sajassi (sajassi); l2vpn@ietf.org Subject: RE: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE So is it possible to have a mix-and-match of VLAN tagged and untagged services on a pair of PEs per VSI or is there never a need for this case?=20 =20 =20 Thanks, Asheesh =09 ________________________________ From: Ali Sajassi (sajassi) [mailto:sajassi@cisco.com]=20 Sent: Thursday, February 23, 2006 1:59 PM To: Asheesh Jadav; l2vpn@ietf.org Subject: RE: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE =20 =20 =20 =09 ________________________________ From: Asheesh Jadav [mailto:asheeshj@wwp.com]=20 Sent: Thursday, February 23, 2006 1:53 PM To: l2vpn@ietf.org Subject: Re: supporting both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same PE Hi, Can there also be a case where you need both these types of PWs to the same peer simultaneously for the same VSI? If so, when would this scenario arise? [AS] No, by definition, there is only one PW per pair of PEs per VPLS instance (per VSI/PE). -Ali=20 TIA, Asheesh =20 ----- Original Message ----- From: "Tao Gu" To: Sent: Wednesday, January 11, 2006 8:11 AM Subject: supporting both Ethernet PW and Ethernet VLAN PW on the same VSI on the same PE Hi folks, =20 According to section 8 in draft-ietf-l2vpn-vpls-ldp-08.txt, =09 A VPLS MAY have both Ethernet and Ethernet VLAN PWs. However, if a PE is not able to support both PWs simultaneously, it SHOULD send a Label Release on the PW messages that it cannot support with a status code "Unknown FEC" as given in [RFC3036]. My understanding is that a VSI on the same PE (say PE1) can support both types of PWs, i.e., using a Ethernet PW to connect to PE2 while using a Ethernet VLAN PW to connect to PE3. Can anyone confirm this?=20 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =20 Tao, =20 This is correct as long as peer PEs support the corresponding PW types. =20 Marc =20 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =20 Thanks a lot in advance. =20 Best regards, =20 Tao Gu =20 -- Tao Gu =20 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =20 Centec Networks Inc. www.centecnetworks.com =20 tgu at centecnetworks.com Tel (0512) 62885358 ext 815 Fax (0512) 62885870 Cell 136-4621-3957 =20 ------_=_NextPart_001_01C638C9.8E908A18 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

But in such a case how would one = decide the PW type between the PEs for this VSI?

Thanks,

Asheesh

From: Ali = Sajassi (sajassi) [mailto:sajassi@cisco.com]
Sent: Thursday, February = 23, 2006 2:25 PM
To: Asheesh Jadav; l2vpn@ietf.org
Subject: RE: supporting = both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same = PE

VPLS instance is defined as a = single broadcast domain (e.g., analogous to a VLAN in IEEE 802.1ad). So, you = can have a mix of tagged and untagged frames within a VSI but that would imply = that all those tagged and untagged frames share the same broadcast = domain which further imply they need to have a unique MAC addresses across them (no overlapping of MAC addresses are allowed in this = case).

-Ali

=

From: Asheesh Jadav [mailto:asheeshj@wwp.com] =
Sent: Thursday, February = 23, 2006 2:18 PM
To: Ali Sajassi = (sajassi); l2vpn@ietf.org
Subject: RE: supporting = both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same = PE

So is it possible to have a = mix-and-match of VLAN tagged and untagged services on a pair of PEs per VSI or is = there never a need for this case?

Thanks,
=
Asheesh
=

From: Ali = Sajassi (sajassi) [mailto:sajassi@cisco.com]
Sent: Thursday, February = 23, 2006 1:59 PM
To: Asheesh Jadav; l2vpn@ietf.org
Subject: RE: supporting = both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same = PE
=

From: Asheesh Jadav [mailto:asheeshj@wwp.com] =
Sent: Thursday, February = 23, 2006 1:53 PM
To: l2vpn@ietf.org
Subject: Re: supporting = both Ethernet PW and Ethernet VLAN PW on the sameVSI on the same = PE

Hi,

Can there = also be a case where you need both these types of PWs to the same peer = simultaneously for the same VSI? If so, when would this scenario = arise?
[AS] No, by definition, there is = only one PW per pair of PEs per VPLS instance (per = VSI/PE).

-Ali

TIA,

Asheesh

----- Original = Message ----- From: "Tao Gu" <gu at = centecnetworks.com>
To: <l2vpn at = ietf.org>
Sent: Wednesday, January 11, 2006 8:11 = AM
Subject: supporting both Ethernet PW and = Ethernet VLAN PW on the same VSI on the same = PE
Hi folks,
According to section 8 in =
draft-ietf-l2vpn-vpls-ldp-08.txt,
A VPLS MAY have both Ethernet and Ethernet VLAN PWs. However, if a PE is = not able to support both PWs simultaneously, it SHOULD send a Label Release on = the PW messages that it cannot support with a status code "Unknown = FEC" as given in [RFC3036].
My understanding is that a VSI on the = same PE (say PE1) can support both types of PWs, i.e., using a Ethernet PW to connect = to PE2 while using a Ethernet VLAN PW to connect to PE3. Can anyone confirm = this?
 
Tao,
This is correct as long as peer PEs support =
the corresponding PW types.
Marc
 
Thanks a =
lot in advance.
Best regards,
Tao Gu
--
Tao =
Gu
 
Centec =
Networks Inc.
www.centecnetworks.com
tgu at = centecnetworks.com
Tel = (0512) 62885358 ext 815
Fax = (0512) 62885870
Cell = 136-4621-3957

------_=_NextPart_001_01C638C9.8E908A18--