All, The ICANN staff recognizes the intent behind this resolution and we will begin to think through any implications associated with this recommendation. As a threshold matter, it may be helpful to mention that many structures within ICANN have pre-defined requirements for conducting public comments, including the time frames required for soliciting public comment. These differ today by entity, many requirements are specified in various bylaws provisions applicable to various structures, including requirements applicable to Board-initiated solicitations for public comment. The current bylaws provisions applicable to GNSO Council-related solicitations for public comment are specific to the GNSO Council. Staff has also heard concerns from some Council members about the volume of reports and materials produced by ICANN staff (and possibly working group reports as well) just prior to and during ICANN meetings, because of the challenges associated with reviewing and being prepared to comment on late-breaking documents and reports. For example, staff was directed to complete the registration abuse issues report prior to the Cairo ICANN meeting specifically so that the report could be discussed in Cairo, but, understandably, many Council members were unable to read the report in time for a timely discussion. Thus, it may also be appropriate to consider whether deadlines for other deliverables should also be extended accordingly to further address Council member concerns. Staff looks forward to discussing all this further with Council members. Thanks, Liz