RFC 7538 on The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)

rfc-editor@rfc-editor.org Mon, 06 April 2015 20:46 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA4FC1A9237 for <ietf-announce@ietfa.amsl.com>; Mon, 6 Apr 2015 13:46:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 Kmir9XsjgvS3 for <ietf-announce@ietfa.amsl.com>; Mon, 6 Apr 2015 13:46:35 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 2E4E21A916B for <ietf-announce@ietf.org>; Mon, 6 Apr 2015 13:46:18 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 36711180470; Mon, 6 Apr 2015 13:45:49 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7538 on The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150406204549.36711180470@rfc-editor.org>
Date: Mon, 06 Apr 2015 13:45:49 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/O9R9ICDDx83A-l4CMlGp_wX26gw>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 06 Apr 2015 20:46:40 -0000

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

        
        RFC 7538

        Title:      The Hypertext Transfer Protocol Status 
                    Code 308 (Permanent Redirect) 
        Author:     J. Reschke
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2015
        Mailbox:    julian.reschke@greenbytes.de
        Pages:      6
        Characters: 11189
        Obsoletes:  RFC 7238

        I-D Tag:    draft-ietf-httpbis-rfc7238bis-03.txt

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

This document specifies the additional Hypertext Transfer Protocol
(HTTP) status code 308 (Permanent Redirect).

This document is a product of the HyperText Transfer Protocol Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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/rfc.html

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