Re: [89all] [89attendees] Welcome to IETF-89

<> Wed, 26 February 2014 09:28 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 443461A0190; Wed, 26 Feb 2014 01:28:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.898
X-Spam-Status: No, score=-3.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vM-5N_tBwbWb; Wed, 26 Feb 2014 01:28:10 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id F205F1A018D; Wed, 26 Feb 2014 01:28:09 -0800 (PST)
Received: from (unknown [xx.xx.xx.2]) by (ESMTP service) with ESMTP id 4A03A32444E; Wed, 26 Feb 2014 10:28:08 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown []) by (ESMTP service) with ESMTP id 2467327C0B7; Wed, 26 Feb 2014 10:28:08 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([]) by OPEXCLILH03.corporate.adroot.infra.ftgroup ([]) with mapi id 14.03.0174.001; Wed, 26 Feb 2014 10:28:07 +0100
From: <>
To: "" <>
Thread-Topic: [89attendees] [89all] Welcome to IETF-89
Thread-Index: AQHPMh1K0xp3nLY8s0uFLxXZIi9CyZrHBJoAgAACHoCAAD6xQA==
Date: Wed, 26 Feb 2014 09:28:07 +0000
Message-ID: <23035_1393406888_530DB3A8_23035_4284_1_E7E18C472D67E84580701DBFDED9240F4F74B287@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-US, fr-FR
Content-Language: en-US
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/related; boundary="_004_E7E18C472D67E84580701DBFDED9240F4F74B287OPEXCLILM23corp_"; type="multipart/alternative"
MIME-Version: 1.0
X-PMX-Version:, Antispam-Engine:, Antispam-Data: 2014.2.25.93015
X-Mailman-Approved-At: Wed, 26 Feb 2014 08:07:06 -0800
Cc: "" <>, " Discussion" <>, "" <>
Subject: Re: [89all] [89attendees] Welcome to IETF-89
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list of all IETF 89 attendees." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 26 Feb 2014 09:28:15 -0000

Hi Guys
I am registered to attend the event remotely , I wonder how this is coordinated and is there any live sessions through web collaborations or conferencing ?

Thanks and Best Regards

Abdelmoniem Rezk ,M.Sc.,MIET,MIEEE

From: 89attendees [] On Behalf Of Nabil Benamar
Sent: 26 February 2014 06:42
Cc:; Discussion;
Subject: Re: [89attendees] [89all] Welcome to IETF-89

So, lot of thanks to ICANN for hosting this meeting !

Best wishes
نبيل بنعمرو
Nabil Benamar
Moulay Ismail University.
Meknes. Morocco<>

On Wed, Feb 26, 2014 at 6:34 AM, Nabil Benamar <<>> wrote:
Dear Jari,

Thank you for the nice words and invitation...I have particularly appreciated this comment in your message:" ICANN is a consumer of the technology that we produce at the IETF..." .Well said :)

Best wishes
نبيل بنعمرو
Nabil Benamar
Moulay Ismail University.
Meknes. Morocco<>

On Tue, Feb 25, 2014 at 11:32 AM, IETF Chair <<>> wrote:
I would like to welcome you all to our meeting in London next week. Here are some thoughts for the week from my perspective:

Jari Arkko, IETF Chair

89all mailing list<>


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.