Re: [trill] [rbridge] draft-hu-trill-rbridge-esadi-04

[[e-mail]]

See in-line, pls.



Thanks,
Zhai Hongjun
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
 Protocol Development Dept.VI, Central R&D Institute, ZTE Corporation
 No. 68, Zijinghua Road, Yuhuatai District, Nanjing, P.R.China, 210012
 
 Zhai Hongjun
 
 Tel: [phone]
 Email: [e-mail]
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""





somnath chatterjee <[e-mail]> 
发件人:  [e-mail]
2012-04-23 16:40

收件人
[e-mail]
抄送
[e-mail], [e-mail]
主题
Re: [trill] [rbridge] draft-hu-trill-rbridge-esadi-04






 > Hi ,

> In introduction of draft-hu-trill-rbridge-esadi-04
> "  An RBridge that is announcing connectivity to VLAN-x (normally a
>    VLAN-x appointed forwarder) MAY use the (ESADI) protocol to announce
>    the end station address of some or all of its attached VLAN-x end
>   nodes to other RBridges that are running ESADI for VLAN-x."

> An ESADI supported RBridge MAY selectively send about end-station MACs
> and MAY opt to not send all the end-station MACs.

> I am only suggesting to send MAC in updated ESADI-LSP with confidence
> zero(for every lost MAC), so that other ESADI RBridges could easily
> recognize that this MAC needs to be deleted, rather than compare it
> with previously stored information and then delete.

Thanks for your good suggestion. I think it is feasible.


Thank you,
Regards,
Somnath

