Re: [lisp] Proposed LISP WG Charter

Luigi Iannone <ggx@gigix.net> Wed, 20 January 2016 11:01 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E96E1B2A7A for <lisp@ietfa.amsl.com>; Wed, 20 Jan 2016 03:01:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level:
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HELO_EQ_FR=0.35, SPF_PASS=-0.001] autolearn=no
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 blk8B3bGwP01 for <lisp@ietfa.amsl.com>; Wed, 20 Jan 2016 03:01:05 -0800 (PST)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (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 7738C1B3A2C for <lisp@ietf.org>; Wed, 20 Jan 2016 03:01:05 -0800 (PST)
Received: by mail-wm0-x231.google.com with SMTP id 123so127663272wmz.0 for <lisp@ietf.org>; Wed, 20 Jan 2016 03:01:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gigix-net.20150623.gappssmtp.com; s=20150623; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=3w05BYNSlvENN8HVvKjr54LNnjbSjJyoj29/d6gTrjg=; b=w2RtksZuKAa1tE6euNLQIjGlNQhXjfto1W5Sd5uNxgu9e2xCP0yOHhVpUWVsQSB0lG bFjjONnQOSGPoFOWUKb5rRbUpTSb6vIzTtdcUI9pohHaAeswdpJ2gUp/xg5USlmEhbYE sIY1l0lW1F8RdtteQ7GZElsh+sETYnDUD7SxaHpY/Eipnj5nzlFLLd4jql31sGZ3QidG 9xUg1gygc7GozgwbsHn2Ye34RglOzRDPaOST6xbhP7Oj+j1rEbSB7fr2dHiPE/G0O8P8 hIUaK1YMUsknRswzBY8SNVtrhTvZ2uot7iQvxjJNqt6faQQinHTc8btlf0JPC/2TEaO/ zryQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=3w05BYNSlvENN8HVvKjr54LNnjbSjJyoj29/d6gTrjg=; b=F+rCt4bLGFexF+2lSKuuzTwBAwu3aGf4p9Ny37hZLXODTtzzNGWDptn0nFLl3L+1Ej /DxRoowImCegfu+UgHPYmPRsdPn9roEuIwqHGWR7vqKJXx/W1aX1N3exav4NX/CMkLPX sbtinSfvCytq7J08BuA1nd0gbk2GhX6qK4xpKIn2Had+ZA20w0K3QjN3JfWmhKdrtjAM mbGUbtaFZWri+/KHOYJfqIfclxOLKCM2NqoaqSQDWaF1TfvN64KQvNhEH77zmemgW3f8 F8pNtUkaio0uJoPqf73Crc+zftMtDqSn7ko5o07q+Om6wJmYnkmI73HIoMDFhHZk8l9w tDew==
X-Gm-Message-State: AG10YOQS+SLwOfZktAFlESZX4Fas0XjDtu7oER7GYR4YNuJA0vA668C2PQkjNwIpJGmmLg==
X-Received: by 10.28.228.87 with SMTP id b84mr3146563wmh.81.1453287664076; Wed, 20 Jan 2016 03:01:04 -0800 (PST)
Received: from dhcp164-132.enst.fr (dhcp164-132.enst.fr. [137.194.165.132]) by smtp.gmail.com with ESMTPSA id 73sm24554346wmm.7.2016.01.20.03.01.02 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 20 Jan 2016 03:01:03 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <F64C10EAA68C8044B33656FA214632C8527DC7F2@MISOUT7MSGUSRDE.ITServices.sbc.com>
Date: Wed, 20 Jan 2016 12:01:06 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C7AB49B7-05FE-4388-A7F7-BCD8F2E4830F@gigix.net>
References: <EA0997EC-B945-41A3-A11E-98A5DB1C30E8@gigix.net> <F64C10EAA68C8044B33656FA214632C8527DC7F2@MISOUT7MSGUSRDE.ITServices.sbc.com>
To: "BRUNGARD, DEBORAH A" <db3546@att.com>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/HOMUsQTVA_fk7DaxOzEQ6kvi6S4>
Cc: Joel Halpern Direct <jmh.direct@joelhalpern.com>, LISP mailing list list <lisp@ietf.org>
Subject: Re: [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: Wed, 20 Jan 2016 11:01:09 -0000

This can be surely be done.

Will update the proposed charter before the end of the week.

ciao

L.


> On 19 Jan 2016, at 23:58, BRUNGARD, DEBORAH A <db3546@att.com> wrote:
> 
> Hi Luigi,
> 
> Looks good - can you add a few words to scope better the three bullet items: mobility, data-plane encryption, NAT-Traversal?
> 
> Thanks,
> Deborah
> 
> 
> -----Original Message-----
> From: Luigi Iannone [mailto:ggx@gigix.net] 
> Sent: Friday, January 15, 2016 4:15 AM
> To: BRUNGARD, DEBORAH A <db3546@att.com>om>; Joel Halpern Direct <jmh.direct@joelhalpern.com>
> Cc: LISP mailing list list <lisp@ietf.org>
> Subject: Proposed LISP WG Charter
> 
> 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.
> 
> thanks
> 
> ciao
> 
> Luigi
> 
> 
> %%%%%%%% 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.
>