Applicability Statement for IETF Core Email Protocols
draft-ietf-emailcore-as-00
EMAILCORE J. Klensin, Ed.
Internet-Draft October 6, 2020
Intended status: Standards Track
Expires: April 9, 2021
Applicability Statement for IETF Core Email Protocols
draft-ietf-emailcore-as-00
Abstract
Electronic mail is one of the oldest Internet applications that is
still in very active use. While the basic protocols and formats for
mail transport and message formats have evolved slowly over the
years, events and thinking in more recent years have supplemented
those core protocols with additional features and suggestions for
their use. This Applicability Statement describes the relationship
among many of those protocols and provides guidance and makes
recommendations for the use of features of the core protocols.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 9, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Klensin Expires April 9, 2021 [Page 1]
Internet-Draft Core Email A/S October 2020
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Applicability of Some SMTP Provisions . . . . . . . . . . . . 3
3. Applicability of Message Format Provisions . . . . . . . . . 3
4. MIME and Its Implications . . . . . . . . . . . . . . . . . . 3
5. Other Stuff . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
8. Security Considerations . . . . . . . . . . . . . . . . . . . 4
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
9.1. Normative References . . . . . . . . . . . . . . . . . . 4
9.2. Informative References . . . . . . . . . . . . . . . . . 5
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 6
A.1. Changes from draft-klensin-email-core-as-00 (2020-03-30)
to draft-ietf-emailcore-as-00 . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
In its current form, this draft is a placeholder and beginning of an
outline for the Applicability Statement that has been discussed as a
complement for proposed revisions of the base protocol specifications
for SMTP [RFC5321] (being revised as ID.RFC5321bis [ID.RFC5321bis])
and Internet Message Format [RFC5322] (being revised as ID.RFC5322bis
[ID.RFC5322bis]). Among other things, it is expected to capture
topics that a potential WG concludes are important but that should
not become part of those core documents.
As discussed in RFC 2026 [RFC2026],
"An Applicability Statement specifies how, and under what
circumstances, one or more TSs may be applied to support a
particular Internet capability."
That form of a standards track document is appropriate because one of
the roles of such a document is to explain the relationship among
technical specification, describe how they are used together, and
make statements about what is "required, recommended, or elective".
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119] and
RFC 8174 [RFC8174].
Klensin Expires April 9, 2021 [Page 2]
Show full document text