2012/4/23 <[e-mail]>
>
>
> Hi, chatterjee
>
> By my understanding, If RB1 supports ESADI, it advertises all the 
end-station MAC attached to the remote RBridges.
>
> The remote RBridge can do some policy forwarding based on the MAC 
address, but I think it is no need to opt to send the end-station MAC by 
the local RBridge.
>
> Regards
>
>
> somnath chatterjee <[e-mail]>
>
> 2012-04-23 14:57
>
> 收件人
> [e-mail]
> 抄送
> [e-mail], [e-mail]
> 主题
> Re: [trill] [rbridge] draft-hu-trill-rbridge-esadi-04
>
>
>
>
>
> Hi Fangwei,
>
> Thank you for the explanation.
>
> So, RB1 doesnot include the end-stations MAC in its LSP. What if RB1 has 
opted not to send this end-station MAC in its ESADI-LSP earlier? The other 
ESADI RBridges has no way to learn that this MAC has to be flushed(which 
may be learned through other procedures except ESADI). It would be good if 
ESADI RBridges could explicitly tell other RBridges to forget a MAC.
>
> Regards,
> Somnath
>
> 2012/4/22 <[e-mail]>
>
> Thanks for the reviewing and comments.
>
> Pls see the following in line.
>
> >Hi Authors,
>
> >I have read the draft-hu-trill-rbridge-esadi-04 and support it.
>
> >I have one question regarding the problem stated in the draft
>
> > " 2. Fast update advantages: ESADI protocol provides a fast update of
>     end nodes MAC (Media Access Control) addresses.  If an end station
>     is unplugged from one RBridge and plugged into another, frames
>     addressed to that older RBridge can be black holed.  They can be
>     sent just to the older RBridge that the end station was connected
>     to until cached address information at some remote RBridge times
>     out, possibly for tens of seconds [RFC6325]."
>
> >In this scenario when an end-station moves TO a link where an
> >RBridge(RBx) with ESADI support is serving as AF for the vlan on which
> >the end-station is connected, this RBridge sends the end-station MACs
> >through ESADI pdu to other ESADI RBridges with a higher confidence and
> >the old routes in other ESADI RBridges are over-written.New routes(MAC
> >"A" is reachable via egress RBridge RBx) exist and frames destined to
> >MAC "A" are not black holed.
>
> >But what if this end-station moves FROM a link which has RBridge(RB1)
> >with ESADI support TO a link where RBridge(RB2) donot have ESADI
> >support. Is there any way RB1 can notify other ESADI implemented
> >RBridges in the campus to flush the old route(MAC "A" is reachable via
> >egress RB1) so that frames for MAC "A" are not send directly to RB1
> >and are rather treated as unknown unicast frame and send on a DTree?
> >Could RB1 send to ESADI Implemented RBridges that MAC "A" is no longer
> >reachable via itself by sending confidence as 0 for that MAC in its
> >ESADI pdus?
>
> [hfw] If RB1 notify that the end-station moves from the link, RB1 will 
update
>
> and flood the LSP originated with nulling out the end-station address. 
When other ESADI
>
> RBridge receives the updated LSP, they will forget the MAC "A" from its 
MAC table.
>
> In this way, ESADI protocol can fast update the MAC table of remote 
RBridges when the end station attached
>
> is unpluged or a new end station is pluged.
>
>
>
> >Please correct me if my understanding is wrong.
>
> >Also could we recommend ESADI implemented RBridges to become DRB and
> >serve more AF for vlans.
>
> >Editorial comments and typos:
>
> >In Abstract
> >ESADI (End System Address Distribution Information) should be replaced 
by
> >ESADI (End Station Address Distribution Information) as per RFC6325
>
> >In section 3. ESADI DRB State
> >8th line: "for which RB1 is holding an ESADI-LSP zero with an ESADI
> >Pararmeters" , typo for "Parameters"
>
>
> >In section 4. ESADI PDU processing
> >4th line:     "are only EASDI-LSP, EASDI-CSNP and EASDI-PSNP PDUs used
> >in ESADI."should be changed to
> >   "are only ESADI-LSP, ESADI-CSNP and ESADI-PSNP PDUs used in ESADI."
>
> >In section 4.1 Sending of ESASI PDUs
>
> >Change the typo in the header itself.
>
> >4th line:    "6(Innter.MacSA)" to '6(Inner.MacSA)"
>
> >5th line:     "starting with the Intradomain Routeing Protocol
> >Discriminator," Typo "Routeing" to "Routing"
>
> >2nd Para, 1st line: "Once an ESADI instance is operationally up, it
> >multicasts it self-
> >  originated LSP number zero on the virtual link to announce its ESADI
> >  parameters."   may be changed to
> >"Once an ESADI instance is operationally up, it multicasts/sends its 
self-
> >   originated LSP number zero on the virtual link to announce its ESADI
> >   parameters."
>
> >5th Para, 2nd line: Typo "EASDI"
>
> >In section 5. ESADI-LSP Contents
> >7th line typo "EASDAI-LSPs
>
> >In section 5.1 ESADI Parameter Data
> >4th line typo "occurrnce"
>
> [hfw] Thanks for the correcting, we will correct it in the next version.
>
>
> somnath chatterjee <[e-mail]>
> 发件人:  [e-mail]
>
> 2012-04-21 01:17
>
>
> 收件人
> [e-mail]
> 抄送
> 主题
> [trill] [rbridge] draft-hu-trill-rbridge-esadi-04
>
>
>
>
>
>
>
> Hi Authors,
>
> I have read the draft-hu-trill-rbridge-esadi-04 and support it.
>
> I have one question regarding the problem stated in the draft
>
> " 2. Fast update advantages: ESADI protocol provides a fast update of
>     end nodes MAC (Media Access Control) addresses.  If an end station
>     is unplugged from one RBridge and plugged into another, frames
>     addressed to that older RBridge can be black holed.  They can be
>     sent just to the older RBridge that the end station was connected
>     to until cached address information at some remote RBridge times
>     out, possibly for tens of seconds [RFC6325]."
>
> In this scenario when an end-station moves TO a link where an
> RBridge(RBx) with ESADI support is serving as AF for the vlan on which
> the end-station is connected, this RBridge sends the end-station MACs
> through ESADI pdu to other ESADI RBridges with a higher confidence and
> the old routes in other ESADI RBridges are over-written.New routes(MAC
> "A" is reachable via egress RBridge RBx) exist and frames destined to
> MAC "A" are not black holed.
>
> But what if this end-station moves FROM a link which has RBridge(RB1)
> with ESADI support TO a link where RBridge(RB2) donot have ESADI
> support. Is there any way RB1 can notify other ESADI implemented
> RBridges in the campus to flush the old route(MAC "A" is reachable via
> egress RB1) so that frames for MAC "A" are not send directly to RB1
> and are rather treated as unknown unicast frame and send on a DTree?
> Could RB1 send to ESADI Implemented RBridges that MAC "A" is no longer
> reachable via itself by sending confidence as 0 for that MAC in its
> ESADI pdus?
>
> Please correct me if my understanding is wrong.
>
> Also could we recommend ESADI implemented RBridges to become DRB and
> serve more AF for vlans.
>
> Editorial comments and typos:
>
> In Abstract
> ESADI (End System Address Distribution Information) should be replaced 
by
> ESADI (End Station Address Distribution Information) as per RFC6325
>
> In section 3. ESADI DRB State
> 8th line: "for which RB1 is holding an ESADI-LSP zero with an ESADI
> Pararmeters" , typo for "Parameters"
>
>
> In section 4. ESADI PDU processing
> 4th line:     "are only EASDI-LSP, EASDI-CSNP and EASDI-PSNP PDUs used
> in ESADI."should be changed to
>  "are only ESADI-LSP, ESADI-CSNP and ESADI-PSNP PDUs used in ESADI."
>
> In section 4.1 Sending of ESASI PDUs
>
> Change the typo in the header itself.
>
> 4th line:    "6(Innter.MacSA)" to '6(Inner.MacSA)"
>
> 5th line:     "starting with the Intradomain Routeing Protocol
> Discriminator," Typo "Routeing" to "Routing"
>
> 2nd Para, 1st line: "Once an ESADI instance is operationally up, it
> multicasts it self-
>  originated LSP number zero on the virtual link to announce its ESADI
>  parameters."   may be changed to
> "Once an ESADI instance is operationally up, it multicasts/sends its 
self-
>  originated LSP number zero on the virtual link to announce its ESADI
>  parameters."
>
> 5th Para, 2nd line: Typo "EASDI"
>
> In section 5. ESADI-LSP Contents
> 7th line typo "EASDAI-LSPs
>
> In section 5.1 ESADI Parameter Data
> 4th line typo "occurrnce"
>
> Thank you,
> Regards,
> Somnath
> _______________________________________________
> trill mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/trill
>
>
>
_______________________________________________
trill mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/trill