Re: [lisp] Update Proposed CHarter

"Vina Ermagan (vermagan)" <vermagan@cisco.com> Tue, 05 January 2016 01:49 UTC

Return-Path: <vermagan@cisco.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 D290C1ACE46 for <lisp@ietfa.amsl.com>; Mon, 4 Jan 2016 17:49:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 BIURCtvhWBnD for <lisp@ietfa.amsl.com>; Mon, 4 Jan 2016 17:49:06 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17CE81ACE47 for <lisp@ietf.org>; Mon, 4 Jan 2016 17:49:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3686; q=dns/txt; s=iport; t=1451958546; x=1453168146; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ltXozePUCl/Lf8V9IZhGKsnSCAhKV+CMbbDeUoWnMGE=; b=fPRi2tsZLxbOlcm8zJBlq+kuG7J2pr/4cC4KHNf4y6u/Qb6lTUmTOQRa YqBcJgMsznTvJoAuZP9JrSAY6+f93qpr2sx3zDDYz4U3d022JaiJyRjTB StO1ZMWfr+6ojN37DmSLS9bYixYDyZesdgY5DrkkgUlZh3SSYqFiNimDe Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ABAgBpIItW/4YNJK1egzpSbQaIU7N3A?= =?us-ascii?q?Q2BZBgKhW0CgR44FAEBAQEBAQGBCoQ1AQEEAQEBZAcLEAIBCBgMIiEGCyUCBAE?= =?us-ascii?q?NBYgaAxIOvjoNgnQBAQEBAQEBAQEBAQEBAQEBAQEBAQEUBIZWhH+CT4ZtBY1zi?= =?us-ascii?q?RMBiDCDKIF4gVyERohZhViBCYdYASABAUKCFheBXXKECIEIAQEB?=
X-IronPort-AV: E=Sophos;i="5.20,523,1444694400"; d="scan'208";a="224368060"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 05 Jan 2016 01:49:04 +0000
Received: from XCH-ALN-017.cisco.com (xch-aln-017.cisco.com [173.36.7.27]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id u051n4u6000871 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 5 Jan 2016 01:49:04 GMT
Received: from xch-rcd-019.cisco.com (173.37.102.29) by XCH-ALN-017.cisco.com (173.36.7.27) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 4 Jan 2016 19:49:04 -0600
Received: from xch-rcd-019.cisco.com ([173.37.102.29]) by XCH-RCD-019.cisco.com ([173.37.102.29]) with mapi id 15.00.1104.009; Mon, 4 Jan 2016 19:49:04 -0600
From: "Vina Ermagan (vermagan)" <vermagan@cisco.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Sharon <sbarkai@gmail.com>, "Dino Farinacci" <farinacci@gmail.com>
Thread-Topic: [lisp] Update Proposed CHarter
Thread-Index: AQHRRu21HHJELY4k+UCUQcVryKwMOJ7sKLMAgAAwbgCAAAejAP//ploA
Date: Tue, 5 Jan 2016 01:49:04 +0000
Message-ID: <D2B03EE0.73463%vermagan@cisco.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>
In-Reply-To: <568AFBC2.2020103@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.3.140616
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.19.60.133]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <14BB5D935256434DA5CFA4F6AB76B31A@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/NYJDrrBl5Ffn8mWpO7M2L8woeng>
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: Tue, 05 Jan 2016 01:49:08 -0000

Hello Chairs,

Thanks for the text. One minor comment: in addition to Fabio's suggestion,
perhaps we can also include a wording that explicitly includes control
plane protocol extensions needed to accommodate the new mapping functions.
I have captures both additions in << >> below.

- Alternative Mapping System Design. By extending 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
and related security extensions, << or alternative transports of the LISP
control protocol >>).

Regarding the ordering of the list, I believe we should stay away from
officially prioritizing the list in the charter. Therefore I think we
should avoid numbering the list. I have no objection to re-arranging the
list in any order as long as it does not imply prioritization.

Best,
Vina

On 1/4/16 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
>
>_______________________________________________
>lisp mailing list
>lisp@ietf.org
>https://www.ietf.org/mailman/listinfo/lisp