The 'leaptofrogans' URI Scheme
RFC 8589

Document Type RFC - Informational (May 2019; No errata)
Was draft-op3ft-leaptofrogans-uri-scheme (individual in art area)
Last updated 2019-05-21
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state (None)
Document shepherd Peter Saint-Andre
Shepherd write-up Show (last changed 2018-10-14)
IESG IESG state RFC 8589 (Informational)
Consensus Boilerplate No
Telechat date
Responsible AD Alexey Melnikov
Send notices to (None)
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                          A. Tamas
Request for Comments: 8589                               B. Phister, Ed.
Category: Informational                                   J-E. Rodriguez
ISSN: 2070-1721                                                    OP3FT
                                                                May 2019

                     The 'leaptofrogans' URI Scheme

Abstract

   This document describes the 'leaptofrogans' Uniform Resource
   Identifier (URI) scheme, which enables applications to launch Frogans
   Player on a given Frogans site.  Frogans is a medium for publishing
   content and services on the Internet, defined as a generic software
   layer on the Internet.  Frogans Player is software that enables end
   users to browse Frogans sites.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It has been approved for publication by the Internet
   Engineering Steering Group (IESG).  Not all documents approved by the
   IESG are candidates for any level of Internet Standard; see Section 2
   of RFC 7841.

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

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.

Tamas, et al.                 Informational                     [Page 1]
RFC 8589                leaptofrogans URI Scheme                May 2019

Table of Contents

   1.  Background Information  . . . . . . . . . . . . . . . . . . .   2
     1.1.  About Frogans . . . . . . . . . . . . . . . . . . . . . .   2
     1.2.  About the OP3FT . . . . . . . . . . . . . . . . . . . . .   3
   2.  The Need for a New URI Scheme and Its Purpose . . . . . . . .   3
   3.  Choice of the Scheme Name . . . . . . . . . . . . . . . . . .   4
   4.  Scheme Syntax . . . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  URI Scheme  . . . . . . . . . . . . . . . . . . . . . . .   5
     4.2.  IRI Usage and Encoding  . . . . . . . . . . . . . . . . .   6
   5.  Trademarks  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Background Information

1.1.  About Frogans

   Frogans is a medium for publishing content and services on the
   Internet.  From its inception in 1999, the medium was designed as a
   generic software layer running on top of the original Internet
   infrastructure (i.e., the TCP and IP protocols and the Domain Name
   System (DNS)), alongside other existing layers such as E-mail or the
   World Wide Web.

   As a medium, Frogans is not meant for publishing Web sites, but
   Frogans sites, a kind of site founded upon a different format,
   enabling a different kind of communication between end users and
   publishers of content and services.

   Frogans is intended to be complementary to the World Wide Web; it is
   not intended to be a replacement.  This is analogous to instant
   messaging, which was not intended to and did not replace E-mail.

   Compared to the World Wide Web, Frogans suggests publishing content
   and services that involve visual rather than text-based
   communication, focused content rather than long pages, and natural
   interaction rather than complex user interfaces.  For further
   information on the reasons for introducing Frogans on the Internet,
   and for an in-depth discussion of the similarities and differences
   between Frogans sites and Web sites, see [FSDL], Section 1.4
   ("Frogans sites and Web sites").

Tamas, et al.                 Informational                     [Page 2]
RFC 8589                leaptofrogans URI Scheme                May 2019

   The technology making up the medium, i.e., the Frogans technology,
   includes multiple components such as:
Show full document text