Re: [trill] WG LC for draft-ietf-trill-smart-endnodes (5/31 to 6/13)
<chen.ran@zte.com.cn> Wed, 21 June 2017 09:26 UTC
Return-Path: <chen.ran@zte.com.cn>
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 B2DBC131C7F for <trill@ietfa.amsl.com>; Wed, 21 Jun 2017 02:26:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 DmGxEkxAx0Pg for <trill@ietfa.amsl.com>; Wed, 21 Jun 2017 02:26:54 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 17737131C56 for <trill@ietf.org>; Wed, 21 Jun 2017 02:26:52 -0700 (PDT)
X-scanvirus: By SEG_CYREN AntiVirus Engine
X-scanresult: CLEAN
X-MAILFROM: <chen.ran@zte.com.cn>
X-RCPTTO: <trill-chairs@ietf.org>
X-FROMIP: 10.30.3.20
X-SEG-Scaned: 1
X-Received: unknown,10.30.3.20,20170621171941
Received: from unknown (HELO mse01.zte.com.cn) (10.30.3.20) by localhost with (AES256-SHA encrypted) SMTP; 21 Jun 2017 09:19:41 -0000
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id v5L9QdGf040849; Wed, 21 Jun 2017 17:26:39 +0800 (GMT-8) (envelope-from chen.ran@zte.com.cn)
Received: from njxapp01.zte.com.cn ([10.41.132.200]) by njhub02.zte.com.cn (IBM Domino Release 9.0.1FP5) with SMTP id 2017062117263562-3006208 ; Wed, 21 Jun 2017 17:26:35 +0800
Received: from mapi (njxapp03[null]) by mapi (Zmail) with MAPI id mid203; Wed, 21 Jun 2017 17:26:40 +0800 (CST)
Date: Wed, 21 Jun 2017 17:26:40 +0800
X-Zmail-TransId: 2afb594a3bd00ba-d640d
X-Mailer: Zmail v1.0
Message-ID: <201706211726403746151@zte.com.cn>
Mime-Version: 1.0
From: chen.ran@zte.com.cn
To: trill@ietf.org, trill-chairs@ietf.org
X-MIMETrack: Itemize by SMTP Server on NJHUB02/server/zte_ltd(Release 9.0.1FP5|November 22, 2015) at 2017/06/21 17:26:35, Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP6|November 21, 2013) at 2017-06-21 17:26:31, Serialize complete at 2017-06-21 17:26:31
X-TNEFEvaluated: 1
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse01.zte.com.cn v5L9QdGf040849
X-HQIP: 127.0.0.1
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/sjrUnnrlQ-sgjT5ELM0TvTeWjoc>
Subject: Re: [trill] WG LC for draft-ietf-trill-smart-endnodes (5/31 to 6/13)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 21 Jun 2017 09:27:00 -0000
Yes/support. Regards, Ran －－－－－－－－－－－－－－－－－－－－－－－－－－－－－ 原始邮件发件人： <shares@ndzh.com>收件人：<trill@ietf.org>抄送人：<trill-chairs@ietf.org> <draft-ietf-trill-smart-endnodes@ietf.org>日 期 ：2017年05月31日 22:15主 题 ：[trill] WG LC for draft-ietf-trill-smart-endnodes (5/31 to 6/13) This begins a 2 week WG LC for draft-ietf-trill-smart-endnodes, and you can see the draft at: https://datatracker.ietf.org/doc/draft-ietf-trill-smart-endnodes/ Due to my errors, this WG LC has been delayed. We will be running this WG LC in parallel with the IPR call. The authors (Radia, Fangwei, Donald, Kesava, Ting) should send their IPR statements by 6/5. If the IPR statements are not received, we will need to extend the WG LC. For this WG, please consider the following questions: 1) Does the draft-ietf-trill-smart-endnodes provide a good solution for the problem of the size and freshness of the endnode learning table in edge RBridges by allowing endnodes to volunteer for endnode learning and encapsulation/decapsulation? 2) Do you know of any situations where deployment of this technology will be helpful? 3) Is this technology and this draft ready for IESG publication? Sue Hares