[discuss] Opportunity for input on the development process for IANA oversight transition plan
Shatan, Gregory S.
GShatan at ReedSmith.com
Tue Mar 25 08:04:12 UTC 2014
I am also in Singapore and would love to get together. I’m heading back first thing Friday morning.
From: discuss-bounces at 1net.org [mailto:discuss-bounces at 1net.org] On Behalf Of James Seng
Sent: Tuesday, March 25, 2014 4:01 PM
To: George Sadowsky
Cc: discuss at 1net.org List
Subject: Re: [discuss] Opportunity for input on the development process for IANA oversight transition plan
I am in Singapore but heading back to Beijing on Thurs morning.
On Tue, Mar 25, 2014 at 3:55 PM, George Sadowsky <george.sadowsky at gmail.com<mailto:george.sadowsky at gmail.com>> wrote:
Who else on this list is here in Singapore at the ICANN meeting? Would it be worth getting together?
If so, is there any interest in getting together? The schedule here is really full, but I can suggest Friday, at any time. I should be able to get a room for such a meeting.
On Mar 25, 2014, at 3:03 PM, Seun Ojedeji <seun.ojedeji at gmail.com<mailto:seun.ojedeji at gmail.com>> wrote:
sent from Google nexus 4
kindly excuse brevity and typos.
On 25 Mar 2014 14:27, "George Sadowsky" <george.sadowsky at gmail.com<mailto:george.sadowsky at gmail.com>> wrote:
> I am in Singapore and involved in Internet governance discussions resulting from the recent NTIA announcement.
I am too ;)
discuss mailing list
discuss at 1net.org<mailto:discuss at 1net.org>
* * *
This E-mail, along with any attachments, is considered confidential and may well be legally privileged. If you have received it in error, you are on notice of its status. Please notify us immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Thank you for your cooperation.
* * *
To ensure compliance with Treasury Department regulations, we inform you that, unless otherwise indicated in writing, any U.S. Federal tax advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (1) avoiding penalties under the Internal Revenue Code or applicable state and local provisions or (2) promoting, marketing or recommending to another party any tax-related matters addressed herein.
Disclaimer Version RS.US.20.10.00
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the discuss