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

Ted Hardie <ted.ietf@gmail.com> Wed, 20 May 2015 22:50 UTC

Return-Path: <ted.ietf@gmail.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 5BA241AC3B7 for <ianaplan@ietfa.amsl.com>; Wed, 20 May 2015 15:50:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 y2_j_-jTeVM0 for <ianaplan@ietfa.amsl.com>; Wed, 20 May 2015 15:50:56 -0700 (PDT)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17ECF1A8A0E for <ianaplan@ietf.org>; Wed, 20 May 2015 15:50:56 -0700 (PDT)
Received: by wicmx19 with SMTP id mx19so170921349wic.0 for <ianaplan@ietf.org>; Wed, 20 May 2015 15:50:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JY974/DHMkvUCx4BSVOZsltRG7wJEOXkP13KfTzG05Q=; b=f4IsMV9uYAK/8XYmGHtP3R1gAazmBeL8tOKtLXj9o7C8oJplzhdkrWsBaL4GxFFjE6 q5H2jbCiF1lCGtPuIPvQCSP4TchQ624z/93Xhiaz6e9Bovkip5mWDmuEoILmhZlrNZ9V d8xrjcgKjvuf90zbOILUTA5yidACjmM6To/O2gPj+LcOYfun/FgLVvxYgfR6Fb0dV59F VfSTm01J2j+P2ElbhxK52X48wkVDX6/1cUcoNDEj+kj1jGPgPjtVt37IOAvR8rHUzNwd uYWrYnpTTr87YKm4afGOQl5WQ+H+thuXlWz/ba6k94OsSPRgWqzOyhpMfBq6aSmMNqOr ZDHw==
MIME-Version: 1.0
X-Received: by 10.194.187.170 with SMTP id ft10mr47064297wjc.26.1432162254828; Wed, 20 May 2015 15:50:54 -0700 (PDT)
Received: by 10.195.17.163 with HTTP; Wed, 20 May 2015 15:50:54 -0700 (PDT)
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> <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>
Date: Wed, 20 May 2015 15:50:54 -0700
Message-ID: <CA+9kkMDDUuc7ViXPHy60d52j5KmGwFku4Dh1-11sLaVD9wwKmg@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Milton L Mueller <mueller@syr.edu>
Content-Type: multipart/alternative; boundary="047d7bb03a9275c78d05168b42c3"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/YNyv4XuCPsOQCIxAxuYSDuyBEts>
Cc: Christian Huitema <huitema@microsoft.com>, "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: Wed, 20 May 2015 22:50:59 -0000

On Wed, May 20, 2015 at 2:53 PM, Milton L Mueller <mueller@syr.edu> wrote:

>
> > -----Original Message-----
> >
> > There is an underlying question: would the system be less stable if
> > protocols numbers, IP addresses, and domain names were managed
> > by three different structures? Or would it be more stable?
>
> That is the right question.
>
> Although not all comments are in yet, it looks like the concept of a
> legally separate PTI has sufficient support from the names community to
> become part of the plan (indeed, the most salient dissents are calling for
> more separation, not less). And it's also clear that numbers community is
> not objecting to this structure and does not see any risk in it, though
> they have made it clear that they want to continue to contract directly
> with ICANN.
>
>
​Your statement is not clear.  Are you saying that the numbers community is
not objecting to this structure for the names community and does not see
any risk in that community choosing that for its use?  Given that they have
made it clear they wish to contract directly with ICANN, this seems a
logical inference, but it is not clear that it is the one you have drawn.​


> 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.
>
>
​That is a very curious idea of secession.  The IETF community came to
consensus on a document that was completed prior to the PTI proposal being
made.  Having the IETF community continue to contract with ICANN is not
secession.​



> 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?
>
>
​This may be blunt, but it is also wrong.  The IETF has declared itself
satisfied with the work of  IANA and contracting with ICANN for the
relevant SLAs.  We are not adding anything to the transition by keeping
that set of arrangements.


> Or does it want the protocols functions to move with the names and number
> functions into PTI?
>
>
That's the real choice.
>
> How anyone can portray the first option as less destabilizing than the
> second, is beyond me. I view the second one as simpler. I hope no one at
> this point is pretending that the status quo ante is an option. It isn't.
>
>
​The *status quo ante* needs ​a time reference to be sensible.  *ante *the
decision of the NTIA to solicit proposals?  *ante* the publication of the
IANAPLAN and CRISP documents?  *ante* the decision of the names community
to propose PTI?

Ted




> > Having system concentrated creates a concentration of
> > power that increases risks for abuse.
>
> Remember that while all three functions might be provided by the same
> organization, each community would have its own distinct contract for those
> functions. In that respect there is a pretty powerful check/balance in
> place against abuse of concentrated power. Furthermore, extracting the
> supply of the IANA functions from an organization that is overwhelmingly
> dominated by the money and politics of names policy development is also a
> step in the direction of less concentration of power.
>
> _______________________________________________
> Ianaplan mailing list
> Ianaplan@ietf.org
> https://www.ietf.org/mailman/listinfo/ianaplan
>