Re: [Ideas] WG Review: IDentity Enabled Networks (ideas)

Padma Pillay-Esnault <> Sat, 07 October 2017 03:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0AAFA1326FE; Fri, 6 Oct 2017 20:38:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id P_TXPLeJoI1I; Fri, 6 Oct 2017 20:38:13 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 60D9E132076; Fri, 6 Oct 2017 20:38:13 -0700 (PDT)
Received: by with SMTP id 196so4625758wma.1; Fri, 06 Oct 2017 20:38:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=cVepUijScZf8MBa9ggQT3GtQ8LXqimLyLEDbKhXiaSo=; b=i+OX8VoiRCU8Kdwx3T98LxPVcQ8oEJdgPfFyocusDOw+EwLBCPMNMVwxSHZ0kzwKfI tREzP/i8gYbpb38+u38W7GWdQWQ9A9/h2D+2ekXtvV+qFdSA4YasHIkxVzEqdYZw7vMe 7IT9tHzIKFpqs0VMzMRY1hQjqZ09zi+CEqh0rsACwrOC8Os4K27suKf5+sFWfR8FQy++ AlsqAAWe3GTn3VPcF4CXS+b38UOkPVM34BRYKEKpSjkBv9bv8WCRyIWQy0ww8S74a/v1 zBAawh6goceePF73IIMegtx0Mfcw6izVg61+aTfxreFC/eHhAfT2N4lCyvrRyPJqWFzB WLHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=cVepUijScZf8MBa9ggQT3GtQ8LXqimLyLEDbKhXiaSo=; b=caVB208nbQ7TsESC9Ij8lmPI+NAKEo8IMUkogw6VzcJU0P/bPwPZKVuHb9W5s5rIYR IBI5ah5lgeDUMLpVTna0MfzPx2mQ9JKFV8bM8Qd1JQ5KJLcQPoGpJVJGX1BPop4yrfM6 nkAXZUmRBdI2tftAA3ErJXZkskv5UuOATooQlfc9QgZ41suVA0Spj4Ivizz2biz8aBPv REHzZRVzK0+B1jGstzr9rj041sJDx268kSvp7EyDkgbSJzUFb1pGRJOiCMl5sS23QNTT n6ksPCw9zhShh7RxsOpekuI0o9eJGJ1Rw0jd06AWM7aCyCskefx0eBxDb0BY1jrkFB9w 2v1g==
X-Gm-Message-State: AMCzsaUIaIciDAp724eYWQ7XbRuT6ZVe5uOgOtZ06Lc3UGtAgB22P5Sf 3VD/9c41pTu1tXTEJqb1DbfntRMsWBsu0pZgTrICtw==
X-Google-Smtp-Source: AOwi7QC/x/aumAXn37EdBmWBrn/DLWZ/JI0offx4yaQZw7eohmRlGLi/PLFJYX5PX6xuM2NK28pOaHCq31ILMsFUQwQ=
X-Received: by with SMTP id t18mr3901687wrg.19.1507347491906; Fri, 06 Oct 2017 20:38:11 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Fri, 6 Oct 2017 20:38:10 -0700 (PDT)
In-Reply-To: <>
References: <> <> <> <> <> <> <> <> <> <> <> <C5034E44CD620A44971BAAEB372655DC2DD336ED@lhreml502-mbs> <>
From: Padma Pillay-Esnault <>
Date: Fri, 6 Oct 2017 20:38:10 -0700
Message-ID: <>
To: Stephen Farrell <>
Cc: Georgios Karagiannis <>, Uma Chunduri <>, "Joel M. Halpern" <>, Benjamin Kaduk <>, Jari Arkko <>, "" <>, "" <>
Content-Type: multipart/alternative; boundary="089e082452d0ceeaeb055aecaf1c"
Archived-At: <>
Subject: Re: [Ideas] WG Review: IDentity Enabled Networks (ideas)
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." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 07 Oct 2017 03:38:15 -0000

On Fri, Oct 6, 2017 at 2:32 AM, Stephen Farrell <>

> <snip>
> It is not at all clear that that would
> be even relevant if one wanted to build the kind of all
> encompassing IdPs envisaged in the ideas charter/draft.
> <snip>

What kind of all encompassing IdPs is being referred to above? The charter
does not propose to build such an all encompassing system.

The charter refers to a mapping system for Id/Loc protocols. The data is
routing information. It may have some limited information if useful for
routing purposes - such as the list of locators, groupings and so on.

Today, routing information of this nature in mapping systems is not hidden.
All nodes in ID/Loc protocols typically access this information for
encapsulation, translation or forwarding decisions without any restrictions
(within their instance/scope).

One of the goals is to be able to authenticate and have access-control on
the lookups if so desired.  This functionality should enhance privacy on
revealing locators of nodes.

For example, you may want to advertise the location of some of  your mobile
IoT nodes in a factory on a need to know basis. The solution proposed here
is one of them.

To address your concerns: no all encompassing system, or humans involved