Re: MAC route with IP

"Ali Sajassi (sajassi)" <sajassi@cisco.com> Mon, 12 May 2014 05:34 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 9BB891A03F8 for <l2vpn@ietfa.amsl.com>; Sun, 11 May 2014 22:34:03 -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 GMEtG6fZZMXH for <l2vpn@ietfa.amsl.com>; Sun, 11 May 2014 22:34:01 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 812311A02C7 for <l2vpn@ietf.org>; Sun, 11 May 2014 22:34:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9926; q=dns/txt; s=iport; t=1399872836; x=1401082436; h=from:to:cc:subject:date:message-id:in-reply-to: mime-version; bh=5L4Sg1veED+uEpJ2EzABVe8l7NqcB83fXHTjSOLRvFQ=; b=LN5ZT+E80XlSJYYHcZiE3GjiDh/3ANxaBHncLJZhwnia7Yur3xRZfmxm R4A4hmA1GnObrMEuO9w5AJ38W+zSIiTFTdH0BqecvvgvRFFByy3jMUbju HbCssR0HPzir0Kud+OXn+C6cl4Lsi2iGte27RhggWXLbUCax+919q7nxZ o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjYFAKJccFOtJA2B/2dsb2JhbABZgkIjIU9YxWEBgRcWdIIlAQIELUwSAQgRAwECKDkUCQgBAQQBDQWIQQHOBxeOQREHhEAEmUiTB4M2gi8
X-IronPort-AV: E=Sophos;i="4.97,1033,1389744000"; d="scan'208,217";a="324128309"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-8.cisco.com with ESMTP; 12 May 2014 05:33:55 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id s4C5XtR3007208 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 12 May 2014 05:33:55 GMT
Received: from xmb-aln-x13.cisco.com ([fe80::5404:b599:9f57:834b]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.03.0123.003; Mon, 12 May 2014 00:33:55 -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
Date: Mon, 12 May 2014 05:33:54 +0000
Message-ID: <CF95A92D.D380B%sajassi@cisco.com>
In-Reply-To: <2F3EBB88EC3A454AAB08915FBF0B8C7E03053A80@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.21.66.92]
Content-Type: multipart/alternative; boundary="_000_CF95A92DD380Bsajassiciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/GlS3wgViLNsTAXI3YBLYkd_JrhQ
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: Mon, 12 May 2014 05:34:03 -0000

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.