[RDS-WHOIS2-IDNS] Initial letter

Sat Dec 30 10:24:59 UTC 2017

Hello,

Inspired by Alan's letter, I provide the work statement for our subgroup.
Please review it.

Happy New Year!

On Tue, Dec 19, 2017 at 3:05 PM, Dmitry Belyavsky <beldmit at gmail.com> wrote:

> Dear Alan,
>
> Thank you for your comprehensive analysis!
>
> I agree with you in total, and after checking the RDAP specification, I
> have no more questions about EAI.
>
> Lili, do you have something to add?
>
>
> On Fri, Dec 15, 2017 at 8:56 PM, Alan Greenberg <alan.greenberg at mcgill.ca>
> wrote:
>
>> 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.
>>
>> 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.
>>
>> 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.
>>
>> 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.
>>
>> 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).
>>
>> Workload I put at a 2. Not much more than carefully reading the Recs and
>> their background and the reports.
>>
>> Team size I would put at 3. If 3 of us can agree, I think that is enough.
>>
>> 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.
>>
>> 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.
>>
>> At 04/12/2017 02:00 PM, Dmitry Belyavsky wrote:
>>
>> Hello,
>>
>> Letâ€™s make an initial discussion of the scope of our subgroup.
>> I kindly ask Lili and Alan to share their ideas on our duties not later
>> than December 7.
>>
>> According to Susan's letter
>>
>> =============
>> Please note that the following actions will need to be achieved by
>> December 12, 2017:
>>
>> Establish mandate, objectives and timeline for the work
>>
>> Determine topics for investigation and validate against ICANN Bylaws
>>
>> Identify briefings/data sources needed
>>
>> Determine requirements for independent expert(s) and – if necessary –
>> develop statement of work
>>
>> Adopt statement of work and assoociated work plan
>>
>> ================
>>
>> I tried to describe my understanding below, so any feedback is welcome.
>> After that let's convert it to plan.
>>
>> 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.
>>
>>
>> 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].
>>
>>
>> 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.
>>
>>
>> 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.
>>
>> 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.
>>
>> [1] https://community.icann.org/download/attachments/69279139/WH
>> OIS%20Briefing%20-%2028September2017%20-%20V2.0.pptx?
>> version=1&modificationDate=1506686336000&api=v2
>>
>> [2] https://community.icann.org/download/attachments/54691767/WH
>> OIS%20Recs%201_16%2030Sept2016.pdf
>>
>> [3] https://community.icann.org/download/attachments/54691767/WH
>> OIS%20Quarterly%20Summary%2031December2016.pdf
>>
>>
>> --
>> SY, Dmitry Belyavsky
>> Content-Type: text/plain; charset="us-ascii"
>> Content-Transfer-Encoding: 7bit
>> Content-Disposition: inline
>> X-Microsoft-Exchange-Diagnostics:
>>          1;YQXPR0101MB1589;27:HE4HUjqHu1NifahA1P0Ja7cgQY//hrREQRCMICN
>> rd4ntBo8XEr6KMIHfT00P2bd0Lou+nrKYrJxZY4kMdK9cZ6gekUmPXmC1Zxt
>> /TbBpvn4F1j4alkW8gkrIeyTrHWKu
>> X-Microsoft-Antispam-Message-Info:
>>          iFfZKQmok7EFRUMSvaVsvrAg0oFo8vTeQljbH5FEla/IIl9QXjTZzSoD3vur
>> ZR2DMqYYV/yQdwEvtHYlIDmuW75nhr5ulY1xhzSCbqvdVCjVmMy5tj5tMr9B
>> lfgiU3lOa7YH5kSGjUa8bspVVYroWw==
>>
>> _______________________________________________
>> RDS-WHOIS2-IDNS mailing list
>> RDS-WHOIS2-IDNS at icann.org
>> https://mm.icann.org/mailman/listinfo/rds-whois2-idns
>>
>>
>
>
> --
> SY, Dmitry Belyavsky
>

-- 
SY, Dmitry Belyavsky
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rds-whois2-idns/attachments/20171230/ed54a35a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: WHOIS1 Rec #12-14 - IDNs v1.1-20171230.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 17016 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/rds-whois2-idns/attachments/20171230/ed54a35a/WHOIS1Rec12-14-IDNsv1.1-20171230-0001.docx>