From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: jose@ietf.org
Reply-To: iesg@ietf.org
Subject: WG Review: Javascript Object Signing and Encryption (jose)
The Javascript Object Signing and Encryption (jose) WG in the Security Area
of the IETF is undergoing rechartering. The IESG has not made any
determination yet. The following draft charter was submitted, and is provided
for informational purposes only. Please send your comments to the IESG
mailing list (iesg@ietf.org) by 2023-12-12.
Javascript Object Signing and Encryption (jose)
-----------------------------------------------------------------------
Current status: Active WG
Chairs:
John Bradley <ve7jtb@ve7jtb.com>
John Preuß Mattsson <john.mattsson@ericsson.com>
Karen O'Donoghue <kodonog@pobox.com>
Assigned Area Director:
Roman Danyliw <rdd@cert.org>
Security Area Directors:
Roman Danyliw <rdd@cert.org>
Paul Wouters <paul.wouters@aiven.io>
Mailing list:
Address: jose@ietf.org
To subscribe: https://www.ietf.org/mailman/listinfo/jose
Archive: https://mailarchive.ietf.org/arch/browse/jose/
Group page: https://datatracker.ietf.org/group/jose/
Charter: https://datatracker.ietf.org/doc/charter-ietf-jose/
The original [JSON Object Signing and Encryption (JOSE) working group][1]
standardized JSON-based representations for: Integrity-protected objects
(JSON Web Signatures/JWS, RFC 7515), Encrypted objects (JSON Web
Encryption/JWE, RFC7516), Key representations (JSON Web Key/JWK, RFC 7517),
Algorithm definitions (JSON Web Algorithms/JWA, RFC 7518), and Test vectors
for the above (Examples of Protecting Content Using JSON Object Signing and
Encryption, RFC 7520).
These were used to define the JSON Web Token (JWT) (RFC 7519), which in turn,
has seen widespread deployment in areas as diverse as [digital identity][2]
and [secure telephony][3].
As adoption of these standards to express and communicate sensitive data has
grown, so too has an increasing societal focus on privacy. User consent,
minimal disclosure, and unlinkability are common privacy themes in identity
solutions.
A multi-decade research activity for a sizeable academic and applied
cryptography community has focused on these privacy and knowledge mechanisms
(often referred to as anonymous credentials). Certain cryptographic
techniques developed in this space involve pairing-friendly curves and
zero-knowledge proofs (ZKPs) (to name just a few). Some of the benefits of
ZKP algorithms include unlinkability, selective disclosure, and the ability
to use predicate proofs.
The current container formats defined by JOSE and JWT are not able to
represent data using ZKP algorithms. Among the reasons are that most require
an additional transform or finalize step, many are designed to operate on
sets and not single messages, and the interface to ZKP algorithms has more
inputs than conventional signing algorithms. The reconstituted JOSE working
group will address these new needs, while reusing aspects of JOSE and JWT,
where applicable.
This group is chartered to work on the following goals:
- An Informational document detailing Use Cases and Requirements for new
specifications enabling JSON-based selective disclosure and zero-knowledge
proofs.
- Standards Track document(s) specifying representation(s) of
independently-disclosable integrity-protected sets of data and/or proofs
using JSON-based data structures, which also aims to prevent the ability to
correlate by different verifiers.
- Standards Track document(s) specifying representation(s) of JSON-based
claims and/or proofs enabling selective disclosure of these claims and/or
proofs, and that also aims to prevent the ability to correlate by different
verifiers.
- Standards Track document(s) specifying how to use existing cryptographic
algorithms and defining their algorithm identifiers. The working group will
not invent new cryptographic algorithms.
- Standards Track document(s) specifying how to represent keys for these new
algorithms as JSON Web Keys (JWKs).
- Informational document(s) defining test vectors for these new
specifications.
- Standards Track document(s) defining CBOR-based representations
corresponding to all the above, building upon the COSE and CWT specifications
in the same way that the above build on JOSE and JWT.
One or more of these goals may be combined into a single document, in which
case the concrete milestones for these goals will be satisfied by the
consolidated document(s).
The JOSE working group will also maintain the JOSE standard and facilitate
discussion of clarifications, improvements, and extensions to JWS, JWE, JWA,
and JWK. The WG will evaluate, and potentially adopt, proposed standard
documents dealing with algorithms that would fit the criteria of being IETF
consensus algorithms. Potential candidates would include those algorithms
that have been evaluated by the CFRG and algorithms which have gone through a
public review and evaluation process such as was done for the NIST SHA-3
algorithms. Potential candidates would not include national-standards-based
algorithms that have not gone through a similar public review process. The WG
may also publish informational and BCP documents describing the proper use of
these algorithms in JOSE.
An informal goal of the working group is close coordination with the
[rechartered W3C Verifiable Credentials WG][4], which has taken a dependency
on this work for the second version of its Verifiable Credentials
specification. The working group will also coordinate with the [Selective
Disclosure JWT][5] work in the [OAuth][6] working group, the [Privacy
Pass][7] working group, the [CBOR][8] working group, the [COSE][10] working
group, and the [CFRG][9].
[1]: https://datatracker.ietf.org/doc/charter-ietf-jose/02/
[2]: https://openid.net/connect/
[3]: https://www.ietf.org/blog/stir-action/
[4]: https://www.w3.org/2022/05/proposed-vc-wg-charter.html
[5]:
https://datatracker.ietf.org/doc/draft-ietf-oauth-selective-disclosure-jwt/
[6]: https://datatracker.ietf.org/wg/oauth/about/ [7]:
https://datatracker.ietf.org/wg/privacypass/about/ [8]:
https://datatracker.ietf.org/wg/cbor/about/ [9]:
https://datatracker.ietf.org/rg/cfrg/about/ [10]:
https://datatracker.ietf.org/wg/cose/about/
Milestones:
Jan 2024 - Adopt document registering cryptographic algorithm identifiers
that fully specify the cryptographic operations to be performed (as
proposed standard)
Apr 2024 - Adopt document describing the use of the NIST algorithm ML-KEM
in JOSE (as proposed standard)
Apr 2024 - Adopt document describing the use of the NIST algorithm ML-DSA
in JOSE (as proposed standard)
Apr 2024 - Adopt document describing the use of the NIST algorithm SLH-DSA
in JOSE (as proposed standard)
Apr 2024 - Adopt document describing the use of the NIST algorithm NL-DSA
in JOSE (as proposed standard)
WG action announcement
WG Action Announcement
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>,
jose-chairs@ietf.org,
jose@ietf.org
Subject: WG Action: Rechartered Javascript Object Signing and Encryption (jose)
The Javascript Object Signing and Encryption (jose) WG in the Security Area
of the IETF has been rechartered. For additional information, please contact
the Area Directors or the WG Chairs.
Javascript Object Signing and Encryption (jose)
-----------------------------------------------------------------------
Current status: Active WG
Chairs:
John Bradley <ve7jtb@ve7jtb.com>
John Preuß Mattsson <john.mattsson@ericsson.com>
Karen O'Donoghue <kodonog@pobox.com>
Assigned Area Director:
Roman Danyliw <rdd@cert.org>
Security Area Directors:
Roman Danyliw <rdd@cert.org>
Paul Wouters <paul.wouters@aiven.io>
Mailing list:
Address: jose@ietf.org
To subscribe: https://www.ietf.org/mailman/listinfo/jose
Archive: https://mailarchive.ietf.org/arch/browse/jose/
Group page: https://datatracker.ietf.org/group/jose/
Charter: https://datatracker.ietf.org/doc/charter-ietf-jose/
The original [JSON Object Signing and Encryption (JOSE) working group][1]
standardized JSON-based representations for: Integrity-protected objects
(JSON Web Signatures/JWS, RFC 7515), Encrypted objects (JSON Web
Encryption/JWE, RFC7516), Key representations (JSON Web Key/JWK, RFC 7517),
Algorithm definitions (JSON Web Algorithms/JWA, RFC 7518), and Test vectors
for the above (Examples of Protecting Content Using JSON Object Signing and
Encryption, RFC 7520).
These were used to define the JSON Web Token (JWT) (RFC 7519), which in turn,
has seen widespread deployment in areas as diverse as [digital identity][2]
and [secure telephony][3].
As adoption of these standards to express and communicate sensitive data has
grown, so too has an increasing societal focus on privacy. User consent,
minimal disclosure, and unlinkability are common privacy themes in identity
solutions.
A multi-decade research activity for a sizeable academic and applied
cryptography community has focused on these privacy and knowledge mechanisms
(often referred to as anonymous credentials). Certain cryptographic
techniques developed in this space involve pairing-friendly curves and
zero-knowledge proofs (ZKPs) (to name just a few). Some of the benefits of
ZKP algorithms include unlinkability, selective disclosure, and the ability
to use predicate proofs.
The current container formats defined by JOSE and JWT are not able to
represent data using ZKP algorithms. Among the reasons are that most require
an additional transform or finalize step, many are designed to operate on
sets and not single messages, and the interface to ZKP algorithms has more
inputs than conventional signing algorithms. The reconstituted JOSE working
group will address these new needs, while reusing aspects of JOSE and JWT,
where applicable.
This group is chartered to work on the following goals:
- An Informational document detailing Use Cases and Requirements for new
specifications enabling JSON-based selective disclosure and zero-knowledge
proofs.
- Standards Track document(s) specifying representation(s) of
independently-disclosable integrity-protected sets of data and/or proofs
using JSON-based data structures, which also aims to prevent the ability to
correlate by different verifiers.
- Standards Track document(s) specifying representation(s) of JSON-based
claims and/or proofs enabling selective disclosure of these claims and/or
proofs, and that also aims to prevent the ability to correlate by different
verifiers.
- Standards Track document(s) specifying how to use existing cryptographic
algorithms and defining their algorithm identifiers. The working group will
not invent new cryptographic algorithms.
- Standards Track document(s) specifying how to represent keys for these new
algorithms as JSON Web Keys (JWKs).
- Informational document(s) defining test vectors for these new
specifications.
- Standards Track document(s) defining CBOR-based representations
corresponding to all the above, building upon the COSE and CWT specifications
in the same way that the above build on JOSE and JWT.
One or more of these goals may be combined into a single document, in which
case the concrete milestones for these goals will be satisfied by the
consolidated document(s).
The JOSE working group will also maintain the JOSE standard and facilitate
discussion of clarifications, improvements, and extensions to JWS, JWE, JWA,
and JWK. The WG will evaluate, and potentially adopt, proposed standard
documents dealing with algorithms that would fit the criteria of being IETF
consensus algorithms. Potential candidates would include those algorithms
that have been evaluated by the CFRG and algorithms which have gone through a
public review and evaluation process such as was done for the NIST SHA-3
algorithms. Potential candidates would not include national-standards-based
algorithms that have not gone through a similar public review process. The WG
may also publish informational and BCP documents describing the proper use of
these algorithms in JOSE.
An informal goal of the working group is close coordination with the
[rechartered W3C Verifiable Credentials WG][4], which has taken a dependency
on this work for the second version of its Verifiable Credentials
specification. The working group will also coordinate with the [Selective
Disclosure JWT][5] work in the [OAuth][6] working group, the [Privacy
Pass][7] working group, the [CBOR][8] working group, the [COSE][10] working
group, and the [CFRG][9].
[1]: https://datatracker.ietf.org/doc/charter-ietf-jose/02/
[2]: https://openid.net/connect/
[3]: https://www.ietf.org/blog/stir-action/
[4]: https://www.w3.org/2022/05/proposed-vc-wg-charter.html
[5]:
https://datatracker.ietf.org/doc/draft-ietf-oauth-selective-disclosure-jwt/
[6]: https://datatracker.ietf.org/wg/oauth/about/ [7]:
https://datatracker.ietf.org/wg/privacypass/about/ [8]:
https://datatracker.ietf.org/wg/cbor/about/ [9]:
https://datatracker.ietf.org/rg/cfrg/about/ [10]:
https://datatracker.ietf.org/wg/cose/about/
Milestones:
Jan 2024 - Adopt document registering cryptographic algorithm identifiers
that fully specify the cryptographic operations to be performed (as
proposed standard)
Apr 2024 - Adopt document describing the use of the NIST algorithm ML-KEM
in JOSE (as proposed standard)
Apr 2024 - Adopt document describing the use of the NIST algorithm ML-DSA
in JOSE (as proposed standard)
Apr 2024 - Adopt document describing the use of the NIST algorithm SLH-DSA
in JOSE (as proposed standard)
Apr 2024 - Adopt document describing the use of the NIST algorithm NL-DSA
in JOSE (as proposed standard)