RE: L2vpn Digest, Vol 95, Issue 93

[Lucy yong <[e-mail]>]

Sam,

I think we are talking two different things. S-VLAN IDs for root and leaf are necessary to be informed between PE and remote PE. Here we talk about the frames from/to s-tagged port and how PE performs local translation in supporting E-Tree.

If you are still confused, please read many e-mail responses for original subject carefully.

Regards,
Lucy  
-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On Behalf Of Sam Cao
Sent: Wednesday, April 25, 2012 9:11 PM
To: [e-mail]
Subject: RE: L2vpn Digest, Vol 95, Issue 93

Lucy,

I am confused with "use local translation instead of mapping". My
understanding on this is, there is VLAN mapping negotiation between ingress
PE and egress PE. This meeting global VLAN allocation is proposed, but based
on my understanding, we should add new VLAN ID, for raw mode or tagged mode.
Anything missing?

Thanks,

Sam

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On Behalf Of
[e-mail]
Sent: Thursday, April 26, 2012 5:02 AM
To: [e-mail]
Subject: L2vpn Digest, Vol 95, Issue 93

If you have received this digest without all the individual message
attachments you will need to update your digest options in your list
subscription.  To do so, go to 

https://www.ietf.org/mailman/listinfo/l2vpn

Click the 'Unsubscribe or edit options' button, log in, and set "Get
MIME or Plain Text Digests?" to MIME.  You can set this option
globally for all the list digests you receive at this point.



Send L2vpn mailing list submissions to
	[e-mail]

To subscribe or unsubscribe via the World Wide Web, visit
	https://www.ietf.org/mailman/listinfo/l2vpn
or, via email, send a message with subject or body 'help' to
	[e-mail]

You can reach the person managing the list at
	[e-mail]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of L2vpn digest..."


Today's Topics:

   1. RE: The status of the approaches to the E-Tree solution?
      (Lucy yong)


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

Message: 1
Date: Wed, 25 Apr 2012 20:59:59 +0000
From: Lucy yong <[e-mail]>
To: Daniel Cohn <[e-mail]>, "Rogers, Josh"
	<[e-mail]>, Shahram Davari <[e-mail]>,
	Lizhong Jin <[e-mail]>, "[e-mail]"
<[e-mail]>,
	"[e-mail]"
<[e-mail]>
Cc: "[e-mail]" <[e-mail]>
Subject: RE: The status of the approaches to the E-Tree solution?
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D3264C1A2@dfweml505-mbx>
Content-Type: text/plain; charset="utf-8"

The current VLAN draft does not assume double tag frame at AC. If we have to
consider this case, the solution was discussed in the e-mail. I should use
local translation instead of mapping in previous e-mail, which makes it more
clear. In this case, PE knows which S-VLAN ID is used on an AC, so PE
inserts the same S-VLAN ID on the frames going toward to the AC. This is the
part you missed.

Lucy

-----Original Message-----
From: Daniel Cohn [mailto:[e-mail]] 
Sent: Wednesday, April 25, 2012 3:31 PM
To: Lucy yong; Rogers, Josh; Shahram Davari; Lizhong Jin; [e-mail];
[e-mail]
Cc: [e-mail]
Subject: RE: The status of the approaches to the E-Tree solution?

Lucy, don't understand what you mean by "obey the rule first".
Say you get a frame with double tag at a leaf ac. According to the 2 vlan
draft, you must add the leaf vlan before forwarding the frame to the mpls,
otherwise the egress pe won't know it can only forward the frame over root
acs. If you remove the outer tag on ingress, how can you recover it on
egress? If you don't remove it, you get a 3-deep stack.

Daniel

Thumb typed - please be tolerant

Lucy yong <[e-mail]> wrote:

Local mapping is sufficient for this. If a customer wish both ingress VLAN
ID and egress VLAN ID are the same, it obeys the rule first, then local
translate in MPLS will work perfectly.
Lucy

-----Original Message-----
From: Daniel Cohn [mailto:[e-mail]] 
Sent: Wednesday, April 25, 2012 2:46 PM
To: Lucy yong; Rogers, Josh; Shahram Davari; Lizhong Jin; [e-mail];
[e-mail]
Cc: [e-mail]
Subject: RE: The status of the approaches to the E-Tree solution?

