<div dir="ltr">Hello,<div><br></div><div>Inspired by Alan's letter, I provide the work statement for our subgroup.</div><div>Please review it.</div><div><br></div><div>Happy New Year!</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 19, 2017 at 3:05 PM, Dmitry Belyavsky <span dir="ltr"><<a href="mailto:beldmit@gmail.com" target="_blank">beldmit@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Dear Alan, <div><br></div><div>Thank you for your comprehensive analysis!</div><div><br></div><div>I agree with you in total, and after checking the RDAP specification, I have no more questions about EAI. </div><div><br></div><div>Lili, do you have something to add?</div><div><br><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Fri, Dec 15, 2017 at 8:56 PM, Alan Greenberg <span dir="ltr"><<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">alan.greenberg@mcgill.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
After doing a brief review of the three IDN-related Recommendation from
the first WHOIS RT, here are my conclusions. Note I am not an IDN expert,
but have been involved in these discussions for quite some time.<br><br>
Rec 12 and 13 seem to have been fully addressed, with further action
pending the GNSO RDS PDP. Clearly we need to review the Recs and reports
in details, but superficially, that seems to be the case.
Translated/transliterated may be a bit more difficult, because my
recollection is that the report leaves open a lot of questions.<br><br>
Rec 14 I find more difficulty as it was looking at accuracy and metrics
for accuracy and I am not at all sure how it can be marked as complete
when the internationalized data has not yet been implemented.<br><br>
So for "Questions we will need to answer in assessing whether the
objective has been reached", the answer is that we need to verify
that the reports address all aspects of the Rec. issues, up to the point
where they need to be implemented.<br><br>
I would put the complexity at 3, since it will take careful work to
assess how well the work is done since we cannot rely on final
results - those are impossible until we have a new RDS that handles
the internationalized data (and multiple forms for
translated/transliterated data).<br><br>
Workload I put at a 2. Not much more than carefully reading the Recs and
their background and the reports.<br><br>
Team size I would put at 3. If 3 of us can agree, I think that is
enough.<br><br>
New data (in addition to the written briefings we are already asking
for), only perhaps a discussion with the SMEs within ICANN on the
difficulty of proceeding. No external experts.<br><br>
Related to EAI, I really don't see the issue. If the new RDS fields can
hold names and addresses using multiple scripts, why is the e-mail
address a special case? Worthy of double checking with an RDAP
expert, but I am not expecting anything other than a confirmation that
the e-mail address is just another field. It IS interesting in that the
part to the right of the @ sign could be stored either in its own natural
language or in punycode, but I don't think that is more than a technical
decision on which way to go.<br><br>
At 04/12/2017 02:00 PM, Dmitry Belyavsky wrote:<br><br>
<blockquote type="cite" class="m_6211534849594479813m_7239569155412349896cite">Hello,<br><br>
Let’s make an initial discussion of the scope of our subgroup.<span><br>
I kindly ask Lili and Alan to share their ideas on our duties not later
than December 7.<br>
<br>
According to Susan's letter<br><br>
=============<br>
Please note that the following actions will need to be achieved by
December 12, 2017:<br><br>
Establish mandate, objectives and timeline for the work<br><br>
Determine topics for investigation and validate against ICANN
Bylaws<br><br>
Identify briefings/data sources needed<br><br>
Determine requirements for independent expert(s) and – if necessary –
develop statement of work<br><br></span>
Adopt statement of work and assoociated work plan<span><br><br>
================<br><br>
I tried to describe my understanding below, so any feedback is welcome.
After that let's convert it to plan.<br><br>
As for now, I do not think we need conference calls, especially taking
into account our geographical distribution. I hope we can just use
mailing list for most cases.<br><br>
<br>
I suggest to start from the analysis of the RT1 recommendation and
actions/decisions taken by board according to the materials of Briefing
on WHOIS Recommendations [1], WHOIS Review Executive Summaries [2] and
Detailed Quarterly Implementation Report on WHOIS
Improvements[3].<br><br>
<br></span>
According to [2], p.23, “Implementation plan to be developed†but I
have no idea what it is related to. According to [3] p.6, the
implementation plan should be the part of completing Recommendation 13.
Both Recommendations 12 and 13 are described as completed. If it is OK, I
do not see what are we to do with it. According to [1] p.17 there is no
recommendations by IRT to be implemented yet. So I think that we can just
mention this situation and it will be OK.<span><br><br>
<br>
Regarding Recommendation 14, I think we have a previously-absent
circumstances. I mean Email Address International (EAI). I know that at
least some ccTLDs allow using such email addresses as email addresses of
registrants. I expect that sooner or later EAI will be allowed in EPP
protocol used in gTLDs so we need to say something about it. At least we
must raise the question whether EAI addresses are RDAP-compatible in this
or that way.<br><br></span>
According to [3] p.7, “Internationalized registration data (IRD) for
WHOIS Records are being proactively identified in Phase I and Phase II of
ARS reports†. But the EAI case was not covered.<span><br><br>
[1]
<a href="https://community.icann.org/download/attachments/69279139/WHOIS%20Briefing%20-%2028September2017%20-%20V2.0.pptx?version=1&modificationDate=1506686336000&api=v2" target="_blank">
https://community.icann.org/do<wbr>wnload/attachments/69279139/WH<wbr>OIS%20Briefing%20-%2028Septemb<wbr>er2017%20-%20V2.0.pptx?<wbr>version=1&modificationDate=150<wbr>6686336000&api=v2</a>
<br><br>
[2]
<a href="https://community.icann.org/download/attachments/54691767/WHOIS%20Recs%201_16%2030Sept2016.pdf" target="_blank">
https://community.icann.org/do<wbr>wnload/attachments/54691767/WH<wbr>OIS%20Recs%201_16%2030Sept2016<wbr>.pdf</a>
<br><br>
[3]
<a href="https://community.icann.org/download/attachments/54691767/WHOIS%20Quarterly%20Summary%2031December2016.pdf" target="_blank">
https://community.icann.org/do<wbr>wnload/attachments/54691767/WH<wbr>OIS%20Quarterly%20Summary%2031<wbr>December2016.pdf</a>
<br><br>
<br>
-- <br>
SY, Dmitry Belyavsky<br></span>
Content-Type: text/plain; charset="us-ascii"<br>
Content-Transfer-Encoding: 7bit<br>
Content-Disposition: inline<br>
X-Microsoft-Exchange-Diagnosti<wbr>cs:<br>
<u></u> <u></u>
1;YQXPR0101MB1589;27:HE4HUjqHu<wbr>1NifahA1P0Ja7cgQY//hrREQRCMICN<wbr>rd4ntBo8XEr6KMIHfT00P2bd0Lou+n<wbr>rKYrJxZY4kMdK9cZ6gekUmPXmC1Zxt<wbr>/TbBpvn4F1j4alkW8gkrIeyTrHWKu<br>
X-Microsoft-Antispam-Message-I<wbr>nfo:<br>
<u></u> <u></u>
iFfZKQmok7EFRUMSvaVsvrAg0oFo8v<wbr>TeQljbH5FEla/IIl9QXjTZzSoD3vur<wbr>ZR2DMqYYV/yQdwEvtHYlIDmuW75nhr<wbr>5ulY1xhzSCbqvdVCjVmMy5tj5tMr9B<wbr>lfgiU3lOa7YH5kSGjUa8bspVVYroWw<wbr>==<span><br>
<br>
______________________________<wbr>_________________<br>
RDS-WHOIS2-IDNS mailing list<br>
<a href="mailto:RDS-WHOIS2-IDNS@icann.org" target="_blank">RDS-WHOIS2-IDNS@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/rds-whois2-idns" target="_blank">
https://mm.icann.org/mailman/l<wbr>istinfo/rds-whois2-idns</a></span></blockquote>
</div>
</blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div class="m_6211534849594479813gmail_signature" data-smartmail="gmail_signature">SY, Dmitry Belyavsky</div>
</font></span></div></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">SY, Dmitry Belyavsky</div>
</div>