The application/timestamped-data Media Type
The registered media type for TimeStampedData envelopes, which bind a file to time-stamp tokens.
Santoni, A., "The application/timestamped-data Media Type", RFC 5955, DOI 10.17487/RFC5955, August 2010, <https://www.rfc-editor.org/info/rfc5955>.
@misc{rfc5955,
series = {Request for Comments},
number = 5955,
howpublished = {RFC 5955},
publisher = {RFC Editor},
doi = {10.17487/RFC5955},
url = {https://www.rfc-editor.org/info/rfc5955},
author = {A. Santoni},
title = {{The application/timestamped-data Media Type}},
pagetotal = 3,
year = 2010,
month = aug,
} RFC text
Contents
Internet Engineering Task Force (IETF) A. Santoni
Request for Comments: 5955 Actalis S.p.A.
Updates: 5544 August 2010
Category: Informational
ISSN: 2070-1721
The application/timestamped-data Media Type
Abstract
This document defines a new media type for TimeStampedData envelopes
as described in RFC 5544.
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 represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are 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/rfc5955.
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. 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...................................................2
2. Registration...................................................2
3. Security Considerations........................................3
4. IANA Considerations............................................3
5. Normative References...........................................3
1. Introduction
This document defines a new media type for TimeStampedData envelopes.
A TimeStampedData envelope, described in [RFC5544], binds a file with
one or more time-stamp tokens obtained for that file. A media type
registration, lacking in [RFC5544], enhances shareability.
2. Registration
Type name: application
Subtype name: timestamped-data
Required parameters: none
Optional parameters: none
Encoding considerations: binary
Security considerations:
See the Security Considerations in the published specification.
Interoperability considerations: none
Published specification: RFC 5544
Applications which use this media type:
Any application that exchanges TimeStampedData envelopes over a
MIME-based transport and possibly processes them, either directly
or via external handlers or viewers. Such applications may be,
for instance, digital signature applications, archival systems,
email clients, web browsers, etc.
Additional information:
Magic number(s):
File extension(s): .tsd
Macintosh file type code(s):
Person & email address to contact for further information:
Adriano Santoni
<adriano.santoni@actalis.it>
Intended usage: COMMON
Restrictions on usage: none
Author:
Adriano Santoni
<adriano.santoni@actalis.it>
Change controller: the IESG
3. Security Considerations
The security considerations of [RFC5544] apply; no new security
considerations are introduced by this document.
4. IANA Considerations
Section 2 of this document registers one media subtype.
5. Normative References
[RFC5544] Santoni, A., "Syntax for Binding Documents with Time-
Stamps", RFC 5544, February 2010.
Author's Address
Adriano Santoni
Actalis S.p.A.
Via dell'Aprica 18
20158 Milano
Italy
EMail: adriano.santoni@actalis.it
AI ELI5
On this page
§1Why a Media Type
A TimeStampedData envelope, described in RFC 5544, binds a file with one or more time-stamp tokens obtained for that file. RFC 5544 lacked a media type registration, and the RFC says adding one enhances shareability. That is why RFC 5955 is marked as updating RFC 5544.
A time-stamped file is like a photo with a date stamp. This note adds the label that tells programs what kind of file it is.
§2The Registration
The type name is application and the subtype name is timestamped-data. There are no required or optional parameters, and the encoding is binary. The file extension is .tsd. The published specification is RFC 5544, the intended usage is COMMON, and the change controller is the IESG.
The RFC lists applications such as digital signature applications, archival systems, email clients and web browsers as ones that may exchange these envelopes.
The label says: this is a binary file ending in .tsd, and many kinds of programs may handle it.
§3Security Considerations
The security considerations of RFC 5544 apply, and this document introduces no new ones. Section 2 of the document registers a single media subtype with IANA.
Adding a label does not change how safe the file is, so the old safety rules still apply.