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

A new Request for Comments is now available in online RFC libraries.

        RFC 9460

        Title:      Service Binding and Parameter Specification 
                    via the DNS (SVCB and HTTPS 
                    Resource Records) 
        Author:     B. Schwartz,
                    M. Bishop,
                    E. Nygren
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2023
        Mailbox:    ietf@bemasc.net,
                    mbishop@evequefou.be,
                    erik+ietf@nygren.org
        Pages:      47
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dnsop-svcb-https-12.txt

        URL:        https://www.rfc-editor.org/info/rfc9460

        DOI:        10.17487/RFC9460

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.

This document is a product of the Domain Name System Operations Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC