On Wed, Dec 2, 2020, at 02:18, Barry Leiba wrote:
> And yeah - if the latest mmark is causing artifacts I'll see what I can do about those. I admit I didn't> read through the whole thing in detail again after making the last updates.If it's easy to fix, please do, but don't get too wrapped up inspending time on that: the RFC Editor will be converting it to xml2rfcv3 anyway, and those issues will be resolved in that process.
Thanks Barry, it was really this simple:
-For servers which also support [!@RFC8579] delivery to special-use mailboxes,
+For servers which also support [@!RFC8579] delivery to special-use mailboxes,
Yep, I did feel rather silly. My workflow already spits out xml2rfc v3 files, so hopefully that saves the RFC editor some work :)
I've uploaded -06 with those two fixes, since I haven't seen any other feedback yet.
Bron.
--
Bron Gondwana, CEO, Fastmail Pty Ltd
brong@xxxxxxxxxxxxxxxx
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
