September 2005 - council - lists.icann.org

Updated Draft Agenda for GNSO Council teleconference on Thursday 22 September 2005
by Bruce Tonkin Sept. 16, 2005

Sept. 16, 2005

Hello All, I have added an update from Glen on the schedule for the Vancouver meeting to agenda item 2, and added a separate agenda item 7 to address whether to initiate an issues report on single letter domain names at the request of Marilyn Cade. Regards, Bruce Tonkin Updated Draft Agenda for Council meeting Thursday 22 September 2005 Coordinated Universal Time UTC 12:00 (5:00 Los Angeles, 8:00 Washington DC, 14:00 Brussels, 22:00 Melbourne) Item 1: Approval of minutes - teleconference - 18 August 2005 Item 2: Staff action items - list of current GNSO work items - status report on single letter domain names - update on statements of interest and amendment to the bylaws - GNSO Councillors induction proposal for Vancouver - GNSO session in ICANN newcomers session at Vancouver - update from Glen on Vancouver meeting schedule Item 3: Evaluation of new gtlds (.biz, .info etc as well as .travel, .jobs. .mobi etc) - determine next steps E.g - clearly define remaining questions - a 30 day comment period - require constituency statements, registry operator statements - staff to produce evaluation report - identify time required from staff Item 4: Policy Development Process for new gtlds - initiate vote for an issues report (as per annex A, Section 1 (b)) of the bylaws) - issues report to contain background material on: * whether to continue to introduce new gTLDs - collect previous submissions from constituencies on new gTLDs * the criteria for approving applications for new gTLDs - collect previous material used for .org and .net tenders * the allocation method, assuming that there was a limit to how many gTLDs could be introduced at once - collect previous input (e.g OECD etc) * the key contractual conditions for those gTLDs which might include conditions such as : escrow policies, obligation to use an ICANN accredited registrar etc. - collect current significant conditions from new gTLD agreements Item 5: Policy development for IDNs - recommend request staff to provide a background document listing all past Board decisions regarding the implementation of IDNs, and the status of the IDN guidelines - this can be a precursor to motion to request an official issues report - establish clearly roles of: -- President's Advisory Committee on IDN -- IDN registry review group (gtld and cctld reps) to development Guidelines for the Implementation of the IETF IDN standards -- GAC work on IDNs -- GNSO/ccNSO policy development initiative Item 6: Draft terms of reference for GNSO Review - review current version Item 7: Discussion whether to initiate an "issues report" on single letter domain names ((as per annex A, Section 1 (b)) of the bylaws)) Item 8: Update on GNSO Planning teleconferences Item 9: Any other business

1 0

RE: [council] GNSO current work items - September
by Bruce Tonkin Sept. 16, 2005

Sept. 16, 2005

Thanks Maria. Please also add the issues report request from Jan 05 on secondary market/deleted names. It could be listed as on hold until resources available. Or noted as "to be prioritised". Regards, Bruce ________________________________ From: owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] On Behalf Of Maria Farrell Sent: Thursday, 15 September 2005 10:52 PM To: council(a)gnso.icann.org Subject: [council] GNSO current work items - September Dear all, Ahead of next week's GNSO Council call, please find attached the most recent version of the table on current GNSO work items. All the best, Maria

2 1

RSS Feed on ICANN Website
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG Sept. 16, 2005

Sept. 16, 2005

[To: liaison6c[at]gnso.icann.org; council[at]gnso.icann.org] [To: ga[at]gnso.icann.org; announce[at]gnso.icann.org] [To: gnso-dow123[at]gnso.icann.org] FYI from ICANN Technical Staff. Some of you may have seen this already, but we now have an RSS feed on the main ICANN web page. RSS stands for Really Simple Syndication and is meant to push out information to the subscriber. In order to subscribe, you must have an application known as an RSS Reader (or News Aggregator). Then you just type in the url of the feed:. Everytime something is updated in the New and Noteworthy section of the ICANN website (the middle portion of the main page), your news reader will see the change and notify you. You can then read the blurb within the reader or click the link provided within the reader and be directed to the actual article. The URL for our ICANN feed is: feed://www.icann.org/rss/news.rss . By clicking on the orange RSS icon, you will also see this feed: url. Many applications have RSS readers built in. Some browsers like Apple's Safari and some mail applications like Thunderbird have integrated RSS-handling features. There is also quite a variety of third party RSS readers. I hesitate to recommend any one application, but a pretty comprehensive list can be found at: http://en.wikipedia.org/wiki/List_of_news_aggregators as well as web-based RSS readers such as www.bloglines.com For those of you who manage announcement lists, this would be a good item to add to your newsletter. Kudos to our webmaster, Yan Sun, for getting this up and running! In related news; using RSS technology, Yan has been working with Glen de Saint Gery (and I've missed some accents there somewhere, sorry Glen!) on getting Podcasting of GNSO teleconferences. Podcasting is very similar to the RSS feeds but will push mp3 audio files to your computer if you have the right software (Apple's iTunes for example, I don't have a good list of alternate applications for podcasting). The GNSO podcasts can be found at: http://gnso.icann.org/calendar/ and you'll find two seperate podcast RSS links there. Simply click on the RSS icon and copy the feed: URL into a podcast compatible application to subscribe. It will download the mp3 automatically to your computer next time there's an audio update. Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

