Algorithm Implementation Requirements and Usage Guidance for DNSSEC
draft-wouters-sury-dnsop-algorithm-update-01

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2016-09-22 (latest revision 2016-03-21)
Replaced by rfc8624, draft-ietf-dnsop-algorithm-update
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-wouters-sury-dnsop-algorithm-update-01.txt

Abstract

The DNSSEC protocol makes use of various cryptographic algorithms in order to provide authentication of DNS data and proof of non- existence. To ensure interoperability between DNS resolvers and DNS authoritative servers, it is necessary to specify a set of algorithm implementation requirements and usage guidance to ensure that there is at least one algorithm that all implementations support. This document defines the current algorithm implementation requirements and usage guidance for DNSSEC. This document obsoletes RFC-6944.

Authors

Paul Wouters (pwouters@redhat.com)
Ondřej Surý (ondrej.sury@nic.cz)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)