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

Olaf Kolkman <kolkman@isoc.org> Mon, 18 May 2015 08:04 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 0C9FF1A8794 for <ianaplan@ietfa.amsl.com>; Mon, 18 May 2015 01:04:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.799
X-Spam-Level:
X-Spam-Status: No, score=0.799 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, 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 3t266JYfBNks for <ianaplan@ietfa.amsl.com>; Mon, 18 May 2015 01:04:49 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0604.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::604]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 732EC1A8789 for <ianaplan@ietf.org>; Mon, 18 May 2015 01:04:49 -0700 (PDT)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=kolkman@isoc.org;
Received: from [185.49.141.211] (185.49.141.211) by BLUPR0601MB723.namprd06.prod.outlook.com (10.141.252.14) with Microsoft SMTP Server (TLS) id 15.1.160.19; Mon, 18 May 2015 08:04:30 +0000
From: Olaf Kolkman <kolkman@isoc.org>
To: John C Klensin <john-ietf@jck.com>
Date: Mon, 18 May 2015 10:04:13 +0200
Message-ID: <44A0F230-A98C-4060-88E2-B20FE1DE1FC5@isoc.org>
In-Reply-To: <88F741BF3D4C2A597622A70C@JcK-HP8200.jck.com>
References: <5550F809.80200@cisco.com> <55511064.2000300@gmail.com> <CAOW+2dvBb4n4W=q7NoO_V1X+JoqvO1TWYBqPAEseY9T7vybj9Q@mail.gmail.com> <CAKFn1SEkBSfk5H5ZjOqfiyaxPak_62cNcRR-SDFH2JJ2HxQumA@mail.gmail.c om> <59edd953c1d349cfa377bcd72b514b7f@EX13-MBX-13.ad.syr.edu> <C3D17473E06220755959AB78@JcK-HP8200.jck.com> <27ed27614a6b47729043610f09ac197f@EX13-MBX-13.ad.syr.edu> <88F741BF3D4C2A597622A70C@JcK-HP8200.jck.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_31BE1FB1-94C9-4949-936C-D9B0DA429F07_="; micalg="pgp-sha1"; protocol="application/pgp-signature"
X-Mailer: MailMate (1.9.1r5084)
X-Originating-IP: [185.49.141.211]
X-ClientProxiedBy: DBXPR04CA0024.eurprd04.prod.outlook.com (10.141.8.152) To BLUPR0601MB723.namprd06.prod.outlook.com (10.141.252.14)
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR0601MB723;
X-Microsoft-Antispam-PRVS: <BLUPR0601MB723BF5463E349FA5D291AFFD9C40@BLUPR0601MB723.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:BLUPR0601MB723; BCL:0; PCL:0; RULEID:; SRVR:BLUPR0601MB723;
X-Forefront-PRVS: 058043A388
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6049001)(199003)(189002)(51704005)(24454002)(512874002)(15975445007)(84326002)(19617315012)(5890100001)(82746002)(19580395003)(105586002)(83716003)(92566002)(2950100001)(42186005)(87976001)(33656002)(40100003)(101416001)(93886004)(5001960100002)(110136002)(5001830100001)(97736004)(81156007)(5001860100001)(4001540100001)(50226001)(122386002)(189998001)(86362001)(64706001)(68736005)(77156002)(62966003)(36756003)(568964001)(46102003)(66066001)(77096005)(50986999)(106356001)(76176999)(7059030)(3940600001)(104396002)(72826003); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR0601MB723; H:[185.49.141.211]; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
Received-SPF: None (protection.outlook.com: isoc.org does not designate permitted sender hosts)
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 18 May 2015 08:04:30.0705 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR0601MB723
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/E_SVKUkVZJlP9XzeUq0QdIeo0ys>
Cc: Milton L Mueller <mueller@syr.edu>, ianaplan@ietf.org
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: Mon, 18 May 2015 08:04:52 -0000

On 15 May 2015, at 18:54, John C Klensin wrote:

> First of all and as far as I can tell, if we ended up with the
> IETF and/or RIRs/NRO having agreements about relevant IANA
> functions with ICANN and the names community having an agreement
> with a PTI for IANA functions that are relevant to them, either
> we end up splitting IANA into two (or three) separate
> organizations or we end up with a picture that looks like:
>
> IETF -> ICANN -> IANA Department
> NRO -> ICANN ->  IANA Department
> Names Community -> PTI -> ICANN -> IANA Department

Working from the thesis that what is confusing to me might be confusing to others. I am going to ask for clarification.

My mental model of the setup that is being discussed here (that is, if I were to determine the current consensus):


```
Mental model 1

IETF -> ICANN [-> IANA blackbox ] 
NRO  -> ICANN [—> IANA blackbox ]
Names Community -> PTI 
```

Where the _IANA blackbox_  and _PTI_ deliver the registry publication and maintenance functions. The reason why I picture an IANA blackbox is because the SLA is with ICANN and how the service is being subcontracted is a detail that the IETF and NRO would not particularly care about as long as the SLA is honored.


Depending on how ICANN sub contracts the IANA services the _IANA Blackbox_ could look in fact be the _PTI_, with the IANA department being a one-to-one mapping to the PTI. And the then looks like:

```
Mental Model 1 - implementation 

IETF -> ICANN [-> PTI ] 
NRO  -> ICANN [—> PTI ]
Names Community -> PTI 
```

Where PTI == the IANA department.

The Names Community is organized within ICANN and there is a funding stream from ICANN to the PTI.

If I understand Milton correctly then he favors:

```
Mental model 2

IETF -> PTI
NRO -> PTI
Names Community -> PTI
```


The picture is a bit more complicated since the Names Community is part of 'ICANN' and the funding of the PTI comes through 'ICANN'.

So here is my clarification question: Am I correct in my understanding that my mental model 1 aligns with where most people on this list are going, and Milton, is my mental model 2 a reasonable representation of your thoughts?


—Olaf




- - -
Olaf M Kolkman
On Personal Title
- - -