RFC 2930: Secret Key Establishment for DNS (TKEY RR)
In plain English — editorial summary, not part of the RFC
This document describes a Transaction Key (TKEY) RR that can be used in a number of different modes to establish shared secret keys between a DNS resolver and server. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2930
- Published
- September 2000
- Authors
- D. Eastlake 3rd
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 16
- Also known as
- —
- Updated by:
- RFC 6895
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3123A DNS RR Type for Lists of Address Prefixes (APL RR)Current
June 2001
- RFC 3597Handling of Unknown DNS Resource Record (RR) TypesUpdated
September 2003
- RFC 3402Dynamic Delegation Discovery System (DDDS) Part Two: The AlgorithmCurrent
October 2002
- RFC 3403Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) DatabaseCurrent
October 2002
- RFC 3404Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI)Current
October 2002
- RFC 2931DNS Request and Transaction Signatures ( SIG(0)s )Current
September 2000
- RFC 2874DNS Extensions to Support IPv6 Address Aggregation and RenumberingUpdated
July 2000
- RFC 2782A DNS RR for specifying the location of services (DNS SRV)Updated
February 2000
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?