Hi Rob, On 9/21/20 2:20 AM, Rob Sayre wrote: > Paul Hoffman <[email protected]> wrote: > >> Greetings again. A document on which I am a co-author refers to >> draft-ietf-dprive-rfc7626-bis. As I was updating references in that >> draft, I thought that maybe draft-ietf-dprive-rfc7626-bis was done. >> However, according to > https://datatracker.ietf.org/doc/draft-ietf-dprive-rfc7626-bis/, >> this draft's state has be "AD followup" for many months now. >> >> Is there something that the draft authors or the DPRIVE WG need to do to >> help move this forward? > > Other recent submissions have changed their references to RFC 7626. What > changes in the 7626-bis document are important to you? >
The changes made to the BCP document were driven by feedback from IESG members who rightly pointed out that the BCP referred to text originally found in 7626 and that 7626-bis was in a state of churn. In order to move the BCP forward, it was determined that the references could be safely changed to 7626. I cannot speak to changes made in other documents. Regards, Brian
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dns-privacy mailing list [email protected] https://www.ietf.org/mailman/listinfo/dns-privacy
