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

[David Dong via RT <[e-mail]>]

Hi Brian,

Apologies for the delay in my response, and thank you for the review. Thank you also for attaching a copy for the other reviewers.

We plan to put [CTA-5009] as the reference, linking to <https://shop.cta.tech/collections/standards/products/fast-and-readable-geographical-hashing-cta-5009>. 

There are already some existing registrations with specifications either difficult to access or paywalled that we link to in the "Reference" field in other Specification Required registries (namely the ISO specs), for reference.

Please let us know if this registration in JWT is okay, or if we should wait for other reviewers to respond (we will mark this as OK one week after approval otherwise).

Best regards,

David Dong
IANA Services Sr. Specialist

On Thu Feb 01 22:12:24 2024, [e-mail] wrote:
> 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 <
> [e-mail]> 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:
> > > > [e-mail]
> > > >
> > > > 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
> >
> >
>