Mismatch between Route Coordination and Forward RFC

[rolsonquadras]

The recKeys are registered on the router as per the Route Coordination RFC, for which the edge agents expect redirection/forward from the router. But the to field in the Forward message takes a destination DID with/without key references. The Router won't be able to figure out the recKey from DID.

[rolsonquadras]

@llorllale @troyronda created this to track our earlier discussion.

[troyronda]

This issue seems like it could be an aries-rfcs discussion (issue)?

[llorllale]

hyperledger/aries-rfcs#274

[rolsonquadras]

To bridge the gap between the Route Coordination RFC and Forward message RFC, the Aries Framework Go uses Recipient key in the to field of forward message instead of DID.

Forward RFC:
"to" : "did:sov:1234abcd#4",

Aries Framework Go Implementation:
"to" : "<recKey of the destination agent>",

[troyronda]

To bridge the gap

(as a temporary workaround pending further discussions).

[rolsonquadras]

To bridge the gap

(as a temporary workaround pending further discussions).

Yes, @llorllale had raised this question in Aries RFC issue hyperledger/aries-rfcs#274 (comment).

[TelegramSam]

I'm realizing that this RFC missed an update to reflect an early decision. We ended up only using keys for routing because it was the simplest thing that would work. On that note, the decision in Aries Framework Go follows that method.

On the plus side, now is a really good time to revisit this issue.