Re: [bess] draft-ietf-bess-evpn-prefix-advertisement-05 comments

2017-10-19 Thread Rabadan, Jorge (Nokia - US/Mountain View)
OK, just published rev 07 with the latest changes you suggested. I guess it is ready from your perspective now? Thank you, Jeffrey, for the detailed review! Jorge On 10/19/17, 1:25 PM, "Jeffrey (Zhaohui) Zhang" wrote: Yup - perhaps add "since the EC could be used for

Re: [bess] draft-ietf-bess-evpn-prefix-advertisement-05 comments

2017-10-19 Thread Jeffrey (Zhaohui) Zhang
Yup - perhaps add "since the EC could be used for other purposes". Thanks! Jeffrey > -Original Message- > From: Rabadan, Jorge (Nokia - US/Mountain View) > [mailto:jorge.raba...@nokia.com] > Sent: Thursday, October 19, 2017 1:54 AM > To: Jeffrey (Zhaohui) Zhang ;

Re: [bess] draft-ietf-bess-evpn-prefix-advertisement-05 comments

2017-10-18 Thread Rabadan, Jorge (Nokia - US/Mountain View)
Yes, also since the MAC is not part of the NLRI, some co-authors suggested that. Do you think we should add?: “The presence of the Router's MAC EC alone is not enough to indicate the use of the mac address as the overlay index” Thx Jorge On 10/19/17, 4:37 AM, "Jeffrey (Zhaohui) Zhang"

Re: [bess] draft-ietf-bess-evpn-prefix-advertisement-05 comments

2017-10-18 Thread Jeffrey (Zhaohui) Zhang
Are you saying that the presence of the Router's MAC EC alone is not enough to indicate the use of the mac address as the overlay index (since the EC was originally designed for other purpose), but the encoding of ESI and GW IP addr in the NLRI is enough to indicate that they will be used as

Re: [bess] draft-ietf-bess-evpn-prefix-advertisement-05 comments

2017-10-17 Thread Rabadan, Jorge (Nokia - US/Mountain View)
Hi Jeffrey, Ah ok, I see what you mean. The label column is basically based on this text in section 3.1: o The MPLS Label field is encoded as 3 octets, where the high-order 20 bits contain the label value. When sending, the label value SHOULD be zero if recursive resolution based

Re: [bess] draft-ietf-bess-evpn-prefix-advertisement-05 comments

2017-10-17 Thread Jeffrey (Zhaohui) Zhang
Hi Jorge, > >+--+--+--+++ > >| ESI | GW-IP| MAC* | Label | Overlay Index | > >|--| > >| Non-Zero | Zero | Zero

Re: [bess] draft-ietf-bess-evpn-prefix-advertisement-05 comments

2017-10-17 Thread Rabadan, Jorge (Nokia - US/Mountain View)
Hi Jeffrey, Pls see in-line. I’ve made the two minor changes below, but I won’t publish rev 07 until we need to make more changes. Is it ready now from your perspective? Thanks. Jorge On 10/16/17, 8:12 PM, "Jeffrey (Zhaohui) Zhang" wrote: Hi Jorge, >

Re: [bess] draft-ietf-bess-evpn-prefix-advertisement-05 comments

2017-10-16 Thread Jeffrey (Zhaohui) Zhang
Hi Jorge, >+--+--+--+++ >| ESI | GW-IP| MAC* | Label | Overlay Index | >|--| >| Non-Zero | Zero | Zero | Don't Care | ESI

Re: [bess] draft-ietf-bess-evpn-prefix-advertisement-05 comments

2017-10-16 Thread Rabadan, Jorge (Nokia - US/Mountain View)
Hi Jeffrey, Thank you very much for yet another good look at it. I took most of your suggestions. By the way, I changed the terms MAC-VRF and Core-EVI to BD and SBD as you suggested. I agree it is better. Please find my responses below, and check out rev 06 that is already posted. Thank you.

[bess] draft-ietf-bess-evpn-prefix-advertisement-05 comments

2017-10-12 Thread Jeffrey (Zhaohui) Zhang
Hi Jorge and other co-authors, I am giving another round of review as the document shepherd before I do the shepherd write-up. Please see some nits/comments/questions below. Thanks! Jeffrey -- EVPN provides