Re: [Ideas] IDEAS Charter
Lan Gao <langao@cdi.cn> Mon, 04 September 2017 00:35 UTC
Return-Path: <langao@cdi.cn>
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 39B3C124319 for <ideas@ietfa.amsl.com>; Sun, 3 Sep 2017 17:35:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.42
X-Spam-Level:
X-Spam-Status: No, score=-1.42 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=no 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 EaOK-UM-JzqR for <ideas@ietfa.amsl.com>; Sun, 3 Sep 2017 17:35:21 -0700 (PDT)
Received: from regular1.263xmail.com (regular1.263xmail.com [211.150.99.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C538132198 for <ideas@ietf.org>; Sun, 3 Sep 2017 17:35:20 -0700 (PDT)
Received: from langao?cdi.cn (unknown [192.168.165.103]) by regular1.263xmail.com (Postfix) with ESMTP id 16EA04A47 for <ideas@ietf.org>; Mon, 4 Sep 2017 08:35:17 +0800 (CST)
X-263anti-spam: KSV:0;bpcheck:1;
X-MAIL-GRAY: 0
X-MAIL-DELIVERY: 1
X-KSVirus-check: 0
X-ADDR-CHECKED: 0
X-ABS-CHECKED: 1
X-ANTISPAM-LEVEL: 2
Received: from smtp.263.net (va-smtp01.263.net [54.88.144.211]) by smtp.263.net (Postfix) with ESMTP id 7384C3FE for <ideas@ietf.org>; Mon, 4 Sep 2017 08:35:16 +0800 (CST)
Received: from mail-oi0-f50.google.com (localhost.localdomain [127.0.0.1]) by smtp.263.net (Postfix) with ESMTP id D0AB39F60F for <ideas@ietf.org>; Mon, 4 Sep 2017 08:35:00 +0800 (CST)
X-RL-SENDER: langao@cdi.cn
X-FST-TO: ideas@ietf.org
X-SENDER-IP: 209.85.218.50
X-LOGIN-NAME: langao@cdi.cn
X-UNIQUE-TAG: <16c19e5b09a4e24195f1b68e83dafdb3>
X-ATTACHMENT-NUM: 0
X-SENDER: langao@cdi.cn
X-DNS-TYPE: 0
Received: from mail-oi0-f50.google.com (unknown [209.85.218.50]) by smtp.263.net (Postfix) whith ESMTP id 32265BWZVQK; Mon, 04 Sep 2017 08:35:00 +0800 (CST)
Received: by mail-oi0-f50.google.com with SMTP id t75so34206190oie.3 for <ideas@ietf.org>; Sun, 03 Sep 2017 17:35:00 -0700 (PDT)
X-Gm-Message-State: AHPjjUiQvV/+HraMymh8Y6mIPZoiezUu66My+1LhMBYl2qRWvCWqu6L9 Uvi6xxYbHC71Xq18CKoiJAxyWjKuyA==
X-Google-Smtp-Source: ADKCNb5Iu4Qqqja72/PBV/TUyUALFapQiVB96YhIpPnJ4gV4IEx6rzJDfOhIM3IoImXRknO629+X5lZZmi9+JPf6T4M=
X-Received: by 10.202.73.206 with SMTP id w197mr3324705oia.203.1504485297563; Sun, 03 Sep 2017 17:34:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.58.36.203 with HTTP; Sun, 3 Sep 2017 17:34:57 -0700 (PDT)
In-Reply-To: <DE35D83C-1B36-40AC-8D44-0459A46A8827@cisco.com>
References: <CAG-CQxpgzXMYQbUxPpGPL6xJD4kUeL70v5MJ8R9FbFFqnzQsug@mail.gmail.com> <5u0s47x32il27lvo9gerxjxa.1504356176497@email.android.com> <DE35D83C-1B36-40AC-8D44-0459A46A8827@cisco.com>
From: Lan Gao <langao@cdi.cn>
Date: Mon, 04 Sep 2017 08:34:57 +0800
X-Gmail-Original-Message-ID: <CAOB5waJf3084Lp9UmB3V_z0PY2BRouE7cFHo79ja_ZiSxwS4cw@mail.gmail.com>
Message-ID: <CAOB5waJf3084Lp9UmB3V_z0PY2BRouE7cFHo79ja_ZiSxwS4cw@mail.gmail.com>
To: Sam Sun <sam.sun.ietf@gmail.com>, "ideas@ietf.org" <ideas@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c14fc0bb2e4f055852470f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ideas/ZxQ6P7FisZx1FPCvlqmjwm5AN0g>
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 00:35:24 -0000
The new charter looks great. It will be a good foundation to build upon. Regards, Lan Gao On Sun, Sep 3, 2017 at 1:59 PM, Victor Moreno (vimoreno) <vimoreno@cisco.com > wrote: > +1 > > I support this as the charter to put forward. > > Victor > > On Sep 2, 2017, at 5:43 AM, Sam Sun <sam.sun.ietf@gmail.com> wrote: > > Padma, > > The updated charter looks great! > > Thanks for the relentless effort in putting everything together. Looking > forward to the next phase to implement the charter! > > All the best, > Sam > > > -------- Original Message -------- > Subject: [Ideas] IDEAS Charter > From: Padma Pillay-Esnault > To: ideas@ietf.org > CC: > > > 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 > > > > _______________________________________________ > Ideas mailing list > Ideas@ietf.org > https://www.ietf.org/mailman/listinfo/ideas > > > _______________________________________________ > Ideas mailing list > Ideas@ietf.org > https://www.ietf.org/mailman/listinfo/ideas > >
- [Ideas] IDEAS Charter Padma Pillay-Esnault
- Re: [Ideas] IDEAS Charter Sam Sun
- Re: [Ideas] IDEAS Charter Victor Moreno (vimoreno)
- Re: [Ideas] IDEAS Charter Lan Gao
- Re: [Ideas] IDEAS Charter Georgios Karagiannis
- Re: [Ideas] IDEAS Charter christian.jacquenet
- Re: [Ideas] IDEAS Charter Albert Cabellos
- Re: [Ideas] IDEAS Charter Rita Mi
- Re: [Ideas] IDEAS Charter Pascal Thubert (pthubert)
- Re: [Ideas] IDEAS Charter Di Ma
- Re: [Ideas] IDEAS Charter Alberto Rodriguez-Natal
- Re: [Ideas] IDEAS Charter Reshad Rahman (rrahman)
- Re: [Ideas] IDEAS Charter Alexander Clemm
- Re: [Ideas] IDEAS Charter Yingzhen Qu
- Re: [Ideas] IDEAS Charter Alvaro Retana (aretana)