ICANN/GNSO GNSO Email List Archives

[council]


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

[council] GNSO Council resolutions 13 September 2012

  • To: "council@xxxxxxxxxxxxxx" <council@xxxxxxxxxxxxxx>
  • Subject: [council] GNSO Council resolutions 13 September 2012
  • From: Glen de Saint Géry <Glen@xxxxxxxxx>
  • Date: Fri, 14 Sep 2012 01:27:09 -0700
  • Accept-language: fr-FR, en-US
  • Acceptlanguage: fr-FR, en-US
  • List-id: council@xxxxxxxxxxxxxx
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Thread-index: Ac2SUq8yJuIlt7v6Qxq+CrOoPF+6/g==
  • Thread-topic: GNSO Council resolutions 13 September 2012

Dear All,

On 13 September 2012 the GNSO Council unanimously passed the following 
resolutions:

Consent agenda:

Resolved sending the IRD-WG letter from GNSO Council to ICANN Board.

13 September 2012
To: ICANN Board
From: Chair of the GNSO Council and Chair of the SSAC
Via: SSAC and GNSO Liaisons to the ICANN Board

We hereby forward to you the Final Report of the Internationalized Registration 
Data Working Group (IRD-WG). The SSAC has approved the report. At its meeting 
on 27 June 2012 in Prague the GNSO Council passed a motion by which it approved 
the
delivery of the report to the Board. In its motion the Council also agreed to 
review the recommendations in the Report and to provide to the Board its advice 
with regard to those recommendations that may have policy implications.
As you may recall, on 26 June 2009 the ICANN Board of Directors approved a 
resolution (2009.06.26.18) requesting that the GNSO and the SSAC, in 
consultation with staff, convene an IRD-WG to study the feasibility and 
suitability of introducing display
specifications to deal with the internationalization of registration data. In 
November 2010 the IRD-WG produced an Interim Report requesting community input 
on several questions relating to possible models for internationalizing Domain 
Name Registration
Data. On 03 October the IRD-WG posted a draft Final Report in the Public Forum 
for comment for 45 days. After considering the comments received, the attached 
Final Report is the IRD-WG's response to the Board request regarding the 
feasibility and suitability of introducing display specifications to deal with 
the internationalized registration data. The Report contains the following 
recommendations:

1. To introduce submission and display specifications, ICANN staff should 
develop, in consultation with the community, a data model for domain 
registration data. The data model should specify the elements of the 
registration data, the data flow, and a formal
data schema that incorporates the standards that the working group has agreed 
on for internationalizing various registration data elements. This data model 
should also include tagging information for language/scripts.

2. The GNSO Council and the SSAC should request a common Issue Report on 
translation and transliteration of contact information. The Issue Report should 
consider whether it is desirable to translate contact information to a single 
common language or transliterate contact information to a single common script. 
It should also consider who should bear the burden and who is in the best 
position to address these issues. The Issue Report should consider policy 
questions raised in the IRD-WG Final Report and should also recommend whether 
to start a policy development process (PDP) to address those
questions.

3. ICANN staff should work with the community to identify a Domain Name 
Registration Data Access Protocol that meets the needs of internationalization, 
including 2 but not limited to the work products resulting from recommendations 
1 and 2, and the
requirements enumerated in the IRD-WG Final Report.

4. ICANN should take appropriate steps to require gTLD registries and 
registrars and persuade ccTLD registries and registrars to support the 
following standards:


·          Domain Names - both A-label and U-label forms during both submission 
and display for all domain names except nameservers; nameserver Names- require 
Alabel form, and optionally U-label form;


·         Telephone/fax- ITU-T E.123; Email-RFC 6531; Registration Status- 
Exact EPP status where applicable; Date and time - in UTC as specified in 
[RFC3339], with no offset from the zero meridian.

The GNSO Council and the SSAC welcome comments from the Board concerning this 
report.

Stéphane Van Gelder
Chair, GNSO Council
Patrik Fältström

Chair, ICANN Security and Stability Advisory Committee


Main agenda


Resolved to adopt the revised GNSO Operating Procedures incorporating a consent 
agenda provision and updated voting results table and to adopt a technical 
change in proxy notification



Whereas, the GNSO Council requested the Standing Committee on Improvements 
Implementation (SCI) on 20 February to formalize the process for a consent 
agenda with a view to including the consent agenda in the GNSO rules and 
procedures;

Whereas the SCI deliberated on a process for a consent agenda and reached 
unanimous consensus on a proposed consent agenda provision for inclusion in the 
GNSO Operating Procedures;

Whereas the voting results table included in the GNSO Operating Procedures 
required updating following the adoption of the revised GNSO Policy Development 
Process;

Whereas the revised GNSO Operating Procedures, including the proposed consent 
agenda provision as well as the updated voting results table were put out for a 
minimum 21-day public comment period on 9 July 2012 (see 
http://www.icann.org/en/news/public-comment/gnso-operating-procedures-2012-09jul12-en.htm)
 as required by the ICANN Bylaws;

Whereas as a result of the public comment period, no further changes were 
deemed necessary by the SCI;

Whereas the GNSO Council also requested the SCI to review the current 
procedures in place for proxy voting;

Whereas the SCI reviewed the current procedures in place and recommends that no 
changes are made to the proxy notification procedures in the GNSO Council 
Operating Procedures but instead requests that staff makes a technical change 
so that the proxy notification is sent to the GNSO Council list at the same 
time as it is sent to the Secretariat, which occurs when the form is submitted.

RESOLVED

The GNSO Council adopts the revised GNSO Operating Procedures including the new 
consent agenda provision and the updated voting results table (see 
http://gnso.icann.org/en/council/gnso-operating-procedures-redline-09jul12-en.pdf).

The GNSO Council instructs ICANN staff to post the new version of the GNSO 
Operating Procedures (GOP), which becomes effective immediately upon adoption.

The GNSO Council requests staff to make a technical change so that the proxy 
notification is sent to the GNSO Council list at the same time as it is sent to 
the Secretariat, which occurs when the form is submitted.
Thank you.
Kind regards,

Glen

Glen de Saint Géry
GNSO Secretariat
gnso.secretariat@xxxxxxxxxxxxxx<mailto:gnso.secretariat@xxxxxxxxxxxxxx>
http://gnso.icann.org




Attachment: Final Report of the Internationalized Registration Data Working Group 07 May 2012.pdf
Description: Final Report of the Internationalized Registration Data Working Group 07 May 2012.pdf



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