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

Eliot Lear <lear@cisco.com> Sat, 23 May 2015 06:10 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 B1EEA1A90D7 for <ianaplan@ietfa.amsl.com>; Fri, 22 May 2015 23:10:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 IWpanTabwncF for <ianaplan@ietfa.amsl.com>; Fri, 22 May 2015 23:10:48 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DF4B1A90C4 for <ianaplan@ietf.org>; Fri, 22 May 2015 23:10:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2325; q=dns/txt; s=iport; t=1432361449; x=1433571049; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=HPqVdyX94TElTAIOxO4/OmC69aASZWV1d3jOsfK/IvY=; b=L9ajkht5be4vhOOOMXcUNqiQvFsv89gL8trTuHPYtLSQaF3rrt+G2NQc 3DSJcZOKiw0qngqDwh5xZk/8dj3+Ly082QvS1mgdtVdCLMwz9SLmv1rf1 8VnY/DMS03IjOcSDuHCj2RrqHPzupSJ21DI3CiImhrWI2muh2NODOjvFO U=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D9AwDmGGBV/4YNJK1cgxCEUcADCYdQAoEwOBQBAQEBAQEBgQqEIwEBBCNOBxELGAkWCwICCQMCAQIBRQYBDAgBARCIGK9HpAYBAQEBAQEBAwEBAQEBAQEbizqEIWuCaIFFAQSVGoFDhzqHeI83I2GDGTyCeAEBAQ
X-IronPort-AV: E=Sophos;i="5.13,480,1427760000"; d="asc'?scan'208";a="152771165"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-4.cisco.com with ESMTP; 23 May 2015 06:10:48 +0000
Received: from [10.86.250.11] (bxb-vpn3-523.cisco.com [10.86.250.11]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id t4N6AjgR011804; Sat, 23 May 2015 06:10:46 GMT
Message-ID: <556019E6.9020401@cisco.com>
Date: Sat, 23 May 2015 08:10:46 +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.7.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, "'ianaplan@ietf.org'" <ianaplan@ietf.org>
References: <5550F809.80200@cisco.com> <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> <555CEDFF.5010601@gmail.com> <51E8C05D9CFB07754ECD13F5@JcK-HP8200.jck.com> <DM2PR0301MB065543B4DCBCB751656B563DA8C20@DM2PR0301MB0655.namprd03.prod.outlook.com> <a78386a2666240d48be0aba1fb543e75@EX13-MBX-13.ad.syr.edu> <555DE2E7.2010201@cs.tcd.ie>
In-Reply-To: <555DE2E7.2010201@cs.tcd.ie>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="0exEVoOngDGjC7jM0rE7g9dbxQ0AwIe6l"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/rN2EPggqK3PPfZo_TII7T7jnG14>
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: Sat, 23 May 2015 06:10:52 -0000

Stephen,

You asked this question:

On 5/21/15 3:51 PM, Stephen Farrell wrote:
> So I'd be interested in hearing from other folks [...] who think that the IETF ought do something directly involving the PTI (e.g. to re-open the MoU to change the partner involved or something.)

To me I think there are aspects of moving to the PTI model which are
quite attractive over time, because depending on how it is implemented,
the PTI can provide for better separation from the naming community and
associated politics.

But there are many many risks involved with adopting that approach in
haste.  Maybe there will be opportunities over time to take advantage of
the benefits, once we have some understanding as to how to manage the
drawbacks that have been discussed on this list (there may be more).  My
point is that we should not forever shut the door on the approach.

It's not clear to me that this involves reopening the MoU.  Most of the
hard lifting has to be done at ICANN and how they are organized, and how
funding works.  Some of that probably should be considered by them now,
because it may be harder to fix later, but as we have something that
works reasonably well now, and some of those issues are quite knotty,
and there is only so much time in the day, if the transition is to
happen, ICANN may need to address other more pressing concerns.

Eliot