Re: registries and designated experts

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 12 June 2012 18:13 UTC

Return-Path: <brian.e.carpenter@gmail.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 8BF3B21F858A for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 11:13:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.252
X-Spam-Level:
X-Spam-Status: No, score=-101.252 tagged_above=-999 required=5 tests=[AWL=0.439, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, 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 GR1C47bFK523 for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 11:13:55 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id D7E4621F8535 for <ietf@ietf.org>; Tue, 12 Jun 2012 11:13:54 -0700 (PDT)
Received: by eaaq13 with SMTP id q13so3184603eaa.31 for <ietf@ietf.org>; Tue, 12 Jun 2012 11:13:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=/5lgSOI0puNECqdsYRcRd0l/AIE/q2D9jyEltkm5Z74=; b=LJmWbH74Qjt2CcVFtulNDw4C3h2GC+sEro/wh3PJW7CZCFThJjCcgU4kQpDIQzzHOd W7b07Yj8D/vnDdnmq2yAbR3Y0W/NDHUNz2Uga19cPUESYKTINa89+UAU5ch9WUC1+1UW 8knR+TvX5bE1PEtJEoQZiJxuteUultGHBfSxilQVVq5nDM7Ok1Cyy8eAQbrQHDPRofu1 QoD2lzkCoVKP/jKJjHX9DceBJNpj8VsqQShEwK26n/5WhT0YjKIjrpwTzYG/xupWS3xg jnGITBSST6rGI66koPeRgKcR9tgqpQ6Ndqf0MFOlgAtCt28OYJkBNTa5OGL8f1SVI+TG 8ghA==
Received: by 10.14.98.204 with SMTP id v52mr6901986eef.198.1339524833848; Tue, 12 Jun 2012 11:13:53 -0700 (PDT)
Received: from [192.168.1.67] (host-2-102-219-50.as13285.net. [2.102.219.50]) by mx.google.com with ESMTPS id h53sm67071459eea.1.2012.06.12.11.13.51 (version=SSLv3 cipher=OTHER); Tue, 12 Jun 2012 11:13:52 -0700 (PDT)
Message-ID: <4FD786DC.4090403@gmail.com>
Date: Tue, 12 Jun 2012 19:13:48 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: registries and designated experts
References: <4FCDD499.7060206@it.aoyama.ac.jp> <4FCDE96E.5000109@cs.tcd.ie> <4FD7083A.6080502@it.aoyama.ac.jp> <4FD74FFC.3050905@stpeter.im> <6.2.5.6.2.20120612073602.09c8cbb8@resistor.net>
In-Reply-To: <6.2.5.6.2.20120612073602.09c8cbb8@resistor.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
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, 12 Jun 2012 18:13:55 -0000

On 2012-06-12 17:31, SM wrote:
> Hi Peter,
> At 07:19 12-06-2012, Peter Saint-Andre wrote:
>> By my reading, the "happiana" discussions [1] over the 12+ months have
>> led most participants to the conclusion that registration does not imply
>> standardization, and that it's not the role of the designated expert to
>> act as a gatekeeper with respect to the technical merits of the
>> technologies that trigger registration requests. It might be good to
>> have a wider discussion about the purpose of registries and the role of
>> designated experts, but IMHO it's not correct to conclude that a
>> technology is acceptable just because the designated expert didn't
>> object to the registrations related to that technology.
> 
> I'll +1 the above.
> 
> In a recent review the path followed by the draft is Standards Action
> whereas the assignment policy is Expert Review.  Explaining to the
> authors that they should not use the assigned value isn't a worthwhile
> effort given that they have already been through the gate to get the
> value.  The Designated Expert did his job; that is to see that the
> requirements were met instead of acting as gatekeeper.  If you reject
> assignment requests people will find it simpler not to register the
> values.  If you accept the request people might consider that the
> specification is fine.
> 
> The reasons provided for managing a namespace are:
> 
>   - prevent the hoarding of or unnecessary wasting of values
> 
>   - provide a sanity check that the request actually makes sense
> 
>   - interoperability issues
> 
> The above is at odds with standardization.  The last reason does not
> apply for Expert review.

I don't understand that statement. RFC 5226 says, in Section 2 about
"Why Management of a Namespace May Be Necessary":

"  A third, and perhaps most important, consideration concerns potential
   impact on the interoperability of unreviewed extensions."

One of the specific considerations for designated experts in section 3.3
is

"      - the extension would cause problems with existing deployed
        systems."

It seems clear that interoperability is a primary concern for any
expert review.

    Brian