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

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