Re: [trill] draft-perlman-trill-rbridge-multilevel-10: Extension of WG Adoption call (7/16 to 8/16)

Mingui Zhang <zhangmingui@huawei.com> Fri, 07 August 2015 06:46 UTC

Return-Path: <zhangmingui@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 D8B6C1B374A for <trill@ietfa.amsl.com>; Thu, 6 Aug 2015 23:46:44 -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 hJyTs4lBJIq1 for <trill@ietfa.amsl.com>; Thu, 6 Aug 2015 23:46:42 -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 C78961B3744 for <trill@ietf.org>; Thu, 6 Aug 2015 23:46:41 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BVZ23482; Fri, 07 Aug 2015 06:46:39 +0000 (GMT)
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.235.1; Fri, 7 Aug 2015 07:46:37 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.33]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0235.001; Fri, 7 Aug 2015 14:46:26 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: Donald Eastlake <d3e3e3@gmail.com>, Liyizhou <liyizhou@huawei.com>
Thread-Topic: [trill] draft-perlman-trill-rbridge-multilevel-10: Extension of WG Adoption call (7/16 to 8/16)
Thread-Index: AdDOumCjEfzgUzLdQRaZ+EX5fr8W0ABKoWIQABL5tIAAKrp5QA==
Date: Fri, 07 Aug 2015 06:46:25 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E787174845@nkgeml512-mbx.china.huawei.com>
References: <022701d0ceba$7d31a9b0$7794fd10$@ndzh.com> <D408889639FC5E4FADB4E00A3E01FA8F838CF3A1@nkgeml503-mbx.china.huawei.com> <CAF4+nEFw2z+S-GgU8p=biRZikjB8u_xAXecRMXsPx=S6uX5HmA@mail.gmail.com>
In-Reply-To: <CAF4+nEFw2z+S-GgU8p=biRZikjB8u_xAXecRMXsPx=S6uX5HmA@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.146.93]
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/aVAuEuAeSXRyR_HxS_CttMttpq8>
Cc: "trill@ietf.org" <trill@ietf.org>, Susan Hares <shares@ndzh.com>, Jon Hudson <jon.hudson@gmail.com>
Subject: Re: [trill] draft-perlman-trill-rbridge-multilevel-10: Extension of WG Adoption call (7/16 to 8/16)
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 06:46:45 -0000

Hi Donald,

> I think that the most desirable outcome would be for the
> perlman-trill-rbridge-multilevel draft to become an Information RFC.
> There should then also be one TRILL multilevel standards track RFC that
> explains how to do multilevel TRILL with unique nicknames (which is basically
> the simplest option) and how to do multilevel TRILL with some form of
> aggregated nicknames (more complex but more scalable), including a mixed
> campus in which some areas use unique and some areas use aggregated
> nicknames.

Fair enough. This is a reasonable way to go. First, we need detail the unique nickname solution. Second, we can specify how to conduct the coexistence issue. They ought to be standards track.

Thanks,
Mingui

> -----Original Message-----
> From: trill [mailto:trill-bounces@ietf.org] On Behalf Of Donald Eastlake
> Sent: Friday, August 07, 2015 2:15 AM
> To: Liyizhou
> Cc: Jon Hudson; Susan Hares; trill@ietf.org
> Subject: Re: [trill] draft-perlman-trill-rbridge-multilevel-10: Extension of WG
> Adoption call (7/16 to 8/16)
> 
> Hi Yizhou,
> 
> On Wed, Aug 5, 2015 at 9:35 PM, Liyizhou <liyizhou@huawei.com> wrote:
> > I support the adoption of the multi-level drafts.
> >
> > Multi-level is a useful feature to solve scalability issue in trill campus.
> >
> > This draft gives great details in introducing the issues caused by
> > multi-level and comparing the pros and cons in Unique and Aggregated
> > nickname approaches.
> >
> > I simply want to clarify that the intention of the draft is
> > informational, right? I do not see the exact TLV format to be used
> > either in unique or in aggregated nickname approaches. The references
> > listed two expired drafts [DraftUnique] and [DraftUnique].
> 
> Yes, this draft is intended to become an Informational RFC. It surveys different
> approaches and references some drafts as examples of those approaches. ( I
> think the two drafts you wanted to mentions were [DraftUnique] and
> [DraftAggregated]. )
> 
> > Are we going to make them both standards? If that is the case,
> > together with another single nickname approach, I would like to see
> > the text to describe the co-existence of them.
> 
> Assuming this draft and the other multi-level draft in call for adoption,
> draft-zhang-trill-multilevel-single-nickname are adopted, we will have to see
> what the WG wants to do.
> 
> I think that the most desirable outcome would be for the
> perlman-trill-rbridge-multilevel draft to become an Information RFC.
> There should then also be one TRILL multilevel standards track RFC that
> explains how to do multilevel TRILL with unique nicknames (which is basically
> the simplest option) and how to do multilevel TRILL with some form of
> aggregated nicknames (more complex but more scalable), including a mixed
> campus in which some areas use unique and some areas use aggregated
> nicknames.
> 
> 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:36 PM
> > To: trill@ietf.org
> > Cc: 'Donald Eastlake'; 'Jon Hudson'
> > Subject: [trill] draft-perlman-trill-rbridge-multilevel-10: Extension
> > of WG Adoption call (7/16 to 8/16)
> >
> >
> >
> > This extends the  WG adoption call for
> > draft-perlman-trill-rbridge-multi-level-10 from 7/16 to 8/16.  You can
> > find the draft at:
> >
> >
> >
> > http://datatracker.ietf.org/doc/draft-perlman-trill-rbridge-multilevel
> > /
> >
> >
> >
> > In your response to the WG adoption call, please comment on the
> > technology
> >
> > and places this technology might be deployed.
> >
> >
> >
> > Sue Hares and Jon Hudson
> >
> >
> >
> > PS – the first email on this subject is at:
> >
> > https://mailarchive.ietf.org/arch/msg/trill/BamyFV6L7Yky4LiTBd1OHjoKVZ
> > Y
> >
> >
> 
> _______________________________________________
> trill mailing list
> trill@ietf.org
> https://www.ietf.org/mailman/listinfo/trill