13:00:59 RRSAgent has joined #vcwg 13:01:04 logging to https://www.w3.org/2026/09/23-vcwg-irc 13:01:04 RRSAgent, make logs Public 13:01:05 please title this meeting ("meeting: ..."), ivan 13:01:16 Meeting: Verifiable Credentials Working Group Telco 13:01:16 Agenda: https://lists.w3.org/Archives/Public/public-vc-wg/2026Sep/0058.html 13:01:16 chair: phila 13:01:16 ivan has changed the topic to: Meeting Agenda 2026-09-23: https://lists.w3.org/Archives/Public/public-vc-wg/2026Sep/0058.html 15:00:22 hsano has joined #vcwg 15:00:37 phila has joined #vcwg 15:00:44 Antony has joined #vcwg 15:00:46 present+ 15:00:51 present+ 15:01:10 present+ 15:01:10 brent has joined #vcwg 15:02:10 wes-smith has joined #vcwg 15:02:18 pdl-ASU has joined #vcwg 15:02:27 present+ 15:02:30 present+ 15:02:42 Elaine has joined #vcwg 15:02:42 michaelshea has joined #vcwg 15:02:44 present+ 15:02:56 present+ 15:03:04 present+ 15:03:04 present+ 15:03:24 https://www.w3.org/register/tpac2026/registrants 15:03:30 kezike has joined #vcwg 15:03:31 present+ 15:03:43 scribe+ 15:03:52 present+ 15:03:53 present+ 15:03:56 Topic: Introductions 15:04:07 Antony: Hello 15:04:22 JennieM has joined #vcwg 15:04:23 zoom link? 15:04:34 present+ 15:04:37 rrsagent, who is here? 15:04:37 I'm logging. I don't understand 'who is here?', ivan. Try /msg RRSAgent help 15:04:46 phila: reviewing agenda, nothing one additional topic (DC-API) 15:04:47 zakim, who is here? 15:04:47 Present: phila, Antony, hsano, pdl-ASU, dlongley, TallTed, Elaine, manu, michaelshea, brent, ivan, kezike, JennieM 15:04:49 On IRC I see JennieM, kezike, michaelshea, Elaine, pdl-ASU, brent, Antony, phila, hsano, RRSAgent, Zakim, TallTed, klea, simone, hadleybeeman, ivan, pchampin, jyasskin, shigeya, 15:04:49 ... manu, dlehn, dlongley, cel 15:05:08 wes-smith has joined #vcwg 15:05:11 Topic: Task Force Updates 15:05:24 present+ wes-smith 15:05:39 present+ michaelshea 15:05:56 manu: DI, Barcodes, Bitsring, Forgery Defense are all making progress 15:06:16 present+ Antony 15:06:45 ... One request: BBS specification at W3C is relying on IRTF Crypto forum. That spec is not progressing, not a lot of author involvement 15:06:52 present+ jimr 15:06:54 q+ to provide update for VCALM TF 15:07:43 ... this is a big risk for us. Greg is in the VCWG, has good relationships with the BBS Authors. Greg has volunteered to help push things forward. 15:07:59 s/IRTF/IETF/ 15:08:00 ... Could we resolve to ask the IETF to add Greg as an author. 15:08:05 qq+ 15:08:18 ... everything else is going well 15:08:27 scribe+ 15:08:28 scribe+ 15:08:33 ack brent 15:08:33 brent, you wanted to react to a previous speaker 15:08:36 scribe- 15:09:43 brent: I agree that greg should be added as an author - this group passing a resolution asking the IETF to add someone as an author would be unusual, and I'm not sure that the IETF would know how to respond to such a resolution. Though not quite as decisive, it could be more effective to get the existing authors to add him as an author. Even 15:09:43 without him added as an author, he can fill the role that he is currently filling. 15:10:02 q+ 15:10:18 phila: I was a bit surprised to hear we might make a resolution for this 15:11:00 ivan: I have not heard of this and of resolution, but I also have not run into this problem. What we could do is that the WG could agree that this is what needs to happen, but without passing a formal resolution, and with that we could talk to the liaisons to the IETF. 15:11:11 ivan: I'm not familiar, I don't know. What we could do is agree on what would be good to happen and talk to Simone and Philippe who are the liaisons 15:11:14 JimR has joined #vcwg 15:11:31 present+ dmitriz 15:11:40 ack manu 15:11:52 q+ to note something else about the VCB/DI TF 15:11:58 phila: The liaisons should be brought into this conversation. It would be useful to have a resolution in the minutes. 15:12:26 manu: We need someone who can make changes to the specification in a timely manner. Greg is willing to do that. 15:13:05 ... It has more weight when we as a working group make the statement. Saying we want it to move forward and we want Greg added as an author. 15:13:19 ... Our ability to get BBS done is at risk. 15:14:00 phila: the motivation is clear, and we should take a resolution. That's not enough, we also need the liaisons involved.. I take the action to move it forward with Philippe. 15:14:10 qq+ 15:14:15 ack brent 15:14:15 brent, you wanted to react to manu 15:14:31 Elaine has joined #vcwg 15:15:16 brent: I think we should resolve to urge the IETF to move the BBS document forward and encourage reaching out to the authors and gain additional support. I would not be able to +1 a resolution directly calling for Greg's addition - that would be an overstep. 15:15:24 +1 to Brent 15:15:26 I'm author on an IETF draft, admittedly with zero other authors at present, so not experienced much. Perhaps a small and friendly step before a resolution or official channel, might be for Greg simply as an individual just to contact one or more of the authors and just ask if they're willing to add him as author. As Gret's already a contributor, 15:15:26 this low-key approach maybe will get the job done! 15:15:56 +1 to saying we have a WG willing to help as an additional author. 15:16:02 s/WG/WG member 15:16:08 +1 to that proposal 15:16:32 PROPOSED RESOLUTION: We urge the IETF to move the BBS spec (https://datatracker.ietf.org/doc/draft-irtf-cfrg-bbs-signatures/) forward by all means available. We have a WG member willing to help as an additional author 15:16:39 +1 15:16:40 +1 15:16:40 +1 15:16:41 +1 15:16:42 +1 15:16:43 +1 15:16:43 +1 15:16:43 +1 15:16:43 +1 15:16:44 +1 15:16:50 +1 15:16:50 +1 15:16:54 +1 15:16:58 JoeAndrieu has joined #vcwg 15:17:03 RESOLVED: We urge the IETF to move the BBS spec (https://datatracker.ietf.org/doc/draft-irtf-cfrg-bbs-signatures/) forward by all means available. We have a WG member willing to help as an additional author 15:17:07 +1 15:17:13 ack wes-smith 15:17:13 wes-smith, you wanted to note something else about the VCB/DI TF 15:17:37 ack kezike 15:17:37 kezike, you wanted to provide update for VCALM TF 15:17:57 q+ to speak to recognized entities TF 15:18:29 kezike: brief update on VCALM. Two things: first we are getting some review from internationalization. Second, big threat model update is in place. 15:18:39 q+ 15:18:51 ... keeping an eye out for the new Threat Model protocol, we will be moving to that. 15:19:06 q- 15:19:13 phila: How likely you will be ready for VCALM to move forward at TPAC? 15:19:23 q+ to speak to CR by TPAC 15:19:32 kezike: Fairly confident, we're relying on getting timely review. 15:20:01 ack manu 15:20:01 manu, you wanted to speak to recognized entities TF and to speak to CR by TPAC 15:20:06 phila: We are hoping to move into CR with all specs at TPAC 15:20:29 manu: It is becoming unliekly that we will get to CR with anything by TPAC. 15:20:46 ... Threat model work and lack of reviews are both holding things up. 15:20:48 q+ to mention conversation with Simone 15:20:53 ... still need TAG reviews 15:21:09 ... without that we can't really move forward 15:21:59 JimR has joined #vcwg 15:22:12 ... Recognized Entities is making progress. Privacy review is coming in. They are not resonating with using a threat model to develop Privcy considerations. Did get security review, lot's of work. 15:22:34 q+ 15:22:38 ack JoeAndrieu 15:22:38 JoeAndrieu, you wanted to mention conversation with Simone 15:22:43 ... I think there is a bit of uncertainty on exactly what good enough is with regards to the threat model 15:23:19 JoeAndrieu: Simone and I are engaged productively. Between us three, we can find a reasonable place to land. 15:23:34 ack ivan 15:23:40 ... there's a route we can get there with SING. Simone will help us talk with PING 15:24:22 ivan: Recognized Entities is also testing out a Vocabulary, that is available for review. 15:24:36 confidence-method has nothing significant to report. working towards starting horizontal review by TPAC. 15:24:43 phila: There iwll be more coming from GS1 for Recognized Entities. 15:24:43 exe has joined #vcwg 15:24:48 Topic: Blog Post 15:24:54 -> https://lists.w3.org/Archives/Member/member-vc-wg/2026Sep/0000.html Blog post 15:25:00 wes-smith has joined #vcwg 15:25:09 phila: Not sure who's reviewed 15:25:10 present+ exe 15:25:23 present+ 15:26:17 wes-smith: Hopefully folks have looked at the draft. It is fairly short, arguing VC Barcodes is uniquely positioned to address attacks such as we've seen lately with millions of drivers licenses. Digital signatures and real-time revocation mechanisms are key. 15:26:44 ... It asserts that you should use VC-Barcodes to mitigate from attacks like this. 15:27:13 ... we've discussed with the comms team, they will have some review. Haven't heard anything from the group requesting changes. 15:27:51 ... can we resolve to publish modulo any changes requested by comms? This discussion is happening elsewhere so publishing soon is important. 15:28:13 ... also talking with comms team about publicizing the blog 15:28:17 Elaine has joined #vcwg 15:28:29 I have read it and looks good to me. 15:28:35 phila: does anyone have comments on the blog post? 15:28:37 q+\ 15:28:48 I have also read it and think it is good as well. 15:28:49 ack pdl-ASU 15:28:55 ack \ 15:29:31 pdl-ASU: I have read it. It seems a bit longer than it needs to be. I suggest an edit after the section that ends with "as Cyberattacks grow in frequency" 15:29:43 ... the text after that has a lot of repetition 15:30:04 phila: does that edit sound reasonable? 15:30:33 wes-smith: can we still resolve to publish today, even with those changes? 15:31:06 go for it Wes! 15:31:22 pdl-ASU: I will put suggested change in IRC 15:31:32 wes-smith has joined #vcwg 15:31:53 PROPOSED RESOLUTION: The VCWG seeks publication of the text in https://lists.w3.org/Archives/Member/member-vc-wg/2026Sep/0000.html as a W3C blog post no later than Tuesday 29th September, modulo minor changes to be made following suggestions made during the meeting and any editorial changes required by the Comms team 15:31:55 phila: any comments? 15:31:57 +1 15:31:58 +1 15:32:00 +1 15:32:00 +1 15:32:00 +1 15:32:00 +1 15:32:01 +1 15:32:03 +1 15:32:04 +1 15:32:04 +1 15:32:06 +1 15:32:07 +1 15:32:07 +1 15:32:12 End the post text at the line "W3C Verifiable Credential Barcodes are the solution - and the technology is 15:32:12 open and free for all to use." What follows then is the list of links and whatever minimum explanation of them is requireds 15:32:19 RESOLVED: The VCWG seeks publication of the text in https://lists.w3.org/Archives/Member/member-vc-wg/2026Sep/0000.html as a W3C blog post no later than Tuesday 29th September, modulo minor changes to be made following suggestions made during the meeting and any editorial changes required by the Comms team 15:32:27 q+ 15:32:29 thanks to Wes for spearheading this 15:32:30 phila: thanks everyone 15:32:37 ack TallTed 15:33:09 TallTed: I will be making suggested changes during the meeting 15:33:28 Topic: Data Integrity re-structuring overview 15:33:58 q+ 15:34:06 ack manu 15:34:48 open and free for all to use.") are intended to be section headers, not core text - the minuted version has lost all formatting. Does that impact your request at all? 15:35:13 q+ 15:35:24 manu: This is all credit to Greg Bernstein. When we published DI 1.0 and the suites there was a lot of duplicate text. Greg re-factored all of that and unified. For example, the selective disclosure mechanism is now generalized and available for use by all of the cyphersuites. 15:35:48 JennieM has joined #vcwg 15:36:01 Elaine has joined #vcwg 15:36:35 ... There is also work around single individual hashing and selctive disclosure. There are a number of options to take, hashing together vs hasing individual items. The takewaya is this is good and important work that Greg has done. This will help future cryptosuite authors to re-use these common algotirhms. 15:37:06 ... had a discussion around cryptosute identifiers and where certain parameters will go, decided to put them in the identifier string. 15:37:28 ... also some BBS optionality stuff has been covered. It's in really good shape now. 15:37:30 ack ivan 15:37:32 Wes Smith While I didn't realize that was a heading (W3C Verifiable credentials are the solution..." I think that's a good closing sentence to the post. Followed by the URLs with whatever context for them is needed. 15:37:34 phila: all editorial? 15:37:39 manu: yes 15:38:50 ivan: I want to emphasize something. The current documents are frightening to add new cryptosuites. With the new format, adding new crypto algorithms will be relatively easy. 15:39:20 ... outsiders will be able to create their own cryptosuites more easily and comprehensievly than before 15:39:29 ... this was agreat thing to do 15:39:53 Topic: TPAC, goals etc. 15:40:00 https://www.w3.org/register/tpac2026/registrants 15:40:01 s/comprehensievly/comprehensively/ 15:40:34 phila: There's a link of who has registered. We want as many as possible there. We are meeting Thursday and Friday. 15:40:52 ... Wednesday there are a bunch of breakouts. Lot's of initial proposals. 15:41:09 ... If anyone wants to suggest a breakout, now is the time. 15:41:43 ... They are always exciting. Threat modeling, for example could be a good breakout. 15:41:54 Wes-Smith That's fine. My suggestion is just that, a suggestion, in an attempt to make it a bit more succinct (aka shorter :-) 15:43:11 Joint meeting detauils https://www.w3.org/events/meetings/7f5ffe2d-c418-47f1-880a-36710212b347/ 15:43:23 ... Need to report on joint meeting agenda planning meeting from yesterday. Lots of groups meeting together. There is a joint meeting Tuesday during TPAC. 15:43:49 ... this is an important route to make sure the work we are doing is recognized and used elsewhere. 15:44:15 q+ to speak to raising issues on DC API before W3C TPAC wrt. exclusion of W3C VCs from DC API work. 15:44:18 ... As far as I know no one here is involved in the DC API, and no one there is involved here. 15:44:32 manu: related to earlier topic of Greg's editorial refactoring the two specs - another shoutout to Greg who opened the 'linkability' discussion here https://github.com/w3c/vc-data-integrity/issues/363. Will likely be useful to many. 15:44:40 ... this joint meeting is one way to address that. 15:44:47 s/manu: related/manu, related/ 15:45:06 ack manu 15:45:06 manu, you wanted to speak to raising issues on DC API before W3C TPAC wrt. exclusion of W3C VCs from DC API work. 15:45:09 ... This is important to us and others need to recognize that. It is important to our companies. 15:46:18 manu: To make that concrete, I think this group should raise issues on the DC-API around the fact that is doesn't support VCALM and isn't headed in that direction. In implementations, the only thing that can be passed is ISO MDoc, though supposedly supported, W3C VCs aren't supported. 15:46:47 ... I can write up the technical concerns for interoperability to put before ths group. The goal is to raise these issues before TPAC. 15:47:06 phila: Do you want to draft them and discuss them here before raising them? 15:47:10 manu: yes 15:47:34 phila: in light of your workload, do you have time to get this together by next week? 15:47:38 manu: no. 15:47:55 phila: I can help as a chair and as GS1. 15:48:07 manu: maybe in a few weeks. 15:48:34 those registered to Joint PTAC meeting: https://www.w3.org/register/tpac2026/registrants#meeting-465 15:49:01 phila: important to note that these people are not opposed to us, they just don't know us. 15:49:35 ... hoping this can be a positive discussion. We are all W3C working groups and should work together. 15:49:55 ... It was a very positive call yesterday. 15:50:01 q+ 15:50:04 phila: any other business? 15:50:05 ack wes-smith 15:50:21 q+ 15:50:30 ack TallTed 15:50:34 q+ 15:50:38 wes-smith: Am I blocking on reviews from anyone here? I'm in touch with Phil, anyone else? 15:50:46 acl pdl-ASU 15:50:47 TallTed: I will email you my suggestions 15:50:50 ack pdl-ASU 15:50:58 pdl-ASU: those changes look good to me 15:51:40 phila: If you are an AC rep, don't forget to get your Board votes in. Election closes tomorrow. I felt this was very important to do. The makeup of the board matters today. 15:51:48 thank you all! 15:51:55 phila: Thaks all, thanks Brent, see you all next week. 15:52:11 RRSAgent, draft minutes 15:52:13 I have made the request to generate https://www.w3.org/2026/09/23-vcwg-minutes.html phila 15:52:44 Antony has left #vcwg 15:53:12 rrsagent, draft minutes 15:53:13 I have made the request to generate https://www.w3.org/2026/09/23-vcwg-minutes.html ivan 16:00:12 rrsagent, bye 16:00:12 I see no action items