Well-Known Uniform Resource Identifiers (URIs)
draft-nottingham-rfc5785bis-09

Document Type Active Internet-Draft (individual in art area)
Last updated 2019-02-25
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state (None)
Document shepherd Martin Thomson
Shepherd write-up Show (last changed 2018-09-05)
IESG IESG state IESG Evaluation::AD Followup
Consensus Boilerplate Yes
Telechat date
Has a DISCUSS. Has enough positions to pass once DISCUSS positions are resolved.
Responsible AD Alexey Melnikov
Send notices to Martin Thomson <martin.thomson@gmail.com>
IANA IANA review state Version Changed - Review Needed
IANA action state None
Network Working Group                                      M. Nottingham
Internet-Draft                                         February 26, 2019
Obsoletes: 5785, 8307 (if approved)
Updates: 7230, 6455 (if approved)
Intended status: Standards Track
Expires: August 30, 2019

             Well-Known Uniform Resource Identifiers (URIs)
                     draft-nottingham-rfc5785bis-09

Abstract

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

   In doing so, it obsoletes RFC 5785 and RFC 8307, and updates the URI
   schemes defined in RFC 7230 and RFC 6455 to reserve that space.

Note to Readers

   _RFC EDITOR: please remove this section before publication_

   This draft is a proposed revision of RFC5875.

   The issues list for this draft can be found at
   https://github.com/mnot/I-D/labels/rfc5785bis [1].

   The most recent (often, unpublished) draft is at
   https://mnot.github.io/I-D/rfc5785bis/ [2].

   Recent changes are listed at https://github.com/mnot/I-D/commits/gh-
   pages/rfc5785bis [3].

   See also the draft's current status in the IETF datatracker, at
   https://datatracker.ietf.org/doc/draft-nottingham-rfc5785bis/ [4].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

Nottingham               Expires August 30, 2019                [Page 1]
Internet-Draft               Well-Known URIs               February 2019

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 30, 2019.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Notational Conventions  . . . . . . . . . . . . . . . . . . .   3
   3.  Well-Known URIs . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Registering Well-Known URIs . . . . . . . . . . . . . . .   5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
     4.1.  Interaction with Web Browsing . . . . . . . . . . . . . .   6
     4.2.  Scoping Applications  . . . . . . . . . . . . . . . . . .   7
     4.3.  Hidden Capabilities . . . . . . . . . . . . . . . . . . .   8
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  The Well-Known URI Registry . . . . . . . . . . . . . . .   8
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   9
     6.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .  10
   Appendix A.  Frequently Asked Questions . . . . . . . . . . . . .  11
   Appendix B.  Changes from RFC5785 . . . . . . . . . . . . . . . .  11
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Some applications on the Web require the discovery of information
   about an origin [RFC6454] (sometimes called "site-wide metadata")
   before making a request.  For example, the Robots Exclusion Protocol
   (http://www.robotstxt.org/ [5]) specifies a way for automated

Nottingham               Expires August 30, 2019                [Page 2]
Internet-Draft               Well-Known URIs               February 2019

   processes to obtain permission to access resources; likewise, the
   Platform for Privacy Preferences [P3P] tells user-agents how to
   discover privacy policy before interacting with an origin server.

   While there are several ways to access per-resource metadata (e.g.,
   HTTP header fields, WebDAV's PROPFIND [RFC4918]), the perceived
   overhead (either in terms of client-perceived latency and/or
   deployment difficulties) associated with them often precludes their
Show full document text