RFC 8615: Well-Known Uniform Resource Identifiers (URIs)

This memo defines a path prefix for "well-known locations", "/.well-known/", in selected Uniform Resource Identifier (URI) schemes. In doing so, it obsoletes…

Read RFC 8615 on the RFC Editor

Outgoing relationships (3 related RFCs)

Updates — RFC 7230: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
Updates — RFC 7595: Guidelines and Registration Procedures for URI Schemes
Obsoletes — RFC 5785: Defining Well-Known Uniform Resource Identifiers (URIs)

Incoming relationships (14 related RFCs)

Normatively referenced by — RFC 9132: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
Normatively referenced by — RFC 8827: WebRTC Security Architecture
Normatively referenced by — RFC 9483: Lightweight Certificate Management Protocol (CMP) Profile
Normatively referenced by — RFC 8801: Discovering Provisioning Domain Names and Data
Normatively referenced by — RFC 9205: Building Protocols with HTTP
Normatively referenced by — RFC 9482: Constrained Application Protocol (CoAP) Transfer for the Certificate Management Protocol
Normatively referenced by — RFC 9811: Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP)
Normatively referenced by — RFC 9472: A YANG Data Model for Reporting Software Bills of Materials (SBOMs) and Vulnerability Information
Normatively referenced by — RFC 9511: Attribution of Internet Probes
Normatively referenced by — RFC 9540: Discovery of Oblivious Services via Service Binding Records
Normatively referenced by — RFC 9727: api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs
Normatively referenced by — RFC 9728: OAuth 2.0 Protected Resource Metadata
Informatively referenced by — RFC 9031: Constrained Join Protocol (CoJP) for 6TiSCH
Informatively referenced by — RFC 9820: Authentication Service Based on the Extensible Authentication Protocol (EAP) for Use with the Constrained Application Protocol (CoAP)