Last Call Review of draft-ietf-emailcore-rfc5322bis-11
review-ietf-emailcore-rfc5322bis-11-opsdir-lc-jiang-2024-04-28-00
Request | Review of | draft-ietf-emailcore-rfc5322bis |
---|---|---|
Requested revision | No specific revision (document currently at 12) | |
Type | Last Call Review | |
Team | Ops Directorate (opsdir) | |
Deadline | 2024-04-29 | |
Requested | 2024-04-15 | |
Authors | Pete Resnick | |
I-D last updated | 2024-04-28 | |
Completed reviews |
Genart Last Call review of -11
by Thomas Fossati
(diff)
Opsdir Last Call review of -11 by Sheng Jiang (diff) Artart Last Call review of -11 by Joseph Yee (diff) |
|
Assignment | Reviewer | Sheng Jiang |
State | Completed | |
Request | Last Call review on draft-ietf-emailcore-rfc5322bis by Ops Directorate Assigned | |
Posted at | https://mailarchive.ietf.org/arch/msg/ops-dir/qtMSoKyk5qK75cE2GAS0Rp7zrL0 | |
Reviewed revision | 11 (document currently at 12) | |
Result | Has nits | |
Completed | 2024-04-28 |
review-ietf-emailcore-rfc5322bis-11-opsdir-lc-jiang-2024-04-28-00
Reviewer: Sheng Jiang Review result: Has Nits I have reviewed this document as part of the OPS directorate's ongoing effort to review all IETF documents being processed by the IESG. Comments that are not addressed in last call may be included in AD reviews during the IESG review. Document editors and WG chairs should treat these comments just like any other last call comments. Document: draft-ietf-emailcore-rfc5322bis Reviewer: Sheng Jiang Review Date: 2024-04-29 This Standards Track document replaces RFC5322, specifies the Internet Message Format (IMF), a syntax for text messages that are sent between computer users, within the framework of "electronic mail" messages. This document is well-written. It is almost ready for publication from the INT area perspective. A couple of Nits is listed below: It is not needed to list RFC2822 & RFC822, the historic documents far before RFC5322. The history can be tracked just from the mentioning of RFC5322. The quoting format is not following the normal RFC setting. The format of requiring language boilerplate is also containing errors. It is recommended to replace quoting label, such as BCP14, STD13, STD18, by normal RFC +number.