[Iana-transition] Draft of ARIN proposal for review and comments

Fri Nov 21 12:48:42 EST 2014

attached word doc with edits and notes.

Page 3 - paragraph starting "The Address Supporting Organization Advisory
Council (ASO AC)"
Noting David's edit that this should simply be Address Council.

The paragraph suggests the the ASO AC reviews Global Policy Process to
ensure significant viewpoints have been considered.

Actually it does three things.
1. reviews Global Policy Process to ensure the process for each RIR has
been followed
2. ensure significant viewpoints have been considered
3. in the event that non-identical policy is passed in each region, that
the unified text is not substantively different that what the communities
passed.

--

Page 5 - "The agreement should have the IANA operator perform
administration of the unallocated portions of the Internet number
registries on behalf of the Regional Internet Registries and specify
service levels and performance reporting  commensurate with current
mechanisms."

I wonder what conclusion the community will draw from the text suggesting
that the contract should include SLAs and performance reporting
commensurate with current mechanisms.

Does this suggest the current SLAs and reporting are adequate?
I suspect the community does not know what the current SLAs are (although
reporting is pretty clear).

Does this instead suggest that ICANN is doing a fine job with the IANA
operations WRT number resources, and
the current SLAs and reporting may or may not be adequate, but we do not
see addressing this as critical, we should keep the current structure in
place for now, and modify it in the future.

If we want to change the SLAs and reporting, should this require opening up
and resigning the contract?

Might it be better easier to change SLAs with a standalone living document,
that he contract refers to?

--

Open, Transparent, and Bottom-up

I was expecting everywhere I saw "open" to also see transparent and
bottom-up.
Page 5 - paragraph starting "While it has not been utilized..."

"the RIRs should reaffirm their commitment to open, transparent,
[bottom-up,] and accountable global number policy."

--

Page 5 - paragraph starting "While it has not been utilized..."
Shouldn't this affirmation also be made to the RIR communities?

Page 7 - point 1.

"1. 1. Global number policy development which is open, transparent, and
[bottom-up] to any and all participants."

--

Page 5 - end of  paragraph starting "While it has not been utilized..." and
the next paragraph.
I think an ASO AC review of RIR accountability is a good idea.  The
conclusion of this work should be supported by each of the communities, and
implemented by the RIR prior to the transition of the NTIA contract.

This should include a review of RIR governance.

This should also include a review of the oversight of IANA functions WRT
the contract with ICANN for the number related operations, and oversight of
governance of ICANN WRT ratification of Global Policy Ratification.

I expect this work would include a formal process for modification of IANA
function SLA metrics and reporting, as well as a formal process of
reviewing IANA operations reports and declaration of (non-)compliance, and
appropriate community (or membership) oversight.

___Jason

On Fri, Nov 21, 2014 at 11:25 AM, Jason Schiller <jschiller at google.com>
wrote:

