allow use of a future fully specified JWS algorithm identifier for EdDSA w/ Ed25519

[Filip Skokan]

The to-be-adopted JOSE WG draft https://www.ietf.org/archive/id/draft-jones-jose-fully-specified-algorithms-02.html aims to add a fully specified identifier for the EdDSA using Ed25519 sub-type algorithm.

The FAPI 2.0 SP language should account to allow this future fully specified algorithm identifier. Today its use would be prohibited on the account of the language enumerating actual algorithm identifiers.

[Brian Campbell]

Filip is technically correct here, I think. Maybe using more general names/descriptions rather than actual algorithm identifiers? Although that’s maybe harder/uglier to do than it sounds…

[Nat Sakimura]

Perhaps we should try to do it in FAPI 2.1 or something like that? Or is there concrete action that we can do now?

[Nat Sakimura]

Talked in Pacific call.

[Filip Skokan]

Perhaps we should try to do it in FAPI 2.1 or something like that? Or is there concrete action that we can do now?

We’re not in a position that we can’t change 2.0 yet. Unless there’s good reason not to do this I think we should account for it now.

[Brian Campbell]

The “Fully-Specified Algorithms” draft is now an adopted WG item FWIW https://datatracker.ietf.org/doc/draft-ietf-jose-fully-specified-algorithms/

‌

[Filip Skokan]

https://bitbucket.org/openid/fapi/pull-requests/470

[Filip Skokan]

Resolved with https://bitbucket.org/openid/fapi/pull-requests/470

[Filip Skokan]

FYI: https://mailarchive.ietf.org/arch/msg/jose/kqJehzKvJmNkFhwhQvgebIyKRUE/