[RDS-WHOIS2-IDNS] Report IDN 1214.docx

[Dmitry Belyavsky]

Dear Lili,

It's a possible case. As for now, the RDAP implementation can be delayed
because of commercial reasons, and even when it is feasible, RDAP itself
does not imply the IDN data.
So what do you suggest to write in the Conclusion and/or Recommendation?

On Fri, Jun 8, 2018 at 7:34 AM, SUN Lili <L.SUN at interpol.int> wrote:

> Hi Dmitry,
>
>
>
> I got your point. But will it be the case that even after the RDAP was
> implemented, the IRD is still pending implementation due to no requesting
> party and no budget?
>
>
>
> Correct me if my logic is wrong.
>
>
>
> Lili
>
>
>
> *From:* Dmitry Belyavsky [mailto:beldmit at gmail.com]
> *Sent:* Thursday, 7 June, 2018 11:52 PM
> *To:* SUN Lili <L.SUN at interpol.int>
> *Cc:* rds-whois2-idns at icann.org
> *Subject:* Re: [RDS-WHOIS2-IDNS] Report IDN 1214.docx
>
>
>
> Dear Lili,
>
>
>
> After rereading the report I understand that I do not get your idea :(
>
>
>
> The overall conclusion describes the current state:
>
> - there is classification of the data to be localized is provide by the
> IRD study
>
> - we have a protocol (RDAP) to be implemented that takes into account the
> IRD recommendations
>
>
>
> The recommendation says that for now it is done as far as it can be done.
>
> As RDAP is not implemented, we can't check whether the IRD recommendations
> go alive.
>
> But if the next RT works when RDAP is in use, it should check whether
> these recommendation are implemented in RDAP.
>
>
>
>
>
> On Mon, Jun 4, 2018 at 1:18 PM, SUN Lili <L.SUN at interpol.int> wrote:
>
> Hi Dmitry,
>
>
>
> Thanks for rolling out the draft report  by yourself and sorry for my late
> response.
>
>
>
> One comment: I see inconsistency between the “Overall conclusion” and
> “Recommendation”. The conclusion said the IRD could be done without an
> RDAP-based WHOIS system, while the recommendation suggest to review the
> implementation after RDAP is implemented. I read from the report that the
> requesting party for IRD is not identified and there is no budget source to
> implement the Rec #12-14. As such, I’d suggest to make recommendation
> regarding the feasibility and roadmap of IRD.
>
>
>
> Thanks,
>
> Lili
>
>
>
>
>
> *From:* RDS-WHOIS2-IDNS [mailto:rds-whois2-idns-bounces at icann.org] *On
> Behalf Of *Dmitry Belyavsky (via Google Docs)
> *Sent:* Sunday, 13 May, 2018 6:22 PM
> *To:* rds-whois2-idns at icann.org
> *Subject:* [RDS-WHOIS2-IDNS] Report IDN 1214.docx
>
>
>
> Dmitry Belyavsky <beldmit at gmail.com> has attached the following document:
>
> [image: Image removed by sender.]
>
> Report IDN 1214.docx
>
> [image: Image removed by sender. Sender's profile photo]Hello,
>
> Please find attached the updated version of the subgroup report.
> Some data moved to appendices, the conclusion is written according to the
> Brussels Meeting #2 - Review Team Agreements
>
>
>
> Google Docs: Create and edit documents online.
> Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA
> <https://maps.google.com/?q=1600+Amphitheatre+Parkway,+Mountain+View,+CA+94043,+USA&entry=gmail&source=g>
> You have received this email because someone shared a document with you
> from Google Docs.
>
> [image: Image removed by sender. Logo for Google Docs]
> <https://drive.google.com>
>
>
>
> ************************************************************
> ***************************************
> This message, and any attachment contained, are confidential and subject
> of legal privilege. It may be used solely for the designated police/justice
> purpose and by the individual or entity to whom it is addressed. The
> information is not to be disseminated to another agency or third party
> without the author’s consent, and must not be retained longer than is
> necessary for the fulfilment of the purpose for which the information is to
> be used. All practicable steps shall be taken by the recipients to ensure
> that information is protected against unauthorised access or processing.
> INTERPOL reserves the right to enquire about the use of the information
> provided.
> If you are not the intended recipient, be advised that you have received
> this message in error. In such a case, you should not print it, copy it,
> make any use of it or disclose it, but please notify us immediately and
> delete the message from any computer.
> ************************************************************
> *************************************
>
>
>
>
>
> --
>
> SY, Dmitry Belyavsky
>



-- 
SY, Dmitry Belyavsky
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rds-whois2-idns/attachments/20180608/76b8ce10/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 823 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/rds-whois2-idns/attachments/20180608/76b8ce10/image002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 368 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/rds-whois2-idns/attachments/20180608/76b8ce10/image003.jpg>