RE: MAC route with IP

Jakob Heitz <jakob.heitz@ericsson.com> Wed, 14 May 2014 17:20 UTC

Return-Path: <jakob.heitz@ericsson.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 CF1301A0323 for <l2vpn@ietfa.amsl.com>; Wed, 14 May 2014 10:20:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 dM3pvARtt9Mf for <l2vpn@ietfa.amsl.com>; Wed, 14 May 2014 10:20:06 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 4C0291A032B for <l2vpn@ietf.org>; Wed, 14 May 2014 10:20:04 -0700 (PDT)
X-AuditID: c618062d-f79c96d000001cfc-d8-5373565c47f7
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id A8.82.07420.C5653735; Wed, 14 May 2014 13:41:16 +0200 (CEST)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.03.0174.001; Wed, 14 May 2014 13:19:55 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: 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: Ac9tnTVAaQfHHQKqR0C1MGMVDrT48///65IA///deaD//7hWkIACA6eA//8w+kAAMBG6gP//3aLA///WaoD//4r38P//LYQA//434xD//I4AAP/4sfYA//Fe5YD/4i9hAP/EJsOA/4iDnNH/EE6MAP4gex+A/EEmkiA=
Date: Wed, 14 May 2014 17:19:55 +0000
Message-ID: <2F3EBB88EC3A454AAB08915FBF0B8C7E03057CEE@eusaamb109.ericsson.se>
References: <AC766891-B9AF-493A-A242-95D58BDC7069@ericsson.com> <CF98C654.D3B54%sajassi@cisco.com> <CAOA2mbyTFDESF5Wuyv8+mExPHF7xdxEcyXXDvkLMr_KkDQr49g@mail.gmail.com>
In-Reply-To: <CAOA2mbyTFDESF5Wuyv8+mExPHF7xdxEcyXXDvkLMr_KkDQr49g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.10]
Content-Type: multipart/alternative; boundary="_000_2F3EBB88EC3A454AAB08915FBF0B8C7E03057CEEeusaamb109erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjkeLIzCtJLcpLzFFi42KZXLonVjcmrDjY4Op1FYuZu1tZLObcdbZ4 /O0Qu8W7s80sDiweU35vZPXYOesuu8eSJT+ZPK43XWUPYInisklJzcksSy3St0vgyvjY85St 4NAtxoqlr5eyNTA+uMLYxcjJISFgInF9730WCFtM4sK99WxdjFwcQgJHGSUuPt4F5SxnlHg/ 5zkTSBWbgI7Et+tdzCC2iECExPbbTUBxDg5mgTqJljNZIGFhATmJzx1HmSBK5CUaf6xlBZkj IrCJUWLh79usIAkWAVWJGWv7wYp4BXwlpuz9yQixbDWjxKxVR8EWcAoEStzqOM0OYjMCnff9 1BqwBmYBcYlbT+YzQZwtILFkz3lmCFtU4uXjf6wQtpLEpKXnWCHq8yVmf7zHCLFMUOLkzCcs ExhFZyEZNQtJ2SwkZbPAftOUWL9LH6JEUWJK90N2CFtDonXOXHZk8QWM7KsYOUqLU8ty040M NjECI/CYBJvuDsY9Ly0PMQpwMCrx8CaoFgULsSaWFVfmHmKU5mBREuct+BIbLCSQnliSmp2a WpBaFF9UmpNafIiRiYNTqoGxJrZ0z+GqC6V7ve8cLbvsGa7GUMnqZ3znR/UDNtWJDELubnfb SjiV3D/N6rKd9k7kgorkZHfR6R4LJO0KmVYYans4/i4xs/Hf+Uqp1PBn+WeWUJVUacujMQfX tKaayHz4MfN5+yxjuXJnZUGef585i/5Ia71jjQp7/jOqZY9d2Rq3Vsk6ayWW4oxEQy3mouJE AItjNGWhAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/DZTD3iUVdgU5UetZ7wyE-Hl2ALE
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 17:20:11 -0000

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; 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