- WG-RIUP - mailman.kantarainitiative.org

Re: [EXTERNAL] RIUP, special out of cycle, WG meeting; Oct 31, 2023 1 PM; apologize for not sending an earlier notice; good intention but forgot!
by Tom (Thomas) Sullivan 07 Nov '23

07 Nov '23

Thanks Jim, Nice work and thank you Tom J. I attached 3 minor edits that are highlighted. I hope everyone can attend so we can get a consensus vote. Tom Thomas E Sullivan, MD Consultant [A close up of a logo Description automatically generated] DrFirst.com, Inc. (978) 729-5075 (M) tsullivan(a)drfirst.com<mailto:tsullivan@drfirst.com> ________________________________ From: kragh65(a)gmail.com <kragh65(a)gmail.com> Sent: Monday, October 30, 2023 3:24 PM To: ThomasClinganJones(a)gmail.com <ThomasClinganJones(a)gmail.com>; nwhysel(a)gmail.com <nwhysel(a)gmail.com>; 'Bev Corwin' <bevcorwin(a)gmail.com>; jeff_brennan(a)sbcglobal.net <jeff_brennan(a)sbcglobal.net>; 'Salvatore D'Agostino' <sal(a)idmachines.com>; 'Catherine Schulten' <catherineschulten(a)yahoo.com>; Tom (Thomas) Sullivan <tsullivan(a)drfirst.com>; michael.magrath(a)kuma.pro <michael.magrath(a)kuma.pro>; 'Simone Alcorn' <salcorn(a)easydynamics.com>; wg-riup(a)kantarainitiative.org <wg-riup(a)kantarainitiative.org> Cc: 'Kay Chopard Cohen' <kay(a)kantarainitiative.org>; 'Amanda Gay' <amanda(a)kantarainitiative.org>; kragh65(a)gmail.com <kragh65(a)gmail.com> Subject: [EXTERNAL] RIUP, special out of cycle, WG meeting; Oct 31, 2023 1 PM; apologize for not sending an earlier notice; good intention but forgot! During our last meeting (Oct 17) the WG agreed to a year end deadline for completing this document and agreed to having an out-of-cycle meeting on the 5th Tuesday of October (this not a trick but a polite request to join our RIUP Please review an updated version of the document and share your comments, questions and recommendations. RIUP's 1st/3rd and (out of cycle) 5th Tuesday Meeting Link: your valued input is important so we can finalize this document by year end. Please join the WG at: https://us06web.zoom.us/j/87499194761?pwd=cmhDTHBXV2VTbFBMZzllMlZVbnFoZz09<https://urldefense.com/v3/__https://us06web.zoom.us/j/87499194761?pwd=cmhDT…> Meeting ID: 874 9919 4761 Passcode: 837815 Dial by your location +1 346 248 7799 US (Houston) +1 646 558 8656 US (New York) +1 669 900 9128 US (San Jose) +1 253 215 8782 US (Tacoma) +1 301 715 8592 US (Washington DC) +1 312 626 6799 US (Chicago) Meeting ID: 874 9919 4761 Passcode: 837815 Project theme: An All Empowering D-ID Ecosystem; No One Left Behind Attached is the updated document Tom sent out last week; please review and be prepared to contribute. Notice of Confidentiality: The information included and/or attached in this electronic mail transmission may contain confidential or privileged information and is intended for the addressee. Any unauthorized disclosure, reproduction, distribution or the taking of action in reliance on the contents of the information is prohibited. If you believe that you have received the message in error, please notify the sender by reply transmission and delete the message without copying or disclosing it.

5 5

Document shared with you: "Digital Identifier Inclusion.docx"
by Tom Jones (via Google Docs) 06 Nov '23

06 Nov '23

I've shared an item with you: Digital Identifier Inclusion.docx https://docs.google.com/document/d/12Dwknikb3pk1QNYSXm9QbNkC8n6d4ZYM/edit?u… It's not an attachment -- it's stored online. To open this item, just click the link above. This is a combined contribution on Google docs so we don't have version conflicts - everyone should have access, let me know if that didn't work. ..tom

2 1

NIST comments and Testimony to Standing Committee on Industry and Technology
by Salvatore D'Agostino 04 Nov '23

04 Nov '23

HI LC, We submitted the attached comments to NIST on their Cybersecurity framework 2.0. Also Sharon Polski (workgroup member and contributor to our proposed Recommendation) gave testimony in the Canadian Parliament on Bill C- 27, (An Act to enact the Consumer Privacy Protection Act, the Personal Information and Data Protection Tribunal Act and the Artificial Intelligence and Data Act) including specifically on the role receipts can play to address what was inaccurately referred to as Consent Fatigue as well as other gaps/issues. Well done Sharon! https://parlvu.parl.gc.ca/Harmony/en/PowerBrowser/PowerBrowserV2?fk=12381376 am presenting the Transparency Performance Scheme and Indicators, Controller Credentials and AuthC at an IEEE Cybersecurity for Next Generation Connectivity Systems in Washington on 15 Nov. https://engagestandards.ieee.org/Protecting-our-Future-Workshop-2023.html Have a great weekend. Sal IDmachines 4 Lamson Place Cambridge, MA 02139-2612 +1 617.201.4809 @idmachines https://idmachines.com Please note our new address. Email, phones, other contacts remain the same. Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. If you have received this email in error, please delete it and advise the sender.

1 0

current draft of DII
by Tom Jones 31 Oct '23

31 Oct '23

based on the meeting of 2023-10-31. Reminder - next meeting is next week. Please prepare comments for that meeting. ..tom

1 0

ACLU and others on the mDL
by Tom Jones 23 Oct '23

23 Oct '23

