[RDS-WHOIS2-RT-Leadership_Staff] Update on timing and final report.

[Alan Greenberg]

At 05/11/2018 11:39 AM, Jean-Baptiste Deroulez wrote:
Hi Alan,

Thank you for your email.

We reviewed your suggested plan moving forward, and would like to provide some clarification on processes after the final report has been submitted to the ICANN Board.

1) Public Comment Period
The public comment period lasts 40 days. An extension occurs when the public comment period hits ICANN Public Meeting dates, and these should not be included in the day count for a proceeding.

With the planned schedule, it WILL overlap with ICANN64.


2) Budget
After the final report is submitted to the Board, the Review Team will disband (see specific review process<https://www.icann.org/en/system/files/files/specific-reviews-process-flowchart-31aug17-en.pdf>) and no longer have budget, this includes travel support which is available only when conducting the review. As per your approved outreach plan<https://community.icann.org/download/attachments/64084100/Outreach_Plan%204.0.pdf?version=1&modificationDate=1517496782000&api=v2>, the outreach scheduled for the final report is to hold two webinars to accommodate all time zones.

My understanding was that the Terms of Reference and the associated schedule could be modified if appropriate (and with the support of the Board RT member (and the Board if appropriate).

I'm curious who will participate in giving the webinars of the Review Team is disbanded.


3) Meeting with the ICANN Board/ICANN org in Kobe
Looking at the suggested timeline and in addition to 2), meeting with the ICANN Board in Kobe might not be timely as the ICANN Board would not have seen the Public Comment summary by then, and therefore not able to comment on it. Additionally, if the ICANN Board has comments, the review team will not be in a position to update its report at this stage.

Nothing was said about updating the report. The rest of ICANN solidly supports the concept of an Implementation Review Team (IRT) to ensure that the intent of recommendations are properly implemented. Our review of the WHOIS1-RT Recommendations has demonstrated that having an IRT for that review would likely have resulted in a better implementation record than what the present RT has found. It is unfortunate that MSSI does not seem to recognize the value in this.

The draft operating standard even include the phrase "working to confirm that the implementation reflects the intention of the review team".

Alan


Hope this helps,

Kind regards,
Jean-Baptiste

On 11/2/18, 9:34 PM, "RDS-WHOIS2-RT-Leadership_Staff on behalf of Alan Greenberg" <rds-whois2-rt-leadership_staff-bounces at icann.org on behalf of alan.greenberg at mcgill.ca> wrote:

    May I please have an update from MSSI staff on this?

    Alan

    At 01/11/2018 12:34 PM, Alan Greenberg wrote:
    >Both Catherine and Susan have supported this proposal. My
    >recollection is that Cathrin cannot accept ICANN funding, and Susan
    >is already funded (although she may need us to cover a few extra
    >days. I will need funding.
    >
    >Since this will have a cost in thousands of dollars (although below
    >the amount we put in the budget) I assume this needs staff approval.
    >Can we have this done as soon as possible to meet the 06 Nov
    >traveller submission date?
    >
    >Alan
    >
    >At 30/10/2018 03:56 PM, Alan Greenberg wrote:
    >>To: RDS-WHOIS2-Leadership <rds-whois2-rt-leadership_staff at icann.org>
    >>From: Alan Greenberg <alan.greenberg at mcgill.ca>
    >>Subject: Update on timing and final report.
    >>
    >>As I think you know, Lisa Phifer will not be able to work with us
    >>to complete the report, and MSSI is looking at options for an
    >>editor. It will not be anyone with knowledge of the subject.
    >>
    >>The draft report was too long and not cohesive, so I think it needs
    >>a careful overall review and revision. SInce the editor will not
    >>have a feel for the intent of the analysis and recommendations, it
    >>will fall on us to do a fair amount of the work. Given my lessened
    >>responsibilities with regard to At-Large, I am willing to do at
    >>least part of this, but we will need to adjust the timeline, both
    >>for the rework and to have team members sign off.
    >>
    >>We meet 10-12 December which leaves just one week before the
    >>holiday season. That will not be enough time to complete the
    >>substantive edits and to clean up the overall report. So we will
    >>definitely go into January. My target is to issue the report no
    >>later than the end of the month.
    >>
    >>If there is a 50 day public comment once submitted to the Board
    >>(which is what was done for the CCT Review), that puts the comment
    >>ending about a week after the end of the Kobe meeting.
    >>
    >>I suggest that we plan for:
    >>
    >>- An engagement session with the community; and
    >>
    >>- An opportunity for the RT leadership (and possibly other team
    >>members if appropriate) to meeting with Board and/or ICANN Org to
    >>clarify or elaborate on any aspect of the report.
    >>
    >>I have passed this by Chris and he supports it.
    >>
    >>Cathrin and Susan, do you support this proposal?
    >>
    >>The budget we used in stopping the public comment on short term
    >>actions included funding for a few people for the Kobe meeting and
    >>still came out using only $300k of the $690k allocated. I suggest
    >>that we look at funding up to three people for the meeting (people
    >>who authored key sections of the report and are not otherwise
    >>funded. (At this point I will likely need funding.)
    >>
    >>Travel lists need to be submitted in about a week, so we will need
    >>to move fast if we proceed.
    >>
    >>Alan

    _______________________________________________
    RDS-WHOIS2-RT-Leadership_Staff mailing list
    RDS-WHOIS2-RT-Leadership_Staff at icann.org
    https://mm.icann.org/mailman/listinfo/rds-whois2-rt-leadership_staff

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rds-whois2-rt-leadership_staff/attachments/20181105/9a53f302/attachment.html>