[OAUTH-WG] Re: Nit in section 4 of draft 13 of SD-JWT

Travis Spencer <travis@curity.io> Fri, 25 October 2024 07:17 UTC

Return-Path: <travis.spencer@curity.io>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB3D2C1CAE71 for <oauth@ietfa.amsl.com>; Fri, 25 Oct 2024 00:17:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=curity.io
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ucnYZdWmZHJL for <oauth@ietfa.amsl.com>; Fri, 25 Oct 2024 00:16:56 -0700 (PDT)
Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D507BC19ECBA for <oauth@ietf.org>; Fri, 25 Oct 2024 00:16:56 -0700 (PDT)
Received: by mail-lf1-x12a.google.com with SMTP id 2adb3069b0e04-539f76a6f0dso1616668e87.1 for <oauth@ietf.org>; Fri, 25 Oct 2024 00:16:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=curity.io; s=google; t=1729840615; x=1730445415; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=Cp6nt4cHdOhp5/+PnOM34/cjgbhmIqdVFdVrTiNsEVs=; b=WuAX93BWSTYVu+YnecUW43g2J/JtPJ1XoQsR83gZ3HK7p+5E7kbvQkkduSm1b5c0uG za64wQzgUw2Y5N50e4m65rM7ClxJJI6YcqdzNm8j2Qp86OOXfnjUf07wZ/kV9l6c5Upn f0I9Y/I7YDqdKpsb5/jhXk9QDbRb9oD07c3zWK3UunDUPiFmHBIcK8t1beLLxv077kgj e2529mvpxa3/zXE7plvGPJk7rPURCas16NLizpWE0ZgPdtf502bsfo6Fag3jmMMc0D4B 4XzTQ+x3p72S20izGboYej8OK155c80HEGBfBwi3ijVfWGGzSavblVHeGCRpF7AYqKb2 l7/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729840615; x=1730445415; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Cp6nt4cHdOhp5/+PnOM34/cjgbhmIqdVFdVrTiNsEVs=; b=HDcxjOnQnxDLTZrEkqR1A2Ec62DAbyirRyx7D4whkhW+EblCXJPffEW1OydloE2efh HeO+GDAf0qDPha+Pip1pRx1HCnNbmCDW2+HujqbS24iXNuzQZ8Evu4YMOOnx/GDaamu6 t5OllmcpPOrqqgHxg2+QoieoZJGFJJL5mCUGgUMQ7eQI6QgxnWWheLBW3EmK1FaekjGS v2vc+gcKWB+gSr52QdDp6QV13Tf0SwLXKuGV0Rsd4LpvBDCiKPD7N0xZW8U9l7P+FSpX 3gpAoRTkKP39R7WT31QrtNjk4noUPzsGbjKe0aZxE9R6Hn4YS06Dux74Bdx1mUCaV8ls KWmg==
X-Gm-Message-State: AOJu0Yxn+BPIlOyBqKUlNQjxSzW8NXMfJmP2ko2+VAoaLcZFVDqqb82p J0CF9lZG9tY58aAtFoO7ranwqH1cCtZMR4i1Fg8mBzdB+YxJLWAbCSWtBFiFw95rWHQj4NnBGRN NNSBdtgCHhLNP+NN6OQq00L+tEBP1cgZQUkvoxRSGZrV7EDWYVrE=
X-Google-Smtp-Source: AGHT+IGyHV8STjqUOZFmeYe7SU56LOiPIXR3XHs43MYUz0ClKWoACU9DFvg/qdNdILnAJsw8TXYGd+1vaBSXNquWxfg=
X-Received: by 2002:a05:6512:10d4:b0:53a:bb7:ed77 with SMTP id 2adb3069b0e04-53b1a307d90mr4972406e87.14.1729840614668; Fri, 25 Oct 2024 00:16:54 -0700 (PDT)
MIME-Version: 1.0
References: <CAEKOcs32HCRh5oZTjvjso9sFV3bsMm48tfDsdXsrC5S++kam3g@mail.gmail.com> <CA+k3eCSxxkEUzDKgbd3ueh-newLyvOODfo4d2kNvbk2Wt1X3Lw@mail.gmail.com>
In-Reply-To: <CA+k3eCSxxkEUzDKgbd3ueh-newLyvOODfo4d2kNvbk2Wt1X3Lw@mail.gmail.com>
From: Travis Spencer <travis@curity.io>
Date: Fri, 25 Oct 2024 09:16:42 +0200
Message-ID: <CAEKOcs1JxpvhLXnOJoaPHtOOr_DGg4+C6JJDzOEvH+JSkrTizw@mail.gmail.com>
To: Brian Campbell <bcampbell=40pingidentity.com@dmarc.ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: DWWDV7GYZZH4XSQP4YWU3VFCFVQRVNMG
X-Message-ID-Hash: DWWDV7GYZZH4XSQP4YWU3VFCFVQRVNMG
X-MailFrom: travis.spencer@curity.io
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-oauth.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: oauth <oauth@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [OAUTH-WG] Re: Nit in section 4 of draft 13 of SD-JWT
List-Id: OAUTH WG <oauth.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/sZU7j_p0tRBKkJmVBW-MdDEAiSM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Owner: <mailto:oauth-owner@ietf.org>
List-Post: <mailto:oauth@ietf.org>
List-Subscribe: <mailto:oauth-join@ietf.org>
List-Unsubscribe: <mailto:oauth-leave@ietf.org>

