Re: MAC route with IP
"Ali Sajassi (sajassi)" <sajassi@cisco.com> Tue, 13 May 2014 18:32 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 8C18C1A010C
for <l2vpn@ietfa.amsl.com>; Tue, 13 May 2014 11:32:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.151
X-Spam-Level:
X-Spam-Status: No, score=-15.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, RCVD_IN_DNSWL_HI=-5,
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 HDecot8bA97H for <l2vpn@ietfa.amsl.com>;
Tue, 13 May 2014 11:32:39 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72])
by ietfa.amsl.com (Postfix) with ESMTP id 3ED651A0101
for <l2vpn@ietf.org>; Tue, 13 May 2014 11:32:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
d=cisco.com; i=@cisco.com; l=13269; q=dns/txt;
s=iport; t=1400005953; x=1401215553;
h=from:to:cc:subject:date:message-id:in-reply-to: mime-version;
bh=pDV3igocgjZ1xDiy/5CiP3y/RVkdysitk5J9gfeWHe0=;
b=QFJyDF1SmJxIpJKjm77XruRsgdzuKtD6A00VjD6oMmOAl+2vxD3CFaB8
wfZI2xhEw7pKK8UrV8VCwng7wVfRUjnj8RRPix3h0lq3t9Et4lqODtAYM
xew6cpMVF+MdoaUtyY20FIRq537HY2aEYEFQuRp92s30wJNP/w/7LlOxU I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQFAENkclOtJA2B/2dsb2JhbABZgkIjIU9YxX4BgSMWdIIlAQEBBG0MEgEIEQMBAQEoKBEUCQgCBA4FiC0DEQHAOg2GVBQDBowzggQRBgGEQASFeI9fggaBc40nhWmDNoFuBzs
X-IronPort-AV: E=Sophos;i="4.97,1044,1389744000";
d="scan'208,217";a="324379732"
Received: from alln-core-9.cisco.com ([173.36.13.129])
by rcdn-iport-1.cisco.com with ESMTP; 13 May 2014 18:32:32 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79])
by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id s4DIWWPi025740
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
Tue, 13 May 2014 18:32:32 GMT
Received: from xmb-aln-x13.cisco.com ([fe80::5404:b599:9f57:834b]) by
xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0123.003; Tue, 13
May 2014 13:32:32 -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//GyuYA=
Date: Tue, 13 May 2014 18:32:31 +0000
Message-ID: <CF97B0F9.D3A93%sajassi@cisco.com>
In-Reply-To: <CAOA2mbyfVfRYqgsnZAuc8cpt=zdD1hFPijbXTkkrqV+T3MA=uQ@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.128.2.48]
Content-Type: multipart/alternative;
boundary="_000_CF97B0F9D3A93sajassiciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/x6y56OrFttTre2qiXhDvuHRwcmQ
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: Tue, 13 May 2014 18:32:41 -0000
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<mailto:aldrin.isaac@gmail.com>> Date: Tuesday, May 13, 2014 11:14 AM 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 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<mailto: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<javascript:_e(%7B%7D,'cvml','jdrake@juniper.net');>> Date: Tuesday, May 13, 2014 10:44 AM To: Cisco Employee <sajassi@cisco.com<javascript:_e(%7B%7D,'cvml','sajassi@cisco.com');>>, 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');>> Cc: Antoni Przygienda <antoni.przygienda@ericsson.com<javascript:_e(%7B%7D,'cvml','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: Tuesday, May 13, 2014 10:13 AM To: Cisco Employee <sajassi@cisco.com>om>, "l2vpn@ietf.org" <l2vpn@ietf.org> Cc: Antoni Przygienda <antoni.przygienda@ericsson.com> Subject: RE: MAC route with IP A route reflector can and frequently does reorder routes from the same speaker. For example, a version walk of a tree does not walk in version order, it walks in key order.
- 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