Re: [Din] draft-mazieres-dinrg-scp-04 (page 16) setting preparedPrime

David Mazieres <dm-list-ietf-ilc@scs.stanford.edu> Sat, 29 September 2018 01:46 UTC

Return-Path: <dm-list-ietf-ilc@scs.stanford.edu>
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 10115130DEB for <din@ietfa.amsl.com>; Fri, 28 Sep 2018 18:46:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=scs.stanford.edu
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 5w1Yexl3KF3o for <din@ietfa.amsl.com>; Fri, 28 Sep 2018 18:46:10 -0700 (PDT)
Received: from market.scs.stanford.edu (www.scs.stanford.edu [IPv6:2001:470:806d:1::9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91F28130DD7 for <din@irtf.org>; Fri, 28 Sep 2018 18:46:10 -0700 (PDT)
Received: from market.scs.stanford.edu (localhost [127.0.0.1]) by market.scs.stanford.edu (8.16.0.21/8.16.0.21) with ESMTP id w8T1k7wr058495; Fri, 28 Sep 2018 18:46:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=scs.stanford.edu; s=scs; t=1538185567; bh=xnV5dpm/dDlzymH66+CZRA/cnh0ttRLEX5UQP/ar0sY=; h=From:To:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version; b=DNiY2FsQ5/caTzWjs6oC3ADwklNvIz3+qlPlqGC2BAi88XA643DZXSRWNW8/RJETs 37RllQnSTYwgerJW0Y786cmkeMkFk9vluJmUflTwj2nn5oD/om7ZTqMs0GrN+J7w5j 21kp1AxIDbaG2h0jSLSuwdhs5ZYOBmR01ecHhjHU=
Received: (from dm@localhost) by market.scs.stanford.edu (8.16.0.21/8.16.0.21/Submit) id w8T1k7uJ064928; Fri, 28 Sep 2018 18:46:07 -0700 (PDT)
From: David Mazieres <dm-list-ietf-ilc@scs.stanford.edu>
To: Piers Powlesland <pierspowlesland@gmail.com>, din@irtf.org
In-Reply-To: <CAFXacXk5KeMbSWfgUvi7LL+Ca64HD30vwA-iAi_QcCZmtDWqvw@mail.gmail.com>
References: <CAFXacXk5KeMbSWfgUvi7LL+Ca64HD30vwA-iAi_QcCZmtDWqvw@mail.gmail.com>
Reply-To: David Mazieres expires 2018-12-27 PST <mazieres-fev3hh3q6e9d3mijfy7x2ybtk6@temporary-address.scs.stanford.edu>
Date: Fri, 28 Sep 2018 18:46:06 -0700
Message-ID: <87k1n53wkh.fsf@ta.scs.stanford.edu>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/Ss1pt1g798sv4MTu3K2Cb2X2Ve8>
Subject: Re: [Din] draft-mazieres-dinrg-scp-04 (page 16) setting preparedPrime
X-BeenThere: din@irtf.org
X-Mailman-Version: 2.1.29
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: Sat, 29 Sep 2018 01:46:12 -0000

Piers Powlesland <pierspowlesland@gmail.com> writes:

> In the section "preparedPrime", I'm wondering if the "highest accepted
> prepared ballot", is referring to a concrete ballot that has been seen
> or a ballot within the conceptual space of ballots?
>
> For example, if we consider a system with 3 possible values x, y and z and
> x<y<z. If you imagine we have p == (4,z) and we see blocking threshold for
> (3,x) and so set p' == (3,x) if you consider the ballots that have been
> accepted aborted through p and p', you can see that all the ballots required to
> be aborted in order for (3,y) to be considered prepared have been aborted. Do
> we now set p' to (3,y) since (3,y) is greater than (3,x) ?

Thanks for raising the point.  The short answer is that it doesn't
matter--the protocol works either way.

The slightly longer answer, which someone recently pointed out to me, is
that because of this fact, it is actually wasteful to send around the
value of preparedPrime, rather than just the counter.  So the next
revision of the draft will probably address this question...

David