August 2013 - council - lists.icann.org

Advisory: Registrar Implementation of the 2013 RAA's Whois Requirements
by Glen de Saint Géry 01 Aug '13

01 Aug '13

https://www.icann.org/en/news/announcements/announcement-31jul13-en.htm Advisory: Registrar Implementation of the 2013 RAA's Whois Requirements 31 July 2013 Purpose This advisory is intended to help registrars understand which Whois fields must be populated pursuant to the 2013 Registrar Accreditation Agreement<https://www.icann.org/en/resources/registrars/raa/approved-with-specs-27jun…> immediately upon their signing of the agreement and which are not required until 1 January 2014. Background The 2013 Registrar Accreditation Agreement ("RAA"), like earlier forms of the registrar accreditation agreement, requires registrars to operate web-based and port 43 Whois services that provide public access to certain enumerated registration data fields. Section 3.3.1<https://www.icann.org/en/resources/registrars/raa/approved-with-specs-27jun…> of the RAA specifies required data fields, such as the name and address of the registered name holder, and name, address, email address, and phone number of the administration and technical contacts for each domain name (among other required data elements). The 2013 RAA, unlike previous versions of the registrar accreditation agreement, also includes a Registration Data Directory Service (Whois) Specification<https://www.icann.org/en/resources/registrars/raa/approved-with-specs-27jun…> which, among other things, describes a mandatory format registrars must use when publishing Whois data. This format includes a number of fields that were not required by earlier versions of the RAA. As examples, the Registration Data Directory Service (Whois) Specification requires registrars to include in their Whois output the email address and telephone number of the registrar's abuse point of contact as well as the IDs or handles used by the registry to identify the domain name and its contacts. Because the 2013 RAA includes a number of new operational responsibilities for registrars that could reasonably take weeks or months to implement, the agreement also incorporates a Transition Addendum<https://www.icann.org/en/resources/registrars/raa/approved-with-specs-27jun…>. The Transition Addendum describes a number of obligations for which ICANN will not require registrar compliance until 1 January 2014. By way of example, registrars are not required to fully implement an abuse point-of-contact (see section 3.18<https://www.icann.org/en/resources/registrars/raa/approved-with-specs-27jun…> of the RAA) until 1 January 2014. Some registrars have asked ICANN to clarify whether they must immediately begin populating Whois data with fields, such as the abuse point-of-contact email address and telephone number, even though they are not yet required to comply with the underlying obligation. Required Whois Fields The Transition Addendum to the RAA explicitly references a list of RAA provisions for which registrar compliance is not required until 1 January 2014. The Registration Data Directory Service (Whois) Specification is not included within that list of provisions. Accordingly, registrars are immediately required to comply with obligations described in that specification, including the obligation to format Whois data as defined in the specification. Registrars are not, however, required to include in their Whois output, data elements that don't yet exist or are not already in the registrar's possession. This includes reference to the items for which compliance is not yet required. To be clear, registrars who are subject to the 2013 RAA must continue to include all of the fields described in section 3.3.1 of the RAA in their Whois output and the data elements they have within their possession. Registrars are not, however, required to include the following fields in their Whois output until 1 January 2014 (although registrars may, and are encouraged to, comply earlier): Registry Domain ID Registrar Abuse Contact Email Registrar Abuse Contact Phone Domain Status Registry Registrant ID Registrant Phone Registrant Phone Ext Registrant Fax Registrant Fax Ext Registrant Email: Registry Admin ID Registry Tech ID DNSSEC Last update of WHOIS database Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

MP3 recording GNSO Council teleconference, Thursday, 1 August 2013
by Glen de Saint Géry 01 Aug '13

01 Aug '13

[To: liaison6c[at]gnso.icann.org; council[at]gnso.icann.org] Please find the MP3 recording of the GNSO Council teleconference, held on Thursday, 1 August, 2013 at: http://audio.icann.org/gnso/gnso-council-20130801-en.mp3 on page http://gnso.icann.org/en/group-activities/calendar#aug Thank you. Happy listening! Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0

Requirements for GNSO Council meeting Thursday, 1 August at 15:00UTC
by Glen de Saint Géry 01 Aug '13

01 Aug '13

