Re: [Din] draft-mazieres-dinrg-scp-04 peer priority algorithm

Piers Powlesland <pierspowlesland@gmail.com> Fri, 10 August 2018 17:14 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 AA175130E5C for <din@ietfa.amsl.com>; Fri, 10 Aug 2018 10:14:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 fViMXZ1U_vQI for <din@ietfa.amsl.com>; Fri, 10 Aug 2018 10:14:38 -0700 (PDT)
Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) (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 E57D3130EA3 for <din@irtf.org>; Fri, 10 Aug 2018 10:14:37 -0700 (PDT)
Received: by mail-lf1-x12c.google.com with SMTP id u202-v6so7069256lff.9 for <din@irtf.org>; Fri, 10 Aug 2018 10:14:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LbcHGbs7MOfj/+qMcaFsD0OZTY6Ya9A5v49ZRz8gZ/I=; b=gWmRPPxWAHwdZNH0F145rLh2XydXtsOOwXsHQzxUXRkzXVC+jwN4gnfD3V+JgGFY7i jRwQkG/59fDcsV809Kpu/W3KJHimcSsBSYnr8DX/+4JE6BjxH5P3HSvktuEFuLbNiO4e BOmnsDvhEUVxHtwTYw82/doIwmACkJ7Ju2QUmKYAGWvh1F8B5Engnf5DIaXf4ToQbhy1 Jx484m+6o89BO6w9LuuZxFPja1RUL7Uwe6FQIM+Q6jrvbFcHtS7sNoeOSetCOdJ49ne0 xH6gNP4aWbmtWbiGium4/kRBcuYQYfAanDH6wTxOgtqGaQzNYvzPVy1RQrNncs9LSLqm VZYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LbcHGbs7MOfj/+qMcaFsD0OZTY6Ya9A5v49ZRz8gZ/I=; b=ch+rcIsJ5UwBcCKzqvfCMlcGWIBTmCmrOTcpbqrAVKLhS9Gxvjq7XlPJGAENSB9iMc zpNaeAYKMVSagBgOkSIOFFnrXlWADs4XhfSNTj+wM/uu6VD8eoroGt3Q00EY+BTRYRg0 O+5szsB9dLMABCX9U4BMG4mcxSfQtbRFzFNN0MeFoOvqUCn18k/Ecpci1CKxksH9uDSz AzsS3iG76acXQfChLFIyQhEvVfwyxXnXSpMBIBW8+SJ3jT0EJ0lvRFKqa0Y70Fxtpkd8 fLzF1dEXCRPaJtnPkm8whtG/MQrSOfG6vT+Y9Ou/iWeK3+jrZ8f98mdcg+udz0sP5Z+w Wq4Q==
X-Gm-Message-State: AOUpUlF6ZgpvXlluE9ajFgf3LP/km71JjsEU2y2dmmOPyk14NBuIJUnq y2pgIv4Df/euUd/AfFC8QiGDrcUc5oxdIUIgAmfzmoDA
X-Google-Smtp-Source: AA+uWPzEwSCNJK03Sen/rk1CE3SEdl3fAvqtBRe3bbfI9VWcrPwglAsybYJoGAUZxgxUo7yZZmTAG+UcdUeARPbThfg=
X-Received: by 2002:a19:5d54:: with SMTP id p20-v6mr4858746lfj.143.1533921275885; Fri, 10 Aug 2018 10:14:35 -0700 (PDT)
MIME-Version: 1.0
References: <CAFXacXkx+y5mqwatwJoQib=q3W+6u02QHDLqtS66P4wGXqwCEQ@mail.gmail.com> <8736vquer0.fsf@ta.scs.stanford.edu> <87zhxyszwn.fsf@ta.scs.stanford.edu>
In-Reply-To: <87zhxyszwn.fsf@ta.scs.stanford.edu>
From: Piers Powlesland <pierspowlesland@gmail.com>
Date: Fri, 10 Aug 2018 18:14:24 +0100
Message-ID: <CAFXacXmSOwm2P7AqPTm=oRFm88xjZFS9ce80qnAC988APksg_g@mail.gmail.com>
To: mazieres-w6kdgs48q4kevhhfbq3r54nani@temporary-address.scs.stanford.edu
Cc: din@irtf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/xBm-4EN3OBYXvYUzZD8b79-Uheg>
Subject: Re: [Din] draft-mazieres-dinrg-scp-04 peer priority algorithm
X-BeenThere: din@irtf.org
X-Mailman-Version: 2.1.27
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: Fri, 10 Aug 2018 17:14:41 -0000

Hi David,

The new wording looks good to me.

And thanks for clarifying the 2 stage approach to choosing a preferred
peer, I can see now that my approach would not correctly reflect the
importance nodes as they appear in SCPSlices.
On Tue, Aug 7, 2018 at 9:08 PM David Mazieres
<dm-list-ietf-ilc@scs.stanford.edu> wrote:
>
> David Mazieres <dm-list-ietf-ilc@scs.stanford.edu> writes:
>
> >> As I understand, this filtering could lead to a situation where the
> >> neighbours set is empty, since there is no guarantee that any hash
> >> calculated above will be less than '2^256 * weight(peer_id)'. Is this
> >> intentional?
> >
> > There is a guarantee, because a node must belong to all of its own
> > quorum sets.  So even if a node has no other neighbors, it will still be
> > its own neighbor... which highlights the fact that maybe "neighbor" is a
> > misleading term here?  Or maybe at least suggests we should mention
> > this.
>
> I went to clarify this in the draft and realize it's not clear at all
> because of the way slices are defined.  (You implicitly have to be in a
> quorum, but it never says you are in every slice.)  So I propose the
> following wording on neighbors:
>
>    o  Define the set of nodes "neighbors(n)" as the set of nodes v for
>       which "Gi(1 || n || v) < 2^{256} * weight(v)", where "1" and "n"
>       are both 32-bit XDR "int" values.  Note that a node is always its
>       own neighbor because conceptually a node belongs to all of its own
>       quorum slices.
>
> David