[Din] draft-mazieres-dinrg-scp-04 page 15 settting prepared

Piers Powlesland <pierspowlesland@gmail.com> Fri, 21 September 2018 13: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 D038D130DC0 for <din@ietfa.amsl.com>; Fri, 21 Sep 2018 06:58:37 -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 P72kHBtvEyqf for <din@ietfa.amsl.com>; Fri, 21 Sep 2018 06:58:36 -0700 (PDT)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::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 38B4512F1A6 for <din@irtf.org>; Fri, 21 Sep 2018 06:58:36 -0700 (PDT)
Received: by mail-lj1-x233.google.com with SMTP id s12-v6so11745949ljj.0 for <din@irtf.org>; Fri, 21 Sep 2018 06:58:36 -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=6UI4RffJqoyYuGiDB8UsNWNLEK9MC0HimKEskuGQPt4=; b=szNqB3Za78BBsXC1OJlJ/siksrBGIVoUOXozRIpW1IMzPuQ2qD4kwjsQ26i3RfUbt/ sBAQezcag86NTzZ1USF51kxqYL5Bcv1gqeXmltpmwHY0B7yRnSmOu6O00NV/Y7ZmnO1H yTR9EUtgKNZ84EK51yTMjK1QHStJZPu2epxCdG792G1XaH5k5RZDz23zIoM2Shw0LE09 S66t+PBTD3HfiQ+Kt9kPqyHkwVUhTBbGqOnATuctlxHBP4NJyg+4cZjwtd1+aXkIf3YP 4Z/JTqK4Ml8UzDEUBnKlRCBdgsrKe551KNDu8JdnYXRA0LLpbzdIWFDDHHio2wLgr3dC ym7A==
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=6UI4RffJqoyYuGiDB8UsNWNLEK9MC0HimKEskuGQPt4=; b=ArDLd92YN23voMfYwEXv3CVwywbNDVoRttGy4dnhrc840PjE28axAJSqCmEpm3pyF1 NGz/kEc4YULQasRtzpH/UTxHg2oMqG/2UDtLFS8s3ocdDJHej7WPjgwAEWJ6nSkiqnmd 8Znk1cUP37XVvREBrd97g3YWl0qr0qbRiyMEFIv2qNU2vZ1yqPLeatNdpuEM6ChR9hF6 5zQjI1NKHPXHtp/RjHhg9F4LHsobg2nR0tBUzViaGUpEJ/EEJP8SkEFnWq6NeA+PcbI4 o+pKjYBEeAJbjkBHK5GJs/spyG+SCEt7q9pPMMnInhCA+PIzaDLXR/t7SuiU+OVP6NnR 06+Q==
X-Gm-Message-State: APzg51AmAg7VJqfAS2vtMUS+Xe7dS5QcYneYBNvIp385Z56IDb+Wkzhe lSxDiWNF4Zi7y8bDP5Tcu8jR1m+69YhnFzJI/JtR+9vsfxU=
X-Google-Smtp-Source: ACcGV626PAfR7vmt8OQD7efPuhF/TCppZJbSLHTM4CRA2uJ8NftIJPUwWNZAoQ5ucSgshnjZVPegH0dM03Ki93O3874=
X-Received: by 2002:a2e:2c0d:: with SMTP id s13-v6mr1961897ljs.106.1537538313992; Fri, 21 Sep 2018 06:58:33 -0700 (PDT)
MIME-Version: 1.0
From: Piers Powlesland <pierspowlesland@gmail.com>
Date: Fri, 21 Sep 2018 14:58:22 +0100
Message-ID: <CAFXacXkriN-4OukQw43msZ74VZ9tecNAnPbC8sukmizAHOaxew@mail.gmail.com>
To: din@irtf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/M81A7grM45O9c55G0e-Ykm5xBzc>
Subject: [Din] draft-mazieres-dinrg-scp-04 page 15 settting prepared
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: Fri, 21 Sep 2018 13:58:38 -0000

Hi,

The segment describing setting "prepared" on page 15 is as follows.

>The highest accepted prepared ballot not exceeding the "ballot"
>field, or NULL if no ballot has been accepted prepared.  Recall
>that ballots with equal counters are totally ordered by the value.
>Hence, if "ballot = <n, x>" and the highest prepared ballot is
>"<n, y>" where "x < y", then the "prepared" field in sent messages
>must be set to "<n-1, y>" instead of "<n, y>", as the latter would
>exceed "ballot".

I am wondering why the prepared counter must be set so that it does
not exceed ballot as opposed to increasing the ballot counter so that
ballot >= prepared?

Also I can't see such a condition in the original SCP whitepaper, and
I'm wondering if I have missed it or if this is a new addition to the
balloting protocol?

Thanks,

Piers