I have empathy for the difficulties of creating standards, Brian, and
would be OK with keeping it if for no other reason than your
wellbeing. If it were me, however, I'd remove it. If the reader misses
the comma after the word celebrate or isn't familiar with the phrase
(like me), it makes the sentence hard to understand IMO. Your call
though. In any case, shall we agree that Oct. 25 is ABNF Day, so we
can celebrate it or not?


On Fri, Oct 25, 2024 at 1:10 AM Brian Campbell
<bcampbell=40pingidentity.com@dmarc.ietf.org> wrote:
>
> The phrase "for those who celebrate" there is a subtle attempt at a little bit of good-natured humor. ChatGPT explains the general phrase thusly:
>
> The phrase "for those who celebrate" is often used to acknowledge that not everyone may participate in a particular holiday, event, or tradition. It's a way of being inclusive and respectful of diverse beliefs, practices, and customs. For example, saying "Happy Holidays to those who celebrate" recognizes that while some people may be celebrating a specific holiday, others may not observe it or may celebrate different holidays.
>
> The meaning in the context of this document is to playfully acknowledge that some people really like ABNF while others aren't readily familiar with it and/or don't find it particularly useful. The former are those who celebrate. The latter are those who do not. The document is inclusive of all.
>
> This lighthearted reference also reflects the journey of how ABNF came to be included in the document. Seen here: https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/393, there was initially a suggestion that including ABNF would be helpful for implementers. Even though this was met with some skepticism about how many people would actually find it useful, it was added to the document anyway.
>
> Of course, if a joke requires explanation, it tends to lose its humor. Nevertheless, I remain partial to the text. Little attempts at satire, like this one, that poke fun at the occasional absurdity involved in standards development work help me keep it together in the face of the occasional absurdity.
>
>
>
>
>
> On Thu, Oct 24, 2024 at 1:54 AM Travis Spencer <travis=40curity.io@dmarc.ietf.org> wrote:
>>
>> Section 4 of draft 13 of the SD-JWT WG document says:
>>
>> As an alternative illustration of the SD-JWT format, for those who celebrate,
>> ABNF [RFC5234] for the SD-JWT, SD-JWT+KB, and various constituent parts
>> is provided here:
>>
>> Who are those who celebrate? Those that celebrate birthdays,
>> Midsummer, Halloween? I don't understand and think that phrase should
>> be deleted.
>>
>> Suggested alternative:
>>
>> As an alternative illustration of the SD-JWT format in ABNF [RFC5234] for
>> the SD-JWT, SD-JWT+KB, and various constituent parts is provided here:
>>
>> HTH!
>>
>> _______________________________________________
>> OAuth mailing list -- oauth@ietf.org
>> To unsubscribe send an email to oauth-leave@ietf.org
>
>
> CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited.  If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you.