draft-ietf-httpbis-legally-restricted-status-02, example on 3. 451 Unavailable For Legal Reasons

Kari Hurtta <khurtta@welho.com> Wed, 30 September 2015 05:26 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 433501B5C47 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 29 Sep 2015 22:26:29 -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 3B07n37qYpv4 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 29 Sep 2015 22:26:27 -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 2A6011B5C46 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 29 Sep 2015 22:26:24 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1Zh9rl-00076n-A1 for ietf-http-wg-dist@listhub.w3.org; Wed, 30 Sep 2015 05:23:45 +0000
Resent-Message-Id: <E1Zh9rl-00076n-A1@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <ylafon@w3.org>) id 1Zh9re-00075a-Ds for ietf-http-wg@listhub.w3.org; Wed, 30 Sep 2015 05:23:38 +0000
Received: from raoul.w3.org ([128.30.52.128]) by lisa.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <ylafon@w3.org>) id 1Zh9rR-0005Nv-P7 for ietf-http-wg@w3.org; Wed, 30 Sep 2015 05:23:35 +0000
Received: from homard.platy.net ([80.67.176.7] helo=[192.168.1.37]) by raoul.w3.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <ylafon@w3.org>) id 1Zh9rR-000GTG-9R for ietf-http-wg@w3.org; Wed, 30 Sep 2015 05:23:25 +0000
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: text/plain; charset="us-ascii"
From: Kari Hurtta <khurtta@welho.com>
Resent-From: Yves Lafon <ylafon@w3.org>
Date: Wed, 30 Sep 2015 03:54:33 +0000
Cc: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
Content-Transfer-Encoding: quoted-printable
Resent-Date: Wed, 30 Sep 2015 07:23:24 +0200
Message-Id: <E1Zh8TO-0000g8-Lv@maggie.w3.org>
X-Name-Md5: efe3dad792d606410c9cc49cedaffc94
Resent-To: ietf-http-wg@w3.org
To: Tim Bray <tbray@textuality.com>, HTTPBIS working group mailing list <ietf-http-wg@w3.org>
X-Mailer: Apple Mail (2.2104)
X-W3C-Hub-Spam-Status: No, score=-2.4
X-W3C-Hub-Spam-Report: ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, W3C_NW=0.5
X-W3C-Scan-Sig: lisa.w3.org 1Zh9rR-0005Nv-P7 ed7b1f098f2e60377c0e3f031f75cb51
X-Original-To: ietf-http-wg@w3.org
Subject: draft-ietf-httpbis-legally-restricted-status-02, example on 3. 451 Unavailable For Legal Reasons
Archived-At: <http://www.w3.org/mid/E1Zh8TO-0000g8-Lv@maggie.w3.org>
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/30288
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>


An HTTP Status Code to Report Legal Obstacles
draft-ietf-httpbis-legally-restricted-status-02
August 31, 2015

https://tools.ietf.org/html/draft-ietf-httpbis-legally-restricted-status-02

On

3. 451 Unavailable For Legal Reasons
https://tools.ietf.org/html/draft-ietf-httpbis-legally-restricted-status-02#section-3

there is an example.

Next chapter

4. Identifying Blocking Entities
https://tools.ietf.org/html/draft-ietf-httpbis-legally-restricted-status-02#section-4

introduces "Link" HTTP header field for that.

Should previous example also include that "Link" header field or is it
too early?

Otherwise the example do not fulfill that "SHOULD" -requirement.


/ Kari Hurtta
( not member of the mailing list)