RE: MAC route with IP

Linda Dunbar <linda.dunbar@huawei.com> Wed, 14 May 2014 19:33 UTC

Return-Path: <linda.dunbar@huawei.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 48CD21A0146 for <l2vpn@ietfa.amsl.com>; Wed, 14 May 2014 12:33:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Level:
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 tAxkecUELX8s for <l2vpn@ietfa.amsl.com>; Wed, 14 May 2014 12:33:16 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 755231A00D5 for <l2vpn@ietf.org>; Wed, 14 May 2014 12:33:15 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BGT87535; Wed, 14 May 2014 19:33:04 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 14 May 2014 20:32:26 +0100
Received: from DFWEML704-CHM.china.huawei.com (10.193.5.141) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 14 May 2014 20:33:02 +0100
Received: from DFWEML701-CHM.china.huawei.com ([169.254.1.127]) by dfweml704-chm.china.huawei.com ([169.254.6.56]) with mapi id 14.03.0158.001; Wed, 14 May 2014 12:32:58 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Jakob Heitz <jakob.heitz@ericsson.com>, Aldrin Isaac <aldrin.isaac@gmail.com>, "Ali Sajassi (sajassi)" <sajassi@cisco.com>
Subject: RE: MAC route with IP
Thread-Topic: MAC route with IP
Thread-Index: AQHPbyDoaQfHHQKqR0C1MGMVDrT485tAEOWAgAAM+ACAAHWeAIAAIfmAgAATFYD//69u0A==
Date: Wed, 14 May 2014 19:32:58 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645D09BE9@dfweml701-chm.china.huawei.com>
References: <AC766891-B9AF-493A-A242-95D58BDC7069@ericsson.com> <CF98C654.D3B54%sajassi@cisco.com> <CAOA2mbyTFDESF5Wuyv8+mExPHF7xdxEcyXXDvkLMr_KkDQr49g@mail.gmail.com> <2F3EBB88EC3A454AAB08915FBF0B8C7E03057CEE@eusaamb109.ericsson.se>
In-Reply-To: <2F3EBB88EC3A454AAB08915FBF0B8C7E03057CEE@eusaamb109.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.155]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F645D09BE9dfweml701chmchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/8su3X-bUVKijRSX8mWsJG6EWq2c
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, 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: Wed, 14 May 2014 19:33:19 -0000

Isn’t it same as “Sticky MAC” or “Persistent MAC Learning”?

Linda

From: L2vpn [mailto:l2vpn-bounces@ietf.org] On Behalf Of Jakob Heitz
Sent: Wednesday, May 14, 2014 12:20 PM
To: Aldrin Isaac; Ali Sajassi (sajassi)
Cc: l2vpn@ietf.org; Antoni Przygienda
Subject: RE: MAC route with IP

I would be more inclined to put a comma after when:
"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,
Jakob.

From: Aldrin Isaac [mailto:aldrin.isaac@gmail.com]
Sent: Wednesday, May 14, 2014 9:12 AM
To: Ali Sajassi (sajassi)
Cc: Jakob Heitz; John E Drake; l2vpn@ietf.org<mailto:l2vpn@ietf.org>; Antoni Przygienda
Subject: Re: MAC route with IP

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

On Wednesday, May 14, 2014, Ali Sajassi (sajassi) <sajassi@cisco.com<mailto: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<mailto: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<mailto:aldrin.isaac@gmail.com>>
Date: Tuesday, May 13, 2014 8:02 PM
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

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<mailto: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<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 no