RFC 8153 on Digital Preservation Considerations for the RFC Series

rfc-editor@rfc-editor.org Thu, 20 April 2017 00:19 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C295412EAEC for <ietf-announce@ietfa.amsl.com>; Wed, 19 Apr 2017 17:19:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mfita0u155Xc for <ietf-announce@ietfa.amsl.com>; Wed, 19 Apr 2017 17:19:03 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C78DE12EAD7 for <ietf-announce@ietf.org>; Wed, 19 Apr 2017 17:18:35 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3D412B801CC; Wed, 19 Apr 2017 17:18:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8153 on Digital Preservation Considerations for the RFC Series
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Message-Id: <20170420001821.3D412B801CC@rfc-editor.org>
Date: Wed, 19 Apr 2017 17:18:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/h7ivKs_b9tUd4PD8CJasFBV_mMM>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 00:19:07 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8153

        Title:      Digital Preservation Considerations 
                    for the RFC Series 
        Author:     H. Flanagan
        Status:     Informational
        Stream:     IAB
        Date:       April 2017
        Mailbox:    rse@rfc-editor.org
        Pages:      18
        Characters: 40770
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-iab-rfc-preservation-04.txt

        URL:        https://www.rfc-editor.org/info/rfc8153

        DOI:        10.17487/RFC8153

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 describes the tools required to view or re-create RFCs as
necessary.  This document also highlights gaps in the current process
and suggests compromises to balance cost with best practice.

This document is a product of the Internet Architecture Board.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC