Hi

Since we (the chairs) took the summer recovering from the .onion IETF Last Call, I wanted to update the working group on what has been accomplished and what is currently outstanding.

        The Negative-Trust-Anchor draft is now RFC7646.

        The root-loopback draft is getting ready to be published.

        The dns-terminology draft is in the RFC Editor Queue.

Along with the key-timing and .onion drafts, the Working Group will have published 9 drafts this year. We want to thank you for all your work. However, we are not done:

We have *two* Working Group Last Calls on documents that have been through a major discussion process, but received *no* mention during the process:

     draft-ietf-dnsop-qname-minimisation-05
     https://datatracker.ietf.org/doc/draft-ietf-dnsop-qname-minimisation/


     draft-ietf-dnsop-cookies-05
     https://datatracker.ietf.org/doc/draft-ietf-dnsop-cookies/


The chairs feel these documents are done and ready to move forward. But it does seem bad form to just act unilaterally.

We have one document in Call for Adoption.

     draft-howard-isp-ip6rdns
     https://datatracker.ietf.org/doc/draft-howard-isp-ip6rdns/

The author has addressed many comments and concerns raised since IETF91 (Honolulu), and the chairs feel that all concerns have been addressed and should be adopted. Again, there has been no comments since starting call for adoption.
We have several drafts which have been steadily being worked on and are ready for Working Group Last Call:

     draft-ietf-dnsop-alt-tld
     https://datatracker.ietf.org/doc/draft-ietf-dnsop-alt-tld/

     draft-dnsop-edns-tcp-keepalive
     https://datatracker.ietf.org/doc/draft-ietf-dnsop-edns-tcp-keepalive/

     draft-dnsop-ietf-dnsop-5966bis
     https://datatracker.ietf.org/doc/draft-ietf-dnsop-5966bis/

alt-tld may be waiting for keeping RFC6761 discussions, but the other tcp-keepalive is more than ready, and 5966bis is ready once I give it another editorial read.
Saying all of this, we’re putting out a call for agenda items for Yokohama. Please send your request to dnsop-cha...@ietf.org

We plan on spending the next month(s) moving the levers of the process forward.

thanks

tim

_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to