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

John C Klensin <john-ietf@jck.com> Thu, 21 May 2015 03:10 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 A5A8D1ACEAA for <ianaplan@ietfa.amsl.com>; Wed, 20 May 2015 20:10:33 -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 wxt1zXIXUQnJ for <ianaplan@ietfa.amsl.com>; Wed, 20 May 2015 20:10:32 -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 D8BFD1ACEAB for <ianaplan@ietf.org>; Wed, 20 May 2015 20:10:31 -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 1YvGsL-000F6d-Rp; Wed, 20 May 2015 23:10:25 -0400
Date: Wed, 20 May 2015 23:10:20 -0400
From: John C Klensin <john-ietf@jck.com>
To: Milton L Mueller <mueller@syr.edu>, 'Christian Huitema' <huitema@microsoft.com>
Message-ID: <9F5DADEC7B0F069BA5BCB67A@JcK-HP8200.jck.com>
In-Reply-To: <a78386a2666240d48be0aba1fb543e75@EX13-MBX-13.ad.syr.edu>
References: <5550F809.80200@cisco.com> <55511064.2000300@gmail.com> <CAOW+2dvBb4n4W=q7NoO_V1X+JoqvO1TWYBqPAEseY9T7vybj9Q@mail.gmail.com> <CAKFn1SEkBSfk5H5ZjOqfiyaxPak_62cNcRR-SDFH2JJ2HxQumA@mail.gmail.c > <om@mac.com> <59edd953c1d349cfa377bcd72b514b7f@EX13-MBX-13.ad.syr.edu> <C3D17473E06220755959AB78@JcK-HP8200.jck.com> <27ed27614a6b47729043610f09ac197f@EX13-MBX-13.ad.syr.edu> <88F741BF3D4C2A597622A70C@JcK-HP8200.jck.com> <44A0F230-A98C-4060-88E2-B20FE1DE1FC5@isoc.org> <14ff00ba1aae45f2a8f4befb896e2a08@EX13-MBX-13.ad.syr.edu> <D17525F2-190B-4D00-AEBE-5AD96BA79E79@arin.net> <A026656644A030B7130B94B5@JcK-HP8200.jck.com> <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>
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/UeJL5yHrKmKpf1y6P0qIxGN_-QU>
Cc: "'ianaplan@ietf.org'" <ianaplan@ietf.org>
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 03:10:33 -0000


--On Wednesday, May 20, 2015 21:53 +0000 Milton L Mueller
<mueller@syr.edu> 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. 
> 
> To put the question more bluntly: 
> 
> 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? 
>...

Milton, it seems to me that the way you are characterizing the
situation brings us perilously close to a situation in which the
names community will block any transition in which the PTI,
defined however the names community decides to define it, is not
the main element.  My understanding of the charge from NTIA is
that all of the relevant communities need to reach consensus on
a single plan for their to be a transition.  From my point of
view, proposals/positions from the protocol and numbers
community were put on the table and both of those groups
concluded that their proposals were compatible.  Those proposals
also made minimal changes to the existing system and, at least
IMO, explained and justified the changes they did want to make.
Then the names community (or at least the CWG) comes along with
a proposal with big gaps, large changes, and little explanation
or rationale and they (or at least you) say "accept PTI or no
transition" and tell the IETF community what questions we are
allowed to ask and that, because PTI is a done deal, our only
option is to secede.

Speaking again for myself only, I don't see it that way.   What
I do see is a demonstration of a concern that a few of us have
had for some time -- the possibility that, freed of external
oversight, portions of the names community would make decisions
about what is in their best interest without much regard for
other needs or the opinions of other communities (except
possibly in the form of the names community's opinion of what
those communities should want and need) and then, because of the
way ICANN is structured, impose their view on everyone else.  

If that is where we are then, again from my point of view, we
are conclusively demonstrating that we are not ready for a
transition that removes external oversight (whether via NTIA or
otherwise) and that conclusion is largely independent of whether
the IETF and/or numbers community agree to whatever the PTI
model turns out to be.

I think that would be very sad.

   best,
     john