Mathematical Mesh 3.0 Part II: Uniform Data Fingerprint.
draft-hallambaker-mesh-udf-06

Document Type Active Internet-Draft (individual)
Last updated 2019-09-23 (latest revision 2019-08-15)
Replaces draft-hallambaker-udf
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                    P. Hallam-Baker
Internet-Draft                                           August 15, 2019
Intended status: Informational
Expires: February 16, 2020

        Mathematical Mesh 3.0 Part II: Uniform Data Fingerprint.
                     draft-hallambaker-mesh-udf-06

Abstract

   This document describes the naming and addressing schemes used in the
   Mathematical Mesh.  The means of generating Uniform Data Fingerprint
   (UDF) values and their presentation as text sequences and as URIs are
   described.

   A UDF consists of a binary sequence, the initial eight bits of which
   specify a type identifier code.  Type identifier codes have been
   selected so as to provide a useful mnemonic indicating their purpose
   when presented in Base32 encoding.

   Two categories of UDF are described.  Data UDFs provide a compact
   presentation of a fixed length binary data value in a format that is
   convenient for data entry.  A Data UDF may represent a cryptographic
   key, a nonce value or a share of a secret.  Fingerprint UDFs provide
   a compact presentation of a Message Digest or Message Authentication
   Code value.

   A Strong Internet Name (SIN) consists of a DNS name which contains at
   least one label that is a UDF fingerprint of a policy document
   controlling interpretation of the name.  SINs allow a direct trust
   model to be applied to achieve end-to-end security in existing
   Internet applications without the need for trusted third parties.

   UDFs may be presented as URIs to form either names or locators for
   use with the UDF location service.  An Encrypted Authenticated
   Resource Locator (EARL) is a UDF locator URI presenting a service
   from which an encrypted resource may be obtained and a symmetric key
   that may be used to decrypt the content.  EARLs may be presented on
   paper correspondence as a QR code to securely provide a machine-
   readable version of the same content.  This may be applied to
   automate processes such as invoicing or to provide accessibility
   services for the partially sighted.

   [Note to Readers]

Hallam-Baker            Expires February 16, 2020               [Page 1]
Internet-Draft                  Mesh UDF                     August 2019

   Discussion of this draft takes place on the MATHMESH mailing list
   (mathmesh@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/search/?email_list=mathmesh.

   This document is also available online at
   http://mathmesh.com/Documents/draft-hallambaker-mesh-udf.html [1] .

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

   This Internet-Draft will expire on February 16, 2020.

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  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.1.  UDF Types . . . . . . . . . . . . . . . . . . . . . . . .   5
       1.1.1.  Cryptographic Keys and Nonces . . . . . . . . . . . .   5
       1.1.2.  Fingerprint type UDFS . . . . . . . . . . . . . . . .   6
     1.2.  UDF URIs  . . . . . . . . . . . . . . . . . . . . . . . .   7
       1.2.1.  Name Form . . . . . . . . . . . . . . . . . . . . . .   7
       1.2.2.  Locator Form  . . . . . . . . . . . . . . . . . . . .   7

Hallam-Baker            Expires February 16, 2020               [Page 2]
Internet-Draft                  Mesh UDF                     August 2019

     1.3.  Secure Internet Names . . . . . . . . . . . . . . . . . .   9
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .  10
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .  10
     2.2.  Defined Terms . . . . . . . . . . . . . . . . . . . . . .  10
     2.3.  Related Specifications  . . . . . . . . . . . . . . . . .  11
Show full document text