Sam Curren

DIscussed WG 20220316. Should be an ACK-ok, or a Problem Report, not an ACK-fail. Needs explaining text added to relevant RFCs. Also update please-ack decorator. Stephen Curran volunteered.

>Also, does it mean that we should take just serviceEndpoint from the service block? No. It means everything relevant from the service block, not just the serviceEndpoint. >The service MUST...

@dhh1128 @tmarkovski @swcurran

I committed a markdown fumble in the original post. I've edited to represent what I had originally intended.

After some reading (https://en.wikipedia.org/wiki/Uniform_Resource_Identifier) and thinking, I think option 3 with this uri is what I'm recommending: `didcomm:transport/hold` This is a valid URI (which does not require an //authority) and...

@dhh1128 yeah, mostly. It was the least confusing thing I could come up with. Totally open to better ideas.

didcomm:transport/pickup didcomm:transport/none

didcomm:transport/queue

@dhh1128 I'm realizing that this relates more to Peer DIDs than it does to any specific protocol within Aries. Does this concept have a home in that conversation?

Discussed WG 202211207. We concluded that nobody knows the state of adoption in the codebases.