On Apr 6, 2018, at 14:43, 神明達哉 <jin...@wide.ad.jp> wrote: > At Thu, 05 Apr 2018 17:15:47 +0000, > Job Snijders <j...@ntt.net> wrote: > >> While the chair notes awareness of the point I raised, I’d like the be >> explicit to avoid any confusion. >> >> This document is *not* ready for publication. There is no implementation >> report available for review and consideration. > > (After reading other messages in this thread) I tend to agree. Even > after careful reviews of protocol text, an attempt of actually > implementing it often reveals non-negligible issues that were > overlooked in the review.
I think it's perhaps worth looking at this from the implementation perspective, yes. I don't doubt that we can expect close collaboration and testing between APNIC Labs and the various resolver implementors, especially given the experience with 8145. If I'm right about that, it seems to me that (a) delaying the last call to allow any unexpected issues with the specification to be documented and (b) including details of the testing/compliance criteria in the document for the benefit of future implementations are both good ideas. In other words, don't think of this as a constraint on publication but rather an opportunity to make the document better without holding up implementation. Joe _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
