RFC 7725 on An HTTP Status Code to Report Legal Obstacles

rfc-editor@rfc-editor.org Mon, 29 February 2016 23:34 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 E46691A0363 for <ietf-announce@ietfa.amsl.com>; Mon, 29 Feb 2016 15:34:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.908
X-Spam-Level:
X-Spam-Status: No, score=-106.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.006, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 pbzNt2h-tEyg for <ietf-announce@ietfa.amsl.com>; Mon, 29 Feb 2016 15:34:00 -0800 (PST)
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 EBA261A035F for <ietf-announce@ietf.org>; Mon, 29 Feb 2016 15:33:59 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id C9C0A180009; Mon, 29 Feb 2016 15:33:08 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7725 on An HTTP Status Code to Report Legal Obstacles
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160229233308.C9C0A180009@rfc-editor.org>
Date: Mon, 29 Feb 2016 15:33:08 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/F7rPqe7s7iQf9KwcelEe8gfGsV4>
Cc: drafts-update-ref@iana.org, ietf-http-wg@w3.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: <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: Mon, 29 Feb 2016 23:34:02 -0000

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

        
        RFC 7725

        Title:      An HTTP Status Code to 
                    Report Legal Obstacles 
        Author:     T. Bray
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2016
        Mailbox:    tbray@textuality.com
        Pages:      5
        Characters: 9309
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-httpbis-legally-restricted-status-04.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7725

This document specifies a Hypertext Transfer Protocol (HTTP) status
code for use when resource access is denied as a consequence of legal
demands.

This document is a product of the Hypertext Transfer Protocol Bis 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/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