--On Tuesday, February 18, 2020 19:08 +0100 Alessandro Vesely
I don't think a cleanup, like e.g. the one you proposed[*],
would revert rfc5321bis to proposed standard. However, I'm
not clear on how that works. Certainly, rfc2821 was reverted
to proposed standard, but I wasn't there and I don't know
who/how decided to label that I-D to a lower standard.
BCP 9 is not so precise:
At the time, there was at least one important issue and it was
independent of the BCP 9 text you cited. 2821 was essentially a
merge of RFCs
821 (a full standard)
974 (don't remember its status at the time 2821 was in
progress, but note that it is listed as part of STD 10, so I
assume full standar)
some text from 1123 (another full standard)
1829 (another full standard)
and bits and pieces of text, some of it completely new, either
picked up from assorted places or inserted to better align 2821
with 2822 than 821 and 822 were aligned.
That new text, and the merger itself, were, in principle and
maybe in practice, untested for how they would work in terms of
comprehension, implementations, and deployment in the future.
Hence PS. Could we have pushed it through as full standard?
Maybe. But the experience of the changes that needed to be made
to get to 5321 (virtually all of which were "cleanup") suggests
that would have been a bad decision.
Since there are quite some issues to be clarified[†], I
think the new WG will need some detailed guidelines about what
would be a very significant change.
Yes. See my earlier note. And, again, I'm skeptical that can
actually be done by guidelines rather that a case-by-case review.
ietf-smtp mailing list