3 2

WIPO-II and new gTLDs
by Bruce Tonkin Sept. 15, 2005

Sept. 15, 2005

Hello All, We should also look at including the input from WIPO-II into the policy development process on the criteria or conditions associated with new gTLDs. Note that the more recent gTLD agreements already have some restrictions related to country names etc. Just to be clear - I am not proposing that we pre-empt the outcome of the PDP with respect to the input from WIPO-II, merely suggesting that this material be part of the background material. Regards, Bruce

2 1

GNSO Council draft minutes, 8 September 2005
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG Sept. 15, 2005

Sept. 15, 2005

[To: council[at]gnso.icann.org] Dear Council members, Please find the GNSO Council draft minutes for the teleconference held on 8 September 2005. Please let me know what changes you would like made. Thank you very much. Kind regards, Glen -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

GNSO current work items - September
by Maria Farrell Sept. 15, 2005

Sept. 15, 2005

Dear all, Ahead of next week's GNSO Council call, please find attached the most recent version of the table on current GNSO work items. All the best, Maria

1 0

Draft Agenda for GNSO Council teleconference on Thursday 22 September 2005
by Bruce Tonkin Sept. 15, 2005

Sept. 15, 2005

Draft Agenda for Council meeting Thursday 22 September 2005 Coordinated Universal Time UTC 12:00 (5:00 Los Angeles, 8:00 Washington DC, 14:00 Brussels, 22:00 Melbourne) Item 1: Approval of minutes - teleconference - 18 August 2005 Item 2: Staff action items - list of current GNSO work items - status report on single letter domain names - update on statements of interest and amendment to the bylaws - GNSO Councillors induction proposal for Vancouver - GNSO session in ICANN newcomers session at Vancouver Item 3: Evaluation of new gtlds (.biz, .info etc as well as .travel, .jobs. .mobi etc) - determine next steps E.g - clearly define remaining questions - a 30 day comment period - require constituency statements, registry operator statements - staff to produce evaluation report - identify time required from staff Item 4: Policy Development Process for new gtlds - initiate vote for an issues report (as per annex A, Section 1 (b)) of the bylaws) - issues report to contain background material on: * whether to continue to introduce new gTLDs - collect previous submissions from constituencies on new gTLDs * the criteria for approving applications for new gTLDs - collect previous material used for .org and .net tenders * the allocation method, assuming that there was a limit to how many gTLDs could be introduced at once - collect previous input (e.g OECD etc) * the key contractual conditions for those gTLDs which might include conditions such as : escrow policies, obligation to use an ICANN accredited registrar etc. - collect current significant conditions from new gTLD agreements Item 5: Policy development for IDNs - recommend request staff to provide a background document listing all past Board decisions regarding the implementation of IDNs, and the status of the IDN guidelines - this can be a precursor to motion to request an official issues report - establish clearly roles of: -- President's Advisory Committee on IDN -- IDN registry review group (gtld and cctld reps) to development Guidelines for the Implementation of the IETF IDN standards -- GAC work on IDNs -- GNSO/ccNSO policy development initiative Item 6: Draft terms of reference for GNSO Review - review current version Item 7: Update on GNSO Planning teleconferences Item 8: Any other business

2 1

President's Advisory Committee on IDNs
by Bruce Tonkin Sept. 15, 2005

Sept. 15, 2005

