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

Milton L Mueller <mueller@syr.edu> Tue, 19 May 2015 14:51 UTC

Return-Path: <mueller@syr.edu>
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 313B51A910B for <ianaplan@ietfa.amsl.com>; Tue, 19 May 2015 07:51:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.31
X-Spam-Level:
X-Spam-Status: No, score=-2.31 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 yhbhQcsf8zFs for <ianaplan@ietfa.amsl.com>; Tue, 19 May 2015 07:51:39 -0700 (PDT)
Received: from smtp1.syr.edu (smtp1.syr.edu [128.230.18.82]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E07361B2FA7 for <ianaplan@ietf.org>; Tue, 19 May 2015 07:49:13 -0700 (PDT)
Received: from EX13-MBX-11.ad.syr.edu (ex13-mbx-11.ad.syr.edu [128.230.108.142]) by smtp1.syr.edu (8.14.7/8.14.7) with ESMTP id t4JEnAZa017156 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 19 May 2015 10:49:10 -0400
Received: from EX13-MBX-13.ad.syr.edu (128.230.108.144) by EX13-MBX-11.ad.syr.edu (128.230.108.142) with Microsoft SMTP Server (TLS) id 15.0.847.32; Tue, 19 May 2015 10:49:08 -0400
Received: from EX13-MBX-13.ad.syr.edu ([128.230.108.144]) by EX13-MBX-13.ad.syr.edu ([128.230.108.144]) with mapi id 15.00.0847.030; Tue, 19 May 2015 10:49:08 -0400
From: Milton L Mueller <mueller@syr.edu>
To: 'Eliot Lear' <lear@cisco.com>, "'ianaplan@ietf.org'" <ianaplan@ietf.org>
Thread-Topic: [Ianaplan] CWG draft and its impact on the IETF
Thread-Index: AQHQjBpMEY3mz9BPA0WCyomEcYFu4J133IVAgAtGPICAAEnNMA==
Date: Tue, 19 May 2015 14:49:07 +0000
Message-ID: <b94401a6fbf34d2b9002366ea1fffd10@EX13-MBX-13.ad.syr.edu>
References: <5550F809.80200@cisco.com> <a7cee9a6045a4f65966aa33ba02a854d@EX13-MBX-13.ad.syr.edu> <555AD643.10303@cisco.com>
In-Reply-To: <555AD643.10303@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [128.230.182.126]
Content-Type: multipart/alternative; boundary="_000_b94401a6fbf34d2b9002366ea1fffd10EX13MBX13adsyredu_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.14.151, 1.0.33, 0.0.0000 definitions=2015-05-19_05:2015-05-19,2015-05-19,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1505190186
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/D2tmV6Pn0kDD5H8mIsTg8gVbi4s>
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:51:41 -0000


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?