# Invitation URLs

Purpose:
- Connect
- Proof Request (Connectionless)
- Issue Credential (Connectionless)

Content:
- Message Payload

Problems:
- Payload Size

### Related Specs
- https://github.com/hyperledger/aries-rfcs/blob/main/concepts/0217-linkable-message-paths/README.md
- https://github.com/hyperledger/aries-rfcs/blob/main/features/0434-outofband/README.md
- https://github.com/hyperledger/aries-rfcs/blob/main/concepts/0268-unified-didcomm-agent-deeplinking/README.md#message-requirements

### Formats
- [Connection Protocol](https://github.com/hyperledger/aries-rfcs/blob/3faeb95b92869936fd69aeddab4e921f50ee33f6/features/0160-connection-protocol/README.md#standard-invitation-encoding)

  https://<domain>/<path>?c_i=<invitationstring>

- [DIDComm Messaging V2](https://identity.foundation/didcomm-messaging/spec/v2.1/)

  https://<domain>/<path>?_oob=<encoded plain text jwm>
  https://<domain>/<path>?_oobid=<sender tracked GUID>
  
  didcomm://?_oob=<encoded plain text jwm>
  didcomm://?oob=<encoded plain text jwm>
  didcomm://?c_i=<encoded plain text jwm>
  didcomm://?d_m=<encoded plain text jwm>
  
  didcomm://?_url=<base64 encoded url>
  
  NOT supported:
  didcomm://?_oobid=<sender tracked GUID>

`oobid` "generate and track a GUID for the out-of-band message URL". NOT an URL itself as defined in Aries RFC 0700: Out-of-Band through redirect
- [Unified DIDCOMM Deeplinking](https://github.com/hyperledger/aries-rfcs/blob/main/concepts/0268-unified-didcomm-agent-deeplinking/README.md#message-requirements)

  # Universal Links
  # connection invite (c_i)
  https://<domain>/<path>?c_i=<encoded plain text jwm>
  # DIDCOMM message (d_m)
  https://<domain>/<path>?d_m=<encoded plain text jwm>
  
  # Custom Protocol (didcomm://)
  # connection invite (c_i)
  didcomm://?c_i=<encoded plain text jwm>
  # DIDCOMM message (d_m)
  didcomm://?d_m=<encoded plain text jwm>

**Question**: how about deep linking of short URL?
- [OOB](https://github.com/hyperledger/aries-rfcs/blob/main/features/0434-outofband/README.md#standard-out-of-band-message-encoding)

  https://<domain>/<path>?oob=<outofbandMessage>

**Question**: Confusing [URL shortening](https://github.com/hyperledger/aries-rfcs/blob/main/features/0434-outofband/README.md#url-shortening). Why the Redirect?
- [Out-of-Band through redirect](https://github.com/hyperledger/aries-rfcs/tree/main/concepts/0700-oob-through-redirect)

  https://<domain>/<path>?oob=<encoded plain text jwm>
  https://<domain>/<path>?oobid=<sender tracked GUID>

`oobid` = out-of-band invitation URL
- Credo
Inconsistent support for `c_i`, `d_m`, `oob`
- [packages/core/src/modules/connections/messages/ConnectionInvitationMessage.ts](https://github.com/openwallet-foundation/credo-ts/blob/88767cf2667d683448cce0c302dc818c7ae11450/packages/core/src/modules/connections/messages/ConnectionInvitationMessage.ts#L134)
- [packages/core/src/utils/parseInvitation.ts#parseInvitationUrl](https://github.com/openwallet-foundation/credo-ts/blob/88767cf2667d683448cce0c302dc818c7ae11450/packages/core/src/utils/parseInvitation.ts#L77)
- [packages/core/src/utils/parseInvitation.ts#oobInvitationFromShortUrl](https://github.com/openwallet-foundation/credo-ts/blob/88767cf2667d683448cce0c302dc818c7ae11450/packages/core/src/utils/parseInvitation.ts#L92)
- ACAPY?
- Bifold

# Going Foward

  https://<domain>/<path>?_oob=<encoded plain text jwm>
  https://<domain>/<path>?_oobid=<sender tracked GUID>
  
  didcomm://?_oob=<encoded plain text jwm>
  didcomm://?oob=<encoded plain text jwm>
  didcomm://?c_i=<encoded plain text jwm>
  didcomm://?d_m=<encoded plain text jwm>
  
  didcomm://?_url=<base64 encoded url>
  
  NOT supported:
  didcomm://?_oobid=<sender tracked GUID>