Re: [Idna-update] Expiration impending: <draft-klensin-idna-rfc5891bis-01.txt>

[Francisco Arias <[e-mail]>]

Except for a couple of legacy gTLDs that do not yet have that requirement, for the vast majority of the gTLDs, compliance with the IDN Implementation Guidelines is mandatory.

If there were a requirement on this regard in the guidelines, compliance could be checked when new tables are submitted to ICANN for approval. If needed, an active monitoring could also be done.

-- 
Francisco

On 3/6/18, 2:32 AM, "IDNA-UPDATE on behalf of Patrik Fältström" <[e-mail] on behalf of [e-mail]> wrote:

    How do you believe this is to be implemented in all TLDs? I.e. what do you believe is the enforcement mechanism?
    
       Patrik
    
    On 5 Mar 2018, at 23:22, Francisco Arias wrote:
    
    > Following on Asmus' comment below, perhaps the IDN Implementation Guidelines could help as a way to reach out to TLD registries?
    >
    > https://www.icann.org/resources/pages/implementation-guidelines-2012-02-25-en
    >
    > I believe the process to update them is ongoing https://community.icann.org/display/IDN/IDN+Implementation+Guidelines
    >
    > Regards,
    >
    > -- 
    > Francisco
    >
    > On 3/5/18, 2:12 PM, "IDNA-UPDATE on behalf of Asmus Freytag" <[e-mail] on behalf of [e-mail]> wrote:
    >
    >     Secondary to that is finding a way to communicate the to consumers of
    >     these tables that simply allowing all PVALID code points isn't a robust
    >     solution for many writing systems and additional due diligence needs to
    >     be preformed - for example along the same lines as is being done now for
    >     the Root Zone (which is quickly defining the state of the art in that
    >     respect).
    >
    >
    > _______________________________________________
    > IDNA-UPDATE mailing list
    > [e-mail]
    > https://www.ietf.org/mailman/listinfo/idna-update