RE: AD review of draft-ietf-l2vpn-etree-frwk
Lucy yong <lucy.yong@huawei.com> Tue, 01 July 2014 16:59 UTC
Return-Path: <lucy.yong@huawei.com>
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 EF96C1B2855
for <l2vpn@ietfa.amsl.com>; Tue, 1 Jul 2014 09:59:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level:
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651,
SPF_PASS=-0.001] 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 a1l3mVWbErqg for <l2vpn@ietfa.amsl.com>;
Tue, 1 Jul 2014 09:59:17 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17])
(using TLSv1 with cipher RC4-SHA (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 193E71A0527
for <l2vpn@ietf.org>; Tue, 1 Jul 2014 09:59:16 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com)
([172.18.7.190])
by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued)
with ESMTP id BGR52280; Tue, 01 Jul 2014 16:59:15 +0000 (GMT)
Received: from DFWEML703-CHM.china.huawei.com (10.193.5.130) by
lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server
(TLS) id 14.3.158.1; Tue, 1 Jul 2014 17:59:14 +0100
Received: from DFWEML701-CHM.china.huawei.com ([169.254.1.95]) by
dfweml703-chm.china.huawei.com ([169.254.5.198]) with mapi id 14.03.0158.001;
Tue, 1 Jul 2014 09:59:06 -0700
From: Lucy yong <lucy.yong@huawei.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>,
"draft-ietf-l2vpn-etree-frwk.all@tools.ietf.org"
<draft-ietf-l2vpn-etree-frwk.all@tools.ietf.org>
Subject: RE: AD review of draft-ietf-l2vpn-etree-frwk
Thread-Topic: AD review of draft-ietf-l2vpn-etree-frwk
Thread-Index: Ac+VKNbK7L9DFlaMQpybP0Am8ll+tQAEQ0awABLQaYAADhwVwA==
Date: Tue, 1 Jul 2014 16:59:06 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D453B0AD9@dfweml701-chm.china.huawei.com>
References: <05fe01cf9528$ff1aa340$fd4fe9c0$@olddog.co.uk>
<2691CE0099834E4A9C5044EEC662BB9D453B09ED@dfweml701-chm.china.huawei.com>
<06df01cf954a$7a6ebd30$6f4c3790$@olddog.co.uk>
In-Reply-To: <06df01cf954a$7a6ebd30$6f4c3790$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.134.13]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/LcTlcjinFuTIfBpFyRNZA1y5rWM
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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:59:19 -0000
[Lucy] Hi Adrian, >> 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? [Lucy] In an E-LAN service, all ACs have root role. If an AC has leaf role, the service is not an E-LAN service. I see this example as an E-Tree service. But, in principle that text is fine by me. [Lucy] Thanks. I'll use that text. Lucy
- AD review of draft-ietf-l2vpn-etree-frwk Adrian Farrel
- RE: AD review of draft-ietf-l2vpn-etree-frwk Lucy yong
- RE: AD review of draft-ietf-l2vpn-etree-frwk Adrian Farrel
- RE: AD review of draft-ietf-l2vpn-etree-frwk Lucy yong
- Re: AD review of draft-ietf-l2vpn-etree-frwk Bitar, Nabil N