Re: [Din] New SCP draft

Piers Powlesland <pierspowlesland@gmail.com> Thu, 14 June 2018 11:09 UTC

Return-Path: <pierspowlesland@gmail.com>
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 3A25E130F3F for <din@ietfa.amsl.com>; Thu, 14 Jun 2018 04:09:14 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 mNOKnXzBfa2H for <din@ietfa.amsl.com>; Thu, 14 Jun 2018 04:09:11 -0700 (PDT)
Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::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 8E9FE130E0A for <din@irtf.org>; Thu, 14 Jun 2018 04:09:11 -0700 (PDT)
Received: by mail-wr0-x233.google.com with SMTP id o12-v6so5951339wrm.12 for <din@irtf.org>; Thu, 14 Jun 2018 04:09:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=PxhcEBRzlKlKU/jgcjU7izV4AGBC+guCa3Y2GBdeWJo=; b=qlYswgPP4j5Hh+szKm35d1zSpx+Y4IhFlFmdOOLLCTSQiLq5MXvKIgUsMoLSK8cQI7 JDa7l20ol/AhaVmj1bcuIHcywLVj2aSuIxwjLs2DvV5OIy2XjnAdKxeikjaZ7aEUDUyw PDb6Abb16cN3wSQ7hJWPt3G2ZIThLjbBDnG358a7ceDIqaHCOEpcSUOyqXCMtiec8acX LyAbJ1uQVQsys2oObe6wbFsvHU/I47bG0bkCtu72gTNuEEl++VBuCQcyaVlOAeyI8dWv IinUhPXy/5ngd6y/CXt/OMYUdTq+LUidMzX076cW2e1kVdAtcASbuhB0F8PlWptHgKq+ d72Q==
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=PxhcEBRzlKlKU/jgcjU7izV4AGBC+guCa3Y2GBdeWJo=; b=hG62Kf0QG+hXob1Fi/clWazq6jLCEdCi3dhOq2la9ndjQHJGdSydUkEtiMrUmPguc4 YtueZXEfqe+HFwrhDZXJU5m9aJGkl7zGBU1Ix7yGXlS03hcdzv5TN7EMtqKZYdxpncAJ tcNrwo1ZbCrChg8mnGM56g7ojnunpuidF0rJjnQtxD8HUZlD2nMO737cDWxDgG4mt1+D /XsYwCdzXE97xLs45FBcgNNcQz/dSZYtrbvAowBbg+9VDFlz3QOqB3J5l9QKGvfrkzKu ML1iL9W5/5Fq7yjZJSJYTZuNWx/OcqpDj7xDNLUrFxHgghkaXreS0RKUs2IDYEIqpUEM HgPg==
X-Gm-Message-State: APt69E2zoJOA72lLYKsV/VFZ8yVp3G9hYsWBO7Nh0deCBruCFmKs5+YN D9tfL5SZVcwCsOAkr9U9yXO5EWia/PK2gO5MEn6HLA==
X-Google-Smtp-Source: ADUXVKJFfFekgjs6jDoHIJ0bOE7o565T7Fn98s9wFlzBwyQQzi/dZV6/mP8hLMvU0bFD6mT8TOfnAg9Sq2MQ/HTsyWM=
X-Received: by 2002:adf:d10a:: with SMTP id a10-v6mr1750398wri.18.1528974549958; Thu, 14 Jun 2018 04:09:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:adf:eec9:0:0:0:0:0 with HTTP; Thu, 14 Jun 2018 04:09:09 -0700 (PDT)
In-Reply-To: <87vaambccw.fsf@ta.scs.stanford.edu>
References: <87vaambccw.fsf@ta.scs.stanford.edu>
From: Piers Powlesland <pierspowlesland@gmail.com>
Date: Thu, 14 Jun 2018 12:09:09 +0100
Message-ID: <CAFXacXk7acKpvA5RvLJuxgWfCCD3hOAxjwaD56Td-uzJ9cnB+w@mail.gmail.com>
To: David Mazieres expires 2018-09-11 PDT <mazieres-eq766ki9si5biqs9svj98v52hi@temporary-address.scs.stanford.edu>
Cc: din@irtf.org
Content-Type: multipart/alternative; boundary="000000000000ebc529056e982081"
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/iQ4qjs5THLdoqE88vBTnxh3SI0w>
Subject: Re: [Din] New SCP draft
X-BeenThere: din@irtf.org
X-Mailman-Version: 2.1.26
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: Thu, 14 Jun 2018 11:09:14 -0000

Hi David,

A couple of thoughts.

I think SCPQuorumSet could be renamed to SCPScliceSet or SCPQuorumSliceSet.
As it is, the naming implies that the set contains quorums when in fact it
may not.

Also does echoing a peer involve forwarding messages from a peer to other
peers? My usual understanding of the word "echo" is that a message sent is
sent back, in this context my immediate understanding of "echoing a peer"
would be that messages from a peer are forwarded on or redistributed to the
network, but the definition of echoing a peer makes no mention of that.

'To echo "v", the node merges any valid values from "v"’s "voted" and
"accepted" sets into its own "voted" set.'



On Wed, Jun 13, 2018 at 10:33 PM, David Mazieres <
dm-list-ietf-ilc@scs.stanford.edu> wrote:

> Hi, everyone.  We've posted a new draft of the SCP protocol spec in the
> usual place:
>
>         https://datatracker.ietf.org/doc/draft-mazieres-dinrg-scp/
>
> In addition to a bunch of clarifications, the new draft addresses a bug
> or serious ambiguity in how nodes may exit the NOMINATION phase.
> Previously, nomination effectively had to go on in perpetuity.  Now, we
> just run the NOMINATION and PREPARE phases concurrently, and allow a
> node to accept a prepared ballot even before it has completed the
> nomination phase.  This makes it possible for a node that has
> externalized a slot to remember only the externalize message and no
> longer have to participate in nomination.
>
> To make this all clearer, we also added a new section with a table
> summarizing the phase transitions.
>
> Thanks for any comments and feedback.
>
> David
>
> _______________________________________________
> Din mailing list
> Din@irtf.org
> https://www.irtf.org/mailman/listinfo/din
>