[Internal-cg] Questions to send - today and tomorrow

Thu Sep 24 18:00:54 UTC 2015

Thanks, Russ. Does that apply to these questions to the CWG as well (which Alan sent yesterday)?

> Q: The CWG-Stewardship proposal uses the terms "IANA Functions Operator" and "IFO" in a way that appears to refer to the operator of the IANA Naming Functions, and not necessarily to the operator of other IANA functions, such as the IANA Numbering Functions or the IANA Protocol Parameters Functions.  Please could you clarify whether or not these terms, in the CWG-Stewardship proposal, are intended to refer only to the names portion of the IANA functions.
> 
> Q: Please could you clarify whether or not the Customer Standing Committee (CSC) applies only to the names portion of the IANA functions.
> 
> Q: Please could you clarify whether or not the IANA Functions Review (IFR) and Special IFR apply only to the names portion of the IANA functions.
> 
> Q: The .ARPA domain is used for special purposes.  Please could you clarify whether or not the .ARPA domain will be included in the CSC and IFR processes.

> Q: Please could you clarify whether or not compliance by ICANN and/or PTI is mandatory when decisions or recommendations are made by an IFR or Special IFR process.

Thanks,
Alissa

> On Sep 24, 2015, at 9:44 AM, Russ Housley <housley at vigilsec.com> wrote:
> 
> For the comments that we are sending to CRISP and IANAPLAN, I do not think we expect updated proposals.  Rather, we just want confirmation of our interpretation.
> 
> Russ
> 
> 
> 
> On Sep 23, 2015, at 4:15 PM, Alissa Cooper wrote:
> 
>> Updated doc attached <https://www.dropbox.com/s/jy5o5gfnrp6i9iv/questions-for-OCs-v2.docx?dl=0 <https://www.dropbox.com/s/jy5o5gfnrp6i9iv/questions-for-OCs-v2.docx?dl=0>>. I propose to send CWG questions 1-5 after 23:59 UTC today, and send the rest after 20:00 UTC tomorrow, to give the ICG one more day to review and finalize them.
>> 
>> I incorporated an edit from Joe on the cooperation question.
>> 
>> Alissa
>> 
>> <questions-for-OCs-v2.docx>
>> 
>>> On Sep 23, 2015, at 11:23 AM, Russ Mundy <mundy at tislabs.com <mailto:mundy at tislabs.com>> wrote:
>>> 
>>> Alissa,
>>> 
>>> Thanks for incorporating the changes - I agree that adding the Daniel disclaimer is a good addition.  I think that I’ll have a little time later today to look at the rest of them later today but doubt that I’ll see other things.
>>> 
>>> Russ
>>> 
>>> On Sep 23, 2015, at 9:32 AM, Alissa Cooper <alissa at cooperw.in <mailto:alissa at cooperw.in>> wrote:
>>> 
>>>> I made one edit to include the disclaimer that Daniel had suggested and that we discussed at the F2F about setting expectations concerning further public comment:
>>>> 
>>>> "Some of the questions below include requests or suggestions for amendments to the text of the CWG proposal as reflected in Part 1 of the combined proposal. The ICG would like to state explicitly that we do not expect a further ICG public comment period to be necessary on the combined proposal if these amendments are made. While the ICG reserves the right to seek further public comment if we receive extensive amendments from the operational communities, we do not expect to do so at this time."
>>>> 
>>>> 
>>>> Alissa
>>>> 
>>>> <questions-for-OCs-v1.docx>
>>>> 
>>>>> On Sep 23, 2015, at 6:06 AM, Alissa Cooper <alissa at cooperw.in <mailto:alissa at cooperw.in>> wrote:
>>>>> 
>>>>> The attached document reflects these changes and has the question to all of the OCs about coordination in the event of change of operator. Everyone please have a look. I will keep adding the questions to this document as we finalize them.
>>>>> 
>>>>> Also in Dropbox: https://www.dropbox.com/s/ndriu6fj9o0c3sb/questions-for-OCs-v1.docx?dl=0 <https://www.dropbox.com/s/ndriu6fj9o0c3sb/questions-for-OCs-v1.docx?dl=0>
>>>>> 
>>>>> Thanks,
>>>>> Alissa
>>>>> 
>>>>> <questions-for-OCs-v1.docx>
>>>>>> On Sep 22, 2015, at 10:09 PM, Russ Mundy <mundy at tislabs.com <mailto:mundy at tislabs.com>> wrote:
>>>>>> 
>>>>>> 
>>>>>> Alissa, thanks for putting this together - it’s very helpful.
>>>>>> 
>>>>>> I think that we agreed at our last f2f meeting that it would be best to provide suggested text changes rather than editing the word documents so I’m going to suggest some changes a portion of the first RZM question:
>>>>>> 
>>>>>> Currently reads:  … requirements as expressed in paragraph 1150, sections 2 and 3 of Part 1 of the …
>>>>>> 
>>>>>> Suggested change:  … requirements expressed in paragraph 1150 (sections 2 and 3) and multiple Annexes of Part 1 of the  … 
>>>>>> 
>>>>>> 
>>>>>> RussM
>>>>>> 
>>>>>> On Sep 22, 2015, at 7:27 PM, Alissa Cooper <alissa at cooperw.in <mailto:alissa at cooperw.in>> wrote:
>>>>>> 
>>>>>>> I thought having the OC questions in one place would make it easier to live-edit on the call if necessary: https://www.dropbox.com/s/8hx06iasdvh3kd4/questions-for-OCs-v0.docx?dl=0 <https://www.dropbox.com/s/8hx06iasdvh3kd4/questions-for-OCs-v0.docx?dl=0> (also attached)
>>>>>>> 
>>>>>>> I’ll try to update this before the call if changes come in but the call is at 4:00 in my time zone so no guarantees.
>>>>>>> 
>>>>>>> Alissa
>>>>>>> 
>>>>>>> <questions-for-OCs-v0.docx>_______________________________________________
>>>>>>> Internal-cg mailing list
>>>>>>> Internal-cg at mm.ianacg.org <mailto:Internal-cg at mm.ianacg.org>
>>>>>>> http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org <http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org>
>>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> Internal-cg mailing list
>>>>> Internal-cg at mm.ianacg.org <mailto:Internal-cg at mm.ianacg.org>
>>>>> http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org <http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org>
>>>> 
>>> 
>> 
>> _______________________________________________
>> Internal-cg mailing list
>> Internal-cg at mm.ianacg.org <mailto:Internal-cg at mm.ianacg.org>
>> http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org <http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org>
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.ianacg.org/pipermail/internal-cg_ianacg.org/attachments/20150924/086b5ed6/attachment.html>