It's time to ship. I mean sure, if somebody who does detailed reading has a killer problem I can see we'd talk it out but we're 7 revisions in, its 4 years later, and it seems rational to document the expectation this is modern DNS, and we do TCP as a MUST SUPPORT, Auth and recursive.
Its overdue. so +1 to ship -G On Mon, Apr 19, 2021 at 9:17 AM Suzanne Woolf <suzworldw...@gmail.com> wrote: > > Dear colleagues, > > > This message starts the Working Group Last Call for > draft-ietf-dnsop-tcp-requirements > (https://datatracker.ietf.org/doc/draft-ietf-dnsop-dns-tcp-requirements/) > > Since this draft has not been recently discussed in the WG, we figure people > might need to swap it back in, and we’re requesting BCP status. So the WGLC > will end in three weeks (instead of the usual two), on 3 May. > > Substantive comments to the list, please. It’s fine for minor edits to go > direct to the authors. > > We’d like to advance this but it needs some active support, so we need to > hear from folks who have found it useful, especially implementers. > > > Thanks, > Suzanne > For the chairs > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
