ICANN/GNSO GNSO Email List Archives

[council]


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

[council] - Preliminary Issue Report - New gTLD Subsequent Procedures

  • To: "council@xxxxxxxxxxxxxx" <council@xxxxxxxxxxxxxx>
  • Subject: [council] - Preliminary Issue Report - New gTLD Subsequent Procedures
  • From: Steve Chan <steve.chan@xxxxxxxxx>
  • Date: Tue, 18 Aug 2015 20:26:52 +0000
  • Accept-language: en-US
  • List-id: council@xxxxxxxxxxxxxx
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Thread-index: AQHQ2fQ3MIPLeEXfTECYOC5+tAR+6g==
  • Thread-topic: [council] - Preliminary Issue Report - New gTLD Subsequent Procedures
  • User-agent: Microsoft-MacOutlook/14.5.3.150624

Dear Councilors,

Staff is on track to be able to deliver the Preliminary Issue Report on New
gTLD Subsequent Procedures for public comment by the end of August, as
discussed on the previous GNSO Council meeting. However, I wanted to note
that during the meeting, the possibility of providing for an extended public
comment period was also discussed, which would keep it open through the
ICANN54 meeting. This topic is expected to be on the agenda for the next
Council meeting, scheduled for 03 September and as such, it may make sense
to delay the publication of the report by approximately 3 days to allow for
discussion during the meeting and a decision to be made, to avoid confusion
from possibly amending the comment close date. The impact appears to be
minimal:
* Publish 31 August -> 40 Day Public Comment -> Close 10 October (note that
this is a Saturday)
* Publish 3 September -> 40 Day Public Comment -> Close 13 October
* Publish 3 September -> 60 Day (for instance) Public Comment -> Close 2
November  
Staff is leaning towards waiting the three days and immediately putting in
the request to publish the Preliminary Issue Report after a decision is
made, but wanted to be sure there were no strong objections to this
approach.

Best,



Steven Chan
Sr. Policy Manager

ICANN
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536
steve.chan@xxxxxxxxx
 <mailto:steve.chan@xxxxxxxxx>
direct: +1.310.301.3886
mobile: +1.310.339.4410
tel: +1.310.301.5800
fax: +1.310.823.8649


Attachment: smime.p7s
Description: S/MIME cryptographic signature



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