Re: MAC route with IP
"Ali Sajassi (sajassi)" <sajassi@cisco.com> Tue, 13 May 2014 06:21 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 2103C1A03F7
for <l2vpn@ietfa.amsl.com>; Mon, 12 May 2014 23:21:30 -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 DzcFIvY_bwDO for <l2vpn@ietfa.amsl.com>;
Mon, 12 May 2014 23:21:27 -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 D9B151A0844
for <l2vpn@ietf.org>; Mon, 12 May 2014 23:21:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
d=cisco.com; i=@cisco.com; l=21304; q=dns/txt;
s=iport; t=1399962081; x=1401171681;
h=from:to:cc:subject:date:message-id:in-reply-to: mime-version;
bh=wQWU+s+kl4dJRTi2CDMx5R+Gvs5JcFb3rTEC73VUplo=;
b=iy9ih+EHQqYret87OjI98zXdewuISqryjqNh/dVgBze4lrOCblt1ZYMu
el30czHVsuw5StzkGalfuWd6LkfNMh426eIh/LUkprHEvEy2pDiPVR8TY
rVCiGIxFVITAc7vXdYEqpIlCRiF5pCpJBCWCN3IRk88AwHp19+3gdzIeX g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiEFAO24cVOtJA2L/2dsb2JhbABZgkIjIU9YxXoBgRoWdIIlAQEBBC1MEgEIEQMBAQEhBzkUCQgBAQQBDQWIQQHQbBeOQREGAQaEOgSFeJNQkweDNoIv
X-IronPort-AV: E=Sophos;i="4.97,1041,1389744000";
d="scan'208,217";a="324222477"
Received: from alln-core-6.cisco.com ([173.36.13.139])
by rcdn-iport-1.cisco.com with ESMTP; 13 May 2014 06:21:18 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77])
by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s4D6LI8p002368
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
Tue, 13 May 2014 06:21:18 GMT
Received: from xmb-aln-x13.cisco.com ([fe80::5404:b599:9f57:834b]) by
xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0123.003; Tue, 13
May 2014 01:21:18 -0500
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: Jakob Heitz <jakob.heitz@ericsson.com>, "l2vpn@ietf.org" <l2vpn@ietf.org>
Subject: Re: MAC route with IP
Thread-Topic: MAC route with IP
Thread-Index: Ac9tnTVAaQfHHQKqR0C1MGMVDrT48///65IA///deaD//7hWkIACA6eA
Date: Tue, 13 May 2014 06:21:18 +0000
Message-ID: <CF96FC89.D38FD%sajassi@cisco.com>
In-Reply-To: <2F3EBB88EC3A454AAB08915FBF0B8C7E03053BF0@eusaamb109.ericsson.se>
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.9.64]
Content-Type: multipart/alternative;
boundary="_000_CF96FC89D38FDsajassiciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/GNJT4VmxSJ2U_FYO5Fw7xK2uq1U
Cc: Antoni Przygienda <antoni.przygienda@ericsson.com>
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 06:21:30 -0000
Jakob, Antoni: Agreed that the ARP entries can timeout independent from the MAC table and thus the entries in MAC-VRF and ARP table can be deleted independent of each other. However, the existing text is still accurate. It already covers the scenario that is interest to you where there are multiple IP/MAC pair advertisement for a given MAC plus MAC-only advertisement. In such case, the withdraw of a IP/MAC pair will remove the corresponding IP/MAC entry in the ARP table but it doesn't remove the MAC entry in the MAC-VRF table. I added the following couple of sentences to the end of 2nd para of section 10 for further clarification: "If the receiving PE has already received a MAC-only advertisement for MACx in addition to the IPx/MACx advertisement, then when it receives a withdraw message for the IPx/MACx, it MUST delete the corresponding entry from the ARP table. However, it MUST not delete the MACx entry from the MAC-VRF table unless it receives a withdraw message for MACx only." Cheers, Ali From: Jakob Heitz <jakob.heitz@ericsson.com<mailto:jakob.heitz@ericsson.com>> Date: Sunday, May 11, 2014 10:59 PM To: Jakob Heitz <jakob.heitz@ericsson.com<mailto:jakob.heitz@ericsson.com>>, Cisco Employee <sajassi@cisco.com<mailto:sajassi@cisco.com>>, "l2vpn@ietf.org<mailto:l2vpn@ietf.org>" <l2vpn@ietf.org<mailto:l2vpn@ietf.org>> Cc: Antoni Przygienda <antoni.przygienda@ericsson.com<mailto:antoni.przygienda@ericsson.com>> Subject: RE: MAC route with IP People clear ARP caches when they get too big. When that happens, the bridge table may not be cleared at the same time or at all. An ARP cache may have a different timeout than the bridge table. A bridge can snoop ARP messages to learn bindings and those bindings can time out. However, many other packets can come from the same MAC address, keeping the MAC alive in the bridge table. In this case, the MAC-IP binding will be lost without the MAC address itself being lost. IP-MAC bindings can be learnt other than by snooping ARPs, by configuration, for example. Such configurations can be removed. Cheers, Jakob. From: L2vpn [mailto:l2vpn-bounces@ietf.org] On Behalf Of Jakob Heitz Sent: Sunday, May 11, 2014 10:39 PM To: Ali Sajassi (sajassi); l2vpn@ietf.org<mailto:l2vpn@ietf.org> Cc: Antoni Przygienda Subject: RE: MAC route with IP When the IP address is dissociated with the MAC address, but the MAC address still exits. Cheers, Jakob. From: Ali Sajassi (sajassi) [mailto:sajassi@cisco.com] Sent: Sunday, May 11, 2014 10:34 PM To: Jakob Heitz; l2vpn@ietf.org<mailto:l2vpn@ietf.org> Cc: Antoni Przygienda Subject: Re: MAC route with IP Hi Jakob, I believe the currency text is correct and sufficient. What use case do you have in mind? EVPN PE devices that only do L2 (w/ flooding), only advertise MAC route (w/o IP address) and EVPN PE devices that do L2 w/ ARP suppression, advertise both MAC and IP. In the latter case, if there are several IP addresses map to the same MAC address, then the MAC address from MAC-VRF only gets removed, when there is no more ARP entry with that MAC address. Cheers, Ali From: Jakob Heitz <jakob.heitz@ericsson.com<mailto:jakob.heitz@ericsson.com>> Date: Sunday, May 11, 2014 9:56 PM To: "l2vpn@ietf.org<mailto:l2vpn@ietf.org>" <l2vpn@ietf.org<mailto:l2vpn@ietf.org>> Cc: Antoni Przygienda <antoni.przygienda@ericsson.com<mailto:antoni.przygienda@ericsson.com>> Subject: MAC route with IP We have another issue In section 10: ARP and ND, the draft says: If there are multiple IP addresses associated with a MAC address, then multiple MAC advertisement routes MUST be generated, one for each IP address. For instance, this may be the case when there are both an IPv4 and an IPv6 address associated with the MAC address. When the IP address is dissociated with the MAC address, then the MAC advertisement route with that particular IP address MUST be withdrawn. If such a route is withdrawn and no MAC route without IP exists, then the MAC address will be forgotten. Therefore, we would like to add a sentence: Whenever a PE advertises one or more MAC advertisement routes with IP address for a particular MAC address, it MUST also advertise one MAC advertisement route without an IP address for that MAC address. Thanks, Jakob.
- 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