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).
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).