Thanks, David, for the re-review.
A draft has just been
submitted to replace RFC 1846 (Experimental) with a Standards Track RFC:
https://datatracker.ietf.org/doc/draft-klensin-rfc1846bis/
The IESG should decide whether to proceed with the downref to RFC 1846bis
vs. publish the 1846bis draft as a standards track RFC and reference it.
That decision is the open issue in this review of the nullmx draft.
Right, and the decision has already been made, which is why the second
last-call notice says that the document has been "tentatively
approved":
The plan is to put the nullmx draft into the RFC Editor queue. If we
can do the 1846bis processing quickly, so that when AUTH48 comes for
nullmx we see 1846bis as being essentially done, we will hold nullmx,
process the two documents together, and change the reference. But if
it looks like 1846bis is getting hung up, we will proceed with
publication of nullmx with the downref.
That plan was discussed on the apps-discuss list a couple of weeks ago.
Barry