[Ctn-crosscom] FW: Notes CWG CTN meeting

Wed Nov 25 15:28:58 UTC 2015

Dear all,

Below you will find the summary of last week¹s call.

Attached you will find updated versions of the responses submitted to-date.

Please note that our next call is on
Monday 30 November 2015 at 2100 UTC.
13:00 PDT, 16:00 EDT, 21:00 London, 22:00 CET, 05:00 Beijing, 08:00 Sydney

for other places see: http://tinyurl.com/pnb2o4x

Best. Lars

From:  Bart Boswinkel <bart.boswinkel at icann.org>
Date:  Thursday, 19 November 2015 at 02:49
To:  Lars HOFFMANN <lars.hoffmann at icann.org>
Subject:  Notes CWG CTN meeting

Lars, Included notes from last Mondays call, please check if okay suggest
you send them to the list
Kind regards,
Bart

CWG Country and Territory Names, Monday 16 November 2015, 21:00 UTC

AGENDA

1. Welcome

Apologies: 
* Annebeth Lange
* Jaap Akkerhuis
* Laura Hutchinson
2. Re-cap of Dublin and reminder of work plan until Marrakech
* Circulation of survey questions
First time out send late August

Reminders send. Last group was approached after the Dublin meeting. In
person and generic reminders

During Dublin and since, 5 comments received, from various communities

Goal is to have internal views and circulate prior to Marrakesh

Co-chair proposal:

Send out as prelimanry report also include section around methodology.

Comment: bundling together work on two and three letter codes, and then seek
feed-back.

Recognition major issue is country names, but before handling it send out
prelimenary report to show methodology

3. Letter from Thomas Schneider, GAC Chair

Background; ccNSO and GNSO chairs informed about concern of potetial overlap
between work Geographic names and CTN WG. Positive:Issue identified,
awareness has been raised

Interpretation of letter response: Mandate of CTN is ISO 3166 list. GAC WG
will focus on other Geographic names.

Limited to ISO 3166.  does that include names of countries? Names in
different languages?

Interpretation: Includes names as on ISO list Paul S: Does not read it as
limiting or intentionally. Work deriving from ISO 3166

Suggests to park the issue until such time it hits that point ( around
Marrakesh meeting), after dealing with 3 letter codes.

Heather F. Concern: There are two groups on geographic names -> may result
in different definitions. Deal with concern going forward. Clarity needed
for future applicants.

Other Questions?

Cheryl: GAC's own work will proceed at its own pace. At th etime the work of
GAC moves forward  CTN will be able to negotiate mutually agreed
terminology. It is early days of the GAC group.

Paul S: Potential risk recognised by both CTN and GAC and hence potential to
mitigate, as result of letter.

4. Confirm and Discuss input received on 3-character codes

Heather: 

Comments received to date . ( 5 ), including from two law-firms

ccTLD submissions to follow. Question: Does response need to be official?
Official letter not needed, Seeeking input at this time.

Time to digest the input received

5. Next steps in tabulating community input received to-date

Lesson learned: Strategy on how to seek response: create a kind format.
Challanges on input

Next step; How to deal with comments, taking into account variety of format.
How to deal woth it

Carlos: Background paper and two-letter paper.

In seeking public comment and working move forward on straw man.

Use methodology of two-letter code

Lars suggestion:  Possibility creating sub-groups, staff could make a
summary,  Check by group. Bring in comments as much as possible.

Carlos: Include comments in paper. Include as annexes/ Appendices. Need to
maintain original source

By and large responses with rationale. Create overview and cluster
reasoning.

CTN members to look at comments recevied and then discussion on how to
include them.

Discuss formal methodology at that time, and document it.

Cheryl: Community expectation some form of archive how CTN has dealt with
comment.

Template approach used by CWG and CCWG

Recommend on how to use column approach. Bring out rationale

Tackle at next meeting?

Create a sub-group ( self-identified) supported by staff  to work on
digesting the comment.

6. AOB and next meeting

No comments

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/ctn-crosscom/attachments/20151125/345eafa8/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 3-character-Overview_Q1-4-20151125.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 151844 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/ctn-crosscom/attachments/20151125/345eafa8/3-character-Overview_Q1-4-20151125-0001.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 3-character-Overview_Q5-7-20151125.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 118368 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/ctn-crosscom/attachments/20151125/345eafa8/3-character-Overview_Q5-7-20151125-0001.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5091 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/ctn-crosscom/attachments/20151125/345eafa8/smime-0001.p7s>