[RZERC] RZERC Procedures redline and clean copy docs

[Russ Mundy]

Hi Duane & others,

> On Jun 22, 2017, at 8:25 PM, Wessels, Duane <dwessels at verisign.com> wrote:
> 
> Thank you Russ,
>  
> I think this could be useful to include in the procedures document, although the text isn’t really procedural in nature.  I’m a little uncertain if the introduction is the best place for it.  

I would be fine with the text going into a later section.  The primary reason the intro seemed like a good place to me was that this is where we area where relationships are discussed.

>  
> I think what you’re getting at here is that RZERC’s view might not always match the views of its member’s appointing organizations.  What do you think about making this point in section 5.4 “Deliberation and Decision Making”?

I’d be okay with the idea being in this section.  And, yes, the main point is to say that RZERC views might or might not align with those of any of designating organization but also to note that neither RZERC nor any of the designating organizations are in any way “bound” to have their recommendations aligned.

One thing that I did note when re-reading the Intro and Section 5.4, they don’t seem to be fully consistent.  The Intro says that RZERC makes recommendations to the ICANN Board while section 5.4 says:
"The response and the recommendations of the Committee will be communicated to the requesting body as well as posted on the Committee’s website." 

The ‘requesting body’ might or might not be the ICANN Board - if we think that all of our recommendations will always be to the Board (which I infer from the Intro & our Charter) then I think we should say that in a more direct manner in this section.

Russ 

>  
> DW
>  
>  
> From: Russ Mundy <mundy at tislabs.com <mailto:mundy at tislabs.com>>
> Date: Thursday, June 22, 2017 at 3:44 PM
> To: Duane Wessels <dwessels at verisign.com <mailto:dwessels at verisign.com>>, ICANN Root Zone Evolution Review Committee <rzerc at icann.org <mailto:rzerc at icann.org>>
> Cc: Russ Mundy <mundy at tislabs.com <mailto:mundy at tislabs.com>>
> Subject: [EXTERNAL] Re: [RZERC] RZERC Procedures redline and clean copy docs
>  
> During our last meeting, I suggested that our procedures document should have one or two sentences added to the end of the Introduction to make it clear that RZERC recommendations were not intended to be a replacement or substitute for recommendations by the organizations that designate RZERC members.  
>  
> My apologies for this taking a little longer that I anticipated but here are my proposed sentences to be added to the first paragraph of the Introduction section:
>  
> Organizations/groups that designate RZERC members might also submit recommendations or comments to the ICANN Board of Directors on the proposed changes.  RZERC recommendations should be considered additional information that the ICANN Board may use to make their decisions on the proposed changes. RZERC recommendations are not intended to be a substitute for recommendations/comments made by the organizations/groups that designate RZERC members.
> 
>  
> 
> I’ve included the .docx and a pdf with the change incorporated.  Thought and comments by others are, of course, appreciated.
> 
>  
> Russ
>  
>> On Jun 1, 2017, at 11:05 AM, Wessels, Duane via RZERC <rzerc at icann.org <mailto:rzerc at icann.org>> wrote:
>>  
>> Dear RZERC,
>>  
>> Attached is an updated copy of the draft RZERC procedures document.  Mario, Steve, and I spent some time editing the document after our May 22 meeting.  I believe we have addressed all of the comments and suggestions provided.  Note in particular that the procedures document now makes clear when it references the RZERC charter.
>>  
>> I'd like to encourage everyone to take a look at this version and provide feedback soon so that we can iterate on this faster than once per month.
>>  
>> DW
>>  
>> 
>> 
>>  
>> <Draft_RZERCOperationalProcedures_clean copy01.docx><Draft_RZERCOperationalProcedures_clean copy01.pdf><RZERC Operational Procedures_redlineV01.docx>_______________________________________________
>> RZERC mailing list
>> RZERC at icann.org <mailto:RZERC at icann.org>
>> https://mm.icann.org/mailman/listinfo/rzerc <https://mm.icann.org/mailman/listinfo/rzerc>
>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rzerc/attachments/20170623/bdec7a4c/attachment.html>