Browse Prior Art Database

Syntax for Binding Documents with Time-Stamps (RFC5544)

IP.com Disclosure Number: IPCOM000193049D
Original Publication Date: 2010-Feb-01
Included in the Prior Art Database: 2010-Feb-09
Document File: 26 page(s) / 27K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Santoni: AUTHOR

Abstract

Time-stamping has become the standard technique for proving the existence of a document before a certain point in time. Several legislations around the world embrace the concept and provide for time-stamping services, mainly for the purpose of extending the validity of signed documents. However, while time-stamping enhances digital signatures, its value does not depend on them. It can clearly be useful to time-stamp a document even if it is not signed. And it can also be useful, or even mandatory in some cases, to time- stamp a signed document in its entirety, regardless of how many signatures it contains.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 10% of the total text.

Independent Submission                                        A. Santoni Request for Comments: 5544                                Actalis S.p.A. Category: Informational                                    February 2010 ISSN: 2070-1721

              Syntax for Binding Documents with Time-Stamps

Abstract

   This document describes an envelope that can be used to bind a file    (not necessarily protected by means of cryptographic techniques) with    one or more time-stamp tokens obtained for that file, where "time-    stamp token" has the meaning defined in RFC 3161 or its successors.    Additional types of temporal evidence are also allowed.

   The proposed envelope is based on the Cryptographic Message Syntax as    defined in RFC 5652.

Status of This Memo

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

   This is a contribution to the RFC Series, independently of any other    RFC stream.  The RFC Editor has chosen to publish this document at    its discretion and makes no statement about its value for    implementation or deployment.  Documents approved for publication by    the RFC Editor are not a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

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

IESG Note

   This RFC is not a candidate for any level of Internet Standard.  The    standards track specification RFC 4998, Evidence Record Syntax (ERS),    specifies an alternative mechanism.  Readers are encouraged to also    review RFC 4998 when evaluating the suitability of this mechanism.

 Santoni                       Informational                     [Page 1]
 RFC 5544                                                   February 2010

 Copyright Notice

   Copyright (c) 2010 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    (http: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.

Table of Contents

   1. Introduction ....................................................2

      1.1. Conventions Used in This Document ..........................3

   2. Syntax for TimeStampedData ......................................3

   3. Compliance Requirements ...........................................