this document may of interest to PKIX members

[Stephen Kent <[e-mail]>]

>
>
>The IESG has no problem with the publication of 'Syntax for binding
>documents with time stamps' <draft-santoni-timestampeddata-04.txt> as an
>Informational RFC.
>
>The IESG would also like the IRSG or RFC-Editor to review the comments in
>
>the datatracker
>(https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=16302&rfc_flag=0)
>related to this document and determine whether or not they merit
>incorporation into the document. Comments may exist in both the ballot
>and the comment log.
>
>The IESG contact person is Tim Polk.
>
>A URL of this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-santoni-timestampeddata-04.txt
>
>
>The process for such documents is described at
>http://www.rfc-editor.org/indsubs.html.
>
>Thank you,
>
>The IESG Secretary
>
>Technical Summary
>
>    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.
>
>Working Group Summary
>
>   This document is not the product of any IETF WG.
>
>Protocol Quality
>
>   The documents were reviewed by Tim Polk for the IESG.  Carl Wallace
>   also reviewed the document for conflicts with the LTANS working group.
>
>RFC Editor Note
>
>   The IESG thinks that this work is related to IETF work done in the
>   Long-Term Archive and Notary Services (ltans) WG, but this does not
>   prevent publishing.
>
>IESG Note
>
>   This RFC is not a candidate for any level of Internet Standard.
>   The IETF disclaims any knowledge of the fitness of this RFC for
>   any purpose and notes that the decision to publish is not based on
>   IETF review apart from IESG review for conflict with IETF work.  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.
>   The RFC Editor has chosen to publish this document at its
>   discretion.  See RFC 3932 for more information.
>
>_______________________________________________
>IETF-Announce mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/ietf-announce