The following from the report should be considered in our work I believe. https://epic.org/documents/comments-of-epic-aclu-cdt-and-eff-to-the-tsa-on-… The current standards govern how an mDL should transmit information from the phone to the verifying party (e.g. the TSA agent in the airport), and they govern how an mDL reader should verify the validity of the license.11 But the standards do not govern provisioning (how states install an mDL on a phone). They do not provide sufficient protections for data storage on the phone, sufficient guidance for mobile wallet design or user experience, or accountable constraints that would limit invasive or unwarranted requests from abusive mDL verifiers. Standards for the issuing authority to load mDLs onto a phone are in development as the ISO/IEC 23220 series.12 Standards for digital wallet privacy, security, and consent management are even less developed. thx ..Tom (mobile)

3 2

adgenda for Tuesday meeting
by Tom Jones 21 Oct '23

21 Oct '23

My suggestion is to focus on getting as long a list of scenarios where digital inclusion might be compromised. Attached is my attempt to add more detail. I have also started a section on the harms that digital identities might inflict on users. More to come. Please bring your own list of use cases where inclusion must be considered. ..tom

1 0

FW: Register Now! NIST Personal Identity Verification Webinar
by Salvatore D'Agostino 19 Oct '23

19 Oct '23

Just received this. From: NIST Cybersecurity and Privacy Program <csrc.nist(a)service.govdelivery.com> Sent: Thursday, October 19, 2023 2:30 PM To: Salvatore D'Agostino <sal(a)idmachines.com> Subject: Register Now! NIST Personal Identity Verification Webinar Register Now! <https://content.govdelivery.com/attachments/fancy_images/USNIST/2019/04/248 7463/2805250/nist_crop.png> <https://lnks.gd/l/eyJhbGciOiJIUzI1NiJ9.eyJidWxsZXRpbl9saW5rX2lkIjoxMDAsInVy aSI6ImJwMjpjbGljayIsInVybCI6Imh0dHBzOi8vY29udGVudC5nb3ZkZWxpdmVyeS5jb20vYWNj b3VudHMvVVNOSVNUL2J1bGxldGlucy8zNzY0MmExIiwiYnVsbGV0aW5faWQiOiIyMDIzMTAxOS44 NDMyNTUzMSJ9.iGdqCjUnqBleb6eOa76GppVQURGiYY0jmUhu-w4HLIg/s/15856856/br/22862 0664378-l> View As Web Page <https://content.govdelivery.com/attachments/fancy_images/USNIST/2019/09/280 0392/cyber-header_original.png> NIST Cybersecurity and Privacy Program Register for our NIST Webinar! Learn about Revisions to Two of our Identity Special Publications Event Date: November 8, 2023 Time: 1:00 PM-2:30 PM ET Description: The National Institute of Standards and Technology (NIST) will be hosting a webinar to introduce two recently published Public Draft Special Publications (SPs): The 3-part <https://lnks.gd/l/eyJhbGciOiJIUzI1NiJ9.eyJidWxsZXRpbl9saW5rX2lkIjoxMDEsInVy aSI6ImJwMjpjbGljayIsInVybCI6Imh0dHBzOi8vY3NyYy5uaXN0Lmdvdi9wdWJzL3NwLzgwMC83 My9wdDEvNS9pcGQiLCJidWxsZXRpbl9pZCI6IjIwMjMxMDE5Ljg0MzI1NTMxIn0.seMJhhNw-U2c --Vv9Sz2tE2BOO-9LRMBHes-MrOuKRQ/s/15856856/br/228620664378-l> Drafts of SP 800-73 Revision 5, Interfaces for Personal Identity Verification (PIV) and <https://lnks.gd/l/eyJhbGciOiJIUzI1NiJ9.eyJidWxsZXRpbl9saW5rX2lkIjoxMDIsInVy aSI6ImJwMjpjbGljayIsInVybCI6Imh0dHBzOi8vY3NyYy5uaXN0Lmdvdi9wdWJzL3NwLzgwMC83 OC81L2lwZCIsImJ1bGxldGluX2lkIjoiMjAyMzEwMTkuODQzMjU1MzEifQ.SUXxWpKf0ol1P7YrP v2vA8r3mschS0E1dPXaRnyCskY/s/15856856/br/228620664378-l> Draft SP 800-78 Revision 5, Cryptographic Algorithms and Key Sizes for Personal Identity Verification. These publications are complements to FIPS 201-3, which defines the requirements and characteristics of government-wide interoperable identity credentials used by federal employees and contractors. The workshop will discuss the necessary changes made to the PIV card, its credentials, and cryptographic capability to align with FIPS 201-3. Full Agenda: 1:00 PM-1:05 PM - Introduction and Welcome 1:05 PM-1:15 PM - Introduction to the PIV Standard 1:15 PM-1:45 PM - Changes to Draft SP 800-73 Revision 5 1:45 PM-2:15 PM - Changes to Draft SP 800-78 Revision 5 2:15 PM-2:30 PM - Key Dates/Next Steps/Closing Visit the event page to register and learn more about the workshop. If you have any questions, please reach out to our team at <mailto:piv_comments@nist.gov> piv_comments(a)nist.gov. <https://lnks.gd/l/eyJhbGciOiJIUzI1NiJ9.eyJidWxsZXRpbl9saW5rX2lkIjoxMDMsInVy aSI6ImJwMjpjbGljayIsInVybCI6Imh0dHBzOi8vd3d3Lm5jY29lLm5pc3QuZ292L2dldC1pbnZv bHZlZC9hdHRlbmQtZXZlbnRzL3BlcnNvbmFsLWlkZW50aXR5LXZlcmlmaWNhdGlvbi13ZWJpbmFy IiwiYnVsbGV0aW5faWQiOiIyMDIzMTAxOS44NDMyNTUzMSJ9._nMm1VHJrw9Uhpqc62B_thJQagt qnBQ-JE8pRAVfzec/s/15856856/br/228620664378-l> Register Now NIST Cybersecurity and Privacy Program Questions/Comments about this notice: <mailto:piv_comments@nist.gov> piv_comments(a)nist.gov NCCoE Website questions: <mailto:nccoe@nist.gov> nccoe(a)nist.gov Connect with us <https://lnks.gd/l/eyJhbGciOiJIUzI1NiJ9.eyJidWxsZXRpbl9saW5rX2lkIjoxMDQsInVy aSI6ImJwMjpjbGljayIsInVybCI6Imh0dHBzOi8vd3d3LmZhY2Vib29rLmNvbS9OSVNUIiwiYnVs bGV0aW5faWQiOiIyMDIzMTAxOS44NDMyNTUzMSJ9.qaJ4eZw_SnEKtyv-qr55XroaE-Hqvb3hP7V 5DVDnOGU/s/15856856/br/228620664378-l> <https://lnks.gd/l/eyJhbGciOiJIUzI1NiJ9.eyJidWxsZXRpbl9saW5rX2lkIjoxMDUsInVy aSI6ImJwMjpjbGljayIsInVybCI6Imh0dHBzOi8vdHdpdHRlci5jb20vTklTVCIsImJ1bGxldGlu X2lkIjoiMjAyMzEwMTkuODQzMjU1MzEifQ.ankJWpMpZIcGzigZC360Vx7Oq-QZ83TTJKmyv2eHN tk/s/15856856/br/228620664378-l> <https://lnks.gd/l/eyJhbGciOiJIUzI1NiJ9.eyJidWxsZXRpbl9saW5rX2lkIjoxMDYsInVy aSI6ImJwMjpjbGljayIsInVybCI6Imh0dHBzOi8vd3d3LnlvdXR1YmUuY29tL05JU1QiLCJidWxs ZXRpbl9pZCI6IjIwMjMxMDE5Ljg0MzI1NTMxIn0.nDNbFKcS6tcIzUNkesJUykjc6vX7bJq4yMY2 FSe3dys/s/15856856/br/228620664378-l> <https://lnks.gd/l/eyJhbGciOiJIUzI1NiJ9.eyJidWxsZXRpbl9saW5rX2lkIjoxMDcsInVy aSI6ImJwMjpjbGljayIsInVybCI6Imh0dHBzOi8vd3d3LmxpbmtlZGluLmNvbS9jb21wYW55L25p c3QiLCJidWxsZXRpbl9pZCI6IjIwMjMxMDE5Ljg0MzI1NTMxIn0.rE5a_oupVR1rFt--KtDuUtqP pMCRn8vU5MtxnoVsVnY/s/15856856/br/228620664378-l> <https://lnks.gd/l/eyJhbGciOiJIUzI1NiJ9.eyJidWxsZXRpbl9saW5rX2lkIjoxMDgsInVy aSI6ImJwMjpjbGljayIsInVybCI6Imh0dHBzOi8vd3d3Lmluc3RhZ3JhbS5jb20vbmlzdC8iLCJi dWxsZXRpbl9pZCI6IjIwMjMxMDE5Ljg0MzI1NTMxIn0.jYA7j9lArNiOjucwTovtAzLCs091I4eT YZoYeRjJZYU/s/15856856/br/228620664378-l> Received this email from a friend? <https://lnks.gd/l/eyJhbGciOiJIUzI1NiJ9.eyJidWxsZXRpbl9saW5rX2lkIjoxMDksInVy aSI6ImJwMjpjbGljayIsInVybCI6Imh0dHBzOi8vcHVibGljLmdvdmRlbGl2ZXJ5LmNvbS9hY2Nv dW50cy9VU05JU1Qvc3Vic2NyaWJlci9uZXc_dG9waWNfaWQ9VVNOSVNUXzEiLCJidWxsZXRpbl9p ZCI6IjIwMjMxMDE5Ljg0MzI1NTMxIn0.DDxB_yWmqHL8BemJUuc9p7Prs3p8-I3wXTqDMc0CUq4/ s/15856856/br/228620664378-l> Subscribe here. <https://lnks.gd/l/eyJhbGciOiJIUzI1NiJ9.eyJidWxsZXRpbl9saW5rX2lkIjoxMTAsInVy aSI6ImJwMjpjbGljayIsInVybCI6Imh0dHBzOi8vd3d3Lm5pc3QuZ292L2l0bCIsImJ1bGxldGlu X2lkIjoiMjAyMzEwMTkuODQzMjU1MzEifQ.8EaTVnyEWPKfBR5gBfqoSIouIMxubKpOGsse6sr5P Iw/s/15856856/br/228620664378-l> Subscriber services: <https://lnks.gd/l/eyJhbGciOiJIUzI1NiJ9.eyJidWxsZXRpbl9saW5rX2lkIjoxMTEsInVy aSI6ImJwMjpjbGljayIsInVybCI6Imh0dHBzOi8vcHVibGljLmdvdmRlbGl2ZXJ5LmNvbS9hY2Nv dW50cy9VU05JU1Qvc3Vic2NyaWJlci9lZGl0P3ByZWZlcmVuY2VzPXRydWUjdGFiMSIsImJ1bGxl dGluX2lkIjoiMjAyMzEwMTkuODQzMjU1MzEifQ.I96vs7GTxOcGZK11UTrj535SrnJNZm-F8uRj1 xmAwYk/s/15856856/br/228620664378-l> Manage Preferences | <https://lnks.gd/l/eyJhbGciOiJIUzI1NiJ9.eyJidWxsZXRpbl9saW5rX2lkIjoxMTIsInVy aSI6ImJwMjpjbGljayIsInVybCI6Imh0dHBzOi8vcHVibGljLmdvdmRlbGl2ZXJ5LmNvbS9hY2Nv dW50cy9VU05JU1Qvc3Vic2NyaWJlci9lZGl0P3ByZWZlcmVuY2VzPXRydWUjdGFiMSIsImJ1bGxl dGluX2lkIjoiMjAyMzEwMTkuODQzMjU1MzEifQ.S0MWx6TLC2NjpNDAW6jRfTjnM7ZxsC5W7H81e xyP5_U/s/15856856/br/228620664378-l> Unsubscribe | <https://lnks.gd/l/eyJhbGciOiJIUzI1NiJ9.eyJidWxsZXRpbl9saW5rX2lkIjoxMTMsInVy aSI6ImJwMjpjbGljayIsInVybCI6Imh0dHBzOi8vc3Vic2NyaWJlcmhlbHAuZ292ZGVsaXZlcnku Y29tLyIsImJ1bGxldGluX2lkIjoiMjAyMzEwMTkuODQzMjU1MzEifQ.i0lA5WdBqz7ec4eNkP-VR fFZuI8iV-mo3cDomH11yCM/s/15856856/br/228620664378-l> Help _____ If you have questions or problems with the subscription service, please contact subscriberhelp.govdelivery.com <https://lnks.gd/l/eyJhbGciOiJIUzI1NiJ9.eyJidWxsZXRpbl9saW5rX2lkIjoxMTQsInVy aSI6ImJwMjpjbGljayIsInVybCI6Imh0dHBzOi8vc3Vic2NyaWJlcmhlbHAuZ292ZGVsaXZlcnku Y29tLyIsImJ1bGxldGluX2lkIjoiMjAyMzEwMTkuODQzMjU1MzEifQ.zaakIPw4S07-6Nkab9_CP zXLivQbPqGcOqOqCwS_sdo/s/15856856/br/228620664378-l> . Technical questions? Contact inquiries(a)nist.gov <mailto:inquiries@nist.gov> . (301) 975-NIST (6478). This service is provided to you at no charge by National Institute of Standards and Technology (NIST). 100 Bureau Drive, Stop 1070 . Gaithersburg, MD 20899 . 301-975-6478 <https://lnks.gd/l/eyJhbGciOiJIUzI1NiJ9.eyJidWxsZXRpbl9saW5rX2lkIjoxMTUsInVy aSI6ImJwMjpjbGljayIsInVybCI6Imh0dHBzOi8vc3Vic2NyaWJlcmhlbHAuZ3JhbmljdXMuY29t LyIsImJ1bGxldGluX2lkIjoiMjAyMzEwMTkuODQzMjU1MzEifQ.jgG9eFCvmWRqMFlaK1YLCgCSP _imR-4XIT2ZsBugI_Y/s/15856856/br/228620664378-l> <https://links.govdelivery.com/track?enid=ZWFzPTEmYnVsbGV0aW5yZWNpcGllbnRpZD 0yMjg2MjA2NjQzNzgtbCZzdWJzY3JpYmVyaWQ9MTU4NTY4NTYmbXNpZD0mYXVpZD0mbWFpbGluZ2 lkPTIwMjMxMDE5Ljg0MzI1NTMxJm1lc3NhZ2VpZD1NREItUFJELUJVTC0yMDIzMTAxOS44NDMyNT UzMSZkYXRhYmFzZWlkPTEwMDEmdHlwZT1vcGVuJnNlcmlhbD0xNjg2MjIwNCZlbWFpbGlkPXNhbE BpZG1hY2hpbmVzLmNvbSZ1c2VyaWQ9c2FsQGlkbWFjaGluZXMuY29tJnRhcmdldGlkPSZmbD0mbX ZpZD0mZXh0cmE9JiYm>

