Re: Bikeshed: "context" parameter for signatures

Tyler Ham <> Fri, 23 September 2022 09:27 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D8778C14CEFC for <>; Fri, 23 Sep 2022 02:27:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.06
X-Spam-Status: No, score=-5.06 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ytStAljwEqpv for <>; Fri, 23 Sep 2022 02:27:02 -0700 (PDT)
Received: from ( []) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by (Postfix) with ESMTPS id 04215C14F74A for <>; Fri, 23 Sep 2022 02:27:01 -0700 (PDT)
Received: from lists by with local (Exim 4.94.2) (envelope-from <>) id 1obev2-00Ezvl-Tq for; Fri, 23 Sep 2022 09:24:24 +0000
Resent-Date: Fri, 23 Sep 2022 09:24:24 +0000
Resent-Message-Id: <>
Received: from www-data by with local (Exim 4.94.2) (envelope-from <>) id 1obev0-00Ezt6-P7 for; Fri, 23 Sep 2022 09:24:22 +0000
Received: from ([]) by with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <>) id 1obRL7-00DKph-OC for; Thu, 22 Sep 2022 18:54:25 +0000
Received: from ([2607:f8b0:4864:20::630]) by with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from <>) id 1obRL6-0026ss-7s for; Thu, 22 Sep 2022 18:54:25 +0000
Received: by with SMTP id x1so9654497plv.5 for <>; Thu, 22 Sep 2022 11:54:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=googleth; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=Fm4qMmCVruX7BU5q/qhM/6XG3buYWkmu2+2yBu7LgyQ=; b=tjV778Qdv9R7/cmrpdeDUxJ0wHUSHwly/y1sxozkT10qHEmS8nCtXLkxbqFGsMJyHF oc0cR2V+ZWIS1fwbqDGRmb/ERc6yLoi3kcRY5S2B46QUuHf9J5vXEsUePp6Hz+DBtNus iDwRHTsIPGBXYRzBIdD1m5nJI+iySG4vNVz0Y=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=Fm4qMmCVruX7BU5q/qhM/6XG3buYWkmu2+2yBu7LgyQ=; b=CLxw7Qdzl2D51mkiN0MYT3nBl0enD6N9pjivgSTjmiwZaDV71yfZzQpUBebXYayLSv FQeCwahjjbQuTz0KSbgHb6kj6QKn9a+qLu3LsgwCKnTFovOO2ETcRuWN/KZUOqtl9E1H SLu3b/CdMlv4hfXf6WCyerakE8Tb9jyO5n0hJY1Bob5QVn40a3B+uYH50aO9wE4KPker NCeeGQaXB70x/R518ViugNpdrgEfoWbvDxkVQ+Bg19l9iYGhpsjp8rsMR6jQlpyCpXIZ 4LUDIAB04E9zHt9E/LKaNIW+5NJPNjYvGPfiRrSYnoTdv0ObBBkGLTA14mT7VIsc9N3D QsBA==
X-Gm-Message-State: ACrzQf22jWxJYnWq8GMEfupT/tZ56dt27ewg6v4rztlqz6nYABqgPHLd hr8g0qezb6ThfYZcJUGOtjYV33DcGUh9Jfhm4v9QX/XptqY=
X-Google-Smtp-Source: AMsMyM4UoG9JlqZBjlU4tC2kQmkOxocyzDFBPi7YHdjM2rL6RBkhxbzA+oRcBKJshfndI6TY9/8gQZDe9zQT34nNoG8=
X-Received: by 2002:a17:902:7281:b0:178:388d:6f50 with SMTP id d1-20020a170902728100b00178388d6f50mr4707689pll.127.1663872852858; Thu, 22 Sep 2022 11:54:12 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Tyler Ham <>
Date: Thu, 22 Sep 2022 12:53:36 -0600
Message-ID: <>
To: Justin Richer <>
Cc: HTTP Working Group <>
Content-Type: multipart/alternative; boundary="00000000000058ac1305e94896aa"
Received-SPF: pass client-ip=2607:f8b0:4864:20::630;;
X-W3C-Hub-DKIM-Status: validation passed: (, signature is good
X-W3C-Hub-Spam-Status: No, score=-4.1
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: 1obRL6-0026ss-7s e3f5592573d64460213f65540403c580
X-caa-id: 611c280409
Subject: Re: Bikeshed: "context" parameter for signatures
Archived-At: <>
X-Mailing-List: <> archive/latest/40401
Precedence: list
List-Id: <>
List-Help: <>
List-Post: <>
List-Unsubscribe: <>

My first thought when I see the labels "app" and "application" is that the
value is meant to be the name of an application.

How about something like "appdata"? This changes the noun to a generic
"data", but it keeps "app" in there as an adjective to indicate that this
parameter is for something application-specific.


On Thu, Sep 22, 2022, 8:43 AM Justin Richer <> wrote:

> I missed an issue that had been filed (but not tagged) prior to the
> publication of signatures-12, and it asks a pretty simple question:
> We added a “context” parameter to allow applications to put a specific
> string that the application can recognize into the signature parameter set,
> so that (for example) an authz protocol can declare that a specific value
> be used or a cloud deployment can have all of its proxies use the same
> value. However, the term “context” is used in other ways in the spec, so
> it’s not the best term to use for this new parameter. The proposal is to
> change “context” to “application” or even the shorter “app”:
> I’d like to do a quick bike shed on this parameter name here, for anyone
> who has an opinion. Since it’s newer, existing libraries mostly don’t have
> it supported yet so if we’re going to change it we should change it right
> now.
> Thanks,
>  — Justin