Re: [Ianaplan] Fwd: For your Information: CWG-Stewardship Response for Chartering Organization Consideration and Approval

John C Klensin <john-ietf@jck.com> Sat, 20 June 2015 12:57 UTC

Return-Path: <john-ietf@jck.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 C025D1A871C for <ianaplan@ietfa.amsl.com>; Sat, 20 Jun 2015 05:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] 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 aq0wuPviWwVC for <ianaplan@ietfa.amsl.com>; Sat, 20 Jun 2015 05:57:39 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 598741A8715 for <ianaplan@ietf.org>; Sat, 20 Jun 2015 05:57:39 -0700 (PDT)
Received: from [198.252.137.35] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Z6IL0-000NnJ-GV; Sat, 20 Jun 2015 08:57:34 -0400
Date: Sat, 20 Jun 2015 08:57:29 -0400
From: John C Klensin <john-ietf@jck.com>
To: Milton L Mueller <mueller@syr.edu>
Message-ID: <CB03F6BC66083F3F809C97B0@JcK-HP8200.jck.com>
In-Reply-To: <9d673c1e7cc14f68aea47bdbbe887bbb@EX13-MBX-13.ad.syr.edu>
References: <D1A45F80.1B274%grace.abuhamad@icann.org> <90E3156B-428B-4A61-92B7-BAC932842FB5@viagenie.ca> <557F63E2.40302@gmail.com> <20150619155355.GI17513@mx2.yitter.info> <55847B53.60106@gmail.com> <5584C304.9000806@acm.org> <9d673c1e7cc14f68aea47bdbbe887bbb@EX13-MBX-13.ad.syr.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.35
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/Oucn3TBqrOV7pPo_ZQyEhVn2-9Q>
Cc: ianaplan@ietf.org, avri@acm.org
Subject: Re: [Ianaplan] Fwd: For your Information: CWG-Stewardship Response for Chartering Organization Consideration and Approval
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: Sat, 20 Jun 2015 12:57:40 -0000


--On Saturday, June 20, 2015 11:53 +0000 Milton L Mueller
<mueller@syr.edu> wrote:

>...
> I can't take seriously people who say "if we ever have to
> change IFO everything will be so messed up that it won't
> matter who controls the marks;" this is neither logically true
> (one can posit many scenarios in which it isn't) and it is
> obvious that fighting or confusion over the marks would make
> even that bad scenario worse.
>...

Milton,

I agree with the rest of your note and its conclusion, but the
statement above is a strawman, one that I don't think anyone who
has thought through the issues has actually suggested.  

A closer statement of at least one version of the "not
important" hypothesis would go something like:

"Should the IETF conclude that it is necessary to remove the
protocol parameter registries from the responsibilities and
operation of whoever the IANA Function Operation is at the time,
and do so without that operator's full cooperation (presumably
splitting the IANA function in the process), the amount of work
necessary to relocate registries, sort out new operational
arrangements, etc., would be significant enough that the
marginal work to pick a new name, domain, etc., would be
insignificant."

A perhaps-subtle points in the above is that it presumes the
need for a unilateral move against resistance and the splitting
up of the IANA function.  There is an underlying assumption at
the other end of the spectrum of options.  It is that, if
rearrangements were needed in the future in which everyone
involved more or less agreed about, especially if those new
arrangements included keeping the IANA function together, it
would be just about as easy to sort out name and domain-related
issues then as it would be today.  Indeed, it would be likely to
be easier, because we would be dealing with a concrete situation
and a single plan, rather than trying to design systems on the
basis of what might hypothetically happen.

best,
     john