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

Seun Ojedeji <seun.ojedeji@gmail.com> Mon, 18 May 2015 08:28 UTC

Return-Path: <seun.ojedeji@gmail.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 62AEC1A87C5 for <ianaplan@ietfa.amsl.com>; Mon, 18 May 2015 01:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level:
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 aK_8lSUIfO15 for <ianaplan@ietfa.amsl.com>; Mon, 18 May 2015 01:28:18 -0700 (PDT)
Received: from mail-qg0-x233.google.com (mail-qg0-x233.google.com [IPv6:2607:f8b0:400d:c04::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C33701A87C1 for <ianaplan@ietf.org>; Mon, 18 May 2015 01:28:17 -0700 (PDT)
Received: by qgf59 with SMTP id 59so11770258qgf.3 for <ianaplan@ietf.org>; Mon, 18 May 2015 01:28:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=v+Dvx3+B799fZNkZ5Nhb+4FV4xB3wgEROWgwuPIhCiU=; b=TSMoDH2WfURV53L/PbcIDh7SD3J0gbGj7iLucwjoR/9SRi1gs5LHmoVJLyZOnIKgmE NkJeXUsr7VX56W0t3bjXiPvxj5XhrwxdVwWcm/sNezbg5ggcHqhgLexLBFvtWFqn4wq2 0wxuCieZ/UDd/+VEl3XrSuqAbfkOhudTcoQDIHirNoyjiklCjbqVJR8WHwqU/nMVFmjf 5uzynYmDJyuxlwbH9F0iHyIRQmLCWAWYODwXFLWXwxTCJPP+dh8D2o7Han7mv3DVjCUf 6T/ULDaVc3K/R0hGXHPPg3LCwFJ9ohQsbBvTnDHeoOGOGtx9ZxtJPrHfCDl23/hD2qcT /b7g==
X-Received: by 10.140.88.242 with SMTP id t105mr26935797qgd.92.1431937697080; Mon, 18 May 2015 01:28:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.157.20 with HTTP; Mon, 18 May 2015 01:27:46 -0700 (PDT)
In-Reply-To: <44A0F230-A98C-4060-88E2-B20FE1DE1FC5@isoc.org>
References: <5550F809.80200@cisco.com> <55511064.2000300@gmail.com> <CAOW+2dvBb4n4W=q7NoO_V1X+JoqvO1TWYBqPAEseY9T7vybj9Q@mail.gmail.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>
From: Seun Ojedeji <seun.ojedeji@gmail.com>
Date: Mon, 18 May 2015 09:27:46 +0100
Message-ID: <CAD_dc6hN58zCt1sd0NNQ5M0jbZaz-vo=R0n2z=-=_9NkS0UZGg@mail.gmail.com>
To: Olaf Kolkman <kolkman@isoc.org>
Content-Type: multipart/alternative; boundary="001a11c118dec669e4051656f916"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/SQagtMkVMPtmYhWSIRRJmtQ-pAY>
Cc: John C Klensin <john-ietf@jck.com>, Milton L Mueller <mueller@syr.edu>, "ianaplan@ietf.org" <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:28:20 -0000

On Mon, May 18, 2015 at 9:04 AM, Olaf Kolkman <kolkman@isoc.org> wrote:

> On 15 May 2015, at 18:54, John C Klensin wrote:
>
> 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.
>
> 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,
>
For RIR and names, model 1 seem to be the case. However from my observation
of current IETF discussion, it seem there is a "but" in their preferred
version of model 1 as thus:

IETF -> ICANN [-> IANA Department ]

Where oversight(administrative) of IETF related function is not done by PTI

Regards

> —Olaf
>  ------------------------------
>  Olaf M. Kolkman
> On Personal Title.  Twitter: @Kolkman <https://twitter.com/kolkman>
> ------------------------------
>
> _______________________________________________
> Ianaplan mailing list
> Ianaplan@ietf.org
> https://www.ietf.org/mailman/listinfo/ianaplan
>
>


-- 
------------------------------------------------------------------------





*Seun Ojedeji,Federal University Oye-Ekitiweb:      http://www.fuoye.edu.ng
<http://www.fuoye.edu.ng> Mobile: +2348035233535**alt email:
<http://goog_1872880453>seun.ojedeji@fuoye.edu.ng
<seun.ojedeji@fuoye.edu.ng>*

The key to understanding is humility - my view !