Responsibility for Authoritative DNSSEC Mistakes
draft-livingood-dnsop-auth-dnssec-mistakes-03
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Author | Jason Livingood | ||
| Last updated | 2016-05-05 (Latest revision 2015-11-02) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
DNS Security Extensions (DNSSEC) is now entering widespread deployment. However, domain signing tools and processes are not yet as mature and reliable as is the case for non-DNSSEC-related domain administration tools and processes. Authoritative DNS operators should focus on improving these processes and establishing a high level of quality in their work.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)