<html>
<body>
Thank you very much Lili. <br><br>
With this reply, I am posting your updated draft to the subgroup. We will
now incorporate this version of the subgroup's report into the draft RT
report.<br><br>
Regarding Subsection 4: We suggest just referencing other subgroup's full
report sections, allowing each subgroup to carefully state its own
conclusion, while expanding this subsection to explain how plan/report
implementation impacted those outcomes. For example, based on your
current draft text, one possible way to fill this gap might be:<br><br>
<i>Many of the WHOIS1 recommendations were fully-implemented as detailed
throughout Section 4. However, some resulted in prolonged on-going
processes (e.g., Section 4.7, Privacy/Proxy). Others did not achieve the
full intent of the WHOIS1 recommendation (e.g., Section 4.6, Data
Accuracy). <Continue by describing specific problem(s) you may see in
WHOIS implementation plans and/or reports that contributed to prolonged
processes, not fully realizing intent, etc.><br><br>
</i>Detailing how plans/reports affected the implementation of other
WHOIS1 recommendations will help everyone understand how those
plans/reports could be improved in specific, measurable ways to increase
effectiveness of WHOIS2 rec implementation. I hope this helps explain the
gap we'd flagged in Subsection 4, helping the subgroup flesh out the
recommendation in Subsection 5.<br><br>
Best, Lisa<br><br>
<br>
At 03:45 AM 7/22/2018, SUN Lili wrote:<br>
<blockquote type=cite class=cite cite="">Hi Lisa,<br>
<br>
Please refer to attached the updated version. Regarding your comments on
“summarizing the problems identified by other subgroups” in Subsection 4,
it was agreed by this subgroup to “Cross check with other subgroups about
whether the Action Plan properly addressed the WHOIS1 recommendations”.
<br>
<br>
During the plenary call on 19 July, we raised a follow up question to
ICANN to check whether there is a overseeing of the whole Whois package,
I put a place holder in Subsection 4 to reflect the pending answer.<br>
<br>
Thanks,<br>
Lili<br>
<br>
<b>From:</b> Lisa Phifer
[<a href="mailto:lisa@corecom.com" eudora="autourl">
mailto:lisa@corecom.com</a>] <br>
<b>Sent:</b> Saturday, 21 July, 2018 2:39 PM<br>
<b>To:</b> SUN Lili <L.SUN@interpol.int><br>
<b>Cc:</b> Alice Jansen <alice.jansen@icann.org><br>
<b>Subject:</b> Recs#15-16 subgroup report<br>
<br>
Hi Lili,<br><br>
I wanted to draw your attention to the gap assessment on your subgroup
report:<br>
<a href="https://community.icann.org/download/attachments/71604726/Subgroup1-Rec1516-PlanAnnual-Report-Draft4.docx">
https://community.icann.org/download/attachments/71604726/Subgroup1-Rec1516-PlanAnnual-Report-Draft4.docx<br>
<br>
</a>- Draft report to be updated to include changes identified in
subgroup call<br>
- Subsection 1: Move methodology to Subsection 2.<br>
- Subsection 4: Problems do not appear to be linked to Subsection 3
Findings/Analysis.<br>
Instead of summarizing the problems identified by
other subgroups, <br>
this Subsection needs to identify problems (if any)
that result from the analysis in Subsection 3, <br>
leading to the Recommendation in Subsection 5.<br>
- Recommendation in Subsection 5 needs to be fleshed out and made
specific & measurable.<br>
Specific elements to be included in the
recommendation:<br>
<img src="cid:6.2.3.4.2.20180722095829.08c69250@mail.corecom.com.1" width=210 height=312 alt="Emacs!">
<br><br>
I know that in this week's subgroup call, some of this was discussed, and
the recommendation may not be fully fleshed out in your next draft.
However, please cover as many elements as you can or perhaps leave
placeholders for any missing elements to be used as a guide during review
at our F2F meeting?<br><br>
Please provide any report updates to address these gaps no later than
<br>
<b>Sunday 22 July 23:59 UTC</b> <br><br>
Thank you<br>
Lisa </blockquote></body>
</html>