Re: MAC route with IP

Aldrin Isaac <aldrin.isaac@gmail.com> Wed, 14 May 2014 16:11 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 D718F1A02CC for <l2vpn@ietfa.amsl.com>; Wed, 14 May 2014 09:11:51 -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 xX3MVwrBEHzY for <l2vpn@ietfa.amsl.com>; Wed, 14 May 2014 09:11:44 -0700 (PDT)
Received: from mail-yk0-x231.google.com (mail-yk0-x231.google.com [IPv6:2607:f8b0:4002:c07::231]) by ietfa.amsl.com (Postfix) with ESMTP id 33FB91A029F for <l2vpn@ietf.org>; Wed, 14 May 2014 09:11:44 -0700 (PDT)
Received: by mail-yk0-f177.google.com with SMTP id 19so1753318ykq.36 for <l2vpn@ietf.org>; Wed, 14 May 2014 09:11:37 -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=p2/9Lne1Ccqodi5ShX3FGSY1EjJrOaWEci86kAu4uuo=; b=aDoUQbwrC4aRZHt6YIVnFl1P0FzxV9QLJQdaPGOmLvxESBfmrco019kpHB55cecjlB ej5qo9pj2BKMw/aLba4ko2nJElUOCIaT+7BQLupVz4C6jJWQnOjJhoewEG/z2HD2jvC+ GpJK84O/nBcT7AMlOpnv4YrxPkaJ4CT9y/GbjvhMG0laoU1uaAHEINK7Pt0TVisl6/no rFGf+AqWVJRp3XFiuX/23inRAT6CtBPgKOFNHoGHYb8OHnHgtwA1Q0rVM6vf/OQonH+r W+gkVfKTOMs4AQJ3TGwHtpyr5/gNW8ba8DYE76u9BFU7tcbDUUilLmNmcItykl74VFwh DHxQ==
MIME-Version: 1.0
X-Received: by 10.236.167.105 with SMTP id h69mr6713360yhl.30.1400083897297; Wed, 14 May 2014 09:11:37 -0700 (PDT)
Received: by 10.170.75.136 with HTTP; Wed, 14 May 2014 09:11:37 -0700 (PDT)
In-Reply-To: <CF98C654.D3B54%sajassi@cisco.com>
References: <AC766891-B9AF-493A-A242-95D58BDC7069@ericsson.com> <CF98C654.D3B54%sajassi@cisco.com>
Date: Wed, 14 May 2014 12:11:37 -0400
Message-ID: <CAOA2mbyTFDESF5Wuyv8+mExPHF7xdxEcyXXDvkLMr_KkDQr49g@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=20cf303f6b725ab22804f95e6f1d
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/5kAxCa_dMjxeBjVh3I4VZlTIvjI
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 16:11:52 -0000

Btw should "in such scenerarios when" be "in such scenarios where" ?

On Wednesday, May 14, 2014, Ali Sajassi (sajassi) <sajassi@cisco.com> wrote:

>
>  Hi Jakob,
>
>  Changed your sentence to: "In such scenarios when the ARP entry times
> out and causes the MAC/IP to be withdrawn, then the MAC information will
> not be lost."
>
>  Cheers,
> Ali
>
>   From: Jakob Heitz <jakob.heitz@ericsson.com<javascript:_e(%7B%7D,'cvml','jakob.heitz@ericsson.com');>
> >
> Date: Wednesday, May 14, 2014 12:09 AM
> To: Cisco Employee <sajassi@cisco.com<javascript:_e(%7B%7D,'cvml','sajassi@cisco.com');>
> >
> Cc: Aldrin Isaac <aldrin.isaac@gmail.com<javascript:_e(%7B%7D,'cvml','aldrin.isaac@gmail.com');>>,
> John E Drake <jdrake@juniper.net<javascript:_e(%7B%7D,'cvml','jdrake@juniper.net');>>,
> "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
>
>   "Note that a MAC-only route can be advertised along with but
> independently of a MAC/IP route in scenarios where the MAC learning over
> the access network is done in the data-plane and independently of ARP
> snooping that generates the MAC/IP route. This ensures that if the ARP
> entry times out and causes the MAC/IP to be withdrawn, then the MAC
> information will not be lost. In scenarios where the host MAC/IP is learned
> via the management or control planes, the sender PE may advertise only the
> MAC/IP route."
>
> --
> Jakob Heitz.
>
>
> On May 13, 2014, at 11:22 PM, "Ali Sajassi (sajassi)" <sajassi@cisco.com>
> wrote:
>
>
>  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>
> Date: Tuesday, May 13, 2014 8:02 PM
> To: Cisco Employee <sajassi@cisco.com>
> Cc: John E Drake <jdrake@juniper.net>et>, Jakob Heitz <
> jakob.heitz@ericsson.com>gt;, "l2vpn@ietf.org" <l2vpn@ietf.org>rg>, Antoni
> Przygienda <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> 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>
> Date: Tuesday, May 13, 2014 11:14 AM
> To: Cisco Employee <sajassi@cisco.com>
> Cc: John E Drake <jdrake@juniper.net>et>, Jakob Heitz <
> jakob.heitz@ericsson.com>gt;, "l2vpn@ietf.org" <l2vpn@ietf.org>rg>, Antoni
> Przygienda <antoni.przygienda@ericsson.com>
> Subject: Re: MAC route with IP
>
>  Would it be worthwhile to mention that MAC/IP routes should no
>
>