[Ideas] IDEAS Charter

Padma Pillay-Esnault <padma.ietf@gmail.com> Sat, 02 September 2017 01:55 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 68769132F42 for <ideas@ietfa.amsl.com>; Fri, 1 Sep 2017 18:55:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.799
X-Spam-Level:
X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 tests=[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 K2FzHyjeGJyZ for <ideas@ietfa.amsl.com>; Fri, 1 Sep 2017 18:55:19 -0700 (PDT)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (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 BEE3A1343A3 for <ideas@ietf.org>; Fri, 1 Sep 2017 18:55:18 -0700 (PDT)
Received: by mail-qk0-x234.google.com with SMTP id l65so7391703qkc.0 for <ideas@ietf.org>; Fri, 01 Sep 2017 18:55:18 -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; bh=ZwtskrgUuQ6yd8IzyyiUYXV2g7FfD0xXs1c5208U2H4=; b=HewMM2xySNq8Gr/WguZILpAAZS+6cB8XsFRrr6b54JWDj6DvQUIEWtitHipE9YynJJ YFmsjtmscp4BoFP5WjxjcEg4r+JHDkY3kyNp930peOgi9Eov0Mnlpv5pD8tDeWdbCv8I b67zNishcua2cnxB2zcdwjIDYd1UqzB/BzqRVxAJdDn4OQEDnM9qh1QkbHQ5TXEFXQII 7PyV5wobHtH84eHWlzF5uHyvv37mOGW2/49tK9GyAFkU5qLj9rgiszua2DYTCzjhlqMC y9VAClYycpz5wI+81MjmMfF6nOsocv/IuzNBpoO8I5FStdZEhE1m8Um3KLSnIt+mTuu/ Rrvg==
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; bh=ZwtskrgUuQ6yd8IzyyiUYXV2g7FfD0xXs1c5208U2H4=; b=o8SPLIgGxNuzBndPoqwPPjSYOEtEVyUt95XY7atu632/bxbyxpTwcCIs0mTJdaCleQ bluTkEAPghLJIHvozjF/kh1nBbD9j76XRC2oZCQeJ1Zt1nMgshddbH7GwhjP17H71oPK Fb2oc6J/q9nIlArVffCvtmf61Rq+23RNhnC/JrPDU0FdHFjVBChOMcnJ/peRHdLlV38I wZKOIECWrnusS2haqnOivfOAC4B59uu62Ml4Rvwmx2g+ucDmc8hVljoFfK56W82BwRB8 33Ftk5UMLRGrdA7XcHbt3WMabF+4V4XdUVB8QEjRUtrkfZ3sz1yRyxZFAhWIJjMd1w12 IvzQ==
X-Gm-Message-State: AHPjjUhtywtTWnpIibBwcqj/yB5RXe63Mj6hq3kFZ2Jt50g7LSc9bWom +ODqlYav2df/XKWcgtxQXWs9/blOJYkb
X-Google-Smtp-Source: ADKCNb7KTsX4Ww/QQcaP67B8YZysDdQIVocr+poygi5X/0AC21R7ynYFgOVA75zB+9JtHPU6TiSEwfl4xaBEbHh6o5M=
X-Received: by 10.55.164.134 with SMTP id n128mr5622798qke.145.1504317317737; Fri, 01 Sep 2017 18:55:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.47.106 with HTTP; Fri, 1 Sep 2017 18:55:17 -0700 (PDT)
From: Padma Pillay-Esnault <padma.ietf@gmail.com>
Date: Fri, 01 Sep 2017 18:55:17 -0700
Message-ID: <CAG-CQxpgzXMYQbUxPpGPL6xJD4kUeL70v5MJ8R9FbFFqnzQsug@mail.gmail.com>
To: ideas@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c0763fc5a731805582b2bff"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ideas/mCkGxLsxwc1mxm-Ps1qPitG7a1M>
Subject: [Ideas] IDEAS Charter
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: Sat, 02 Sep 2017 01:55:24 -0000

Dear IDEAS

The final outcome of the discussions on the alias is reflected in the text
below. This version is based on the edits done by Alvaro, some of the
latest comments and fixing some nits.

Thank you all for your feedback and comments.

Looking forward to the next milestone

Padma



IDEAS: “IDentity EnAbled networkS”



Network solutions based on the concept of Identifier-Locator separation are
increasingly considered to support mobility, overlay networking for
virtualization 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. Identifier-locator
protocols are also useful for additional services involving dynamic
association of a name to a set of network addresses - these include dynamic
multicast, cloud service anycast and context-aware IoT queries.



The IDEAS WG is chartered to produce a framework document that defines the
expected behavior of a mapping system across the multiple existing use
cases.  The framework will aim at a homogeneous behavior across use cases,
and it will call out specific trade-offs that may be considered in the
development of solutions.  We refer to the framework providing the set of
services as Generic Identity Services (GRIDS).



Some of the areas that should be considered when developing the framework
include:



- Flexibility and extensibility considerations



- Description of interfaces for different protocols to interact with the
framework (e.g. id-loc split protocols, management protocols, etc)



- Requirements for identifier/locator mapping resolution and mapping update
(e.g. discovery, pub/sub, multi-homing, ...)



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



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



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



- Analysis of the concepts of identity-identifier split and dynamic
identifier changes, including their implications on anonymity and privacy.





The IDEAS WG will closely collaborate with LISP and HIP WGs. The WG will
also collaborate with other WG as needed.



WG deliverables include:



(1) Generic Identity Services Framework



(2) Other 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 for identifier/locator mapping and resolution



- Requirements for identity authentication and authorization service (for
GRIDS).



- Applications of the architecture for use cases



- Threat model document





Milestones



January 2018 Adopt WG draft for the Generic Identity Services framework



July 2018 WGLC for the Generic Identity Services framework



September 2018 Send Generic Identity Services framework draft to the IESG



November 2018 Recharter