ICANN/GNSO GNSO Email List Archives

[ispcp]


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

RE: [ispcp] Re: [ispcp] FW: [council] Current draft of Fadi's requested communication from council

  • To: <Wolf-Ulrich.Knoben@xxxxxxxxxxx>, "'Novoa, Osvaldo'" <onovoa@xxxxxxxxxxxx>, <ispcp@xxxxxxxxx>
  • Subject: RE: [ispcp] Re: [ispcp] FW: [council] Current draft of Fadi's requested communication from council
  • From: "tony holmes" <tonyarholmes@xxxxxxxxxxxxxx>
  • Date: Thu, 14 Feb 2013 16:03:42 -0000
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=s1024; t=1360857823; bh=IbPga9REKbw2d2Z1Z3KbiqubGtaRr8gdtMmJUyRpRzw=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language; b=Ceh4O3SiQtXvxh8vvqNuVi0y9wBfudeRATF6LW4NEAvBtkaavC5H7DXeL+kjUczs/4Z1p1xkHtdMhcXPaNjAE/3kHZkNXgdnMd7iFAmNTv+XUGb8+FqGXAVHfG0WXgZZALi6grobwZm1p397F4ykD7aOQq9Y44SQxuiIAcOp0AQ=
  • In-reply-to: <1U5yzt-1ri0wa0@fwd52.aul.t-online.de>
  • List-id: ispcp@xxxxxxxxxxxxxx
  • References: <1U5xdN-1VIWoa0@fwd07.aul.t-online.de> <5AD57EB74F850E4C9681A52E3C21FDA76EC11167@E2k7-Mbx3.net.in.iantel.com.uy> <1U5yzt-1ri0wa0@fwd52.aul.t-online.de>
  • Sender: owner-ispcp@xxxxxxxxxxxxxx
  • Thread-index: AQEdnOx8iaJAw4EBBAu4fI5KAK5gRQKmQBM4AfCUD5yZtajBAA==

I agree with Wolf-Ulrich. I hope some form of compromise is possible here. 
It's worth remembering that the ISPs did not agree all items fell in to the
'policy' bucket.
Tony
-----Original Message-----
From: owner-ispcp@xxxxxxxxxxxxxx [mailto:owner-ispcp@xxxxxxxxxxxxxx] On
Behalf Of Wolf-Ulrich.Knoben@xxxxxxxxxxx
Sent: 14 February 2013 13:37
To: Novoa, Osvaldo; ispcp@xxxxxxxxx
Subject: [ispcp] Re: [ispcp] FW: [council] Current draft of Fadi's requested
communication from council


It's my preference, too. But let's wait for the compromise intended.

Wolf-Ulrich


-----Original Message-----
Date: Thu, 14 Feb 2013 13:22:28 +0100
Subject: RE: [ispcp] FW: [council] Current draft of Fadi's requested
communication from council
From: "Novoa, Osvaldo" <onovoa@xxxxxxxxxxxx>
To: "'Wolf-Ulrich.Knoben@xxxxxxxxxxx'" <Wolf-Ulrich.Knoben@xxxxxxxxxxx>,
"ispcp@xxxxxxxxx" <ispcp@xxxxxxxxx>


I, personally, support sending this letter as written.
Best regards,
Osvaldo

-----Mensaje original-----
De: owner-ispcp@xxxxxxxxxxxxxx [mailto:owner-ispcp@xxxxxxxxxxxxxx] En nombre
de Wolf-Ulrich.Knoben@xxxxxxxxxxx Enviado el: Jueves, 14 de Febrero de 2013
10:10
Para: ispcp@xxxxxxxxx
Asunto: [ispcp] FW: [council] Current draft of Fadi's requested
communication from council

I'd like to put a short discussion about the letter annexed to the agenda
today.

Clearly BC and IPC are against sending this letter. There shall be a last
try to find a conclusion about. Fadi's deadline is end of Feb.

We should settle our position.

Regards

Wolf-Ulrich

-----Original Message-----
Date: Wed, 13 Feb 2013 00:00:47 +0100
Subject: [council] Current draft of Fadi's requested communication from
council
From: Mason Cole <mcole@xxxxxxxxxx>
To: "council@xxxxxxxxxxxxxx List" <council@xxxxxxxxxxxxxx>

Council colleagues --

As you know, Fadi requested of the council its input regarding the strawman
proposal resulting from the BC's and IPC's request for additional RPMs in
new gTLDs.  On December 27, I circulated an early draft of a council reply.

The communication is due very shortly, and has been taken up by a small
group within the council to ensure that all points of view are represented.
Because this is an agenda item for our meeting this week, at Maria Farrell's
helpful suggestion, I'm sending the current draft to council so we can be
prepared to discuss it then.  This draft does not reflect additional input
of the BC and IPC -- if this is provided prior to the meeting, I'll be happy
to forward it to the council.

Thanks --

Mason



El presente correo y cualquier posible archivo adjunto está dirigido
únicamente al destinatario del mensaje y contiene información que puede ser
confidencial. Si Ud. no es el destinatario correcto por favor notifique al
remitente respondiendo anexando este mensaje y elimine inmediatamente el
e-mail y los posibles archivos adjuntos al mismo de su sistema. Está
prohibida cualquier utilización, difusión o copia de este e-mail por
cualquier persona o entidad que no sean las específicas destinatarias del
mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier
comunicación que haya sido emitida incumpliendo nuestra Política de
Seguridad de la Información


This e-mail and any attachment is confidential and is intended solely for
the addressee(s). If you are not intended recipient please inform the sender
immediately, answering this e-mail and delete it as well as the attached
files. Any use, circulation or copy of this e-mail by any person or entity
that is not the specific addressee(s) is prohibited.
ANTEL is not responsible for any communication emitted without respecting
our Information Security Policy.








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