> Comments in line,
>
> __Jason
>
> On Fri, Nov 21, 2014 at 10:42 AM, David Huberman <
> David.Huberman at microsoft.com> wrote:
>
>>  Channeling my inner Megan Kruse with grammar nitpicks, and also some
>> substantive editorial comments:
>>
> I support all grammar fixes.
>
>
>>
>> Page 2: "which is associated with" should be "which are associated with"
>> since the previous noun was "zones" plural.
>>
>>
>>  Page 2: inconsistent capitalization of "Internet Number Resource
>> Policies" throughout the document.  So far I see:
>>     Internet number resource policies
>>
>>     Internet Number Resource Policies
>>
>>
>>  Page 3: First full sentence.  "describe the proposed global policy"
>> doesn't agree in singular/plural with the preceding text.  Perhaps replace
>> "the proposed" with "a proposed" to denote that results occur when a policy
>> is agreed upon?
>>
>>
>>  Page 3: Paragraph 3 - you defined ASO Advisory Council (ASO AC) and
>> then in paragraph 3 keep mentioning ASO *Address* Council.  I am not 100%
>> sure, but don't you mean to use the defined initialism "ASO AC" in all
>> instances of the third paragraph?
>>
>>
>>  Page 3: Paragraph 4: you can substitute "Regional Internet Registries"
>> with the defined initialism RIR.  This is true throughout the document -
>> you may want to search-and-replace "Regional Internet Registries".  Just an
>> idea.
>>
>>
>>   Page 4: "The five <RIRs> are intimately familiar with..."  I
>> think this sentence is a run-on, as the second clause doesn't depend on the
>> first clause. I'm not sure. Recommend breaking it into two different
>> sentences, or at least using a semi-colon if you are expressing a singular
>> idea.
>>
>>
>>  Substantive comment, not editorial:  Page 5, the phrase "commensurate
>> with current mechanisms" - I think this should be stricken.  The paragraph
>> goes on to define specific parameters. I think it's better to define all
>> the parameters of the service levels and performance reporting, rather than
>> rely on associations ("commensurate with") that aren't explicitly defined
>> right there.
>>
> I think if you really want to keep the "commensurate with current
> mechanisms" text, then it is relevant in the NTIA Requirements section, as
> part of the theme about building on an existing
>
>
>>
>> Substantive comment:  Page 5, third paragraph, starting with "While it
>> has not been utilized".   What is the purpose of this paragraph?  In what
>> way does reaffirmation by the RIRs of their commitment to these goals
>> germane to this document?
>>
> I think this section is about the NTIA's ability to revoke the contract to
> perform the IANA function, and this capability will pass from the NTIA to
> the RIRs.  I think the rest of this section is an attempt to address how
> such a function could be invoked and the oversight of such.  It points to
> existing process, and existing oversight, and a commitment to the ASO-AC
> completing a review and making recommendations.
>
> I think this boils down to two points.
> 1. We have pretty good oversight (appropriate for the NTIA Requirements
> section)
> 2. The ASO-AC will review RIR oversight, and shore up any issues with RIR
> oversight
> (which in general is fine if the work successfully concludes before
> transition)
>
>>
>>   Page 5/6 transition - you've already defined this term, ASO AC.
>>
>>
>>
>>
>>   *David R Huberman*
>> Microsoft Corporation
>> Principal, Global IP Addressing
>>   ------------------------------
>> *From:* iana-transition-bounces at arin.net <
>> iana-transition-bounces at arin.net> on behalf of Sweeting, John <
>> john.sweeting at twcable.com>
>> *Sent:* Friday, November 21, 2014 7:15 AM
>> *To:* iana-transition at arin.net
>> *Subject:* [Iana-transition] Draft of ARIN proposal for review and
>> comments
>>
>>  All,
>>
>>  As members of the CRISP team representing the ARIN region Bill
>> Woodcock, Michael Abejuela and I held an initial call on Nov 17th to
>> discuss direction. Pulling from the comments that were already posted to
>> this list as well as others Michael Abejuela put together the attached
>> draft response to the RFP that we would like to use as the baseline to
>> start our ARIN region discussion. Please review the document and provide
>> input via this list. I want to thank Michael for doing this and also
>> commend him on, what I think, is a very good first draft. We look forward
>> to your input. Thanks in advance for taking the time to review and comment.
>>
>>  Your ARIN CRISP members - Bill, Michael and John
>>
>>
>>
>>
>> ------------------------------
>> This E-mail and any of its attachments may contain Time Warner Cable
>> proprietary information, which is privileged, confidential, or subject to
>> copyright belonging to Time Warner Cable. This E-mail is intended solely
>> for the use of the individual or entity to which it is addressed. If you
>> are not the intended recipient of this E-mail, you are hereby notified that
>> any dissemination, distribution, copying, or action taken in relation to
>> the contents of and attachments to this E-mail is strictly prohibited and
>> may be unlawful. If you have received this E-mail in error, please notify
>> the sender immediately and permanently delete the original and any copy of
>> this E-mail and any printout.
>>
>> _______________________________________________
>> Iana-transition mailing list
>> Iana-transition at arin.net
>> http://lists.arin.net/mailman/listinfo/iana-transition
>>
>>
>
>
> --
> _______________________________________________________
> Jason Schiller|NetOps|jschiller at google.com|571-266-0006
>
>

-- 
_______________________________________________________
Jason Schiller|NetOps|jschiller at google.com|571-266-0006
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/iana-transition/attachments/20141121/4df407ac/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: schiller-IANA-ICG-RFP-ARIN-DRAFT-response[1].pdf
Type: application/pdf
Size: 143231 bytes
Desc: not available
URL: <https://lists.arin.net/pipermail/iana-transition/attachments/20141121/4df407ac/attachment.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: schiller-IANA-ICG-RFP-ARIN-DRAFT-response[1].docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 244220 bytes
Desc: not available
URL: <https://lists.arin.net/pipermail/iana-transition/attachments/20141121/4df407ac/attachment.docx>