[trill] 答复: RE: WG LC for draft-ietf-trill-smart-end-nodes (8/26 to 9/9)- extending WG LC (10/4 to 10/18)//FWD: I-D Action: draft-ietf-trill-smart-endnodes-05.txt
hu.fangwei@zte.com.cn Tue, 07 February 2017 01:40 UTC
Return-Path: <hu.fangwei@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 21155129576 for <trill@ietfa.amsl.com>; Mon, 6 Feb 2017 17:40:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 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, 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 DnLzRleuu7KA for <trill@ietfa.amsl.com>; Mon, 6 Feb 2017 17:40:36 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id B85A5126FDC for <trill@ietf.org>; Mon, 6 Feb 2017 17:40:35 -0800 (PST)
X-MAILFROM: <hu.fangwei@zte.com.cn>
X-RCPTTO: <trill@ietf.org>
X-FROMIP: 10.30.3.20
X-SEG-Scaned: 1
X-Received: unknown,10.30.3.20,20170207093200
Received: from unknown (HELO mse01.zte.com.cn) (10.30.3.20) by localhost with (AES256-SHA encrypted) SMTP; 7 Feb 2017 01:32:00 -0000
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id v171e0Zn012207; Tue, 7 Feb 2017 09:40:00 +0800 (GMT-8) (envelope-from hu.fangwei@zte.com.cn)
In-Reply-To: <002c01d280e0$16e016e0$44a044a0$@ndzh.com>
References: <OF5D9CECCE.E7141C00-ON482580C0.00040A9B-482580C0.0004DBA5@zte.com.cn> <002c01d280e0$16e016e0$44a044a0$@ndzh.com>
To: Susan Hares <shares@ndzh.com>
MIME-Version: 1.0
X-KeepSent: 93600764:E5A9C89F-482580C0:0008F849; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.3 September 15, 2011
Message-ID: <OF93600764.E5A9C89F-ON482580C0.0008F849-482580C0.00092837@zte.com.cn>
From: hu.fangwei@zte.com.cn
Date: Tue, 07 Feb 2017 09:39:50 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP6|November 21, 2013) at 2017-02-07 09:39:45, Serialize complete at 2017-02-07 09:39:45
Content-Type: multipart/alternative; boundary="=_alternative 00092835482580C0_="
X-MAIL: mse01.zte.com.cn v171e0Zn012207
X-HQIP: 127.0.0.1
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/AnwnlqoUt4FPsalaKd0GLY-sAj4>
Cc: 'Donald Eastlake' <d3e3e3@gmail.com>, trill@ietf.org, 'Jon Hudson' <jon.hudson@gmail.com>
Subject: [trill] 答复: RE: WG LC for draft-ietf-trill-smart-end-nodes (8/26 to 9/9)- extending WG LC (10/4 to 10/18)//FWD: I-D Action: draft-ietf-trill-smart-endnodes-05.txt
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: Tue, 07 Feb 2017 01:40:40 -0000
Sue, Thanks. Regards. Fangwei. "Susan Hares" <shares@ndzh.com> 2017/02/07 09:18 收件人 <hu.fangwei@zte.com.cn>, <trill@ietf.org>, "'Donald Eastlake'" <d3e3e3@gmail.com>, 抄送 "'Jon Hudson'" <jon.hudson@gmail.com> 主题 RE: [trill] WG LC for draft-ietf-trill-smart-end-nodes (8/26 to 9/9)- extending WG LC (10/4 to 10/18)//FWD: [trill] I-D Action: draft-ietf-trill-smart-endnodes-05.txt Fangwei: Thank you for uploading the new draft today. I will review the draft as the shepherd and send you comments. Sue Hares From: hu.fangwei@zte.com.cn [mailto:hu.fangwei@zte.com.cn] Sent: Monday, February 6, 2017 7:53 PM To: Susan Hares; trill@ietf.org; Donald Eastlake Cc: Jon Hudson Subject: Re: [trill] WG LC for draft-ietf-trill-smart-end-nodes (8/26 to 9/9)- extending WG LC (10/4 to 10/18)//FWD: [trill] I-D Action: draft-ietf-trill-smart-endnodes-05.txt Hi,all A new draft is updated based on the discussion with Donald to solve his comments. Please check the link for the new drafts: https://datatracker.ietf.org/doc/draft-ietf-trill-smart-endnodes/ Regards. Fangwei. >Hi, >See below answers to questions and a review of this draft. >Thanks, >Donald =============================== Donald E. Eastlake 3rd +1-508-333-2270 (cell) 155 Beaver Street, Milford, MA 01757 USA d3e3e3@gmail.com >On Tue, Oct 4, 2016 at 12:10 PM, Susan Hares <shares@ndzh.com> wrote: > This begins a 2 week extension to the WG LC for > draft-ietf-trill-smart-end-nodes (10/4 to 10/18). We started the call > during August Holidays so the WG may missed this in the email list. The > authors are asked to indicate whether they know of the IPR relating to this > draft. I do not know of any IPR in this draft that has not already been declared. (Note there are two IPR declarations to the IETF by myself. The first is related to a patent application while the second states authoritatively that that patent application has been abandoned.) > WG participants are asked to consider: > > 1) Does this draft ready for publication? I do not think this document is ready for publication. See review below. > 2) Does the extension of the Rbridge to smart-end nodes solve the > problem of learning freshness and provide offload for the > encapsulation/decapsulation problem? Yes, if all the problems in the draft can be cleaned up, it describes a general approach that can solve these problems. > 3) Do you know of any planned implementations or deployments? > Sue Hares and Jon Hudson Comments on draft-ietf-trill-smart-endnodes-04: On Smart-Hellos It turns out that you also need something like Smart-Hellos and a concept of ajdacency in order to support end station access to Pull Directories as well as end station hosting of Pull Directories. So draft-ietf-trill-directory-assist-mechanisms-08 specifies "TRILL ES-IS" which has Hellos and adjacency determination. A problem with Hellos is their limited capacity and that they cannot generally be fragmented. Sending the MAC addresses a Smart Endnode is handling inside Smart Hellos, as the smart-endndoes draft currently specifies, is probably fine for most servers but if there were some kind of specialized gateway or the like that was acting as a Smart Endnode, the MAC addresses (and Data Labels they are in) might not fit into one Hello PDU. TRILL ES-IS also supports local E-L1CS LSPs which provide fragmentation and plenty of room. So perhaps it should be supported to put MAC reachability information in both TRILL ES-IS Hellos and TRILL ES-IS E-L1CS LSPs. [hfw] On using ESADI This draft says that ESADI can be used by Smart Endnodes. But it is not clear how ESADI works to an end station. As ESADI is currently specified, ESADI LSPs would not even be sent onto a link with end stations unless there was more than one edge RBridge on the link with the Smart End Stations and the ESADI distribution tree happens to include that link. Even if ESADI LSPs are being sent on the link, it seems that all the end station could do currently is snoop on the LSPs, which would not be a reliable distribution mechanism because it is not clear how the end station would request ESADI for a particular Data Label or how it would request retransmission of LSPs it missed -- maybe it could originate ESADI PSNPs in that case... But how does the Smart Endstation originate ESADI LSPs? If it uses the nickname the edge RBridge gives it, how does it know that LSP fragments it originates won't colide with those originated by the edge RBridge? If we can figure out how to support ESADI, that should probably go into draft-trill-ietf-directory-assist-mechanisms draft... Since ESADI is the basis of Push Directories, I suggest that this draft be changed to assume that, for directory like stuff, only Pull Directory information is available, not ESDAI or Push Directories. (How an end station can access Pull Directory information is described in draft-ietf-trill-directory-assist-mechanims.) Some other points The draft does not seem to cover the case of an edge RBridge port that supports Smart Endnodes with a link having both Smart and non-Smart end nodes where the edge RBridge port receives a native multi-destination frame from a non-Smart Endnode. In particular, as well as the usual encapsulation, it would seem that the edge RBridge always needs to send the encapsulated multi-destination frame out that same port so it will be seen by Smart Endnodes since the draft says that the Smart Endnodes will ignore the native multi-destination frame. But what about the case where there are two edge RBridges with ports on the link and the link is part of the distribution tree? The draft says that if a Smart Endnode originates a multi-destination frame, it encpsulates it to a ditribution tree and unicasts it to an edge RBridge that sends it on the distribution tree. But if that tree includes the link, then it will get sent out the port and the Smart Endnode that originated the encapuslated multi-destinaiton frame will see it -- this violates a fundamental principal of Ethernet that when you send a frame, you don't see it echoed back to you. Maybe the Smart Endnode can look as the inner and/or outer source MAC address on some of these things to decide what to listen to and what to do... But, in any case, I do not think all the cases are covered in this draft and things don't really work for mised Smart/non-Smart links in the current draft. Section 6 doesn't really read like part of a standards document. It talks about one possibility and then another. It suggests that under one option multiple edge RBridges on a link that support Smart Endnodes could cooperate to provide a psuedo-nickname to Smart Endnodes on that link to use in encapsulating. But how this would all work, including if the link partitions or rejoints, does not seem to be specified either directly in this draft or indirectly by reference to another document. As a standards track document, this draft need to clearly specify a way to do things. There can be options but all alternatives in the main flow of the document need to be specified. If there are actually options so interesting that they have to be mentioned but that are not specified, they should be relegated to an appendix or something and their descrition should explicitly say that the otion is just besing sketched out and not specified. It is good that a Smart End Node can support Fine Granied Labels (FGL) but the draft should probably say that when and how a Smart End Node decides to use an FGL to encapsulate is beyond the scope of the document. Or say there is configurable mapping from VLANs to FGLs. Or at least say something more. ----- 转发人 胡方伟175772/user/zte_ltd 时间 2017/02/07 08:44 ----- internet-drafts@ietf.org 发件人: "trill" <trill-bounces@ietf.org> 2017/02/07 08:40 收件人 <i-d-announce@ietf.org>, 抄送 trill@ietf.org 主题 [trill] I-D Action: draft-ietf-trill-smart-endnodes-05.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Transparent Interconnection of Lots of Links of the IETF. Title : TRILL Smart Endnodes Authors : Radia Perlman Fangwei Hu Huawei technology Kesava Vijaya Krupakaran Ting Liao Filename : draft-ietf-trill-smart-endnodes-05.txt Pages : 15 Date : 2017-02-06 Abstract: This draft addresses 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. Such an endnode is known as a "Smart Endnode". Only the attached edge RBridge can distinguish a "Smart Endnode" from a "normal endnode". The smart endnode uses the nickname of the attached edge RBridge, so this solution does not consume extra nicknames. The solution also enables Fine Grained Label aware endnodes. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-trill-smart-endnodes/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-trill-smart-endnodes-05 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-trill-smart-endnodes-05 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ trill mailing list trill@ietf.org https://www.ietf.org/mailman/listinfo/trill