Dear Councillors, As a reminder for Thursday's Council meeting, 'In order for the GNSO Council to initiate a vote, a quorum must be present. A quorum is a majority of voting members in each House, which must include at least one member of each Stakeholder Group'. Also note that, 'An absent Council member does not count toward quorum even if a proxy has been established. A Temporary Alternate (see Section 4.7-Temporary Alternate below) if present, would count toward quorum'. Furthermore, as it concerns a vote to approve a PDP recommendation, absentee voting is allowed (but absentee voting does not affect quorum requirements). As noted in the operating procedures, 'Absentee ballots, when permitted, must be submitted within the announced time limit, which shall be 72 hours from the meeting's adjournment. In exceptional circumstances, announced at the time of the vote, the Chair may reduce this time to 12 hours or extend the time to 7 calendar days, provided such amendment is verbally confirmed by all Vice-Chairs present'. As it concerns a PDP vote, to approve a PDP Recommendation with a GNSO Supermajority it requires an affirmative vote of a GNSO Supermajority (A "GNSO Supermajority" shall mean: (a) two-thirds (2/3) of the Council members of each House, or (b) three-fourths (3/4) of one House and a majority of the other House."). Please make the necessary arrangements if you are not able to be present on Thursday. The link to the form to be completed by a SG/C officer can be found here: http://gnso.icann.org/council/abstention-notification-form-en.htm Thank you very much. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

2 1

TR: GNSO Council Abstention Notification Form [#129]
by Glen de Saint Géry 01 Aug '13

01 Aug '13

FYI De : ICANN [mailto:no-reply@wufoo.com] Envoyé : jeudi 1 août 2013 06:44 À : gnso.secretariat(a)icann.org; council(a)gnso.icann.org Objet : GNSO Council Abstention Notification Form [#129] Name of Officer: * Robin Gross Officer Email Address: * robin(a)ipjustice.rg<mailto:robin@ipjustice.rg> Date Prepared: * Wednesday, July 31, 2013 GNSO Organization: * Non-Commercial Stakeholder Group Officer Position or Title: * Chair Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * Wolfgang Kleinwachter will be absent from the 1 August 2013 GNSO Council Meeting and therefore David Cake will serve as Wolfgan's proxy for that meeting. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * Any and all. Date upon which the remedy will expire or terminate: [Note: may not exceed 3 months initially; may be renewed by sending an email with explanation to GNSO Secretariat] * Friday, August 2, 2013 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. * Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). * Yes Please identify the GNSO Councilor who will serve as the voting proxy: * David Cake

1 0

TR: GNSO Council Abstention Notification Form [#130]
by Glen de Saint Géry 01 Aug '13

01 Aug '13

FYI De : ICANN [mailto:no-reply@wufoo.com] Envoyé : jeudi 1 août 2013 11:25 À : gnso.secretariat(a)icann.org; council(a)gnso.icann.org Objet : GNSO Council Abstention Notification Form [#130] Name of Officer: * Keith Drazek Officer Email Address: * kdrazek(a)verisign.com<mailto:kdrazek@verisign.com> Date Prepared: * Thursday, August 1, 2013 GNSO Organization: * Registries Stakeholder Group Officer Position or Title: * RySG CJhair Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * Jeff Neuman may be unavailable during the next GNSO Council call on August 1, 2013. We request that his vote be proxied to Jonathan Robinson. If Jonathan Robinson is also unavailable, then Jeff's vote should be proxied to Ching Chiao. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * Votes during the next GNSO Council meeting - August 1, 2013 Date upon which the remedy will expire or terminate: [Note: may not exceed 3 months initially; may be renewed by sending an email with explanation to GNSO Secretariat] * Wednesday, August 7, 2013 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. * Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). * Yes Please identify the GNSO Councilor who will serve as the voting proxy: * Jonathan Robinson

1 0

Reminder: Proposed Agenda for the GNSO Council Meeting 1 August 2013
by Glen de Saint Géry 01 Aug '13

01 Aug '13

Dear Councillors, Please find below the proposed agenda for the GNSO Council meeting on 1 August 2013 at 15:00 UTC. This agenda confirms the one item contained in the 18 July 2013 notice of the GNSO Council meeting (see http://gnso.icann.org/mailing-lists/archives/council/msg14866.html) and there have been no additions since provision of that notice. Please let me know if you have any questions. Thank you. Kind regards, Glen Proposed Agenda for the GNSO Council Meeting 1 August 2013 https://community.icann.org/display/gnsocouncilmeetings/Agenda+01+August+20… This agenda was established according to the GNSO Council Operating Procedures approved 13 September 2012 for the GNSO Council and updated. <http://gnso.icann.org/en/council/op-procedures-13jun13-en.pdf > For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Meeting Times 15:00UTC<http://tinyurl.com/bojlrbx> http://tinyurl.com/lsq557k Coordinated Universal Time 15:00 UTC 08:00 Los Angeles; 11:00 Washington; 16:00 London; 17:00 Paris; 03:00 Wellington next day Dial-in numbers will be sent individually to Council members. Councilors should notify the GNSO Secretariat in advance if a dial out call is needed. Item 1: Administrative matters (10 mins) 1.1 Roll Call 1.2 Statement of interest updates 1.3 Review/amend agenda Item 2: Opening Remarks from Chair (10 mins) Review focus areas and provide updates on specific key themes / topics Include review of Projects List<http://gnso.icann.org/meetings/projects-list.pdf> and Action List<https://community.icann.org/display/gnsocouncilmeetings/Action+Items>. Comments or questions arising. Item 3: Consent agenda No items Item 4: MOTION - Locking of a Domain Name subject to UDRP Proceedings (15 mins) The "locking" of a domain name registration associated with UDRP proceedings is not something that is literally required by the UDRP as written, but is a practice that has developed around it. As a result, there is no uniform approach, which has resulted in confusion and misunderstandings. The GNSO Council initiated a PDP on this specific topic in December 2011 and tasked the WG to make recommendations to the GNSO Council to address the issues identified with the locking of a domain name subject to UDRP Proceedings. The PDP Working Group has now submitted its Final Report for GNSO Council consideration containing 17 full consensus recommendations (see http://gnso.icann.org/en/issues/locking/domain-name-final-05jul13-en.pdf). 4.1 - Review motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+1-August-20…> (See: https://community.icann.org/display/gnsocouncilmeetings/Motions+1-August-20…) 4.3 - Discussion 4.4 - Vote (Threshold supermajority) Item 5: Any Other Business (5 min) Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article X, Section 3) 9. Except as otherwise specified in these Bylaws, Annex A hereto, or the GNSO Operating Procedures, the default threshold to pass a GNSO Council motion or other voting action requires a simple majority vote of each House. The voting thresholds described below shall apply to the following GNSO actions: a. Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. b. Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A<http://www.icann.org/en/about/governance/bylaws#AnnexA>): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. c. Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority. d. Approve a PDP Team Charter for a PDP Within Scope: requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. e. Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. f. Changes to an Approved PDP Team Charter: For any PDP Team Charter approved under d. or e. above, the GNSO Council may approve an amendment to the Charter through a simple majority vote of each House. g. Terminate a PDP: Once initiated, and prior to the publication of a Final Report, the GNSO Council may terminate a PDP only for significant cause, upon a motion that passes with a GNSO Supermajority Vote in favor of termination. h. Approve a PDP Recommendation Without a GNSO Supermajority: requires an affirmative vote of a majority of each House and further requires that one GNSO Council member representative of at least 3 of the 4 Stakeholder Groups supports the Recommendation. i. Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, j. Approve a PDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. k. Modification of Approved PDP Recommendation: Prior to Final Approval by the ICANN Board, an Approved PDP Recommendation may be modified or amended by the GNSO Council with a GNSO Supermajority vote. l. A "GNSO Supermajority" shall mean: (a) two-thirds (2/3) of the Council members of each House, or (b) three-fourths (3/4) of one House and a majority of the other House." Appendix 2: Absentee Voting Procedures (GNSO Operating Procedures 4.4<http://gnso.icann.org/council/gnso-operating-procedures-22sep11-en.pdf>) 4.4.1 Applicability Absentee voting is permitted for the following limited number of Council motions or measures. a. Initiate a Policy Development Process (PDP); b. Approve a PDP recommendation; c. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; d. Fill a Council position open for election. 4.4.2 Absentee ballots, when permitted, must be submitted within the announced time limit, which shall be 72 hours from the meeting's adjournment. In exceptional circumstances, announced at the time of the vote, the Chair may reduce this time to 24 hours or extend the time to 7 calendar days, provided such amendment is verbally confirmed by all Vice-Chairs present. 4.4.3 The GNSO Secretariat will administer, record, and tabulate absentee votes according to these procedures and will provide reasonable means for transmitting and authenticating absentee ballots, which could include voting by telephone, e- mail, web-based interface, or other technologies as may become available. 4.4.4 Absentee balloting does not affect quorum requirements. (There must be a quorum for the meeting in which the vote is initiated.) ---------------------------------------------------------------------------- Local time between March and October, Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 15:00 ---------------------------------------------------------------------------- California, USA (PST<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-8+1DST 08:00 New York/Washington DC, USA (EST) UTC-5+1DST 11:00 Rio de Janiero, Brazil (BRST) UTC-3+1DST 12:00 Montevideo, Uruguay (UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-3+1DST 12:00 London, United Kingdom (BST) UTC+0DST 16:00 Abuja, Nigeria (WAT<http://www.timeanddate.com/library/abbreviations/timezones/africa/wat.html>) UTC+1+0DST 16:00 Bonn, Germany (CEST) UTC+1+0DST 17:00 Stockholm, Sweden (CET) UTC+1+0DST 17:00 Istanbul, Turkey (EEST) UTC+2+0DST 18:00 Ramat Hasharon, Israel(IST<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+2+0DST 18:00 Karachi, Pakistan (PKT<http://www.timeanddate.com/library/abbreviations/timezones/asia/pkt.html> ) UTC+5+0DST 20:00 Beijing/Hong Kong, China (HKT ) UTC+8+0DST 23:00 Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+0DST 23:00 Wellington, New Zealand (NZDT<http://www.timeanddate.com/library/abbreviations/timezones/pacific/nzdt.html> ) UTC+12+1DST 03:00 (next day) ---------------------------------------------------------------------------- The DST starts/ends on last Sunday of October 2013, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com http://tinyurl.com/lsq557k Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

4 3