[Yeti DNS Discuss] Proposed Yeti KSK rollover communication plan
shane at biigroup.cn
Mon Aug 31 01:36:16 UTC 2015
On 2015-08-27 09:53:37+0800 (Thursday)
Shane Kerr <shane at biigroup.cn> wrote:
> On 2015-08-26 15:20:44+0200 (Wednesday)
> Stephane Bortzmeyer <bortzmeyer at nic.fr> wrote:
> > On Wed, Aug 26, 2015 at 03:18:37PM +0800,
> > Shane Kerr <shane at biigroup.cn> wrote
> > a message of 30 lines which said:
> > > It might help if I actually added a link to the proposal. :(
> > >
> > > https://github.com/shane-kerr/Yeti-Project/blob/yeti-ksk-communication-plan/doc/KSK-rollover-communication-plan.md
> > > Maintain a web page with all past and present KSK [...] Also include
> > > a history of changes to the web page itself.
> > Why not relying simply on git, since the key is there? Just a small
> > script pulling old and recent keys from git. Let's not reinvent the
> > VCS :-)
> I guess that's okay, although we need to add some documentation on how
> to view old keys (for example for someone who is interested in looking
> at this who may know about DNS but not about Git).
I updated the text to remove this. One thing missing from Git is any
kind of future schedule. Do we care about this?
I think that since we're announcing rolls on the discuss list that we
are probably okay. Nobody should be surprised.
> > > the front page of http://yeti-dns.org
> > https
> We don't have an TLS-secured version of the site now. We will look
> into this.
We now DO have a TLS-secured version of the site now. (Thanks to Paul
Vixie for helping get this set up.)
More information about the discuss