RE: AD review of draft-ietf-l2vpn-etree-frwk

"Adrian Farrel" <adrian@olddog.co.uk> Tue, 01 July 2014 16:35 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: l2vpn@ietfa.amsl.com
Delivered-To: l2vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3562B1B2867 for <l2vpn@ietfa.amsl.com>; Tue, 1 Jul 2014 09:35:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c6CdQu8xKHZ2 for <l2vpn@ietfa.amsl.com>; Tue, 1 Jul 2014 09:35:47 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28EA01A0298 for <l2vpn@ietf.org>; Tue, 1 Jul 2014 09:35:43 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s61GZbcE025174; Tue, 1 Jul 2014 17:35:37 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s61GZZnh025154 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 1 Jul 2014 17:35:36 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Lucy yong'" <lucy.yong@huawei.com>, <draft-ietf-l2vpn-etree-frwk.all@tools.ietf.org>
References: <05fe01cf9528$ff1aa340$fd4fe9c0$@olddog.co.uk> <2691CE0099834E4A9C5044EEC662BB9D453B09ED@dfweml701-chm.china.huawei.com>
In-Reply-To: <2691CE0099834E4A9C5044EEC662BB9D453B09ED@dfweml701-chm.china.huawei.com>
Subject: RE: AD review of draft-ietf-l2vpn-etree-frwk
Date: Tue, 1 Jul 2014 17:35:31 +0100
Message-ID: <06df01cf954a$7a6ebd30$6f4c3790$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQM57IkawgYIQRteiH6AbUn6+/ce9QG0Hrm4mKkWJuA=
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1017-20792.000
X-TM-AS-Result: No--10.964-10.0-31-10
X-imss-scan-details: No--10.964-10.0-31-10
X-TMASE-MatchedRID: 9zTThWtzIms4HKI/yaqRm2YNYtsE5knD8GRhP/nTHNYUl9bvAS7WQJqb MiXJH8nxRqvEAANPmZiRXfyCXqS62Tzr4TJKjukKC2KCgTQN5v6H19CYqnBg4PzaSz3Z/4aa8xO 4isLpZaHy5f20Xv+MegpggsDMbNmSW3NX3Rq13v2628cXbnOhT6OI1u80g4PZMg1H4vnDInOjxY yRBa/qJX3mXSdV7KK4QiE5bJj38wALbigRnpKlKSPzRlrdFGDwi2yPHwO4XecLBq01WcsHQKi0p sz+iKWyU99LHx3EIESvHvHgamj+qw==
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/udc2iqEo9a2k9X6877MoFdno9rE
Cc: l2vpn@ietf.org
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Layer 2 Virtual Private Networks <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn/>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jul 2014 16:35:50 -0000

Hi Lucy,

>> Section 2.2 has
>> 
>>    An E-Tree service has one or more Root ACs and many Leaf ACs.
>> 
>> I suggest that "many" is not a necessary part of the definition although it
may be
>> probable in deployments. For the definition I think you need:
>> 
>>    An E-Tree service has one or more Root ACs and at least one Leaf AC.
>
> [Lucy] Since one key of E-tree service is prohibiting the communication
between
> leaf ACs. Therefore, one leaf AC case does not make sense. How about: An E-
> Tree service has one or more Root ACs and at least two Leaf ACs.

So, if I buy an E-tree service from my service provider to support video
distribution, and I have two leaf nodes, and one leaf node goes away, you are
saying that the service I have bought suddenly becomes an E-LAN service?

But, in principle that text is fine by me.

>> Section 2.3.1 para 2
>> 
>> s/fame/frame/
>
> [Lucy] will change it. Thanks.
> 
>> Figure 1 shows two notations "E-Tree". The associated arrows do not make it
>> clear what is the extent of the E-tree since the top one and the bottom one
show
>> different edge points. Can you tidy that up?
>
> [Lucy] I'll fix it.

Thanks,
Adrian