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

John C Klensin <john-ietf@jck.com> Mon, 18 May 2015 14: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 CA3871A0AF1 for <ianaplan@ietfa.amsl.com>; Mon, 18 May 2015 07: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 3tjZhfu5ykCY for <ianaplan@ietfa.amsl.com>; Mon, 18 May 2015 07:57:39 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.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 28D081A0173 for <ianaplan@ietf.org>; Mon, 18 May 2015 07: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 1YuMTw-000MkH-Tl; Mon, 18 May 2015 10:57:28 -0400
Date: Mon, 18 May 2015 10:57:23 -0400
From: John C Klensin <john-ietf@jck.com>
To: John Curran <jcurran@arin.net>, Milton L Mueller <mueller@syr.edu>
Message-ID: <A026656644A030B7130B94B5@JcK-HP8200.jck.com>
In-Reply-To: <D17525F2-190B-4D00-AEBE-5AD96BA79E79@arin.net>
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>
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/yogMQaRG5QiH3N7G8vK53cS0zg8>
Cc: 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: Mon, 18 May 2015 14:57:41 -0000


--On Monday, May 18, 2015 14:08 +0000 John Curran
<jcurran@arin.net> wrote:

>>          "So Mental Model 1 and 2 could co-exist, as long as
>> ICANN has PTI perform the protocol and number registries work
>> on ICANN's behalf."

>   i.e. an internal subcontracting from ICANN to PRI versus
> agreement _assignment_ from   ICANN to PTI.   A internal
> subcontracting arrangement is unlikely to be material for the
> IETF   and the RIRs, whereas an agreement assignment is
> visible, has some significant implications,   and would
> require consent of the parties.

Yes.  See the response I just sent to Olaf, but it seems to me
that a "PTI" as a subcontracting arrangement to (more or less)
an internal department is inconsistent with the (apparent) CWG
of separation and independence and, as you have pointed out a
separately-managed and accountable PTI that operates as a
mostly-independent affiliate or subsidary of ICANN would not be
plausible without IETF and address community consent and that
there are reasons why it might not be in the interest of those
bodies to provide that consent.

Assuming that consent will not be lightly or quickly given, the
question for me becomes whether the independent-affiliate
version of the PTI concept is valuable enough to the Names
community to justify splitting up the IANA function.  And, if it
is, whether the result is a sufficiently consistent and coherent
proposals to meet NTIA's transition proposal requirements.

best,
   john