Channel Binding being transport-specific specified
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Currently, Channel Binding provides a map of all the fields of all possible transport types that could have been used to engage the protocol.
DC API is moving to provide a 'Client Data' structure. It would be nice to provide a similar approach for each transport so it is something like:
ChannelBinding = {
1 => DCAPIClientData, // DCAPI ClientData structure
2 => IsoDeviceEngagment, // 18013-5 DeviceEngagment structure
3 => OpenId4VPClientData, // OpenId4VP
}
This make the separation more clear, and makes it easier to add new transports in the future (e.g. issuance, agentic etc).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the current Channel Binding definition and comparing it with the referenced DC API, ISO/IEC 18013-5, and OpenID4VP client-data structures. The issue names no files or tests; the work is done when the transport-specific structure and its extension approach are agreed and reflected consistently in the project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100