Re: IETF 78 Annoucement

From: Harald Alvestrand <harald at alvestrand.no>
To: Iljitsch van Beijnum <iljitsch at muada.com>
Cc: "David A. Bryan" <dbryan at ethernot.org>, Ole Jacobsen <ole at cisco.com>, IETF Discussion <ietf at ietf.org>
Date: Mon, 25 May 2009 16:15:15 +0200
In-reply-to: <496540A6-FFCB-47CC-9DE6-6137A0F7D394 at muada.com>
References: <56893382-1EE0-4FCF-8B2D-840570321110 at isoc.org> <8F0735D5-9D24-4891-B9D0-2886D3B8DB46 at muada.com> <497FC9FDFB832567A27E2EDD at 192.168.1.110> <4A19950E.8080707 at dcrocker.net> <FCC80B9A78AC0A9046F7953D at 192.168.1.110> <Pine.GSO.4.63.0905241235500.12220 at pita.cisco.com> <8b2769930905241516y1122cce3gfb6b3a6d74aa6546 at mail.gmail.com> <Pine.GSO.4.63.0905241534040.12220 at pita.cisco.com> <5E9E5488-8946-49A4-AC01-5BDD31F60613 at cisco.com> <496540A6-FFCB-47CC-9DE6-6137A0F7D394 at muada.com>

Iljitsch van Beijnum wrote:

And as I said before, I would be very interested to learn whetherdoing this in june rather than july would have made a differentlocation in the Netherlands a more viable option.

ICANN's holding its Latin America meeting June 20-25. Guess why theychose those dates?

Follow-Ups:
- Re: IETF 78 Annoucement
  - From: Iljitsch van Beijnum

References:
- IETF 78 Annoucement
  - From: Ray Pelletier
- Re: IETF 78 Annoucement
  - From: Iljitsch van Beijnum
- Re: IETF 78 Annoucement
  - From: Dave CROCKER
- Re: IETF 78 Annoucement
  - From: Ole Jacobsen
- Re: IETF 78 Annoucement
  - From: David A. Bryan
- Re: IETF 78 Annoucement
  - From: Ole Jacobsen
- Re: IETF 78 Annoucement
  - From: Fred Baker
- Re: IETF 78 Annoucement
  - From: Iljitsch van Beijnum

Prev by Date: tsv-dir review of draft-ietf-sip-outbound-17
Next by Date: Re: IETF 78 Annoucement
Previous by thread: Re: IETF 78 Annoucement
Next by thread: Re: IETF 78 Annoucement
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Re: IETF 78 Annoucement

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.