And to this I asked how this mapping works - how does the egress pe recover
the ingress vid when it gets the frame tagged with only the root/leaf vid?
How can you convey the ingress vid plus the root/leaf attribute in the same
number of bits?
What am I missing?

Daniel

Thumb typed - please be tolerant

Lucy yong <[e-mail]> wrote:

Daniel,

David Allen already explained the solution. 

>From David:
ingress VLAN ID <-> Etree Root/Leaf VID <-> Egress VID.

Ingress VID does not have to equal Egress VID but regardless there is only
ever one VID on a frame at a time.

-end

This works when customer makes ingress VLAN ID not equal to or equal to
egress VLAN ID.

Regards,
Lucy

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On Behalf Of
Daniel Cohn
Sent: Wednesday, April 25, 2012 11:39 AM
To: Lucy yong; Rogers, Josh; Shahram Davari; Lizhong Jin; [e-mail];
[e-mail]
Cc: [e-mail]
Subject: RE: The status of the approaches to the E-Tree solution?

Hi Lucy,

The scenario we are discussing is not the E-Tree E-NNI, but a general
scenario where frames arriving at the root or leaf AC  are already double
tagged. In this case, the dual vlan solution cannot preserve the vlans
without adding a third one, can it?

Maybe Shahram can add details on the scenario he had in mind

Thumb typed - please be tolerant

Lucy yong <[e-mail]> wrote:

Daniel,

MEF has S-VLAN preservation attribute for ENNI only because there is no
s-vlan at UNI. When an MEN connects to multiple ENNI interfaces, S-VALN
preservation attribute is used. It applies to E-Tree as well.

Regards,
Lucy

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On Behalf Of
Daniel Cohn
Sent: Tuesday, April 24, 2012 2:12 AM
To: Lucy yong; Rogers, Josh; Shahram Davari; Lizhong Jin; [e-mail];
[e-mail]
Cc: [e-mail]
Subject: RE: The status of the approaches to the E-Tree solution?

Lucy,

even if the current MEF framework doesn't require s-vlan preservation, I
believe it's to the industry's benefit to adopt a solution that is not
constrained to a specific enni model that, like all things networking, is
likely to evolve. Especially when such a solution is available.

Daniel

Thumb typed - please be tolerant

Lucy yong <[e-mail]> wrote:

Daniel,

MEF has worked in ENNI interface for a long time with many service
providers' inputs. It had a fair reason to assume S-VLAN over ENNI by then.
It may open B-VLAN for the future. It is better for us not to discuss  a
future framework here, because it will lead us to nowhere. Here, we want to
extend VPLS in supporting E-Tree.

Best Regards,
Lucy

From: [e-mail] [mailto:[e-mail]] On Behalf Of
Daniel Cohn
Sent: Sunday, April 22, 2012 7:34 AM
To: Rogers, Josh; Shahram Davari; Lizhong Jin; [e-mail];
[e-mail]
Cc: [e-mail]
Subject: RE: The status of the approaches to the E-Tree solution?

Shahram and all,

This question already came up in our discussions - is it safe to assume that
the VLAN tags at the E-NNI will always be according to the current MEF
model? Or should we try to be as transparent as possible to user VLAN
encapsulation at the E-NNI, to accommodate future frameworks?
I believe that any approach that looks at user payload (in this case VLAN
tag) to signal VPLS information (in this case root/leaf origin) is
necessarily tied to specific assumptions on user payload encapsulation (in
this case, that S-VLAN tag is "available" to encode root/leaf). I don't
think this is a future-proof assumption, it's very likely that other network
models will come up that require S-VLAN preservation, which in the 2-VLAN
approach would necessitate adding a third VLAN-ID.

Daniel

From: Shahram Davari <[e-mail]<mailto:[e-mail]>>
To: Lizhong Jin <[e-mail]<mailto:[e-mail]>>,
"[e-mail]<mailto:[e-mail]>"
<[e-mail]<mailto:[e-mail]>>,
"[e-mail]<mailto:[e-mail]>"
<[e-mail]<mailto:[e-mail]>>
Cc: "[e-mail]<mailto:[e-mail]>"
<[e-mail]<mailto:[e-mail]>>
Subject: RE: The status of the approaches to the E-Tree solution?

