< draft-ietf-emailcore-as-00.txt		draft-ietf-emailcore-as-01.txt >
	EMAILCORE J. Klensin, Ed.		EMAILCORE J. Klensin, Ed.
	Internet-Draft October 6, 2020		Internet-Draft
	Intended status: Standards Track		Intended status: Standards Track K. Murchison
	Expires: April 9, 2021		Expires: October 11, 2021 Fastmail
			E. Sam
			April 9, 2021
	Applicability Statement for IETF Core Email Protocols		Applicability Statement for IETF Core Email Protocols
	draft-ietf-emailcore-as-00		draft-ietf-emailcore-as-01
	Abstract		Abstract
	Electronic mail is one of the oldest Internet applications that is		Electronic mail is one of the oldest Internet applications that is
	still in very active use. While the basic protocols and formats for		still in very active use. While the basic protocols and formats for
	mail transport and message formats have evolved slowly over the		mail transport and message formats have evolved slowly over the
	years, events and thinking in more recent years have supplemented		years, events and thinking in more recent years have supplemented
	those core protocols with additional features and suggestions for		those core protocols with additional features and suggestions for
	their use. This Applicability Statement describes the relationship		their use. This Applicability Statement describes the relationship
	among many of those protocols and provides guidance and makes		among many of those protocols and provides guidance and makes
	recommendations for the use of features of the core protocols.		recommendations for the use of features of the core protocols.
			Note on draft-ietf-emailcore-as-01
			This version is provided as a document management convenience to
			update the author list and make an un-expired version available to
			the WG. There are no substantive changes from the prior version.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on April 9, 2021.		This Internet-Draft will expire on October 11, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2021 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Applicability of Some SMTP Provisions . . . . . . . . . . . . 3		2. Applicability of Some SMTP Provisions . . . . . . . . . . . . 3
	3. Applicability of Message Format Provisions . . . . . . . . . 3		3. Applicability of Message Format Provisions . . . . . . . . . 3
	4. MIME and Its Implications . . . . . . . . . . . . . . . . . . 3		4. MIME and Its Implications . . . . . . . . . . . . . . . . . . 4
	5. Other Stuff . . . . . . . . . . . . . . . . . . . . . . . . . 4		5. Other Stuff . . . . . . . . . . . . . . . . . . . . . . . . . 4
	6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4		6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 4		8. Security Considerations . . . . . . . . . . . . . . . . . . . 4
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 4		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
	9.1. Normative References . . . . . . . . . . . . . . . . . . 4		9.1. Normative References . . . . . . . . . . . . . . . . . . 5
	9.2. Informative References . . . . . . . . . . . . . . . . . 5		9.2. Informative References . . . . . . . . . . . . . . . . . 5
	Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 6		Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 6
	A.1. Changes from draft-klensin-email-core-as-00 (2020-03-30)		A.1. Changes from draft-klensin-email-core-as-00 (2020-03-30)
	to draft-ietf-emailcore-as-00 . . . . . . . . . . . . 6		to draft-ietf-emailcore-as-00 . . . . . . . . . . . . 6
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6		A.2. Changes from draft-ietf-emailcore-as-00 (2020-10-06) to
			-01 . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
	1. Introduction		1. Introduction
	In its current form, this draft is a placeholder and beginning of an		In its current form, this draft is a placeholder and beginning of an
	outline for the Applicability Statement that has been discussed as a		outline for the Applicability Statement that has been discussed as a
	complement for proposed revisions of the base protocol specifications		complement for proposed revisions of the base protocol specifications
	for SMTP [RFC5321] (being revised as ID.RFC5321bis [ID.RFC5321bis])		for SMTP [RFC5321] (being revised as ID.RFC5321bis [ID.RFC5321bis])
	and Internet Message Format [RFC5322] (being revised as ID.RFC5322bis		and Internet Message Format [RFC5322] (being revised as ID.RFC5322bis
	[ID.RFC5322bis]). Among other things, it is expected to capture		[ID.RFC5322bis]). Among other things, it is expected to capture
	topics that a potential WG concludes are important but that should		topics that a potential WG concludes are important but that should
	skipping to change at page 5, line 12 ¶		skipping to change at page 5, line 30 ¶
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<https://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC		[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
	2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,		2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	9.2. Informative References		9.2. Informative References
	[ID.RFC5321bis]		[ID.RFC5321bis]
	Klensin, J., "Simple Mail Transfer Protocol", December		Klensin, J., "Simple Mail Transfer Protocol", Feburary
	2019, <https://datatracker.ietf.org/doc/draft-klensin-		2021, <https://datatracker.ietf.org/doc/draft-klensin-
	rfc5321bis/>.		rfc5321bis/>.
	[ID.RFC5322bis]		[ID.RFC5322bis]
	Resnick, P., "Internet Message Format", December 2019,		Resnick, P., "Internet Message Format", March 2021,
	<https://datatracker.ietf.org/doc/draft-resnick-		<https://datatracker.ietf.org/doc/draft-resnick-
	rfc5322bis/>.		rfc5322bis/>.
	[RFC0822] Crocker, D., "STANDARD FOR THE FORMAT OF ARPA INTERNET		[RFC0822] Crocker, D., "STANDARD FOR THE FORMAT OF ARPA INTERNET
	TEXT MESSAGES", STD 11, RFC 822, DOI 10.17487/RFC0822,		TEXT MESSAGES", STD 11, RFC 822, DOI 10.17487/RFC0822,
	August 1982, <https://www.rfc-editor.org/info/rfc822>.		August 1982, <https://www.rfc-editor.org/info/rfc822>.
	[RFC1341] Borenstein, N. and N. Freed, "MIME (Multipurpose Internet		[RFC1341] Borenstein, N. and N. Freed, "MIME (Multipurpose Internet
	Mail Extensions): Mechanisms for Specifying and Describing		Mail Extensions): Mechanisms for Specifying and Describing
	the Format of Internet Message Bodies", RFC 1341,		the Format of Internet Message Bodies", RFC 1341,
	skipping to change at page 6, line 15 ¶		skipping to change at page 6, line 31 ¶
	Appendix A. Change Log		Appendix A. Change Log
	RFC Editor: Please remove this appendix before publication.		RFC Editor: Please remove this appendix before publication.
	A.1. Changes from draft-klensin-email-core-as-00 (2020-03-30) to draft-		A.1. Changes from draft-klensin-email-core-as-00 (2020-03-30) to draft-
	ietf-emailcore-as-00		ietf-emailcore-as-00
	o Change of filename, metadata, and date to reflect transition to WG		o Change of filename, metadata, and date to reflect transition to WG
	document for new emailcore WG. No other substantive changes		document for new emailcore WG. No other substantive changes
	Author's Address		A.2. Changes from draft-ietf-emailcore-as-00 (2020-10-06) to -01
			o Added co-authors (list is in alphabetical order for the present).
			o Updated references to 5321bis and 5322bis.
			o Added note at top, "This version is provided as a document
			management convenience to update the author list and make an un-
			expired version available to the WG. There are no substantive
			changes from the prior version", which should be removed for
			version -02.
			Authors' Addresses
	John C Klensin (editor)		John C Klensin (editor)
	1770 Massachusetts Ave, Ste 322		1770 Massachusetts Ave, Ste 322
	Cambridge, MA 02140		Cambridge, MA 02140
	USA		USA
	Phone: +1 617 245 1457		Phone: +1 617 245 1457
	Email: john-ietf@jck.com		Email: john-ietf@jck.com
			Kenneth Murchison
			Fastmail US LLC
			1429 Walnut Street - Suite 1201
			Philadelphia, PA 19102
			USA
			Email: murch@fastmailteam.com
			E Sam
			Email: winshell64@gmail.com
End of changes. 12 change blocks.
	14 lines changed or deleted		36 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/