Re: [Internetgovtech] Cross community

John Curran <jcurran@istaff.org> Wed, 23 July 2014 20:56 UTC

Return-Path: <jcurran@istaff.org>
X-Original-To: internetgovtech@ietfa.amsl.com
Delivered-To: internetgovtech@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D44D1B2B7F for <internetgovtech@ietfa.amsl.com>; Wed, 23 Jul 2014 13:56:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 EuCf5uQL-m0s for <internetgovtech@ietfa.amsl.com>; Wed, 23 Jul 2014 13:56:16 -0700 (PDT)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B1671A035A for <internetgovtech@iab.org>; Wed, 23 Jul 2014 13:56:16 -0700 (PDT)
Received: from pool-108-56-179-253.washdc.fios.verizon.net ([108.56.179.253] helo=[192.168.1.10]) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1XA3aB-000C5M-IM; Wed, 23 Jul 2014 20:56:15 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 108.56.179.253
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/3sjUD4eVEAUPAbia2Z6pD
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: John Curran <jcurran@istaff.org>
In-Reply-To: <53D016B6.2020000@gih.com>
Date: Wed, 23 Jul 2014 16:56:11 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <96042C9F-CFBD-434D-990D-F931DEA587AB@istaff.org>
References: <A193D048-2B67-469A-93BA-C61BB362DA75@vigilsec.com> <53CD1E8A.1060804@acm.org> <FA4238C4-ADDC-435F-9591-E3B074C2F6F6@vigilsec.com> <53CD2300.5050307@acm.org> <20140721143105.GH16966@mx1.yitter.info> <53CD291E.1020801@acm.org> <9045EC0A-E123-4CDC-B87F-5BC32C644C85@istaff.org> <53CD57E8.4000909@acm.org> <B7163126-31B6-4CC6-A711-F225051C294A@istaff.org> <53CD8F41.9060909@gih.com> <53CD939D.5020001@cisco.com> <9DE8F705-9748-407D-8E77-7B787ACD9873@gmail.com> <53CE4B39.1090202@acm.org> <53D016B6.2020000@gih.com>
To: Olivier MJ Crepin-Leblond <ocl@gih.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/internetgovtech/RK1rg4wllDkiVqP7IDfZJnbxb5s
Cc: internetgovtech@iab.org
Subject: Re: [Internetgovtech] Cross community
X-BeenThere: internetgovtech@iab.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Internet Governance and IETF technical work <internetgovtech.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/internetgovtech>, <mailto:internetgovtech-request@iab.org?subject=unsubscribe>
List-Archive: <http://www.iab.org/mail-archive/web/internetgovtech/>
List-Post: <mailto:internetgovtech@iab.org>
List-Help: <mailto:internetgovtech-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/internetgovtech>, <mailto:internetgovtech-request@iab.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jul 2014 20:56:18 -0000

On Jul 23, 2014, at 4:10 PM, Olivier MJ Crepin-Leblond <ocl@gih.com> wrote:

> I'd just like to register my agreement with Avri on this.
> 
> Please be so kind to review the table in this document:
> https://www.icann.org/en/system/files/files/iana-transition-scoping-08apr14-en.pdf
> 
> I clearly points to new accountability mechanisms needed for *all*
> functions.

The scoping document calls for "defining accountability mechanisms 
that would serve to replace the current stewardship role played by 
NTIA to ensure ICANN’s performance of the IANA functions based on 
the agreements and/or policies provided by the respective bodies 
(IETF, GNSO, RIRs, ASO, ccTLDs, ccNSO)."

In short, before one can meaningfully define any "new accountability 
mechanisms" with respect to protocol parameters or IP addresses that
would "replace the current stewardship role played by NTIA", you'll
first want to confirm that there is an operative NTIA stewardship 
role in these spaces to be replaced, i.e., some NTIA accountability 
mechanisms aside from the referenced agreements with the IAB & RIRs.
Otherwise, you stand to risk replacing the existing, well-functioning
IANA accountability mechanisms to these communities with something 
"new" and hence by definition unproven.

Thanks!
/John

Disclaimer: My views alone.