Re: [Internetgovtech] Documents from the ICG Meeting Last Week are Available

Avri Doria <> Mon, 21 July 2014 14:52 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id BAD9A1A014B for <>; Mon, 21 Jul 2014 07:52:23 -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 Zr68QvePm9kN for <>; Mon, 21 Jul 2014 07:52:22 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id E086A1A00B8 for <>; Mon, 21 Jul 2014 07:52:21 -0700 (PDT)
Received: from ([]) by (8.14.4/8.14.4) with ESMTP id s6LEqKRh004499 for <>; Mon, 21 Jul 2014 10:52:20 -0400
Received: (qmail 21531 invoked by uid 0); 21 Jul 2014 14:52:20 -0000
Received: from unknown (HELO ? ( by 0 with ESMTPA; 21 Jul 2014 14:52:20 -0000
Message-ID: <>
Date: Mon, 21 Jul 2014 10:52:14 -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] Documents from the ICG Meeting Last Week are Available
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 14:52:24 -0000


I am not necessarily looking for joint efforts - though it might be
nice, just allowing for any of the communities to produce
recommendations on any of the aspects.

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.  Why does our
process say that they can't make recommendations on that?

Likewise the IETF has great concerns over the allocations of some names
and may want to make a suggestion of how the allocation of names is done
given the IETF's decision that it is able to assign names for protocol
reasons.  That is a tussle waiting in the wings that needs to come out
into the light for all of this assignment of responsibilities.

Yes, the IETF will naturally choose to mostly produce recommendations on
parameters, but need it be limited to that?  Likewise with the other groups.

I have no problem with the notion of an expectation that mostly
parameters will be covered by IETF and names by GNSO and the ccNSO, and
numbers by the NRO.  What I have problems with is the construction of
silo walls that indicate an expectation that others might not have
standing and ability to contribute to the proposed solutions on
particular subjects.

I do not want there to be a possibility that someone calls an
uncomfortable recommendaton out of scope for the organization making it.

As for this have been handed down, I do not remember there ever being a
community wide discussion on slice and dice, just announcements of this
being the way it would be from various leaders.


On 21-Jul-14 10:31, Andrew Sullivan wrote:
> On Mon, Jul 21, 2014 at 10:26:08AM -0400, Avri Doria wrote:
>> I fund this silo approach very problematic and more likely to produce a
>> disjointed set of solutions 
> Where would be the joint whereof you speak?  To put this another way,
> in my opinion protocol parameters belong squarely in the IETF's
> purview, and nobody else's.  Similarly, given the protocols, names
> fall squarely into ICANN's purview, no?  What is the "joint" that
> wouldn't be better solved (in the case of names) by working within the
> ICANN community?  Similarly for number resources, except a different
> community.
> I don't think there's any handed-down-ness about it.  This is a fully
> community-based approach, I think.
> A