Re: [Ianaplan] CWG draft and its impact on the IETF

Andrew Sullivan <ajs@anvilwalrusden.com> Thu, 21 May 2015 00:18 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8498C1ACD95 for <ianaplan@ietfa.amsl.com>; Wed, 20 May 2015 17:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QMg9jLuh9Hnz for <ianaplan@ietfa.amsl.com>; Wed, 20 May 2015 17:18:54 -0700 (PDT)
Received: from mx2.yitter.info (mx2.yitter.info [50.116.54.116]) by ietfa.amsl.com (Postfix) with ESMTP id 56C1C1ACDBA for <ianaplan@ietf.org>; Wed, 20 May 2015 17:18:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id DAF84106CB for <ianaplan@ietf.org>; Thu, 21 May 2015 00:18:41 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2C0B9xc3Z6G9 for <ianaplan@ietf.org>; Thu, 21 May 2015 00:18:41 +0000 (UTC)
Received: from mx2.yitter.info (unknown [IPv6:2400:8901::f03c:91ff:fe37:9daf]) by mx2.yitter.info (Postfix) with ESMTPSA id 51D47106B3 for <ianaplan@ietf.org>; Thu, 21 May 2015 00:18:40 +0000 (UTC)
Date: Thu, 21 May 2015 00:18:36 +0000
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ianaplan@ietf.org
Message-ID: <20150521001835.GA18401@mx2.yitter.info>
References: <ad1d0707ff1b44eb9e48fef18d8e1268@EX13-MBX-13.ad.syr.edu> <687222FF507C0D3EDBD9CAAA@JcK-HP8200.jck.com> <000001d091f7$266de3f0$7349abd0$@ch> <51ce19bc2a93443586adcdd2fac3888a@EX13-MBX-13.ad.syr.edu> <555BD28F.10402@gmail.com> <97E5874491A30994EC386C37@JcK-HP8200.jck.com> <555CEDFF.5010601@gmail.com> <51E8C05D9CFB07754ECD13F5@JcK-HP8200.jck.com> <DM2PR0301MB065543B4DCBCB751656B563DA8C20@DM2PR0301MB0655.namprd03.prod.outlook.com> <a78386a2666240d48be0aba1fb543e75@EX13-MBX-13.ad.syr.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <a78386a2666240d48be0aba1fb543e75@EX13-MBX-13.ad.syr.edu>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/lDAqfdY29xLj8RN0grkSaQVk7d4>
Subject: Re: [Ianaplan] CWG draft and its impact on the IETF
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IANA Plan <ianaplan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ianaplan/>
List-Post: <mailto:ianaplan@ietf.org>
List-Help: <mailto:ianaplan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 May 2015 00:18:55 -0000

Hi,

On Wed, May 20, 2015 at 09:53:21PM +0000, Milton L Mueller wrote:

> This means that comments questioning "what problem PTI is trying to solve" or "whether we should move in the PTI direction" are quite misdirected. We are not discussing whether PTI will happen, but whether IETF will choose to secede from it. 
> 

I don't understand how that is a helpful position to take.  People
asking, "What problem is this trying to solve?" and, "Should we move
in that direction?" are not doing that for the fun of it.  Most of us
don't have a professional interest in governance models _qua_
governance model, though I am aware that at least one of us does.

Instead, they are asking perfectly reasonable clarifying questions --
reasonable partly because the CWG released for public comment a
proposal that was _in its own admission_ (indeed, stated in the text
itself) full of incomplete answers, and unsettled and controversial
issues.  It's hardly surprising that people should ask the sorts of
questions they're asking.  

> Does IETF want to add to the transition a new process of extracting itself from the current IANA department and leaving the protocols registry as a stand-alone service within ICANN? 
> 
> Or does it want the protocols functions to move with the names and number functions into PTI? 
> 
> That's the real choice. 

It's not the "real choice"; in fact it's a false alternative.  It
seems to me that, without quite a lot of additional detail, it's more
or less impossible to know whether it would be better to continue the
MoU with ICANN, or to undertake a new agreement with a PTI, or to
initiate a completely new arrangement including an RFP process, or
just to take the entire thing over and bring it back inside the IETF.
None of that should be news to you, since I in fact made similar
arguments on the CWG list quite some time ago.

And none of this answers the question, either, of what the correct
long-term arrangement ought to be.  Given the terrible lack of detail,
it's entirely possible that whatever the PTI arrangements end up being
will be unstable and poorly-suited to the long term health of the
relevant registries, even if they are perfectly servicable and useful
for the purposes of transition.  As I've said repeatedly in the CWG
context, we had better be assuming that the arrangement can be altered
again in the future if such needs turn up.  If it cannot, then that
suggests we're doing it wrong.  Practical arrangements should never be
so brittle.

Best regards,

A

-- 
--
Andrew Sullivan
ajs@anvilwalrusden.com
Awkward access to mail.  Please forgive formatting problems.