{"action":"created","issue":{"url":"https://api.github.com/repos/hyperledger/aries-rfcs/issues/255","repository_url":"https://api.github.com/repos/hyperledger/aries-rfcs","labels_url":"https://api.github.com/repos/hyperledger/aries-rfcs/issues/255/labels{/name}","comments_url":"https://api.github.com/repos/hyperledger/aries-rfcs/issues/255/comments","events_url":"https://api.github.com/repos/hyperledger/aries-rfcs/issues/255/events","html_url":"https://github.com/hyperledger/aries-rfcs/issues/255","id":505903924,"node_id":"MDU6SXNzdWU1MDU5MDM5MjQ=","number":255,"title":"RFCs 023 and 0094 contradiction around routing","user":{"login":"jovfer","id":5072859,"node_id":"MDQ6VXNlcjUwNzI4NTk=","avatar_url":"https://avatars0.githubusercontent.com/u/5072859?v=4","gravatar_id":"","url":"https://api.github.com/users/jovfer","html_url":"https://github.com/jovfer","followers_url":"https://api.github.com/users/jovfer/followers","following_url":"https://api.github.com/users/jovfer/following{/other_user}","gists_url":"https://api.github.com/users/jovfer/gists{/gist_id}","starred_url":"https://api.github.com/users/jovfer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jovfer/subscriptions","organizations_url":"https://api.github.com/users/jovfer/orgs","repos_url":"https://api.github.com/users/jovfer/repos","events_url":"https://api.github.com/users/jovfer/events{/privacy}","received_events_url":"https://api.github.com/users/jovfer/received_events","type":"User","site_admin":false},"labels":[{"id":1353221289,"node_id":"MDU6TGFiZWwxMzUzMjIxMjg5","url":"https://api.github.com/repos/hyperledger/aries-rfcs/labels/question","name":"question","color":"d876e3","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2019-10-11T15:00:08Z","updated_at":"2019-10-29T05:04:19Z","closed_at":null,"author_association":"MEMBER","body":"There are 3 options of invitation message https://github.com/hyperledger/aries-rfcs/tree/master/features/0023-did-exchange#0-invitation-to-exchange \r\nOne of them is the case of Invitation Message with Keys and URL endpoint\r\n```\r\n{\r\n    \"@type\": \"did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/didexchange/1.0/invitation\",\r\n    \"@id\": \"12345678900987654321\",\r\n    \"label\": \"Alice\",\r\n    \"recipientKeys\": [\"8HH5gYEeNc3z7PYXmd54d4x6qAfCNrqQqEB3nS7Zfu7K\"],\r\n    \"serviceEndpoint\": \"https://example.com/endpoint\",\r\n    \"routingKeys\": [\"8HH5gYEeNc3z7PYXmd54d4x6qAfCNrqQqEB3nS7Zfu7K\"]\r\n}\r\n```\r\nAccording to https://github.com/hyperledger/aries-rfcs/tree/master/features/0023-did-exchange#request-transmission the connection request for this invitation should be wrapped by fordard message via 8HH5gYEeNc3z7PYXmd54d4x6qAfCNrqQqEB3nS7Zfu7K key.\r\nAnd there is no way in Forward message definition to do it\r\nhttps://github.com/hyperledger/aries-rfcs/tree/master/concepts/0094-cross-domain-messaging#corerouting10forward as there is no way to define `to` filed as we have only key itself, but to may be either\r\n>* A DID without a key reference (e.g. did:sov:1234abcd)\r\n>* A DID with a key reference (e.g. did:sov:1234abcd#4)\r\n\r\nit seems like a contradiction between RFCs"},"comment":{"url":"https://api.github.com/repos/hyperledger/aries-rfcs/issues/comments/547257761","html_url":"https://github.com/hyperledger/aries-rfcs/issues/255#issuecomment-547257761","issue_url":"https://api.github.com/repos/hyperledger/aries-rfcs/issues/255","id":547257761,"node_id":"MDEyOklzc3VlQ29tbWVudDU0NzI1Nzc2MQ==","user":{"login":"kdenhartog","id":23125059,"node_id":"MDQ6VXNlcjIzMTI1MDU5","avatar_url":"https://avatars0.githubusercontent.com/u/23125059?v=4","gravatar_id":"","url":"https://api.github.com/users/kdenhartog","html_url":"https://github.com/kdenhartog","followers_url":"https://api.github.com/users/kdenhartog/followers","following_url":"https://api.github.com/users/kdenhartog/following{/other_user}","gists_url":"https://api.github.com/users/kdenhartog/gists{/gist_id}","starred_url":"https://api.github.com/users/kdenhartog/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kdenhartog/subscriptions","organizations_url":"https://api.github.com/users/kdenhartog/orgs","repos_url":"https://api.github.com/users/kdenhartog/repos","events_url":"https://api.github.com/users/kdenhartog/events{/privacy}","received_events_url":"https://api.github.com/users/kdenhartog/received_events","type":"User","site_admin":false},"created_at":"2019-10-29T05:04:19Z","updated_at":"2019-10-29T05:04:19Z","author_association":"CONTRIBUTOR","body":"Would this need to be an actual key, a reference to a key, or a JWK? I suspect like elsewhere it would need to be a JWK. @dhh1128 looks like this is becoming a common problem that we may want to standardize around the use of JWKs."}}
{"actor":{"display_login":"kdenhartog"}}