Re: [Jwt-reg-review] [IANA #1352928] Request for Assignment (jwt, CTA-5009)

Brian Campbell <bcampbell@pingidentity.com> Thu, 01 February 2024 22:10 UTC

Return-Path: <bcampbell@pingidentity.com>
X-Original-To: jwt-reg-review@ietfa.amsl.com
Delivered-To: jwt-reg-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6679EC14F605 for <jwt-reg-review@ietfa.amsl.com>; Thu, 1 Feb 2024 14:10:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.003
X-Spam-Level:
X-Spam-Status: No, score=-2.003 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, HTML_MESSAGE=0.001, MIME_BOUND_DIGITS_15=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=pingidentity.com
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 XtPTc1Xum_7I for <jwt-reg-review@ietfa.amsl.com>; Thu, 1 Feb 2024 14:10:14 -0800 (PST)
Received: from mail-il1-x135.google.com (mail-il1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03C60C14F6E1 for <jwt-reg-review@ietf.org>; Thu, 1 Feb 2024 14:10:13 -0800 (PST)
Received: by mail-il1-x135.google.com with SMTP id e9e14a558f8ab-363ac2149e2so1702795ab.3 for <jwt-reg-review@ietf.org>; Thu, 01 Feb 2024 14:10:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=google; t=1706825413; x=1707430213; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=dKKtNDbeIrBKMCYRHAJ1rVpdEajA5aHbSMXmGJ4ubTw=; b=MSKzvKsP76YgrC2dzUL8SFKmymGHR6E2sPparto+YwEl2QIMC46E+3sX2HcorrjNRP PzrrDW1luaApP4XMijRskiWFAM8ajpaDOrzG5m5+kGNbsvtIFac2kEfxO5yHDJgMNs1U LAwsTdPsspzi1HSy0fY9kay2gYldCdwXBCVWRRHU71+d+K5nCpqsQHFSZPeWZQSpSLZ9 TDIPn5p0MaNowfcqBoEzpHONbpi5Lgxgbh8deVWPlVbcoe79CdYKC2/hn+INWt9hSToI +RaarHzIZD8lscLYqprJgPWV6Qux9YlQBiM/ZefQBghSiNSHZR64EGj02zn0XY00SpRj 20Vg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706825413; x=1707430213; h=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=dKKtNDbeIrBKMCYRHAJ1rVpdEajA5aHbSMXmGJ4ubTw=; b=wsClAWa6Fhy5TavpxwOacvn9Z2HDezUJ5IGx4S/1O/qQ81crgls7ocs4DsmaM0youO Sqgk6HEbfYVd4Cu2r5tNUtGnAmOWMQkXIBmnLWceaWCHAjoUKm31IjxAnbxfRMpcE46d NG/rqZDcsd2+NSe+zqwkslQUbVeO0mxUDgHCUOF2ygktgGENaIT7h1vcOVDvzmFpYPht 5hnKyDca+aplPm9cwiz+RKvg5wS+cHab3hmoUr7WI2V3tyAMc+1JZX/Re8ffLFM/9Qn7 CqH+bXIe3cPThsmKI89tkSE0W10fm/JKFBXzYgvumjuJjai9WxP1tBX92rzAs9PVHIb1 UHng==
X-Gm-Message-State: AOJu0YxPE7JAuKa94w00aiOlg/uZhvLSj4dLasdSXUU0jvx1iPGXyMgb mYDE6nbkDfg+rLurrubYlJme8lkoC4uMzJ/RnM3/lYC7I5N/S7m/p/XV0VpSUESYzsSq2siVzGU exZjJNovfrW0Wz4ks/x8jWu0MP/0owyZ9oOp234IwfU32R5GKg9NeLTZ6xZ6i3LcRSc4tgfV/KI mDWL0a7njI/OqtEMGyHvXgLx9fJsJ9ANslecM=
X-Google-Smtp-Source: AGHT+IEvJJek2tgIaAgm8OlJ/o7uV0sJggx22IRcO/2xdF79SjwXpTAN/8ACj715/st4Y4r4MjJiynmoH3VzPOeOKF8=
X-Received: by 2002:a92:d441:0:b0:362:ad5d:6f4 with SMTP id r1-20020a92d441000000b00362ad5d06f4mr184239ilm.23.1706825411406; Thu, 01 Feb 2024 14:10:11 -0800 (PST)
MIME-Version: 1.0
References: <RT-Ticket-1352928@icann.org> <rt-5.0.3-1104910-1706036005-376.1352928-9-0@icann.org> <rt-5.0.3-96476-1706119200-1688.1352928-9-0@icann.org> <rt-5.0.3-1120593-1706812087-1771.1352928-9-0@icann.org>
In-Reply-To: <rt-5.0.3-1120593-1706812087-1771.1352928-9-0@icann.org>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Thu, 01 Feb 2024 15:09:39 -0700
Message-ID: <CA+k3eCSm3GwkzY0YgP4N-Pxu70tYvjwYy9y_dVFQi_5z35L6Fw@mail.gmail.com>
To: iana-prot-param-comment@iana.org
Cc: ve7jtb@ve7jtb.com, michael_b_jones@hotmail.com, jwt-reg-review@ietf.org
Content-Type: multipart/mixed; boundary="0000000000005793850610594291"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jwt-reg-review/3Se2zZoY-CFYX9Dc5ABK-iM84lM>
Subject: Re: [Jwt-reg-review] [IANA #1352928] Request for Assignment (jwt, CTA-5009)
X-BeenThere: jwt-reg-review@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Expert review of proposed IANA registrations for JSON Web Token \(JWT\) claims." <jwt-reg-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jwt-reg-review>, <mailto:jwt-reg-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jwt-reg-review/>
List-Post: <mailto:jwt-reg-review@ietf.org>
List-Help: <mailto:jwt-reg-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jwt-reg-review>, <mailto:jwt-reg-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Feb 2024 22:10:19 -0000

I honestly don't have the knowledge to evaluate the semantics of this
"geohash" claim but don't  in general object to its registration. It seems
okay to add.

I will note, however, that the registration request does not have the
"Specification Document(s):" part listed in the original registration
template <https://datatracker.ietf.org/doc/html/rfc7519#section-10.1.1>.
What does IANA plan to put in the corresponding "Reference" column of the
registry <https://www.iana.org/assignments/jwt/jwt.xhtml#claims>? I don't
think it can be omitted. The registry is supposed to "record the Claim Name
and a reference to the specification that defines it" according to the text
that establishes it
<https://datatracker.ietf.org/doc/html/rfc7519#section-10.1> (presumably so
that folks can find the corresponding specifications from the registry
entries). I suspect a similar question might arise for the CBOR and CWT
registration requests as well.

This sort of speaks to the Fast and Readable Geographical Hashing CTA-5009
specification being unfortunately rather cumbersome to access. It is
available free of charge, as mentioned, but requires a shopping cart and a
checkout process that requests some personal information. I've attached a
copy here for the convenience of other reviewers.

CTA-5009 Final.pdf

On Thu, Feb 1, 2024 at 11:28 AM David Dong via RT <
iana-prot-param-comment@iana.org> wrote:

> Dear John Bradley, Brian Campbell, and Michael B. Jones (cc:
> jwt-reg-review),
>
> Following up on this; as the designated experts for the JSON Web Token
> Claims registry, can you review the JWT Claim registration proposal below?
> If it's OK, we'll make the assignment at:
>
> https://www.iana.org/assignments/jwt/
>
> Unless you ask us to wait for the other reviewers, we’ll act one week
> after the first response we receive.
>
> The due date is February 14th.
>
> With thanks,
>
> David Dong
> IANA Services Sr. Specialist
>
> On Wed Jan 24 18:00:00 2024, david.dong wrote:
> > Dear John Bradley, Brian Campbell, and Michael B. Jones (cc: jwt-reg-
> > review),
> >
> > As the designated experts for the JSON Web Token Claims registry, can
> > you review the JWT Claim registration proposal below? If it's OK,
> > we'll make the assignment at:
> >
> > https://www.iana.org/assignments/jwt/
> >
> > Unless you ask us to wait for the other reviewers, we’ll act one week
> > after the first response we receive.
> >
> > The due date is February 14th.
> >
> > With thanks,
> >
> > David Dong
> > IANA Services Sr. Specialist
> >
> > On Tue Jan 23 18:53:25 2024, david.dong wrote:
> > > Contact Name:
> > > Chris Lemmons
> > >
> > > Contact Email:
> > > alficles@gmail.com
> > >
> > > Type of Assignment:
> > > Permanent
> > >
> > > Registry:
> > > CBOR Tag, JSON Web Token Claims, CBOR Web Token Claims
> > >
> > > Description:
> > > These tags and claims are defined in CTA-5009, which was recently
> > > published by the Consumer Technology Association. The specification
> > > is
> > > available free of charge at
> > > https://shop.cta.tech/collections/standards/products/fast-and-
> > > readable-geographical-hashing-cta-5009 , but a courtesy copy can be
> > > provided to IANA and any relevant experts on request if desired.
> > >
> > > Additional Info:
> > > These are defined in CTA-5009 as noted above. These define tags and
> > > claims for the storage of Geohash strings and arrays. As described in
> > > the document:
> > >
> > > Show quoted text
> > > article on Wikipedia. These are excellent resources, but they can
> > > change over time
> > > and are not generally suitable for building on in a consensus-based
> > > standards-making process.
> > > This document exists to remediate that. It describes the practice as
> > > it exists at the time of writing and
> > > provides general, straightforward algorithms for understanding and
> > > communicating with Geohashes. It
> > > also exists to serve as a stable reference document for a few IANA
> > > registrations.
> > >
> > > To that end, we request these numbers:
> > >
> > > CBOR Tag:
> > >
> > > Tag: 105
> > > Data Item: text string or array
> > > Semantics: Geohash String
> > > Point of Contact: Consumer Technology Association
> > >
> > > Tag: 279
> > > Data Item: array
> > > Semantics: Coordinate Reference System Wrapper
> > > Point of Contact: Consumer Technology Association
> > >
> > > JWT Claim:
> > >
> > > Claim Name: geohash
> > > Claim Description: Geohash String or Array
> > > Change Controller: Consumer Technology Association
> > >
> > > CWT Claim:
> > >
> > > Claim Name: geohash
> > > Claim Description: Geohash String
> > > JWT Claim Name: geohash
> > > Claim Key: 282
> > > Claim Value Type(s): text string or array
> > > Change Controller: Consumer Technology Association
>
>

-- 
_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._