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

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 20 May 2015 20:26 UTC

Return-Path: <brian.e.carpenter@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 4E72F1A9084 for <ianaplan@ietfa.amsl.com>; Wed, 20 May 2015 13:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 ZJHmY8mx0nVF for <ianaplan@ietfa.amsl.com>; Wed, 20 May 2015 13:26:38 -0700 (PDT)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) (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 69CE51A8F37 for <ianaplan@ietf.org>; Wed, 20 May 2015 13:26:38 -0700 (PDT)
Received: by pdbqa5 with SMTP id qa5so81251052pdb.0 for <ianaplan@ietf.org>; Wed, 20 May 2015 13:26:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=H+V436JTh7v1wZlVbkPEt9yZH5xUCfq5Vh7XrOidoP8=; b=eWhfuajA1kWiT1UtjfCKn/UZfp0RJhzsad6+VIbOTxWNuWgNJ/MnlxAPKDVY9BAptO Rv5hGBQ1eHP0LIU6LLNNMK6thzhWj9KB55tKNKcz9+yEpACif7WXMNnRCeya4wI18r0o hy34+u/fAwJcjyADuuzomweiV6qChmlnk90vb4F4ey903rDb65XZwDZqZazqPInODVcA So6LhuPKlmDPBdf1fqZidcQJvqAkTXlDR4+/uonuUnt+o01fsvRMrDW+rgLJq0TIoNh9 fERoHwzir/dwXyNxgmgGYpq/hNqw3aES5iO7yLhsXFoRU37QiRuhzetKqn/mGhill/MH AgnA==
X-Received: by 10.70.54.103 with SMTP id i7mr67741583pdp.134.1432153598180; Wed, 20 May 2015 13:26:38 -0700 (PDT)
Received: from ?IPv6:2406:e007:5eca:1:28cc:dc4c:9703:6781? ([2406:e007:5eca:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id pn6sm17011412pdb.72.2015.05.20.13.26.34 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 May 2015 13:26:36 -0700 (PDT)
Message-ID: <555CEDFF.5010601@gmail.com>
Date: Thu, 21 May 2015 08:26:39 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, Milton L Mueller <mueller@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>
In-Reply-To: <97E5874491A30994EC386C37@JcK-HP8200.jck.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/PE8CNaye-hCfjXarXCsyhJtcmmo>
Cc: "'ianaplan@ietf.org'" <ianaplan@ietf.org>, 'Olaf Kolkman' <kolkman@isoc.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 20:26:40 -0000

Excuse front posting, but I just want to say that John is correct;
of course Plan B would be neither desirable nor smooth sailing, but there
are circumstances in which it would be the IETF's only choice.

Regards
   Brian

On 21/05/2015 06:08, John C Klensin wrote:
> Brian,
> 
> A quick comment on this analysis only:
> 
> --On Wednesday, May 20, 2015 12:17 +1200 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
> 
>> ...
>> I've been mulling over the implications of this. Either PTI
>> will be controlled by ICANN or it won't. If it *is*
>> effectively controlled by ICANN, the IETF can sit back and
>> relax until our SLA is no longer met, in which case we go to
>> Plan B (i.e. no change in the state that has existed for 15
>> years).
>>
>> If PTI is *not* effectively controlled by ICANN, we are
>> straight into Plan B: giving notice to ICANN and bidding out a
>> protocol parameter services contract, with PTI as an obvious
>> bidder, hopefully at zero cost. (I would seriously expect
>> several zero- cost bids to show up.)
> 
> The difficulty with "Plan B" is that the costs to the IETF and
> the IETF's user community, or invoking it and making some sort
> of transfer would be considerable and disruptive.  Good planning
> and cooperation from ICANN (or PTI or some other current
> operator) could significant reduce that pain, but not either
> eliminate it or reduce it to something trivial.  As a result
> "SLA is no longer met" is less like to be a simple binary
> decision but a collection of evaluations and tradeoffs about
> whether things are sufficiently out of hand, or showing enough
> of a patter of deterioration, to justify making that move.  
> 
> Even if PTI were, by your definition, not controlled by ICANN,
> under most scenarios I'd assume the position of the IETF/IAOC
> would be to stick with PTI-IANA unless (or until) something went
> seriously wrong.  Making a change just because the
> organizational structure changes seems to me unlikely in
> practice (I note that neither of us would be part of making the
> decision other than as members of the community so there are no
> commitments in that prediction).   
> 
> In either case, the IETF community would need to evaluate costs
> and risks of the scenario.  I don't believe that PTI implies
> enough advantages for us (or anyone else) to justify that
> investment.   Milton doesn't believe that is a legitimate reason
> for not going ahead.  And that leaved us at a little bit of an
> impasse that your analysis does not address.
> 
>    john
> 
>