IETF Logo Mail Archive

Re: future of identifiers

jnc@mercury.lcs.mit.edu (Noel Chiappa) Tue, 29 October 2013 19:57 UTC

Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 584C621F9B65 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 12:57:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.497
X-Spam-Level:
X-Spam-Status: No, score=-6.497 tagged_above=-999 required=5 tests=[AWL=0.102, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9S59XeW-GLdS for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 12:57:06 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 400CB11E8294 for <ietf@ietf.org>; Tue, 29 Oct 2013 12:56:35 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 4E19418C180; Tue, 29 Oct 2013 15:56:34 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: future of identifiers
Message-Id: <20131029195634.4E19418C180@mercury.lcs.mit.edu>
Date: Tue, 29 Oct 2013 15:56:34 -0400
From: jnc@mercury.lcs.mit.edu
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Oct 2013 19:57:38 -0000

    > From: Eliot Lear <lear@cisco.com>

    > And having chaired NSRG

It might be worth observing that NSRG was focused on new namespaces for the
lower-middle part of the stack (e.g. TCP endpoint names), whereas I get
the impression from Jari's note that that was about names further up
(application, etc).

But maybe I got an incorrect impression?

	Noel

v2.23.0 | Report a Bug | By Email