Re: [Ianaplan] making ARPA explicit (Re: draft-ietf-ianaplan-icg-response-02 working group last call)

[Jefsey <[e-mail]>]

So, even geniuses can be erroneous.

".arpa" is a IANA function managed by the IAB and operated by the 
IANA operator under RFC 2960 Section 4.3. where all the IANA/IETF 
infrastructural names should be migrated.

Chairs committed that this WG would consider the other communities' 
proposals, including my Draft. I cannot do anything to force anyone 
to discuss it, but as it is an other community's proposal it will be 
forwarded independently to the ICG, to the NTIA and to the multiple 
political stakeholders. It would be sad it would be alone in 
promoting the existing IETF solution because an entire WG of leaders 
simply ignore the IETF standardization process modalities.

Anyway, the Libre Intelligent Internet Use global community of my 
local (IEN 48 meaning) surroundings, will use the experience gathered 
by Mike Robert at ICANN, including ICP-3 and the RFC 3172 agreement, 
as indicated in its 
http://iuwg.net/images/draft-iuwg-intlnet-sdo-registry-relations.01.pdf.

Best
jfc


At 18:36 06/11/2014, Brian E Carpenter wrote:
>>On 06/11/2014 15:04, Bernard Aboba wrote:
>> > Yes, .ARPA was left out and needs to be put in.
>
>I'll be picky. .ARPA is one of the technical exceptions to the
>policy issues and is therefore already included in the term "protocol
>parameters registries." So if you want to mention it, it
>should definitely be
>
>IETF Response: the protocol parameters registries including the .ARPA domain.
>
>Regards