Appropriate Mailing List Behaviour
draft-palme-maillist-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jacob Palme | ||
| Last updated | 2002-12-02 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This memo summarizes common ideas on how good mailing lists should behave. Some of this is taken from IETF standards, some is not. This memo is not intended, itself, to become a standard, but might, if accepted by the IETF, be published as informational RFC or as a Best Current Practice (BCP) document.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)