# WG Meeting: 2022-11-15

## Agenda
- [Shayne] Discuss Phil Hunt's request for `sub_id` instead of a per-SET `subject`
- [Atul] Stream ID pull request
- [Atul] Name change update?

## Attendees
- Atul Tulshibagwale (SGNL)
- Topher Marie (Strata)
- Shayne Miel (Cisco)
- Greg Brown (Axiad)
- Stan Bounev (VeriClouds)
- Asad Ali (Thales)
- Edmund Jay ()

## Notes
### Discuss Phil Hunt's request for "sub" instead of a per-SET "subject"
- Currently the SSE spec inserts a subject in each "event" claim
- All of the events in a SET should be about the same subject
- Interop is really hard because "sub" is commonly used
- What is the history here?
- Q: Is our complex subject format compatible with how "sub" is used / specified by JWTs?
- Q: Does the spec allow for multiple events to be sent in the same SET?
-

### Stream ID pull request
- Please review the "stream Id" [pull request](https://github.com/openid/sse/pull/9)
- Q: Is "stream id" a part of the RISC spec? A: It is a part of the [SSF spec](https://openid.net/specs/openid-sse-framework-1_0-ID1.html) that the RISC spec depends upon

### Name Change Update
- The new name of the working group is "Shared Signals Framework" (SSF)
- We should change the name in the specifications after the "stream id" pull request is merged in

## Action Items
- Shayne to investigate whether the JWT "sub" claim is compatible with the compound / complex subject format used in SSF
- Atul to investigate whether multiple events are permitted in the same SSF SET, and if not clarify that in the spec