Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP

Sam Hartman <hartmans-ietf@mit.edu> Tue, 01 February 2011 20:08 UTC

Return-Path: <hartmans@mit.edu>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B14E13A6E78; Tue, 1 Feb 2011 12:08:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.919
X-Spam-Level:
X-Spam-Status: No, score=-102.919 tagged_above=-999 required=5 tests=[AWL=-0.654, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nRT9QzOE690M; Tue, 1 Feb 2011 12:08:50 -0800 (PST)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by core3.amsl.com (Postfix) with ESMTP id DB3043A6E58; Tue, 1 Feb 2011 12:08:49 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 1C6D72028C; Tue, 1 Feb 2011 15:10:08 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 42B32432C; Tue, 1 Feb 2011 15:12:01 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Joe Touch <touch@isi.edu>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com> <4D421795.70505@isi.edu> <tslbp2vh8ig.fsf@mit.edu> <4D485E2B.4080201@isi.edu>
Date: Tue, 01 Feb 2011 15:12:01 -0500
In-Reply-To: <4D485E2B.4080201@isi.edu> (Joe Touch's message of "Tue, 01 Feb 2011 11:25:31 -0800")
Message-ID: <tslk4hjfram.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: tsvwg@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>, IESG IESG <iesg@ietf.org>, Sam Hartman <hartmans-ietf@MIT.EDU>, IETF discussion list <ietf@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 20:08:50 -0000

>>>>> "Joe" == Joe Touch <touch@isi.edu> writes:

    Joe> On 2/1/2011 11:14 AM, Sam Hartman wrote:
    Joe> ...
    >> Joe, the IESG had a fair amount of negative experience with this
    >> style of review just before I joined; this type of review was
    >> just about out of the process leading to blocking objections when
    >> I joined as an AD.
    >> 
    >> I think that being able to discuss concerns with reviewers and
    >> being able to consider potential conflicts and other issues mean
    >> that an open dialogue with identified reviewers is an important
    >> part of our process. Anonymous contributions may have their place
    >> in the WG process, but I don't think they should have a place in
    >> expert review oor blocking objections to documents.  So, as an
    >> individual I strongly support making expert reviewers identities
    >> public.

    Joe> Such reviews occur elsewhere in the IETF as well; it's not a
    Joe> requirement that every review include a list of all consulted
    Joe> parties. This is no different. IANA is the one making the
    Joe> decision of how to use the advice they receive.

Joe, RFC 5226 disagrees with you fairly significantly.
I draw your attention in particular to section 3.2, and particularly
call our attention to several points made there:

* The designated expert is responsible for initiating and coordinating
  the review.

* Designated experts are expected to be able to defend their *decisions*
  to the IETf community

* The process is not intended to be secretive

* Experts make a single clear recommendation to IANA

* In cases of deadlock IESG may be pulled in to resolve disputes

* When IANA receives conflicting advice, chair of pool of experts  gives
  clear *instructions* to IANA.
On page 10, the expert review criteria  requires approval of a
  designated expert.

I submit based on the above that the experts rather than IANA are making
the decision; the expert has the responsibility of justifying and
defending their decision. Moreover anonymous expert reviews violate two
BCP requirements: they tend to a secretive process and they do not
facilitate the expert defending their decision to the IETF community.

Having read RFc 5226 my objection to anonymous expert reviews is much
stronger than when I first read Cullen's message.