Defined Resource Operator (drop) The 'drop' URI Scheme
draft-mcsweeney-drop-scheme-03

Document Type Active Internet-Draft (individual)
Author Tim McSweeney 
Last updated 2020-08-30
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force (IETF)                       T.McSweeney
Internet-Draft                               
Intended status: Informational                                                                                      
Expires: March 3,2021                                    August 30, 2020

                     draft-mcsweeney-drop-scheme-03
                     Defined Resource Operator (drop)     
                     The 'drop' URI Scheme
                     

Abstract

   This document describes the 'drop' Uniform Resource
   Identifier (URI) scheme.   

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

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

Copyright Notice

   Copyright (c) 2020 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.
        
   This document may not be modified, and derivative works of it may not
be created, except to format it for publication as an RFC or to
translate it into languages other than English.
 
Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Scheme Definitions . . . . . . . . . . . . . . . . . . . . .  2
     2.1.  Demonstrable, New, Long-Lived Utility  . . . . . . . . .  2  
     2.2.  Syntactic Compatibility . . . . . . . . . . . . . . . . . 2  
     2.3.  Definitions and Operations  . . . . .  . . . . . . . . . .3
     2.4.  Internationalization and Character Encoding . . . . . . . 3  
     2.5.  Interoperability Considerations . . . . . . . . . . . . . 4  
   3.  The drop URI Scheme Registration Request. . . . . . . . . . . 4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . 4
   6.  Normative References  . . . . . . . . . . . . . . . . . . . . 4  
   7.  Informative References. . . . . . . . . . . . . . . . . . . . 5  
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . . 5 
   Contributor . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . 5 

1.  Introduction

   This document is provided to inform the internet community of the
'drop' URI scheme and to meet the required guidelines of a permanent
URI scheme. This scheme shortens the path to further unifying
communications by using public mechanisms of continuity for the pre-
resolution of private and public service integration.

2.  Scheme definitions and syntax

2.1.  Demonstrable, New, Long-Lived Utility

   Phone numbers and physical addresses are antiquated but still very
useful. But what is to say that they both can not be represented by the
same character string?  For any given person or business, it is simpler
to enter a single string into one's phone than what is currently an ever
growing list of communication method identifiers.  When an owner is able
to update contact information it requires no changes by another user's
contact list or database.  People, businesses, and machines generally
have a wide variety of, and specific uses for, different modes of
communication.  Where those modes of communication overlap, there should
also be consolidation.  The 'drop' scheme was created in a way to be
able to reuse current infrastructure making it easy to use and quick to
deploy.

2.2.  Syntactic Compatibility
 
   "While it is common for schemes to further delegate their
   substructure to the URI's owner, publishing independent standards
   that mandate particular forms of URI substructure is inappropriate,
   because that essentially usurps ownership.  [RFC7320] abstract

nonetheless....

   "The URI syntax defines a grammar that is a superset of all
   valid URIs, allowing an implementation to parse the common components
Show full document text