Re: [Ideas] Your Input requested: Charter Proposal New Version

Padma Pillay-Esnault <padma.ietf@gmail.com> Mon, 07 August 2017 20:24 UTC

Return-Path: <padma.ietf@gmail.com>
X-Original-To: ideas@ietfa.amsl.com
Delivered-To: ideas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2B77132355 for <ideas@ietfa.amsl.com>; Mon, 7 Aug 2017 13:24:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 8lG6Qy-cS8wx for <ideas@ietfa.amsl.com>; Mon, 7 Aug 2017 13:24:34 -0700 (PDT)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (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 543C0132381 for <ideas@ietf.org>; Mon, 7 Aug 2017 13:24:34 -0700 (PDT)
Received: by mail-qk0-x22f.google.com with SMTP id d145so9188079qkc.2 for <ideas@ietf.org>; Mon, 07 Aug 2017 13:24:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=z6O6R+NzHhyxwqN715589I8c0IjoAPEPdwWSe5SOGJw=; b=jAND33C+El7n2JP59CqmpecGfDsoKaGtVvf4+C6NEjRpTzGZkG5oSacL4xRvSvrLum hTEsTN+WjnsGSFDYep5KEeKyLJs+C1ff0hsYyaLZPlzKhIgy6Hn4Vq9HmMaYsdQ+SNWh EC6Twf6LZwNPxvlikOBA86ApSH0Jf80cW3tFP9Me7x2iIi3XN3mPN6syPfV/T8XhbjwM 0J4+yguOEDJDfvw9AwecPI0/gCE9bTHLj6GMFkfGQkWg4uB1PkNB+BXFBv5Ejan7Ph7e RzzkRRIzGCSZ3ThFbzkfNXUco6jQRPCThjpjv3mpxbopo+s8y3DL24Jnm/j4LKaNcGPE BcyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=z6O6R+NzHhyxwqN715589I8c0IjoAPEPdwWSe5SOGJw=; b=o2FQ8EQO3vgx2QAItyVF41OaOX+YLxMHsR3bcVRjX120+ujmrnpnmjNaunVtN8DIsZ l5duyN/kwbIk0NWcb9olnxueLgAP3jmXjwf/H0xLhqjfCvhjK7/RVi5rpJw/N7YPwDiA v8sjHyQYYM2tzPYCXU8FZuBK49VEP4ie+KuNZKrJ0ITTl8nWSTNYnb7QS8TMRC51Mj2k QJrE4UJGQT2zMwNeAoO5sdPSksxtwAgRYy1cn2ZM4Z6LRu4ej7p40jdGWomlpidCSF6z DafoMoQ36F9YmYEhQr6ex622mHjUpNwmUNzn3ZYHUiMCaMMOPhAS1ZDX6615lcO7UWa/ zjvg==
X-Gm-Message-State: AHYfb5ikbzk8JR8OVI+AbYvNjuNW0YtlKt5yOsxGSig0nlNKTdK/omT/ IEFk1lUcsPx6ocZZYTCzQoqjyTVK8w==
X-Received: by 10.55.162.210 with SMTP id l201mr2640195qke.180.1502137473370; Mon, 07 Aug 2017 13:24:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.43.199 with HTTP; Mon, 7 Aug 2017 13:24:32 -0700 (PDT)
In-Reply-To: <83622B5F-A2D0-40A4-BD75-BC6222754059@telefonica.com>
References: <CAG-CQxpxDXxLXdu0a2GdBRfTFLM_C+jqCz58HoNim52C7Yzr8g@mail.gmail.com> <CALx6S34hbV5D84RZQ1+V3zFz+VNeJsDn0rsr-PN6Wg4b1gdSpA@mail.gmail.com> <83622B5F-A2D0-40A4-BD75-BC6222754059@telefonica.com>
From: Padma Pillay-Esnault <padma.ietf@gmail.com>
Date: Mon, 07 Aug 2017 13:24:32 -0700
Message-ID: <CAG-CQxrWxUe2bTBe-OJTHsw9Wmcupg2fRX=c+jQrMNgRqsudXg@mail.gmail.com>
To: "Diego R. Lopez" <diego.r.lopez@telefonica.com>
Cc: Tom Herbert <tom@herbertland.com>, "ideas@ietf.org" <ideas@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ideas/AjquPGElHvBAWhqADzT2e7yRZPQ>
Subject: Re: [Ideas] Your Input requested: Charter Proposal New Version
X-BeenThere: ideas@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussions relating to the development, clarification, and implementation of control-plane infrastructures and functionalities in ID enabled networks." <ideas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ideas>, <mailto:ideas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ideas/>
List-Post: <mailto:ideas@ietf.org>
List-Help: <mailto:ideas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ideas>, <mailto:ideas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Aug 2017 20:24:37 -0000

Hi Diego

Thanks for the pointer.

Padma

Sent from my iPhone

> On Aug 7, 2017, at 08:57, Diego R. Lopez <diego.r.lopez@telefonica.com> wrote:
>
> Hi,
>
>
> On 7/8/2017, 17:23, "Ideas on behalf of Tom Herbert" <ideas-bounces@ietf.org on behalf of tom@herbertland.com> wrote:
>
>    On Sun, Aug 6, 2017 at 10:20 PM, Padma Pillay-Esnault
>    <padma.ietf@gmail.com> wrote:
>> Dear IDEAS,
>>
>> Thanks to everyone who sent their comments and feedback both on the list and
>> off the list.
>>
>> This new version should address comments from:
>> -  Michael Menth. Michael, please let us know if this revision address some
>> of your comments on clarity.
>> - Alex Clemm. Alex , please chime on the revision regarding your addition.
>> - Tom Herbert. Tom, Some of your suggestions are incorporated in this
>> version.
>> -Tom and Alex, this version include specific working that the framework is
>> modular. The set of areas to be covered has been reordered to put the basic
>> identifier protocol common infrastructure first and then the new identity
>> concept and functionalities.
>> - Georgios Karagiannis, Uma Chundhuri. Georgios, Uma, there is still an
>> ongoing discussion about the framework. This version is flexible enough to
>> accommodate the work to be done on defining the framework.
>> - Uma Chundhuri. Uma, the pub/sub reference should cover the inter-grids
>> aspect if needed.
>>
>> Please find the new version below:
>>
>> IDEAS: “IDentity EnAbled networkS”
>>
>>
>>
>> Proposed Charter
>>
>>
>>
>> Network solutions based on the concept of Identifier-Locator separation are
>> increasingly considered to support mobility and multi-homing across
>> heterogeneous access networks. Identifier-locator separation protocols
>> require infrastructure that allows nodes to discover the network topological
>> location(s) of its peer(s) for packet delivery. A common infrastructure and
>> protocol could be used by identifier/locator protocols as well as network
>> virtualization. However, additional infrastructure and new protocol
>> extensions are needed to address new requirements that go well beyond the
>> traditional discovery service and mapping of identifier-to-location for
>> packet delivery.
>>
>>
>>
>> At the same time, end users require greater privacy for their networking
>> information and protection from outside threats, while operators demand
>> greater operational efficiency. Identity-enabled networks aim to enable
>> networking applications and services that provide a high degree of privacy
>> and control of end points over their networking data, coupled with greater
>> inherent security than provided by today’s networks.
>>
>>
>>
>> To this end, the working group shall:
>>
>> - define a framework for the development of an identifier/locator mapping
>> system that provides a common solution for all identifier/locator mapping
>> protocols and network virtualization.
>>
>>
>>
>> - in addition, introduce the concept of identity-identifier split and new
>> mechanisms that let endpoints dynamically change identifiers. These new
>> functionalities may, for example, facilitate anonymity through obscurity
>> while preventing security issues that might result from abuse, ensuring that
>> information about actual endpoints and their location is revealed only on a
>> need-to-know basis.
>>
>    Padma,
>
>    I don't think this goes far enough in terms of protections for users
>    against the potential abuse of something that might be able to
>    individually and persistently identify them on the Internet. First,
>    it's not clear what network layer identity means in this context. I
>    hope it refers to an ad hoc collection of identifiers as opposed to
>    the identity of individual users or devices. In any case maybe a
>    definition of identity might be in order here. Secondly, I think it
>    should be stated up front that identity cannot in any way be used to
>    identify individual users, it cannot be used to create a global
>    database of Internet users, in no way can it be used by networks or
>    governments to track or block individuals, nor can it ever be required
>    for communications. That implies network layer identities cannot
>    contain PII (personally identifiable information) and cannot be
>    permanently assigned to users or devices (in the same spirit that
>    Ethernet addresses were removed from IIDs because of privacy
>    concerns).
>
>    Thanks,
>    Tom
>
> When it comes to these concerns I’d strongly recommend to have a look at how identity attributes were exchanged and trust established within the ABFAB framework (https://tools.ietf.org/wg/abfab/)
>
> Be goode,
>
>
>
> ________________________________
>
> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.
>
> The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.
>
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição