Re: [Internetgovtech] Cross community

John Curran <jcurran@istaff.org> Tue, 22 July 2014 11:49 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 186BF1A0AD5 for <internetgovtech@ietfa.amsl.com>; Tue, 22 Jul 2014 04:49:41 -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 jF97zjgq_xRO for <internetgovtech@ietfa.amsl.com>; Tue, 22 Jul 2014 04:49:40 -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 DF1231A00FE for <internetgovtech@iab.org>; Tue, 22 Jul 2014 04:49:39 -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 1X9YZe-000LQY-VU; Tue, 22 Jul 2014 11:49:39 +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: U2FsdGVkX18MPjCyJoTZou4qxX2KGv7f
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: John Curran <jcurran@istaff.org>
In-Reply-To: <53CE4B39.1090202@acm.org>
Date: Tue, 22 Jul 2014 07:49:37 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <13B40B76-5D7E-4288-82E3-7162795936C1@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>
To: Avri Doria <avri@acm.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/internetgovtech/HRrPHVFqBwm8RXyiUjgvlXE22SI
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: Tue, 22 Jul 2014 11:49:41 -0000

On Jul 22, 2014, at 7:30 AM, Avri Doria <avri@acm.org> wrote:

> On 22-Jul-14 06:00, Suzanne Woolf wrote:
>> NTIA today has nothing to do with "accountability mechanisms for each
>> of the parties administering each parameter space" under IETF policy
>> management, and touches only a very small handful of general purpose
>> parameter spaces associated with IETF protocols (DNS and IP).
> 
> I disagree.  NTIA provides a giant accountability function.
> 
> Just about everyone goes running to NTIA whenever something they don't
> like happens.  And the fine folks at NTIA finesse the situation and get
> things back on the right track.  I believe it happens all the time.

That might happen with respect to DNS general-purpose identifiers, but such
is consequential of ICANN being in all of the roles at once when it comes to
DNS (coordination/accountability, policy development, policy administration, 
registry update, and registry publication), whereas the original blueprint 
called DNS policy development to be primarily arms-length to ICANN in an 
independent body.  Mash all of those roles together, and you get lots of 
accountability concerns and opportunities for NTIA involvement.  

Both the RIRs and IETF operate with policy development external to ICANN;
NTIA has not, to my knowledge, ever been involved in "finessing" any issue
in those areas.

> NTIA are the adults in the room and we better have adequate

> accountability all around when they step out of their role.

It's worth noting that (for IP addresses and protocol parameters) that we've 
had that solid accountability via membership structures, long-established 
use of open/transparent practices, and contractual separation of roles from 
the IANA since day one, so it would indeed be nice to see some of that sort 
of progress in the DNS area.

Please remember that both the IETF and several of teh Regional Internet 
registries predate ICANN and have represented "running code" long before
the IANA functions contract came into being.

Thanks!
/John

Disclaimer: My views alone.