W3C home > Mailing lists > Public > public-interledger@w3.org > March 2016

Re: WIP: Interledger Architecture

From: Jehan Tremback <jehan.tremback@gmail.com>
Date: Mon, 21 Mar 2016 14:51:24 -0700
Message-ID: <CABG_PfTkBERof8fdJjnR=Qrc1b=Zfrm8=o-xciaUbDwnpwBeJw@mail.gmail.com>
To: Nicholas Addison <nick@addisonbrown.com.au>
Cc: Stefan Thomas <stefan@ripple.com>, Interledger Community Group <public-interledger@w3.org>
I noticed "Routing complexity should be in the connectors". Does this mean
that you will be moving away from the proposal phase as a necessary part of

On Mon, Mar 21, 2016 at 1:09 PM, Nicholas Addison <nick@addisonbrown.com.au>

> That’s a pretty fleshy strawman you have there, Stefan. Well done.
> I assume there can be a failure response to the Setup call in the OWPS
> layer. This would be needed when the Payer had made a mistake and entered
> an invalid Payee account.
> Regards
> Nick
> On 22 Mar 2016, at 5:52 AM, Stefan Thomas <stefan@ripple.com> wrote:
> Based on the requests for information about the layers in Interledger and
> how the different protocols relate to each other I've put together a
> strawman over the weekend:
> https://stackedit.io/viewer#!provider=gist&gistId=f534bfb53dfffb980c66&filename=interledger-architecture.md
> There isn't much totally new stuff in there. It takes the ideas that are
> floating around in our team, gives names to everything and makes a bunch of
> arbitrary choices, all just to give us a starting point. Note that we're
> still very actively working on this doc.
> If you're easily confused by changing specs, maybe you'll want to wait
> until the doc settles down a bit more before diving in. :)
> Source for the doc is tracked on Github:
> https://gist.github.com/justmoon/f534bfb53dfffb980c66
Received on Monday, 21 March 2016 21:51:52 UTC

This archive was generated by hypermail 2.3.1 : Monday, 21 March 2016 21:51:53 UTC