Security Considerations Issues for RFC 2821bis
draft-klensin-rfc2821-security-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. John C. Klensin | ||
| Last updated | 2005-07-12 | ||
| 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
RFC 3552 is a useful analysis and presentation of recommendations for Security Considerations Sections. Part of its content is an extensive analysis of, and proposed replacement for, the Security Considerations section of RFC 2821. In important respects, the proposed replacement text may not be appropriate for this type of document. It also raises some specific issues that may not be consistent with the consensus community of email experts about best practice. Given the way it is worded, and the fact that it was published as a BCP document, it is plausible to consider it as an Update to RFC 2821 and to consider its "example" to be normative for any future revision of RFC 2821 such as the work that has been started in [7]. Those perceptions should be definitively evaluated and corrected if necessary. This document is a first step in doing so and also makes some specific additional suggestions about the handling of Security Considerations material.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)