Re: [Internetgovtech] an initial proposal wrt IANA developments

John Curran <jcurran@istaff.org> Fri, 21 March 2014 03: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 67B701A090C for <internetgovtech@ietfa.amsl.com>; Thu, 20 Mar 2014 20:49:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 ghjHobJDTY0V for <internetgovtech@ietfa.amsl.com>; Thu, 20 Mar 2014 20:49:25 -0700 (PDT)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) by ietfa.amsl.com (Postfix) with ESMTP id 770841A0805 for <internetgovtech@iab.org>; Thu, 20 Mar 2014 20:49:25 -0700 (PDT)
Received: from 1-193.icannmeeting.org ([199.91.193.1] helo=[10.196.204.240]) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1WQqSJ-000L2P-Pf; Fri, 21 Mar 2014 03:49:16 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 199.91.193.1
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX197KACG82MYN3FqOdKQRCOt
Content-Type: multipart/alternative; boundary="Apple-Mail=_22C44021-75CF-493B-975E-C07C6085FDD2"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: John Curran <jcurran@istaff.org>
In-Reply-To: <CAL02cgSXy-i5P1k0006hsuG0MCaT+6LUNemB3m1RT=9oG+1BDA@mail.gmail.com>
Date: Fri, 21 Mar 2014 11:49:08 +0800
Message-Id: <46560FA3-2ACF-4DB2-AF2C-528F9F64FE58@istaff.org>
References: <CAL02cgSXy-i5P1k0006hsuG0MCaT+6LUNemB3m1RT=9oG+1BDA@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/internetgovtech/w5Ha-JE2C8nQJMFT7AInBsxJxQA
Cc: internetgovtech@iab.org
Subject: Re: [Internetgovtech] an initial proposal wrt IANA developments
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: Fri, 21 Mar 2014 03:49:28 -0000

On Mar 21, 2014, at 1:54 AM, Richard Barnes <rlb@ipv.sx> wrote:

> Thanks for starting the discussion on this.  It's important that we as an organization understand how the recent NTIA news affects us.  Unfortunately, I disagree pretty fundamentally with the characterization in the text below.  
> The below text seems to suppose or imply that ICANN is changing its behavior to compensate for the lack of NTIA involvement.  That's just false.  Or it should be — since NTIA has had no operational role for a long time, our multistakeholder processes are not affected by their departure.
> 
> I'm not denying that there may be changes over time in how the multistakeholder organizations work or how they relate to one another.  Only that these changes are just part of the natural evolution of the community.  They're not driven by NTIA's decision, so they don't need to be part of this discussion.
> 
> My concern with focusing on change rather than continuity is that it invites trouble.  Saying that there is a "transition" implies that there is some vacuum that needs to be filled by somebody.  That just invites other people to argue that they should get to do NTIA's supposed job (which was actually nothing).  There's no need for anyone to take on additional responsibilities
> 
> Our focus in any statement should be to reaffirm our current processes -- as we have been executing for years. Any changes are simply to strengthen those processes, and should have been done irrespective of the NTIA decision.

Richard - 

   Several of the IETF protocol parameter spaces are general-purpose (i.e. the DNS space, the 
   IP address spaces, etc.) and thus they pose "policy issues" in additional to the technical criteria
   set by the IETF.

   Presently, these particular spaces are administered in a framework which was established by 
   the Internet community and documented by two principal parties: both by the USG/DoC/NTIA
   (via ICANN's formation and the IANA Function contract), and also by the IAB/IETF (via RFC 2860).

   While NTIA's involvement has been extremely light-handed, its presence supports the proposition
   that the various policy bodies in the general-purpose Internet registry system (including ICANN 
   and the RIRs) are not operating completely without oversight, and this is very reassuring to many 
   globally given the importance of the Internet today in societal and economic development.

   So, while I agree with you that the message should be ongoing evolution and continuity,  it is also
   important for the IETF community to maintain some awareness of how its general-purpose identifier 
   spaces are being administered, since their administration is essential to the successful deployment 
   of IETF protocols globally.  Similarly, NTIA's announcement does require specific consideration by 
   this community, to the extent it leads to changes in oversight mechanisms applicable to IETF's 
   general-purpose registries.  (I am optimistic that any changes made will continue to support the 
   success of IETF protocols, but that's presuming that IAB/IETF stays engaged in the discussion...)

/John

Disclaimer: My views alone.