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

Document Type Active Internet-Draft (individual in art area)
Last updated 2017-11-13
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state AD is watching
Consensus Boilerplate Unknown
Telechat date
Responsible AD Alexey Melnikov
Send notices to (None)
Network Working Group                                      M. Nottingham
Internet-Draft                                         November 13, 2017
Obsoletes: 5785 (if approved)
Intended status: Standards Track
Expires: May 17, 2018

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

Abstract

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

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/5785bis .

   The most recent (often, unpublished) draft is at
   https://mnot.github.io/I-D/5785bis/ .

   Recent changes are listed at https://github.com/mnot/I-D/commits/gh-
   pages/5785bis .

   See also the draft's current status in the IETF datatracker, at
   https://datatracker.ietf.org/doc/draft-nottingham-5785bis/ .

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 http://datatracker.ietf.org/drafts/current/.

   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."

Nottingham                Expires May 17, 2018                  [Page 1]
Internet-Draft          Defining Well-Known URIs           November 2017

   This Internet-Draft will expire on May 17, 2018.

Copyright Notice

   Copyright (c) 2017 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
   (http://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
     1.1.  Appropriate Use of Well-Known URIs  . . . . . . . . . . .   3
   2.  Notational Conventions  . . . . . . . . . . . . . . . . . . .   3
   3.  Well-Known URIs . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  The Well-Known URI Registry . . . . . . . . . . . . . . .   5
       5.1.1.  Registration Template . . . . . . . . . . . . . . . .   5
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Appendix A.  Frequently Asked Questions . . . . . . . . . . . . .   6
   Appendix B.  Changes from RFC5785 . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Some applications on the Web require the discovery of policy or other
   information about an origin [RFC6454] (sometimes called "site-wide
   metadata") before making a request.  For example, the Robots
   Exclusion Protocol (http://www.robotstxt.org/ ) specifies a way for
   automated processes to obtain permission to access resources;
   likewise, the Platform for Privacy Preferences [W3C.REC-P3P-20020416]
   tells user-agents how to discover privacy policy before interacting
   with a site.

   While there are several ways to access per-resource metadata (e.g.,
   HTTP headers, WebDAV's PROPFIND [RFC4918]), the perceived overhead
   (either in terms of client-perceived latency and/or deployment

Nottingham                Expires May 17, 2018                  [Page 2]
Internet-Draft          Defining Well-Known URIs           November 2017

   difficulties) associated with them often precludes their use in these
   scenarios.

   When this happens, one solution is designating a "well-known
   location" for data or services related to the origin, so that it can
Show full document text