I would be happy to give an overview of draft-barnes-acme-*, and some of the design rationales for what's in there.
It would be good to have some input form other folks who have designed and deployed cert automation stuff, e.g., CAs and hosting/server/CDN operators. In terms of goals for the BoF, it wouldn't be unreasonable to try to get some agreement around scope -- what certificate management are we trying to automate, what's missing in existing RFCs, and what solutions have people come up with already? On Thu, Feb 12, 2015 at 10:57 AM, Salz, Rich <rs...@akamai.com> wrote: > Our BoF for the Dallas IETF next month was approved. The chairs are Ted > Hardie (on cc) and myself. Remote access will be available via jabber and > meetecho. > > As Stephen said, this is a non-WG-forming BoF, but it’s quite likely > that the WG will form before we have a chance to hold another BoF. > > > > This note is to solicit agenda topics, open issues, people who want to > make a presentation, and so on. We only have an hour, so presentations > will likely be short and the bulk of the time will be open mic and > capturing issues. > > > > And if anyone is in an early mood to volunteer to take notes, I’ll buy you > a beverage after the BoF J > > > > -- > > Principal Security Engineer, Akamai Technologies > > IM: rs...@jabber.me Twitter: RichSalz > > > > _______________________________________________ > Acme mailing list > Acme@ietf.org > https://www.ietf.org/mailman/listinfo/acme > >
_______________________________________________ Acme mailing list Acme@ietf.org https://www.ietf.org/mailman/listinfo/acme
