Indirect KEY RRs in the Domain Name System (DNS)
draft-ietf-dnsind-indirect-key-00
| Document | Type |
Expired Internet-Draft
(dnsind WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Donald E. Eastlake 3rd | ||
| Last updated | 1999-04-29 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| 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 is available in these formats:
Abstract
[RFC 2535] defines a means for storing cryptographic public keys in the Domain Name System. An additional code point is defined for the algorithm field of the KEY resource record (RR) to indicate that the key is not stored in the KEY RR but is pointed to by the KEY RR. Encodings to indicate different types of key and pointer formats are specified. [This draft is moved from the DNSSEC WG as part of that WG's merger into me DNSIND WG. It would have been draft-ietf-dnssec-indirect- key-02.txt in the DNSSEC WG.]
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)