Browse Prior Art Database

Guidelines and Registration Procedures for URI Schemes (RFC7595)

IP.com Disclosure Number: IPCOM000242159D
Original Publication Date: 2015-Jun-01
Included in the Prior Art Database: 2015-Jun-20
Document File: 38 page(s) / 43K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Thaler: AUTHOR [+4]

Abstract

The Uniform Resource Identifier (URI) protocol element and generic syntax is defined by [RFC3986]. Each URI begins with a scheme name, as defined by Section 3.1 of RFC 3986, that refers to a specification for identifiers within that scheme. The URI syntax provides a federated and extensible naming system, where each scheme's specification can further restrict the syntax and define the semantics of identifiers using that scheme.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 6% of the total text.

Internet Engineering Task Force (IETF)                    D. Thaler, Ed. Request for Comments: 7595                                     Microsoft Obsoletes: 4395                                                T. Hansen BCP: 35                                                AT&T Laboratories Category: Best Current Practice                                T. Hardie ISSN: 2070-1721                                                   Google                                                                June 2015

          Guidelines and Registration Procedures for URI Schemes

Abstract

   This document updates the guidelines and recommendations, as well as    the IANA registration processes, for the definition of Uniform    Resource Identifier (URI) schemes.  It obsoletes RFC 4395.

Status of This Memo

   This memo documents an Internet Best Current Practice.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    BCPs is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7595.

Copyright Notice

   Copyright (c) 2015 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.

 Thaler, et al.            Best Current Practice                 [Page 1]
 RFC 7595                  URI Scheme Guidelines                June 2015

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2

     1.1.  URIs and IRIs . . . . . . . . . . . . . . . . . . . . . .   3

   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3

   3.  Requirements for Permanent Scheme Definitions . . . . . . . .   4

     3.1.  Demonstrable,...