idnits 2.17.00 (12 Aug 2021) /tmp/idnits31486/draft-ietf-yam-5321bis-smtp-pre-evaluation-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 364: '... extensions SHOULD explicitly spe...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: Small Editorial Errors: Clear up various small editorial errors, e.g., the use of "SHOULD not" in one location. YAM issue tracker issues 5, 6, 9, 12, and 13 refer to issues of this sort. The working group will add others that may be identified in its detailed review. See Appendix B for details. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: Tracker Issue 13: In section 4.2.5, "SHOULD not" appears, with lowercase "not". The "NOT" should be in uppercase. http://trac.tools.ietf.org/wg/yam/trac/ticket/13 This item documents an editorial error, and the working group will make a change for it. -- The document date (April 15, 2010) is 4418 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 821 (Obsoleted by RFC 2821) -- Obsolete informational reference (is this intentional?): RFC 1869 (Obsoleted by RFC 2821) -- Obsolete informational reference (is this intentional?): RFC 2821 (Obsoleted by RFC 5321) Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 YAM Working Group J. Klensin 3 Internet-Draft 4 Intended status: Informational B. Leiba 5 Expires: October 17, 2010 Huawei Technologies 6 April 15, 2010 8 Preliminary Evaluation of RFC5321, Simple Mail Transfer Protocol (SMTP), 9 for advancement from Draft Standard to Full Standard by the YAM Working 10 Group 11 draft-ietf-yam-5321bis-smtp-pre-evaluation-04 13 Abstract 15 This memo is a preliminary evaluation of RFC 5321, Simple Mail 16 Transfer Protocol for advancement from Draft to Full Standard. It 17 has been prepared by the The Yet Another Mail Working Group. 19 THIS INTERNET DRAFT IS NOT MEANT TO BE PUBLISHED AS AN RFC, BUT IS 20 WRITTEN TO FACILITATE DISCUSSION WITH THE IESG. 22 Status of this Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on October 17, 2010. 39 Copyright Notice 41 Copyright (c) 2010 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 1.1. Note to RFC Editor . . . . . . . . . . . . . . . . . . . . 3 58 2. Preliminary Evaluation . . . . . . . . . . . . . . . . . . . . 3 59 2.1. Document . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 2.2. Time in Place . . . . . . . . . . . . . . . . . . . . . . . 3 61 2.3. Implementation and Operational Experience . . . . . . . . . 3 62 2.4. Proposed Changes . . . . . . . . . . . . . . . . . . . . . 4 63 2.5. Non-Changes . . . . . . . . . . . . . . . . . . . . . . . . 5 64 2.6. Downward references . . . . . . . . . . . . . . . . . . . . 6 65 2.7. IESG Feedback . . . . . . . . . . . . . . . . . . . . . . . 6 66 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 67 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 68 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7 69 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 70 6.1. Normative References . . . . . . . . . . . . . . . . . . . 7 71 6.2. Informative References . . . . . . . . . . . . . . . . . . 7 72 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . . 7 73 A.1. Changes from version -01 to -02 . . . . . . . . . . . . . . 7 74 A.2. Changes from version -00 to -01 . . . . . . . . . . . . . . 8 75 Appendix B. Detailed Issues List . . . . . . . . . . . . . . . . . 8 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 78 1. Introduction 80 A preliminary evaluation has been made of Simple Mail Tranfer 81 Protocol [RFC5321] by the Yet Another Mail (YAM) Working Group for 82 advancing it from Draft to Full Standard. The YAM WG requests 83 feedback from the IESG on this decision. 85 1.1. Note to RFC Editor 87 This Internet-Draft is not meant to be published as an RFC. It is 88 written to facilitate processing within the IESG. 90 2. Preliminary Evaluation 92 2.1. Document 94 Title: Simple Mail Transfer Protocol 96 Link: http://tools.ietf.org/html/rfc5321 98 2.2. Time in Place 100 RFC2026: _ "A specification shall remain at the Draft Standard 101 level for at least four (4) months, or until at least one IETF 102 meeting has occurred." _ 104 Published: October 2008 106 2.3. Implementation and Operational Experience 108 RFC2026: _ "significant implementation and successful operational 109 experience ... characterized by a high degree of technical 110 maturity and by a generally held belief that the specified 111 protocol or service provides significant benefit to the Internet 112 community." _ 114 Confidence level: Very high. 116 Electronic mail (historically known as "netmail" before "email" came 117 into common use) has been in active use in the Internet community 118 since the early 1970s. Although many small adjustments and 119 clarifications have been made, the basic transport protocol that is 120 now used has been changed in only two important ways since the 121 publication of RFC 821 in August 1982. One of those changes was the 122 introduction of DNS-based mail routing with the MX record with RFC 123 974 in January 1986 (with some small clarifications in RFC 1123 in 124 October 1979). The second was the introduction of a model for 125 negotiating optional services with RFC 1425 in February 1993. 127 While many mail systems over the years have relied more on the 128 robustness of receiving systems in the face of deviations (or 129 creative interpretations of RFC 821 language in spite of changes and 130 clarifications over the last 27 years), the DRUMS WG work that 131 produced RFC 2821 [RFC2821] in April 2001 was largely an update to 132 clarify various provisions. With the exception of a very few edge- 133 case clarifications and changes in requirements levels, systems that 134 conform to the combination of RFC 821 [RFC0821] and RFC 1869 135 [RFC1869] (both Full Standards) conform to RFCs 2821 (April 2001) and 136 5321. Those differences represented existing practice when RFC 5321 137 was written and have been well-tested and widely deployed. 139 2.4. Proposed Changes 141 The YAM WG proposes making the changes listed below in a revision. 142 That the working group will review or consider an issue means that 143 when RFC 5321bis is submitted for IESG approval, either changes will 144 have be made for that issue or the working group will provide the 145 IESG a summary of why it decided not to. 147 Terminology: There has been ongoing controversy about the 148 terminology in RFC 5321 and especially changes made between 821 149 and 2821 or between 2821 and 5321. While we assume that 5321 is 150 adequate, the WG will review terminology as appropriate and may 151 make some adjustments. 153 Metalanguage: During and after IETF Last Call on 5321, some 154 suggestions were made about how to make metalanguage productions 155 easier to find and connect. A complete rewrite or restructuring 156 of the metalanguage should be avoided on the grounds that it would 157 carry a very high risk of introducing errors. Instead, resources 158 and tools permitting (significant manual work is now required), 159 the revised document will contain an index to productions and 160 where they are defined. 162 Normative References: RFC 5321 is worded in a way that makes some 163 references normative that are not strictly required to be. The WG 164 will consider whether those rewordings are appropriate. In 165 particular, the reference to RFC 821 will be moved to Informative 166 because all normative uses have been removed. 168 Existing Errata Reports: The working group will incorporate 169 corrections to accepted errata, as shown in the RFC Editor's 170 errata tool. Errata ID 1683 is currently the only such item. IDs 171 1543 and 1851 are reported, but unverified; the working group will 172 consider those. See Appendix B for details. 174 Small Editorial Errors: Clear up various small editorial errors, 175 e.g., the use of "SHOULD not" in one location. YAM issue tracker 176 issues 5, 6, 9, 12, and 13 refer to issues of this sort. The 177 working group will add others that may be identified in its 178 detailed review. See Appendix B for details. 180 Clarifications: The working group will attempt to address things 181 that have ben identified as unclear in RFC 5321. YAM issue 182 tracker issues 7, 8, 10, and 11 refer to issues of this sort. 183 There has been discussion of these on the mailing list, and the 184 resolutions of each may or may not result in a change in the 185 document. See Appendix B for details. In no case will 186 clarification changes be significant enough to violate "Non- 187 Changes", Section 2.5. 189 2.5. Non-Changes 191 The YAM WG discussed and chose not to make the following changes: 193 1. Complete revision, rearrangement, or reformatting of metalanguage 194 (see #2 above). 196 2. Any extensions that would violate the rules for Full Standard or 197 otherwise require revisiting the approved interoperability report 198 for RFC 5321. 200 3. A number of extensions and changes that would have imposed 201 significant new requirements on SMTP, or that would have implied 202 incompatible changes, were proposed both during the DRUMS WG 203 period (leading up to RFC 2821) and during the subsequent 204 discussions that led to RFC 5321. In each case, the authors were 205 advised to prepare a specific Internet-Draft describing the 206 change, convince the community to progress it to Proposed 207 Standard, and then implement and deploy the change quickly enough 208 to "catch up" with the progress that started with RFC 2821. The 209 notion was that those changes could then be integrated with the 210 progression at the same maturity level. It is important to note 211 that, independent of any constraints imposed by the YAM charter 212 design, none of those proposals have appeared and been progressed 213 even to IETF Last Call. 215 4. As agreed when RFC 5321 was reviewed, the examples will not be 216 revised to bring them into alignment with RFC 2606 (BCP 32) 217 conventions (example.com, etc.). The issues are explained in 218 Section 1.3 of RFC 5321. The community also noted at the time 219 that the relevant examples have been in use, substantially 220 unchanged, for more than a quarter-century with no serious claims 221 of confusion or other harm being caused. 223 5. The Security Considerations section was extensively reviewed in 224 2008 (during the review and approval of RFC 5321). No evidence 225 has appeared since then that would require further review or 226 additional changes. 228 2.6. Downward references 230 At Full Standard, the following references would be downward 231 references: 233 RFC 5322 if 5322bis is not progressed simultaneously with 5321bis. 234 (This is not expected to happen.) 236 RFC 4291, IP Version 6 Addressing Architecture. 238 RFC 3848, ESMTP and LMTP Transmission Types Registration. Note 239 that it is possible to rephrase RFC 5321bis to avoid this 240 normative reference and the WG will consider doing that. 242 2.7. IESG Feedback 244 The YAM WG requests feedback from the IESG on this decision. In 245 particular: 247 o Does the IESG believe the proposed changes are suitable during a 248 move from Draft to Full Standard? 250 o Excluding the previous proposed changes and expected IESG support 251 for technically substantive IETF last call feedback, does the IESG 252 believe any additional changes are critical to advance this 253 document from draft to full standard? If so, please provide 254 sufficient information so the WG can address these issues prior to 255 IETF last call or determine that the document is inappropriate for 256 the YAM WG to process at this time. 258 o Does the IESG consider the downward references acceptable for a 259 full standard? If not, please cite which specific downward 260 reference or references are problematic and why so the WG can 261 address these issues prior to IETF last call or determine the 262 document is inappropriate for the YAM WG to process at this time. 264 3. IANA Considerations 266 This document contains no IANA actions. 268 4. Security Considerations 270 This document requests IESG feedback and does not raise any security 271 concerns. Security considerations for RFC 5321 have been taken into 272 account during the preliminary evaluation and appear in either 273 Section 2.4 or Section 2.5 of this document. 275 5. Acknowledgments 277 This document was prepared from a template supplied by Subramanian 278 Moonesamy. 280 Some of the information provided in this document, but not provided 281 in the RFC 1652 evaluation (http://www.ietf.org/id/ 282 draft-ietf-yam-rfc1652bis-pre-evaluation-00.txt), was inspired by 283 brief discussions with Pasi Eronen and Subramanian Moonesamy during 284 IETF 76. 286 6. References 288 6.1. Normative References 290 [RFC5321] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321, 291 October 2008. 293 6.2. Informative References 295 [RFC0821] Postel, J., "Simple Mail Transfer Protocol", STD 10, 296 RFC 821, August 1982. 298 [RFC1869] Klensin, J., Freed, N., Rose, M., Stefferud, E., and D. 299 Crocker, "SMTP Service Extensions", STD 10, RFC 1869, 300 November 1995. 302 [RFC2821] Klensin, J., "Simple Mail Transfer Protocol", RFC 2821, 303 April 2001. 305 Appendix A. Change Log 307 A.1. Changes from version -01 to -02 309 o Added classes of changes for "errata" and "clarifications". 311 o Included YAM issue tracker numbers in the lists of possible 312 changes. 314 A.2. Changes from version -00 to -01 316 o Added Security Considerations and Examples to the "no change" list 317 in Section 2.5. 319 o Identified RFC 821 as a specific reference to be moved from 320 Normative to Informative. 322 o Add blanket placeholder for changes due to small editorial errors. 324 Appendix B. Detailed Issues List 326 What follows are abbreviated details of the errata and tracker issues 327 at the time of this writing, along with URLs to the actual entries. 328 They are provided here to make it easier for IESG members -- and 329 others -- to review them. If your browser does not automatically 330 turn URLs into clickable links, copy/paste should still be 331 convenient. 333 Errata ID 1543: In section 3.8, client should treat a closed 334 connection as a 451 response, not as 421 (current). 335 http://www.rfc-editor.org/errata_search.php?rfc=5321 336 The working group will consider this item. Discussion so far 337 leans toward not making the change. 339 Errata ID 1683: In section 4.4, missing repeat in grammar for 340 Additional-Registered-Clauses. 341 http://www.rfc-editor.org/errata_search.php?rfc=5321 342 This item has been accepted, and the working group will make a 343 change for it. 345 Errata ID 1851: In section 4.1.1.5, text specifying server behaviour 346 on a closed connection is misplaced, and should be in section 347 4.1.1.10 or section 3.8. 348 http://www.rfc-editor.org/errata_search.php?rfc=5321 349 The working group will consider this item. 351 Tracker Issue 5: In section 6.1, reword "next subsection" to specify 352 the section number, for clarity. 353 http://trac.tools.ietf.org/wg/yam/trac/ticket/5 354 This item suggests an editorial change, and the working group will 355 consider it. 357 Tracker Issue 6: In section 4.4, there is extraneous text that 358 should be removed or corrected (probably a paste error). 359 http://trac.tools.ietf.org/wg/yam/trac/ticket/6 360 This item documents an editorial error, and the working group will 361 make a change for it. 363 Tracker Issue 7: In section 2.2.2, add a bullet saying "Future SMTP 364 extensions SHOULD explicitly specify if they are valid on the 365 Submission port." 366 http://trac.tools.ietf.org/wg/yam/trac/ticket/7 367 The working group will consider this item. 369 Tracker Issue 8: In section 4.1.1.3, remove text about source routes 370 and move text about failed recipients here. 371 http://trac.tools.ietf.org/wg/yam/trac/ticket/8 372 The working group will consider this item. 374 Tracker Issue 9: In section 3.9.2, there is extraneous text that 375 should be removed or corrected (probably a paste error). 376 http://trac.tools.ietf.org/wg/yam/trac/ticket/9 377 This item documents an editorial error, and the working group will 378 make a change for it. 380 Tracker Issue 10: In section 3.9, add a subsection for "Backup MX" 381 or "Plain forwarding". 382 http://trac.tools.ietf.org/wg/yam/trac/ticket/10 383 The working group will consider this item. 385 Tracker Issue 11: In section 3.1, a server can offer two greeting 386 codes to a new connection: 220 or 554. Clarify the semantics of 387 the 554 code. 388 http://trac.tools.ietf.org/wg/yam/trac/ticket/11 389 The working group will consider this item. 391 Tracker Issue 12: In examples, explicitly state that the examples 392 will not be changed to use RFC 2606 domain names (such as 393 example.com). 394 http://trac.tools.ietf.org/wg/yam/trac/ticket/12 395 This item suggests an editorial change, and the working group will 396 consider it. 398 Tracker Issue 13: In section 4.2.5, "SHOULD not" appears, with 399 lowercase "not". The "NOT" should be in uppercase. 400 http://trac.tools.ietf.org/wg/yam/trac/ticket/13 401 This item documents an editorial error, and the working group will 402 make a change for it. 404 Authors' Addresses 406 John C Klensin 407 1770 Massachusetts Ave, Ste 322 408 Cambridge, MA 02140 409 USA 411 Phone: +1 617 245 1457 412 Email: john+ietf@jck.com 414 Barry Leiba 415 Huawei Technologies 417 Phone: +1 646 827 0648 418 Email: barryleiba@computer.org 419 URI: http://internetmessagingtechnology.org/