Protocol Action: 'Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content' to Proposed Standard (draft-ietf-httpbis-p2-semantics-26.txt)
The IESG <iesg-secretary@ietf.org> Wed, 12 February 2014 14:55 UTC
Return-Path: <iesg-secretary@ietf.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 EE2771A099A for <ietf-announce@ietfa.amsl.com>; Wed, 12 Feb 2014 06:55:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 8Pvw3nRzH5Jc; Wed, 12 Feb 2014 06:55:16 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A1CB21A09BE; Wed, 12 Feb 2014 06:55:01 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content' to Proposed Standard (draft-ietf-httpbis-p2-semantics-26.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140212145501.2233.49062.idtracker@ietfa.amsl.com>
Date: Wed, 12 Feb 2014 06:55:01 -0800
Cc: httpbis chair <httpbis-chairs@tools.ietf.org>, httpbis mailing list <ietf-http-wg@w3.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 12 Feb 2014 14:55:18 -0000
The IESG has approved the following document: - 'Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content' (draft-ietf-httpbis-p2-semantics-26.txt) as Proposed Standard This document is the product of the Hypertext Transfer Protocol Bis Working Group. The IESG contact persons are Barry Leiba and Pete Resnick. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-httpbis-p2-semantics/ Technical Summary The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation. Note that this document is part of a set, which should be reviewed together: * draft-ietf-httpbis-p1-messaging * draft-ietf-httpbis-p2-semantics * draft-ietf-httpbis-p4-conditional * draft-ietf-httpbis-p5-range * draft-ietf-httpbis-p6-cache * draft-ietf-httpbis-p7-auth * draft-ietf-httpbis-method-registrations * draft-ietf-httpbis-authscheme-registrations Review and Consensus As chartered, this work was very constrained; the WG sought only to clarify RFC2616, making significant technical changes only where there were considerably interoperability or security issues. While the bulk of the work was done by a core team of editors, it has been reviewed by a substantial number of implementers, and design issues enjoyed input from many of them. It has been through two Working Group Last Calls, with multiple reviewers each time. We have also discussed this work with external groups (e.g., the W3C TAG). Downward references * RFC1950 * RFC1951 (already in downref registry) * RFC1952 * "Welch" Personnel Document Shepherd: Mark Nottingham Responsible Area Director: Barry Leiba RFC Editor Note Please update the reference to RFC1305 to point instead to RFC5905