IETF Logo Mail Archive

Re: Last Call: <draft-sahib-451-new-protocol-elements-01.txt> (New protocol elements for HTTP Status Code 451) to Informational RFC

valdis.kletnieks@vt.edu Thu, 05 July 2018 16:11 UTC

Return-Path: <valdis@vt.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C485130F05 for <ietf@ietfa.amsl.com>; Thu, 5 Jul 2018 09:11:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
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 FSCz4oJqzJiG for <ietf@ietfa.amsl.com>; Thu, 5 Jul 2018 09:11:54 -0700 (PDT)
Received: from omr2.cc.vt.edu (omr2.cc.ipv6.vt.edu [IPv6:2607:b400:92:8400:0:33:fb76:806e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE66D130E70 for <ietf@ietf.org>; Thu, 5 Jul 2018 09:11:53 -0700 (PDT)
Received: from mr1.cc.vt.edu (mr1.cc.vt.edu [IPv6:2607:b400:92:8300:0:31:1732:8aa4]) by omr2.cc.vt.edu (8.14.4/8.14.4) with ESMTP id w65GBqWL003777 for <ietf@ietf.org>; Thu, 5 Jul 2018 12:11:52 -0400
Received: from mail-qk0-f199.google.com (mail-qk0-f199.google.com [209.85.220.199]) by mr1.cc.vt.edu (8.14.7/8.14.7) with ESMTP id w65GBlvD018531 for <ietf@ietf.org>; Thu, 5 Jul 2018 12:11:52 -0400
Received: by mail-qk0-f199.google.com with SMTP id u22-v6so10122332qkk.10 for <ietf@ietf.org>; Thu, 05 Jul 2018 09:11:52 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:in-reply-to:references :mime-version:content-transfer-encoding:date:message-id; bh=kweFuNQ+LOuUN5Fch2D6rZOULlRHtRSVS4C+vR/QvzM=; b=JdZ4/cedcrk0/AvrlfB0SWjaoFdDGMFbIyIDHgce6UMOf0acetFr0QwvjbEgzDGO9R UyGVekvwgLzbnpF64Eg6sJwdvdeUNHhAqH3cVpARepp79THdBkCtWYqDV/CbJ4yD0oFy QCkfEqIna5HALH/rAUjrFl4kmfpJosgR9gjEkq1YEbRMOmWMChnYe2+42p1egCaA2mhM bsL8OfDxFj5EffIEnpRNYOJPs6ezE/rQJYQMKSUrN1QBlnOhcX6neOiXD/AKSivwZM2V ZF49yHrWSORfOZTha2ua89lrQSaxrApuybeUAfG9gWkvn7BS+enJaOZBhB3qDkzTvfNu kHVA==
X-Gm-Message-State: APt69E0RuM2OOwOf7eg4xJyCZGAOECdaS2rMGyAqo6hB91+MqgjSks/p GUruZGZown6cX9p4RarxO6TWk6HLdYnAHR21aXpcy6OVdbGED/9J34gXOeR3F2sRDEXTcHJ94in FBwLVLBu0wZnOmCw=
X-Received: by 2002:a37:5f01:: with SMTP id t1-v6mr5513282qkb.231.1530807107616; Thu, 05 Jul 2018 09:11:47 -0700 (PDT)
X-Google-Smtp-Source: AAOMgpdIKN1uPr4e0197DxWx8XrOBdEQYbaG0hL9+vbbeijeaq8mIFEuArIdbpulwMNOjH/tDVf70A==
X-Received: by 2002:a37:5f01:: with SMTP id t1-v6mr5513273qkb.231.1530807107462; Thu, 05 Jul 2018 09:11:47 -0700 (PDT)
Received: from turing-police.cc.vt.edu (turing-police.cc.ipv6.vt.edu. [2001:468:c80:2103:f21f:afff:fe0c:8ada]) by smtp.gmail.com with ESMTPSA id w128-v6sm4023060qka.47.2018.07.05.09.11.45 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 05 Jul 2018 09:11:46 -0700 (PDT)
Sender: Valdis Kletnieks <valdis@vt.edu>
From: valdis.kletnieks@vt.edu
X-Google-Original-From: Valdis.Kletnieks@vt.edu
X-Mailer: exmh version 2.8.0 04/21/2017 with nmh-1.7+dev
To: Shivan Kaul Sahib <shivankaulsahib@gmail.com>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, IETF-Discussion Discussion <ietf@ietf.org>, Tim Bray <tbray@textuality.com>, draft-sahib-451-new-protocol-elements@ietf.org
Subject: Re: Last Call: <draft-sahib-451-new-protocol-elements-01.txt> (New protocol elements for HTTP Status Code 451) to Informational RFC
In-Reply-To: <CAG3f7MjEhq_v==1YDS2piZTG=tOw9RZpjKc3bhpbxTY9j05zRg@mail.gmail.com>
References: <153054106529.16082.5456844530797164969.idtracker@ietfa.amsl.com> <CAHBU6iunrrZ6W1hQTWqx7ziEPdDMspt+mf6u0t6DVJn_rS04aQ@mail.gmail.com> <130562.1530665238@turing-police.cc.vt.edu> <CAG3f7MjEhq_v==1YDS2piZTG=tOw9RZpjKc3bhpbxTY9j05zRg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1530807105_2731P"; micalg="pgp-sha1"; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 05 Jul 2018 12:11:45 -0400
Message-ID: <9010.1530807105@turing-police.cc.vt.edu>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/W2FnCAf0glibiqYf4Y7q_N8lnD4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jul 2018 16:11:57 -0000

On Tue, 03 Jul 2018 18:24:40 -0700, Shivan Kaul Sahib said:

> The intention of the draft asking for resource identification in the legal
> demand was *not* to say that the resource has to be named - like I said,
> the Vatican example was fine.

Unfortunately, that's not my reading of this text:

> "HTTP 451 SHOULD NOT be used by an operator to deny access to a resource on
> the basis of a legal demand that is not specific to the requested resource.

A legal request to block "anything from East Wombat" isn't specific to the
requested resource. It may cover that resource, and 38,915 other resources.

If a news item saying "all people in <insert town you are in> should seek
immediate shelter from an oncoming tornado", would you call that *specific to
you* (which it isn't, as it covers every other person in the town as well), or
merely *applicable* to you?

That's why I suggested "not applicable to the requested resource".

v2.23.0 | Report a Bug | By Email