Verifying Resource Records Without Knowing Their Contents
draft-ietf-dnsind-verify-00
| Document | Type | Expired Internet-Draft (dnsind WG) | |
|---|---|---|---|
| Author | Mark P. Andrews | ||
| Last updated | 1999-02-17 | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| 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-ietf-dnsind-verify-00.txt
https://www.ietf.org/archive/id/draft-ietf-dnsind-verify-00.txt
Abstract
DNSSEC [RFC2065] provides a mechanism to cryptographically verify a DNS resource record provided we can get it into canonical form. The problem is how do we do this without knowing the contents of all resource record types? This document provides one possible solution to this problem.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)