Hi Benno, On 9 May 2018, at 09:12, Benno Overeinder <be...@nlnetlabs.nl> wrote:
> There are now 2 implementations of kskroll-sentinel: > 1) peer-reviewed and merged in the BIND master branch; > 2) released with Unbound 1.7.1 last week. > > (And the draft mentions the implemention early versions of this > technique into the Knot resolver.) > > Implementation reports/observations for BIND and Unbound have been sent > to the mailing list. That's great. To the earlier question (the WGLC or WGLCish one) I have sympathy with what Job is saying, but I think we should be pragmatic and not pick on the one DNS extension that is actually seeing coordinated funding, implementation and testing because of problems that have been observed with entirely different extensions whose track record is not so good. Perhaps an acceptable compromise would be to expand slightly on the implementation reports from -12 (which I tend to agree look a bit like placeholders) and expand them to include details of: - specific revisions of code bases, and whether they were released, public and private - revisions of code bases (with similar detail) that exhibited interestingly different behaviour from that described in -12 For example, the use of different labels in earlier revisions of the draft seems worth mentioning to the extent that it's possible some code based on those earlier revisions is or has been running, and examples of those labels might well show up in historical or future data sets. With the observed high level of engagement from three major vendors on this it doesn't seem like fleshing out that section would take very long, and if it helped improve consensus on pushing the doc towards the IESG (which I am in favour of) it might be a good investment in time. I realise it's only a snapshot in time, but really so is a release. (Draft is good though, and in my opinion it could be written up and sent to the IESG right now. It still has to pass the IESG's scrutiny and an IETF-wide last call though, and I think the suggestions above if followed could only oil the tracks through those processes.) Joe
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
