Re: MAC route with IP

Aldrin Isaac <aldrin.isaac@gmail.com> Wed, 14 May 2014 03:02 UTC

Return-Path: <aldrin.isaac@gmail.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 62EAC1A0226 for <l2vpn@ietfa.amsl.com>; Tue, 13 May 2014 20:02:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 fxvuyadlpMPy for <l2vpn@ietfa.amsl.com>; Tue, 13 May 2014 20:02:22 -0700 (PDT)
Received: from mail-yh0-x235.google.com (mail-yh0-x235.google.com [IPv6:2607:f8b0:4002:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id C99B01A0197 for <l2vpn@ietf.org>; Tue, 13 May 2014 20:02:21 -0700 (PDT)
Received: by mail-yh0-f53.google.com with SMTP id i57so1168937yha.12 for <l2vpn@ietf.org>; Tue, 13 May 2014 20:02:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FdKyr9Aw3Ke+ougl7hSnb69Htfib4+xetu+x3C6TXyI=; b=LDLu61lbgNsFXtvq9z8qxcwQzoCc5gNRlm4kLTYV3Upa4+nCwXaic854TOxf/+IDyS RuA5GVXg68ktO8p+ARE9toDFySoEwAj1HbsoOrxUBTnfyGHrNMpEgwfeaSx8u3Edrfbq 6JJNe6zO2z7h6Z+M/PTY/w12IpHLq3QZ2IEsZZ5A5A+NSNZqqB3htMmiYS3m/k/HM66x nlC1D34u0ecPRg/yi/Gmayt8IHxZfx+th+xST9z9IkMwJjcC74yJGiLh8eBUjnmNrw+t m9rh9gNrnTxsnx7lyNnbuNuRimShUrn9S++KMkSXY7J1DwKXxMGb19zCAFigbP+9it6u hvQg==
MIME-Version: 1.0
X-Received: by 10.236.159.67 with SMTP id r43mr1303152yhk.50.1400036535239; Tue, 13 May 2014 20:02:15 -0700 (PDT)
Received: by 10.170.75.136 with HTTP; Tue, 13 May 2014 20:02:14 -0700 (PDT)
In-Reply-To: <CF97B0F9.D3A93%sajassi@cisco.com>
References: <CAOA2mbyfVfRYqgsnZAuc8cpt=zdD1hFPijbXTkkrqV+T3MA=uQ@mail.gmail.com> <CF97B0F9.D3A93%sajassi@cisco.com>
Date: Tue, 13 May 2014 23:02:14 -0400
Message-ID: <CAOA2mbzei_th6MB5DUPcJ2jE7mdExX3aO6frx6VeLZLLB+Eo8g@mail.gmail.com>
Subject: Re: MAC route with IP
From: Aldrin Isaac <aldrin.isaac@gmail.com>
To: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
Content-Type: multipart/alternative; boundary=20cf30434c645b0bc904f9536831
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/L1q4BYjm1DG-tBO4nwUqbn3WGhg
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 03:02:26 -0000

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> 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>gt;, "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: *
>
>