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

Eliot Lear <lear@cisco.com> Wed, 13 May 2015 06:05 UTC

Return-Path: <lear@cisco.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 554A21AC3E6 for <ianaplan@ietfa.amsl.com>; Tue, 12 May 2015 23:05:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 huL6uxZdJvuV for <ianaplan@ietfa.amsl.com>; Tue, 12 May 2015 23:05:48 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E43961AC3E1 for <ianaplan@ietf.org>; Tue, 12 May 2015 23:05:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3226; q=dns/txt; s=iport; t=1431497148; x=1432706748; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=a1DojctYPp0y73b5d2aeKODCWEoh8q3eOJc4cgZ7UBo=; b=ezAm5v++dHcBgNf7n9HOhEht5kkD2w4ovczJZFuQcbRaj0SSqZYTeScA t1PeVMnDe8kYk0AR9OgwxNP44XBgpAWMfSCBueyk7LwCd9AVE8Plo4RTa GNnlddPhCJqFykN6QLCp5jH+cM7YySf6/R1lUzuXhgin0x8tmEc25Q6LO U=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CyBACC6FJV/xbLJq1cg3+DYMISh10CEoFcEwEBAQEBAQGBCoQhAQEEI08GEQsOCgkMCgsCAgkDAgECAUUGAQwIAQEQiBi1ZpI3AQEBAQEBAQMBAQEBAQEBG4s5hQwKgl6BRQEElF6BP4Mlg3+HY48TI2GBBYITPIJ3AQEB
X-IronPort-AV: E=Sophos;i="5.13,419,1427760000"; d="asc'?scan'208";a="471653213"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 13 May 2015 06:05:46 +0000
Received: from [10.61.211.148] ([10.61.211.148]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t4D65jI0005711; Wed, 13 May 2015 06:05:45 GMT
Message-ID: <5552E9B8.7040206@cisco.com>
Date: Wed, 13 May 2015 08:05:44 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ianaplan@ietf.org
References: <5550F809.80200@cisco.com> <20150511203447.GF73721@mx2.yitter.info>
In-Reply-To: <20150511203447.GF73721@mx2.yitter.info>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="bVosF8t4RIDghCMDh8uQ4u4DTLPXcTc7k"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/YfMy4iRdcBaUKE2Cvofa_C71TBU>
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, 13 May 2015 06:05:50 -0000

Hi Andrew,

On 5/11/15 10:34 PM, Andrew Sullivan wrote:
> On Mon, May 11, 2015 at 08:42:17PM +0200, Eliot Lear wrote:
>> to retain a direct relationship with ICANN, and NOT the PTI[4].  The IAB
>> could do the same, but then it seems to me that the value of the PTI
>> itself is diminished.
> Why?  The names community presumably wants this because it offers some
> mechanism to them (in this case a way to break the policy from
> implementation, if need be).  It needn't have anything to do with us.

It does, of course.  At the very least the terms of RFC 2860 needs to be
considered as part of this. Beyond that, it seems like the vision here
is the correct one, that policy is separated from execution, but the
financing of it in particular bothers me (see my note to Milton).
>> indirect and shared costs as well.  What isn't in those costs is an
>> allocation across functions.  At the very least we should have that
>> information.
> But what if we can't get it?  The breakout that we got from ICANN, it
> seemed to me inside the CWG, was itself rather hard to get.
> Apparently ICANN doesn't account things this way.

If you don't ask, you don't get.  I have heard various people over the
years talk about this in rough terms.  Now the names proposal has at
least something.  The simple question to ask is this: how much of that
$6 million is used for protocol parameters?  It's not an unreasonable
question.

>
>>   * Under this new arrangement, does it make sense to continue the
>>     relationship with ICANN as it stood before or does it make sense to
>>     go directly to PTI?
>>   * If the arrangement is with PTI, should we seek a budgetary
>>     separation, and what would be the complexities of that?
> If you need ot answer question 2 in order to answer question 1, then
> it seems obbvious to me that if we want to get this done in a
> reasonable time frame the answer to 1 is "leave it alone".

At the moment I would tend to agree, but would still want to ask the
above question.   I'd also suggest that feedback be given that if the
PTI is intended to take on more than just names over time, some amount
of thought be given to how the concerns of long term stability of the
other functions should be addressed.

Eliot