Re: [Ideas] IDEAS Charter

<christian.jacquenet@orange.com> Mon, 04 September 2017 07:43 UTC

Return-Path: <christian.jacquenet@orange.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 2B17E1252BA for <ideas@ietfa.amsl.com>; Mon, 4 Sep 2017 00:43:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Level:
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
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 BCiHrKbxcxla for <ideas@ietfa.amsl.com>; Mon, 4 Sep 2017 00:43:29 -0700 (PDT)
Received: from relais-inet.orange.com (mta239.mail.business.static.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAC0F1200F3 for <ideas@ietf.org>; Mon, 4 Sep 2017 00:43:28 -0700 (PDT)
Received: from opfedar06.francetelecom.fr (unknown [xx.xx.xx.8]) by opfedar21.francetelecom.fr (ESMTP service) with ESMTP id DDCEB1001D7; Mon, 4 Sep 2017 09:43:26 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.42]) by opfedar06.francetelecom.fr (ESMTP service) with ESMTP id C637180062; Mon, 4 Sep 2017 09:43:26 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM41.corporate.adroot.infra.ftgroup ([fe80::c845:f762:8997:ec86%19]) with mapi id 14.03.0361.001; Mon, 4 Sep 2017 09:43:26 +0200
From: christian.jacquenet@orange.com
To: Padma Pillay-Esnault <padma.ietf@gmail.com>, "ideas@ietf.org" <ideas@ietf.org>
Thread-Topic: [Ideas] IDEAS Charter
Thread-Index: AQHTI46NYelfsMLbbEOIZqWeY8kJX6KkW7Xg
Date: Mon, 04 Sep 2017 07:43:25 +0000
Message-ID: <25942_1504511006_59AD041E_25942_68_1_88132E969123D14D9BD844E1CD516EDE14784A1C@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <CAG-CQxpgzXMYQbUxPpGPL6xJD4kUeL70v5MJ8R9FbFFqnzQsug@mail.gmail.com>
In-Reply-To: <CAG-CQxpgzXMYQbUxPpGPL6xJD4kUeL70v5MJ8R9FbFFqnzQsug@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.1]
Content-Type: multipart/alternative; boundary="_000_88132E969123D14D9BD844E1CD516EDE14784A1COPEXCLILMA3corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ideas/tAZcN2Xg_8JAEBdblq5Y5cDY1ME>
Subject: Re: [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: Mon, 04 Sep 2017 07:43:34 -0000

Dear all,

Thanks again to Padma for the editing effort. I too support this charter.

Cheers,

Christian.

De : Ideas [mailto:ideas-bounces@ietf.org] De la part de Padma Pillay-Esnault
Envoyé : samedi 2 septembre 2017 03:55
À : ideas@ietf.org
Objet : [Ideas] IDEAS Charter

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



_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.