Re: [Din] New SCP draft
David Mazieres <dm-list-ietf-ilc@scs.stanford.edu> Thu, 14 June 2018 15:12 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 DD69A130E46 for <din@ietfa.amsl.com>; Thu, 14 Jun 2018 08:12:36 -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 iYUqS8w7JTap for <din@ietfa.amsl.com>; Thu, 14 Jun 2018 08:12:35 -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 84141130E29 for <din@irtf.org>; Thu, 14 Jun 2018 08:12:35 -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 w5EFCYq9077637; Thu, 14 Jun 2018 08:12:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=scs.stanford.edu; s=scs; t=1528989154; bh=yNywyURTaHWSm9/PmvrCKfdkgBvFc8Zy8cgjo1Boftw=; h=From:To:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version; b=btT+CCgPbVLZsxrl7hkQXKEbPUUEnFvzGO+qVfKw9vPQY/nmIRUe4eObniBrSJaa9 Gz9EceqnMenHamwR3/XaGJoBnIB8fFd8oObQ0PpyKMdhgt3sT7NCSqoUbmqjTj/rFQ juOCziqENIWvF0RFFMF2cekT9oHq0RS+ncStf8wg=
Received: (from dm@localhost) by market.scs.stanford.edu (8.16.0.21/8.16.0.21/Submit) id w5EFCXnO052840; Thu, 14 Jun 2018 08:12:33 -0700 (PDT)
From: David Mazieres <dm-list-ietf-ilc@scs.stanford.edu>
To: Piers Powlesland <pierspowlesland@gmail.com>
Cc: din@irtf.org
In-Reply-To: <CAFXacXk7acKpvA5RvLJuxgWfCCD3hOAxjwaD56Td-uzJ9cnB+w@mail.gmail.com>
References: <87vaambccw.fsf@ta.scs.stanford.edu> <CAFXacXk7acKpvA5RvLJuxgWfCCD3hOAxjwaD56Td-uzJ9cnB+w@mail.gmail.com>
Reply-To: David Mazieres expires 2018-09-12 PDT <mazieres-7igfdpy63nsk4nif4fkwyhqr6s@temporary-address.scs.stanford.edu>
Date: Thu, 14 Jun 2018 08:12:33 -0700
Message-ID: <87h8m5e71a.fsf@ta.scs.stanford.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/rnCv0qWlFNVr00ZzECVunhx5FeM>
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 15:12:37 -0000
Piers Powlesland <pierspowlesland@gmail.com> writes: > 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. That's a good idea. I think maybe just SCPSlices is clear enough and shorter. > 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.' Since the messages are broadcast, technically the sending node may hear its votes echoed back, but I agree this could provide the wrong intuition. Similarly "mirroring" might convey the wrong thing. Maybe "relaying" or "repeating" or "following"? Any other ideas? David
- Re: [Din] New SCP draft David Mazieres
- Re: [Din] New SCP draft Piers Powlesland
- [Din] New SCP draft David Mazieres
- Re: [Din] New SCP draft Piers Powlesland