Re: [httpapi] Discussion of adopting Content-Warning header

Roberto Polli <robipolli@gmail.com> Tue, 15 December 2020 15:31 UTC

Return-Path: <robipolli@gmail.com>
X-Original-To: httpapi@ietfa.amsl.com
Delivered-To: httpapi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D14B13A11DA for <httpapi@ietfa.amsl.com>; Tue, 15 Dec 2020 07:31:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.698
X-Spam-Level:
X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 0CMDBuSq01XQ for <httpapi@ietfa.amsl.com>; Tue, 15 Dec 2020 07:31:53 -0800 (PST)
Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 972053A11DD for <httpapi@ietf.org>; Tue, 15 Dec 2020 07:31:53 -0800 (PST)
Received: by mail-io1-xd33.google.com with SMTP id m23so6076577ioy.2 for <httpapi@ietf.org>; Tue, 15 Dec 2020 07:31:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nWnu2QTWSsSOFfgE1O7plEMYqFXHfdxyAvrASDfjTs0=; b=hXzqUHWiH9IzeHtkhIFySdpf0XTzkPyiz2plevWW66HHs9xcK6ZhQrbECEZ+PCHUBa dfiE/2UgemgmmByHvd52gJf5f/urMZlE1G7TDWqQpSgdTa/4lQhM/iO0DJUo/YiUlJaV 4AB9dS0APT8l7Eu0WnHioHIgfeN0FPWbgr4H91h0jDk+SyeboloU9fgnZNzORC60Y+69 oxLzsyxunyXW6/EhXtWFEfFMMZpL6B+2DSAIt8u6iRLfK4GPV+OIQXbEMMMobv8RNX89 gzyzMMktLeEZydl7tJShAyYfBHK3fxF2e5pc6OqmHYjhXrV1GFRrOWL+6EwZZuBb7Fyz dWsA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nWnu2QTWSsSOFfgE1O7plEMYqFXHfdxyAvrASDfjTs0=; b=LkdUcL8CW6sxpJyNPJhqaOAU1YlQI9ZwLsSZYPGKRrq0ojzIi10xd61XI5ab1/xfyG ka4wDCcIRNs/9m9jeo/NOwNv/6U5bgLDauOhYlCy9l9Xcdy+SNJVnKF4uugynv9UJscl Sbmc8Hz1GdtNjEFNQyGk6Qix6Ryl00bZFRw/QwcvQHcuX0JUKTv9E+UfDdCviQmuCN6o c1pApL/K9/v1WgDTvWEyctx3MLkyry3u25YpXcJ1E0XZz55f/BA3Jio1FhMq8DPJ8vd4 fP+wOhvCbZJnMZUjjqRsNtbpTYHx9hIg7OPPa4tip+cOlPKmBgmRLvvTB76fuyNGUbNt bgDA==
X-Gm-Message-State: AOAM530wOGMhJHglIYBK+dAaG1KK0V3QBoV26+ILAyHvFwVbeFCtOxcn FuwC9Cra6HQDrm2VBbmE4pnBLhgi4I1yItR4Pek=
X-Google-Smtp-Source: ABdhPJz5qxmwUzXyNv7m1UEpFn8JvxP/SptZmw+yRltgHH0hY8IFPb97kPq2HI8xt39+OmTlctuQI6VgX7aApeVX2Y8=
X-Received: by 2002:a02:bb99:: with SMTP id g25mr39669838jan.11.1608046312793; Tue, 15 Dec 2020 07:31:52 -0800 (PST)
MIME-Version: 1.0
References: <88ED49DB-E081-4C97-9FB9-080A1C585435@akamai.com> <80acc592-be10-533d-d6ba-e39ea78ef8de@dret.net> <BL0PR00MB0836A53E8E6526BF29BEF6DCF0C69@BL0PR00MB0836.namprd00.prod.outlook.com>
In-Reply-To: <BL0PR00MB0836A53E8E6526BF29BEF6DCF0C69@BL0PR00MB0836.namprd00.prod.outlook.com>
From: Roberto Polli <robipolli@gmail.com>
Date: Tue, 15 Dec 2020 16:31:41 +0100
Message-ID: <CAP9qbHW3N4yyN+pGf6T15xfDawZnNoFzChEzOqQB6C4S7zh4Sw@mail.gmail.com>
To: Darrel Miller <Darrel.Miller=40microsoft.com@dmarc.ietf.org>
Cc: "erik.wilde@dret.net" <erik.wilde@dret.net>, "rsalz=40akamai.com@dmarc.ietf.org" <rsalz=40akamai.com@dmarc.ietf.org>, "httpapi@ietf.org" <httpapi@ietf.org>, "andre@shipcloud.io" <andre@shipcloud.io>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/Tv2iAYNKaFIV523_XPuonWZG25A>
Subject: Re: [httpapi] Discussion of adopting Content-Warning header
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/httpapi>, <mailto:httpapi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/httpapi/>
List-Post: <mailto:httpapi@ietf.org>
List-Help: <mailto:httpapi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/httpapi>, <mailto:httpapi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Dec 2020 15:31:55 -0000

Hi @all,


Il giorno mar 15 dic 2020 alle ore 06:00 Darrel Miller
<Darrel.Miller=40microsoft.com@dmarc.ietf.org> ha scritto:
> > if
> > there isn't enough interest, an alternative path may be to keep
> > developing it as an individual draft
I think this draft will benefit from a wider discussion, including the
considerations provided by Darrell.

> [..] I've see the Warnings header from RFC 7234 used in several cases.
> [..] One advantage of using the Warning header was the fact that the warnings did not need to affect the structure of the payload.
> Would you consider a change to this draft that enabled representing details of the warning in the header itself?
iiuc this behavior can be configured via the content-warning-type: the
payload one is  "embedded-warning",
so the field definition already has an extension mechanism capable of
supporting further types, eg "expensive-request" or "old-api-version"
or whatever.

I think this kind of discussions are the kind of activity of the workgroup.

Have a nice day,
R.