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)? If yes, it is deviated with RFC 6325(the 
specification in section 3.7.2 in RFC6325 is "Once the ingress nickname 
field is set, it MUST NOT be changed by any  subsequent transit 
RBridge."). R1 should not change the ingress nickname field because it is 
not a egress/ingress RBridge for that trill encapsulation frame. R1 is the 
transit RBridge for that frame; If not, the remote RB could not learn the 
nickname of R1. So I think the non-RBridge use the phantom nickname (or 
other special nickname) is not a good idea.

In addition, how about the multi-destination forwarding , does the 
multi-destination forwarding support in this document?

 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>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