Re: [Din] Draft IETF-101 DINRG meeting minutes

"Dirk Kutscher" <ietf@dkutscher.net> Mon, 26 March 2018 14:41 UTC

Return-Path: <ietf@dkutscher.net>
X-Original-To: din@ietfa.amsl.com
Delivered-To: din@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60F6E1275FD for <din@ietfa.amsl.com>; Mon, 26 Mar 2018 07:41:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no
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 lqrhZCvTP6Z7 for <din@ietfa.amsl.com>; Mon, 26 Mar 2018 07:41:27 -0700 (PDT)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.187]) (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 1811F12420B for <din@irtf.org>; Mon, 26 Mar 2018 07:41:26 -0700 (PDT)
Received: from [192.168.178.50] ([77.21.39.2]) by mrelayeu.kundenserver.de (mreue007 [212.227.15.167]) with ESMTPSA (Nemesis) id 0MUPVW-1f9vGB1HTW-00QyT8 for <din@irtf.org>; Mon, 26 Mar 2018 16:41:25 +0200
From: Dirk Kutscher <ietf@dkutscher.net>
To: din@irtf.org
Date: Mon, 26 Mar 2018 16:41:24 +0200
X-Mailer: MailMate (1.11r5462)
Message-ID: <F677227C-3AB6-4443-9F05-0F5537C8ED4F@dkutscher.net>
In-Reply-To: <87efk8t6g0.fsf@ta.scs.stanford.edu>
References: <BDF91284-3DCA-4397-AF51-125ED358822F@dkutscher.net> <87efk8t6g0.fsf@ta.scs.stanford.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:BEQ+jI4wEaDezoAfSj+bW0vcCR2QFaKkUe4CSWIqTVV/blKXyHn dl+4+lglc2athhZy3bq9rp6SZ+NrM5MBxevUdQsM8LTkRU4FGRlbtOiwKb1PPm6pWFQyERs sXrLplCAv3bVLA8srmgqamx8fqwLyTYPxrV2BrUaHK0/t64aQLEtax0vvfM+CS4e+cZSUq9 pslwN6tndpBSsTyy/uM8w==
X-UI-Out-Filterresults: notjunk:1;V01:K0:BtzRTRpsae0=:Sry6BP22uphyqiIymNnelg ViPlgPhhNgsxxFANRqf6Mq8enyF8CYQoqpIOdqygI54o5BChJoMj0ayLtuC6/waleeft65h3F laAWvgXUGVJrhFbkWc/FcknULMnWzI31xNmFHIlpcL3ihmOa6LW9CsSHbxIvRCphQjv1B+PPL NwZPH88K3oz7gKGKbU5dvetdJFVQyApb08RR51Hu9mAoF5lNYWy7PewXtm949LaMP1s3ukf6+ 6k4FAVspie8lHDNsfKVOZDqqbevjiRJMnW+sbUE4N+KbBIJcukX4bzji3wFLkc5lVD8H+qN9+ PgH+9UIyZSZnzXVBOYIypVtQFRS5v8L+diPksNFLNQnVJIQLcd8LcYheGYFPPOb1UhoNoclx/ wLo3suoj9/Nhy3TOQuby9gLHUAAw0kDjX7S2acmr4bm/l4HlCm+hX+JiAT0NxI7qrl5T2PuTh bSe0fSe/nE6sg9JwlAV2N4GdVlmrm5bKwRF1zWOybFHQwehunI1VEP0yhryhg0EG9GBmcFYT9 VbEZX5sjnQ7Ju3RMUykf+VvY7o7+vst7R8czka/mD30dcGm0264fojGSSMXPleIK0NzDT0w6p ZCgLSJrjIyIyHH8MpyPrNbsryoHROE5hHm74dJWMQ3Tyr4ej8vsyzZGlmxscNQuT0ymduGu5H ZVQ8SSFaMGHd7ShrXZgnJ4zyhp9A+IvQk7Vutp0K7GShTLC+iWniCaUWnPKP3APmxq3EEb8/G iGn1jMx6b87FLbvNj0k8jQHVJyccGONzz0Pj7qXWfaBiFGFbENd6iXZ6mSo=
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/WA7pTe7k3pIJAfcKvbZimdGdY78>
Subject: Re: [Din] Draft IETF-101 DINRG meeting minutes
X-BeenThere: din@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" <din.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/din>, <mailto:din-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/din/>
List-Post: <mailto:din@irtf.org>
List-Help: <mailto:din-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/din>, <mailto:din-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2018 14:41:31 -0000

Thanks — I’ll clarify that in the minutes.

(This is exactly why we are asking for comments on the draft minutes — 
there may have been misunderstandings, language problems etc.)

Dirk

On 25 Mar 2018, at 19:23, David Mazieres wrote:

> Dirk Kutscher <ietf@dkutscher.net> writes:
>
>> Hi,
>>
>> We have posted the draft minutes from last week’s meeting:
>> https://datatracker.ietf.org/meeting/101/materials/minutes-101-dinrg-00.html
>>
>> Thanks a lot to our note takers Chris and Jordi Paillissé!
>>
>> Everyone, please let us know if you have additions or corrections.
>
> For Chainspace, my comment:
>
>         David: Can amortize cost over arbitrarily many transactions,
>         which has latency, but still low throughput. You could batch
>         transactions to increase throughput.
>
> I think maybe I said "but high throughput," not low?  I don't remember
> my exact words, but the point I intended to make is that the consensus
> algorithm should not impact throughput at all, only latency, since you
> can amortize a single round of consensus over an arbitrary number of
> transactions.
>
> David
>
> _______________________________________________
> Din mailing list
> Din@irtf.org
> https://www.irtf.org/mailman/listinfo/din