idnits 2.17.1 draft-ietf-smime-esformats-04.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3126 5 Title: Electronic Signature Formats for long term 6 electronic signatures 7 Author(s): D. Pinkas, J. Ross, N. Pope 8 Status: Informational 9 Date: September 2001 10 Mailbox: harri.rasilainen@etsi.fr, Denis.Pinkas @bull.net, 11 ross@secstan.com, pope@secstan.com 12 Pages: 84 13 Characters: 175886 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-smime-esformats-03.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3126.txt 20 This document defines the format of an electronic signature that can 21 remain valid over long periods. This includes evidence as to its 22 validity even if the signer or verifying party later attempts to deny 23 (i.e., repudiates the validity of the signature). 25 The format can be considered as an extension to RFC 2630 and RFC 2634, 26 where, when appropriate additional signed and unsigned attributes have 27 been defined. 29 The contents of this Informational RFC is technically equivalent to 30 ETSI TS 101 733 V.1.2.2. The ETSI TS is under the ETSI Copyright (C). 31 Individual copies of this ETSI deliverable can be downloaded from 32 http://www.etsi.org 34 This document is a product of the S/MIME Mail Security Working Group 35 of the IETF. 37 This memo provides information for the Internet community. It does 38 not specify an Internet standard of any kind. Distribution of this 39 memo is unlimited. 41 This announcement is sent to the IETF list and the RFC-DIST list. 42 Requests to be added to or deleted from the IETF distribution list 43 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 44 added to or deleted from the RFC-DIST distribution list should 45 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 47 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 48 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 49 help: ways_to_get_rfcs. For example: 51 To: rfc-info@RFC-EDITOR.ORG 52 Subject: getting rfcs 54 help: ways_to_get_rfcs 56 Requests for special distribution should be addressed to either the 57 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 58 specifically noted otherwise on the RFC itself, all RFCs are for 59 unlimited distribution.echo 60 Submissions for Requests for Comments should be sent to 61 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 62 Authors, for further information.