Re: [bess] draft-ietf-bess-evpn-prefix-advertisement-02

2015-10-08 Thread Rabadan, Jorge (Jorge)
Sami, Besides what Ali says, for your second question note that in the use-case 5.4 we are explicitly avoiding GW-IP non-zero plus router’s mac in the same update: "The Router's MAC Extended Community MUST be sent if the associated RT-5's GW IP Address is zero.” Thanks. Jorge On

Re: [bess] draft-ietf-bess-evpn-prefix-advertisement-02

2015-10-07 Thread Ali Sajassi (sajassi)
Sami, There are intended for different scenarios. When a subnet is sitting behind a TS, there is no need to advertise label/VNI in RT5 for that subnet because it gets resolved via label/VNI associated with RT2 for that TS. In other scenarios, where subnet gets directly advertised by PE (e.g., no

[bess] draft-ietf-bess-evpn-prefix-advertisement-02

2015-10-07 Thread Sami Boutros (sboutros)
Hi Jorge, In some of the use case sections in the draft, there is no mention of the label/VNI that will be associated with RT-5. As well if the router-mac will be associated with RT-5 and the GW-IP will be set, why do we need to advertise those again in RT-2? Thanks, Sami