Re: [Internetgovtech] Cross community

Avri Doria <> Mon, 21 July 2014 18:12 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 5A6A81A0175 for <>; Mon, 21 Jul 2014 11:12:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 1.465
X-Spam-Level: *
X-Spam-Status: No, score=1.465 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id YefXtv88OH3A for <>; Mon, 21 Jul 2014 11:12:00 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 7F61A1A00B5 for <>; Mon, 21 Jul 2014 11:12:00 -0700 (PDT)
Received: from ([]) by (8.14.4/8.14.4) with ESMTP id s6LIBwta019780 for <>; Mon, 21 Jul 2014 14:11:58 -0400
Received: (qmail 9487 invoked by uid 0); 21 Jul 2014 18:11:58 -0000
Received: from unknown (HELO ? ( by 0 with ESMTPA; 21 Jul 2014 18:11:58 -0000
Message-ID: <>
Date: Mon, 21 Jul 2014 14:11:52 -0400
From: Avri Doria <>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
References: <> <> <> <> <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 140721-0, 07/21/2014), Outbound message
X-Antivirus-Status: Not-Tested
Subject: Re: [Internetgovtech] Cross community
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Internet Governance and IETF technical work <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 21 Jul 2014 18:12:04 -0000


On 21-Jul-14 12:37, John Curran wrote:
> On Jul 21, 2014, at 10:52 AM, Avri Doria <> wrote:
>> > There are cross over concerns, for example in ICANN the Advisory
>> > Committees (At Large, Government, Security etc) have purview to advise
>> > on addresses as well as numbers and even parameters when it concerns
>> > tech that will be used to manage those names and numbers.

> Could you elaborate some on the above concepts?  I understand how there is 
> potential for consultation with such advisory committees if considered 
> appropriate by the ICANN Board (and as provided for in the ASO Global Policy 
> Development process), but the more typical method of engagement is directly 
> in the policy development processes taking place in each RIR region... in 
> this way, the input is considered closer to those affected by the outcome.  

The ASO is part of ICANN.  Anything it does, is open to comment by any
of the Adivisory Committees (AC).  I am assuming that the ASO and the
NRO are not identical as they both got seats on the ICG.  That indicates
that there are ICANN concerns with numbers that may be more
appropriately dealt by ICANN participants.

I understand that the RIRs all have their own regional participants, but
at the global level, there is very little stakeholder participation,
with the ICANN Advisory Committees being the only possible venue for
such concerns.  doea the NRO provide a multistakeholder venue at the
global level or is that the task of the ASO?  Because the ASO is part of
ICANN, the ACs have a voice in their activities and thus have a say in
the accountability methods for those issues.

On a specific example that I pay more attention to than numbers, the
IETF has recently asserted its ability to take names out of the general
pool of labels available for TLDs by declaring them to be protocol
artifacts, i.e. RFC 6761 on Special Use Names.  To assert IETF having
full control of this interface without any accountability to others is
problematic.  While this may just be an edge case from the IETF protocol
perspective, it could could be a huge issue from the ICANN perspective.

It is just not as simple as one group per each issue.   And I am sure
that as we go on, we will find other issues of commonality that need to
be explored.

And I still don't know who submits proposals on the .arpa, or .int issue
and the root server issues.

In a world where the various tech and the various policy issues are so
intertwined and interdependent, I think siloing is risky and should be


BTW, i have sent too many messages to this list today and figure i
better stop before someone speaks to me sternly.