Re: Comment on draft-ietf-l2vpn-etree-reqt-02

["Ali Sajassi (sajassi)" <[e-mail]>]

Raymond,

Thanks for updating the draft. May I suggest the following minor changes:

Abstract:
From:  "This document provides functional requirements for Metro Ethernet Forum (MEF) Ethernet Tree (E-Tree) support in L2VPN."
To:  "This document provides functional requirements for Metro Ethernet Forum (MEF) Ethernet Tree (E-Tree) support in multipoint L2VPN solutions (referred to as simply L2VPN)."

Introduction, 1st para: same change as in Abstract

The reason for adding the keyword "multipoint" is to differentiate VPLS and E-VPN solutions from VPWS solution. All three of them are L2VPN solutions but E-TREE requirements applies to the former two.

Cheers,
Ali

From: Raymond Key <[e-mail]<mailto:[e-mail]>>
Date: Tuesday, October 9, 2012 5:56 AM
To: "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>, "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
Subject: RE: Comment on draft-ietf-l2vpn-etree-reqt-02

Thanks Lucy.
As this draft is not intended to define E-VPN, I simply use the wording in the working group charter to describe E-VPN in section 2.2. Hope this serve the purpose.
Raymond

________________________________
From: [e-mail]<mailto:[e-mail]>
To: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: Comment on draft-ietf-l2vpn-etree-reqt-02
Date: Mon, 8 Oct 2012 21:57:52 +0000


Raymond,



IMO:  E-VPN provides a l2 VPN service, but it does not only emulate an Ethernet LAN or VLAN across a PSN. E-VPN can provide some features that LAN or VLAN can not achieve today. For example, the ability to construct different topologies in one E-VPN instance.



Having said that, EVPN is very similarity to L3 VPN, but is at L2 basis.



Lucy



From: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]] On Behalf Of Raymond Key
Sent: Saturday, October 06, 2012 9:16 PM
To: [e-mail]<mailto:[e-mail]>
Subject: draft-ietf-l2vpn-etree-reqt-02



Hi L2VPN working group,

I have updated the captioned draft.  The document is now referring to L2VPN rather than specific to VPLS, so that it can be used as guideline for both VPLS and E-VPN. Please review and feedback on the mailing list.

Thanks,
Raymond Key


> From: [e-mail]<mailto:[e-mail]>
> To: [e-mail]<mailto:[e-mail]>
> Subject: I-D Action: draft-ietf-l2vpn-etree-reqt-02.txt
> Date: Sat, 6 Oct 2012 18:29:51 -0700
> CC: [e-mail]<mailto:[e-mail]>
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Layer 2 Virtual Private Networks Working Group of the IETF.
>
> Title : Requirements for MEF E-Tree Support in L2VPN
> Author(s) : Simon Delord
> Frederic Jounay
> Lu Huang
> Zhihua Liu
> Manuel Paul
> Ruediger Kunze
> Nick Del Regno
> Josh Rogers
> Filename : draft-ietf-l2vpn-etree-reqt-02.txt
> Pages : 14
> Date : 2012-10-06
>
> Abstract:
> This document provides functional requirements for Metro Ethernet
> Forum (MEF) Ethernet Tree (E-Tree) support in L2VPN. It is intended
> that potential solutions will use these requirements as guidelines.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-l2vpn-etree-reqt
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-l2vpn-etree-reqt-02
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-l2vpn-etree-reqt-02
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>