Re: [lisp] Update Proposed CHarter

Stefano Secci <stefano.secci@lip6.fr> Mon, 04 January 2016 22:47 UTC

Return-Path: <stefano.secci@lip6.fr>
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 B927A1ACC86 for <lisp@ietfa.amsl.com>; Mon, 4 Jan 2016 14:47:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.338
X-Spam-Level:
X-Spam-Status: No, score=0.338 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 023vuSTG2NKu for <lisp@ietfa.amsl.com>; Mon, 4 Jan 2016 14:47:01 -0800 (PST)
Received: from osiris.lip6.fr (osiris.lip6.fr [132.227.60.30]) by ietfa.amsl.com (Postfix) with ESMTP id 917861AC410 for <lisp@ietf.org>; Mon, 4 Jan 2016 14:47:00 -0800 (PST)
Received: from tibre.lip6.fr (tibre.lip6.fr [132.227.74.2]) by osiris.lip6.fr (8.15.1/lip6) with ESMTP id u04MkwYb025928 for <lisp@ietf.org>; Mon, 4 Jan 2016 23:46:58 +0100 (CET)
X-pt: osiris.lip6.fr
Received: from [192.168.1.42] (bre75-4-78-194-65-24.fbxo.proxad.net [78.194.65.24]) (authenticated bits=0) by tibre.lip6.fr (8.15.1/8.14.7) with ESMTPSA id u04MkwpH018455 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <lisp@ietf.org>; Mon, 4 Jan 2016 23:46:58 +0100 (MET)
From: Stefano Secci <stefano.secci@lip6.fr>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5B4631D2-8DAC-44D2-9129-28903DAFBFCB"
Message-Id: <91600CE8-B881-4947-BEB2-E04486FBE566@lip6.fr>
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
Date: Mon, 4 Jan 2016 23:46:58 +0100
References: <mailman.9.1451937602.20775.lisp@ietf.org>
To: lisp@ietf.org
In-Reply-To: <mailman.9.1451937602.20775.lisp@ietf.org>
X-Mailer: Apple Mail (2.1993)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (osiris.lip6.fr [132.227.60.30]); Mon, 04 Jan 2016 23:46:58 +0100 (CET)
X-Scanned-By: MIMEDefang 2.75 on 132.227.60.30
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/J2NPRxuwDUE7JCygjwYHrPbnhFE>
Subject: Re: [lisp] Update Proposed 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: Mon, 04 Jan 2016 22:47:02 -0000

Hi WG,

the text looks ok to me and fully agree with Dino's order of preference/importance.

Just a comment for current point 7 - it might be worth being more explicit on independent mapping system interconnect / inter-domain mapping system issues.

Cheers,
Stefano

>> If the text looks good for you, please state so in the mailing list.
> 
> I am fine with the text. But I have one comment about sequencing the list below. Can we sequence the list in order of generality or importance?
> 
> See inline comment below.
> 
>> Beside this main focus, the LISP WG work on the following items:
>> 
>> -       NAT-Traversal
>> 
>> -       Mobility
>> 
>> -       Data-Plane Encryption
>> 
>> -       Multicast: Support for overlay multicast by means of
>>       replication as well as interfacing with existing
>>       underlay multicast support.
>> 
>> -       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
>> 
>> -       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 extensions to
>>       operate LISP map-assisted  networks (which might
>>       include Hierarchical Pull, Publish/Subscribe, or Push
>>       models and related security extension).
> 
> I will number the above as 1 - 7 and feel they should be ordered in sequence:
> 
> 6, 7, 2, 4, 3, 1, 5
> 
> Dino

-- 
Stefano Secci
Associate Professor
Univ. Pierre and Marie Curie
LIP6 - Bureau 25-26/518, BC 169
4 place Jussieu, 75005 Paris, France
Tel:  +33 (0) 1 4427 3678
http://www-phare.lip6.fr/~secci