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

Patrick McManus <pmcmanus@mozilla.com> Tue, 03 July 2018 14:51 UTC

Return-Path: <pmcmanus@mozilla.com>
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 E3FFF130E6D; Tue, 3 Jul 2018 07:51:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.974
X-Spam-Level:
X-Spam-Status: No, score=-0.974 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, SPF_SOFTFAIL=0.665] autolearn=no 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 JH4xkGr0s69M; Tue, 3 Jul 2018 07:51:25 -0700 (PDT)
Received: from linode64.ducksong.com (linode6only.ducksong.com [IPv6:2600:3c02::f03c:91ff:fe6e:e8da]) by ietfa.amsl.com (Postfix) with ESMTP id F245E130E70; Tue, 3 Jul 2018 07:51:24 -0700 (PDT)
Received: from mail-oi0-f51.google.com (mail-oi0-f51.google.com [209.85.218.51]) by linode64.ducksong.com (Postfix) with ESMTPSA id 69C383A05B; Tue, 3 Jul 2018 10:51:24 -0400 (EDT)
Received: by mail-oi0-f51.google.com with SMTP id i12-v6so4350348oik.2; Tue, 03 Jul 2018 07:51:24 -0700 (PDT)
X-Gm-Message-State: APt69E0VZ7HboWlXMRayiVS3NO2LOde9qV+kIHVUQWDKq3lKYtkSIZAa 7fLXNADTVhRBoCkfQRMt9KexUHGNmw0RHwNi7/A=
X-Google-Smtp-Source: AAOMgpeLWFAI7XGrO+eSatjUrCB2qX2ipS7K+8Uup7nv4EomxVxtCO2d7UmNXNe58r/Sg7a095VDAz9CtmgCPxVcN28=
X-Received: by 2002:aca:5c46:: with SMTP id q67-v6mr20022271oib.17.1530629484054; Tue, 03 Jul 2018 07:51:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:8a22:0:0:0:0:0 with HTTP; Tue, 3 Jul 2018 07:51:23 -0700 (PDT)
In-Reply-To: <153054106529.16082.5456844530797164969.idtracker@ietfa.amsl.com>
References: <153054106529.16082.5456844530797164969.idtracker@ietfa.amsl.com>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Tue, 03 Jul 2018 10:51:23 -0400
X-Gmail-Original-Message-ID: <CAOdDvNqSCWPtNM=08PA-NAO24gJ6LcOsxzsVwraRMu7ta086YA@mail.gmail.com>
Message-ID: <CAOdDvNqSCWPtNM=08PA-NAO24gJ6LcOsxzsVwraRMu7ta086YA@mail.gmail.com>
Subject: Re: Last Call: <draft-sahib-451-new-protocol-elements-01.txt> (New protocol elements for HTTP Status Code 451) to Informational RFC
To: IETF Discussion Mailing List <ietf@ietf.org>
Cc: IETF-Announce <ietf-announce@ietf.org>, draft-sahib-451-new-protocol-elements@ietf.org, Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: multipart/alternative; boundary="000000000000ae0e37057019724a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/s0sqDFuD1D1PTUgC_EKszNhRAMk>
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: Tue, 03 Jul 2018 14:51:28 -0000

>From an HTTP pov: new response headers, such as the proposed
geo-scope-block, would really benefit from a more rigorous syntax than is
provided here..  see: sections 2 and 3 of https://httpwg.org/http-
extensions/draft-ietf-httpbis-variants.html#variants for how a current wg
draft does it. Also, its composition of a list of country codes should
probably be a MUST as Tim hints.

Tim's concerns resonate with me as questions a WG really should debate and
reach rough consensus on rather than this being an AD sponsored doc
(especially as its a defacto update of a standards track document by an
informational one). I'm not sure which WG - httpbis did not have a critical
mass of interest in this in the past.

-Patrick



On Mon, Jul 2, 2018 at 10:17 AM, The IESG <iesg-secretary@ietf.org> wrote:

>
> The IESG has received a request from an individual submitter to consider
> the
> following document: - 'New protocol elements for HTTP Status Code 451'
>   <draft-sahib-451-new-protocol-elements-01.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits final
> comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2018-07-30. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of
> the Subject line to allow automated sorting.
>
> Abstract
>
>
>    This draft recommends protocol updates to Hypertext Transfer Protocol
>    (HTTP) status code 451 (defined by RFC7725) based on an examination
>    of how the new status code is being used by parties involved in
>    denial of Internet resources because of legal demands.  Also included
>    is an analysis of HTTP 451 from a human rights perspective using
>    guidelines from RFC8280.
>
>    Discussion of this draft is at https://www.irtf.org/mailman/listinfo/
>    hrpc [1] and https://lists.ghserv.net/mailman/listinfo/statuscode451
>    [2].
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-sahib-451-new-protocol-elements/
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-sahib-451-new-protoco
> l-elements/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
>
>