ICANN ICANN Email List Archives

[gnso-osc-csg]


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

RE: [gnso-osc-csg] OSC CSG Working Team - Next Steps

  • To: "Olga Cavalli" <olgac@xxxxxxxxxxxxxxx>, "OSC-CSG Work Team" <gnso-osc-csg@xxxxxxxxx>
  • Subject: RE: [gnso-osc-csg] OSC CSG Working Team - Next Steps
  • From: "Papac, Krista" <Krista.Papac@xxxxxxxxxxxxxxxx>
  • Date: Tue, 29 Sep 2009 14:40:00 -0400

Olga and Team,

 

I support sending 1.4 toolkit document, as an independent document, to the OSC 
and to the GNSO Council.  My name is Krista Papac, I am an employee of Iron 
Mountain (an ICANN accredited registrar), and a member of the Registrars 
Stakeholder Group.

 

Best,

Krista Papac

 

**Please note my new Mobile Number 

Krista Papac 
Sales Executive 
Iron Mountain Digital 
5530 Bandini Blvd 
Bell, CA  90201  US 
Home Office: +1.714.846.8780 
Mobile: +1.714.865.7655 
Fax: +1.323.443.3573 
krista.papac@xxxxxxxxxxxxxxxx <mailto:krista.papac@xxxxxxxxxxxxxxxx>  

Order your complimentary copy of Software Escrow for Dummies today at 
ironmountain.com/escrowfordummies <http://ironmountain.com/escrowfordummies>  
<http://digital.ironmountain.com/content/SoftwareEscrowforDummies> 

 

________________________________

From: owner-gnso-osc-csg@xxxxxxxxx [mailto:owner-gnso-osc-csg@xxxxxxxxx] On 
Behalf Of Olga Cavalli
Sent: Tuesday, September 29, 2009 7:42 AM
To: OSC-CSG Work Team
Cc: Glen de Saint Géry; Julie Hedlund; Robert Hoggarth
Subject: [gnso-osc-csg] OSC CSG Working Team - Next Steps

 

Dear Working Team,


I was away for three days and I am really impressed by the level of activity in 
our mailing list.

After reviewing all the comments, I want to summarize what we agreed in our 
last conference call and propose some next steps to follow. 

In relation with the Subworking team´s draft documents:

1.1: SS will send a new draft version by early this week that includes all 
comments recieved by the subworking team. The draft document will be reviewed 
by the whole working team. A reasonable due date for reviewing this draft 
document must be established.

1.2: Victoria will send a new draft version by early this week that includes 
all comments recieved by the subworking team. The draft document will be 
reviewed by the whole working team. A reasonable due date for reviewing this 
draft document must be established.

1.3: Krista and Tony have already submitted their draft document, that contains 
already all comments from the subworking team. This document is ready to be 
reviewed by the whole working team.

1.4: Julie submitted on 9 September a new draft version of 1.4 subtask document 
that included comments made by Claudio and myself. Some workteam members have 
not had the chance to review this document and will do soon, they can also 
submit comments.

Once the 1.4 draft document is reveiwed and agreed by the working team, there 
has been a suggestion of sending it to the OSC as a separate document, before 
the rest of the documents have been reviewed by the whole working team.

The working team did not reach unanimous consensus.

In this sense, and in the light of all the comments exchanged in the call and 
in the email list, I would like to remind what the Working Group Process 
indicates on this regard:

*       The WG shall function on the basis of rough consensus, meaning all 
points of view will be discussed until the chair can ascertain that the point 
of view is understood and has been covered. Consensus views should include the 
names and affiliations of those in agreement with that view. Anyone with a 
minority view will be invited to include a discussion in the WG report. 
Minority report should include the names and affiliations of those contributing 
to the minority report.

(for the whole text of the Working Group Process please refer to: 
https://st.icann.org/gnso-council/index.cgi?working_group_process)

After reviewing all the comments in the mailing list, there seems to be rough 
consensus in sending 1.4 toolkit document, as an independent document, to the 
OSC and to the GNSO Council.

In this sense I encourage those not in favour of sending this 1.4 toolkit 
document, to send their names and affiliations and their views in order to be 
included in a minority report.

Also all those in agreement of sending the 1.4 tool kit document as a separate 
one, please send name an affiliations to be included in the report.

I really appreciate the high involvement of all the working team, and at the 
same time I want to stress the value of constructive work and the need for 
respecting theoppinions and work of other collegues members of the working team 
and staff.

Althoug we all have the right to express ourselves and support our positions, 
flexibility is many times the best way for a constructive work and for a timely 
and good outcome.

I also want to thank again the excellent work done by ICANN Staff involved in 
this working team.

Looking forward to recieveing your comments.

I send you my best regards.

Olga









-- 
Olga Cavalli, Dr. Ing.
www.south-ssig.com.ar



The information contained in this email message and its attachments
is intended
only for the private and confidential use of the recipient(s) named
above, unless the sender expressly agrees otherwise. Transmission
of email over the Internet
 is not a secure communications medium. If you are requesting or
have requested
the transmittal of personal data, as defined in applicable privacy
laws by means
 of email or in an attachment to email you must select a more
secure alternate means of transmittal that supports your
obligations to protect such personal data. If the reader of this
message is not the intended recipient and/or you have received this
email in error, you must take no action based on the information in
this email and you are hereby notified that any dissemination,
misuse, copying, or disclosure of this communication is strictly
prohibited. If you have received
this communication in error, please notify us immediately by email
and delete the original message.


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

Privacy Policy | Terms of Service | Cookies Policy