Subject: Re: [trill] draft-zhang-trill-multilevel-unique-nickname-00 - WG adoption (4/11 to 4/25)

From: "honjun.zhai" <[email-masked]>
Date: Fri, 15 Apr 2016 20:28:24 +0800

As a co-author, I support the WG adoption for this draft.

Thanks,
Hongjun Zhai

来自我的华为手机

-------- 原始邮件 --------
主题：Re: [trill] draft-zhang-trill-multilevel-unique-nickname-00 - WG adoption (4/11 to 4/25)
发件人：Linda Dunbar
收件人：Susan Hares ,[email-masked]
抄送：'Donald Eastlake' ,'Jon Hudson'

I have read the document and support the WG adoption.

Linda

From: trill [mailto:[email-masked]]
On Behalf Of Susan Hares

Sent: Monday, April 11, 2016 1:57 PM

To: [email-masked]

Cc: 'Donald Eastlake'; 'Jon Hudson'

Subject: [trill] draft-zhang-trill-multilevel-unique-nickname-00 - WG adoption (4/11 to 4/25)

This begins a 2 week Working Group adoption call for: draft-zhang-trill-multi-level-unique-nickname.

https://datatracker.ietf.org/doc/draft-zhang-trill-multilevel-unique-nickname/

TRILL routing can be extended to support multiple levels by building

on the multilevel feature of IS-IS routing. Depending on how

nicknames are managed, there are two primary alternatives to realize

TRILL multilevel: the unique nickname approach and the aggregated

Nickname.  This document specifies the unique nickname approach.

In your comments please indicate:

1)
Do you think the nickname approach is useful in deployments of TRILL,

2)
Do you feel this draft provides a good solution for the unique nickname approach.

Sue Hares and Jon Hudson