[L2CP] Guidelines for use of the IETF mailer

"Wojciech Dec \(wdec\)" <wdec@cisco.com> Tue, 23 May 2006 11:02 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FiUf1-0004TL-Ni; Tue, 23 May 2006 07:02:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FiUf0-0004TG-4z for l2cp@ietf.org; Tue, 23 May 2006 07:02:46 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiTxl-0007bg-9o for l2cp@ietf.org; Tue, 23 May 2006 06:18:05 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FiTqh-0005Q4-F1 for l2cp@ietf.org; Tue, 23 May 2006 06:10:51 -0400
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 23 May 2006 12:10:48 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k4NAAjUI027845; Tue, 23 May 2006 12:10:46 +0200 (MEST)
Received: from xmb-ams-33b.cisco.com ([144.254.231.86]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.0); Tue, 23 May 2006 12:10:45 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 23 May 2006 12:10:39 +0200
Message-ID: <D9872168DBD43A41BD71FFC4713274D4020DF1B1@xmb-ams-33b.emea.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Guidelines for use of the IETF mailer
Thread-Index: AcZ+USQvjnQKJKVMRTa5ixtEWQYBMA==
X-Priority: 1
Priority: Urgent
Importance: high
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: l2cp@ietf.org
X-OriginalArrivalTime: 23 May 2006 10:10:45.0998 (UTC) FILETIME=[284948E0:01C67E51]
X-Spam-Score: -2.6 (--)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc:
Subject: [L2CP] Guidelines for use of the IETF mailer
X-BeenThere: l2cp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 2 Control Protocol Discussion List <l2cp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2cp>, <mailto:l2cp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l2cp>
List-Post: <mailto:l2cp@ietf.org>
List-Help: <mailto:l2cp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2cp>, <mailto:l2cp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0588268933=="
Errors-To: l2cp-bounces@ietf.org

Hi All,

In order to resolve an item that has been seemingly causing some
confusion we would like to set the following guidelines regarding the
use of the IETF L2CP/ANCP mailer and any other private discussion list:

- All protocol, protocol field type and value, IETF draft discussions,
proposals, and general protocol use discussions, as well as posts
relating to open to the public interoperability testing, results and
protocol issues are appropriate and encouraged to go on to the IETF
mailing list.
- All discussions regarding customer specific compliance testing and
reports, vendor implementation issues, logistics and planning are
appropriate for going on a private mailing list.

We trust that the above guidelines are clear and simple enough to allow
all participants an easy call regarding the postings.

Regards,
W. Dec


_______________________________________________
L2cp mailing list
L2cp@ietf.org
https://www1.ietf.org/mailman/listinfo/l2cp