1 0

update DII doc for comment
by Tom Jones 17 Oct '23

17 Oct '23

updated at meeting of 2023-10-17 ..tom

1 0

RIUP WG meeting tomorrow, Oct 17, 1 PM EDT, 23,
by jim kragh 17 Oct '23

17 Oct '23

Please review the updated version and be prepared to share your comments, questions and recommendations. *RIUP's 1st/3rd Tuesday Meeting Link:* https://us06web.zoom.us/j/87499194761?pwd=cmhDTHBXV2VTbFBMZzllMlZVbnFoZz09 Meeting ID: 874 9919 4761 Passcode: 837815 Dial by your location +1 346 248 7799 US (Houston) +1 646 558 8656 US (New York) +1 669 900 9128 US (San Jose) +1 253 215 8782 US (Tacoma) +1 301 715 8592 US (Washington DC) +1 312 626 6799 US (Chicago) Meeting ID: 874 9919 4761 Passcode: 837815 Project theme: *An All Empowering dID Ecosystem; No One Left Behind * Attached is the updated document Tom sent out last week; please review the updated version and be prepared to contribute. It is time to start thinking about elections and reviewing our charter; have asked Noreen for some assistance. MAY ALL HAVE A RESTFUL EVENING, Jim

2 1

Digital Identifier Inclusion document.
by Tom Jones 11 Oct '23

11 Oct '23

This document was revised at the last meeting of RIUP which was lightly attended and augmented with flows generated in the ANCR wg. Since we will not meet this week, can i ask for a review and individual input prior to the meeting next week? thanks ..tom

2 1

here is a list of persona / use cases
by Tom Jones 09 Oct '23

09 Oct '23

I was pretty impressed. One thing I missed is that "I am the legal age to buy some controlled substance". or another "I am able to access a controlled-access venue". Does anyone else notice anything missing? Let's discuss it on Tuesday. https://www.id-day.org/2023campaign?ref=blog.identity.foundation ..tom

2 1

RIUP WG meeting tomorrow, Oct 3, 2023; 1 PM EDT, please join the WG discussion; NOTE: a new meeting LINK
by jim kragh 02 Oct '23

02 Oct '23

*RIUP's 1st/3rd Tuesday Meeting Link:* https://us06web.zoom.us/j/87499194761?pwd=cmhDTHBXV2VTbFBMZzllMlZVbnFoZz09 Meeting ID: 874 9919 4761 Passcode: 837815 Dial by your location +1 346 248 7799 US (Houston) +1 646 558 8656 US (New York) +1 669 900 9128 US (San Jose) +1 253 215 8782 US (Tacoma) +1 301 715 8592 US (Washington DC) +1 312 626 6799 US (Chicago) Meeting ID: 874 9919 4761 Passcode: 837815 Project theme: *An All Empowering dID Ecosystem; No One Left Behind * *Tom J. *sent out a link this afternoon ref: a Kantara working draft document entitled:* Digital Identifier Inclusion *dated 2023-09-29 link address: https://mail.google.com/mail/u/0?ui=2&ik=5ec2d9d465&attid=0.1&permmsgid=msg… Items to discuss: Annual Charter review and election of WG chairs along with a PPT (1or 2 frames for annual meeting and trade shoes. May all have a restful evening, Jim

1 0

draft of DII for discussion tomorrow
by Tom Jones 02 Oct '23

02 Oct '23

The sections on 1. Problem 2. Use cases are new and can be discussed. Others are welcome to add additional input. ..tom

1 0

FDA has announced regulation on medical devices
by Tom Jones 30 Sep '23

30 Sep '23

https://buff.ly/3vo7Zf7 Our attempt to get the CDC to do this for medical data was ignored. I no longer have much interest in medical devices, but maybe others do? thx ..Tom (mobile)

1 0

Fwd: Webinar host invited you to be panelist for My Webinar
by Salvatore D'Agostino 23 Sep '23

23 Sep '23

Here is the link to the hackathon today and tomorrow morning.. IDmachines 1264 Beacon Street, #5 Brookline, MA 02446 +1 617.201.4809 @idmachines ________________________________ From: Zoom <no-reply(a)zoom.us> Sent: Saturday, September 23, 2023 9:36:46 AM To: Salvatore D'Agostino <sal(a)idmachines.com> Subject: Webinar host invited you to be panelist for My Webinar [http://us02web.zoom.us/w_p/8WmmtMhDT_CD-p2DxWZNhw/8652212f-596f-4e8f-ba74-4…] Hi Salvatore D'Agostino, Webinar host invited you to be panelist for My Webinar. My Webinar Date & Time Sep 23, 2023 10:00 AM Montreal Webinar ID 861 2396 6915 Participant ID 605271 Passcode 0230506 Add to: [https://us02st3.zoom.us/static/6.3.15784/image/new/google.png] Google Calendar <https://us02web.zoom.us/webinar/tZIsdeqhqD0jG9GFXHHmcV_4ULsP9HSVpFpE/calend…> [https://us02st3.zoom.us/static/6.3.15784/image/new/outlook.png] Outlook Calendar(.ICS) <https://us02web.zoom.us/webinar/tZIsdeqhqD0jG9GFXHHmcV_4ULsP9HSVpFpE/ics?us…> [https://us02st3.zoom.us/static/6.3.15784/image/new/yahoo.png] Yahoo Calendar <https://us02web.zoom.us/webinar/tZIsdeqhqD0jG9GFXHHmcV_4ULsP9HSVpFpE/ics?us…> Please submit any questions to: sharon.polsky(a)aminacorp.ca Thank you! WAYS TO JOIN THIS WEBINAR * Join from PC, Mac, iPad, or Android Join Webinar <https://us02web.zoom.us/w/86123966915?tk=MVbL9-TlSZ6d33UL_Qbp-tJKpZcRtnu5uz…> If the button above does not work, paste this into your browser: https://us02web.zoom.us/w/86123966915?tk=MVbL9-TlSZ6d33UL_Qbp-tJKpZcRtnu5uz… To keep this webinar secure, do not share this link publicly. * Join via audio Canada: +12042727920,,86123966915#<tel:+12042727920,,86123966915#> or +14388097799,,86123966915#<tel:+14388097799,,86123966915#> Or, dial: Canada: +1 204 272 7920 or +1 438 809 7799 or +1 587 328 1099 or +1 613 209 3054 or +1 647 374 4685 or +1 647 558 0588 or +1 778 907 2071 US: +1 267 831 0333 or +1 301 715 8592 or +1 720 928 9299 or +1 206 337 9723 United Kingdom: +44 203 901 7895 More International numbers<https://us02web.zoom.us/u/keJ2aM36pw> Webinar ID: 861 2396 6915 Passcode: 0230506 [https://us02st3.zoom.us/static/6.3.15784/image/new/twitter.png] <https://twitter.com/zoom_us> [https://us02st3.zoom.us/static/6.3.15784/image/new/linkedin.png] <https://www.linkedin.com/company/zoom-video-communications/> [https://us02st3.zoom.us/static/6.3.15784/image/new/zoomblog.png] <https://blog.zoom.us/> +1.888.799.9666<tel:1-888-799-9666> Copyright ©2023 Zoom Video Communications, Inc. Visit Zoom.us<http://zoom.us> 55 Almaden Blvd San Jose, CA 95113<https://www.google.com/maps/place/55+Almaden+Blvd,+San+Jose,+CA+95113/@37.3…> [https://us02st3.zoom.us/static/6.3.15784/image/new/ZoomLogo3.png] <https://zoom.us>

1 0

Workshop Link
by Salvatore D'Agostino 22 Sep '23

22 Sep '23

To make it easy to attend and bypass registration Event Details - When: Sep 22, 2023 08:30 AM Montreal Topic: 0PN Digital Symposium — Montreal — 22 September 2023 Please click the link below to join the webinar: https://us02web.zoom.us/j/83183657519?pwd=NmtTT3NGQk90a2tBa3A2OHN6dGZidz09 Passcode: 0230506 Or One tap mobile : Canada: IDmachines 1264 Beacon Street, #5 Brookline, MA 02446 +1 617.201.4809 @idmachines

1 0

Canceled event: RIUP WG @ Weekly from 1pm to 2pm on Tuesday (EST) (wg-riup@kantarainitiative.org)
by kragh65＠gmail.com 22 Sep '23

22 Sep '23

This event has been canceled. RIUP WG Weekly from 1pm to 2pm on Tuesday Eastern Time - New York Location Join Zoom Meeting https://zoom.us/j/97049100495?pwd=TmRDM1FYR3krMnNXRnl6cTVndUEyZz09 https://www.google.com/maps/search/Join+Zoom+Meeting+https:%2F%2Fzoom.us%2F… Resilient Identifiers for Underserved Populations (RIUP) Work Group - Meeting weekly on Tuesday's at 1PM EST Topic: RIUP Join Zoom Meeting https://zoom.us/j/97049100495?pwd=TmRDM1FYR3krMnNXRnl6cTVndUEyZz09 Meeting ID: 970 4910 0495 Passcode: 351971 One tap mobile +13462487799,,97049100495#,,,,*351971# US (Houston) +16465588656,,97049100495#,,,,*351971# US (New York) Dial by your location +1 346 248 7799 US (Houston) +1 646 558 8656 US (New York) +1 669 900 9128 US (San Jose) +1 253 215 8782 US (Tacoma) +1 301 715 8592 US (Washington DC) +1 312 626 6799 US (Chicago) Meeting ID: 970 4910 0495 Passcode: 351971 Find your local number: https://zoom.us/u/ad4U40uoYU Organizer kragh65(a)gmail.com kragh65(a)gmail.com Guests kragh65(a)gmail.com - organizer kimberly(a)kantarainitiative.org Noreen Whysel. Brett wg-riup(a)kantarainitiative.org Kantara Staff Tom (Thomas) Sullivan ~~//~~ Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this email because you are an attendee on the event. To stop receiving future updates for this event, decline this event. Forwarding this invitation could allow any recipient to send a response to the organizer, be added to the guest list, invite others regardless of their own invitation status, or modify your RSVP. Learn more https://support.google.com/calendar/answer/37135#forwarding

1 0

RIUP WG has a new access link; our next meeting will be Oct 3rd, 1 PM
by jim kragh 19 Sep '23

19 Sep '23

*Attention: RIUP WG* will be using this *new* Kantara link: (I will resend this again with my meeting announcement). https://us06web.zoom.us/j/87499194761?pwd=cmhDTHBXV2VTbFBMZzllMlZVbnFoZz09 Your input is requested: At today's RIUP meeting Tom Jones, document author, reviewed and welcomed WG input on the initial draft of the 'Digital Identifier Inclusion" paper the RIUP WG, agreed to publish as a Kantara Initiative doc at our last meeting. Just as a refresher, here is the PPT we have been discussing during our last 2 WG meetings and where Tom has has been working on and interacting with the Open Wallet Foundation https://docs.google.com/presentation/d/14S4Jz4-lYDShL0fI2h4go3yPMCW6DbzNtUY…

1 0

working doc
by Tom Jones 19 Sep '23

19 Sep '23

from today's meeting. comments are always welcomed. ..tom

1 0

RIUP WG meeting tomorrow, 1 PM EDT, Sept 19 We will be working on a theme or title for our project: put your creative thinking hat on
by jim kragh 19 Sep '23

19 Sep '23

Project theme?: *An All Empowering dID Ecosystem; No One Left Behind * *Resilient Identifiers for Underserved Populations Work Group (**R**IUP* * -WG)* *Tuesday Sept 5, 2023:* *Zoom **Meeting Link* https://zoom.us/j/97049100495?pwd=TmRDM1FYR3krMnNXRnl6cTVndUEyZz09 *Meeting ID:* 970 4910 0495 * Passcode*: 351 971 +13462487799,,97049100495#,,,,*351971# US (Houston) +16465588656,,97049100495#, *351971# US (New York) Here the deck we discussed i have been working on with the Open Wallet Foundation Inclusion which started here https://docs.google.com/presentation/d/14S4Jz4-lYDShL0fI2h4go3yPMCW6DbzNtUY… Tom will lead our discussion and in doing so please review again the link above on inclusion.......that is every unique functioning individual or their appointed guardian. Have a nice evening, Jim

4 3

Zoom link for today
by Amanda Gay 19 Sep '23

19 Sep '23

Hi all: Please use this link: https://us06web.zoom.us/j/87499194761?pwd=cmhDTHBXV2VTbFBMZzllMlZVbnFoZz09 Email if you have issues! Best, -A -- *Amanda Gay | **Administrative** Coordinator* *Twitter:* @KantaraNews *LinkedIn:* @KantaraInitiative

1 0

Re: [Openid-specs-digital-credentials-protocols] Security and Trust document
by Tom Jones 17 Sep '23

17 Sep '23

This is a message that was shared on the digital creds list. I found it interesting and worthy of the attention of the Resilient Identifiers for Underserved Populations. I hope to have a start at a document for our meeting on tuesday. ..tom On Sun, Sep 17, 2023 at 3:24 AM Jo Spencer via Openid-specs-digital-credentials-protocols < openid-specs-digital-credentials-protocols(a)lists.openid.net> wrote: > Hi Tom and Team, > > I think you're spot on, Tom. "Guardianship" is a topic that John Phillips > and I [Sezoo, based in Melbourne, Australia] have been working on, within > the W3C VC-based environment for some time. The W3C VC data model caters to > the subject and holder being different, very well. > > It's been a particular "passion" capability of ours that digital > interactions can forget (probably because it's typically quite complex for > 2-party digital interactions). We believe that delegation or guardianship > is a critical feature of a trusted interaction mechanism (and protocol), > and has to be standardised. Whilst we focused on guardianship, delegation, > support or ownership are similar relationship based considerations that > should also be able to be supported in a consistent model. > > Our work and experience on providing verifiable evidence of guardianship > rights and duties and supported access to online content started in 2019 > when John and I were co-chairs on the Sovrin Guardianship Working Group for > the development of an Implementation Guide and Requirements document for > Guardianship using W3C Verifiable Credentials. The results published in > 2021 can be found here: > > Implementation Guide: > https://drive.google.com/file/d/1vBePVx8n3MRDWcePkwVDya9ab4BHEyU_/view?usp=… > Technical Requirements: > https://drive.google.com/file/d/1M21PznPAd0H6z1t4ODl-jiEoXZjEhwcb/view?usp=… > > These links and the introduction/explanation can be found here: > https://sovrin.org/a-deeper-understanding-of-implementing-guardianship/ > > As a part of these initiatives, a mental model for guardianship was > developed with collaboration with TNO in NL and published under the > ESSIFLabs initiative: > https://essif-lab.github.io/framework/docs/terms/pattern-guardianship/. > > More recently, we've supported the update of the Sovrin Whitepaper on > Guardianship - > https://sovrin.org/wp-content/uploads/Guardianship-Whitepaper-V2.0.pdf - > which may be a very good starting document for those that are interested. > > We developed a Guardianship addendum for the Good Health Pass > Collaborative Blueprint <https://www.goodhealthpass.org/blueprint> which > considered the challenges of supported travel, made more important during > the Covid pandemic. The realisation during that activity was that > guardianship and supported mechanisms are often informal and based on > social expectations, rather than digital credentials. Enabling supported > scenarios using digital credentials into the whole process of travel was a > significant challenge and probably more than the GHPC could influence. > > John Phillips and I have published a number of further papers and work on > this topic, all of which are available on our website ( > https://www.sezoo.digital/resources/) and our LinkedIn profiles ( > https://www.linkedin.com/in/11dot2/recent-activity/articles/ and > https://www.linkedin.com/in/jospencer-1pg/recent-activity/articles/) > > It's critical that any interaction protocol supports delegation, support > or guardianship and clearly articulates the difference between the Holder > and Subject. Impersonation has to be avoided as this is the antithesis of > trusted digital interactions. The combined presentation of credentials from > multiple sources (e.g. a guardianship VC from a government entity and other > credentials from other service providers) would appear to be central to > these types of solutions. We too have been concerned that the OIDC4VP > protocols are deficient in this, but we'd be keen to learn more from those > who are closer to the details. But we are very keen to promote these > considerations in solution design activities. > > Of course, I'd be happy to talk about this topic in the group (if this can > be possible in an Australian-friendly timeslot), or directly. > > Cheers, Jo > *Jo Spencer* > Co-Founder | Digital Trust Evangelist | *Sezoo* > Partner | Payments | Banking | Architecture | *460degrees* > > M: +61 (0) 433 774 729 > E: jo(a)sezoo.digital > L: https://www.linkedin.com/in/jospencer-1pg/ > T: https://twitter.com/spencerjed > > Sezoo acknowledges the Traditional Owners of the country throughout > Australia and their continuing connection to land, sea and community. We > pay our respects to them, their cultures and to Elders past, present and > emerging. > > > > On Fri, 15 Sept 2023 at 04:38, Tom Jones via > Openid-specs-digital-credentials-protocols < > openid-specs-digital-credentials-protocols(a)lists.openid.net> wrote: > >> >> All parties communicate with each other using a set of protocols, or just >> "protocol" in the following. In the case of OpenID4VP, the protocols are >> OpenID for Verifiable Credential Issuance [@!OpenID.VCI] and OpenID for >> Verifiable Presentations [@!OpenID.VP], with an optional use of SIOP v2 >> [@!OpenID.SIOPv2]. >> thx ..Tom (mobile) >> >> On Thu, Sep 14, 2023, 4:17 AM David Chadwick < >> d.w.chadwick(a)truetrust.co.uk> wrote: >> >>> Hi Tom >>> >>> if you read my proposed text I think it caters for the use cases you are >>> suggesting. If it does not, can you say why not please >>> >>> thanks >>> >>> David >>> On 14/09/2023 05:35, Tom Jones wrote: >>> >>> you guys are missing the point - i guess i was not clear. >>> >>> The current CBP-ONE app is used at the border of the US to schedule >>> sessions to acquire asylum. Similarly the child trying to get access to the >>> US may need creds. These children are the subjects of credential. They do >>> not hold smartphones which are held by (for example) their father as >>> guardian. In the US 51 million people do not have smart phones but may need >>> digital creds for one reason or another. I suspect that in many countries >>> the numbers are even more dire. >>> >>> If the wallet cannot handle the case where the subject is not the >>> holder, then it should not be considered adequate to hold government creds >>> because of the many eligible people \who cannot be accommodated. >>> >>> Somehow this spec (and the rest of the VC specs) needs to address the >>> problem where the holder and the subject are not the same person. >>> >>> ..tom >>> >>> >>> On Wed, Sep 13, 2023 at 3:32 AM David Chadwick via >>> Openid-specs-digital-credentials-protocols < >>> openid-specs-digital-credentials-protocols(a)lists.openid.net> wrote: >>> >>>> >>>> On 12/09/2023 20:53, Joseph Heenan via >>>> Openid-specs-digital-credentials-protocols wrote: >>>> >>>> Hi Tom >>>> >>>> Focussing on this particular document, is your concern resolved if >>>> sentences like this: >>>> >>>> "Identity of Holder: A Verifier can trust that the party presenting the >>>> claims in a session with the Verifier is (controlled by) the subject of the >>>> claims.” >>>> >>>> (From >>>> https://github.com/vcstuff/oid4vc-security-and-trust/blob/main/draft-oid4vc… >>>> ) >>>> >>>> are replaced with something like this: >>>> >>>> "Identity of Holder: A Verifier can trust that the party presenting the >>>> claims in a session with the Verifier is (controlled by) the party that the >>>> credential was intended to be issued to.” >>>> >>>> I don't think the above is precise enough, since the credential could >>>> have been passed from the first holder to the second holder and then to the >>>> verifier. Therefore I propose >>>> >>>> "Identity of Holder: A Verifier can trust that the party presenting the >>>> claims in a session with the Verifier is the party who is authorised to >>>> hold the credential (from the Verifier's perspective).” >>>> >>>> The text in parentheses is important for at least the following reasons >>>> >>>> a) the credential could be a bearer credential >>>> >>>> b) the verifier may be willing to completely ignore who the issuer >>>> intended the credential to be presented by and therefore will allow anyone >>>> to present it, e.g. because the verifier gains a benefit from entering into >>>> a session with the holder. >>>> >>>> We have real life examples the above in the physical world. >>>> >>>> Kind regards >>>> >>>> David >>>> >>>> >>>> ? >>>> >>>> Thanks >>>> >>>> Joseph >>>> >>>> On 12 Sep 2023, at 16:06, Tom Jones via >>>> Openid-specs-digital-credentials-protocols >>>> <openid-specs-digital-credentials-protocols(a)lists.openid.net> >>>> <openid-specs-digital-credentials-protocols(a)lists.openid.net> wrote: >>>> >>>> One major problem with the OAuth model and this contribution is the >>>> conflation of the subject and the holder. >>>> To be inclusive these two roles may be entirely different entities. >>>> It seems to be that this conflation must be excised if OAuth is to be >>>> acceptected as the digital credential model to be used for government >>>> supplied rights and privileges. >>>> >>>> ..tom >>>> >>>> >>>> On Mon, Sep 11, 2023 at 8:14 AM Daniel Fett via >>>> Openid-specs-digital-credentials-protocols < >>>> openid-specs-digital-credentials-protocols(a)lists.openid.net> wrote: >>>> >>>>> Hi all, >>>>> >>>>> I'd like to contribute the "Security and Trust" document to the DCP >>>>> WG: https://github.com/vcstuff/oid4vc-security-and-trust >>>>> >>>>> It has been discussed earlier, but had no official status so far. >>>>> >>>>> -Daniel >>>>> -- >>>>> Openid-specs-digital-credentials-protocols mailing list >>>>> Openid-specs-digital-credentials-protocols(a)lists.openid.net >>>>> >>>>> https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-… >>>>> >>>> -- >>>> Openid-specs-digital-credentials-protocols mailing list >>>> Openid-specs-digital-credentials-protocols(a)lists.openid.net >>>> >>>> https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-… >>>> >>>> >>>> >>>> -- >>>> Openid-specs-digital-credentials-protocols mailing list >>>> Openid-specs-digital-credentials-protocols(a)lists.openid.net >>>> >>>> https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-… >>>> >>> -- >> Openid-specs-digital-credentials-protocols mailing list >> Openid-specs-digital-credentials-protocols(a)lists.openid.net >> >> https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-… >> > -- > Openid-specs-digital-credentials-protocols mailing list > Openid-specs-digital-credentials-protocols(a)lists.openid.net > > https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-… >

1 0

Makeup call TODAY Sept 12 at 1 PM EDT
by Noreen Whysel 12 Sep '23

12 Sep '23

1 0

Makeup call TODAY Sept 12 at 1 PM EDT
by Noreen Whysel 12 Sep '23

12 Sep '23

1 0

Kantara's RIUP Co-Chair is inviting you to a make-up Conference Call Zoom meeting this Tuesday at 1 PM EST.
by jim kragh 12 Sep '23

12 Sep '23

*Topic: RIUP Make-up Conference Call Co-Chair Jim Kragh Time: Sep 12, 2023 01:00 PM Eastern Time (US and Canada)* Join Zoom Meeting * (THIS LINK IS AN OUT OF CYCLE, ONE TIME USE ZOOM MEETING LINK FOR THIS CALL ONLY)* https://us06web.zoom.us/j/81066622226?pwd=L3RiZkFKT0xWbWhXbVB6Y1ZrSFRMUT09 * Meeting ID: 810 6662 2226 Passcode: 446287**_* I hope you all had a nice weekend. Please join me in a makeup RIUP con-call. We will continue with Tom Jones on the "Open Wallet' discussion......here are the links he shared: Here are the two decks i have been working on with the Open Wallet > Foundation > Inclusion which started here > https://docs.google.com/presentation/d/14S4Jz4-lYDShL0fI2h4go3yPMCW6DbzNtUY… > Wallets trusted by gov't > https://docs.google.com/presentation/d/12oKDCb5jBBZIobHXJWwNNV_YbMzvVRn5w2G… > *If time permits we will continue with the message I shared last week.* *The National Institute of Standards and Technology is asking for collaborators to participate in a new project on how to "accelerate" the adoption of digital identities for mobile devices using two international standards. August 30, 2023* NIST is seeking several categories of collaborators – “Issuing Authorities, digital identity solutions providers, Verifiers (also known as Relying Parties), and third-party trust service providers” – to participate in developing and testing implementation schemes, according to the *project description* <https://www.nccoe.nist.gov/sites/default/files/2023-06/mdl-project-descript…> published in June. https://www.nccoe.nist.gov/sites/default/files/2023-06/mdl-project-descript… ABSTRACT There are several new digital credentials-based standards emerging and they are all silos operating in specific environments and written for specific contexts. As such, there is a lack of foundational, strongly verifiable, and trustable digital credentials available to make transition to today’s mobile device platforms. NCCoE cybersecurity experts will address this challenge through collaboration with Issuing Authorities, digital identity solutions providers, Verifiers (also known as Relying Parties), and third-party *trust service providers*. …… Let’s discuss: KI’s mission is to provide a Trust Framework service, should the RIUP and other Kantara’s WG leadership explore contributing to NCCOE’s mission? The project description says, “While this project is centered on mDLs defined in ISO/IEC 18013-5*, the concepts explored in this project will be extended to any credentialed Identity such as federal government issued credentials for agency employees or program beneficiaries, corporate credentials, travel credentials, health credentials, etc.”….. this includes the Underserved Population.* Have a good week, remembering 9/11, may God continue to Bless America! Jim One tap mobile +16465588656,,81066622226#,,,,*446287# US (New York) +16469313860,,81066622226#,,,,*446287# US Dial by your location • +1 646 558 8656 US (New York) • +1 646 931 3860 US • +1 301 715 8592 US (Washington DC) • +1 305 224 1968 US • +1 309 205 3325 US • +1 312 626 6799 US (Chicago) • +1 386 347 5053 US • +1 507 473 4847 US • +1 564 217 2000 US • +1 669 444 9171 US • +1 689 278 1000 US • +1 719 359 4580 US • +1 720 707 2699 US (Denver) • +1 253 205 0468 US • +1 253 215 8782 US (Tacoma) • +1 346 248 7799 US (Houston) • +1 360 209 5623 US

2 1