Distributed Ledger Time-Stamp
draft-intesigroup-dlts-00

Document Type Active Internet-Draft (individual)
Authors Emanuele Cisbani  , Daniele Ribaudo  , Giuseppe Damiano 
Last updated 2020-07-07
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
Network Working Group                                         E. Cisbani
Internet-Draft                                                D. Ribaudo
Updates: 3161 (if approved)                                   G. Damiano
Intended status: Standards Track                            Intesi Group
Expires: January 8, 2021                                    July 7, 2020

                     Distributed Ledger Time-Stamp
                       draft-intesigroup-dlts-00

Abstract

   This document defines a standard to extend Time Stamp Tokens with
   Time Attestations recorded on Distributed Ledgers.

   The aim is to provide long-term validity to Time Stamp Tokens,
   backward compatible with currently available software.

   This document update RFC 3161 [RFC3161].

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 January 8, 2021.

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

Cisbani, et al.          Expires January 8, 2021                [Page 1]
Internet-Draft                    dlts                         July 2020

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terms and Definitions . . . . . . . . . . . . . . . . . . . .   3
   3.  Symbols And Abbreviations . . . . . . . . . . . . . . . . . .   5
   4.  DL Attestation  . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  DL Time-Stamp Objects . . . . . . . . . . . . . . . . . . . .   6
     5.1.  DL Time-Stamp Attributes  . . . . . . . . . . . . . . . .   7
       5.1.1.  Response Status . . . . . . . . . . . . . . . . . . .   8
     5.2.  DL Time-Stamp Extensions  . . . . . . . . . . . . . . . .   8
     5.3.  Response Status . . . . . . . . . . . . . . . . . . . . .   9
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   Attesting that a file existed prior to a specific point in time can
   be useful - for example - to:

   o  prove when an agreement was signed, if it is disputed

   o  validate a signature after a revocation occurred

   o  prove the ownership for copyright

   o  grant record integrity

   A Time-Stamp Token (TST) provided by a Time-Stamp Authority (TSA)
   compliant with RFC 3161 [RFC3161] can be based on an accurate time
   source linked to Coordinated Universal Time, and can be very precise
   - it can prove the existence also at the second or less.  It is such
   a consolidated standard that - for example - the European Union
   legally enforced its usage by eIDAS Regulation [eIDAS], European
   Standards and Technical Specifications [ETSI.EN.319.422]
   [ETSI.TS.101.861].

   In an in-deep appraisal of Time Stamping Schemes conducted in 2001 by
   Masashi Une [IMES], PKI TSA was evaluated as one of the most
   desirables in term of security against alteration of a time stamp.

Cisbani, et al.          Expires January 8, 2021                [Page 2]
Internet-Draft                    dlts                         July 2020

   The integrity of the timestamping process that is inevitably bound to
   the integrity of the TSA gave rise to other proposals like ANSI X9.95
   [ANSI.X9.95] and ISO/IEC 18014-4 [ISO.IEC.18014-4].

   Furthermore a TSA TST can be validated for a limited time - usually
   no longer than 20 years for technical reasons such as the TSA
   certificates expiration, or for economic reasons such as the cost of
Show full document text