IETF Logo Mail Archive

Re: future of identifiers

Eliot Lear <lear@cisco.com> Tue, 29 October 2013 16:23 UTC

Return-Path: <lear@cisco.com>
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 795E611E8169 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 09:23:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.439
X-Spam-Level:
X-Spam-Status: No, score=-110.439 tagged_above=-999 required=5 tests=[AWL=0.160, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 WEvEB0xKKhHL for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 09:23:16 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 23D0C11E80F1 for <ietf@ietf.org>; Tue, 29 Oct 2013 09:23:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1039; q=dns/txt; s=iport; t=1383063796; x=1384273396; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=nmPxAOv7m02MwZZk0pa0hUnM4nOn216Gl7rocUPuxNc=; b=INqPyWlT0XDRFRQf1C7gIGQuVY6PkzWIdyw03fxWqXl5p64SeEk882Vi oFbRUoZuNHl4sWaxjriLFt7EnN9z6r8GCz3Ur7zztRI52Sp1lN1cUepFs W5/8JhYyP7EbMQpmC8x4FqgjENkYk08y+GVFncvo16Y0gNys4sei5+7v0 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiAFAH3gb1KQ/khR/2dsb2JhbABZgweEH7wigSoWdIIlAQEBBCMPAUURCxgCAgUWCwICCQMCAQIBKxoGAQwGAgEBiAOnOpJogSmOJYJqgUIDk2iEIpIIgyc7
X-IronPort-AV: E=Sophos;i="4.93,594,1378857600"; d="scan'208";a="18627972"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-3.cisco.com with ESMTP; 29 Oct 2013 16:23:15 +0000
Received: from mctiny.local ([10.61.200.185]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r9TGNATc008854 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Oct 2013 16:23:11 GMT
Message-ID: <526FE0EE.3000608@cisco.com>
Date: Tue, 29 Oct 2013 17:23:10 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>
Subject: Re: future of identifiers
References: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net> <563C58B6-DD66-4CDD-969A-0DAF7DA205D9@frobbit.se> <98DF3DC1-2B5E-43E5-9AE4-0213BD73F3DC@vpnc.org>
In-Reply-To: <98DF3DC1-2B5E-43E5-9AE4-0213BD73F3DC@vpnc.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
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 16:23:21 -0000

On 10/29/13 5:16 PM, Paul Hoffman wrote:
> On Oct 29, 2013, at 9:03 AM, Patrik Fältström <paf@frobbit.se> wrote:
>
>> I think it is important to not restart discussions already held regarding different requirements on identifiers, requirements that in turn lead to various alternatives on how they are allocated, managed and resolved. I do not think one can have one identifier that fits all. Instead multiple kind of identifiers are needed. Because of requirements on uniqueness (absolute, low risk of collisions or not needed at all), persistence, human readable/understandable, whether allocation and resolution should be designed for read (lookups) or write (allocation), what the identifier is to be used for (see id/loc discussions).
> Having sat through many of those discussions with Patrik 15 years ago: +1

And having chaired NSRG, + 1/2.  That is- it's always fair to look at
new developments, but let's at least be aware of what was covered by
others and build on their success (or avoid their failures).

Eliot

v2.23.0 | Report a Bug | By Email