< draft-ietf-yam-5321bis-smtp-pre-evaluation-00.txt		draft-ietf-yam-5321bis-smtp-pre-evaluation-01.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: May 16, 2010 Huawei Technologies		Expires: May 17, 2010 Huawei Technologies
	November 12, 2009		November 13, 2009
	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-00.txt		draft-ietf-yam-5321bis-smtp-pre-evaluation-01.txt
	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.
	skipping to change at page 1, line 44 ¶		skipping to change at page 1, line 44 ¶
	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		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on May 16, 2010.		This Internet-Draft will expire on May 17, 2010.
	Copyright Notice		Copyright Notice
	Copyright (c) 2009 IETF Trust and the persons identified as the		Copyright (c) 2009 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
	skipping to change at page 2, line 33 ¶		skipping to change at page 2, line 33 ¶
	2.4. Proposed Changes . . . . . . . . . . . . . . . . . . . . . 4		2.4. Proposed Changes . . . . . . . . . . . . . . . . . . . . . 4
	2.5. Non-Changes . . . . . . . . . . . . . . . . . . . . . . . . 4		2.5. Non-Changes . . . . . . . . . . . . . . . . . . . . . . . . 4
	2.6. Downward references . . . . . . . . . . . . . . . . . . . . 5		2.6. Downward references . . . . . . . . . . . . . . . . . . . . 5
	2.7. IESG Feedback . . . . . . . . . . . . . . . . . . . . . . . 5		2.7. IESG Feedback . . . . . . . . . . . . . . . . . . . . . . . 5
	3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6		3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
	4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6		4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
	5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 6		5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 6
	6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6		6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
	6.1. Normative References . . . . . . . . . . . . . . . . . . . 6		6.1. Normative References . . . . . . . . . . . . . . . . . . . 6
	6.2. Informative References . . . . . . . . . . . . . . . . . . 6		6.2. Informative References . . . . . . . . . . . . . . . . . . 6
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6		Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . . 7
			A.1. Changes from version -00 to -01 . . . . . . . . . . . . . . 7
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
	1. Introduction		1. Introduction
	A preliminary evaluation has been made of Simple Mail Tranfer		A preliminary evaluation has been made of Simple Mail Tranfer
	Protocol [RFC5321] by the Yet Another Mail (YAM) Working Group for		Protocol [RFC5321] by the Yet Another Mail (YAM) Working Group for
	advancing it from Draft to Full Standard. The YAM WG requests		advancing it from Draft to Full Standard. The YAM WG requests
	feedback from the IESG on this decision.		feedback from the IESG on this decision.
	1.1. Note to RFC Editor		1.1. Note to RFC Editor
	skipping to change at page 4, line 39 ¶		skipping to change at page 4, line 39 ¶
	suggestions were made about how to make metalanguage productions		suggestions were made about how to make metalanguage productions
	easier to find and connect. A complete rewrite or restructuring		easier to find and connect. A complete rewrite or restructuring
	of the metalanguage should be avoided on the grounds that it would		of the metalanguage should be avoided on the grounds that it would
	carry a very high risk of introducing errors. Instead, resources		carry a very high risk of introducing errors. Instead, resources
	and tools permitting (significant manual work is now required),		and tools permitting (significant manual work is now required),
	the revised document will contain an index to productions and		the revised document will contain an index to productions and
	where they are defined.		where they are defined.
	Normative References: RFC 5321 is worded in a way that makes some		Normative References: RFC 5321 is worded in a way that makes some
	references normative that are not strictly required to be. The WG		references normative that are not strictly required to be. The WG
	will consider whether rewording to make such references		will consider whether those rewordings are appropriate.
	informative is appropriate.
	2.5. Non-Changes		2.5. Non-Changes
	The YAM WG discussed and chose not to make the following changes:		The YAM WG discussed and chose not to make the following changes:
	1. Complete revision, rearrangement, or reformatting of metalanguage		1. Complete revision, rearrangement, or reformatting of metalanguage
	(see #2 above).		(see #2 above).
	2. Any extensions that would violate the rules for Full Standard or		2. Any extensions that would violate the rules for Full Standard or
	otherwise require revisiting the approved interoperability report		otherwise require revisiting the approved interoperability report
	skipping to change at page 5, line 19 ¶		skipping to change at page 5, line 19 ¶
	case, the authors were advised to prepare a specific Internet-		case, the authors were advised to prepare a specific Internet-
	Draft describing the change, convince the community to progress		Draft describing the change, convince the community to progress
	it to Proposed Standard, and then implement and deploy the change		it to Proposed Standard, and then implement and deploy the change
	quickly enough to "catch up" with the progress that started with		quickly enough to "catch up" with the progress that started with
	RFC 2821. The notion was that those changes could then be		RFC 2821. The notion was that those changes could then be
	integrated with the progression at the same maturity level. It		integrated with the progression at the same maturity level. It
	is important to note that, independent of any constraints imposed		is important to note that, independent of any constraints imposed
	by the YAM charter design, none of those proposals have appeared		by the YAM charter design, none of those proposals have appeared
	and been progressed even to IETF Last Call.		and been progressed even to IETF Last Call.
			4. The Security Considerations section was extensively reviewed last
			year (during the review and approval of RFC 5321). No evidence
			has appeared since then that would require further review or
			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.)
	RFC 4291, IP Version 6 Addressing Architecture.		RFC 4291, IP Version 6 Addressing Architecture.
	skipping to change at page 7, line 5 ¶		skipping to change at page 7, line 5 ¶
	[RFC0821] Postel, J., "Simple Mail Transfer Protocol", STD 10,		[RFC0821] Postel, J., "Simple Mail Transfer Protocol", STD 10,
	RFC 821, August 1982.		RFC 821, August 1982.
	[RFC1869] Klensin, J., Freed, N., Rose, M., Stefferud, E., and D.		[RFC1869] Klensin, J., Freed, N., Rose, M., Stefferud, E., and D.
	Crocker, "SMTP Service Extensions", STD 10, RFC 1869,		Crocker, "SMTP Service Extensions", STD 10, RFC 1869,
	November 1995.		November 1995.
	[RFC2821] Klensin, J., "Simple Mail Transfer Protocol", RFC 2821,		[RFC2821] Klensin, J., "Simple Mail Transfer Protocol", RFC 2821,
	April 2001.		April 2001.
			Appendix A. Change Log
			A.1. Changes from version -00 to -01
			o Added Security Considerations to the "no change" list in
			Section 2.5.
	Authors' Addresses		Authors' Addresses
	John C Klensin		John C Klensin
	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
End of changes. 7 change blocks.
	7 lines changed or deleted		20 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/