After some discussion with Barry, what seems to have been missing is a
clear statement of needs and goals. Many different approaches to
revision are possible and reasonable. So the reasons for choosing one
needs to be clear.
Logic for a limited effort:
The current, well-established, core specifications for email are at
a lower standards level than what the (realistically) long-obsolete
versions. The goal is to (finally) establish the later versions as full
standards (and, I assume, declare the earlier versions as obsolete.)
Any substantive revision to the current specifications runs the
risk -- actually the likelihood -- of resulting in the output being
labeled at a /lower/ standards level than it current has, thereby
exacerbating the original issue.
Hence the revision effort needs to be constrained to altering only
essential, /minor/ details. A cleanup exercise, if you will.
ietf-smtp mailing list