On Jun 26, 2023, at 8:20 AM, Brian Haberman <[email protected]> wrote:
> 
> Hi all,
>     Tim, Éric, and I have chatted about the next steps for the unilateral 
> probing draft. Here is the proposed plan for moving the draft forward as 
> Experimental:
> 
> 1. The authors verify that the implementations listed in Appendix A is 
> up-to-date. The chairs will request that this list be retained in the 
> published RFC.
> 
> 2. The authors capture the key metrics submitted to the mailing list for 
> assessing the experiment in a new appendix. The chairs believe that the below 
> metrics proposed by Scott Hollenbeck are a good starting point but other WG 
> participants may have other proposed metrics:
> 
>     A. Measurement of CPU and memory use between Do53 and DoT or DoQ.
>     B. Measurement of query response rates between Do53 and DoT or DoQ.
>     C. Measurement of server authentication successes and failures.
>     D. Measurement and descriptions of observed attack traffic, if any.
> 
> 3. The chairs will solicit a volunteer (or volunteers) to collect information 
> on any interoperability testing that has been carried out between 
> implementations that support this specification.

That all seems fine with me (not sure about my co-authors, but I'll speak for 
them unless they yarp about it).

> Once the WG is comfortable with the experimentation section and the metrics, 
> the chairs will submit the draft to the IESG for publication. We will propose 
> to revisit the status of the document twelve (12) months after publication as 
> an RFC.
> 
> Any concerns or suggestions on the above plan?

Please see the messages I sent to the list over the weekend. Florian has a 
major concern (responses from encrypting authoritative servers that are also 
acting as recursive resolvers), and I don't know how to deal with that in the 
draft because I don't see the differences from non-encrypting authoritative 
servers that are also acting as recursive resolvers. 

Beyond that, we have a stack of editorial comments already in the repo, and can 
put out a new draft with all the current text, then one final one with the 
results of the steps above.

--Paul Hoffman

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

Reply via email to