[RDS-WHOIS2-RT] RDS-WHOIS2 Review Team Plenary Call #8 28 September 2017 - 11:00 UTC

[Alan Greenberg]

Thanks Dmitry. Yes, I am well aware of using 
non-ASCII characters to the left of the @ sign.

My recollection is that for 
translation/transliteration, the new version 
would not replace the old one, but be in addition 
to it. And we are still some way from actually 
implementing it due to unresolved issues (who 
will pay for it, whether to use translation or 
transliteration in any given case (and it is FAR 
from obvious, since there are plenty of examples 
where one makes sense and the other is simply meaningless, and vice versa).

Moreover, again my recollection is that the 
action to be taken is field specific, and I would 
presume that e-mail addresses are fields where it 
may not make a lot of sense to even provide T/T 
versions alongside (although the fact that my 
left-of-at-sign is "alan.greenberg" DOES convey 
information, so perhaps there is some reason). 
But regardless, I think the current work does 
address the issue. But of course, my recollection 
could be in error, so we need to verify.

Alan

At 28/09/2017 11:18 AM, Dmitry Belyavsky wrote:
>Hello,
>
>The mentioned RFCs describe using addresses with 
>non-ascii symbols in left part.
>There is an interest to use it as widely as 
>currently we use ASCII email addresses.
>
>The Rec 12 designed to cover the cases of 
>transliteration is not usable for the case of international email addresses.
>But they are already used as part of WHOIS data 
>in some countries and we should expect that they 
>will be used in gTLDs relatively soon.
>
>On Thu, Sep 28, 2017 at 2:03 PM, Alan Greenberg 
><<mailto:alan.greenberg at mcgill.ca>alan.greenberg at mcgill.ca> wrote:
>Thanks Dmitry,
>
>Without our reading the RFCs, can you explain 
>exactly what the problem is and how it relates to WHOIS and Rec 12?
>
>Alan
>
>At 28/09/2017 03:28 AM, Dmitry Belyavsky wrote:
>
>>Hello,
>>
>>It's worth mentioning a significant change that happened after 2012.
>>
>>The International Email (EAI) was standartized (RFC 6530-6533),
>>and at least some ccTLD registries from Asia (I definitely know about .TH)
>>accept such email addresses as domain 
>>adminstrator's email. A lot of registries
>>(mostly in Asia) organize more or less active research in this area.
>>
>>Though it is not acceptable by gTLDs registries 
>>yet, I suspect that it will be done soon.
>>
>>Recommendation #12 is not applicable for the International Email Addresses,
>>so I think that we should deal with this problem.
>>
>>I think it can be a short mention or (better) 
>>recommendation to study this case by an appropriate ICANN working group.
>>
>>Thank you!
>>
>>On Wed, Sep 27, 2017 at 7:35 PM, Jean-Baptiste 
>>Deroulez 
>><<mailto:jean-baptiste.deroulez at icann.org> 
>>jean-baptiste.deroulez at icann.org> wrote:
>>Dear Review Team Members,
>>
>>In preparation for your call 
>><https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_2QAhB&d=DwMFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=a5VfrQZP4r0Kte2xBJT17IgRyRBHECC3vHSuFP_QBqD22G4dgkHhRZBEhshbjycD&m=S9ZDfh8iurFlsSHI1Ijq2MYN1n6BLqkCbi8oiJVuiH>#08, 
>>scheduled for Thursday, 28 September 2017 – 
>>11:00 UTC, pleease findd below a suggested agenda:
>>
>>Welcome, roll-call
>>Implementation Briefings on WHOIS Recommendations 4, 12, 13, 14
>>Scope
>>Face-to-Face meeting #1 Agenda
>>ICANN60 informal meeting
>>A.O.B.
>>
>>In anticipation of the meeting, we invite you 
>>to read the attached slides, the scope and 
>>objectives document, and the draft face-to-face meeting agenda.
>>
>>You should all have received dial-in details to 
>>join this call. If not, please contact us off 
>>list at 
>><mailto:rds-whois2-staff at icann.org>rds-whois2-staff at icann.org 
>>and we will make sure to send you a copy. If 
>>need be, you may join the call up to 20 minutes 
>>prior to the scheduled start to test your audio.
>>
>>As always, feel free to contact us should you have any questions or concerns.
>>
>>Kind regards,
>>
>>Jean-Baptiste Deroulez
>>
>>
>>_______________________________________________
>>RDS-WHOIS2-RT mailing list
>><mailto:RDS-WHOIS2-RT at icann.org>RDS-WHOIS2-RT at icann.org
>>https://mm.icann.org/mailman/listinfo/rds-whois2-rt
>>
>>
>>
>>
>>--
>>SY, Dmitry Belyavsky
>>Content-Type: text/plain; charset="us-ascii"
>>Content-Transfer-Encoding: 7bit
>>Content-Disposition: inline
>>X-Microsoft-Exchange-Diagnostics:
>> 
>>1;DM5PR03MB2714;27:QpaHfL8HWeRFwXoJRUdJiOH5sX9VYdwcqQuGVWCTF+18BaVV99w9ytfTLLQTyEfmXybGukANFzEPALYmod/8UumTop1rSSi8ELRJD+6TzdzKVzlf3X/b49naMH6LMW+n
>>X-Microsoft-Antispam-Mailbox-Delivery:
>> 
>>ex:0;auth:0;dest:I;ENG:(400001000128)(400125000095)(20160514016)(750103)(520002050)(400001001223)(400125100095)(61617095)(400001002128)(400125200095);
>>
>>_______________________________________________
>>RDS-WHOIS2-RT mailing list
>><mailto:RDS-WHOIS2-RT at icann.org>RDS-WHOIS2-RT at icann.org
>>https://mm.icann.org/mailman/listinfo/rds-whois2-rt
>
>
>
>
>--
>SY, Dmitry Belyavsky
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rds-whois2-rt/attachments/20170928/b49bf3c2/attachment.html>