[Ideas] Your Input requested: Charter Proposal New Version

Padma Pillay-Esnault <padma.ietf@gmail.com> Mon, 07 August 2017 05:20 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 4C62B128A32 for <ideas@ietfa.amsl.com>; Sun, 6 Aug 2017 22:20:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=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 29jx53jAhAg6 for <ideas@ietfa.amsl.com>; Sun, 6 Aug 2017 22:20:04 -0700 (PDT)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::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 46EC31287A5 for <ideas@ietf.org>; Sun, 6 Aug 2017 22:20:04 -0700 (PDT)
Received: by mail-qk0-x233.google.com with SMTP id z18so34213995qka.4 for <ideas@ietf.org>; Sun, 06 Aug 2017 22:20:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=LtSUT1WKj/2BvKaQGpZEYOv1/3csZHUWhXSxr7tK4WY=; b=egnPwmruaOyLRaDujOzvV/7Xzr5l1e5mO1ju6U+VMVpYY2xuMbBAy7I2z+c87yJ0W8 GFxZIxuvgLyW3kAqMxMfFsWcNLk3YO92DN0hgdPByRRxiyTEtL42z/x62Aawrkg2jAa8 mIELK6WAvVGgM1k9SkKMGzEhqcwdISfgQO9OBenXURnjTmuQu/CF2K8PRFkoqfY9ZAOE U94MRljIzc724GP5zqpBppOQVtU3KknevxhzhPqTO7So6yIBW9DEd5rhedkm6jFhy187 zwNlR8SvH4Urb/L5fMNob94T/7ldL1J2Epm/+pseMonUuhtjspnIdXr15LTpreaYz4VF 9C9g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=LtSUT1WKj/2BvKaQGpZEYOv1/3csZHUWhXSxr7tK4WY=; b=Fz1wMZ5KxqQ55ts/3kyCBUAgQCrFS1uWdEv3hc5ytZO2mialNYZmSE+g7uw0Hzl/P+ lF7n4Q5S0I+Mq/79gveNGPcFcGV5niCvBkvNbfrUJ+eyFqDLepDRu60CsCDPRYYByBwr OnJFeeU3EQ9oUSMpTyOs1ux0ZaRX7YhzciwsTi3eHvr0B7mxQ2HuzVTohmpDYC4whIGy 0m2BfFn6CuSs8ul4wpj0tmbKg35zuk5p6SmXpbpbudKhjnvpwPbLX/6sFiht7cuw9O3l C95ogtBWXlM6kZUNQIo3GW6GDBDxYDG/5oQlmsCYq21XrCNFVSo62KQvzH0XiYTgzUex kbBw==
X-Gm-Message-State: AHYfb5iy1YK0RF27ZpyZoZgiWo/ZbQ8RJCHx/4qzw1AkjUH0+ES8017I w+FcNqwCmU0X6DQgK7AQRevLPuxBZoL5
X-Received: by 10.55.16.161 with SMTP id 33mr13358711qkq.312.1502083203223; Sun, 06 Aug 2017 22:20:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.43.199 with HTTP; Sun, 6 Aug 2017 22:20:02 -0700 (PDT)
From: Padma Pillay-Esnault <padma.ietf@gmail.com>
Date: Sun, 06 Aug 2017 22:20:02 -0700
Message-ID: <CAG-CQxpxDXxLXdu0a2GdBRfTFLM_C+jqCz58HoNim52C7Yzr8g@mail.gmail.com>
To: ideas@ietf.org
Cc: Padma Pillay-Esnault <padma.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="001a113b0b78c0549e055622ff52"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ideas/lITs5QSDBXEaPV3afqF4lrQ0AGs>
Subject: [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 05:20:06 -0000

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.



Some examples of the problem space are:

- Common infrastructure and primitives: The lack of a common infrastructure
is a barrier for the application of common and consistent basic networking
policies. Likewise, mapping services and infrastructure that apply to
identity-identifier as well as identifier-locator mappings reduces
operational and deployment complexity.



- Access control: Unrestricted look up on an identifier may reveal
information such as the locator to eavesdroppers. Today, there is no way to
prevent the look up of an identifier with some user defined policy or finer
grain rules.



- Privacy:  The use of long-lived and public identifiers may be desirable
for looking up a peer, however it causes privacy issues as well. Indeed,
when identifier-location pairs can be looked up without restriction, flows
can be pinned by anybody to specific end systems.  The endpoint
communications should be able to change their identifier while retaining
their identity and associated policies. The use of temporary identifiers
and access control on lookups should help discourage undesired traffic and
conceal sensitive network information of end devices to eavesdroppers.



The Identity Enabled Networks (IDEAS) working group is chartered to develop
a common framework that can be used by identifier-based protocols and
provides services to address their requirements. We refer to the common
framework providing the set of services as Generic Identity Services
(GRIDS).



The working group will identify gaps and make recommendations on changes
needed for interactions between the framework and identifier-enabled
protocols.



Specifically, the IDEAS WG is chartered to work on these areas for the
modular framework:



- Definition of primitives for interworking with identifier-location split
protocols

- Identifier/locator mapping and resolution (e.g. discovery, pub/sub,
multihoming, ...)

- Registration and lifecycle management of identities and their associated
identifiers.

- Identity authentication and authorization (e.g. access to framework,
update of information for identifiers..)

- Definition and enforcement of basic networking policies (e.g. ability to
look up an identifier-locator pair, permit forwarding traffic for
particular endpoints on a per-identity basis…)

- Identity and Identifier Metadata (fixed or slow changing)

- Management aspects and Data Models where appropriate.



The IDEAS WG will collaborate with other Working Groups to ensure
interoperability with LISP, HIP, ILA and other relevant work. Furthermore,
it will try to reuse technologies already developed when appropriate.



WG deliverables include the definition:

Generic Identity Services Framework



WG sustaining/informational documents may include:

These documents may not necessarily be published, but may be maintained in
a draft form or on a collaborative Working Group wiki to support the
efforts of the Working Group and help new comers:

- Problem statement

- Use cases

- Requirements

- Applications of the architecture for use cases



Milestones

March 2018 Adopt WG draft for the Generic Identity Services framework

August 2018 WGLC for the Generic Identity Services framework

December 2018 Send Generic Identity Services framework draft to the IESG