Hey Jacob, thanks for flagging this! I'm also interested in getting this draft moving again, and I'm willing to poke at it in whatever ways the group's happy with.
The only open issue I know of is some discussion in the thread at https://www.ietf.org/mail-archive/web/dnsop/current/msg18690.html that I need help synthesizing into the draft. I don't know enough about the subtleties here to have a strong opinion, and I'm happy to accept the consensus of the group. Coincidental, I raised the draft again briefly with a few folks in Prague (CC'd here), and I'm hoping for some feedback about reasonable next steps. -mike On Tue, Aug 1, 2017 at 1:17 AM, Jacob Hoffman-Andrews <j...@eff.org> wrote: > Hi, > > I'm interested in seeing > https://tools.ietf.org/html/draft-west-let-localhost-be-localhost-03 > move from draft status to become a standard. In particular, it would > allow browsers to start treating "localhost" as a secure context, which > would reduce attempts by application developers to abuse the public Web > PKI in order to issue certificates for localhost, which harms security. > See: > > https://groups.google.com/d/msg/mozilla.dev.security. > policy/T6emeoE-lCU/-k-A2dEdAQAJ > https://groups.google.com/d/msg/mozilla.dev.security.policy/eV89JXcsBC0/ > wsj5zpbbAQAJ > > What further steps are needed to move this draft along, and how can I help? > > Thanks, > Jacob > > _______________________________________________ > 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
