Re: [trill] draft-zhang-trill-multi-level-single-nickname - WG Adoption Call extension (7/16 to 8/16/2015)

Liyizhou <liyizhou@huawei.com> Fri, 07 August 2015 01:28 UTC

Return-Path: <liyizhou@huawei.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F6251B351D for <trill@ietfa.amsl.com>; Thu, 6 Aug 2015 18:28:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 uR36wM-Fsjvy for <trill@ietfa.amsl.com>; Thu, 6 Aug 2015 18:28:10 -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 6FEDF1B3519 for <trill@ietf.org>; Thu, 6 Aug 2015 18:28:10 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BVZ04683; Fri, 07 Aug 2015 01:28:08 +0000 (GMT)
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.235.1; Fri, 7 Aug 2015 02:28:06 +0100
Received: from NKGEML503-MBX.china.huawei.com ([169.254.5.180]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0235.001; Fri, 7 Aug 2015 09:28:01 +0800
From: Liyizhou <liyizhou@huawei.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Thread-Topic: [trill] draft-zhang-trill-multi-level-single-nickname - WG Adoption Call extension (7/16 to 8/16/2015)
Thread-Index: AdDOu0A8fk+YtNsfRi+PLCIgVt1xcQBLOtxAABI5KwAAH1iV0A==
Date: Fri, 07 Aug 2015 01:28:01 +0000
Message-ID: <D408889639FC5E4FADB4E00A3E01FA8F838D09AB@nkgeml503-mbx.china.huawei.com>
References: <023401d0cebb$533d8010$f9b88030$@ndzh.com> <D408889639FC5E4FADB4E00A3E01FA8F838CF3C4@nkgeml503-mbx.china.huawei.com> <CAF4+nEFicSvAQ099w0hGrk1=HGijuVnCrx-dEz=Gev1x6+bbEQ@mail.gmail.com>
In-Reply-To: <CAF4+nEFicSvAQ099w0hGrk1=HGijuVnCrx-dEz=Gev1x6+bbEQ@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.135.180.237]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/kIbAitRkjD25i_aHsPkPiESxQtc>
Cc: Jon Hudson <jon.hudson@gmail.com>, Susan Hares <shares@ndzh.com>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] draft-zhang-trill-multi-level-single-nickname - WG Adoption Call extension (7/16 to 8/16/2015)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Aug 2015 01:28:14 -0000

So single nickname solution is considered as a type of aggregated nickname approach, right?

I am ok with the logic of unique and aggregated nicknames. When number of nicknames is not a concern, unique nickname probably is good for us. And then grow to aggregated nickname later.

Thanks,
Yizhou

-----Original Message-----
From: Donald Eastlake [mailto:d3e3e3@gmail.com] 
Sent: Friday, August 07, 2015 2:17 AM
To: Liyizhou
Cc: Susan Hares; trill@ietf.org; Jon Hudson
Subject: Re: [trill] draft-zhang-trill-multi-level-single-nickname - WG Adoption Call extension (7/16 to 8/16/2015)

Hi,

On Wed, Aug 5, 2015 at 9:51 PM, Liyizhou <liyizhou@huawei.com> wrote:
> I have responded  in the adoption call of 
> draft-perlman-trill-rbridge-multilevel.
>
> I support the adoption of the solution for multi-level as it is a 
> necessary feature to solve the scalability issue of trill campus.
>
> I support this single nickname solution to be adopted if WG has no 
> intention to advance the other unique/aggregated nickname approaches.
>
> However if we want to make all three solutions available, are they 
> going to co-exist?

I think there are two types of solutions: unique nickname and aggregated nickname. Unique nickname is pretty straight forward and there are not that many choices in deciding how to do it. I believe it can also be done in software with existing hardware. There are more choices in aggregated nicknames which are inherently more complex but more scalable. Aggregated nickname schemes are also likely to requires some firmware/hardware changes to handle high data rates. I think we should only standardize one aggregation nickname method. But both unique and aggregated methods should be able to co-exist.

As a TRILL campus grows it is reasonable to go to multi-level using unique nicknames with a "small" number of level 1 areas, then at some point start adding aggregated level 1 areas and perhaps eventually go to all aggregated. This issue is discussed in the perlman draft.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA  d3e3e3@gmail.com

> Thanks,
>
> Yizhou
>
>
>
>
>
>
>
> From: trill [mailto:trill-bounces@ietf.org] On Behalf Of Susan Hares
> Sent: Tuesday, August 04, 2015 9:42 PM
> To: trill@ietf.org
> Cc: 'Donald Eastlake'; 'Jon Hudson'
> Subject: [trill] draft-zhang-trill-multi-level-single-nickname - WG 
> Adoption Call extension (7/16 to 8/16/2015)
>
>
>
> This email extends the 2 week WG adoption call for 
> draft-zhang-trill-multi-level-single-nickname to go from 7/16 to 8/16/2015.
>
>
>
> The draft can be accessed at:
>
> http://datatracker.ietf.org/doc/draft-zhang-trill-multilevel-single-ni
> ckname
>
>
>
> Please include in your response an evaluation of the technology and 
> places
>
> this technology might be deployed.
>
>
>
> Sue Hares and Jon Hudson
>
>
> _______________________________________________
> trill mailing list
> trill@ietf.org
> https://www.ietf.org/mailman/listinfo/trill
>