IETF Logo Mail Archive

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

"liudx@gsta.com" <liudx@gsta.com> Mon, 18 April 2016 07:56 UTC

Return-Path: <liudx@gsta.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6322512DF79 for <trill@ietfa.amsl.com>; Mon, 18 Apr 2016 00:56:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham autolearn_force=no
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 LA1fX-4XBDlc for <trill@ietfa.amsl.com>; Mon, 18 Apr 2016 00:56:05 -0700 (PDT)
Received: from 189corp.21cn.com (forptr.bnet.cn [183.61.185.78]) by ietfa.amsl.com (Postfix) with ESMTP id 41C0B12DF6C for <trill@ietf.org>; Mon, 18 Apr 2016 00:56:03 -0700 (PDT)
HMM_SOURCE_IP: 10.64.15.13:45092.291076825
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-103.59.216.83 (unknown [10.64.15.13]) by 189corp.21cn.com (HERMES) with ESMTP id 79324480093; Mon, 18 Apr 2016 15:55:22 +0800 (CST)
Received: from Lenovo-K-PC ([103.59.216.83]) by zment-as3(MEDUSA 0.0.0.0) with ESMTP id 00b4db9c-9d52-48e4-ad5b-e2f87f785eb2 for linda.dunbar@huawei.com; Mon Apr 18 15:55:23 2016
0/X-Total-Score: 0:
X-FILTER-SCORE: to=<8d8a8f85824f85968f8382936189968298868a4f84908e>, score=<1460966123CbCCAC9bA1L/ON3CCCCC9CcPPcPbccdrrsstPPPPPbPP>
X-REAL-FROM: liudx@gsta.com
X-Receive-IP: 103.59.216.83
Date: Mon, 18 Apr 2016 15:55:23 +0800
From: "liudx@gsta.com" <liudx@gsta.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, Susan Hares <shares@ndzh.com>, "trill@ietf.org" <trill@ietf.org>
References: <041e01d19423$ef8df840$cea9e8c0$@ndzh.com>, <4A95BA014132FF49AE685FAB4B9F17F657E6EC15@dfweml501-mbb>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 7, 164[cn]
Mime-Version: 1.0
Message-ID: <201604181554489973773@gsta.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart230654572622_=----"
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/FXk4sR7BEEWOXmorp4ReBgCHaEg>
Cc: 'Donald Eastlake' <d3e3e3@gmail.com>, 'Jon Hudson' <jon.hudson@gmail.com>
Subject: Re: [trill] draft-zhang-trill-multilevel-unique-nickname-00 - WG adoption (4/11 to 4/25)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 18 Apr 2016 07:56:12 -0000

I support for adoption. 

This approach is useful in deployment since it promises a scalable TRILL.
 
As an operator, I think multilevel also benefits the scalability of security schemes. This might be a direction that deserves our exploration.
 
Thanks,
Dongxin
China Telecom
 
From: Linda Dunbar
Date: 2016-04-15 04:47
To: Susan Hares; trill@ietf.org
CC: 'Donald Eastlake'; 'Jon Hudson'
Subject: Re: [trill] draft-zhang-trill-multilevel-unique-nickname-00 - WG adoption (4/11 to 4/25)
I have read the document and support the WG adoption. 
 
Linda
 
From: trill [mailto:trill-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Monday, April 11, 2016 1:57 PM
To: trill@ietf.org
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

v2.23.0 | Report a Bug | By Email