RFC 7805 on Moving Outdated TCP Extensions and TCP-Related Documents to Historic or Informational Status
rfc-editor@rfc-editor.org Fri, 08 April 2016 00:49 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 3D2E712D0E9; Thu, 7 Apr 2016 17:49:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 Xg5Y-mvRAC5Y; Thu, 7 Apr 2016 17:49:36 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B95412D0BA; Thu, 7 Apr 2016 17:49:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B40C3180013; Thu, 7 Apr 2016 17:48:38 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7805 on Moving Outdated TCP Extensions and TCP-Related Documents to Historic or Informational Status
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160408004838.B40C3180013@rfc-editor.org>
Date: Thu, 07 Apr 2016 17:48:38 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/gYH3n7cVRWKoClhVz48N3c3e4oU>
Cc: drafts-update-ref@iana.org, tcpm@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: Fri, 08 Apr 2016 00:49:38 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7805
Title: Moving Outdated TCP Extensions and
TCP-Related Documents to Historic or
Informational Status
Author: A. Zimmermann, W. Eddy, L. Eggert
Status: Informational
Stream: IETF
Date: April 2016
Mailbox: alexander@zimmermann.eu.com,
wes@mti-systems.com,
lars@netapp.com
Pages: 8
Characters: 15754
Obsoletes: RFC 675, RFC 721, RFC 761, RFC 813, RFC 816,
RFC 879, RFC 896, RFC 1078, RFC 6013
Updates: RFC 7414
I-D Tag: draft-ietf-tcpm-undeployed-03.txt
URL: https://www.rfc-editor.org/info/rfc7805
DOI: http://dx.doi.org/10.17487/RFC7805
This document reclassifies several TCP extensions and TCP-related
documents that either have been superseded, have never seen
widespread use, or are no longer recommended for use to "Historic"
status. The affected documents are RFCs 675, 721, 761, 813, 816,
879, 896, 1078, and 6013. Additionally, this document reclassifies
RFCs 700, 794, 814, 817, 872, 889, 964, and 1071 to "Informational"
status.
This document is a product of the TCP Maintenance and Minor Extensions Working Group of the IETF.
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