[rfc-i] Fwd: New Version Notification for draft-flanagan-rfc-preservation-03.txt

Heather Flanagan (RFC Series Editor) rse at rfc-editor.org
Wed Jan 14 16:27:15 PST 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

A revised digital preservation draft has been posted.

- From the draft change log:

7.1.  -02 to -03

   Life Cycle of Digital Preservation: modified language to be more
   clear as to when the archival process becomes more complex

   Recommendations: added that the final XML file should be one of the
   items retained in an archive


With this, the draft will be sent to to the IAB for consideration as an
IAB stream document and wind its way down the publishing path (see RFC
4845 for a review of the IAB stream publication process).

- -Heather Flanagan, RSE


- -------- Forwarded Message --------
Subject:     New Version Notification for
draft-flanagan-rfc-preservation-03.txt
Date:     Wed, 14 Jan 2015 16:24:05 -0800
From:     internet-drafts at ietf.org
To:     Heather Flanagan <rse at rfc-editor.org>, Heather Flanagan
<rse at rfc-editor.org>



A new version of I-D, draft-flanagan-rfc-preservation-03.txt
has been successfully submitted by Heather Flanagan and posted to the
IETF repository.

Name:        draft-flanagan-rfc-preservation
Revision:    03
Title:        Digital Preservation Considerations for the RFC Series
Document date:    2015-01-14
Group:        Individual Submission
Pages:        17
URL:           
http://www.ietf.org/internet-drafts/draft-flanagan-rfc-preservation-03.txt
Status:        
https://datatracker.ietf.org/doc/draft-flanagan-rfc-preservation/
Htmlized:      
http://tools.ietf.org/html/draft-flanagan-rfc-preservation-03
Diff:          
http://www.ietf.org/rfcdiff?url2=draft-flanagan-rfc-preservation-03

Abstract:
   The RFC Editor is both the publisher and the archivist for the RFC
   Series.  This document applies specifically to the archivist role of
   the RFC Editor.  It provides guidance on when and how to preserve
   RFCs, and the tools required to view or re-create RFCs as necessary.
   This document also highlights where gaps are in the current process,
   and where compromises are suggested to balance cost with ideal best
   practice.

                                                                                
 


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat



-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJUtwljAAoJEER/xjINbZoGP2wIAJ1H/NM40LsdQK1blPjtHEox
wca2yRCrWX4iJyDSwt/CzHE6ml6RowbdarqKlLKuk0lSJTiRbI+jH5XFV2Bp7zEv
579+VW9oAedhFyA3IgHiiglNHVpcIq/mVf7Yr4o7U9JcWia9D4RUpdrxDplYbuuV
KoXnJVm9uh1M5GRhuuwzAdNtrpnanop09T06X69Z4fddVS52wl1IbbvQw3Wv6qFc
DFLLNS0SxVIB/IkfPM8OBE5I1IiidREV2zXDrCjZjsHvJLYgYHHkq6YG/TxaY4Ma
S3roN7d/3t+3wEbxdHS0OamSXRgDyT4SdiyGZxzUz6ANNBz++W3qYBpEZmDg6Dk=
=f+r/
-----END PGP SIGNATURE-----

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.rfc-editor.org/pipermail/rfc-interest/attachments/20150114/6218c9ad/attachment.html>


More information about the rfc-interest mailing list