AW: [council] Proposed Amendment to RAA Motion

[<KnobenW@xxxxxxxxxx>]

Tim,

Do I understand you going against the - existing - motion whatever amendments 
may be suggested?
Maybe I misinterprete what "unproductive rounds" mean.

Kind regards
Wolf-Ulrich 


-----Ursprüngliche Nachricht-----
Von: owner-council@xxxxxxxxxxxxxx [mailto:owner-council@xxxxxxxxxxxxxx] Im 
Auftrag von Tim Ruiz
Gesendet: Mittwoch, 26. Oktober 2011 16:55
An: Wendy Seltzer
Cc: Council GNSO
Betreff: RE: [council] Proposed Amendment to RAA Motion


Instead of getting into another round of potentally non-productive
dicussions about this motion, given the recent RrSG announcement, can we
simply agree to withdraw it and let us move on and just le us get the
work done? I do not want to see anything potentially derail it at this
point.

Tim  
 
-------- Original Message --------
Subject: [council] Proposed Amendment to RAA Motion
From: Wendy Seltzer <wendy@xxxxxxxxxxx>
Date: Wed, October 26, 2011 9:42 am
To: Council GNSO <council@xxxxxxxxxxxxxx>


Colleagues,

In light of our interest in proceeding quickly to amend the RAA, I
propose an amendment to streamline process B and preserve important
opportunities for transparency and public comment.
Further, as the NCUC does not support many of the identified
"high-priority items," I have removed their endorsement from the
resolveds.

Below I include an updated version of the resolveds my amendment would
create and a redline of the whole against the original motion.

Thanks,
--Wendy

RESOLVED,
that the GNSO Council recommends that Staff adopt an amended version of
the process specified as Process B in the Final Report to develop a new
form of RAA. As amended herein, Process B entails:

1. A 60-day public comment period shall be open from Monday 31
October, to provide members of the ICANN community with the opportunity
to give feedback on the topics described in the Final Report, including
the opportunity to raise considerations and concerns arising since the
Report was issued.

2. ICANN Staff will schedule a public consultation at the ICANN
public meeting in Costa Rica, to provide members of the ICANN community
with the opportunity to give further feedback, including feedback based
on comments received during the public comment period, so as to inform
the negotiations between ICANN staff and the Registrar Stakeholder Group
as a whole (the "Negotiating Group").

3. Within sixty (60) days after the public consultation described
in Step 2, negotiations begin with the Negotiating Group consisting
of ICANN Staff and the Registrar Stakeholder Group (as a whole).

