Re: [lisp] Update Proposed CHarter

Sharon <sbarkai@gmail.com> Mon, 04 January 2016 22:42 UTC

Return-Path: <sbarkai@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 356481AC442 for <lisp@ietfa.amsl.com>; Mon, 4 Jan 2016 14:42:40 -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 uvf8kjss_Pln for <lisp@ietfa.amsl.com>; Mon, 4 Jan 2016 14:42:38 -0800 (PST)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (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 6E3A91A1AA8 for <lisp@ietf.org>; Mon, 4 Jan 2016 14:42:38 -0800 (PST)
Received: by mail-pa0-x233.google.com with SMTP id yy13so111328481pab.3 for <lisp@ietf.org>; Mon, 04 Jan 2016 14:42:38 -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:cc:date :content-transfer-encoding:message-id:references:to; bh=sv82E+JaC88OKI4N1/pf3JSOZ0kA5fvf6S9ydwvnGQ8=; b=OcoCnU+4LnIH5Bx9R0nGz35tlP4XvM1gRnsN9SF5n4hCuT8L7++myJqb8PamOfyWfw 6ufjKw7ynsTtUTX8A8tQTXLNHHUZU8EKCrKtfG6hBYhPHKlL/9wHrbwKiMgsR3bjItRx CxS2SgCwTDyYELo++AwGlp7H6hpKMJXJu8Ns0yBhyQuFr+BNPGFCBqgvVoBoCMFOjxjq i5vXSp0mI1KKaUp4EiBs6G0C6SdJqZ1JlJDRRCca6yzQTw6Rmc5cWrW5YBP+M9Db+JQD Evzq+udGh2LIUmgEQAoclCICoNCv4XtjT2XXSqZ1l588lAjK7HMpsMrPnviXr3b0GrW/ fjqg==
X-Received: by 10.67.3.196 with SMTP id by4mr128651394pad.67.1451947358046; Mon, 04 Jan 2016 14:42:38 -0800 (PST)
Received: from ?IPv6:2600:1010:b057:3db2:5c6e:fa8f:d04c:3220? ([2600:1010:b057:3db2:5c6e:fa8f:d04c:3220]) by smtp.gmail.com with ESMTPSA id d86sm123243872pfj.85.2016.01.04.14.42.35 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Jan 2016 14:42:36 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Sharon <sbarkai@gmail.com>
X-Mailer: iPhone Mail (13C75)
In-Reply-To: <8EB52655-5FF5-44DE-A286-D79E4BB423B2@gmail.com>
Date: Mon, 4 Jan 2016 14:42:34 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <AF133C2D-5627-408F-8B42-BA4E7E3FA5E3@gmail.com>
References: <08A51E69-008C-4DBE-9707-996468F46FC3@gigix.net> <8EB52655-5FF5-44DE-A286-D79E4BB423B2@gmail.com>
To: Dino Farinacci <farinacci@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/1BAZgQpoDGgyqoAEYus5ZO2ijz4>
Cc: Joel Halpern Direct <jmh.direct@joelhalpern.com>, 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 22:42:40 -0000

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