RFC 9018: Interoperable Domain Name System (DNS) Server Cookies
In plain English — editorial summary, not part of the RFC
DNS Cookies, as specified in RFC 7873, are a lightweight DNS transaction security mechanism that provide limited protection to DNS servers and clients against a variety of denial-of-service amplification, forgery, or cache-poisoning attacks by off-path attackers. This document updates RFC 7873 with precise directions for creating Server Cookies so that an anycast server set including diverse implementations will interoperate with standard clients, with suggestions for constructing Client Cookies in a privacy-preserving fashion, and with suggestions on how to update a Server Secret. An IANA registry listing the methods and associated pseudorandom function suitable for creating DNS Server Cookies has been created with the method described in this document as the first and, as of the time of publication, only entry.
Document record
- Document ID
- RFC9018
- Published
- April 2021
- Authors
- O. Sury; W. Toorop; D. Eastlake 3rd; M. Andrews
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 16
- Also known as
- —
- Updates:
- RFC 7873
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8976Message Digest for DNS ZonesCurrent
February 2021
- RFC 9506Explicit Host-to-Network Flow Measurements TechniquesCurrent
October 2023
- RFC 6790The Use of Entropy Labels in MPLS ForwardingUpdated
November 2012
- RFC 6750The OAuth 2.0 Authorization Framework: Bearer Token UsageUpdated
October 2012
- RFC 6749The OAuth 2.0 Authorization FrameworkUpdated
October 2012
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 6283Extensible Markup Language Evidence Record Syntax (XMLERS)Current
July 2011
- RFC 5854The Metalink Download Description FormatCurrent
June 2010
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?