Re: MAC route with IP
"Ali Sajassi (sajassi)" <sajassi@cisco.com> Wed, 14 May 2014 06:22 UTC
Return-Path: <sajassi@cisco.com>
X-Original-To: l2vpn@ietfa.amsl.com
Delivered-To: l2vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 8B2E31A023D
for <l2vpn@ietfa.amsl.com>; Tue, 13 May 2014 23:22:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.151
X-Spam-Level:
X-Spam-Status: No, score=-10.151 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651,
SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id UcWYRzmT2AeW for <l2vpn@ietfa.amsl.com>;
Tue, 13 May 2014 23:22:47 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93])
by ietfa.amsl.com (Postfix) with ESMTP id A7B461A0238
for <l2vpn@ietf.org>; Tue, 13 May 2014 23:22:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
d=cisco.com; i=@cisco.com; l=15473; q=dns/txt;
s=iport; t=1400048561; x=1401258161;
h=from:to:cc:subject:date:message-id:in-reply-to: mime-version;
bh=nKl4QYmQBfFoC5/+u3WKAgAo0qVHyJEVwJsLE5EQiIg=;
b=KU3QioW8bGIYUxdNBfieg1qwZ/FgXjYhFmRygcb8/UWSGXIVOLrfcP0x
RXcMihXEGnpYb1zId+JBgiWoKj4rX6Vp8WwcfYGFK9QrJhPA/TOYn74zA
mncdrb6vbf68Pz1vDLKcQDgN3tfNz+Cy6sYQsk7cmeg3VtOWF+O7PSzLM A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmIFAFcLc1OtJA2I/2dsb2JhbABZgkIjIU9YxXMBgR4WdIIlAQEBBG0MEgEIEQMBAQEoKBEUCQgCBA4FiC0DEQHKCQ2GVBQDBowzggQRBgGEQASFeJFmgXONKYVqgzaBbgc7
X-IronPort-AV: E=Sophos;i="4.97,1050,1389744000";
d="scan'208,217";a="43643380"
Received: from alln-core-3.cisco.com ([173.36.13.136])
by alln-iport-6.cisco.com with ESMTP; 14 May 2014 06:22:40 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76])
by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s4E6MeRS021746
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
Wed, 14 May 2014 06:22:40 GMT
Received: from xmb-aln-x13.cisco.com ([fe80::5404:b599:9f57:834b]) by
xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0123.003; Wed, 14
May 2014 01:22:40 -0500
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: Aldrin Isaac <aldrin.isaac@gmail.com>
Subject: Re: MAC route with IP
Thread-Topic: MAC route with IP
Thread-Index: Ac9tnTVAaQfHHQKqR0C1MGMVDrT48///65IA///deaD//7hWkIACA6eA//8w+kAAMBG6gP//3aLA///WaoD//4r38P//LYQA//434xD//I4AAP/4oTIA//GyuYD/4mGtAP/FALUA
Date: Wed, 14 May 2014 06:22:39 +0000
Message-ID: <CF985727.D3B10%sajassi@cisco.com>
In-Reply-To: <CAOA2mbzei_th6MB5DUPcJ2jE7mdExX3aO6frx6VeLZLLB+Eo8g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.4.130416
x-originating-ip: [10.89.14.185]
Content-Type: multipart/alternative;
boundary="_000_CF985727D3B10sajassiciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/WBHfjIRl4yRLH4PIQAa6_FReyiw
Cc: Antoni Przygienda <antoni.przygienda@ericsson.com>,
"l2vpn@ietf.org" <l2vpn@ietf.org>
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer 2 Virtual Private Networks <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2vpn>,
<mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn/>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>,
<mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 May 2014 06:22:50 -0000
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 <aldrin.isaac@gmail.com<mailto:aldrin.isaac@gmail.com>> Date: Tuesday, May 13, 2014 8:02 PM To: Cisco Employee <sajassi@cisco.com<mailto:sajassi@cisco.com>> Cc: John E Drake <jdrake@juniper.net<mailto:jdrake@juniper.net>>, Jakob Heitz <jakob.heitz@ericsson.com<mailto:jakob.heitz@ericsson.com>>, "l2vpn@ietf.org<mailto:l2vpn@ietf.org>" <l2vpn@ietf.org<mailto:l2vpn@ietf.org>>, Antoni Przygienda <antoni.przygienda@ericsson.com<mailto:antoni.przygienda@ericsson.com>> 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) <sajassi@cisco.com<mailto:sajassi@cisco.com>> 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 <aldrin.isaac@gmail.com<javascript:_e(%7B%7D,'cvml','aldrin.isaac@gmail.com');>> Date: Tuesday, May 13, 2014 11:14 AM To: Cisco Employee <sajassi@cisco.com<javascript:_e(%7B%7D,'cvml','sajassi@cisco.com');>> Cc: John E Drake <jdrake@juniper.net<javascript:_e(%7B%7D,'cvml','jdrake@juniper.net');>>, Jakob Heitz <jakob.heitz@ericsson.com<javascript:_e(%7B%7D,'cvml','jakob.heitz@ericsson.com');>>, "l2vpn@ietf.org<javascript:_e(%7B%7D,'cvml','l2vpn@ietf.org');>" <l2vpn@ietf.org<javascript:_e(%7B%7D,'cvml','l2vpn@ietf.org');>>, Antoni Przygienda <antoni.przygienda@ericsson.com<javascript:_e(%7B%7D,'cvml','antoni.przygienda@ericsson.com');>> 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) <sajassi@cisco.com> 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 <jdrake@juniper.net> Date: Tuesday, May 13, 2014 10:44 AM To: Cisco Employee <sajassi@cisco.com>om>, Jakob Heitz <jakob.heitz@ericsson.com>om>, "l2vpn@ietf.org" <l2vpn@ietf.org> Cc: Antoni Przygienda <antoni.przygienda@ericsson.com> 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:l2vpn-bounces@ietf.org] On Behalf Of Ali Sajassi (sajassi) Sent: Tuesday, May 13, 2014 10:38 AM To: Jakob Heitz; l2vpn@ietf.org 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 <jakob.heitz@ericsson.com> Date:
- MAC route with IP Jakob Heitz
- Re: MAC route with IP Ali Sajassi (sajassi)
- RE: MAC route with IP Jakob Heitz
- Re: MAC route with IP Ali Sajassi (sajassi)
- RE: MAC route with IP Jakob Heitz
- RE: MAC route with IP Antoni Przygienda
- Re: MAC route with IP Ali Sajassi (sajassi)
- RE: MAC route with IP Antoni Przygienda
- Re: MAC route with IP Ali Sajassi (sajassi)
- RE: MAC route with IP Jakob Heitz
- Re: MAC route with IP Ali Sajassi (sajassi)
- Re: MAC route with IP Ali Sajassi (sajassi)
- RE: MAC route with IP Jakob Heitz
- Re: MAC route with IP Ali Sajassi (sajassi)
- RE: MAC route with IP Jakob Heitz
- RE: MAC route with IP Jakob Heitz
- RE: MAC route with IP Antoni Przygienda
- Re: MAC route with IP Ali Sajassi (sajassi)
- RE: MAC route with IP Jakob Heitz
- Re: MAC route with IP Rabadan, Jorge (Jorge)
- RE: MAC route with IP Jakob Heitz
- Re: MAC route with IP Ali Sajassi (sajassi)
- Re: MAC route with IP Rabadan, Jorge (Jorge)
- RE: MAC route with IP John E Drake
- RE: MAC route with IP John E Drake
- Re: MAC route with IP Ali Sajassi (sajassi)
- Re: MAC route with IP Rabadan, Jorge (Jorge)
- Re: MAC route with IP Aldrin Isaac
- Re: MAC route with IP Ali Sajassi (sajassi)
- RE: MAC route with IP Jakob Heitz
- Re: MAC route with IP Aldrin Isaac
- Re: MAC route with IP Ali Sajassi (sajassi)
- Re: MAC route with IP Jakob Heitz
- Re: MAC route with IP Ali Sajassi (sajassi)
- Re: MAC route with IP Jakob Heitz
- Re: MAC route with IP Aldrin Isaac
- Re: MAC route with IP Aldrin Isaac
- RE: MAC route with IP Jakob Heitz
- RE: MAC route with IP Linda Dunbar