John Levine writes: > There's no great hurry in getting the DMARC document published, since > nothing currently depends on it, and if reasonable people are finding > holes in it that make it hard to write interoperable code, I'd rather > fix the holes than add lengthy errata or recycle later.
*If* the existing code bases are interoperable, then it makes sense to postpone publication to fix the spec to conform to actual practice (which is its purpose, after all). Is it worth the effort/editor time to compose and discuss better language and the calendar time to wait for confirmation from implementors? _______________________________________________ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
