Uniform Data Fingerprint (UDF)
draft-hallambaker-udf-08

Document Type Active Internet-Draft (individual)
Last updated 2017-10-07
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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)
Network Working Group                                    P. Hallam-Baker
Internet-Draft                                         Comodo Group Inc.
Intended status: Informational                           October 8, 2017
Expires: April 11, 2018

                     Uniform Data Fingerprint (UDF)
                        draft-hallambaker-udf-08

Abstract

   This document describes means of generating Uniform Data Fingerprint
   (UDF) values and their presentation as text sequences and as URIs.
   Uses of UDF fingerprints include but are not limited to creating
   Strong Internet Names (SINs).

   Cryptographic digests provide a means of uniquely identifying static
   data without the need for a registration authority.  A fingerprint is
   a form of presenting a cryptographic digest that makes it suitable
   for use in applications where human readability is required.  The UDF
   fingerprint format improves over existing formats through the
   introduction of a compact algorithm identifier affording an
   intentionally limited choice of digest algorithm and the inclusion of
   an IANA registered MIME Content-Type identifier within the scope of
   the digest input to allow the use of a single fingerprint format in
   multiple application domains.

   Alternative means of rendering fingerprint values are considered
   including machine-readable codes, word and image lists.

   This document is also available online at
   http://prismproof.org/Documents/draft-hallambaker-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."

Hallam-Baker             Expires April 11, 2018                 [Page 1]
Internet-Draft       Uniform Data Fingerprint (UDF)         October 2017

   This Internet-Draft will expire on April 11, 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
   (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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Algorithm Identifier  . . . . . . . . . . . . . . . . . .   4
     1.2.  Content Type Identifier . . . . . . . . . . . . . . . . .   4
     1.3.  Representation  . . . . . . . . . . . . . . . . . . . . .   5
     1.4.  Truncation  . . . . . . . . . . . . . . . . . . . . . . .   5
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   5
     2.2.  Defined Terms . . . . . . . . . . . . . . . . . . . . . .   6
     2.3.  Related Specifications  . . . . . . . . . . . . . . . . .   7
     2.4.  Implementation Status . . . . . . . . . . . . . . . . . .   7
   3.  Encoding  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  Binary Fingerprint Value  . . . . . . . . . . . . . . . .   7
       3.1.1.  Version ID  . . . . . . . . . . . . . . . . . . . . .   8
     3.2.  Truncation  . . . . . . . . . . . . . . . . . . . . . . .   8
     3.3.  Base32 Representation . . . . . . . . . . . . . . . . . .   8
     3.4.  Example Encoding  . . . . . . . . . . . . . . . . . . . .   9
       3.4.1.  Using SHA-2-512 Digest  . . . . . . . . . . . . . . .   9
     3.5.  Fingerprint Improvement . . . . . . . . . . . . . . . . .  10
     3.6.  Compressed Presentation . . . . . . . . . . . . . . . . .  10
     3.7.  Example of Compressed Encoding. . . . . . . . . . . . . .  11
       3.7.1.  Example . . . . . . . . . . . . . . . . . . . . . . .  11
   4.  Content Types . . . . . . . . . . . . . . . . . . . . . . . .  11
     4.1.  PKIX Certificates and Keys  . . . . . . . . . . . . . . .  11
     4.2.  OpenPGP Key . . . . . . . . . . . . . . . . . . . . . . .  12
Show full document text