Re: [apps-discuss] status and name

Dave CROCKER <dhc@dcrocker.net> Sat, 19 November 2011 03:10 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D081711E809B for <apps-discuss@ietfa.amsl.com>; Fri, 18 Nov 2011 19:10:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.933
X-Spam-Level:
X-Spam-Status: No, score=-4.933 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_RECV_SPAM_DOMN0b=1.666]
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 tkBhCed+FXlM for <apps-discuss@ietfa.amsl.com>; Fri, 18 Nov 2011 19:10:51 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2964B21F8922 for <apps-discuss@ietf.org>; Fri, 18 Nov 2011 19:10:51 -0800 (PST)
Received: from [192.168.0.77] (59-115-128-147.dynamic.hinet.net [59.115.128.147]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id pAJ3AKFn008509 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 Nov 2011 19:10:33 -0800
Message-ID: <4EC71E16.3000200@dcrocker.net>
Date: Sat, 19 Nov 2011 11:10:14 +0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
References: <20111024161910.8048.2279.idtracker@ietfa.amsl.com> <p06240623cae622c69b08@[172.21.1.9]> <4EC0AD84.5060502@dcrocker.net> <p0624062acae67c872451@[172.21.1.9]> <4EC0D517.3030400@dcrocker.net> <p0624062fcae6925f6fe6@[172.21.1.9]> <4EC0F17B.5020003@dcrocker.net> <4EC0F1E7.7000602@stpeter.im> <4B9A1851-31B5-4147-A284-77A63664401C@mnot.net> <4EC18DEB.6090003@stpeter.im> <4EC190AA.3000705@dcrocker.net> <2D961F5E-1613-4B8B-AD35-FF2077DFF8B8@mnot.net>
In-Reply-To: <2D961F5E-1613-4B8B-AD35-FF2077DFF8B8@mnot.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 18 Nov 2011 19:10:34 -0800 (PST)
Cc: Randall Gellens <rg+ietf@qualcomm.com>, apps-discuss@ietf.org
Subject: Re: [apps-discuss] status and name
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Nov 2011 03:10:52 -0000

With apologies, I'm going to try to follow a serious path in spite of that not
being what you intended:

    Note that the problem is not with ICANN but with the population of folk
making registrations.  THEY provide the initiative for the misguided model(s) of
name use..

    That fact can be an important lesson for anyone else doing work involving
name/string registration.

d/


On 11/19/2011 9:34 AM, Mark Nottingham wrote:
> Perhaps this could be communicated to ICANN.
>
> /me ducks
>
> On 14/11/2011, at 2:05 PM, Dave CROCKER wrote:
>> On 11/15/2011 5:53 AM, Peter Saint-Andre wrote:
>>> The same principle has emerged from discussions on the "Happy IANA" list
>>> (i.e., registration of parameters does not imply advancement along a
>>> standardization path). I sense a theme...
>>
>> It's actually closer to a principle.
>>
>> It is extremely natural to want names to carry deep semantics.  It's an
>> easy place to put parametric information.  Unfortunately it seems to
>> always create problems, most notably when there is a change in state, which
>> is exactly the concern we are dealing with in the draft.


-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net