RFC 9540: Discovery of Oblivious Services via Service Binding Records
In plain English — editorial summary, not part of the RFC
This document defines a parameter that can be included in Service Binding (SVCB) and HTTPS DNS resource records to denote that a service is accessible using Oblivious HTTP, by offering an Oblivious Gateway Resource through which to access the target. This document also defines a mechanism for learning the key configuration of the discovered Oblivious Gateway Resource.
Document record
- Document ID
- RFC9540
- Published
- February 2024
- Authors
- T. Pauly; T. Reddy.K
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9799Automated Certificate Management Environment (ACME) Extensions for ".onion" Special-Use Domain NamesCurrent
June 2025
- RFC 9848Bootstrapping TLS Encrypted ClientHello with DNS Service BindingsCurrent
March 2026
- RFC 8598Split DNS Configuration for the Internet Key Exchange Protocol Version 2 (IKEv2)Current
May 2019
- RFC 7585Dynamic Peer Discovery for RADIUS/TLS and RADIUS/DTLS Based on the Network Access Identifier (NAI)Current
October 2015
- RFC 6844DNS Certification Authority Authorization (CAA) Resource RecordObsoleted
January 2013
- RFC 2535Domain Name System Security ExtensionsObsoleted
March 1999
- RFC 2137Secure Domain Name System Dynamic UpdateObsoleted
April 1997
- RFC 2065Domain Name System Security ExtensionsObsoleted
January 1997
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?