Hi,

I also have a question regarding 2-VLAN. What if the customer traffic
already has an S-VLAN? Do we need a 3rd VLAN to identify the L/R?

Thx
Shahram

From: [e-mail]<mailto:[e-mail]>
[mailto:[e-mail]] On Behalf Of Lizhong Jin
Sent: Friday, April 20, 2012 9:38 AM
To: [e-mail]<mailto:[e-mail]>;
[e-mail]<mailto:[e-mail]>
Cc: [e-mail]<mailto:[e-mail]>
Subject: RE: The status of the approaches to the E-Tree solution?

Hi, all,
The difference between 2-VLAN and CW approach is who will provide the R/L
information, customer payload or PW? The customer payload will be always
modified to carry R/L information in 2-VLAN approach, while PW with CW will
carry R/L information for CW approach.
I have a question with the 2-VLAN approach in H-VPLS where H-VPLS is
accessed by VPWS as described in RFC4672 section 10.1.3. If VPWS is used to
access H-VPLS, how could the PE on VPWS side adds VLAN to indicate R/L
information?

Thanks
Lizhong

> ------------------------------
>
> Message: 2
> Date: Thu, 19 Apr 2012 04:38:36 +0000
> From: Alexander Vainshtein
<[e-mail]<mailto:[e-mail]>>
> To: "Rogers, Josh"
<[e-mail]<mailto:[e-mail]>>, Lucy yong
>        <[e-mail]<mailto:[e-mail]>>, Daniel Cohn
<[e-mail]<mailto:[e-mail]>>, Sam Cao
>        <[e-mail]<mailto:[e-mail]>>
> Cc: "[e-mail]<mailto:[e-mail]>"
<[e-mail]<mailto:[e-mail]>>
> Subject: RE: The status of the approaches to the E-Tree solution?
> Message-ID:
>
<[e-mail]<mailto:F933
[e-mail]>>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi all,
> I fully understand that that what I am going to say is not very popular,
but:
>
> IMO one of the advantages of the CW-based solution is that it is
orthogonal to usage (or non-usage) of P2MP PWs for effective delivery of BUN
traffic.
>
> Another advantage is preservation of full mesh of P2P PWs in a VPLS, and,
in a more generic way, localization of effects of changes in the PE
configuration.
>
> In particular, adding a Leaf AC to a PE that previously has been only
supporting Root ACs (or vice versa), removal of the last Leaf or last Root
AC from a PE that previously has been supporting a mix etc. affect only the
PE where this operation happens and not the rest of the PEs.
>
> As for the need for HW changes that have been mentioned as a main
disadvantage of the CW-based approach - I believe it strongly depends on
specific implementations. And some changes in the forwarding process are
required in any solution.
>
> My 2c,
>     Sasha
>
>
>
> ________________________________________
> From: [e-mail]<mailto:[e-mail]>
[[e-mail]<mailto:[e-mail]>] on behalf of Rogers,
Josh [[e-mail]<mailto:[e-mail]>]
> Sent: Wednesday, April 18, 2012 9:57 PM
> To: Lucy yong; Daniel Cohn; Sam Cao
> Cc: [e-mail]<mailto:[e-mail]>
> Subject: Re: The status of the approaches to the E-Tree solution?
>
> Again, the P2MP situation throws me.  Is this something that is used
> commonly?
>
> I'm under the impression that adding P2MP to any model results in a more
> complex model.  Wether outside s-tag is used to differentiate, or
> dedicated pw's are used for the same purpose, it seems both become more
> complex.
>
> Gile's comparison slide still concisely captures the differences between
> these methods, in my opinion.  I haven't seen any new ideas or thoughts
> brought to the group in the past week or two on the subject.  I would hate
> for both proposed methods to die on the vine because we couldn't decide
> between two methods that have nothing inherently wrong with either.
>
> -Josh
>
>
> On 4/18/12 1:53 PM, "Lucy yong"
<[e-mail]<mailto:[e-mail]>> wrote:
>
>>Send this again.
>>
>>Two PW approach can be complex too if the VPLS instance for E-Tree uses
>>P2P PW for unicast traffic and P2MP PW for broadcast and unknown
>>unicast traffic, and some P2MP PWs for multicast traffic. It may double
>>all of them.
>>
>>Lucy
>>
>>-----Original Message-----
>>From: Daniel Cohn [mailto:[e-mail]<mailto:[e-mail]>]
>>Sent: Wednesday, April 18, 2012 1:42 PM
>>To: Lucy yong; Rogers, Josh; Sam Cao
>>Cc: [e-mail]<mailto:[e-mail]>
>>Subject: RE: The status of the approaches to the E-Tree solution?
>>
>>I think the first option its the natural way to go. How is the processing
>>in this case more complex?
>>
>>Thumb typed - please be tolerant
>>
>>Lucy yong <[e-mail]<mailto:[e-mail]>> wrote:
>>
>>
>>
>>Snipped..
>>
>>Multi-PW - On ingress PE, frame is placed onto either a Leaf-only P2MP PW
>>(for traffic coming from a leaf AC), or onto a Root/Leaf P2MP PW (for
>>traffic coming from a root AC)
>>[[LY]] Not that simple. You construct either two P2MP PWs to all other
>>PEs and let egress PE performing filtering, or construct one P2MP PW to
>>leaf-only PEs and two P2MP PWs to root and leaf PEs and let ingress PE
>>perform forwarding and filtering. Both make node process complex.
>>
>>[[LY]] VPLS is built with the mechanism utilizing P2P and P2MP PW for
>>delivering the frames to remote PEs. We should utilize them with the
>>minimized changes. Dual VLAN solution is simpler than Dual PW.
>>
>>Regards,
>>Lucy
>>
>>
>>I see how 2VLAN is simpler when P2MP PW's are involved, I think.  I
>>haven't had any first hand experience with P2MP PW's, however, so don't
>>feel terribly strong about this objection.  Is this a real problem for
>>others (now or in the future), or is this objection in the weeds?
>>
>>I'm not sure the 'additional complexity' is notable, or even relevant.  I
>>encourage others to speak up if they disagree, as P2MP PW is only
>>conceptual to me, and I am unfamiliar with real-life use cases for it.
>>
>>Thanks,
>>Josh
>>
>>
>>
>>On 4/18/12 10:30 AM, "Lucy yong"
<[e-mail]<mailto:[e-mail]>> wrote:
>>
>>>Please see inline.
>>>
>>>-----Original Message-----
>>>From: Sam Cao [mailto:[e-mail]<mailto:[e-mail]>]
>>>Sent: Tuesday, April 17, 2012 7:14 AM
>>>To: 'Daniel Cohn'; Lucy yong; 'Rogers, Josh'; 'Henderickx, Wim (Wim)';
>>>[e-mail]<mailto:[e-mail]>;
[e-mail]<mailto:[e-mail]>;
>>>[e-mail]<mailto:[e-mail]>
>>>Cc: [e-mail]<mailto:[e-mail]>;
[e-mail]<mailto:[e-mail]>;
>>>[e-mail]<mailto:[e-mail]>;
[e-mail]<mailto:[e-mail]>;
>>>[e-mail]<mailto:[e-mail]>;
[e-mail]<mailto:[e-mail]>
>>>Subject: RE: The status of the approaches to the E-Tree solution?
>>>
>>>Yes, 2 pws are only needed between pes with both root and leaf acs after
>>>improving Dual-PW approach. If consider P2MP, Dual-PW approach setup 2
>>>P2MP
>>>PWs if need. There is no difference between P2MP or normal PW setup. But,
>>>can Leaf-ACs be bound to Root PE of P2MP PW?
>>>
>>>[[LY]] No, it makes complex in setting up P2MP PW. Should a PE with both
>>>root and leaf ACs set up two or one P2MP PW to other PEs (some PE have
>>>both root and leaf AC and some only have leaf ACs)?
>>>Regards,
>>>Lucy
>>>
>>>Regards,
>>>
>>>Yuqun (Sam) Cao
>>>E-mail: [e-mail]<mailto:[e-mail]>
>>>
>>>
>>>-----Original Message-----
>>>From: Daniel Cohn [mailto:[e-mail]<mailto:[e-mail]>]
>>>Sent: Tuesday, April 17, 2012 4:56 PM
>>>To: Lucy yong; Rogers, Josh; Henderickx, Wim (Wim);
>>>[e-mail]<mailto:[e-mail]>;
>>>[e-mail]<mailto:[e-mail]>;
[e-mail]<mailto:[e-mail]>;
Sam Cao
>>>Cc: [e-mail]<mailto:[e-mail]>;
[e-mail]<mailto:[e-mail]>;
>>>[e-mail]<mailto:[e-mail]>;
[e-mail]<mailto:[e-mail]>;
>>>[e-mail]<mailto:[e-mail]>;
[e-mail]<mailto:[e-mail]>
>>>Subject: RE: The status of the approaches to the E-Tree solution?
>>>
>>>Adding Sam (as l2vpn@ is holding messages)
>>>
>>>DC
>>>
>>>-----Original Message-----
>>>From: Lucy yong
[mailto:[e-mail]<mailto:[e-mail]>]
>>>Sent: Tuesday, April 17, 2012 12:39 AM
>>>To: Daniel Cohn; Rogers, Josh; Henderickx, Wim (Wim);
>>>[e-mail]<mailto:[e-mail]>;
[e-mail]<mailto:[e-mail]>;
>>>[e-mail]<mailto:[e-mail]>
>>>Cc: [e-mail]<mailto:[e-mail]>;
[e-mail]<mailto:[e-mail]>;
>>>[e-mail]<mailto:[e-mail]>;
[e-mail]<mailto:[e-mail]>;
>>>[e-mail]<mailto:[e-mail]>;
[e-mail]<mailto:[e-mail]>
>>>Subject: RE: The status of the approaches to the E-Tree solution?
>>>
>>>
>>>Snipped,
>>>
>>>As we discussed extensively in the list, and as reflected in giles
>>>slide, 2 pws are only needed between pes with both root and leaf acs,
>>>which will typically be a small minority.
>>>[[LY]] Don't know if the assumption is true. Even it is the case, both
>>>approaches can benefit from it. I was off for a while and captures some
>>>discussions now.
>>>
>>>Also as per giles slide, dual vlan can have scalability issues due to
>>>additional lookup and double use of vlans in internal emulated lan
>>>interface. Also there are potential backward compatibility issues with
>>>silicon that doesn't support vlan mapping.
>>>[[LY]] I was not in IETF83 meeting and wait on the meeting minutes. I am
>>>not clear on all the issues. Could you be more specific? As I mentioned
>>>in below, two PW approach makes VPLS transport construction and packet
>>>forwarding more complex, I can see potential backward compatibility
>>>issues with 2 PW solution.
>>>
>>>Regards,
>>>Lucy
>>>
>>>Regards,
>>>
>>>Daniel
>>>
>>>Thumb typed - please be tolerant
>>>
>>>Lucy yong <[e-mail]<mailto:[e-mail]>> wrote:
>>>
>>>In my mind, the VLAN approach means dual vlan method.
>>>
>>>The main concern for CW approach is hardware support.
>>>
>>>Two PW approach can be complex too if the VPLS instance for E-Tree uses
>>>P2P PW for unicast traffic and P2MP PW for broadcast and unknown unicast
>>>traffic, and some P2MP PWs for multicast traffic. It may double all of
>>>them.
>>>
>>>E-tree is an Ethernet service and there is already VLAN based solution
>>>in IEEE, can we just utilize it without complicating VPLS transport
>>>construction? This also makes interworking with Eth only network easier.
>>>
>>>Cheers,
>>>Lucy
>>>
>>>-----Original Message-----
>>>From: Rogers, Josh
[mailto:[e-mail]<mailto:[e-mail]>]
>>>Sent: Monday, April 16, 2012 8:35 AM
>>>To: Lucy yong; Henderickx, Wim (Wim);
'[e-mail]<mailto:[e-mail]>';
>>>'[e-mail]<mailto:[e-mail]>';
'[e-mail]<mailto:[e-mail]>'
>>>Cc: '[e-mail]<mailto:[e-mail]>';
'[e-mail]<mailto:[e-mail]>';
>>>'[e-mail]<mailto:[e-mail]>';
'[e-mail]<mailto:[e-mail]>';
>>>'[e-mail]<mailto:[e-mail]>';
'[e-mail]<mailto:[e-mail]>'
>>>Subject: RE: The status of the approaches to the E-Tree solution?
>>>
>>>I believe the initial question was in regard to the CW method.  Are you
>>>saying that you no longer are interested in that method in preference of
>>>the dual vlan method?
>>>
>>>
>>>
>>>Lucy yong <[e-mail]<mailto:[e-mail]>> wrote:
>>>
>>>
>>>Agree with Wim. VLAN approach is the best solution for E-Tree.
>>>
>>>Lucy
>>>
>>>-----Original Message-----
>>>From: [e-mail]<mailto:[e-mail]>
[mailto:[e-mail]<mailto:[e-mail]>] On Behalf
>>>Of Henderickx, Wim (Wim)
>>>Sent: Thursday, April 12, 2012 2:03 AM
>>>To: '[e-mail]<mailto:[e-mail]>';
'[e-mail]<mailto:[e-mail]>';
>>>'[e-mail]<mailto:[e-mail]
>'
>>>Cc: '[e-mail]<mailto:[e-mail]>';
'[e-mail]<mailto:[e-mail]>';
>>>'[e-mail]<mailto:[e-mail]>';
'[e-mail]<mailto:[e-mail]>';
>>>'[e-mail]<mailto:[e-mail]>';
'[e-mail]<mailto:[e-mail]>'
>>>Subject: Re: The status of the approaches to the E-Tree solution?
>>>
>>>The vlan approach is superior as it also works for eth only networks,
>>>etc. On top some vendors indicate hw issues with the cw approach. As
>>>such we have dropped more or less the cw approach.
>>>
>>>Cheers,
>>>Wim
>>>_________________
>>>sent from blackberry
>>>
>>>----- Original Message -----
>>>From: Giles Heron [mailto:[e-mail]<mailto:giles.heron@gmail.
com>]
>>>Sent: Thursday, April 12, 2012 08:22 AM
>>>To: Simon Delord <[e-mail]<mailto:[e-mail]>>;
Alexander Vainshtein
>>><[e-mail]<mailto:[e-mail]
>>
>>>Cc: [e-mail]<mailto:[e-mail]>
<[e-mail]<mailto:[e-mail]>>; Vladimir Kleiner
>>><[e-mail]<mailto:[e-mail]>>;
Andrew Sergeev
>>><[e-mail]<mailto:[e-mail]>>; Idan
Kaspit <[e-mail]<mailto:[e-mail]>>;
>>>Mishael Wexler <[e-mail]<mailto:Mishael.Wexler@ecitele.
com>>; Rotem Cohen
>>><[e-mail]<mailto:[e-mail]>>
>>>Subject: Re: The status of the approaches to the E-Tree solution?
>>>
>>>Sorry - the "anonymous presentation" was mine.  I should possibly have
>>>put in a third column on the CW approach.  And hopefully the minutes
>>>will be posted soon.
>>>
>>>We had various discussions, as Simon stated, and consensus seemed to be
>>>forming around the two alternatives of two PWEs or two VLANs.  I believe
>>>three of the authors of the CW approach are also authors of the two VLAN
>>>approach and one is also an author of the two PWE approach. So perhaps
>>>it's best to let those four individuals say which approach they prefer
>>>and why?
>>>
>>>Giles
>>>
>>>On 10/04/2012 00:45, "Simon Delord" <[e-mail]<mailto:simon.
[e-mail]>> wrote:
>>>
>>>> Hi Alexander,
>>>>
>>>> You are right, no discussion on the WG mailing list recently, but
>>>> there have been substantial discussions among the authors of various
>>>> solution drafts off the mailing list. As far as I know, no consensus
>>>> yet before ietf83, not sure the progress in the Paris WG meeting. I
>>>> think the CW approach has not been rejected by the WG yet, or the WG
>>>> has not yet decided on which one to adopt.
>>>>
>>>> Simon
>>>>
>>>> 2012/4/8 Alexander Vainshtein
<[e-mail]<mailto:[e-mail]>>
>>>>
>>>>>  Hi all,
>>>>>
>>>>> Unfortunately I have not been able to attend the Paris IETF.
>>>>>
>>>>> However, looking up the L2VPN proceedings, I've found a short
>>>>> anonymous presentation called "E-Tree Update"  (
>>>>> http://www.ietf.org/proceedings/83/slides/slides-83-l2vpn-1.pptx).
>>>>> This presentation discusses the differences of the E-Tree approaches
>>>>> based on dedicated VLANs (as in
>>>>> http://datatracker.ietf.org/doc/draft-cao-l2vpn-vpls-etree/?include_t
>>>>> ext=1) and multiple PWs between the PEs (as in
>>>>> http://datatracker.ietf.org/doc/draft-ram-l2vpn-etree-multiple-pw/?in
>>>>> clude_te
>>>>> xt=1)
>>>>> and completely ignores the solution based on usage of the CW in the
>>>>> PWs connecting the PEs (as in
>>>>> http://datatracker.ietf.org/doc/draft-key-l2vpn-vpls-etree/?include_t
>>>>> ext=1
>>>>> ).
>>>>>
>>>>>
>>>>>
>>>>> The Minutes of the Paris L2VPN session are not yet available, but I
>>>>> wonder whether the WG has taken a decision to reject the approach
>>>>> based on the CW usage? I do not remember any recent discussion of
>>>>> this topic on the WG mailing list.
>>>>>
>>>>>
>>>>>
>>>>> Regards, and lots of thanks in advance,
>>>>>
>>>>> Sasha
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> This e-mail message is intended for the recipient only and contains
>>>>> information which is CONFIDENTIAL and which may be proprietary to ECI
>>>
>>>>> Telecom. If you have received this transmission in error, please
>>>>> inform us by e-mail, phone or fax, and then delete the original and
>>>>> all copies thereof.
>>>>>
>>>
>>>
>>>
>>>
>>>
>>>This E-mail and any of its attachments may contain Time Warner Cable
>>>proprietary information, which is privileged, confidential, or subject
>>>to copyright belonging to Time Warner Cable. This E-mail is intended
>>>solely for the use of the individual or entity to which it is addressed.
>>>If you are not the intended recipient of this E-mail, you are hereby
>>>notified that any dissemination, distribution, copying, or action taken
>>>in relation to the contents of and attachments to this E-mail is
>>>strictly prohibited and may be unlawful. If you have received this
>>>E-mail in error, please notify the sender immediately and permanently
>>>delete the original and any copy of this E-mail and any printout.
>>>
>>
>>
>>This E-mail and any of its attachments may contain Time Warner Cable
>>proprietary information, which is privileged, confidential, or subject to
>>copyright belonging to Time Warner Cable. This E-mail is intended solely
>>for the use of the individual or entity to which it is addressed. If you
>>are not the intended recipient of this E-mail, you are hereby notified
>>that any dissemination, distribution, copying, or action taken in
>>relation to the contents of and attachments to this E-mail is strictly
>>prohibited and may be unlawful. If you have received this E-mail in
>>error, please notify the sender immediately and permanently delete the
>>original and any copy of this E-mail and any printout.
>
>
> This E-mail and any of its attachments may contain Time Warner Cable
proprietary information, which is privileged, confidential, or subject to
copyright belonging to Time Warner Cable. This E-mail is intended solely for
the use of the individual or entity to which it is addressed. If you are not
the intended recipient of this E-mail, you are hereby notified that any
dissemination, distribution, copying, or action taken in relation to the
contents of and attachments to this E-mail is strictly prohibited and may be
unlawful. If you have received this E-mail in error, please notify the
sender immediately and permanently delete the original and any copy of this
E-mail and any printout.
> This e-mail message is intended for the recipient only and contains
information which is CONFIDENTIAL and which may be proprietary to ECI
Telecom. If you have received this transmission in error, please inform us
by e-mail, phone or fax, and then delete the original and all copies
thereof.
>
>
>
> ------------------------------
>
> _______________________________________________
> L2vpn mailing list
> [e-mail]<mailto:[e-mail]>
> https://www.ietf.org/mailman/listinfo/l2vpn
>
>
> End of L2vpn Digest, Vol 95, Issue 25
> ***********************************

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

_______________________________________________
L2vpn mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/l2vpn


End of L2vpn Digest, Vol 95, Issue 93
*************************************