Re: [Ila] [DMM] Fwd: New Version Notification for draft-herbert-ila-mobile-00.txt

Tom Herbert <tom@quantonium.net> Fri, 02 February 2018 00:57 UTC

Return-Path: <tom@quantonium.net>
X-Original-To: ila@ietfa.amsl.com
Delivered-To: ila@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BDC012E03A for <ila@ietfa.amsl.com>; Thu, 1 Feb 2018 16:57:41 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=quantonium-net.20150623.gappssmtp.com
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 XlOQOC7GJEvu for <ila@ietfa.amsl.com>; Thu, 1 Feb 2018 16:57:39 -0800 (PST)
Received: from mail-wr0-x22c.google.com (mail-wr0-x22c.google.com [IPv6:2a00:1450:400c:c0c::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B46DB126DED for <ila@ietf.org>; Thu, 1 Feb 2018 16:57:38 -0800 (PST)
Received: by mail-wr0-x22c.google.com with SMTP id i56so20944862wra.7 for <ila@ietf.org>; Thu, 01 Feb 2018 16:57:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quantonium-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=jv3Z7I0Z0mpe5YoX/lAmYkVDi8xbwpF5YY9zMmu3XI8=; b=ea84onrLJ0vfAFRIAztrY/vhQ4IdTbyzbB8ihdkNvuqJ628Y8IoqcN0s00S5LF31Yt huOkKwklwirVxKRux0Mzyq14SeRz38fnmwcFzcDeQk0q1lAysap6lgY8bAcz9rKGaxBC X6lJnzGl8DrjIRKdpiGDO5jVolr+If44sZw3ee8Qse06OillKUClNCZWLZ3TVFcxYyU4 ChO5FiMEm6vQBBKj+4dFckWPlctYViZEO6awj3dc6eU0O5nxYSRe2RqSAScmUQhhsSU4 rtOO7HIze0gH2i7CyXCrP3vt/vj1bw2URmA4JEw+95Hh3B6w7gXuBBJulIJiFAf1XmuA G5sg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=jv3Z7I0Z0mpe5YoX/lAmYkVDi8xbwpF5YY9zMmu3XI8=; b=XDR/PxK/MtvuRyy9RFCWxp3nAlO+d3S94WpdMCs7fYrxJVpGU8tQpaEnH1qzEg9S22 p/bVirezHN1FGIAxFKEkWRJWm5fUdZh/ruGf7Gq8irMtew+lIKQaVIMb2FzrfUfsem70 biuDA0Xcgtq/XghIwpRf5+H4ufAC3Vtc0bG5wA5QS+NgYC79pQu4VQmBcCtCpDdSWF9D gMkc+kZzP2L5jGBPWp12Hy1GVvKqz+pEhkh5ymfaue+ZMMZPWvZW67HQ+NUBYJVQfIZ4 bjpOFwCwNX/SvIIbWF4ewNISIrX2B0VNwneXeK382PcSpAuAvqfgGgOlepr3Rk8BZUw8 je3g==
X-Gm-Message-State: AKwxyteX5w6F7geQc5WXo6131nE6S4DtCXA9kzM8vA/V4E3KMhifFy82 Kz4PLgaMaoaBjjgPGyXgQhzfAm2hVUpfWf0Ng5RpBQ==
X-Google-Smtp-Source: AH8x226b/8uLrGGp8209NZ4oFOJlzuoHoUSUgSjZha+Jr0Jtx47DkpC3lLI3ieIbGnpWkijfLsE+uFmG0UyPyr6/PWc=
X-Received: by 10.223.130.234 with SMTP id 97mr13984050wrc.144.1517533057185; Thu, 01 Feb 2018 16:57:37 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.173.66 with HTTP; Thu, 1 Feb 2018 16:57:36 -0800 (PST)
In-Reply-To: <D698F0A8.2A3953%sgundave@cisco.com>
References: <151750859755.24445.6929673804211867286.idtracker@ietfa.amsl.com> <CAPDqMerbX4UJ-mK-A-f=im=1h0Yz-52QfWLLgVDkybtSShNp5Q@mail.gmail.com> <D698D3B3.2A3906%sgundave@cisco.com> <D43DF85C-75F6-445B-895F-D27CE3285061@gmail.com> <D698E00C.10A01%sgundave@cisco.com> <51809684-7D19-4498-83CF-AB0C2FF678EF@gmail.com> <D698F0A8.2A3953%sgundave@cisco.com>
From: Tom Herbert <tom@quantonium.net>
Date: Thu, 01 Feb 2018 16:57:36 -0800
Message-ID: <CAPDqMerzsK65JnDgUhT7Q-h-zC_R4686QkWCGfJnDEDoEgVfVw@mail.gmail.com>
To: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
Cc: Dino Farinacci <farinacci@gmail.com>, dmm <dmm@ietf.org>, "ila@ietf.org" <ila@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ila/2PUgCcrv14IfVJ2HpfHbFwuLMq0>
Subject: Re: [Ila] [DMM] Fwd: New Version Notification for draft-herbert-ila-mobile-00.txt
X-BeenThere: ila@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Identifier Locator Addressing <ila.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ila>, <mailto:ila-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ila/>
List-Post: <mailto:ila@ietf.org>
List-Help: <mailto:ila-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ila>, <mailto:ila-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Feb 2018 00:57:42 -0000

On Thu, Feb 1, 2018 at 4:38 PM, Sri Gundavelli (sgundave)
<sgundave@cisco.com> wrote:
>> One thing to add. LISP has a more mature control-plane mapping system.
>>ILA has a recent proposal for its control-plane.
>
> Mobility architectures started with a unified CP/UP approach, then the
> industry thought its a great idea to move the Control-plane out, and
> reduce the state in the User-plane, and eliminate tunnels. Now, we want to
> eliminate the tunnels, but we need a new control protocol to manage the
> binding tables, and manage the complex cache states. Wondering, what¹s
> wrong with this picture?  What de we name this new CUPS architecture?
>
Sri,

Bear in mind that "industry" has different meanings depending on the
context. For ILA, and probably for LISP, the intent is to build a
generic protocol that can be used across variety of use cases in the
networking industry which hasn't uniformly adopted CUPS. It's pretty
obvious that we'd want to leverage a single data plane control plane
for these (isn't that the point of generic protocols :-) ). The CUPS
actually architecture helps a lot here by creating a clean well
abstracted interface that should make it straightforward to adapt an
ILA control plane. I think our architecture where we define ILA as an
NF reflects that.

Tom

>
> Sri
>
>
> (with no chair hat)
>
>