Out of Band Attempt 342�Try, Try Again

2020.05.13

0434 Out of Band RFC and Protocols

Previous Revision:

• Out of Band Protocols (oob-invitation and oob-request)
• Two protocols, one message each:
• invitation - replaces invitation from at least DID-Exchange
• request - replaces the ephemeral challenge used with Request Presentation + ~service
• Intended to be used with, for example, QR Codes for transfer
• Not DIDComm
• Only one message type used per instance of the protocol
• “goal-code” and “goal” strings convey the (self-asserted) purpose of the out of band message
• Response comes from another protocol, from options in out of band message

Changes — PR to merge into one protocol

• Requested change: ability to both connect and initiate a protocol
• vs. just connect or initiate a protocol
• Now:
• Connect OR connectionless protocol OR connect+protocol
• Changes:
• Rename “protocols” in invitation to “setup_protocols” and make optional
• Add to invitation optional “request~attach” item from request
• Eliminate the oob-request protocol
• Rename the protocol to “out-of-band” with single message “invitation”
• “setup_protocols”, “attach~request” or both MUST be in the message
• If the protocol is to be started by the receiver, “attach~request” should be “protocol_role_request” message.

Example of Message

• Both included, meaning:
• Connect using one of the setup protocols
• Could result in a connection reuse
• Send a response to one of the request~attach messages
• Could be in response to a “protocol_role_request” message

Ready to go?

• PR:
• Sort out the “-” vs. “_” in the protocol name
• Maybe: Need to add link to “protocol_role_request” RFC (PR)
• Add short section on why to use, not use the two together
• Continued interactions after a connection - pthid

Can we move on…???

• Input: URL reduction in size handling
• DID Exchange merge
• Update to Protocol RFC - string matching