Re: MAC route with IP

["Ali Sajassi (sajassi)" <[e-mail]>]

Hi Jakob,

Changed your sentence to: "In such scenarios when the ARP entry times out and causes the MAC/IP to be withdrawn, then the MAC information will not be lost."

Cheers,
Ali

From: Jakob Heitz <[e-mail]<mailto:[e-mail]>>
Date: Wednesday, May 14, 2014 12:09 AM
To: Cisco Employee <[e-mail]<mailto:[e-mail]>>
Cc: Aldrin Isaac <[e-mail]<mailto:[e-mail]>>, John E Drake <[e-mail]<mailto:[e-mail]>>, "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>, Antoni Przygienda <[e-mail]<mailto:[e-mail]>>
Subject: Re: MAC route with IP

"Note that a MAC-only route can be advertised along with but independently of a MAC/IP route in scenarios where the MAC learning over the access network is done in the data-plane and independently of ARP snooping that generates the MAC/IP route. This ensures that if the ARP entry times out and causes the MAC/IP to be withdrawn, then the MAC information will not be lost. In scenarios where the host MAC/IP is learned via the management or control planes, the sender PE may advertise only the MAC/IP route."

--
Jakob Heitz.


On May 13, 2014, at 11:22 PM, "Ali Sajassi (sajassi)" <[e-mail]<mailto:[e-mail]>> wrote:


Hi Aldrin,

How about the following:

"Note that a MAC-only route can be advertised along with but independent from MAC/IP route for scenarios where the MAC learning over access network/node is done in data-plane and independent from ARP snooping that generates MAC/IP route. In scenarios where host MAC/IP is learned via management or control plane, then the sender PE may only generates and advertises MAC/IP route."

Cheers,
Ali

From: Aldrin Isaac <[e-mail]<mailto:[e-mail]>>
Date: Tuesday, May 13, 2014 8:02 PM
To: Cisco Employee <[e-mail]<mailto:[e-mail]>>
Cc: John E Drake <[e-mail]<mailto:[e-mail]>>, Jakob Heitz <[e-mail]<mailto:[e-mail]>>, "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>, Antoni Przygienda <[e-mail]<mailto:[e-mail]>>
Subject: Re: MAC route with IP

How about:

"Note that a MAC-only route can be advertised along with MAC/IP routes for use cases where an active MAC must remain reachable when all IP's become disassociated with that MAC."

On Tuesday, May 13, 2014, Ali Sajassi (sajassi) <[e-mail]<mailto:[e-mail]>> wrote:
Hi Aldrin,

I believe the application of MAC/IP route in section 10 is clear. However, if you think we can make further clarification, please suggest the text. We need to make sure the functionality that we specify is clearly described and explained. We don't need to describe/mention the functionality that is not used/needed.

Thanks,
Ali

From: Aldrin Isaac <[e-mail]<javascript:_e(%7B%7D,'cvml','[e-mail]');>>
Date: Tuesday, May 13, 2014 11:14 AM
To: Cisco Employee <[e-mail]<javascript:_e(%7B%7D,'cvml','[e-mail]');>>
Cc: John E Drake <[e-mail]<javascript:_e(%7B%7D,'cvml','[e-mail]');>>, Jakob Heitz <[e-mail]<javascript:_e(%7B%7D,'cvml','[e-mail]');>>, "[e-mail]<javascript:_e(%7B%7D,'cvml','[e-mail]');>" <[e-mail]<javascript:_e(%7B%7D,'cvml','[e-mail]');>>, Antoni Przygienda <[e-mail]<javascript:_e(%7B%7D,'cvml','[e-mail]');>>
Subject: Re: MAC route with IP

Would it be worthwhile to mention that MAC/IP routes should not be used as a proxy for MAC-only route?

On Tuesday, May 13, 2014, Ali Sajassi (sajassi) <[e-mail]> wrote:

Yes, although my email and Jorge's emails crossed each others, we are both saying exactly the same thing.

That's why I think the existing text is sufficient and we don't need to add any thing more because both of the scenarios I mentioned below can happen and the existing text covers them both.

Cheers,
Ali



From: John E Drake <[e-mail]>
Date: Tuesday, May 13, 2014 10:44 AM
To: Cisco Employee <[e-mail]>om>, Jakob Heitz <[e-mail]>om>, "[e-mail]" <[e-mail]>
Cc: Antoni Przygienda <[e-mail]>
Subject: RE: MAC route with IP


Ali,



As both Jorge and you have pointed out, there may indeed be cases for which there should not be a MAC only route.



Yours Irrespectively,



John



From: L2vpn [mailto:[e-mail]] On Behalf Of Ali Sajassi (sajassi)
Sent: Tuesday, May 13, 2014 10:38 AM
To: Jakob Heitz; [e-mail]
Cc: Antoni Przygienda
Subject: Re: MAC route with IP





Even if there is reordering by route reflector, then as I said, I don't see an issue here :-) In your example, the receiver sees the withdrawn of the IP/MAC route before receiving the MAC-only route. In that case, the traffic toward that MAC address will get flooding (or dropped if flooding is disabled) till it receives the MAC-only route. However, why does the sender has to wait till it withdraws the IP/MAC advertisement before sending the MAC-only advertisement – e.g., why doesn't the sender send MAC-only advertisement as soon as it learns it.



Again, there are scenarios in which learning is done in data-plane along with ARP suppression. In such scenarios, the sender should send MAC-only route as soon as it learns it and MAC/IP route when it snoops the ARP.  However, there are other scenarios where there is no MAC learning in data-plane. In such scenario, when a VM becomes known, the MAC/IP route is advertised and if the VM goes away, MAC/IP is withdrawn. In such scenarios, we don't want to advertise an extra route (MAC-only route) unnecessarily.



Cheers,

Ali



From: Jakob Heitz <[e-mail]>
Date: