From nobody Fri Sep 8 14:59:27 2017 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9B90132D6B for ; Fri, 8 Sep 2017 14:59:26 -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 qJ1sVH4Ug35E for ; Fri, 8 Sep 2017 14:59:25 -0700 (PDT) Received: from mail-vk0-x22f.google.com (mail-vk0-x22f.google.com [IPv6:2607:f8b0:400c:c05::22f]) (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 E0147132D86 for ; Fri, 8 Sep 2017 14:59:24 -0700 (PDT) Received: by mail-vk0-x22f.google.com with SMTP id x85so4754642vkx.5 for ; Fri, 08 Sep 2017 14:59:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopebailie.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=46lw4+Zax9UwZE2LYFOAOMKmptsivnO46To9alz8OIE=; b=NJ2FrGZ/bdKOf4M48RV3rIVMS42v5zGC9yVAOUfH3i01mGF7CfJO5HDogpnjLx0fjE bfTlqY9eBDbWr3le62ARxP+MgV6OB6BbUnklsOYRBYxP4yULZCu6mF2F2i7SZg/hSAli cDaEovBHZekdk3yKq25ukTLHEG7W5po7zUIlQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=46lw4+Zax9UwZE2LYFOAOMKmptsivnO46To9alz8OIE=; b=tBge8zEkNtyGmI8piqt1bmWg4FoVBkrr/7dg8EkVUXEzEuvIQXSOPqZKqCuNPtUQ/P pvNhi+shl59AnZDZLwyOwJtdkCYM6RqoHEi6ZT+1JOuUqOt/McZTcb75z6Qm1BDxDD7J zJFaCdFHFPN1RDDjl9b7KliT1Fi+borlHBULGylrIhbglycawbJDrxtDpOsZiLFum3an dazdisUXW+1qu8SWeNtQrAzn8i68PVzWgFI/4MSjT4iGy5ui3U0EZRj20vrG8cAGpKEY pVNDYn7X1AjKYCfQfkwALIKJmRFsmcPGQkV36lhsY65cFsBq9cQWsZ4yyAyFI4inc7E3 QLxQ== X-Gm-Message-State: AHPjjUgYTHI7QVlNtgp9YbEigIJaZrARyNbum/xUGaXMasIz/yvKINak Qc8bFH+1en1+oR1GPoPfFpUr+pCPfz6Ecj1auw== X-Google-Smtp-Source: AOwi7QA2volCtW2QSA9irQQo2hfHGrIzNu84rakazIDnNKheJ4C8T6ZRajYIav2MGXSclCdv2bbNH9V/RCg6fC9RcCg= X-Received: by 10.31.135.141 with SMTP id j135mr2682724vkd.151.1504907963924; Fri, 08 Sep 2017 14:59:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.0.71 with HTTP; Fri, 8 Sep 2017 14:59:23 -0700 (PDT) From: Adrian Hope-Bailie Date: Fri, 8 Sep 2017 14:59:23 -0700 Message-ID: To: Interledger Community Group , Interledger Mailing List - IETF Content-Type: multipart/alternative; boundary="001a11457a649c164f0558b4b0b9" Archived-At: Subject: [Ledger] Interledger meetups in San Francisco and Singapore (maybe Tokyo?) X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Sep 2017 21:59:27 -0000 --001a11457a649c164f0558b4b0b9 Content-Type: text/plain; charset="UTF-8" The details are confirmed for two upcoming ILP meetups in SF and Singapore and we're gathering interest on having a full-day workshop in Tokyo. *San Francisco - 9 November* If you're planning to be at W3C TPAC in San Francisco (or just in the area at the time) then join us just down the road for an evening meetup on 9 November. Registration and details at: https://interledger.org/sanfrancisco *Singapore - 15 November* Alternatively, if you're going to be in Singapore during Singapore Fintech Festival or IETF then join us for a meetup the evening of 15 November. Registration and details at: https://interledger.org/singapore *Tokyo - TBD (Week of 20 - 24 November)* Finally, we're keen to keep the momentum going with a full day workshop and possibly a short hackathon in Tokyo the following week and are gathering expressions of interest to help us wth the planning. Details at: https://interledger.org/tokyo --001a11457a649c164f0558b4b0b9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The details are confirmed for two= upcoming ILP meetups in SF and Singapore and we're gathering interest = on having a full-day workshop in Tokyo.

San= Francisco - 9 November

If you're planning = to be at W3C TPAC in San Francisco (or just in the area at the time) then j= oin us just down the road for an evening meetup on 9 November.

Registration and details at: https://interledger.org/sanfrancisco

Sin= gapore - 15 November

Alternatively, if you= 're going to be in Singapore during Singapore Fintech Festival or IETF = then join us for a meetup the evening of 15 November.

Registra= tion and details at: https://= interledger.org/singapore

Tokyo - TBD (= Week of 20 - 24 November)

Finally, we're ke= en to keep the momentum going with a full day workshop and possibly a short= hackathon in Tokyo the following week and are gathering expressions of int= erest to help us wth the planning.

Details at: https://interledger.org/tokyo



--001a11457a649c164f0558b4b0b9-- From nobody Mon Sep 18 20:01:34 2017 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4618E1321B6 for ; Mon, 18 Sep 2017 20:01:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 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_NONE=-0.0001, URIBL_BLOCKED=0.001] 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 hsoMFf7fywSQ for ; Mon, 18 Sep 2017 20:01:30 -0700 (PDT) Received: from mail-ua0-x22a.google.com (mail-ua0-x22a.google.com [IPv6:2607:f8b0:400c:c08::22a]) (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 AEF2B12426E for ; Mon, 18 Sep 2017 20:01:30 -0700 (PDT) Received: by mail-ua0-x22a.google.com with SMTP id 72so1429503uas.8 for ; Mon, 18 Sep 2017 20:01:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopebailie.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=oZbXdDZSvrkD45DbrRDfouaJZPzMA8/+qXFvUafoUbQ=; b=Wd4Pn5EP2op9uaDOJPoUVmQc4RwpgKKXKSFzROmpZ7PEKuKHcLIbrPE5q3VRTp1nWj bzz+dI0iUUUhwEy2oTfO8s7xnx4LgeDJRAAtDXWs0f+5EZhg/0ym2NijOASn581DdA7c dOOb61tHxWXZVAII5j24Xyn2d45H3llIReltQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=oZbXdDZSvrkD45DbrRDfouaJZPzMA8/+qXFvUafoUbQ=; b=f2ePCniijrCPHibr5SCOZvNmOfpQlaX+DNjNaLFCqXI7j2buibxVgAk3yWgEVOymSm 3v7x92Tx5e4woTq3YrlZ6156dI5mI8GaB3zyhhmUmf7lPKps/N7l+Hlwk89dQTlk6Xg7 U3UrGl5GdBXhzaoeymaIQmhSQCQ1EcJ0o/bv834z/VXsHpHgEYF5eD4D8OZbfy1wvjit 2J2PJY5bHYtHzWx1iZXJ6ezhZvJRzSZSEveK7KUemPqShqM/4f6R/yix5vpIfUJ+uuaA gfX3oRhMbr2BMTpAvjx4YxIf7ShXnbcePs1uwCwlmi/f0u8OuEdVgs4HEkQkm7e52VYK G+Lw== X-Gm-Message-State: AHPjjUgSNROo7oRHc9mUvJ1jeLg33HSDjdu6W3IBqLms/ZZQj/9ADd2T vrG+LRTxas25HjInngFUIE8wPjF5DdrLNozgkRCcSRRcNEY= X-Google-Smtp-Source: ADKCNb7aAmZjv7di6Xy1eOCD2fGSNm5sNj3UIuu61EOE8/32dA69UDRvjRXY+nbYMT814Fg2u17fiR3uXHA0LojU79U= X-Received: by 10.176.82.43 with SMTP id i40mr31020943uaa.164.1505790089591; Mon, 18 Sep 2017 20:01:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.60.200 with HTTP; Mon, 18 Sep 2017 20:01:29 -0700 (PDT) From: Adrian Hope-Bailie Date: Mon, 18 Sep 2017 20:01:29 -0700 Message-ID: To: Interledger Community Group , Interledger Mailing List - IETF Content-Type: multipart/alternative; boundary="94eb2c190fae6593a205598213dc" Archived-At: Subject: [Ledger] AGENDA - Interledger Community Call - 21 September - 3pm UTC X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2017 03:01:32 -0000 --94eb2c190fae6593a205598213dc Content-Type: text/plain; charset="UTF-8" This week we'll discuss the Bilateral Transfer Protocol (BTP) (previously called the Common Ledger Protocol (CLP)). This has been under development for a number of weeks and is now frozen so we can focus on implementations and interop testing. The best place to review it is here: https://github.com/interledger/rfcs/blob/726705c99d0324d352ab698eb618ae28d369eef1/00XX-bilateral-transfer-protocol/00XX-bilateral-transfer-protocol.md It is documented as PR 291 The purpose of this protocol is to establish a common standard for communications between nodes on the Interledger encompassing both messaging and transfers. Looking forward to the discussion! --94eb2c190fae6593a205598213dc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
This week we'll discuss the Bilate= ral Transfer Protocol (BTP) (previously called the Common Ledger Protocol (= CLP)).

This has been under development for a number of weeks a= nd is now frozen so we can focus on implementations and interop testing.
The best place to review it is here: https://github= .com/interledger/rfcs/blob/726705c99d0324d352ab698eb618ae28d369eef1/00XX-bi= lateral-transfer-protocol/00XX-bilateral-transfer-protocol.md

It is documented as PR 291

The purpose of this protocol= is to establish a common standard for communications between nodes on the = Interledger encompassing both messaging and transfers.

Looking forward to the discussion!
--94eb2c190fae6593a205598213dc-- From nobody Tue Sep 19 00:43:23 2017 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C312713208E for ; Tue, 19 Sep 2017 00:43:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.698 X-Spam-Level: X-Spam-Status: No, score=-2.698 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, URIBL_BLOCKED=0.001] 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 8kiiiWDtebms for ; Tue, 19 Sep 2017 00:43:21 -0700 (PDT) Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::22a]) (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 EEFCD126DFE for ; Tue, 19 Sep 2017 00:43:20 -0700 (PDT) Received: by mail-vk0-x22a.google.com with SMTP id p204so1421630vkp.7 for ; Tue, 19 Sep 2017 00:43:20 -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=5G9xFVoBxwvHzxJHwzwGWmG1QOKVm1AwRIoN102NQUc=; b=SPA0uxeserlvS8eXA8k1qD7eN0DGot/KzZdBQqQYSa9/qOgm1Bo7UH7Vz3OtsEjT/L IoK6aeL/xYEM80V/D9VSj8547WZZPuBbgqD2tU4HR8oxHBwc32xeJk6NwtyzrmwFFrY9 Av0G0JPdXvxNkidSqECy7JUXEC+KcunfqDsP0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=5G9xFVoBxwvHzxJHwzwGWmG1QOKVm1AwRIoN102NQUc=; b=IstWPmTOipRMveMVYvDwP6ZFHeUIFJ0SImoogdNVwqI13XRzQbxkyi4xxVNkWztyHW 3bdGhv/SwOFc4tO0A7ndmdgWnsu6Lwz6Wtv7AyJ+Oks5A1AbwMdz2VPdm8Wsk66/ngTP Y80t4eDsEKWZsPOzfM9YKGjB956dmYtc0eLnb+FbENbZ+ZPi/nQlVIvwrmEZdF3ZMV4A c2mlB6WC3UQsqIB1CSBRbvwPFqK9Nuxd+Vyy3/u8L/sWZ/mrggEIxynYEiudxLRwv+wC GDGD6joOQpUkSQDza9LlOptCIRWt7pjI7Yt7OPYA5FHEC298SGdEfFaCxgotQoc3CPzV FwCQ== X-Gm-Message-State: AHPjjUjh0g1oRJBtwM9qhUvl9lkvQ5tjxe8yZyU9WuYI0uiQKbHK38Nv 1veD1fK5mCX7rr0o+P7Rvz09v08T+f8Kos0jpthXIuGT X-Google-Smtp-Source: AOwi7QAgc+oS4F/cykl8mDCSBMFMiMtPnj9OF3Fr9trqJqf5IlhoPtaYj07UC39NQKBYaANGPkKj/oflqSn8pQ/KZi0= X-Received: by 10.31.92.212 with SMTP id q203mr334500vkb.27.1505806999950; Tue, 19 Sep 2017 00:43:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.60.200 with HTTP; Tue, 19 Sep 2017 00:43:19 -0700 (PDT) In-Reply-To: References: From: Adrian Hope-Bailie Date: Tue, 19 Sep 2017 00:43:19 -0700 Message-ID: To: Per Lind Cc: Interledger Mailing List - IETF , Interledger Community Group Content-Type: multipart/alternative; boundary="001a114e38fc552d07055986039d" Archived-At: Subject: Re: [Ledger] AGENDA - Interledger Community Call - 21 September - 3pm UTC X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2017 07:43:23 -0000 --001a114e38fc552d07055986039d Content-Type: text/plain; charset="UTF-8" Hi Per, I'm not sure what you are referring to? Can you be more specific. Adrian On 18 September 2017 at 22:57, Per Lind wrote: > I would like to know why NTT and Ripple is now claiming credit for the > Interledger project! Anyone? > > Best, > > Per Lind > Co-founder > IOTA Foundation > +66 8 1110 7667 > > On 19 Sep 2017 10:03, "Adrian Hope-Bailie" wrote: > >> This week we'll discuss the Bilateral Transfer Protocol (BTP) (previously >> called the Common Ledger Protocol (CLP)). >> >> This has been under development for a number of weeks and is now frozen >> so we can focus on implementations and interop testing. >> >> The best place to review it is here: https://github.com/interledger >> /rfcs/blob/726705c99d0324d352ab698eb618ae28d369eef1/00XX- >> bilateral-transfer-protocol/00XX-bilateral-transfer-protocol.md >> >> It is documented as PR 291 >> >> >> The purpose of this protocol is to establish a common standard for >> communications between nodes on the Interledger encompassing both messaging >> and transfers. >> >> Looking forward to the discussion! >> > --001a114e38fc552d07055986039d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Per,

I'm not sure what you a= re referring to? Can you be more specific.

Adrian

On 18 September 2017= at 22:57, Per Lind <per.lind@farmorcloud.asia> wrot= e:
I would like to know= why NTT and Ripple is now claiming credit for the Interledger project! Any= one?

Best,

Per Lind
Co-founder<= /div>
IOTA Foundation
+66 8 1110 76= 67=C2=A0

On 19 Sep 2017 10:03, "Adri= an Hope-Bailie" <adrian@hopebailie.com> wrote:
This week we= 'll discuss the Bilateral Transfer Protocol (BTP) (previously called th= e Common Ledger Protocol (CLP)).

This has been under developme= nt for a number of weeks and is now frozen so we can focus on implementatio= ns and interop testing.

The best place to review it is here: <= a href=3D"https://github.com/interledger/rfcs/blob/726705c99d0324d352ab698e= b618ae28d369eef1/00XX-bilateral-transfer-protocol/00XX-bilateral-transfer-p= rotocol.md" target=3D"_blank">https://github.com/interledger/rfcs/blob= /726705c99d0324d352ab698eb618ae28d369eef1/00XX-bilateral-transfer= -protocol/00XX-bilateral-transfer-protocol.md

It= is documented as PR 291

The purpose of t= his protocol is to establish a common standard for communications between n= odes on the Interledger encompassing both messaging and transfers.

Looking forward to the discussion!

--001a114e38fc552d07055986039d-- From nobody Tue Sep 19 08:14:33 2017 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9D9E1342C9 for ; Mon, 18 Sep 2017 22:57:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=farmorcloud-asia.20150623.gappssmtp.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 6gHGl_fZJbql for ; Mon, 18 Sep 2017 22:57:52 -0700 (PDT) Received: from mail-pg0-x233.google.com (mail-pg0-x233.google.com [IPv6:2607:f8b0:400e:c05::233]) (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 3C5D5132EA7 for ; Mon, 18 Sep 2017 22:57:52 -0700 (PDT) Received: by mail-pg0-x233.google.com with SMTP id d8so1475656pgt.4 for ; Mon, 18 Sep 2017 22:57:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=farmorcloud-asia.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=MkyYHDsgGTOjAEOW6Rkd/H07h3KDpVkQXrmSeI815QE=; b=w4VQzut5tYdFRjHX5iLX6CkHF3LyEOKMBmSbtOlvMw1DDd6VDRsjb83CUUSSBJpejx YVFinNVOz99jvyvY1l1n4hsbuU5+WihJn63G93WMVLFyV/qd/cvC0K4yWHESBXWP+d38 gdNZUMfj31aKAroDPTfbnDKL8d5tAvQzIjnjCiqECMkQGLzlPVkPhLoFM5/kfPmMQE+6 WwS10pN3ZiGfyjhuGmx3vsmrNhGCGhaTCHbnIuY0jmdsTHV86129YFalh5GFuZ3BILRf 7xF3IojsIhmOYEGEWS14RHSA+hlOnUC5dvNjqHBEKooJCwSETw7OZG4dBOB1hU4Kewc/ 5STA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=MkyYHDsgGTOjAEOW6Rkd/H07h3KDpVkQXrmSeI815QE=; b=khw1cF8YXADAToRIicKDZcs5KoPBT2RQ+ymZHqH2gXLlFDOOtBUO/yR0K+R5Q8gbyl FvNBMF8MzmaxuIkAsb81WNmI9Csijgr9yJKblHRifLNREL7q1h98UkmFNiEwmcjHWOPe v/LvGcDtr9OM+8IKN3kyoRCakV/jX6mCHHmcpIH+1xYBwu56sl1tFOcSEvbPlVKMcQ+g ep2JXYCgAHYlPXSGl36U5dcwKx8B+SAgFyQ5Ub4mxpV+25BonMFFpJcMYdCwU2wt5ndv VVqJ7eHogoMhleNqocwDc8kY+lDdZXkON+0YxTpYtHP/N50ZPFmL1koYB4tOee0/5BEo qbgA== X-Gm-Message-State: AHPjjUjsZcOLktqiLZuuZGf/GW0cs6h9YPsdtymWFaRIe0Wehcr0Hrep B/Gxl0AzDcLtqFH+tfYxcpL5nJ5OYNyC/jPyxf8usA== X-Google-Smtp-Source: AOwi7QC6oQEOHi+1ZJ8lMlSzu5XtgEhyj+Xd9512zAZZWi8/tXBJkk96+delcsjGX4oGNPhe4n6MMxDraAlHrMC/n/A= X-Received: by 10.98.201.21 with SMTP id k21mr289986pfg.262.1505800671476; Mon, 18 Sep 2017 22:57:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.151.196 with HTTP; Mon, 18 Sep 2017 22:57:50 -0700 (PDT) Received: by 10.100.151.196 with HTTP; Mon, 18 Sep 2017 22:57:50 -0700 (PDT) In-Reply-To: References: From: Per Lind Date: Tue, 19 Sep 2017 12:57:50 +0700 Message-ID: To: Adrian Hope-Bailie Cc: Interledger Mailing List - IETF , Interledger Community Group Content-Type: multipart/alternative; boundary="94eb2c1876b82051270559848a56" Archived-At: X-Mailman-Approved-At: Tue, 19 Sep 2017 08:14:31 -0700 Subject: Re: [Ledger] AGENDA - Interledger Community Call - 21 September - 3pm UTC X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2017 05:57:54 -0000 --94eb2c1876b82051270559848a56 Content-Type: text/plain; charset="UTF-8" I would like to know why NTT and Ripple is now claiming credit for the Interledger project! Anyone? Best, Per Lind Co-founder IOTA Foundation +66 8 1110 7667 On 19 Sep 2017 10:03, "Adrian Hope-Bailie" wrote: > This week we'll discuss the Bilateral Transfer Protocol (BTP) (previously > called the Common Ledger Protocol (CLP)). > > This has been under development for a number of weeks and is now frozen so > we can focus on implementations and interop testing. > > The best place to review it is here: https://github.com/ > interledger/rfcs/blob/726705c99d0324d352ab698eb618ae > 28d369eef1/00XX-bilateral-transfer-protocol/00XX- > bilateral-transfer-protocol.md > > It is documented as PR 291 > > The purpose of this protocol is to establish a common standard for > communications between nodes on the Interledger encompassing both messaging > and transfers. > > Looking forward to the discussion! > --94eb2c1876b82051270559848a56 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I would like to know why NTT and Ripple is now claiming c= redit for the Interledger project! Anyone?

Best,

Per L= ind
Co-founder
IOTA Foundatio= n
+66 8 1110 7667=C2=A0

On 19 Sep 2017 10:03, "Adrian= Hope-Bailie" <adrian@hope= bailie.com> wrote:
This week we'll discuss the = Bilateral Transfer Protocol (BTP) (previously called the Common Ledger Prot= ocol (CLP)).

This has been under development for a number of w= eeks and is now frozen so we can focus on implementations and interop testi= ng.

The best place to review it is here: https://github.com/interledger/rfcs/blob/726705c99d03= 24d352ab698eb618ae28d369eef1/00XX-bilateral-transfer-protocol/00X= X-bilateral-transfer-protocol.md

It is documented as = PR 291

The purpose of this protocol is to= establish a common standard for communications between nodes on the Interl= edger encompassing both messaging and transfers.

Lo= oking forward to the discussion!
--94eb2c1876b82051270559848a56-- From nobody Tue Sep 19 08:14:38 2017 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F3801342E1 for ; Tue, 19 Sep 2017 00:48:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=farmorcloud-asia.20150623.gappssmtp.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 mes5W384w7Rj for ; Tue, 19 Sep 2017 00:47:58 -0700 (PDT) Received: from mail-pf0-x22e.google.com (mail-pf0-x22e.google.com [IPv6:2607:f8b0:400e:c00::22e]) (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 68B491342D5 for ; Tue, 19 Sep 2017 00:47:58 -0700 (PDT) Received: by mail-pf0-x22e.google.com with SMTP id n24so1589266pfk.5 for ; Tue, 19 Sep 2017 00:47:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=farmorcloud-asia.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lVOzL09qH2vxaifppOZi3G8o4BgUWCYatcD/UM8oij0=; b=PL+qGw7Je42dXcUiJ+E1zmYMSOhIz82OjdRBgIV2hBFS5Dfrzrn2THrVHRg0sN75cU FFYQj2ZfHx3p5ezKgm40zoslUFWpQwP1hBvLnINbYgpxS4xlrDuXIjNEinaeQwIq5dYP vP5C745GBoMvq+mE4F01kCA++Jav5jxxPKphYUR35U+3NpACTnzqjKXqIca0aKRGMHEg ZrS1NwJyLbXT9dFSx5ybVdQx/Ha0ALAxjs565eCcF57W2VI8WMyp7YgzTrsUfW3JPyZl gHZKqBmVDF1w5p47/51P2OuPuQlbKfidAmRTfRz53aq7ShnHmYoY59sSVYPXqhLkfy/L xJyw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=lVOzL09qH2vxaifppOZi3G8o4BgUWCYatcD/UM8oij0=; b=NyIZj7hqNeTX9ZCTpqYOlUo12/zohz9ERYVx0mRlHLZ8v0tehLE8EA3Jjjeit9w4m3 I7hjOJ7CVZRtEyVqTtyFBX1mMNglqka9euL9wDhvqWZPMCAZKQna5IoyW8papIchVtPu Vk1rSBBZ/dWu5z8mvRY1xPeS6UL1tdI/C20K1ckfFftrZjUUjRxhtMFasFTt+1LnwbiL Har6BPWsbRSlinOyBafBk4eK2a5WrHRjov0hApAt28YtKKoeiZs0SHbxkA5SeQoZFfOf pxz+K8UY4JrTi70UV5y8DpxMnaQXinCQCGk5FQGCKAKeFHKUUB7I/HZb28LOsjKUqdDa JYIA== X-Gm-Message-State: AHPjjUhnmON4EL6Ax9DTDCFaQFONCYfWlq7e054YGptHOMoGOyQbb4sA OD7kL6zpYmB7JsUlpM1ODAb+BOLBafLKaZQTdywllw== X-Google-Smtp-Source: AOwi7QB4NaDMdqQa6NcvF5Thdc/bobzaq1MyIUoKAYHR0DGY1vvvonTeHUaE22yVYF8sUH4OdXUtt9bZFt952Y9TkSQ= X-Received: by 10.98.17.156 with SMTP id 28mr486925pfr.83.1505807277871; Tue, 19 Sep 2017 00:47:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.151.196 with HTTP; Tue, 19 Sep 2017 00:47:57 -0700 (PDT) Received: by 10.100.151.196 with HTTP; Tue, 19 Sep 2017 00:47:57 -0700 (PDT) In-Reply-To: References: From: Per Lind Date: Tue, 19 Sep 2017 14:47:57 +0700 Message-ID: To: Adrian Hope-Bailie Cc: Interledger Mailing List - IETF , Interledger Community Group Content-Type: multipart/alternative; boundary="001a11458fc4e5e4f505598613ba" Archived-At: X-Mailman-Approved-At: Tue, 19 Sep 2017 08:14:31 -0700 Subject: Re: [Ledger] AGENDA - Interledger Community Call - 21 September - 3pm UTC X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2017 07:48:00 -0000 --001a11458fc4e5e4f505598613ba Content-Type: text/plain; charset="UTF-8" https://www.coindesk.com/old-flames-new-code-ripple-hyperledger-reunite-interledger-effort/ On 19 Sep 2017 14:43, "Adrian Hope-Bailie" wrote: Hi Per, I'm not sure what you are referring to? Can you be more specific. Adrian On 18 September 2017 at 22:57, Per Lind wrote: > I would like to know why NTT and Ripple is now claiming credit for the > Interledger project! Anyone? > > Best, > > Per Lind > Co-founder > IOTA Foundation > +66 8 1110 7667 > > On 19 Sep 2017 10:03, "Adrian Hope-Bailie" wrote: > >> This week we'll discuss the Bilateral Transfer Protocol (BTP) (previously >> called the Common Ledger Protocol (CLP)). >> >> This has been under development for a number of weeks and is now frozen >> so we can focus on implementations and interop testing. >> >> The best place to review it is here: https://github.com/interledger >> /rfcs/blob/726705c99d0324d352ab698eb618ae28d369eef1/00XX-bil >> ateral-transfer-protocol/00XX-bilateral-transfer-protocol.md >> >> It is documented as PR 291 >> >> >> The purpose of this protocol is to establish a common standard for >> communications between nodes on the Interledger encompassing both messaging >> and transfers. >> >> Looking forward to the discussion! >> > --001a11458fc4e5e4f505598613ba Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On 19 Sep 2017 14:4= 3, "Adrian Hope-Bailie" <adrian@hopebailie.com> wrote:
Hi Per,

I'm not = sure what you are referring to? Can you be more specific.

Adrian
<= div class=3D"elided-text">

On 18 September 2017 at 22:57, Per Lind <per.lind@farmorc= loud.asia> wrote:
I would like to know why NTT and Ripple is now claiming credit fo= r the Interledger project! Anyone?

Best,

Per Lind
Co-founder
IOTA Foundation
<= div dir=3D"auto">+66 8 1110 7667=C2=A0

On 19 Sep 2017 10:03, "Adria= n Hope-Bailie" <adrian@hopebailie.com> wrote:
This week we&= #39;ll discuss the Bilateral Transfer Protocol (BTP) (previously called the= Common Ledger Protocol (CLP)).

This has been under developmen= t for a number of weeks and is now frozen so we can focus on implementation= s and interop testing.

The best place to review it is here: https://github.com/interledger/rfcs/blob/= 726705c99d0324d352ab698eb618ae28d369eef1/00XX-bilateral-transfer-= protocol/00XX-bilateral-transfer-protocol.md

It is do= cumented as PR 291

The purpose of this pr= otocol is to establish a common standard for communications between nodes o= n the Interledger encompassing both messaging and transfers.
=
Looking forward to the discussion!


--001a11458fc4e5e4f505598613ba-- From nobody Tue Sep 19 15:07:02 2017 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39A641343AC for ; Tue, 19 Sep 2017 15:07:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.698 X-Spam-Level: X-Spam-Status: No, score=-2.698 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, URIBL_BLOCKED=0.001] 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 aH2Q2w5M3iIe for ; Tue, 19 Sep 2017 15:06:59 -0700 (PDT) Received: from mail-vk0-x22f.google.com (mail-vk0-x22f.google.com [IPv6:2607:f8b0:400c:c05::22f]) (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 45D82134343 for ; Tue, 19 Sep 2017 15:06:59 -0700 (PDT) Received: by mail-vk0-x22f.google.com with SMTP id g69so536470vke.5 for ; Tue, 19 Sep 2017 15:06:59 -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=2Z54HR2SR6YT5fKptqiZj7k+hy+vouHFFCl6CX8gCNs=; b=dG+eA5szkTgnnsuBga45dcxxGd0gUzmUnC6odVwQN+HC+PYPzxBY8IdZE46zXdOOL1 bbPl+oFq4WaGjWhS4whdlfZ1QgDLM7gCj3KYJTzoQus2QTw2cPo5bK9NZ0gvsPyhzJJF W8ZMou/dC0NOxZJImYDVQWTHozV1XhOM5xEkE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=2Z54HR2SR6YT5fKptqiZj7k+hy+vouHFFCl6CX8gCNs=; b=HpTEV34CJ4oqD9Qnp/vuvA4fNUvC2rDd/Dc7Em76VZh/Sqzr2fZMlC6u7vY2lwWIeG MLOoCJ8tZQRkjhhTwhtMxytVsO9Ip4HetqS5mYrX7cC2Je5s64ayPr7Iqj6t1LLCi3nu IUKr3qXaolSryvITcVqIejg0GGW0bRLetjUg1UB550gN621s75YJIgJhL6eftbc1uqcW /uVjUSKytyrGMn2VLcr5qB3kFQqP4h0SVrtcx5zRG+CkLK61Pi3sfoxmxrtTlL+gAyqm YAbKXhTNxwdQAaAQt8smh6v6HOxVdqukViptOXnAK8Op/jpjqPpaQiTNd1XRCLCs6jB5 uGYQ== X-Gm-Message-State: AHPjjUjvtnvCoQS+lflneMv8kHkPE0S7doPkoiElON5y6KpMTO8BUctu E695/gdQF4nWCX6yKbL23Xgc4ZcKbmR74cXKAGw4L1RWMnU= X-Google-Smtp-Source: AOwi7QCzHbTz0bfLxEm+hUwT1uqFyiLxcv7xV766hwDy96zSEHW4ok6J1r5i8CCNdmqDeU01s10EAid8QFw7QxodcPY= X-Received: by 10.31.15.4 with SMTP id 4mr2254602vkp.191.1505858818031; Tue, 19 Sep 2017 15:06:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.60.200 with HTTP; Tue, 19 Sep 2017 15:06:57 -0700 (PDT) In-Reply-To: References: From: Adrian Hope-Bailie Date: Tue, 19 Sep 2017 15:06:57 -0700 Message-ID: To: Per Lind Cc: Interledger Mailing List - IETF , Interledger Community Group Content-Type: multipart/alternative; boundary="001a11433da8ee786405599213e5" Archived-At: Subject: Re: [Ledger] AGENDA - Interledger Community Call - 21 September - 3pm UTC X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2017 22:07:01 -0000 --001a11433da8ee786405599213e5 Content-Type: text/plain; charset="UTF-8" Ripple and NTT (actually, primarily a subsidiary of NTT, Everis) are initiating a new project at the Hyperledger Foundation which will be focused on interoperability. The project will be an implementation of the Interledger protocol and will be written in Java, Taking the existing Java implementations as it's starting code base. These two companies have been the primary contributors to the Java implementations so I'm not sure why it's surprising they'd be the sponsors of this project? This new project doesn't replace the existing ILP community which is focused on development of the protocol and standards. i.e. The community deliverables are specifications, the new project's deliverables will be code libraries (implementations of the protocol). The existing Java code libraries do not have a "home" today as there is no neutral legal entity to which the licenses can be attributed and no governance framework or contributor agreements. The Hyperledger foundation offers such a framework (in the same way that the JS Foundation already does for the Javascript code components). More details in the proposal: https://docs.google.com/document/d/1KVrakb2JsqgMo2aG-QIYl743VHsU9NWYKxy7n-WeXv4/edit If IOTA is able to commit resources to contributing to this project that would be great, we'd love to share that commitment with the TSC at Hyperledger when we meet next week. On 19 September 2017 at 00:47, Per Lind wrote: > https://www.coindesk.com/old-flames-new-code-ripple-hyperledger-reunite- > interledger-effort/ > > On 19 Sep 2017 14:43, "Adrian Hope-Bailie" wrote: > > Hi Per, > > I'm not sure what you are referring to? Can you be more specific. > > Adrian > > On 18 September 2017 at 22:57, Per Lind wrote: > >> I would like to know why NTT and Ripple is now claiming credit for the >> Interledger project! Anyone? >> >> Best, >> >> Per Lind >> Co-founder >> IOTA Foundation >> +66 8 1110 7667 >> >> On 19 Sep 2017 10:03, "Adrian Hope-Bailie" wrote: >> >>> This week we'll discuss the Bilateral Transfer Protocol (BTP) >>> (previously called the Common Ledger Protocol (CLP)). >>> >>> This has been under development for a number of weeks and is now frozen >>> so we can focus on implementations and interop testing. >>> >>> The best place to review it is here: https://github.com/interledger >>> /rfcs/blob/726705c99d0324d352ab698eb618ae28d369eef1/00XX-bil >>> ateral-transfer-protocol/00XX-bilateral-transfer-protocol.md >>> >>> It is documented as PR 291 >>> >>> >>> The purpose of this protocol is to establish a common standard for >>> communications between nodes on the Interledger encompassing both messaging >>> and transfers. >>> >>> Looking forward to the discussion! >>> >> > > --001a11433da8ee786405599213e5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Ripple and NTT (actually, primari= ly a subsidiary of NTT, Everis) are initiating a new project at the Hyperle= dger Foundation which will be focused on interoperability.
The pro= ject will be an implementation of the Interledger protocol and will be writ= ten in Java, Taking the existing Java implementations as it's starting = code base.

These two companies have been the primary co= ntributors to the Java implementations so I'm not sure why it's sur= prising they'd be the sponsors of this project?

This new p= roject doesn't replace the existing ILP community which is focused on d= evelopment of the protocol and standards.
i.e. The community deliv= erables are specifications, the new project's deliverables will be code= libraries (implementations of the protocol).

The = existing Java code libraries do not have a "home" today as there = is no neutral legal entity to which the licenses can be attributed and no g= overnance framework or contributor agreements.
The Hyperledger fo= undation offers such a framework (in the same way that the JS Foundation al= ready does for the Javascript code components).

<= br>
If IOTA is able to commit resources to contributing to this p= roject that would be great, we'd love to share that commitment with the= TSC at Hyperledger when we meet next week.

<= div class=3D"gmail_extra">
On 19 September 20= 17 at 00:47, Per Lind <per.lind@farmorcloud.asia> wr= ote:

On 19 Sep 2017 14:43, "Adrian Hope-Bailie" <= adrian@hopebaili= e.com> wrote:
Hi Per,

I'm no= t sure what you are referring to? Can you be more specific.

Adrian

On 18 September 2017 at 22:57, Per Lind <per.lind@farmorcloud.asia> wrote:
I would like to know why NTT and Ripple is= now claiming credit for the Interledger project! Anyone?
=
Best,

Per Lind
Co-founder
IOTA Foundation
+66 8 1110 7667=C2=A0

On 19 Sep 2017 10:03, "Adrian Hope-= Bailie" <adrian@hopebailie.com> wrote:
This week we'll = discuss the Bilateral Transfer Protocol (BTP) (previously called the Common= Ledger Protocol (CLP)).

This has been under development for a= number of weeks and is now frozen so we can focus on implementations and i= nterop testing.

The best place to review it is here: https://github.com/interledger/rfcs/blob/72670= 5c99d0324d352ab698eb618ae28d369eef1/00XX-bilateral-transfer-proto= col/00XX-bilateral-transfer-protocol.md

It is documen= ted as PR 291

The purpose of this protoco= l is to establish a common standard for communications between nodes on the= Interledger encompassing both messaging and transfers.

<= /div>Looking forward to the discussion!



--001a11433da8ee786405599213e5-- From nobody Wed Sep 20 09:45:55 2017 Return-Path: X-Original-To: ledger@ietfa.amsl.com Delivered-To: ledger@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A33F013202D for ; Wed, 20 Sep 2017 09:45:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 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_NONE=-0.0001] 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 yAR6SJUON6V7 for ; Wed, 20 Sep 2017 09:45:45 -0700 (PDT) Received: from mail-ua0-x234.google.com (mail-ua0-x234.google.com [IPv6:2607:f8b0:400c:c08::234]) (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 1FCB01330B3 for ; Wed, 20 Sep 2017 09:45:45 -0700 (PDT) Received: by mail-ua0-x234.google.com with SMTP id l94so2051197ual.11 for ; Wed, 20 Sep 2017 09:45:45 -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; bh=NGSWt6crtDaW9kqwW9bEe3iHI/q40UyZJs2yCMATROg=; b=d3pEV9frDeRT92QeDORQTOUelWbk0numgTQv5cG+O9400esbPHbnaCnIOG3O2CHZlY 0ZPhfpWsG2QtEYqU/0McA3C1SymKEB4wnj5D/oBVjOH1JW3mKyZ02qpg6B82TTGUNeHW oub+dC4YqYkvgadMDCMw9bwI8dOOKf6z1K5F8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=NGSWt6crtDaW9kqwW9bEe3iHI/q40UyZJs2yCMATROg=; b=BwfVemagdXTDe8gFu0Hy69SeCyjutjSgjT2NalQpPNmPGPJSNq7gcFx+EGO0EqC2UV dvsVqy9WqmMQOzvlMmAAfXPkmGIXEAChK2Kj/ffnRg3XFbcx9lz5wVGQdPGodIJGWyKQ BXCMgwA/LSgWlXXHgG88chId+7m5e4LJOaK3jc8dMjjK/kFSuapnDOMF1ocdF2EPwXSj vMdF5eUxndaWqsEalVvtTw8ORWzMw7LxVCsLTEzBGKJ1K/C8anq2wwKV9erSkClqq/Th fiv0q9iGgaXBp0RHAcVEcro7xeBuR2BcWLv1tzMBkyh86QQZxPFbVk9mzMBTYl2dQqV4 b3eQ== X-Gm-Message-State: AHPjjUimi9d0Fh9O3Q68EXHFIAgmcVXraOcqutOtSQ42tLk8uybLrazN Jx7FOFODXm9Zd1/xGPOOWR80qjIUIPX/nLQpX88CKQ== X-Google-Smtp-Source: AOwi7QBHT9StGDmyKs9pr4O6+gJataIUFG2A1xluBZ89adhf1BEt6UUeueQMwxErQ/W8nUk45Y9ZdUqTqoEdgqGyJ4E= X-Received: by 10.159.32.36 with SMTP id 33mr5129313uam.41.1505925944113; Wed, 20 Sep 2017 09:45:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.60.200 with HTTP; Wed, 20 Sep 2017 09:45:43 -0700 (PDT) In-Reply-To: References: From: Adrian Hope-Bailie Date: Wed, 20 Sep 2017 09:45:43 -0700 Message-ID: To: Interledger Community Group , Interledger Mailing List - IETF Content-Type: multipart/alternative; boundary="94eb2c04c5c2f565ec0559a1b4bf" Archived-At: Subject: Re: [Ledger] AGENDA - Interledger Community Call - 21 September - 3pm UTC X-BeenThere: ledger@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of interledger, originally a protocol stack for moving digital assets \(making payments\) between accounts operating on different payment networks or ledgers." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Sep 2017 16:45:48 -0000 --94eb2c04c5c2f565ec0559a1b4bf Content-Type: text/plain; charset="UTF-8" NO CALL on 21 September Apologies for the date mix-up. The call was earlier today (as usual on a Wednesday). Next call is in 2 weeks (Wednesday 4 October). On 18 September 2017 at 20:01, Adrian Hope-Bailie wrote: > This week we'll discuss the Bilateral Transfer Protocol (BTP) (previously > called the Common Ledger Protocol (CLP)). > > This has been under development for a number of weeks and is now frozen so > we can focus on implementations and interop testing. > > The best place to review it is here: https://github.com/ > interledger/rfcs/blob/726705c99d0324d352ab698eb618ae > 28d369eef1/00XX-bilateral-transfer-protocol/00XX- > bilateral-transfer-protocol.md > > It is documented as PR 291 > > The purpose of this protocol is to establish a common standard for > communications between nodes on the Interledger encompassing both messaging > and transfers. > > Looking forward to the discussion! > --94eb2c04c5c2f565ec0559a1b4bf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
NO CALL on 21 September

Apologies f= or the date mix-up. The call was earlier today (as usual on a Wednesday).
Next call is in 2 weeks (Wednesday 4 October).

On 18 September 2017 at 20:= 01, Adrian Hope-Bailie <adrian@hopebailie.com> wrote:
This w= eek we'll discuss the Bilateral Transfer Protocol (BTP) (previously cal= led the Common Ledger Protocol (CLP)).

This has been under dev= elopment for a number of weeks and is now frozen so we can focus on impleme= ntations and interop testing.

The best place to review it is h= ere: https://github.com/interledger/rfc= s/blob/726705c99d0324d352ab698eb618ae28d369eef1/00XX-bilateral-transfer-protocol/00XX-bilateral-transfer-protocol.md

It is documented as PR 291

The purpos= e of this protocol is to establish a common standard for communications bet= ween nodes on the Interledger encompassing both messaging and transfers.

Looking forward to the discussion!

--94eb2c04c5c2f565ec0559a1b4bf--