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

Olaf Kolkman <kolkman@isoc.org> Tue, 12 May 2015 07:10 UTC

Return-Path: <kolkman@isoc.org>
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 891781A1AE3 for <ianaplan@ietfa.amsl.com>; Tue, 12 May 2015 00:10:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 LR8bNUR-OXRN for <ianaplan@ietfa.amsl.com>; Tue, 12 May 2015 00:10:44 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0081.outbound.protection.outlook.com [207.46.100.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 443921A1ABC for <ianaplan@ietf.org>; Tue, 12 May 2015 00:10:44 -0700 (PDT)
Authentication-Results: gmail.com; dkim=none (message not signed) header.d=none;
Received: from [185.49.141.211] (185.49.141.211) by DM2PR0601MB732.namprd06.prod.outlook.com (10.242.126.140) with Microsoft SMTP Server (TLS) id 15.1.154.19; Tue, 12 May 2015 07:10:41 +0000
From: Olaf Kolkman <kolkman@isoc.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Tue, 12 May 2015 09:10:29 +0200
Message-ID: <CC008D24-9F27-4946-8BD5-3840CA5B2C82@isoc.org>
In-Reply-To: <55511064.2000300@gmail.com>
References: <5550F809.80200@cisco.com> <55511064.2000300@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_5125F18A-1ACB-49A8-BF85-DBC136AC0812_="; micalg="sha1"; protocol="application/pkcs7-signature"
X-Mailer: MailMate (1.9.1r5084)
X-Originating-IP: [185.49.141.211]
X-ClientProxiedBy: DB4PR04CA0005.eurprd04.prod.outlook.com (25.160.41.15) To DM2PR0601MB732.namprd06.prod.outlook.com (10.242.126.140)
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0601MB732;
X-Microsoft-Antispam-PRVS: <DM2PR0601MB732D03906AAF0966A537078D9DA0@DM2PR0601MB732.namprd06.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005006)(3002001); SRVR:DM2PR0601MB732; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0601MB732;
X-Forefront-PRVS: 0574D4712B
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6049001)(24454002)(252514010)(77096005)(46102003)(86362001)(575784001)(50226001)(66066001)(15975445007)(568964001)(110136002)(36756003)(189998001)(50986999)(82746002)(19580395003)(5890100001)(5001960100002)(122386002)(87976001)(92566002)(76176999)(5001920100001)(15974865002)(62966003)(40100003)(84326002)(77156002)(83716003)(2950100001)(19580405001)(512874002)(19617315012)(42186005)(33656002)(3940600001)(72826003)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR0601MB732; H:[185.49.141.211]; FPR:; SPF:None; MLV:sfv; LANG:en;
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 12 May 2015 07:10:41.9480 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0601MB732
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/-10VNDL9L3sHkXSKq60bKvPtyHk>
Cc: "ianaplan@ietf.org" <ianaplan@ietf.org>, Eliot Lear <lear@cisco.com>
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, 12 May 2015 07:10:46 -0000

On 11 May 2015, at 22:26, Brian E Carpenter wrote:

> I think it's simple enough. If the proposed PTI is a wholly owned
> subsidiary of ICANN, the overarching IETF agreement still needs to be
> with ICANN. Obviously operational additions such as the SOW and SLA
> could be with the subsidiary.

I am not there.

Looking at this from a perspective from separation of _policy_ and _implementation_ functions on could argue that the names community has chosen to make a clear separation of ICANN as the _policy_ body and the PTI as the _implementation_ body.

To me there is some logic for the IETF (as a _policy_ body) to contract with the PTI.

Obviously, there still will need to be coordination between the _policy_ bodies but that coordination needs to be there regardless of what the _implementation_ bodies are (yes that is plural, it reflects the current situation of having multiple organizations implementing parts of IANA).

I think it makes much more sense to have an SLA with the _implementation_ body (PTI) without another organization in the middle. There is an esthetic to that setup that I think bring transparency.

But I guess it depends a bit about what type of 'overarching IETF agreement' you are talking about, the cooperation with ICANN is not only about the IANA SLA.



—Olaf




- - -
Olaf Kolkman
Chief Internet Technology Officer
Internet Society
kolkman@isoc.org  www.internetsociety.org
LinkedIn: OlafKolkman, Twitter: @Kolkman
- - -