Re: [lisp] Update Proposed CHarter

Dino Farinacci <farinacci@gmail.com> Mon, 04 January 2016 23:48 UTC

Return-Path: <farinacci@gmail.com>
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 6FEBE1ACD62 for <lisp@ietfa.amsl.com>; Mon, 4 Jan 2016 15:48:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 oSZGVVN9pfcn for <lisp@ietfa.amsl.com>; Mon, 4 Jan 2016 15:48:57 -0800 (PST)
Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) (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 9B4641ACD61 for <lisp@ietf.org>; Mon, 4 Jan 2016 15:48:57 -0800 (PST)
Received: by mail-pf0-x22a.google.com with SMTP id 65so164628707pff.3 for <lisp@ietf.org>; Mon, 04 Jan 2016 15:48:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=E99Dr80YYIODMSbfm4OZbb8QEv5A4ywovJ4wxY3MqFc=; b=ssEVlyiocq8A1PyUdu9V//kDxrU+mVm251oZLjWhWDyPci1aejG11qMY+cxVdQ0CIB KzsEqEFSHV8vKUUQh37fT2e8V/tWlKWd+ZtLI5kFQ0cHLijHVAtlvS+AT+MHt+vmTJgY zvGWEvjirntKL+rc1COOIW5bGQQ7BC8rKNlG1qM1Z7FcSmuYS+aITM2LBtSlIvuBMC07 ePO3MYvm/xw09jGIFNfKRf7tbk3+XojlO8vz8MDmC4IinKUtZnXK+yuAsJc+AmeLk6eY 5/uK+nF+DJjGa0s2AxOPn8Z1FwZj/CbpphszZ2Qhnx7SlmCS/5ymBrrSPtyaC/YHNaIq JlIA==
X-Received: by 10.98.68.68 with SMTP id r65mr81376521pfa.108.1451951337361; Mon, 04 Jan 2016 15:48:57 -0800 (PST)
Received: from [10.197.31.157] (173-11-119-245-SFBA.hfc.comcastbusiness.net. [173.11.119.245]) by smtp.gmail.com with ESMTPSA id tm4sm128705464pab.3.2016.01.04.15.48.55 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 04 Jan 2016 15:48:56 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <568AFBC2.2020103@joelhalpern.com>
Date: Mon, 4 Jan 2016 15:48:53 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B534411C-1DD9-4378-9619-518A39000EEC@gmail.com>
References: <08A51E69-008C-4DBE-9707-996468F46FC3@gigix.net> <8EB52655-5FF5-44DE-A286-D79E4BB423B2@gmail.com> <AF133C2D-5627-408F-8B42-BA4E7E3FA5E3@gmail.com> <568AFBC2.2020103@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/xNIUS_kyMXHEqJWIcADyIMbEvPY>
Cc: LISP mailing list list <lisp@ietf.org>
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 23:48:59 -0000

I should have NOT said in “order of importance”. It is in order of more general to specific features. They are all important and a bullet at the end is not any less important or less priority than prior bullets.

Dino

> On Jan 4, 2016, at 3:09 PM, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> 
> And this is why I tend to prefer an un-ordered list.  But if the WG wants to try to agree on a prioritized list, go for it.
> 
> Yours,
> Joel
> 
> On 1/4/16 5:42 PM, Sharon wrote:
>> I agree with Dino, will pull up (1) though, it allows carriers to anchor access services in POPs where the MAO operations are based.
>> Cloud RAN, NFV, VPN .. type services.
>> 
>> --szb
>> 
>> On Jan 4, 2016, at 11:49 AM, Dino Farinacci <farinacci@gmail.com> wrote:
>> 
>>>> 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
>>> 
>>> _______________________________________________
>>> lisp mailing list
>>> lisp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/lisp