Hello All, I note from the Board minutes of the Kuala Lumpur meeting (23 July 2004): http://www.icann.org/minutes/kl-resolutions-23jul04.htm That the ICANN Board asked the President to establish a President's Advisory Committee on IDN, to provide the Board and ICANN community with advice on issues that relate to IDN policies, in particular issues that impact the implementation of IDN especially at the top level. See full resolution below. Regards, Bruce Tonkin Whereas, the ICANN Board recognizes that it is important that the Internet evolve to be more accessible to those who do not use the ASCII character set. Whereas, the Board notes that the internationalization of the Internet's domain name system must be accomplished through standards that are open, non-proprietary, and fully compatible with the Internet's existing end-to-end model and that preserve globally unique naming in a universally resolvable public name space. Whereas, the IETF has adopted a four-part protocol suite defining a standard for internationalized domain names in applications that was published as RFCs 3490, 3491, 3492, and 3454. Whereas, a broad range of registries, experts, and other stakeholders in the ICANN community have been working hard for several years to develop registry-level registration policies, for example RFC 3743. Whereas, the ICANN Board has had Working Groups investigate facts and identify issues that may arise concerning IDN's and these Committees have reported to the community. Whereas, the Board reiterates the importance of implementing the technical standards for IDN's in a coordinated manner, that does not destabilize the global, single root, unique identifier system. Whereas the Board recognises that significant work remains to be undertaken outside of ICANN's scope in order to provide end-to-end availability of IDN's to end-users and that close co-ordination of these efforts is needed. Whereas, ICANN is committed to the further study of IDNs in the TLD space, and commits to facilitating venues in which IDN can be discussed, and encourages venues to further encourage the implementation of IDNs. Resolved [04.68] that the ICANN staff report to the Board and community on the implementation status of IDNs and pending issues. Resolved further [04.69] that the ICANN staff work with registries and other administrators who use IDNs to report back on usability, successes, and other relevant experiences. Resolved [04.70] to thank the IDN Workshop organizers and participants for their important contributions to the Workshop, and sharing of knowledge on issues surrounding the implementation of IDN. Resolved [04.71] that the Board instructs the President to establish a President's Advisory Committee on IDN, to provide the Board and ICANN community with advice on issues that relate to IDN policies, in particular issues that impact the implementation of IDN especially at the top level.

1 0

Version 1.2 of Terms of Reference for the GNSO Review
by Bruce Tonkin Sept. 15, 2005

Sept. 15, 2005

Hello All, Please find attached the latest draft of the terms of reference for the GNSO Review as updated by Dr Liz Williams in response to comments received on the list and also based on comments received on the joint Council/Board call last week. Please provide any final comments prior to the GNSO Council meeting next week. Regards, Bruce Tonkin

1 0

IDN workshop in Vancouver
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG Sept. 15, 2005

Sept. 15, 2005

[To: ga[at]gnso.icann.org; announce[at]gnso.icann.org] [To: liaison6c[at]gnso.icann.org; council[at]gnso.icann.org] ICANN announces a full-day IDN workshop in Vancouver http://www.icann.org/announcements/announcement-14sep05.htm A full-day IDN workshop will be held during the ICANN meeting in Vancouver. This workshop will build on discussions concerning deployment of internationalized top level domains that occurred during the IDN workshop in Luxembourg. ICANN is issuing this formal call for papers to those who wish to actively participate in the sessions on internationalized top level domain deployment. Presentations should last 15-25 minutes, with time for questions from the floor. Papers should be submitted by 15 November 2005. The Luxembourg IDN workshop described opportunities associated with the deployment of internationalized TLDs (sometimes described as "idn.idn"). The Vancouver workshop will focus on various topics, including: Identifying and assessing IDN TLD implementation issues, and Potential risks of IDN TLD deployment to a global interoperable Internet. All interested parties are invited to provide suggestions for topics and questions that should be addressed during the workshop, to the IDN-Vancouver Discussion Forum (see below). Discussion in the on-line forum below is also open for the review of the following documents. These documents are focused on the implementation of IDNs at the top level. National and Local Characters for DNS Top Level Domain (TLD) http://www.ietf.org/internet-drafts/draft-klensin-idn-tld-05.txt The Proposal for Internationalizing ccTLD Names, By Chinese Domain Name Consortium (CDNC) http://www.icann.org/announcements/idn-tld-cdnc.pdf New gTLD Questions Paper, By ICANN Staff http://www.icann.org/tlds/new-gTLD-questions.pdf If you wish to submit a paper or have documents regarding deployment of internationalized top level domains posted here for review please contact Tina Dam, ICANN's Chief gTLD Registry Liaison. Comments to deployment of Internationalized TLDs can be submitted to: idn-tld-comments(a)icann.org The archived comments regarding deployment of Internationalized TLDs are at: http://forum.icann.org/lists/idn-tld-comments/ Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0