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

Dipankar Raychaudhuri <ray@winlab.rutgers.edu> Wed, 16 August 2017 17:12 UTC

Return-Path: <ray@winlab.rutgers.edu>
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 7886913235E for <ideas@ietfa.amsl.com>; Wed, 16 Aug 2017 10:12:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=winlab-rutgers-edu.20150623.gappssmtp.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 fY1JzkkjikqM for <ideas@ietfa.amsl.com>; Wed, 16 Aug 2017 10:12:02 -0700 (PDT)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (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 76E4513234E for <ideas@ietf.org>; Wed, 16 Aug 2017 10:12:01 -0700 (PDT)
Received: by mail-oi0-x22f.google.com with SMTP id e124so42568833oig.2 for <ideas@ietf.org>; Wed, 16 Aug 2017 10:12:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=winlab-rutgers-edu.20150623.gappssmtp.com; s=20150623; h=from:mime-version:thread-index:date:message-id:subject:to; bh=7mQ+D+NJAyQoIkXl7JbXgXwlavpM66SvCi5Q/rcPH64=; b=Kk2TMcotiVlx7aorvMa34uN9KgoQqsv4GJ+Y/p/5QFBKZJFkBGpJRlOTh79lv9Ckgp 3fkJdRag1LeSp2CGcCmBbZCZZh7KyaoZoOrF24zA/nWD+D7wQTWivZplz7hcbhai82Cf 45NHaxAYzKFisb73QqNHSeZEzKcVci3hVRhciCHKqt7tUNGuPL2PIIIwOHV1la/owgBu d+cqZdmeGXsn3CzaNpXiLBjrp84I8UFmB4yY4Dkh/yNft00kxhKz1BIh3uDjP8DS4n1c dR8WD+dV/GBZnxRFYll9nvpQKbHj1+p8DtzdT4HhvCLZ1puRGhMkIn3cTHyJsES7sMB7 4TFQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:thread-index:date:message-id :subject:to; bh=7mQ+D+NJAyQoIkXl7JbXgXwlavpM66SvCi5Q/rcPH64=; b=HxgqkyqrdmP5XaxYxL5kelHKzu1If2fiebEPBfDzyp8cOuJNby313kz7wevxLr7XRB 3NW+HeWRXjH1Qq/AEWzMmBqgIX+Qfot9nj6KCpJg7aF70UnoyMYLiKte+sh85aaVInNd tQ0QeYG3ByQ/D1/BYWUTQ5OtcWh58ukq9HInJ5NYO7d2wSENKuK2+HZ9yGhdqpXRzzf1 DiY5+9GVBbo//2LQ01zMnDIE4tBshJgmBizOtGQVkSVwZ+vF7aCmXczx7dCN7tnkCRfX XlcT/aJMMtTwC4Zd903wom0ESbDvIWHtILjGFbXrmgIpLbbykglbz3jZ90vBi7o6Qywi jk4g==
X-Gm-Message-State: AHYfb5g0fiYIjL+JH98mzsGePemNftu743l8GxDPcm6No9SgFHOjHc11 Nh+W4adLVMnQAaDxmklNnSDw8G0GtkBc
X-Received: by 10.202.168.145 with SMTP id r139mr2711828oie.147.1502903521026; Wed, 16 Aug 2017 10:12:01 -0700 (PDT)
From: Dipankar Raychaudhuri <ray@winlab.rutgers.edu>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdMWqYLgj03j2Z1tQBCDTLTgEtT9RA==
Date: Wed, 16 Aug 2017 13:11:51 -0400
Message-ID: <175f533795012c49555543dda2f1f3a8@mail.gmail.com>
To: ideas@ietf.org
Content-Type: multipart/alternative; boundary="001a113cc00c80b9540556e1fead"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ideas/15Gj7vZsK-K9kqwwU-nmp0Z8m10>
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 17:12:57 -0000

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