ICANN/GNSO GNSO Email List Archives

[ispcp]


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

Re: [ispcp] [ispcp] ISPCP call

  • To: "Wolf-Ulrich.Knoben@xxxxxxxxxxx" <Wolf-Ulrich.Knoben@xxxxxxxxxxx>
  • Subject: Re: [ispcp] [ispcp] ISPCP call
  • From: tony holmes <tonyarholmes@xxxxxxxxxxxxxx>
  • Date: Wed, 13 Feb 2013 15:24:55 +0000
  • Cc: "Novoa, Osvaldo" <onovoa@xxxxxxxxxxxx>, "Mike O'Connor" <mike@xxxxxxxxxx>, "wuknoben@xxxxxxxxx" <wuknoben@xxxxxxxxx>, "ispcp@xxxxxxxxx" <ispcp@xxxxxxxxx>
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=s1024; t=1360769126; bh=51QjXprhCtLIBNE0HS4Q+o9vLbvB++52yRulKphikgg=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:References:In-Reply-To:Mime-Version:Content-Transfer-Encoding:Content-Type:Message-Id:Cc:X-Mailer:From:Subject:Date:To; b=g3Cg4n0KmvqjjZGpHFhDbvoJ8E/o58flplFNcFQlle265Ju+9f/9IQLf75gVeGViV2eg/G6db8VOzGthhR1Kr6lC0mauBngKJov5PzDEUBpayPj3rjvUds5nKn0+8p9ZuQ+WkJ9jiSHvGiSNbsxEJ6Srj6/hJS8Ko5J4N/Gy4IE=
  • In-reply-to: <1U5dlR-1cX1aC0@fwd11.aul.t-online.de>
  • List-id: ispcp@xxxxxxxxxxxxxx
  • References: <1U4rJD-1MFq5o0@fwd14.aul.t-online.de> <000601ce0855$bcf10ec0$36d32c40$@btinternet.com> <1U4t7h-0uG9OC0@fwd14.aul.t-online.de> <88DC776C-3B7D-42E3-89AD-239B5EDB1964@haven2.com> <002101ce085e$9e582d50$db0887f0$@btinternet.com> <24F42B23-5EBB-4B29-B461-0A818740EF71@haven2.com> <003201ce0860$258f1620$70ad4260$@btinternet.com> <2536694D-E6D0-48F6-B112-C7126F4A43D2@antel.com.uy> <1U5dlR-1cX1aC0@fwd11.aul.t-online.de>
  • Sender: owner-ispcp@xxxxxxxxxxxxxx

Yes the call is 16.30 tomorrow
Tony

Sent from my iPhone


On 13 Feb 2013, at 14:56, "Wolf-Ulrich.Knoben@xxxxxxxxxxx" <Wolf-Ulrich.Knoben@xxxxxxxxxxx> wrote:

