My suggested talking points below:
Given that this will be an enforceable document, what items belong in the guidelines and what items should be moved out to a non enforceable advisory document?

What criteria and oversight will be applied to each item staying within the guidelines? Should items come from authoritative sources and if those sources modify their advice, should the guidelines explicitly allow contracted parties to follow those modifications?

Will we include any items which have not been recommended by a domain name standards or advisory body and if so, should those recommendations be enforceable?



From: <idngwg-bounces@icann.org> on behalf of "idngwg@icann.org" <idngwg@icann.org>
Reply-To: Edmon Chung <edmon@registry.asia>
Date: Wednesday, 18 November 2015 at 1:09 PM
To: "idngwg@icann.org" <idngwg@icann.org>
Subject: Re: [Idngwg] A draft for the meeting Wednesday

Mat’s list is a good set of items for starting discussion.

 

My contribution below on a more abstract/structural level.  I think the following components may be useful for the guidelines:

 

- Terminology

- IDN Registration Policy Components

- IDN policy development checklist/references

            - IDN policies/tables/repertoires considerations

            - Technical & linguistic considerations

- IDN Registration

            - 2LD registrations

- ccTLD vs gTLD contextual differences

- IDN TLDs

- IDN Variants

- IDN Policy implementation recommendations

            - additional implementation guidelines based on ccNSO/GNSO documents

- IDN registration systems

 

A very rough off the top of my head framework.

 

Edmon

 

 

 

From: idngwg-bounces@icann.org [mailto:idngwg-bounces@icann.org] On Behalf Of Mats Dufberg via Idngwg
Sent: Wednesday, November 18, 2015 6:40 AM
To: idngwg
Subject: [Idngwg] A draft for the meeting Wednesday

 

Friends,

 

Enclosed is my contribution to the meeting tomorrow.

 

 

Yours,

Mats

 

--

Mats Dufberg

DNS Specialist, IIS

Mobile: +46 73 065 3899