ICANN/GNSO GNSO Email List Archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

RE: [council] Draft GNSO Council Agenda 25 September 2008


Kristina,

Here is Denise's response to your question: "Services Staff intends to provide 
a status update on RAA Amendments, as requested by the Council." Does that 
answer your question or were you asking whether there would be more than just a 
status report?

Chuck

> -----Original Message-----
> From: owner-council@xxxxxxxxxxxxxx 
> [mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of Rosette, Kristina
> Sent: Friday, September 19, 2008 11:03 AM
> To: Glen de Saint Géry; council@xxxxxxxxxxxxxx
> Subject: RE: [council] Draft GNSO Council Agenda 25 September 2008
> 
> 
> Does 4.7 include the presentation/discussion by staff that 
> Denise referenced in our last meeting? 
> 
> -----Original Message-----
> From: owner-council@xxxxxxxxxxxxxx 
> [mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of Glen de Saint Géry
> Sent: Thursday, September 18, 2008 12:06 PM
> To: council@xxxxxxxxxxxxxx
> Subject: [council] Draft GNSO Council Agenda 25 September 2008
> 
> Dear Councilors,
> 
> Proposed GNSO Council Agenda 25 September 2008
> 
> This agenda was established according to the Rules of 
> Procedure for the GNSO Council
> 
> Coordinated Universal Time12:00 UTC - see below for local 
> times (05:00 Los Angeles, 08:00 Washington DC, 13:00 London, 
> 14:00 Brussels, 22:00 Melbourne)
> 
> Chuck Gomes will be chairing the GNSO Council meeting 
> Scheduled time for meeting 120 mins.
> Dial-in numbers sent individually to Council members.
> 
> Item 0: Roll call of Council members
> Item 1: Update any statements of interest Item 2: Review/amend agenda
> 
> Item 3: Approve GNSO Council minutes of 4 September 2008 
> (Items 0-3 10 mins )
> 
> Item 4: Status Update (15 mins)
> 4.1 ICANN Board
> 
> 4.2 Fast Flux PDP WG
> 
> 4.3 Inter-Registrar Transfer Policy (IRTP) Part A PDP
> 
> 4.4 New gTLDs
> 
> 4.5 Fast Track
> 
> 4.6 AGP
> 
> 4.7 RAA Amendments
> 
> Item 5: Discussion on GNSO Response concerning Geo Regions 
> (15 mins) ICANN Geographic Regions
> -- Constituency feedback
> -- Next Steps
> 
> Item 6: Discussion/Decision GNSO Restructuring and Plan (25 mins)
> -- Overview of Plan
> https://st.icann.org/gnso_transition/index.cgi?gnso_improvements
> 
> Item 7: ICANN subsidization of GNSO travel expenses (10 mins).
> 
> - longer term procedure
> --Next Steps
> 
> Item 8: Planning for Cairo (15 mins)
> 
> 8.1 Proposal for Trans-Silo Joint meeting (ccNSO, GNSO, GAC, 
> ALAC) on Monday 3 November 2008
> 8.2 Thursday 6 November 2008
> Proposed Topics:
> * Issues at the cross-section of implementation of New gTLD 
> (LDH & IDN), and Fast Track IDNccTLDs
> * ICANN Transition and the PSC
> 8.3 Other
> 
> Item 9: Whois Hypotheses Study Group (10 mins) 
> http://gnso.icann.org/issues/whois/whois-study-hypothesis-grou
> p-report-to-council-26aug08.pdf
> -- Constituency feedback
> -- Next Steps
> 
> Item 10: Motion on request for issues report on Registration 
> Abuse Policies. (10 mins)
> Motion: Mike Rodenbaugh Second: Greg Ruth
> Whereas:
> 1. ICANN's mission is to ensure the security and stability of 
> the DNS, and to develop policy reasonably related to that mission.
> 2. Various forms of DNS abuse, in isolation and/or in the 
> aggregate, cause a less secure and stable DNS.
> 3. Some of ICANN's gTLD registry agreements and appended 
> registry-registrar agreements contain a provision such as 
> Section 3.6.5 of the.info Registry Agreement, Appendix 8 :
> 3.6.5. (Registrars) acknowledge and agree that Afilias 
> reserves the right to deny, cancel or transfer any 
> registration or transaction, or place any domain name(s) on 
> registry lock, hold or similar status, that it deems 
> necessary, in its discretion; (1) to protect the integrity 
> and stability of the registry; (2) to comply with any 
> applicable laws, government rules or requirements, requests 
> of law enforcement, or any dispute resolution process; (3) to 
> avoid any liability, civil or criminal, on the part of 
> Afilias, as well as its affiliates, subsidiaries, officers, 
> directors, and employees; (4) per the terms of the 
> registration agreement or (5) to correct mistakes made by 
> Afilias or any Registrar in connection with a domain name 
> registration.
> Afilias also reserves the right to place upon registry lock, 
> hold or similar status a domain name during resolution of a dispute.
> 
> 4. Afilias, the dotInfo Registry Operator, per its recent 
> RSEP request, has sought to clarify and implement its 
> specific abusive registration policy with respect to this 
> provision. This request has been approved by ICANN.
> 5. Some of ICANN's gTLD registry agreements, notably the 
> Verisign contracts for .com and .net, have no such provision. 
> Other gTLD registry agreements do contain such provision, but 
> the registry operators have not developed or have 
> inconsistently developed abusive registration policies.
> The GNSO Council resolves to request an Issues Report from 
> ICANN Staff with respect to the following:
> 1. To identify and describe the various provisions in 
> existing and previous gTLD registry and registry-registrar 
> agreements which relate to contracting parties' ability to 
> take action in response to abuse.
> 2. To identify and describe various provisions in a 
> representative sampling of gTLD registration agreements which 
> relate to contracting parties' and/or registrants rights and 
> obligations with respect to abuse.
> 3. To identify and describe any previous discussion in ICANN 
> fora which substantively pertains to provisions of this 
> nature in any of these agreements.
> 4. To identify and describe potential options for further 
> Council consideration, relating to consistency and propriety 
> of provisions of this nature in all of these agreements.
> 
> Item 11: Any Other Business (5 mins)
> 
> (05:00 Los Angeles, 08:00 Washington DC, 13:00 London, 14:00 
> Brussels, 22:00 Melbourne)
> --------------------------------------------------------------
> --------------
> Local time between March and October, Summer in the NORTHERN 
> hemisphere
> --------------------------------------------------------------
> --------------
> Reference (Coordinated Universal Time) UTC 12:00
> --------------------------------------------------------------
> --------------
> California, USA (PST) UTC-7+1DST 05:00
> New York/Washington DC, USA (EST) UTC-4+1DST 08:00 Buenos 
> Aires, Argentina UTC-3+0DST 09:00 Rio de Janeiro, Brazil 
> UTC-3+0DST 09:00 London, United Kingdom (BST) UTC+1DST 13:00 
> Brussels, Belgium (CEST) UTC+1+1DST 14:00 Karlsruhe, Germany 
> (CEST) UTC+1+1DST 14:00 Barcelona, Spain (CEST) UTC+1+1DST 
> 14:00 Oslo, Norway (CEST) UTC+1+1DST 14:00 Karachi, Pakistan 
> UTC+5+1DST 18:00 Phnom Penh, Cambodia UTC+7+0DST 19:00 Hong 
> Kong, China UTC+8+0DST 20:00 Singapore, Singapore UTC+8+0DST 
> 20:00 Melbourne, Australia (EST) UTC+10+0DST 22:00
> --------------------------------------------------------------
> --------------
> The DST starts/ends on last Sunday of October 2008, 2:00 or 
> 3:00 local time (with exceptions)
> ----------------------------------------------------------------------
> For other places see http://www.timeanddate.com
> 
> Glen de Saint Géry
> GNSO Secretariat
> gnso.secretariat@xxxxxxxxxxxxxx
> http://gnso.icann.org
> 
> 
> 
> 




<<< Chronological Index >>>    <<< Thread Index >>>