[bess] Setting up a regular WG document status update

<stephane.litkowski@orange.com> Thu, 15 November 2018 09:26 UTC

Return-Path: <stephane.litkowski@orange.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id A62C3129C6A for <bess@ietfa.amsl.com>; Thu, 15 Nov 2018 01:26:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id CxU9rwr1IJ87 for <bess@ietfa.amsl.com>; Thu, 15 Nov 2018 01:26:09 -0800 (PST)
Received: from orange.com (mta241.mail.business.static.orange.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 821A0126BED for <bess@ietf.org>; Thu, 15 Nov 2018 01:26:09 -0800 (PST)
Received: from opfedar07.francetelecom.fr (unknown [xx.xx.xx.9]) by opfedar23.francetelecom.fr (ESMTP service) with ESMTP id 42wbZl6wG6zBsCT for <bess@ietf.org>; Thu, 15 Nov 2018 10:26:07 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.32]) by opfedar07.francetelecom.fr (ESMTP service) with ESMTP id 42wbZl66qdz5vNC for <bess@ietf.org>; Thu, 15 Nov 2018 10:26:07 +0100 (CET)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM32.corporate.adroot.infra.ftgroup ([fe80::8924:188:2124:a046%19]) with mapi id 14.03.0415.000; Thu, 15 Nov 2018 10:26:07 +0100
From: <stephane.litkowski@orange.com>
To: "bess@ietf.org" <bess@ietf.org>
Thread-Topic: Setting up a regular WG document status update
Thread-Index: AdR8w1HMt8lwJxNbTvmF+u9WzyIFHQ==
Date: Thu, 15 Nov 2018 09:26:07 +0000
Message-ID: <27850_1542273967_5BED3BAF_27850_357_1_9E32478DFA9976438E7A22F69B08FF924B74AF6E@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_9E32478DFA9976438E7A22F69B08FF924B74AF6EOPEXCLILMA4corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/X588Pj7K4i4kxFkmGdDC8Fl3s6U>
Subject: [bess] Setting up a regular WG document status update
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2018 09:26:12 -0000

Hi WG,

In order to help the WG documents progressing faster in the WG, we have decided to request bi-monthly status update from editors of a WG document.
We would like to get these status report before each IETF but also in between two IETF meetings.

The status report should be sent at the following time:

*         November: 2 weeks before the IETF meeting

*         Mid-January

*         March: 2 weeks before the IETF meeting

*         Mid-May

*         July: 2 weeks before the IETF meeting

*         Mid-September

We do not expect a very long text. Just few lines telling:

*         What is the current status

*         What are the next steps and associated ETAs

*         Is there a blocking point worth mentioning

Our goal is really to help document progressing faster and encouraging work in between IETF meetings.


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.