Currently our public documentation only touches on migration from an existing DNSSEC signer indirectly, the only guidance we give to users to get started is "Quick Start" which doesn't cover migration and has an unlinked "Migrating an existing DNSSEC signed zone" bullet under "Next Steps".
We do have more migration related documentation but it's hidden, and there's no high level guide page on the topic. By hidden I mean that it is not linked from the Cascade documentation. E.g. we have:
Documentation should cover import of keys with Cascade.
This initial version should not attempt to cover multi-signer scenarios.
Also, given that we have existing OpenDNSSEC users we should also cover the OpenDNSSEC migration case explicitly, i.e. include #311 as part of this work.
Currently our public documentation only touches on migration from an existing DNSSEC signer indirectly, the only guidance we give to users to get started is "Quick Start" which doesn't cover migration and has an unlinked "Migrating an existing DNSSEC signed zone" bullet under "Next Steps".
We do have more migration related documentation but it's hidden, and there's no high level guide page on the topic. By hidden I mean that it is not linked from the Cascade documentation. E.g. we have:
dnstdocs aren't linked at all because we hadn't moveddnst keysettodnstmainyet (but we have now) and the guidance it gives is generic, not Cascade specific.Documentation should cover import of keys with Cascade.
This initial version should not attempt to cover multi-signer scenarios.
Also, given that we have existing OpenDNSSEC users we should also cover the OpenDNSSEC migration case explicitly, i.e. include #311 as part of this work.