search

decentralized-identity / didcomm-messaging

https://identity.foundation/didcomm-messaging/spec/
Apache License 2.0
161 stars 56 forks source link

Move Tracing protocol to Protocols section? #368

Closed TelegramSam closed 2 years ago

TelegramSam commented 2 years ago

https://didcomm.org/trace/1.0/trace_report as defined, but outside the protocols section?

TelegramSam commented 2 years ago

Discussed WG 20220418. Should move down to protocols section to be consistent. Refer to the new location from within protocols. Also, Problem Report?

TelegramSam commented 2 years ago

@dhh1128 ^?

dhh1128 commented 2 years ago

I believe we decided that tracing would be an extension, outside the spec entirely.

dhh1128 commented 2 years ago

Actually, after reviewing the content a little more carefully, I don't think we need to do anything difficult. Tracing isn't a protocol, so shouldn't be moved to the Protocols section of the spec. Rather, tracing is a header (to request a trace), plus a non-DIDComm message sent to an arbitrary endpoint. Easiest choice is just to clarify a little. I've proposed a way to do that in #372 .

TelegramSam commented 2 years ago

So, no. we don't need to move tracing to protocols.

This leaves Problem Report as the lone thing that might need to move.