RFC 2230: Key Exchange Delegation Record for the DNS
In plain English — editorial summary, not part of the RFC
This note describes a mechanism whereby authorisation for one node to act as key exchanger for a second node is delegated and made available via the Secure DNS. This mechanism is intended to be used only with the Secure DNS. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2230
- Published
- November 1997
- Authors
- R. Atkinson
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1706DNS NSAP Resource RecordsUpdated
October 1994
- RFC 2541DNS Security Operational ConsiderationsObsoleted
March 1999
- RFC 2052A DNS RR for specifying the location of services (DNS SRV)Obsoleted
October 1996
- RFC 2517Building Directories from DNS: Experiences from WWWSeekerCurrent
February 1999
- RFC 1912Common DNS Operational and Configuration ErrorsCurrent
February 1996
- RFC 1637DNS NSAP Resource RecordsObsoleted
June 1994
- RFC 1538Advanced SNA/IP : A Simple SNA Transport ProtocolCurrent
October 1993
- RFC 1535A Security Problem and Proposed Correction With Widely Deployed DNS SoftwareCurrent
October 1993
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?