Signaling Cryptographic Algorithm Understanding in DNSSEC
draft-crocker-dnssec-algo-signal-07
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Steve Crocker , Scott Rose | ||
| Last updated | 2010-10-08 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
html
xml
htmlized
pdfized
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) | ||
https://www.ietf.org/archive/id/draft-crocker-dnssec-algo-signal-07.txt
Abstract
The DNS Security Extensions (DNSSEC) were developed to provide origin authentication and integrity protection for DNS data by using digital signatures. These digital signatures can be generated using different algorithms. This draft sets out to specify a way for validating end-system resolvers to signal to a server which cryptographic algorithms they support.
Authors
Steve Crocker
(steve@shinkuro.com)
Scott Rose
(scottr.nist@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)