IETF Logo Mail Archive

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

"Liubingyang (Bryan)" <liubingyang@huawei.com> Wed, 16 August 2017 23:30 UTC

Return-Path: <liubingyang@huawei.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 D2447132335 for <ideas@ietfa.amsl.com>; Wed, 16 Aug 2017 16:30:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 Z2RT9iJa-bMp for <ideas@ietfa.amsl.com>; Wed, 16 Aug 2017 16:30:19 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C352413235E for <ideas@ietf.org>; Wed, 16 Aug 2017 16:30:18 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DTO57906; Wed, 16 Aug 2017 23:30:16 +0000 (GMT)
Received: from DGGEMI402-HUB.china.huawei.com (10.3.17.135) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 17 Aug 2017 00:30:15 +0100
Received: from DGGEMI506-MBX.china.huawei.com ([169.254.4.174]) by dggemi402-hub.china.huawei.com ([10.3.17.135]) with mapi id 14.03.0301.000; Thu, 17 Aug 2017 07:30:10 +0800
From: "Liubingyang (Bryan)" <liubingyang@huawei.com>
To: Dipankar Raychaudhuri <ray@winlab.rutgers.edu>, "ideas@ietf.org" <ideas@ietf.org>
Thread-Topic: [Ideas] Your Input requested: Charter Proposal New Version
Thread-Index: AdMWqYLgpUj993RLRk2klH7D5AtAjAAPeWCA
Date: Wed, 16 Aug 2017 23:30:10 +0000
Message-ID: <C1CE72EE84AF224E94DA21AE134209EE01A2A5DC@DGGEMI506-MBX.china.huawei.com>
References: <175f533795012c49555543dda2f1f3a8@mail.gmail.com>
In-Reply-To: <175f533795012c49555543dda2f1f3a8@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.168.116]
Content-Type: multipart/alternative; boundary="_000_C1CE72EE84AF224E94DA21AE134209EE01A2A5DCDGGEMI506MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.5994D589.00C9, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.4.174, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 018e6e1cce410ee72e0571540e9b9256
Archived-At: <https://mailarchive.ietf.org/arch/msg/ideas/jPaOx3_Q5srbEt1uk5isZn6FT1U>
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: Wed, 16 Aug 2017 23:30:22 -0000

Ray,

Could you please name a few such protocols you mentioned in (4) ?

Thanks
Bingyang

From: Ideas [mailto:ideas-bounces@ietf.org] On Behalf Of Dipankar Raychaudhuri
Sent: Thursday, August 17, 2017 1:12 AM
To: ideas@ietf.org
Subject: Re: [Ideas] Your Input requested: Charter Proposal New Version

I reviewed the charter document and feel that it is a good start.  My main comments are:
(1) I agree with the concept of an identity-identifier split, which is necessary for an important set of applications requiring dynamic change of identifier. Realizing this will require something similar to a trusted “name certification service”  [cf. “MobilityFirst: A Robust and Trustworthy Mobility-Centric Architecture for the Future Internet, ACM MC2R, July 2012] in addition to a dynamic name-to-locator mapping/resolution service [cf. ”DMap: A Shared Hosting Scheme for Dynamic Identifier to Locator Mappings in the Global Internet”, ICDCS 2012]
(2) A key requirement for the mapping service is the ability to support multiple types of resolution including identifier to identifier (i.e. recursive), identifier to group of identifiers, identifier to single locator, identifier to a list of locators, etc.  We have found the recursive identifier resolution capability to be very useful for scaling and new service creation.
(3) The final output of the WG at the end of the doc should be filled in a bit further in terms of specific APIs and query/response/update protocol definitions to be included in the spec.
(4) While I realize that the current charter’s scope is intentionally limited to defining general-purpose control plane support, the spec could be of greater value by defining or linking one or more specific identifier-based routing (data plane) protocols compatible with the IDEAS infrastructure.

Ray

(D. Raychaudhuri)
WINLAB, Rutgers University

v2.23.0 | Report a Bug | By Email