[Ila] BOF proposal draft
Tom Herbert <tom@quantonium.net> Fri, 02 February 2018 01:07 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 F135C126DED for <ila@ietfa.amsl.com>; Thu, 1 Feb 2018 17:07:47 -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=ham 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 oykHABnf4EMe for <ila@ietfa.amsl.com>; Thu, 1 Feb 2018 17:07:46 -0800 (PST)
Received: from mail-wr0-x229.google.com (mail-wr0-x229.google.com [IPv6:2a00:1450:400c:c0c::229]) (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 41604129C6D for <ila@ietf.org>; Thu, 1 Feb 2018 17:07:46 -0800 (PST)
Received: by mail-wr0-x229.google.com with SMTP id y3so11138006wrh.3 for <ila@ietf.org>; Thu, 01 Feb 2018 17:07:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quantonium-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc :content-transfer-encoding; bh=gvttYW7ZOghARB0M1RDgmxFnqoqbzUfVAu7xoHT9D4Q=; b=CPvJ4GfI0QCHvM58GM4qeN3A1J/nXdkjyRZxz2wrDrimcx4Mc8qNMDBvCMyq2lBluC BL5+aK5xLoyH/do+uMEKczjTdlb4yoB6dIldw2Miaqc7vRZ603l/pCfLfud6hcx1SFv8 aBpMMIRefWnpNETRjuETXvlFFPN66XYSj3HPP/UnUbfnWCVeb49NKPe+Jnw2UVBtqpCk dRMyxyCCMFynDOU0VI7+2Yr7VVCXHObZZXPoGvTSVIxx2K1vKR1OCYh5uUukhOT/FWdG 8h6KNz8aq4VUVwUlVs4vCowMLp3ob+csPEtRiJcAzj0EOEyk3kh5WlLa6/pgWbkpUDWQ uryQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc :content-transfer-encoding; bh=gvttYW7ZOghARB0M1RDgmxFnqoqbzUfVAu7xoHT9D4Q=; b=BnmJKxp7o9kHc+gP2Zh8y+KlDl5qC/5tcOOtkV7o0m+a7/JPMVlQltVX58cgrVyXK2 H8uPtSYfFNQ25LPbhUBvYdavbYwwSF3RQ89mLcF+fXaRrEoDDycUc04+sfPnygfsbI3T /rYXQ/PqJ4bes4QfDY+gXpLHlgtF6DBv7lKAi+ZsZORc4P5KC5sHq04XZJbO/XlBcBE1 iVJxiKmxgjks5+JYc/84DqFsw5Qx6i0v0kNLH4h23WoPjROXT2i0dCrJmpY0dvtChFfq xEMJxtgJUDUpvc4f9G+7WSbmq5fYtJ2qRqGrr9c7OhZAFCU+4mK3QpckozqH9jTVnx1j nusw==
X-Gm-Message-State: AKwxytd6Bbnr5POcyd3dF/4JCB8N8Vdz8TZEg1sqk2fjm3tnBifFip07 KaF0zKGS6gnDVzhd3osO9RsyaaLu5JvBgWgTztnk1+V5
X-Google-Smtp-Source: AH8x225SzhebqVRT0/ZcHE4QjFO+TT1fb3gXYTxWLQmA0WtUTikdDb9wc59n2YCUGTca9D43V7aH9Nx2jmKUvC5wl18=
X-Received: by 10.223.130.234 with SMTP id 97mr14001091wrc.144.1517533664663; Thu, 01 Feb 2018 17:07:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.173.66 with HTTP; Thu, 1 Feb 2018 17:07:44 -0800 (PST)
From: Tom Herbert <tom@quantonium.net>
Date: Thu, 01 Feb 2018 17:07:44 -0800
Message-ID: <CAPDqMeoLo+vv6ndx6y6nobsVXyb8-jr0cGKQGmMZ+mkz4R68YQ@mail.gmail.com>
To: ila@ietf.org
Cc: "Bogineni, Kalyani" <kalyani.bogineni@verizonwireless.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ila/mbjh0-h9nMVj--KF4GWqI7ED8wI>
Subject: [Ila] BOF proposal draft
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 01:07:48 -0000
Hello, Here is dome draft text for a BOF proposal description. Please comment! Thanks, Tom ----------------------------- The goal of this group is to standardize Identifier-Locator Addressing (ILA). The problem to be addressed by this group is how to provide network overlays with high efficiency, low latency, scaling to billions of users, seamless mobility, strong privacy and security guarantees, be interoperable with existing networks, be anchorless, be usable for a variety of use cases, and have simplified control and management. These requirements are being driven by a huge growth in number of connected devices, particularly IoT, as well as the emergence of next generation applications such as AR and VR that have stringent networking requirements. While there have been many solutions proposed and defined by IETF to provide network overlays, including countless variations of encapsulation, NAT, and segment routing-- we believe none of these have been shown meet all these requirements. ILA is a type of identifier/locator split that partitions an IPv6 address into two components. One part of an address expresses the immutable identity of a node, and another part indicates the topological location of a node which can be dynamic. ILA is a means to implement network overlays without the overhead or complexity of encapsulation or extension headers. ILA leverages the immense size of the IPv6 address space. In this regard, ILA bears similarity to Identifier-Locator Network Protocol (ILNP), however there are some major differences in protocol layer and the control plane. There are three primary use cases proposed for Identifier Locator Addressing: * Mobile user-plane * Datacenter virtualization * Network virtualization A recent trend in the industry is to build converged networks that contain all three of these use cases. In order to meet very low latency requirements and provide high availability, many mobile providers are housing data centers within their networks to run applications. Similarly, many providers also run cloud services within their network. A single networking solution with a common control plane is desirable. There are two aspects to ILA: a data plane and control plane. The data plane includes the ILA address transformation mechanism, checksum neutral handling, and ancillary protocol support (such as considerations of ICMP when ILA addresses are involved). A transformation is drive by a mapping lookup on an identifier to a locator. The control plane’s main focus is on the mapping system. There are two critical problems to be solved in a mapping system 1) scaling to support billions of entries 2) securing information in the mapping system which is inherently privacy sensitive data. The mapping system is essentially a key-value store database. There has been a lot of innovation in key-value store solutions over the past few years, one goal of this group will be to evaluate key-value solutions for providing the mapping system. This activity may leverage protocols and work from working groups within IETF including dmm, nvo3, lisp, 6man, and int-area. Additionally, work in other SDOs, particularly 3GPP, is relevant. Open source projects, particular work in key-value store technology and databases, are also relevant.
- [Ila] BOF proposal draft Tom Herbert
- Re: [Ila] BOF proposal draft Margaret Cullen
- Re: [Ila] BOF proposal draft Tom Herbert