Digital Preservation Considerations for the RFC Series
draft-iab-rfc-preservation-03

Document Type Active Internet-Draft
Last updated 2017-01-25 (latest revision 2017-01-17)
Replaces draft-flanagan-rfc-preservation
Stream IAB
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Stream IAB state Community Review
Consensus Boilerplate Unknown
RFC Editor Note (None)
Network Working Group                                        H. Flanagan
Internet-Draft                                                RFC Editor
Intended status: Informational                          January 17, 2017
Expires: July 21, 2017

         Digital Preservation Considerations for the RFC Series
                     draft-iab-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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 21, 2017.

Copyright Notice

   Copyright (c) 2017 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

Flanagan                  Expires July 21, 2017                 [Page 1]
Internet-Draft            Digital Preservation              January 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Life Cycle of Digital Preservation  . . . . . . . . . . .   4
   2.  Updating Policy and Procedure . . . . . . . . . . . . . . . .   5
     2.1.  Acquisition of Documents  . . . . . . . . . . . . . . . .   6
     2.2.  Ingestion of Documents  . . . . . . . . . . . . . . . . .   6
     2.3.  Metadata and document registration  . . . . . . . . . . .   8
     2.4.  Normalization and standardization of canonical file
           structure and format  . . . . . . . . . . . . . . . . . .   9
       2.4.1.  'Best Effort' data retention  . . . . . . . . . . . .  10
       2.4.2.  Single format for archival purposes . . . . . . . . .  11
       2.4.3.  Holistic archiving of the computing environment . . .  12
     2.5.  Transformation/migration to current publication formats .  12
     2.6.  System Parameters . . . . . . . . . . . . . . . . . . . .  13
     2.7.  Financial Planning  . . . . . . . . . . . . . . . . . . .  13
   3.  Recommendations . . . . . . . . . . . . . . . . . . . . . . .  14
   4.  Summary . . . . . . . . . . . . . . . . . . . . . . . . . . .  15
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   7.  Informative References  . . . . . . . . . . . . . . . . . . .  16
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   The RFC Editor is both the publisher and the archivist for the RFC
   Series, a series of technical specifications and policy documents
   that includes foundational Internet standards [RFC6635] [RFCSERIES].
   As the publisher of these documents, the goal is to produce clear,
   consistent, and readable documents for the community using as many
   modern features, such as hyperlinks and content markup, within the
   document as necessary to convey the information the authors intended
   for their audience.  As the archivist, however, the main goal is to
   preserve both the information described and the documents themselves
   for the indefinite future.  To meet both of these goals, the RFC
   Editor must find the necessary balance between the publication needs
   of today and the archival needs of tomorrow, while acknowledging a
   finite set of resources to complete both aspects of the RFC Editor
Show full document text