How can it go WGLC with section 6 an open question? in every other respect I like the document. Bad Hair and all.
I would like to understand if we could work out a way to do traceroute in the codes, with some defined code to ask the DNS resolver to perform a TTL drop on a counter and mark itself into the chain, which would help uncover resolver chains. With IANA registry requests, I may be wrong here, but I thought we had some (boilerplate?) language about how IANA is asked to operate the registry: what criteria judge acceptance. Is it like the OID and basically open (hair oil) slather, or is it only at WG RFC documented request? -G On Wed, Oct 24, 2018 at 4:42 PM Tim Wicinski <tjw.i...@gmail.com> wrote: > > > Hi > > We've been talking with the authors of Extended Error and now that > they've gotten around to updating the document, and the chairs > feel it is ready for Working Group Last Call. > > We're going to kick this WGLC off this week and run it through IETF103. > This will give folks time during the meeting to bring up any issues > they may have there. > > > This starts a Working Group Last Call for draft-ietf-dnsop-extended-error > > Current versions of the draft is available here: > https://datatracker.ietf.org/doc/draft-ietf-dnsop-extended-error/ > > > The Current Intended Status of this document is: Standards Track > > Please review the draft and offer relevant comments. > If this does not seem appropriate please speak out. > If someone feels the document is *not* ready for publication, > please speak out with your reasons. > > This starts a two+ week Working Group Last Call process, > and ends on at the end of IETF 103: 9 November 2018 > > thanks > tim > > _______________________________________________ > 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