4. The Negotiating Group shall provide, for public comment,
bimonthly written reports on the status and progress of the
negotiations. Such reports shall include proposed text under
consideration and identify items and text agreed upon by the
Negotiating Group. Each bimonthly report shall identify the status of
(a)
topics identified in Step 2 and that were not determined to
require consensus policy development; and (b) proposed amendments put
forth by any Stakeholder Group, Constituency, and/or Advisory Committee;
and shall identify such topics, if any, that have been rejected by
the Negotiating Group (collectively, the "Rejected Topics and
Amendments").

5. The Negotiating Group shall review public comments received and
continue negotiations as necessary. Steps 4 and 5 shall repeat as
necessary; provided, however, that the full final draft of the new
RAA must be posted for public comment not later than March 4,
2013.

6. Subject to the date requirement in Step 5, ICANN Staff and the
Registrar Stakeholder Group shall determine when the full final
draft of the new RAA is ready to be posted for public comment. The
full final draft of the new RAA that is posted for public comment
shall be accompanied by a detailed written explanation, approved
by both Staff and the Registrar Stakeholder Group, that sets forth
the basis for the rejection of all Rejected Topics and Amendments.

7. The GNSO Council shall review the full final draft of the new
RAA, consider public comments, and vote on approval of the draft
new RAA. A Supermajority vote of the GNSO Council is required to
approve the new RAA.

8. If the GNSO Council approves the new RAA, the new RAA goes to
Board for approval.

9. If the GNSO Council does not approve the new RAA, the new RAA
is sent back to the Negotiating Group with appropriate feedback
for reconsideration. Repeat from step 7.

RESOLVED FURTHER, that the GNSO Council recommends that this
process be initiated by ICANN immediately.




REDLINE against the current motion at
<https://community.icann.org/display/gnsocouncilmeetings/Motions+26+October+2011>

>Whereas, on 4 March 2009, the GNSO Council approved the form of the 2009 
>Registrar Accreditation Agreement (RAA) developed as a result of a lengthy 
>consultative process initiated by ICANN;
>>
>Whereas, in addition to approving the 2009 RAA, on 4 March 2009 the GNSO 
>Council convened a joint drafting team with members of the At-Large Community, 
>to conduct further work related to improvements to the RAA; specifically to: 
>(a) draft a charter identifying registrant rights and responsibilities; and 
>(b) develop a specific process to identify additional potential amendments to 
>the RAA on which further action may be desirable;
>>
>Whereas, on 18 October 2010, the Joint GNSO/ALAC RAA Drafting Team published 
>its Final Report describing specific recommendations and proposals to the GNSO 
>Council for improvements to the RAA;
>>
>Whereas, the GNSO Council has reviewed the Final Report and, in its resolution 
>20110113-2, the GNSO Council approved of the Form of Registrant Rights and 
>Responsibilities Charter as described in Annex D of the Final Report and 
>recommended that Staff commence the consultation process with Registrars in 
>the RAA to finalize the Registrant Rights and Responsibilities Charter for 
>posting on the websites of Registrars as specified in Section 3.15 of the RAA;
>>
>Whereas, a GNSO Council motion recommending that Staff adopt the process 
>specified as Process A in the Final Report to develop a new form of RAA with 
>respect to the High and Medium Priority topics described in the Final Report 
>did not pass;
>>
>Whereas, a previous GNSO Council motion to approve an amended version of the 
>process specified as Process B in the Final Report to develop a new form of 
>RAA with respect to the High and Medium Priority topics described in the Final 
>Report did not pass at the GNSO Council's April 7, 2011 meeting;
>>
>Whereas, the GNSO Council desires to approve a further amended version of the 
>process specified as Process B in the Final Report to develop a new form of 
>RAA 
[[REMOVE with respect to the High and Medium Priority topics described
in the Final Report.]]
>>
>NOW THEREFORE, BE IT:
>>
>RESOLVED, that the GNSO Council recommends that Staff adopt an amended version 
>of the process specified as Process B in the Final Report to develop a new 
>form of RAA 
[[REMOVE with respect to the High and Medium Priority topics described
in the Final Report.]]
>As amended herein, Process B entails:

[[REPLACE steps 1 and 2 with
1. A 60-day public comment period shall be open from Monday 31
October, to provide members of the ICANN community with the opportunity
to give feedback on the topics described in the Final Report, including
the opportunity to raise considerations and concerns arising since the
Report was issued.

2. ICANN Staff will schedule a public consultation at the ICANN
public meeting in Costa Rica, to provide members of the ICANN community
with the opportunity to give further feedback, including feedback based
on comments received during the public comment period, so as to inform
the negotiations between ICANN staff and the Registrar Stakeholder Group
as a whole (the "Negotiating Group").
]]

>3. Within sixty (60) days after the public consultation described in Step 2, 
>negotiations begin with the Negotiating Group consisting of ICANN Staff and 
>the Registrar Stakeholder Group (as a whole).
>>
>4. The Negotiating Group shall provide, for public comment, bimonthly written 
>reports on the status and progress of the negotiations. Such reports shall 
>include proposed text under consideration and identify items and text agreed 
>upon by the Negotiating Group. Each bimonthly report shall identify the status 
>of (a) topics identified in 
[[REPLACE with Step 2]
> and that were not determined in Step 1 as requiring consensus policy
> development; and (b) proposed amendments put forth by any Stakeholder
> Group, Constituency, and/or Advisory Committee; and shall identify such
> topics, if any, that have been rejected by the Negotiating Group
> (collectively, the "Rejected Topics and Amendments").
>>
>5. The Negotiating Group shall review public comments received and continue 
>negotiations as necessary. Steps 4 and 5 shall repeat as necessary; provided, 
>however, that the full final draft of the new RAA must be posted for public 
>comment not later than March 4, 2013.
>>
>6. Subject to the date requirement in Step 5, ICANN Staff and the Registrar 
>Stakeholder Group shall determine when the full final draft of the new RAA is 
>ready to be posted for public comment. The full final draft of the new RAA 
>that is posted for public comment shall be accompanied by a detailed written 
>explanation, approved by both Staff and the Registrar Stakeholder Group, that 
>sets forth the basis for the rejection of all Rejected Topics and Amendments.
>>
>7. The GNSO Council shall review the full final draft of the new RAA, consider 
>public comments, and vote on approval of the draft new RAA. A Supermajority 
>vote of the GNSO Council is required to approve the new RAA.
>>
>8. If the GNSO Council approves the new RAA, the new RAA goes to Board for 
>approval.
>>
>9. If the GNSO Council does not approve the new RAA, the new RAA is sent back 
>to the Negotiating Group with appropriate feedback for reconsideration. Repeat 
>from step 7.
>>
>RESOLVED FURTHER, that the GNSO Council recommends that this process be 
>initiated by ICANN immediately.