I would like to present OmniPublish which is the protocol I was working on before ACME came along.
It is not exactly the same as ACME but I think it is important to bear both approaches in mind because we are going to end up requiring both and I think they should both work in the same way and be implemented in the same style. Consider SMTP and NNTP, they do different things but they do them in the same way. The protocols are very similar under the covers which made it easy to write mail/news readers. ACME is a replacement for the CA interface. The reason I did not propose doing that was that IETF has tried that on 3 separate occasions without success to date and W3C has tried it once. OmniPublish is designed as a meta-protocol that provides client applications with a one stop shop for all their network configuration and credential needs. When a Web Service starts up it needs to have a number of separate configurations performed: * Get a WebPKI cert * Get DNS parameters entered * Open firewall ports * Register contact info in a directory (Jabber, etc) Traditionally this information has to be hand configured separately. And this has major consequences for reliability. One of the main reasons I am skeptical about DANE is that we have three levels of configuration that can go wrong and today we expect all three to be done by hand, the DNSSEC config, the DANE entries for the server and the server itself. The only way I am going to trust that data is if those processes are automated. Hence the idea behind OmniPublish. On Tue, Jun 30, 2015 at 4:12 PM, Ted Hardie <[email protected]> wrote: > Just to bump this up on people's lists, Rich and I will put up a > preliminary agenda next Monday. If you want time for something other than > draft-barnes-acme, please let us know. > > thanks, > > Ted and Rich > > On Fri, Jun 26, 2015 at 10:54 AM, Ted Hardie <[email protected]> wrote: > >> Howdy, >> >> As you've seen from the IESG announcement, ACME has been approved as a >> working group, so our meeting in Prague will be as a working group rather >> than a BoF. The IETF agenda is still tentative, but we're currently >> scheduled for Thursday, July 23rd, 15:20-17:20, in Karlin I/II. (There is >> still a chance that will change, though, so please do not tailor travel to >> just that time frame!) >> >> Our charter lists draft-barnes-acme as a starting point, and Rich and I >> are asking the authors to produce an update for the meeting. We expect >> some of the working group time in Prague to be a document review/discussion >> of that draft. >> >> If you have other agenda items you'd like to request time for, please >> send them to the list. >> >> thanks, >> >> Ted and Rich >> > > > _______________________________________________ > Acme mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/acme > >
_______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
