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

Re: Binary Encoding for Crypto-conditions

From: Stefan Thomas <stefan@ripple.com>
Date: Wed, 30 Mar 2016 18:38:26 -0700
Message-ID: <CAFpK0Q2_XvY-7XrBewjLuM9CE25WWCdjAjXGdzq2nw9pxUtrhA@mail.gmail.com>
To: "zaki@manian.org" <zaki@manian.org>
Cc: Tony Arcieri <bascule@gmail.com>, Melvin Carvalho <melvincarvalho@gmail.com>, Interledger Community Group <public-interledger@w3.org>
Just posted a pull request for switching to OER:

The binary encoding switch was the last item on the spec todo list that I'm
aware of. Do any of you still have major breaking changes you want the
group to work on? (Purely from a normative spec perspective, we can always
improve the implementations, spec prose, etc.)

And of course I'm not suggesting that we can't make changes later, I just
want to get crypto-conditions to a state that works, so we can start
spec'ing out the next aspect of the protocol.

@Melvin: Hmm, crypto-conditions are fundamentally a graph, so at least on a
high level HDT would fit pretty well. I'd have to spend a bit of time to
wrap my head around what it would look like in practice. I'll try to read
through the HDT docs this weekend.

On Wed, Mar 30, 2016 at 12:12 PM, zaki@manian.org <zaki@manian.org> wrote:

> Fabrice Bellard(The Man, The Myth, The Legend) has  a ASN.1 C generator
> from a definition file that supports OER.
> http://www.bellard.org/ffasn1/
> On Wed, Mar 30, 2016 at 11:48 AM, Tony Arcieri <bascule@gmail.com> wrote:
>> On Wed, Mar 30, 2016 at 11:45 AM, zaki@manian.org <zaki@manian.org>
>> wrote:
>>> I'm surprised how much I like ASN.1 OER.
>> +1. This is the first I've seen it, and it seems like it addresses a lot
>> of problems with other ASN.1 representations.
>> --
>> Tony Arcieri
Received on Thursday, 31 March 2016 01:39:18 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 31 March 2016 01:39:19 UTC