We will start with serving signed <code>debian.net</code> and
<code>debian.com</code> zones. Assuming nobody complains loudly enough
-the various reverse zones and finally the <code>debian.org</code> will
+the various reverse zones and finally the <code>debian.org</code> zone will
follow. Once all our zones are signed we will publish our trust anchors
in [ISC's DLV Registry](https://www.isc.org/solutions/dlv), again in
stages.
[debian-infrastructure-announce](http://lists.debian.org/debian-infrastructure-announce/)
list until such time that our zones are reachable from a
[signed root](http://www.root-dnssec.org/). KSK rollovers for our own
-child zones (www.d.o et al), once signed, will not be announced because
+child zones (www.d.o et al.), once signed, will not be announced because
we can just put proper
[DS records](http://en.wikipedia.org/wiki/List_of_DNS_record_types#DS)
in the respective parent zone.
Until we announce the first set of trust anchors on the mailinglist the
-keysets present in DNS should not be considered productional. They can
-be changed at any time.
+keysets present in DNS should be considered experimental. They can
+be changed at any time, without observing standard rollover practices.
+
+Please direct questions or comments to either the debian-admin or, if
+you want a more public forum, the debian-project list at
+lists.debian.org.
See also:
* [DNSSEC wikipedia page](http://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions),
* [DNSSEC HOWTO, a tutorial in disguise (Olaf Kolkman, nlnetlabs)](http://www.nlnetlabs.nl/publications/dnssec_howto/index.html).
-Please direct questions or comments to either the debian-admin or, if
-you want a more public forum, the debian-project list at
-lists.debian.org.
+-- Peter Palfrader