Skip to main content

Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
RFC 9460

Revision differences

Document history

Date By Action
2024-04-16
(System) Received changes through RFC Editor sync (removed Errata tag (all errata rejected))
2024-03-26
(System) Received changes through RFC Editor sync (added Errata tag)
2023-11-07
(System) IANA registries were updated to include RFC9460
2023-11-06
(System)
Received changes through RFC Editor sync (created alias RFC 9460, changed title to 'Service Binding and Parameter Specification via the DNS (SVCB and HTTPS …
Received changes through RFC Editor sync (created alias RFC 9460, changed title to 'Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)', changed abstract to 'This document specifies the "SVCB" ("Service Binding") and "HTTPS" DNS resource record (RR) types to facilitate the lookup of information needed to make connections to network services, such as for HTTP origins.  SVCB records allow a service to be provided from multiple alternative endpoints, each with associated parameters (such as transport protocol configuration), and are extensible to support future uses (such as keys for encrypting the TLS ClientHello).  They also enable aliasing of apex domains, which is not possible with CNAME.  The HTTPS RR is a variation of SVCB for use with HTTP (see RFC 9110, "HTTP Semantics").  By providing more information to the client before it attempts to establish a connection, these records offer potential benefits to both performance and privacy.', changed pages to 47, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2023-11-06, changed IESG state to RFC Published)
2023-11-06
(System) RFC published