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

Mark Nottingham <mnot@mnot.net> Thu, 28 January 2021 06:39 UTC

Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <88ED49DB-E081-4C97-9FB9-080A1C585435@akamai.com>
Date: Thu, 28 Jan 2021 17:38:58 +1100
Cc: "httpapi@ietf.org" <httpapi@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C6EF74FA-4987-48EB-8F7B-74EB54C295CD@mnot.net>
References: <88ED49DB-E081-4C97-9FB9-080A1C585435@akamai.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/WbyPH6RTLy9rlV26IpQE8NiN5VE>
Subject: Re: [httpapi] Discussion of adopting Content-Warning header
Precedence: list

Hi,

I've re-read this draft. 

I don't understand what the use case is -- specifically, what benefit exposing this information in a header field brings.

The JSON format described can already be used, and is identified with a distinct media type; that should be enough to indicate to a recipient that the content of the message is a problem.

Are there cases where it's expected that generic HTTP software (e.g., an intermediary) separate from the application in question is going to need to know this information? That's the usual reason for standardising a header field (the other being that the format doesn't accommodate that information in question, but that doesn't seem to be the case here).

Cheers,

> On 11 Dec 2020, at 3:07 am, Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote:
> 
> At our meeting at IETF 109, we discussed
>                                 https://tools.ietf.org/html/draft-cedik-http-warning-02
>  
> Let’s discuss this (we didn’t have enough time at the virtual). Feel free to use this thread or start new ones.
> -- 
> httpapi mailing list
> httpapi@ietf.org
> https://www.ietf.org/mailman/listinfo/httpapi

--
Mark Nottingham   https://www.mnot.net/

[httpapi] Discussion of adopting Content-Warning … Salz, Rich
Re: [httpapi] Discussion of adopting Content-Warn… Erik Wilde
Re: [httpapi] Discussion of adopting Content-Warn… Darrel Miller
Re: [httpapi] Discussion of adopting Content-Warn… Roberto Polli
Re: [httpapi] Discussion of adopting Content-Warn… André Cedik
Re: [httpapi] Discussion of adopting Content-Warn… Mark Nottingham
Re: [httpapi] Discussion of adopting Content-Warn… André Cedik
Re: [httpapi] Discussion of adopting Content-Warn… Mark Nottingham
Re: [httpapi] Discussion of adopting Content-Warn… Roberto Polli
Re: [httpapi] Discussion of adopting Content-Warn… Asbjørn Ulsberg