Re: [Ianaplan] control and negotiation (was Re: draft-ietf-ianaplan-icg-response-02 working group last call)

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 04 November 2014 20:52 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 60E091A7025 for <ianaplan@ietfa.amsl.com>; Tue, 4 Nov 2014 12:52:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.758
X-Spam-Level: *
X-Spam-Status: No, score=1.758 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
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 idI-nsJy5Wy2 for <ianaplan@ietfa.amsl.com>; Tue, 4 Nov 2014 12:52:35 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A9D81A0130 for <ianaplan@ietf.org>; Tue, 4 Nov 2014 12:52:35 -0800 (PST)
Received: from mx1.yitter.info (nat-07-mht.dyndns.com [216.146.45.246]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 382258A031 for <ianaplan@ietf.org>; Tue, 4 Nov 2014 20:52:34 +0000 (UTC)
Date: Tue, 04 Nov 2014 15:52:32 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ianaplan@ietf.org
Message-ID: <20141104205232.GK29755@mx1.yitter.info>
References: <GLEAIDJPBJDOLEICCGMNMENGCNAA.rhill@hill-a.ch> <5458C4C3.6050605@meetinghouse.net> <D07E3874.135E9F%jon.peterson@neustar.biz> <54592D96.8040807@gmail.com> <54593423.4010507@meetinghouse.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <54593423.4010507@meetinghouse.net>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/hpRRYxqulfdz3qiuz1Q1K3oY6TQ
Subject: Re: [Ianaplan] control and negotiation (was Re: draft-ietf-ianaplan-icg-response-02 working group last call)
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: Tue, 04 Nov 2014 20:52:36 -0000

On Tue, Nov 04, 2014 at 03:16:35PM -0500, Miles Fidelman wrote:
> that the IETF needs to step up, and assert itself, and assume the
> responsibilities that go with being the standards body it purports to be.
> 

Oy, the Boss of Internetz again.  The IETF does in fact assume the
responsibilities of being that standards body.  The responsibilities
are entirely in the realm of making standards that people can actually
use, rather than standards that ensure continued existence of a paid
bureaucracy.

This "actually used" criterion is the _exact_ reason I keep saying
that control over iana.org isn't something worth trying to get,
because it cannot make any difference to future action.  If in the
event of a registry split there is co-operation, the pointer will be
there.  If there is controversy, we'll have to do an emergency
transition anyway.

Every time I say that, someone says, "Well, in the event of a
controversial split, having a contract term will put you in a better
legal position," as though that is any kind of help.  In the case of
such a split, we will need to put up a new registry at a new URI
immediately, while the legal situation works itself out.  Having done
that, what possible utility will there be in going back?

This isn't being wishy-washy.  It's being clear-eyed and cold about
what _actually_ would be important in the event of a controversial
split.  Keeping a trademark will be among the very least of our
worries, and I think focussing on it is focussing on the form rather
than the content.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com