Re: ILP Quoting

We're in the midst of switching the pathfinding from source routing to a
non-source routing architecture at the moment. There isn't much
documentation about this at the moment but we'll be working to get that
written up soon. Do you have specific ideas or questions about that that we
could incorporate or address in the meantime?

For normal pathfinding we assume that the source and destination ledgers
are known, but not the path of connectors and intermediary ledgers. With
the non-source routing approach, the sender would query all of the
connectors attached to their ledger (the source ledger) for quotes. The
connectors will have a certain amount of routing information cached and may
need to query others if they do not have a path for the given query stored.
Connectors later in the path do not need to know how much the original
source amount is, only how much they're being asked to deliver from one
ledger to the other. Does that make sense?

On Wed, Apr 13, 2016 at 10:27 PM, David Fuelling <dfuelling@sappenin.com>
wrote:

> Hey All,
>
> I have a few questions around Connector "quoting" in ILP.
>
>    1. In the Interledger Architecure document
>    <https://github.com/interledger/specs/blob/gh-pages/0001-interledger-architecture.md>,
>    there's a reference to ILQP, but not much specific information.  Are there
>    any more details around this, such as a flow-diagram or document that
>    outlines how quoting is envisioned to work?
>
>    2. For multi-connector transfers where a source and final destination
>    are known, *and* all of the Connector hops are are known, who does the
>    source connector "ask" for a quote?  Reading the architecture document, it
>    appears that the source connector merely queries various connectors
>    "connected" to the destination ledger and picks the best one.  However, how
>    does the final hop connector (the destination) know the total quote that
>    any connectors in the path might "charge"?  Just wondering how the
>    mechanism is envisioned to work.
>
> Thanks for any input!
>
> David
>



-- 
Evan Schwartz | Software Architect | Ripple
[image: ripple.com] <http://ripple.com>