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

Mark Nottingham <mnot@mnot.net> Tue, 07 April 2015 01:42 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9471F1B2CBA for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 6 Apr 2015 18:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.912
X-Spam-Level:
X-Spam-Status: No, score=-6.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] 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 DINd6sMpPgqd for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 6 Apr 2015 18:42:09 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71FE81B2CB7 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 6 Apr 2015 18:42:09 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1YfISA-0000l3-UT for ietf-http-wg-dist@listhub.w3.org; Tue, 07 Apr 2015 01:37:22 +0000
Resent-Date: Tue, 07 Apr 2015 01:37:22 +0000
Resent-Message-Id: <E1YfISA-0000l3-UT@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.80) (envelope-from <mnot@mnot.net>) id 1YfIS6-0000jt-3P for ietf-http-wg@listhub.w3.org; Tue, 07 Apr 2015 01:37:18 +0000
Received: from mxout-07.mxes.net ([216.86.168.182]) by lisa.w3.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from <mnot@mnot.net>) id 1YfIS3-00073H-U1 for ietf-http-wg@w3.org; Tue, 07 Apr 2015 01:37:18 +0000
Received: from [192.168.0.16] (unknown [120.149.147.132]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 0BD7322E265; Mon, 6 Apr 2015 21:36:50 -0400 (EDT)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <5522FE59.7060205@greenbytes.de>
Date: Tue, 07 Apr 2015 11:36:48 +1000
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D0FCA6BC-41D6-4A58-95D9-258B7F8BC2DB@mnot.net>
References: <20150406204549.36711180470@rfc-editor.org> <5522FE59.7060205@greenbytes.de>
To: "Julian F. Reschke" <julian.reschke@greenbytes.de>
X-Mailer: Apple Mail (2.2070.6)
Received-SPF: pass client-ip=216.86.168.182; envelope-from=mnot@mnot.net; helo=mxout-07.mxes.net
X-W3C-Hub-Spam-Status: No, score=-7.3
X-W3C-Hub-Spam-Report: AWL=0.404, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: lisa.w3.org 1YfIS3-00073H-U1 a87483a2a1dc28a18313b1de4cab591f
X-Original-To: ietf-http-wg@w3.org
Subject: Re: RFC 7538 on The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)
Archived-At: <http://www.w3.org/mid/D0FCA6BC-41D6-4A58-95D9-258B7F8BC2DB@mnot.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/29278
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

\o/

Good work, Julian, and thanks everyone for contributing.



> On 7 Apr 2015, at 7:44 am, Julian Reschke <julian.reschke@greenbytes.de> wrote:
> 
> 
> 
> 
> -------- Forwarded Message --------
> Subject: RFC 7538 on The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)
> Date: Mon,  6 Apr 2015 13:45:49 -0700 (PDT)
> From: rfc-editor@rfc-editor.org
> Reply-To: ietf@ietf.org
> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> CC: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
> 
> 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
> 
> 
> 
> 
> 
> 

--
Mark Nottingham   https://www.mnot.net/