I've reviewed this document (straight from GitHub in this case).

I've opened a few issues:  
https://github.com/huitema/dnsoquic/issues/created_by/martinthomson

You will observe that some of these issues are old and remain unaddressed.  It 
is my opinion that the document is not ready and it needs another pass to 
improve a number of problems.

To be clear, I think that the core protocol definition is good.  

I found a large number of editorial issues when I was reviewing it.  I provided 
pull requests for some, but there are a great many more that would benefit from 
a careful proof read and cleanup.  Martin Duke found several issues to add to 
this; those also need to be addressed.

However, there are a number of substantive problems in the supporting material 
that I think need to be fixed.  For instance, some of these are false or 
misleading claims about security properties.  There are enough of these that I 
don't think that this document is fit to give to the IESG.  I don't think that 
any of these are hard to address, but there are rather a lot of them.

Regards,
Martin

On Wed, Oct 13, 2021, at 22:30, Brian Haberman wrote:
> DPRIVE & QUIC WG Participants,
>
>       This starts a 2-week DPRIVE WG Last Call for advancing 
> draft-ietf-dprive-dnsoquic-05 as a Proposed Standard. Please send all 
> substantive comments to the DPRIVE mailing list. Editorial comments 
> should be directed to the document editors. This last call will end 
> 11:59pm UTC on Oct. 27, 2021.
>
> Regards,
> Brian & Tim
>
> _______________________________________________
> dns-privacy mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/dns-privacy
>
> Attachments:
> * OpenPGP_signature

_______________________________________________
dns-privacy mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dns-privacy

Reply via email to