[lisp] Proposed LISP WG Charter

Luigi Iannone <ggx@gigix.net> Fri, 15 January 2016 09:14 UTC

Return-Path: <ggx@gigix.net>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 8413D1A8AED for <lisp@ietfa.amsl.com>; Fri, 15 Jan 2016 01:14:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id nV6Ril4JRnBi for <lisp@ietfa.amsl.com>; Fri, 15 Jan 2016 01:14:33 -0800 (PST)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (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 8DD4C1A8AE8 for <lisp@ietf.org>; Fri, 15 Jan 2016 01:14:33 -0800 (PST)
Received: by mail-wm0-x22e.google.com with SMTP id l65so12030433wmf.1 for <lisp@ietf.org>; Fri, 15 Jan 2016 01:14:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gigix-net.20150623.gappssmtp.com; s=20150623; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version; bh=cUx/HWsIDPKRyiNwImS5/BFkh4eOlXuA+2uF/DQjo+Q=; b=NE1Q0YL3l+brtO00uF+v3HyEpdmQlND+ssUbL9Dw7+ITC/iq7ssZOHck6Xaw8F3mVh w1f8pNCnVbbAMbN6JdhRLkIQfk4B/0s9tLxXBs7CBC84RUIhfVSxO0x1rjiSxpys4IsT ifq1YDKiP3QTpKoGCHyPc4PPMjxvNzrudF/bE9j6TSjgJeh+7mibwTwBocyCyXXxgT8T MCBRQs+MaOR8QvzmDvW3zy55986RQ/ZdYPnofamsTBs8UYyHx5J7saZ/VF2JaJjvUlu4 zR97QfLmN1TQCA6G20uzF+uPNhCyA124A0t4QSMkGK9y/sBUoTfs9d8LGoNB35TWDwRY mm6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:content-transfer-encoding :subject:date:message-id:cc:to:mime-version; bh=cUx/HWsIDPKRyiNwImS5/BFkh4eOlXuA+2uF/DQjo+Q=; b=aRTEjjdE+SMjiIbOEVRTbsGScujt04UtK9yMWt2lTUVEnYAqzLOUAkyHecH0jckH5K H0B/zoU/4/WFCNuxQL4gSYQbXGfz54lG6IMyVcKvSRmZ52FyLLnGNURKknxrSYq+hMRo 3Djl7sS5CKqsQprEiLJ5eUO0FpNidh+imXRqZYoRcnzSeOjtKlf2u8Il33VEULdH80IV CeXiy08XZ1qTzrsyBsFq4A/sGDqAWDs6hWkf95M1Wz0187uQaA3WP0wNQ5mDauXA/pgb 56xsGi4Hr2uupBp8WjkxoADNdCx1SXjUES2FA2+gibFpzz9uptbs/TbqKUWC9lwShR1x Wagw==
X-Gm-Message-State: AG10YORqcFHxjKpvh8JPK0+LvP35I1MHQPJ4eKKTIKVyxmFDCzU8Pk+piVMNinND9nOILQ==
X-Received: by with SMTP id 190mr2260759wmw.54.1452849272144; Fri, 15 Jan 2016 01:14:32 -0800 (PST)
Received: from [] (napsach022.hosting-cea.net. []) by smtp.gmail.com with ESMTPSA id x10sm9708818wjx.8.2016. (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 15 Jan 2016 01:14:30 -0800 (PST)
From: Luigi Iannone <ggx@gigix.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Date: Fri, 15 Jan 2016 10:14:37 +0100
Message-Id: <EA0997EC-B945-41A3-A11E-98A5DB1C30E8@gigix.net>
To: "BRUNGARD, DEBORAH A" <db3546@att.com>, Joel Halpern Direct <jmh.direct@joelhalpern.com>
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/ZG1XksS6GxTQKCPpuePQEbG99Cs>
Cc: LISP mailing list list <lisp@ietf.org>
Subject: [lisp] Proposed LISP WG Charter
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jan 2016 09:14:35 -0000

Hi Deborah,

The LISP WG had a final round of discussion (on the mailing list) 
earlier this month on the new proposed charter.

Hereafter you can find the outcome.
This version includes all items the WG is ready to work on.




%%%%%%%% LISP WG PROPOSED CHARTER %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

The LISP WG has completed the first set of Experimental RFCs describing the Locator/ID Separation Protocol (LISP). LISP supports a routing architecture which decouples the routing locators and identifiers, thus allowing for efficient aggregation of the routing locator space and providing persistent identifiers in the identifier space. LISP requires no changes to end-systems or to routers that do not directly participate in the LISP deployment. LISP aims for an incrementally deployable protocol. The scope of the LISP techology is recognized to range from unicast and multicast overlays at Layer 2 as well as at Layer 3, including NAT traversal, VPNs,  and supporting mobility as a general feature, independently of wheter it is a mobile user or a migrating VM, hence being applicable in both Data Centers and public Internet environments.

The LISP WG is chartered to continue work on the LISP base protocol with the main objective to develop a standard solution based on the completed Experimental RFCs and the experience gained from early deployments.

This work will include reviewing the existing set of Experimental RFCs and doing the necessary enhancements to support a base set of standards track RFCs. The group will review the current set of Working Group documents to identify potential standards-track documents and do the necessary enhancements to support standards-track. It is recognized that some of the work will continue on the experimental track, though the group is encouraged to move the documents to standards track in support of network use, whereas the work previously was scoped to experimental documents.

Beside this main focus, the LISP WG work on the following items:

·       Multi-protocol support: Specifying the required extensions to support multi-protocol encapsulation (e.g.,   L2 or NSH – Network Service Headers). Rather than developing new encapsulations the work will aim at using existing well-established encapsulations or emerging from other Working Grops such as  NVO3 and SFC.  

·       Alternative Mapping System Design. By extenting LISP with  new protocols support it is also necessary to develop the required mapping function and control plane extensions to operate LISP map-assisted  networks (which might include Hierarchical Pull, Publish/Subscribe, or Push models, independent mapping systems interconnection, security extensions, or alternative transports of the LISP control protocol).

·       Mobility

·       Multicast: Support for overlay multicast by means of replication as well as interfacing with existing underlay multicast support.

·       Data-Plane Encryption

·       NAT-Traversal

·       Models for managing the LISP protocol and deployments that include data models, as well as allowing for programmable management interfaces. These managament methods should be considered for both the data-plane, control-plane, and mapping system components.