IETF Logo Mail Archive

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

Roberto Polli <roberto@teamdigitale.governo.it> Thu, 28 January 2021 08:50 UTC

Return-Path: <roberto@teamdigitale.governo.it>
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 AFE803A13FB for <httpapi@ietfa.amsl.com>; Thu, 28 Jan 2021 00:50:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=teamdigitale.governo.it
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 uEWqWuFahoAL for <httpapi@ietfa.amsl.com>; Thu, 28 Jan 2021 00:50:13 -0800 (PST)
Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) (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 E81403A13F8 for <httpapi@ietf.org>; Thu, 28 Jan 2021 00:50:12 -0800 (PST)
Received: by mail-ej1-x62a.google.com with SMTP id r12so6534800ejb.9 for <httpapi@ietf.org>; Thu, 28 Jan 2021 00:50:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=teamdigitale.governo.it; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=a9YB9Cuux9lucByP751cd3HEyg/OOdd59BeS0elojrQ=; b=QzVO8nU7O1I1M+FGZMVFa0GDWju6Tpm0mWfO4YNqDHktrAvWhm0e/Vq332CxIB0OXf 3UtK0813lhdpQl7iWns61/tTOVmRLHuwFSqOH3H5Bsp95z+DeWRpVCHERV66Iovlm3hP QKOh4nk0HZ3H6MFv+Mp1vPBlDraE98YNZEZ0e8yXPhmF6O0aBMC1usdVuxhgHn8nCAO+ mDeqr3Izr0RK1TsBxuDFwYZsmHXRuGlKgnZ0fHu78DnBMlkLd5EEzqwJwatPgzH3Aow7 XmYBEzthiFPTRrZqHA7i2zq9eeQpQQIawWvtdGWJn2FyCnowd+gt4uJT3iYN5yeXp0cm fbcA==
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:content-transfer-encoding; bh=a9YB9Cuux9lucByP751cd3HEyg/OOdd59BeS0elojrQ=; b=KzvufzQdfm/zgiu283bB1kb29fR3mZCT+k+PHeSCNdGPossC8QPiv9ji70UrR2NBQf q7f7JExaBM23TxLuF/4IBf++RkYYwaGY4+CmEPlG/fUgUoUYgur1mspXKE0gPABUmRCa pew466aZ2j4K1WPfO+xy/DB6rwO54hlWGEKDHFalgkWYwfvAjuDIejHrLfpMW7FRUmoM SIRHadEIlnGByWAEdONnbwFBebm2YP4H/S20S1BJ+TjJ6QsVZfqY9r9xMuFWQnXKdnFN QiCv5XisyUllI4B787nSQAjuk61BPFGSLpx9P5edkSE2fgxqdNgc6GrkD3lXPmrnEEMa IWCg==
X-Gm-Message-State: AOAM531mvCVfGx3Ie+yGZy+BOywck0diq66bAD0O/z73H79g5JjkXuc6 +Ml6Gzg3p2rdwQGXWpYt7bE5vArjqsC3vMqKOmlb/g==
X-Google-Smtp-Source: ABdhPJyNbwNcwibWkt2nV28FXihUE0bq1jGv/1M+b+pTIqaOagYpXv4nbbqxUcDZM786iHWAMp+osPf+kSxhWgjnK4U=
X-Received: by 2002:a17:906:40ca:: with SMTP id a10mr10412934ejk.295.1611823809618; Thu, 28 Jan 2021 00:50:09 -0800 (PST)
MIME-Version: 1.0
References: <88ED49DB-E081-4C97-9FB9-080A1C585435@akamai.com> <C6EF74FA-4987-48EB-8F7B-74EB54C295CD@mnot.net> <CAEQcYZhF4X9c+4zknGvCQgW4mgcemMTG66dhH6S7=9bVDjmeYQ@mail.gmail.com> <C3A31FE3-A2DA-4A8C-B18E-0D1DFD999E12@mnot.net>
In-Reply-To: <C3A31FE3-A2DA-4A8C-B18E-0D1DFD999E12@mnot.net>
From: Roberto Polli <roberto@teamdigitale.governo.it>
Date: Thu, 28 Jan 2021 09:49:58 +0100
Message-ID: <CAMRHeuxYb215q5M0e2UPNA2d=DSv0D8VeXEKH2NZUqTXOMUmhg@mail.gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: André Cedik <andre.cedik@googlemail.com>, "httpapi@ietf.org" <httpapi@ietf.org>, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/Td76wtoLS-7kZGyHsHKrJE5zQ2g>
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: Thu, 28 Jan 2021 08:50:15 -0000

Hi @all,

Il giorno gio 28 gen 2021 alle ore 09:29 Mark Nottingham
<mnot@mnot.net> ha scritto:
> There may indeed be other use cases for warnings in APIs that justify a header, but without seeing them, it's hard to tell if the design you've proposed will address them.

imho there is a general interest in a replacement of the `Warning`
header (eg. to set alerts in payload-agnostic monitoring systems).
I agree that a strong relationship with the payload data raises
various issues, including Mark's ones.

My suggestion to André - that may still not address Mark's concerns - is to:
1- dis-entangle his proposal from the `Content` (eg. `Api-Warning`)
2- retain the "warning-type" registry, which can specify the type of
warning including content-warning

my 2¢,
R.



-- 
Roberto Polli
API Expert
M. +39 3406522736
MID
DIPARTIMENTO PER LA
TRASFORMAZIONE
DIGITALE
Presidenza del Consiglio dei Ministri - Ministro per l'innovazione
tecnologica e la digitalizzazione
https://innovazione.gov.it/

Il Dipartimento per la Trasformazione Digitale, salvo eccezioni,
comunica con le altre Amministrazioni via posta elettronica ordinaria
e non posta elettronica certificata, in conformità a quanto previsto
dall’art.47 del Codice dell’Amministrazione Digitale.

v2.23.0 | Report a Bug | By Email