[Din] draft-mazieres-dinrg-scp-04 peer priority algorithm
Piers Powlesland <pierspowlesland@gmail.com> Tue, 07 August 2018 16:58 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 92A55130F25 for <din@ietfa.amsl.com>; Tue, 7 Aug 2018 09:58:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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 VdM4BU3VnSXE for <din@ietfa.amsl.com>; Tue, 7 Aug 2018 09:58:23 -0700 (PDT)
Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) (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 5A11812777C for <din@irtf.org>; Tue, 7 Aug 2018 09:58:23 -0700 (PDT)
Received: by mail-lj1-x234.google.com with SMTP id y17-v6so13985268ljy.8 for <din@irtf.org>; Tue, 07 Aug 2018 09:58:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=FIPX/DTJQvR/UEcwjK9SCYceEMSVaqfYL9nd7x/1hLw=; b=ksU11QAOE9PE7Kg79ba5QuOrF/WHo8OixDJhBmMVKMUQIfxy3bevvU1UD+nKSKk02F 1yajSFsAGiTWfPYuCoJWLTpugWYt9LlOoRSucBpVEQdtMcetCpVVcEY+2zxFolEJYx6q 4Mr5ch/41p0FQnf7AndwczNjGCU4cpYuj5eb34tAK791WQaVv89yoQdKG1QKNbBALVde FpU2Fq5WQgEeqS9lI82jfm57A0wK41VuwAxQ3eGvKr/rRqwpQCuccpUf/q7KlZYDGlnl iYP25TfdSi7sVbs2d1hjGZcHfbqR8E27IMQCq4nUkU4LW+MEQRrflis+J60VPaCstfB2 Bk7A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=FIPX/DTJQvR/UEcwjK9SCYceEMSVaqfYL9nd7x/1hLw=; b=e19Nx4NZHQGV46tAjVFv7E7CTzsUuh54QHcCWNBxYhd/tRESjM2w00C0ySqHvAa9If wJT7z8JpiXkvcGX4uH4VA+QbWiPlXEbkVw+dmsro4AZr7LRrHgUiIsGr8o+o7mDsr+Co dl4igS9N7exyVuzAJZBG+J0HH/7ISt3ICjuMeN2ThWDFq6SAYwXVs7N1o/yfkuslXDAL pdfWkSUSRAoppCpanoRe9CPfByMaSzKGAHtTwU2oEnmQeMWdZvEEFz+M3AJ58Wu/cVnD G9sNfwKRAHkoXymXU8LnUhxQ4Q+6KMbeAPvcj2k1/ckkrFq4NCTTmXpOkb/vYtj2IEeU zFsw==
X-Gm-Message-State: AOUpUlFUjuZ3DtfjuJkz6WZ+glnyX/4xOU1KTNLJ5fPthzs0854Cn20S 9vZRToTqEXtuCYWQwjsdnlbt+RCdlNwbNQgBrF6v2AOwhXQ=
X-Google-Smtp-Source: AAOMgpf8mdrqIQaRnCAOwTvGHVLXLjCiv180DZiiCKpV9yRX1mrka4EKpbquFgLsqrxE6V/TTa66UX1p2Jz0iruAmng=
X-Received: by 2002:a2e:59d1:: with SMTP id g78-v6mr17221466ljf.79.1533661101204; Tue, 07 Aug 2018 09:58:21 -0700 (PDT)
MIME-Version: 1.0
From: Piers Powlesland <pierspowlesland@gmail.com>
Date: Tue, 07 Aug 2018 17:58:10 +0100
Message-ID: <CAFXacXkx+y5mqwatwJoQib=q3W+6u02QHDLqtS66P4wGXqwCEQ@mail.gmail.com>
To: din@irtf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/KvdK6VSD-1vUZe2Y-2Y14yB80fc>
Subject: [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: Tue, 07 Aug 2018 16:58:26 -0000
Hello, On page 10 of https://tools.ietf.org/pdf/draft-mazieres-dinrg-scp-04.pdf an algorithm is described to determine the priority of peers for a given node. Peers are selected from a set "neighbours" based on a priority calculated for each peer. The "neighbours" set is constructed by taking the set of peers that constitute the quorum slices for a node and then filtering them to remove any peer for which sha-256(slot_number || 1 || nomination_round || peer_id ) < 2^256 * weight(peer_id) Where "||" means concatenation of serialised values and "weight(peer_id)" is the fraction of slices containing peer_id. 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? Also what is the motivation for creating the "neighbours" set as opposed to simply selecting a peer from all peers based on their priority weighted by their weight?
- [Din] draft-mazieres-dinrg-scp-04 peer priority a… Piers Powlesland
- Re: [Din] draft-mazieres-dinrg-scp-04 peer priori… David Mazieres
- Re: [Din] draft-mazieres-dinrg-scp-04 peer priori… David Mazieres
- Re: [Din] draft-mazieres-dinrg-scp-04 peer priori… Piers Powlesland