< draft-ietf-yam-5321bis-smtp-pre-evaluation-03.txt		draft-ietf-yam-5321bis-smtp-pre-evaluation-04.txt >
	YAM Working Group J. Klensin		YAM Working Group J. Klensin
	Internet-Draft		Internet-Draft
	Intended status: Informational B. Leiba		Intended status: Informational B. Leiba
	Expires: August 1, 2010 Huawei Technologies		Expires: October 17, 2010 Huawei Technologies
	January 28, 2010		April 15, 2010
	Preliminary Evaluation of RFC5321, Simple Mail Transfer Protocol (SMTP),		Preliminary Evaluation of RFC5321, Simple Mail Transfer Protocol (SMTP),
	for advancement from Draft Standard to Full Standard by the YAM Working		for advancement from Draft Standard to Full Standard by the YAM Working
	Group		Group
	draft-ietf-yam-5321bis-smtp-pre-evaluation-03.txt		draft-ietf-yam-5321bis-smtp-pre-evaluation-04
	Abstract		Abstract
	This memo is a preliminary evaluation of RFC 5321, Simple Mail		This memo is a preliminary evaluation of RFC 5321, Simple Mail
	Transfer Protocol for advancement from Draft to Full Standard. It		Transfer Protocol for advancement from Draft to Full Standard. It
	has been prepared by the The Yet Another Mail Working Group.		has been prepared by the The Yet Another Mail Working Group.
	THIS INTERNET DRAFT IS NOT MEANT TO BE PUBLISHED AS AN RFC, BUT IS		THIS INTERNET DRAFT IS NOT MEANT TO BE PUBLISHED AS AN RFC, BUT IS
	WRITTEN TO FACILITATE DISCUSSION WITH THE IESG.		WRITTEN TO FACILITATE DISCUSSION WITH THE IESG.
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF 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), its areas, and its working groups. Note that		Task Force (IETF). Note that other groups may also distribute
	other groups may also distribute working documents as Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts.		Drafts is at http://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."
	The list of current Internet-Drafts can be accessed at		This Internet-Draft will expire on October 17, 2010.
	http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on August 1, 2010.
	Copyright Notice		Copyright Notice
	Copyright (c) 2010 IETF Trust and the persons identified as the		Copyright (c) 2010 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
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://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 BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	1.1. Note to RFC Editor . . . . . . . . . . . . . . . . . . . . 3		1.1. Note to RFC Editor . . . . . . . . . . . . . . . . . . . . 3
	2. Preliminary Evaluation . . . . . . . . . . . . . . . . . . . . 3		2. Preliminary Evaluation . . . . . . . . . . . . . . . . . . . . 3
	2.1. Document . . . . . . . . . . . . . . . . . . . . . . . . . 3		2.1. Document . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2.2. Time in Place . . . . . . . . . . . . . . . . . . . . . . . 3		2.2. Time in Place . . . . . . . . . . . . . . . . . . . . . . . 3
	2.3. Implementation and Operational Experience . . . . . . . . . 3		2.3. Implementation and Operational Experience . . . . . . . . . 3
	2.4. Proposed Changes . . . . . . . . . . . . . . . . . . . . . 4		2.4. Proposed Changes . . . . . . . . . . . . . . . . . . . . . 4
	skipping to change at page 6, line 5 ¶		skipping to change at page 6, line 5 ¶
	even to IETF Last Call.		even to IETF Last Call.
	4. As agreed when RFC 5321 was reviewed, the examples will not be		4. As agreed when RFC 5321 was reviewed, the examples will not be
	revised to bring them into alignment with RFC 2606 (BCP 32)		revised to bring them into alignment with RFC 2606 (BCP 32)
	conventions (example.com, etc.). The issues are explained in		conventions (example.com, etc.). The issues are explained in
	Section 1.3 of RFC 5321. The community also noted at the time		Section 1.3 of RFC 5321. The community also noted at the time
	that the relevant examples have been in use, substantially		that the relevant examples have been in use, substantially
	unchanged, for more than a quarter-century with no serious claims		unchanged, for more than a quarter-century with no serious claims
	of confusion or other harm being caused.		of confusion or other harm being caused.
	5. The Security Considerations section was extensively reviewed last		5. The Security Considerations section was extensively reviewed in
	year (during the review and approval of RFC 5321). No evidence		2008 (during the review and approval of RFC 5321). No evidence
	has appeared since then that would require further review or		has appeared since then that would require further review or
	additional changes.		additional changes.
	2.6. Downward references		2.6. Downward references
	At Full Standard, the following references would be downward		At Full Standard, the following references would be downward
	references:		references:
	RFC 5322 if 5322bis is not progressed simultaneously with 5321bis.		RFC 5322 if 5322bis is not progressed simultaneously with 5321bis.
	(This is not expected to happen.)		(This is not expected to happen.)
End of changes. 7 change blocks.
	17 lines changed or deleted		11 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/