Re: [lisp] Update Proposed CHarter

Luigi Iannone <> Wed, 06 January 2016 14:42 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 730B21B2C2E for <>; Wed, 6 Jan 2016 06:42:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id sCk77HtCfbdj for <>; Wed, 6 Jan 2016 06:42:23 -0800 (PST)
Received: from ( [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AA56C1A7035 for <>; Wed, 6 Jan 2016 06:42:22 -0800 (PST)
Received: by with SMTP id f206so78556184wmf.0 for <>; Wed, 06 Jan 2016 06:42:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Q5tJDIoOFomeoqkck5B4RnWK/socbfKgI8YViIR4Px4=; b=Qf4J8TgQwdtwx5ACZdkTF27dhyvUu/wsxz0dKdkzP6lqskAIk05DhC4cg9QzzGujn1 4MEjMSo/BaNOxeh+lPTOc2awhPTT00TZgW3G2jwdIMpE/FSl+husQCd+lWURcl9AdrYq 3wtumkUuygoLB3FfHbq+SpDlIDYrPWGfgoQ/wkl+EZiljR822/O4Ty5SzOgo0NUy25iX eLZ/qD48ZD1Ioww8ib5SnGwzeXb54Vi4nqk50A6unS9CUI9kxkOWNz10z/hKb55eXSh7 0im1p9T3DY6HIq6vu9u80U0bERQynTdD2C92mfpUWyTfPGQwCdIAE81GjOXRAm3eD2m5 7lVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; 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=Q5tJDIoOFomeoqkck5B4RnWK/socbfKgI8YViIR4Px4=; b=IaKkAkB2PbjnQAevTGtxL/phM2STL6qoLUR5awjEpVUydUknn4Xuozwxm5fEfv/BEV GhmnUUH1jaSwBDBHyn6c8c0ACAreOQfAdGhAG4EPEbmzmh6U9lvBay2Jk5WQiRBG2v55 CioXovkDvSfA+cC2Kg/1HIQAJ4MkTBsC1jUPmaxFcCt0PbfJm9r4Od0QA9ZZ1KDqJ2Pz JJN8T0XmeuOD3R5TU0/V4+ogkVcgKn3zbZ4yluUaHqgThoiKNDLyXw2URKlQQp2rQkbi BqXMyXfPvc6RocjMkQKfYQcV9HFsfLwU9R5K1rluHZmpLtqc3LNSGnwaIgogpzdIT9Fu SSvQ==
X-Gm-Message-State: ALoCoQmgTbxet+JCAFXMxk5S3eocALszB+DmWTgN5dsAcGZ5mog7l4AyNeMw0eX54Ag4LQoqdBeHE8kZUjl2MEVYoWS+8WR1UA==
X-Received: by with SMTP id d62mr10208543wma.35.1452091341237; Wed, 06 Jan 2016 06:42:21 -0800 (PST)
Received: from [] ( []) by with ESMTPSA id r10sm71971637wjz.24.2016. (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 06 Jan 2016 06:42:19 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Luigi Iannone <>
In-Reply-To: <>
Date: Wed, 6 Jan 2016 15:42:27 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <>
To: LISP mailing list list <>
X-Mailer: Apple Mail (2.3112)
Archived-At: <>
Cc: Joel Halpern Direct <>
Subject: Re: [lisp] Update Proposed CHarter
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 06 Jan 2016 14:42:24 -0000

Hi All,

Hereafter a new version of the charter with the comments received so far.

Please send more feedback. Would be good if we can send the charter to our AD by next week.




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, independednt 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.