Re: [saag] Ledger BoF

Adrian Hope-Bailie <adrian@hopebailie.com> Fri, 15 July 2016 11:52 UTC

Return-Path: <adrian@hopebailie.com>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C4EF12DA06 for <saag@ietfa.amsl.com>; Fri, 15 Jul 2016 04:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopebailie.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZkT5H-a4QKeh for <saag@ietfa.amsl.com>; Fri, 15 Jul 2016 04:52:46 -0700 (PDT)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B45AE12D62F for <saag@ietf.org>; Fri, 15 Jul 2016 04:52:46 -0700 (PDT)
Received: by mail-oi0-x230.google.com with SMTP id l72so13542474oig.2 for <saag@ietf.org>; Fri, 15 Jul 2016 04:52:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopebailie.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=GEWV792FVeQcJnyE0MJKm91vcPqQS+sGuSvLt2u638g=; b=Ts0sJQZMJFro61YRVHj8csHoZR0dCRv92XyguppPRWNo1kHm+1sgwymDTodcSNa3LW 8DHgVrJYgfWy+qRhwtLF/z8Xn+OFQ9c9aW9z97Z/vdydApl630zanULX4IgKKDLHD9Mb vZbARORoSo3Xb52V5S1gYBjLIUXMTFLAtmaa8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=GEWV792FVeQcJnyE0MJKm91vcPqQS+sGuSvLt2u638g=; b=GZKQk9B1HmAyKManvMBrmBH9gaQlsGxkhNnR75bRA1+qehMyZv1IMTtr5elmrCwlYY i4UAmG+/pxei7XfHPcafxACRMxBnEHvctJHm1iMZfURbuI29lgKlCW2jvv3rgHZka7WN nMRf1we8msvx35+hcMkwCLM59MgCX3PR6pbiDyp+6atnMQVPVjZigZv42qoO69j02Hi0 ly3mELXbiLyaAD0R0reXg9Cgb/T8o7RiqH9AhyFKdylqJuH/csjB6iEZgiKdZJwd/+vg 0SLXlfSfMFdOYK24Ew5Gz9C85jG+jkynuLsSCQ4Dk9qzNhZPtpN3zV6NSvbSkqgZuNy9 rVNg==
X-Gm-Message-State: ALyK8tKm2OvExsqmkLWBBzvaDXNFVPez3Y8JPmlrFOeUSsNJqmyb7RGuPs3982wUodt2byp2qykEuOmUlfzyZw==
X-Received: by 10.202.226.204 with SMTP id z195mr7631865oig.120.1468583565791; Fri, 15 Jul 2016 04:52:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.172.142 with HTTP; Fri, 15 Jul 2016 04:52:44 -0700 (PDT)
In-Reply-To: <D2838039-928B-450C-8F9C-D3827BC65290@cisco.com>
References: <D2838039-928B-450C-8F9C-D3827BC65290@cisco.com>
From: Adrian Hope-Bailie <adrian@hopebailie.com>
Date: Fri, 15 Jul 2016 13:52:44 +0200
Message-ID: <CA+eFz_J+W7fQ31g2ErJHhF_2ofZ5taBc1X7GBJpoCKtU2LMgKA@mail.gmail.com>
To: "Matt Miller (mamille2)" <mamille2@cisco.com>
Content-Type: multipart/alternative; boundary="001a11408630c32ffc0537ab4109"
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/fO8dBtRy-XAaZkLimMlHzkWP3I4>
Cc: Stefan Thomas <stefan@ripple.com>, Adam Roach <adam@nostrum.com>, "saag@ietf.org" <saag@ietf.org>
Subject: Re: [saag] Ledger BoF
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jul 2016 11:52:50 -0000

Hey Matt,

There is also a lot of info on the project website https://interledger.org
<http://interledger.org> and everything (markdown versions of the Internet
Drafts, reference code etc) is in the GitHub repo:
https://github.com/interledger/

As first timers to an IETF meeting my colleagues and I will be at the
training and meetup on Sunday so we'll be at IETF the whole week and would
love to meet anyone that's keen to chat before the BoF.

If you read https://tools.ietf.org/html/draft-thomas-interledger-00 you'll
see that we've got a lot of the classical networking issues to still figure
out on top of this basic protocol like routing (and a variation on that,
quoting). We've got some proposals but are keen to get input on those.

We're hoping to spend a lot of time next week talking to folks that are
especially knowledgeable in those areas so any suggestions or introductions
are welcome.

With regard to crypto-conditions, we'd also like to hear from anyone that
thinks they have a use case that would benefit from something like
crypto-conditions. We developed it specifically for our use case but it has
pretty general applicability as a drop in replacement for signatures but
with a bunch of additional features.

Looking forward to meeting you all!

Adrian

On Thursday, July 14, 2016, Matt Miller (mamille2) <mamille2@cisco.com>
wrote:

> Hello all,
>
> This is to let you all know about the Ledger BoF. This is a non-working
> group forming BoF to introduce the InterLedger protocol and crypto
> conditions work started in W3C Web Payments. It's on Thursday 21 July at
> Afternoon II (16:20 - 18:20) in Potsdam I.
>
> The Interledger protocol is an open and neutral protocol for making
> payments between disconnected payment networks and ledgers. It defines
> schemes and primitives for dealing with addressing of ledgers,
> fragmentation of payment networks, and cryptographically secured validation
> of transfer conditions and fulfillments.
>
> Initially started within a W3C community group in October 2015, the
> purpose of this non-working group forming BoF is to introduce Interledger
> and the underlying protocols to attendees and discuss how this work might
> progress at the IETF.
>
> The W3C Community where this work originated is at <
> https://www.w3.org/community/interledger/ >.
>
> The relevant drafts are:
>
> * The Interledger Protocol <
> https://tools.ietf.org/html/draft-thomas-interledger-00 >
> * Crypto-Conditions <
> https://tools.ietf.org/html/draft-thomas-crypto-conditions-00 >
>
>
> Thank you,
>
> --
> - m&m
>
> Matt Miller
> Cisco Systems, Inc.
>
>