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

Eliot Lear <lear@cisco.com> Tue, 19 May 2015 14:59 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 C80641B2FE4 for <ianaplan@ietfa.amsl.com>; Tue, 19 May 2015 07:59:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.529
X-Spam-Level:
X-Spam-Status: No, score=-13.529 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=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 AVWsjIeHoQMQ for <ianaplan@ietfa.amsl.com>; Tue, 19 May 2015 07:59:24 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D56F31B2FC1 for <ianaplan@ietf.org>; Tue, 19 May 2015 07:59:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10307; q=dns/txt; s=iport; t=1432047565; x=1433257165; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=eixhEe3gXfqHk0Y0P638k/C2zXSANtaaj10StnkECDA=; b=MqDybaZZaaGrgF82oAACnCG9mLtOPvJJETGLJHETvGvnOSdzzoD+BG/n JAmajh/WlhM56IKZOuB+OWc4jSeSs6/Iyuvc/sA0+sfVVdnRHT0iRCyJR jOIryOekat7aFCNrrXX9Q2tX7wwy45AUelctd+LIr5L1Cx8OnFFkIb5oF E=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CoBAApT1tV/xbLJq1cDoI3gX2DHsF4h1ACgXYSAQEBAQEBAYEKhCIBAQEEIwpLEQsVAwkWCAMCAgkDAgECATQRBgEMBgIBARCIGK5SpC8BAQEBAQEBAQEBAQEBAQEBAQEBAQEXizqFCwGCaIFFAQSUe4FDhyyBJ4ZFi0uDWSNhgSkcgRRAPDGCRwEBAQ
X-IronPort-AV: E=Sophos;i="5.13,458,1427760000"; d="asc'?scan'208,217";a="486279760"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 19 May 2015 14:59:23 +0000
Received: from [10.61.71.148] (ams3-vpn-dhcp1940.cisco.com [10.61.71.148]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t4JExL1h023425; Tue, 19 May 2015 14:59:21 GMT
Message-ID: <555B4FC8.3050403@cisco.com>
Date: Tue, 19 May 2015 16:59:20 +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: Milton L Mueller <mueller@syr.edu>, "'ianaplan@ietf.org'" <ianaplan@ietf.org>
References: <5550F809.80200@cisco.com> <a7cee9a6045a4f65966aa33ba02a854d@EX13-MBX-13.ad.syr.edu> <555AD643.10303@cisco.com> <b94401a6fbf34d2b9002366ea1fffd10@EX13-MBX-13.ad.syr.edu>
In-Reply-To: <b94401a6fbf34d2b9002366ea1fffd10@EX13-MBX-13.ad.syr.edu>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="2aMfB5117Sb1pq3fjOlrXLXmJ8d1sW2W7"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/h9HSYHCyGQUMfouRdNwzpHKSPjU>
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: Tue, 19 May 2015 14:59:29 -0000


On 5/19/15 4:49 PM, Milton L Mueller wrote:
>
>  
>
>  
>
> *From:*Eliot Lear [mailto:lear@cisco.com]
>
> I'm not sure I parsed you entirely correctly here, but the concern I
> was raising was this: the ICANN fee and the naming gold rush have
> cross-subsidized the other functions, most notably protocol
> parameters.  If names pulls out of the PTI, what incentives and
> mechanisms would remain in place to continue to fund the other
> functions at the same service levels?  That simply was not a concern
> before.  It is (at least to me) now.  I don't think it is
> insurmountable, especially over a longer term, but perhaps some
> groundwork may need to be laid within the naming context now, even if
> the IETF or RIRs do not choose to go directly to the PTI.
>
>  
>
> And yes, it is true that the IETF could always have terminated the
> arrangement, and then we would have had a funding problem of our
> making.  But that would have been the IETF's decision, not the naming
> community's.  This situation is different.
>
>  
>
> MM: Eliot, let me rephrase your concern this way. Tell me if you think
> it is fair and then we will have a clearer basis for discussion.
>
>  
>
> You and Alissa are saying that you want the protocols IANA functions
> to remain outside of PTI and in ICANN because that way, the names
> community will have no choice as to whether it can withdraw from the
> arrangement, whereas IETF can decide whether to withdraw at any time.
>
>  
>
> Correct?
>
>
>

I would state it differently: I am all for the names community to have
choices, but let's agree that there are ramifications for the other
communities, and those ramifications should be addressed and not swept
under the rug.

Eliot