Syntax for Binding Documents with Time-Stamps
draft-santoni-timestampeddata-06

[Ballot comment]
Does this commit the IETF to some kind of maintenance for this non-IETF document?

        Additional types of evidence may be used after having registered them
        (and having had a distinguishing tag assigned to them) with the IETF.
        A suitable registration procedure should be defined for that purpose.

Additionally, I don't know if IANA's concern is resolved.

[Ballot comment]
One observation that might be an issue if this went through IETF review:

The "PrintableString" ASN.1 type doesn't permit all the characters that are permitted in a MIME media type.  Of the US-ASCII set, only space, ctrls, and MIME tspecials are disallowed in a MIME media type.  We have registered media types that use "_", which I don't think is permitted in PrintableString.  You might want the ASN.1 type for mimeType to be IA5String.  Also, what about media type parameters?

IANA Evaluation question/comment:

IANA does not maintain the rsadsi/pkcs/pkcs9 numbers arc registry.
What action (if any) should IANA perform?

We believe this document contains no actions for IANA, but we need
confirmation.

[Ballot discuss]
This is discuss-discuss, i.e., a question that I'd like the IESG to discuss before I move to a no-ob.

Can someone more clueful in this space illuminate how this documents intersects with RFC4998 coming out of LTANS? There seems to be some overlap between the two documents.

This RFC-to-be was submitted to the RFC Editor to be published as
Informational: draft-santoni-timestampeddata-04.txt.

Please let us know if this document conflicts with the IETF standards
process or other work being done in the IETF community.

Syntax for binding documents with time stamps

This document describes a syntax which can be used to bind a generic
document (or any set of data, not necessarily protected by means of
cryptographic techniques) to one or more time-stamp tokens obtained
for that document, where "time-stamp token" has the meaning defined
in RFC 3161. Additional types of temporal evidence are also
supported.

This document proposes a simple syntax based on the Cryptographic
Message Syntax (RFC 3852).

Four week timeout expires on 9 July 2008.


Sincerely,

Sandy Ginoza - USC/ISI
Request for Comments Documents