Murray S. Kucherawy writes: > As a reminder, the document passed through a lengthy Working Group > Last Call that ended in August of this year, followed by an > IETF-wide Last Call that ran from mid-November to early December. > The current discussion about XML format started during the latter, > and the discussion about interoperability considerations started > about a week ago.
This is not correct. I first pointed out that that text is not clear about whether both SPF and DKIM is needed in my email in 2024-12-02 [1], and [2]. During this discussion I proposed that we add Conformance requirements [3] section to the draft so that the requirements are clear, and are not hidden in hard to parse text. This discussion was then moved to the github isssue #170 at 2024-12-07 and this ticket was closed at 2024-12-22, and then I objected immediately about the closing of ticket [5], which started this current discussion. > The active discussions can continue. If they result in consensus of > the working group to change the document, we'll have to determine > whether the change necessitates an IETF-wide Last Call, and be > comfortable with whatever delay this will introduce in any case. I think that if we add Conformatnce Requirements section which just summarizes the mandatory to implement features from the current draft this should not have any issues, as everything in there is already been said in other sections. My original conformance requirements section from [3] is not up to date, as we already changed some parts but updating that should not be too big work. [1] https://mailarchive.ietf.org/arch/msg/dmarc/OivmvBSqHWpEAawuYxlFw5iiFD8/ [2] https://mailarchive.ietf.org/arch/msg/dmarc/01R6UF_IQVp7ASn2-mdBwlXxGsU/ [3] https://mailarchive.ietf.org/arch/msg/dmarc/n3C8DlVRxsYuwPX4Ts5OZkrwqNw/ [4] https://github.com/ietf-wg-dmarc/draft-ietf-dmarc-dmarcbis/issues/170 [5] https://mailarchive.ietf.org/arch/msg/dmarc/G3Zr7GhZJZ6kHSeYZfE1HeRQ0VI/ -- [email protected] _______________________________________________ dmarc mailing list -- [email protected] To unsubscribe send an email to [email protected]
