Re: [jose] Consensus call on charter for JSON Web Proofs work

(1) Do you support the charter text?
yes

(2) Are you willing to author or participate in the developed of the WG
drafts?
yes

(3) Are you willing to review the WG drafts?
yes

(4) Are you interested in implementing the WG drafts?
very yes

On Tue, Oct 18, 2022 at 8:38 AM Christian Paquin <cpaquin=
40microsoft.com@dmarc.ietf.org> wrote:

>
>
>    1. Yes, I support the charter text
>    2. Yes
>    3. Yes
>    4. I’m planning to use this WG’s specification to implement various
>    privacy-preserving cryptographic technologies (including U-Prove and BBS+)
>
>
>
> Christian Paquin, Microsoft Research
>
>
>
> *From:* jose <jose-bounces@ietf.org> *On Behalf Of *Karen O'Donoghue
> *Sent:* Monday, October 17, 2022 9:45 PM
> *To:* jose@ietf.org
> *Subject:* [EXTERNAL] [jose] Consensus call on charter for JSON Web
> Proofs work
>
>
>
> You don't often get email from odonoghue=40isoc.org@dmarc.ietf.org. Learn
> why this is important <https://aka.ms/LearnAboutSenderIdentification>
>
>
>
> (1) Do you support the charter text? Or do you have objections or blocking
> concerns (please describe what they might be)?
>
>
>
> If you do support the charter text:
>
> (2) Are you willing to author or participate in the developed of the WG
> drafts?
>
> (3) Are you willing to review the WG drafts?
>
> (4) Are you interested in implementing the WG drafts?
>
>
>
> If you previously spoke of at the BoF, you are welcome to repeat yourself
> here.
>
>
>
> If you have been following along on the mailing list, the charter text
> below is the one that was being polished in GitHub (
> https://github.com/json-web-proofs/json-web-proofs/blob/main/charter-ietf-jose-03.md
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjson-web-proofs%2Fjson-web-proofs%2Fblob%2Fmain%2Fcharter-ietf-jose-03.md&data=05%7C01%7Ccpaquin%40microsoft.com%7C7831ac7266e844051e6608dab0aa62c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638016543111180393%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=raVlxGvhb1M7QfLiRm39Ji8FfbETZ33eldt402GKUEU%3D&reserved=0>).
>
>
>
>
> This call for feedback will end on Monday, 24 October 2022.
>
>
>
> Thanks,
>
> Karen and John
>
>
>
> [1]
> https://datatracker.ietf.org/meeting/interim-2022-jwp-01/materials/minutes-interim-2022-jwp-01-202210121300-00
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fmeeting%2Finterim-2022-jwp-01%2Fmaterials%2Fminutes-interim-2022-jwp-01-202210121300-00&data=05%7C01%7Ccpaquin%40microsoft.com%7C7831ac7266e844051e6608dab0aa62c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638016543111180393%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=oTXmT6Ms95kF8sv7KrgT0j1rOB%2BEuemahkQB5jRh148%3D&reserved=0>
>
> [2] https://notes.ietf.org/notes-ietf-114-jwp#
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnotes.ietf.org%2Fnotes-ietf-114-jwp%23&data=05%7C01%7Ccpaquin%40microsoft.com%7C7831ac7266e844051e6608dab0aa62c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638016543111180393%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Q4gwTZyGq%2FUnJgEmidyGO2srIlOgGFGLzYbqZcnikJE%3D&reserved=0>
>
> [3]
> https://github.com/json-web-proofs/json-web-proofs/blob/main/charter-ietf-jose-03.md
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjson-web-proofs%2Fjson-web-proofs%2Fblob%2Fmain%2Fcharter-ietf-jose-03.md&data=05%7C01%7Ccpaquin%40microsoft.com%7C7831ac7266e844051e6608dab0aa62c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638016543111336611%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=HU0akQK%2BDuL%2FvZiY5%2BVQUzjn8Re5yjFjrQhI0BGNrKY%3D&reserved=0>
>
>
>
> *Draft Charter:*
>
> The original JSON Object Signing and Encryption (JOSE) working group
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-jose%2F02%2F&data=05%7C01%7Ccpaquin%40microsoft.com%7C7831ac7266e844051e6608dab0aa62c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638016543111336611%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=icbIokAMjJw3HUAeVpTtYRmGGkyKSoi3nPzeuzo5usM%3D&reserved=0>
> standardized JSON-based representations for:
>
>    - Integrity-protected objects – JSON Web Signatures (JWS) [RFC 7515
>    <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Frfc%2Frfc7515.html&data=05%7C01%7Ccpaquin%40microsoft.com%7C7831ac7266e844051e6608dab0aa62c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638016543111336611%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3MgZuHpwosSVuBAGdYps5Ot0rPJ0BGU%2FB%2B%2BauWBaNBI%3D&reserved=0>
>    ]
>    - Encrypted objects – JSON Web Encryption (JWE) [RFC 7516
>    <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Frfc%2Frfc7516.html&data=05%7C01%7Ccpaquin%40microsoft.com%7C7831ac7266e844051e6608dab0aa62c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638016543111336611%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=TTGJay8uLgEv08zhRX18qr9SdE%2BWgj46fcEO%2FSFCJ8A%3D&reserved=0>
>    ]
>    - Key representations – JSON Web Key (JWK) [RFC 7517
>    <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Frfc%2Frfc7517.html&data=05%7C01%7Ccpaquin%40microsoft.com%7C7831ac7266e844051e6608dab0aa62c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638016543111336611%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZPICzPhva2nV5KRNouZtpQetfryufhLDGc%2Bniwach2w%3D&reserved=0>
>    ]
>    - Algorithm definitions – JSON Web Algorithms (JWA) [RFC 7518
>    <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Frfc%2Frfc7518.html&data=05%7C01%7Ccpaquin%40microsoft.com%7C7831ac7266e844051e6608dab0aa62c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638016543111336611%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=PCT5kmE%2FVeEGm5mspp%2F7N8FDyayvnEuvjF7%2FsoSJyMY%3D&reserved=0>
>    ]
>    - Test vectors for the above – Examples of Protecting Content Using
>    JSON Object Signing and Encryption [RFC 7520
>    <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Frfc%2Frfc7520.html&data=05%7C01%7Ccpaquin%40microsoft.com%7C7831ac7266e844051e6608dab0aa62c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638016543111336611%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=K8YqvDaJnSjcr3mAQgNl7J67KHQNv8AmaPwPgxMcY1w%3D&reserved=0>
>    ]
>
> These were used to define the JSON Web Token (JWT) [RFC 7519
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Frfc%2Frfc7519.html&data=05%7C01%7Ccpaquin%40microsoft.com%7C7831ac7266e844051e6608dab0aa62c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638016543111336611%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=DroHCfBEoflrPxHVoAfHPm%2B%2Bzdyarn2lknXL1gxitPo%3D&reserved=0>],
> which in turn, has seen widespread deployment in areas as diverse as digital
> identity
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopenid.net%2Fconnect%2F&data=05%7C01%7Ccpaquin%40microsoft.com%7C7831ac7266e844051e6608dab0aa62c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638016543111336611%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=YV3P8pxBDmP2y1s%2BQk0x%2FQkNaWWkyLXVRIIO8Rz%2F%2B4M%3D&reserved=0>
> and secure telephony
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fblog%2Fstir-action%2F&data=05%7C01%7Ccpaquin%40microsoft.com%7C7831ac7266e844051e6608dab0aa62c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638016543111336611%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Srv%2BEjEhK4YvCxA5rSPwr1lnmLlWkQjhaPIwFbVGed4%3D&reserved=0>
> .
>
> Concurrent to the growth of adoption of these standards to express and
> communicate sensitive data has been an increasing societal focus on
> privacy. Common privacy themes in identity solutions are user consent,
> minimal disclosure, and unlinkability.
>
> A multi-decade research activity for a sizeable academic and applied
> cryptography community, often referred to as anonymous credentials, targets
> privacy and knowledge protection. Some of the 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 zero-knowledge
> proof 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 zero-knowledge proof 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 JSON Object Signing and Encryption (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 deliverables:
>
>    - 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).
>    - An Informational document 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).
>
> An informal goal of the working group is close coordination with the rechartered
> W3C Verifiable Credentials WG
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2022%2F05%2Fproposed-vc-wg-charter.html&data=05%7C01%7Ccpaquin%40microsoft.com%7C7831ac7266e844051e6608dab0aa62c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638016543111336611%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=2%2Bo1HD7snONBbcS9B2xgswtyOB8BZV%2FPaL3%2BraDzL5Q%3D&reserved=0>,
> 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
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-oauth-selective-disclosure-jwt%2F&data=05%7C01%7Ccpaquin%40microsoft.com%7C7831ac7266e844051e6608dab0aa62c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638016543111336611%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=db%2BxLwQcR8Fpdxsl7eqia%2BKFmM5YRdFPVz0XXKO0qj0%3D&reserved=0>
> work in the OAuth working group, the Privacy Pass
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-privacypass%2F&data=05%7C01%7Ccpaquin%40microsoft.com%7C7831ac7266e844051e6608dab0aa62c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638016543111336611%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=NzI6ld3J%2Bs5Kw4INn%2B%2FAINOAxPo4DF0WYReiKUu8%2BRs%3D&reserved=0>
> working group, and the CFRG.
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>

-- 
Brent Zundel
Principle Crypto Engineer - Avast