[Yeti DNS Discuss] Proposed Yeti KSK rollover communication plan

Shane Kerr shane at biigroup.cn
Thu Aug 27 01:53:37 UTC 2015

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).

Thursday morning rant: on an unrelated note, I hate that GitHub is
IPv4-only. It's bad enough that people have even created proxies. This
makes me wonder why GitHub cannot do this themselves?


> > 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



More information about the discuss mailing list