RFC 8490: DNS Stateful Operations
In plain English — editorial summary, not part of the RFC
This document defines a new DNS OPCODE for DNS Stateful Operations (DSO). DSO messages communicate operations within persistent stateful sessions using Type Length Value (TLV) syntax. Three TLVs are defined that manage session timeouts, termination, and encryption padding, and a framework is defined for extensions to enable new stateful operations. This document updates RFC 1035 by adding a new DNS header OPCODE that has both different message semantics and a new result code. This document updates RFC 7766 by redefining a session, providing new guidance on connection reuse, and providing a new mechanism for handling session idle timeouts.
Document record
- Document ID
- RFC8490
- Published
- March 2019
- Authors
- R. Bellis; S. Cheshire; J. Dickinson; S. Dickinson; T. Lemon; T. Pusateri
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 64
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8488RIPE NCC's Implementation of Resource Public Key Infrastructure (RPKI) Certificate Tree ValidationCurrent
December 2018
- RFC 8487Mtrace Version 2: Traceroute Facility for IP MulticastCurrent
October 2018
- RFC 8495Allocation Token Extension for the Extensible Provisioning Protocol (EPP)Current
November 2018
- RFC 8482Providing Minimal-Sized Responses to DNS Queries That Have QTYPE=ANYCurrent
January 2019
- RFC 8499DNS TerminologyObsoleted
January 2019
- RFC 8481Clarifications to BGP Origin Validation Based on Resource Public Key Infrastructure (RPKI)Updated
September 2018
- RFC 8501Reverse DNS in IPv6 for Internet Service ProvidersCurrent
November 2018
- RFC 8475Using Conditional Router Advertisements for Enterprise MultihomingCurrent
October 2018
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?