[trill] 答复: Re: Comments on draft-dunbar-trill-directory-assisted-encap
hu.fangwei@zte.com.cn Thu, 22 August 2013 02:34 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 49E3B11E8172; Wed, 21 Aug 2013 19:34:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -94.019
X-Spam-Level:
X-Spam-Status: No, score=-94.019 tagged_above=-999 required=5 tests=[AWL=-0.469, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, SARE_SUB_ENC_GB2312=1.345, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MmFvPsIrXInx; Wed, 21 Aug 2013 19:34:03 -0700 (PDT)
Received: from zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 7E0D121F93E4; Wed, 21 Aug 2013 19:34:00 -0700 (PDT)
Received: from zte.com.cn (unknown [192.168.168.119]) by Websense Email Security Gateway with ESMTP id 599DC1287BD6; Thu, 22 Aug 2013 10:33:33 +0800 (CST)
Received: from mse02.zte.com.cn (unknown [10.30.3.21]) by Websense Email Security Gateway with ESMTPS id ED2F372EF69; Thu, 22 Aug 2013 10:33:31 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id r7M2XNoC095320; Thu, 22 Aug 2013 10:33:23 +0800 (GMT-8) (envelope-from hu.fangwei@zte.com.cn)
In-Reply-To: <CAF4+nEFxPiGh5z8=k0Xx9e-KTTyTuBVfyb3eq9yEmV1pRrpT0w@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
MIME-Version: 1.0
X-KeepSent: 5B1C8559:886EC2DE-48257BCF:000CD8DC; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF5B1C8559.886EC2DE-ON48257BCF.000CD8DC-48257BCF.000DF771@zte.com.cn>
From: hu.fangwei@zte.com.cn
Date: Thu, 22 Aug 2013 10:33:15 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2013-08-22 10:33:05, Serialize complete at 2013-08-22 10:33:05
Content-Type: multipart/alternative; boundary="=_alternative 000DF77148257BCF_="
X-MAIL: mse02.zte.com.cn r7M2XNoC095320
Cc: "trill@ietf.org" <trill@ietf.org>, "trill-bounces@ietf.org" <trill-bounces@ietf.org>, Linda Dunbar <linda.dunbar@huawei.com>
Subject: [trill] 答复: Re: Comments on draft-dunbar-trill-directory-assisted-encap
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 22 Aug 2013 02:34:07 -0000
Hi, Donald Please see my comments inline with [hfw] (1) The remote egress RBridge could not learn the {nickname, MAC} pair by the data frame. [Linda] The “nickname” is Ingress’ nickname, the MAC-SA is ingress’ too. So the egress RBridge should be able to learn the mapping between the Ingress’ nickname and its MAC. Why do you say “could not”? (dee3) Right, its asymmetric. So the end station does the ingress but the egress RBridge does the usual egress process, learning the remote MAC address as attached to the ingress nickname in the TRILL Data frame -- but it does not matter that much if the egress RBridge learns anything if you do ingress for traffic going the other way at the end station also. [hfw] This is one of the scenarios : local end station can do TRILL encapsulation, while the remote endstation only process the native frame. (2) The transit RBridges could not pass the RPF check for multi-destination forwarding. [Linda] Why? The data frame is same as if the frame is encapsulated by the Ingress RBridge. (dee3) The only place where there might be an RPF check problem is on receipt at the first edge RBridge so some care may be needed there. Alternatively, you could just not do the ingress at the end station for multi-destination frames but have them ingressed by the edge RBridge. [hfw] Is phantom nickname golabl unique or RB unique? For global unique, all the edge RBridges have the same value. In this situation, the RPF does not pass for multi-destination. For RB unique, different edge RBridges have different phantom nicknames. In this situation, it wastes many nicknames. We can assign the RB1's nickname (N1, not phantom nickname) to the non-RBridge nodes. Thanks! Fangwei Donald Eastlake <d3e3e3@gmail.com> 发件人: trill-bounces@ietf.org 2013-08-21 08:46 收件人 Linda Dunbar <linda.dunbar@huawei.com> 抄送 "trill-bounces@ietf.org" <trill-bounces@ietf.org>, "hu.fangwei@zte.com.cn" <hu.fangwei@zte.com.cn>, "trill@ietf.org" <trill@ietf.org> 主题 Re: [trill] Comments on draft-dunbar-trill-directory-assisted-encap Hi, See at (dee3). On Tue, Aug 20, 2013 at 5:31 PM, Linda Dunbar <linda.dunbar@huawei.com> wrote: Fang Wei, Answers to your comments are inserted below: From: hu.fangwei@zte.com.cn [mailto:hu.fangwei@zte.com.cn] Sent: Monday, August 19, 2013 9:57 PM To: Linda Dunbar Cc: trill@ietf.org; trill-bounces@ietf.org Subject: RE: [trill] Comments on draft-dunbar-trill-directory-assisted-encap Hi,Linda I understand that R1 would keep the encapsulation frame from E1. There would bring two issues: (1) The remote egress RBridge could not learn the {nickname, MAC} pair by the data frame. [Linda] The “nickname” is Ingress’ nickname, the MAC-SA is ingress’ too. So the egress RBridge should be able to learn the mapping between the Ingress’ nickname and its MAC. Why do you say “could not”? (dee3) Right, its asymmetric. So the end station does the ingress but the egress RBridge does the usual egress process, learning the remote MAC address as attached to the ingress nickname in the TRILL Data frame -- but it does not matter that much if the egress RBridge learns anything if you do ingress for traffic going the other way at the end station also. (2) The transit RBridges could not pass the RPF check for multi-destination forwarding. [Linda] Why? The data frame is same as if the frame is encapsulated by the Ingress RBridge. (dee3) The only place where there might be an RPF check problem is on receipt at the first edge RBridge so some care may be needed there. Alternatively, you could just not do the ingress at the end station for multi-destination frames but have them ingressed by the edge RBridge. Thanks, Donald ============================= Donald E. Eastlake 3rd +1-508-333-2270 (cell) 155 Beaver Street, Milford, MA 01757 USA d3e3e3@gmail.com Linda Linda Dunbar <linda.dunbar@huawei.com> 2013-08-20 10:41 收件人 "hu.fangwei@zte.com.cn" <hu.fangwei@zte.com.cn> 抄送 "trill@ietf.org" <trill@ietf.org>, "trill-bounces@ietf.org" < trill-bounces@ietf.org> 主题 RE: [trill] Comments on draft-dunbar-trill-directory-assisted-encap Fang Wei, Sorry for the late response due to lack of internet access during my vacation last two weeks. Answers to your questions are inserted below: From: hu.fangwei@zte.com.cn [mailto:hu.fangwei@zte.com.cn] Sent: Friday, August 09, 2013 2:59 AM To: Linda Dunbar Cc: trill@ietf.org; trill-bounces@ietf.org Subject: Re: [trill] Comments on draft-dunbar-trill-directory-assisted-encap Hi,Linda When R1 receives a frame, it will check the MAC-SA, and find that it is from E1. Will R1 re-encapsulate the ingress nickname from "phantom nickname" to N1(R1's nickname)? [Linda] R1 will not re-encapsulate the frame because the MAC-DA of the frame is R1. R1 will terminate the MAC header and look into the payload, which is a TRILL frame. R1 will put another MAC header with MAC-DA being the egress RBridge’s MAC and MAC-SA being its own MAC. In addition, how about the multi-destination forwarding , does the multi-destination forwarding support in this document? [Linda] For multi destination frames, the destination Nickname should be a root of multicast tree. Linda Best Regards. Linda Dunbar <linda.dunbar@huawei.com> 发件人: trill-bounces@ietf.org 2013-08-03 14:39 收件人 "hu.fangwei@zte.com.cn" <hu.fangwei@zte.com.cn>, "trill@ietf.org" < trill@ietf.org> 抄送 主题 Re: [trill] Comments on draft-dunbar-trill-directory-assisted-encap Fang Wei, Sorry for the delayed response. Answers to your comments are inserted below: From: trill-bounces@ietf.org [mailto:trill-bounces@ietf.org] On Behalf Of hu.fangwei@zte.com.cn Sent: Wednesday, July 31, 2013 10:49 AM To: trill@ietf.org Subject: [trill] Comments on draft-dunbar-trill-directory-assisted-encap Hi, Linda I have several comments: (1) We say that E1 is the "Non-RBridge Nodes", R1 is the local edge RBridge. E1 will encapsulate the TRILL encapsuation with the ingress nickname as "Phantom nickname", and egress nickname as the nickname of R1(we say it N1). The encapuslation frame will be forwarded to R1. My question is that, how R1 know that the trill encapuslation frame is sent by E1(Non-RBridge node)? [Linda] There is an Ethernet header in front of the RBridge header. R1 knows that the frame from is from E1 from the MAC-SA. (2) The concept of 'TRILL Encapsulating node'' or ''Simplified RBridge' is defined in section 3. But it never used in the document. Is it the same meaning with non-RBridge nodes? [Linda] We call a non-RBridge nodes that can encapsulate TRILL header as “TRILL Encapsulating node”, or “Directory reliant smart end node”. We can finalize the term when going through the WG adoption. Linda Fangwei Regards_______________________________________________ trill mailing list trill@ietf.org https://www.ietf.org/mailman/listinfo/trill _______________________________________________ trill mailing list trill@ietf.org https://www.ietf.org/mailman/listinfo/trill _______________________________________________ trill mailing list trill@ietf.org https://www.ietf.org/mailman/listinfo/trill
- [trill] Comments on draft-dunbar-trill-directory-… hu.fangwei
- [trill] Comments on draft-dunbar-trill-directory-… hu.fangwei
- Re: [trill] Comments on draft-dunbar-trill-direct… Linda Dunbar
- Re: [trill] Comments on draft-dunbar-trill-direct… hu.fangwei
- Re: [trill] Comments on draft-dunbar-trill-direct… Linda Dunbar
- Re: [trill] Comments on draft-dunbar-trill-direct… hu.fangwei
- Re: [trill] Comments on draft-dunbar-trill-direct… Linda Dunbar
- Re: [trill] Comments on draft-dunbar-trill-direct… Donald Eastlake
- Re: [trill] Comments on draft-dunbar-trill-direct… hu.fangwei
- Re: [trill] Comments on draft-dunbar-trill-direct… Linda Dunbar
- [trill] 答复: Re: Comments on draft-dunbar-trill-di… hu.fangwei
- [trill] 答复: Re: Comments on draft-dunbar-trill-di… hu.fangwei
- Re: [trill] 答复: Re: Comments on draft-dunbar-tril… Donald Eastlake
- Re: [trill] Comments on draft-dunbar-trill-direct… hu.fangwei