> Do we stay with the call tomorrow at 16:30 UTC? I didn't yet see the
> details. I'd have to reschedule other potential appointments in case.
> Please advise.
> 
> Wolf-Ulrich
> 
> 
> -----Original Message-----
> Date: Mon, 11 Feb 2013 16:19:54 +0100
> Subject: Re: [ispcp] [ispcp] ISPCP call
> From: "Novoa, Osvaldo" <onovoa@xxxxxxxxxxxx>
> To: tony holmes <tonyarholmes@xxxxxxxxxxxxxx>
> 
> Thurday is fine for me
> 
> El 11/02/2013, a las 12:29, "tony holmes"
> <tonyarholmes@xxxxxxxxxxxxxx<mailto:tonyarholmes@xxxxxxxxxxxxxx>>
> escribi??:
> 
> 
> 
> Sure, will do.
> Tony
> 
> -----Original Message-----
> From: Mike O'Connor [mailto:mike@xxxxxxxxxx]
> Sent: 11 February 2013 13:54
> To: tony holmes
> Cc: Mike O'Connor;
> Wolf-Ulrich.Knoben@xxxxxxxxxxx<mailto:Wolf-Ulrich.Knoben@xxxxxxxxxxx>;
> wuknoben@xxxxxxxxx<mailto:wuknoben@xxxxxxxxx>;
> ispcp@xxxxxxxxx<mailto:ispcp@xxxxxxxxx>
> Subject: Re: [ispcp] [ispcp] ISPCP call
> 
> the Thursday time is fine with me.  can you ping Gisella so she has the
> call
> on her announcement schedule?
> 
> Wolf-Urich, are you getting these posts via the list?  i copied your
> Gmail
> account on this message to make sure you got it.
> 
> m
> 
> On Feb 11, 2013, at 7:49 AM, "tony holmes"
> <tonyarholmes@xxxxxxxxxxxxxx<mailto:tonyarholmes@xxxxxxxxxxxxxx>>
> wrote:
> 
>> I was sure the details had been circulated but with everything else
> going
> on
>> I may be wrong. Apologies, particularly as this was the date we agreed
> in
>> LA. Its best think we postpone  and reschedule.
>> 
>> How does Thursday 14th Feb at 16.30 UTC work?
>> 
>> This also means we need to fix the provisional agenda for our ISPCP
> meeting
>> in Beijing via email. I'll circulate a proposal later.
>> 
>> Regards
>> tony
>> 
>> -----Original Message-----
>> From: owner-ispcp@xxxxxxxxxxxxxx<mailto:owner-ispcp@xxxxxxxxxxxxxx>
> [mailto:owner-ispcp@xxxxxxxxxxxxxx] On
>> Behalf Of Mike O'Connor
>> Sent: 11 February 2013 13:32
>> To:
> Wolf-Ulrich.Knoben@xxxxxxxxxxx<mailto:Wolf-Ulrich.Knoben@xxxxxxxxxxx>
>> Cc: tony holmes; ispcp@xxxxxxxxx<mailto:ispcp@xxxxxxxxx>
>> Subject: Re: [ispcp] [ispcp] ISPCP call
>> 
>> hi Wolf-Urich,
>> 
>> looking back, i don't see a meeting invitation on the ispcp list.  you
> must
>> be subscribed, because i got your messages through the list.  i just
> don't
>> think the meeting announcement ever got sent.
>> 
>> Tony, if you decide to proceed with the call, can you circulate the
> details?
>> i'd push them out to the list myself, but i don't have them.
>> 
>> thanks,
>> 
>> mikey
>> 
>> 
>> On Feb 11, 2013, at 7:08 AM,
> Wolf-Ulrich.Knoben@xxxxxxxxxxx<mailto:Wolf-Ulrich.Knoben@xxxxxxxxxxx>
> wrote:
>> 
>>> 
>>> It matches exactly with the prep call of the GNSO council chairs for
> the
>>> next council meeting. So I have a real problem.
>>> Unfortunately I didn't receive any ISPCP call details  (bridge) etc.
> in
>>> advance. Maybe my email-address is still not on the list.
>>> 
>>> Wolf-Ulrich
>>> 
>>> -----Original Message-----
>>> Date: Mon, 11 Feb 2013 13:45:57 +0100
>>> Subject: RE: [ispcp] ISPCP call
>>> From: "tony holmes"
> <tonyarholmes@xxxxxxxxxxxxxx<mailto:tonyarholmes@xxxxxxxxxxxxxx>>
>>> To:
> <Wolf-Ulrich.Knoben@xxxxxxxxxxx<mailto:Wolf-Ulrich.Knoben@xxxxxxxxxxx>>,
> <ispcp@xxxxxxxxx<mailto:ispcp@xxxxxxxxx>>
>>> 
>>> 
>>> The call is today at 15.00 UTC
>>> Details have been circulated.
>>> Tony
>>> 
>>> -----Original Message-----
>>> From: owner-ispcp@xxxxxxxxxxxxxx<mailto:owner-ispcp@xxxxxxxxxxxxxx>
> [mailto:owner-ispcp@xxxxxxxxxxxxxx] On
>>> Behalf Of
> Wolf-Ulrich.Knoben@xxxxxxxxxxx<mailto:Wolf-Ulrich.Knoben@xxxxxxxxxxx>
>>> Sent: 11 February 2013 11:12
>>> To: ispcp@xxxxxxxxx<mailto:ispcp@xxxxxxxxx>
>>> Subject: [ispcp] ISPCP call
>>> 
>>> 
>>> Guys,
>>> 
>>> do we have an ISP call today, or when is the next call scheduled?
>>> 
>>> Wolf-Ulrich
>> 
>> 
>> PHONE: 651-647-6109, FAX: 866-280-2356, WEB:
> www.haven2.com<http://www.haven2.com>, HANDLE:
>> OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)
> 
> 
> PHONE: 651-647-6109, FAX: 866-280-2356, WEB:
> www.haven2.com<http://www.haven2.com>, HANDLE:
> OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)
> 
> 
> 
> ________________________________
> 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 >>>