Hi, (chair hat on)
To the question of what's on charter for DNSOP: On Mar 9, 2015, at 7:08 AM, D. J. Bernstein <[email protected]> wrote: > My understanding is that [email protected] is not chartered to make DNS > protocol changes, so any discussion here will have to be repeated in an > appropriate working group From our charter as approved (http://datatracker.ietf.org/wg/dnsop/charter/): "4. Publish documents to address operational issues with the DNS protocols by extending or performing protocol maintenance on them. Act as focal-point for operator discussion and provide advice to the Ops ADs and other WGs on EDNS0 options, new RRTYPEs, DNSSEC, record synthesis, or other mechanics of extending DNS to support other applications. 5. Serve as a home for drafts that document the problem space around existing or new DNS issues. The group, with the advice and consent of the responsible AD in coordination with other areas, will then decide whether these issues belong in DNSOP under the existing charter and, if not, will work with the authors and appropriate ADs to determine the proper place for the work to be carried out. " It seems to your chairs at least that discussion is in scope for DNSOP, in that we can decide any of: a) there's no work here, per open discussion in the WG with operators and implementers; b) there's work here, per open discussion, and it's within item 4 above, so we can do it in DNSOP; c) there's work here but it needs to go to another WG, in accordance with item 5, perhaps one to be spun up for the purpose, as was done with DPRIVE At the very least, the draft seems to have generated some interest, and we're happy to host this initial discussion in DNSOP as an initial step in order to decide whether/how to proceed. thanks, Suzanne & Tim
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
