ICANN ICANN Email List Archives

[gnso-policyimpl-wg]


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

Re: [gnso-policyimpl-wg] Notes and updated public comment review tool

  • To: Marika Konings <marika.konings@xxxxxxxxx>
  • Subject: Re: [gnso-policyimpl-wg] Notes and updated public comment review tool
  • From: Tom Barrett <tbarrett@xxxxxxxxxxx>
  • Date: Thu, 9 Apr 2015 09:07:07 -0400

Hi all,

the changes to the second sentence require one more change, since "or" was
changed to "to.  Thus, the previous reference to "either" should be
removed.

as in:

*Furthermore the WG agreed to add in the principles section on ‘community’:*
*Whenever the Board determines that the recommendations of the GNSO do not,
in its view, reflect a broader consensus including the advice of the
Advisory Committees and public comments, it will use existing process
mechanisms to [[[either ]]]send the issue back to the GNSO for further
consideration to initiate broader community discussion.  All final
recommendations would still be the responsibility of the GNSO.  *

*best regards,*

*tom*





On Thu, Apr 9, 2015 at 7:31 AM, Marika Konings <marika.konings@xxxxxxxxx>
wrote:

>  Dear All,
>
>  Please find below the notes from yesterday’s meeting and attached the
> revised public comment review tool. With regard to comment 4.18, those on
> the call agreed to add the following to the principles section:
>
>  *The development and implementation of policy must have a basis in and
> adhere to standards of fairness, notice, transparency, integrity,
> objectivity, predictability and due process consistent with ICANN’s core
> values and in particular its commitment to the global public interest as
> outlined in the ICANN Articles of Incorporation. *
>
>
>  *Furthermore the WG agreed to add in the principles section on
> ‘community’:*
> *Whenever the Board determines that the recommendations of the GNSO do
> not, in its view, reflect a broader consensus including the advice of the
> Advisory Committees and public comments, it will use existing process
> mechanisms to either send the issue back to the GNSO for further
> consideration to initiate broader community discussion.  All final
> recommendations would still be the responsibility of the GNSO.  *
>
>  If you have any comments or concerns about this proposed language,
> please share those with the mailing list.
>
>  The next meeting has been scheduled for *Wednesday 15 April at 19.00 UTC
> for 90 minutes*.
>
>  Best regards,
>
>  Marika
>
>  *Notes 8/4:*
>
>  Public comment 4.18: language proposed by Avri to address comment
> submitted. Update principle with 'in particular' (prior to the global
> public interest). All agreed to add principle to Final Report.
>
>  Recommendation related to community - no objections to including it in
> the Final Report. Update Communities to Committees. Change 'based on' to
> 'including' and 'or' to 'and'. Change ''in their view' to 'its view'.
> Change 'or' to 'to' in second sentence. Change 'discover' to 'determines'.
> Where to include it in the report?
>
>  Include in community section of report (section 4c(2).
>
>  Action item: share updated language as agreed by those on the call with
> the list and encourage those not on the call to speak up if they disagree.
>
>  5.3
> The GIP Team is encouraged...", etc.  Add a sentence after that sentence
> (and in the same place in each of the three processes such as "In this
> regard, it is recommended that the GIP Team Leader or Chair consult with
> the GNSO Council GAC Liaison regarding the best way to achieve early GAC
> participation or consultation with respect to the issues under
> consideration."
>


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

Privacy Policy | Terms of Service | Cookies Policy