Re: [bess] Slots requests for BESS WG session - IETF 101 - London

"Ali Sajassi (sajassi)" <> Tue, 27 February 2018 01:23 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CAA4B12DA29 for <>; Mon, 26 Feb 2018 17:23:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Status: No, score=-14.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id CrMLi4oiY1aF for <>; Mon, 26 Feb 2018 17:23:41 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AE8E512DA2B for <>; Mon, 26 Feb 2018 17:23:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=15954; q=dns/txt; s=iport; t=1519694621; x=1520904221; h=from:to:subject:date:message-id:mime-version; bh=vr4IqYhBKKrwSCt/MC5olxuPknMI58Zj2A3jDyiFAmw=; b=Z1FAZjqPcUBCdF3vMFTMQAlKyncDf7yD3wVsLt9ArlJwxzJzqOVkmzpv WMbzrEG9BvnjWYz2O0i/OdtvbzTanoyH9pSwDambg0EhXRbN5ye4cY0Y9 TjvQ4MORZTNnmLWgCUPWPfdy+Fs+XSpYcUohd0zI7y8VAiXV6n2dEHVx5 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos; i="5.47,398,1515456000"; d="scan'208,217"; a="75956965"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Feb 2018 01:23:40 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id w1R1Ne55008914 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 27 Feb 2018 01:23:40 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 26 Feb 2018 20:23:39 -0500
Received: from ([]) by ([]) with mapi id 15.00.1320.000; Mon, 26 Feb 2018 20:23:39 -0500
From: "Ali Sajassi (sajassi)" <>
To: "" <>, "" <>
Thread-Topic: [bess] Slots requests for BESS WG session - IETF 101 - London
Thread-Index: AQHTr2mYAmqLgRGgx0WXpol4lDcBLA==
Date: Tue, 27 Feb 2018 01:23:39 +0000
Message-ID: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/10.a.0.180210
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_DAB1D6F2B4284B17AB661E17E58E6F26ciscocom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [bess] Slots requests for BESS WG session - IETF 101 - London
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 27 Feb 2018 01:23:44 -0000

Hi Stephane,

I’d like to request a 20 min slot to go over the status of the following drafts and request for WG LC/WG call:


From: BESS <> on behalf of "" <>
Date: Thursday, February 22, 2018 at 6:43 AM
To: "" <>
Subject: [bess] Slots requests for BESS WG session - IETF 101 - London


it is time we start building the BESS WG agenda for London.

The IETF agenda (still preliminary) is available at:

The BESS WG session (2h30) is scheduled on Tuesday, March 20th, 2018 / Afternoon session II / 15:50-18:20 (local time)

Please send us your request for a presentation slot, indicating draft name, speaker, and desired duration (covering presentation and discussion).

Thank you

Stephane & Matthew


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.