Re: [Din] draft-mazieres-dinrg-scp-04 ballot field of SCPCommit

Piers Powlesland <pierspowlesland@gmail.com> Thu, 20 September 2018 13:44 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 03A36130DCC for <din@ietfa.amsl.com>; Thu, 20 Sep 2018 06:44:25 -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 5vFUpBUlTjKL for <din@ietfa.amsl.com>; Thu, 20 Sep 2018 06:44:23 -0700 (PDT)
Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (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 0AF84129619 for <din@irtf.org>; Thu, 20 Sep 2018 06:44:22 -0700 (PDT)
Received: by mail-lj1-x22e.google.com with SMTP id f1-v6so8416074ljc.9 for <din@irtf.org>; Thu, 20 Sep 2018 06:44:22 -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; bh=dua2zNShe8IihfZ0uUJmc/OHD521gQ4SOjz2wVifWYM=; b=ZYcNU+PF1yq6p8a1S3k63psuMim/teFVcmlGC+BT4++v5l+OBYordrPzZrOPxqgQzB iMR57LNl8NsekAxuEH5G3eMsAB6v4kl7jbNkxaXdqi6XdBgEnGYPxOX8uwC8or9dT5q7 a5n65Cm7eMDXaZW0VSelc3z+HgfGJzElxcrxprs4jgtPqjxmqruql5fNYVUhkz3FS+Cw xopyoWYqmZtfrwI8Lo2CqW+joixRAH+H2WEUMtWbZanKVVz6ufrtfLJR1UtzrD0ODOwo SX5trHSxr0jSYwB9Mf802petJLrIktbhZKcJUTYShoIWL5T26t0RwcJCXCEBo94ye80/ OM0A==
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; bh=dua2zNShe8IihfZ0uUJmc/OHD521gQ4SOjz2wVifWYM=; b=N9zG/gbE0zlM/Z+P/6FBLt3OQjYIuZeak1Mv8JP86PmLOH/+Ld0jTlE6aJa1IknGcM zqJbI1FNpmV46ALvTBIJNpeB+CMs4Jl4s7+qPE+saagL6SGZiNDiLfLDdNmfG/P+BfLr GzLhQstqL8PBRR6jB+zyOyILDSAWlTViIl4J9R8x1gwFGcQFc1HLtZoJORbzlIGuvRp7 d52DYuyVylMS8eVyk5/UKUgCCTbJ0/PrKg1cXsHcwwrHbPJpMxNWmQlbtVwSx3uLDHM8 5IudyfhYGupyO91nlxTC49NtXBiOXLkFz1TGZLO+Fxbrlc7sHnj1ni/G4+dqyM/n1DOX S9LA==
X-Gm-Message-State: APzg51AaQiae+BRM1/FTFixbBmgf5lxlKmczl7e9srD0LmGTt2AH3Q40 ouWTtIXSvJUnNSR/D4G4fV/6Br4LuJuWBiOLJ5Q6G75e
X-Google-Smtp-Source: ANB0VdbSl5Li9t5QscjRzcHhndvkzg6pWH8QQZYzhNFxewfSGR/RF7+Qc+KGJFakLuE0ZRhnwDfLJGIEvLQExuvpU30=
X-Received: by 2002:a2e:9941:: with SMTP id r1-v6mr8526866ljj.53.1537451060691; Thu, 20 Sep 2018 06:44:20 -0700 (PDT)
MIME-Version: 1.0
References: <CAFXacXn+SW9qx8gzqL2tC3biEvejYiDtuikDOVQ56LUE-UNTOw@mail.gmail.com>
In-Reply-To: <CAFXacXn+SW9qx8gzqL2tC3biEvejYiDtuikDOVQ56LUE-UNTOw@mail.gmail.com>
From: Piers Powlesland <pierspowlesland@gmail.com>
Date: Thu, 20 Sep 2018 14:44:09 +0100
Message-ID: <CAFXacXk+TduXGGpCXnGT+EMyC1EjP1J5Ycp+-EtvGxoZogs+Aw@mail.gmail.com>
To: din@irtf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/ZWrmYl1SCqTSrLsvkG0ZKcthOSM>
Subject: Re: [Din] draft-mazieres-dinrg-scp-04 ballot field of SCPCommit
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: Thu, 20 Sep 2018 13:44:25 -0000

Apologies, reading on I found the reason for including a ballot.
On Thu, Sep 20, 2018 at 2:40 PM Piers Powlesland
<pierspowlesland@gmail.com> wrote:
>
> Looking at the IETF document section 3.7 I don't see the SCPCommit
> message ballot.counter being referenced anywhere and wondered what the
> reason was for including a ballot there instead of just the value?