
From nobody Mon Sep  3 23:14:03 2018
Return-Path: <melinda.shore@nomountain.net>
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 E9AF3130E04 for <din@ietfa.amsl.com>; Mon,  3 Sep 2018 23:14:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nomountain-net.20150623.gappssmtp.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 6Sql4UJqJKBj for <din@ietfa.amsl.com>; Mon,  3 Sep 2018 23:14:00 -0700 (PDT)
Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (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 0A16D130E08 for <din@irtf.org>; Mon,  3 Sep 2018 23:14:00 -0700 (PDT)
Received: by mail-pg1-x535.google.com with SMTP id i190-v6so1123295pgc.6 for <din@irtf.org>; Mon, 03 Sep 2018 23:14:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomountain-net.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=K2izKt4UWuRO+mnepZQ+/jrtYtGsnU3BGdY0LujrhO4=; b=cv9FdHuiQb/zPmgDQ+2Bf4AoNdLRm5QplgKwKuqxGo2Z4RTFH70tmm3dwVOhQN2Sz0 3Up2hV5RPT+Om8heWt0ItI3xVPwSX3BCd3UI0jRBWR+ZqPMXQjv3OXXBH/pdyN7hVhmB x0TkUDLUT4IzcsFlPoqhK79ocYrmFOiwxkQf6+yde7sLVF1UbhRuRHcUOjF97KSGgDfj g/gvRnXTPMX12IKwD4R4RUpQKEHTv9mIJjNGkyTQUxSU/rqViHqJKmPXJYjDPQAv1JAT lwmVTqjHQA6TctEq0mqEMJ357mGa0s0clKS+FWq8beIxmD0dMHdempTC4PWPb5nKFGgY giRQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=K2izKt4UWuRO+mnepZQ+/jrtYtGsnU3BGdY0LujrhO4=; b=erFUxjLqhRj/Cns8meNaXK7P1R4EJ+hSVV5lj6ajdP2Q//ehGLQRGEiPiS+/F2cUmW MR7uRHsBIyT+mv7x2d5JWtNNeRntG8Uee938Gs33llBIgcN0yK68xsqnaqOCgFwME41U 8RGHfUbyc88IsgZwNY/omQFFTBOJgn07iGSjnYtsr/LKhyGhEWthVfB8ozhSPwewP5sE XJVNLYUooSyLkaQF85dBDXZt9KWNCJNfpyNejvszOsPJJDWJnkFXewhxIXirZaz+w4N3 frznnUxjh56l7tFNkYQd3wndZcGORPv9lRUFZRU9k8kEpTdSoMVx+hLpfKjH8I1nhYwu R7ig==
X-Gm-Message-State: APzg51Ci2JFT7ladQ/rXsL5iSUjGX6b6eE4d+XkgGZwCLj7MbYO/H0O4 fAZ4iyA61BVSw6CG3b4bIGwO
X-Google-Smtp-Source: ANB0VdbfBmT9WleaVNyQ3+nOJIC9XY4uOwSYwHSAlx9dPXPvZc94Aqeb2/PrqdxAd9tBZXm5kK46hg==
X-Received: by 2002:a63:d244:: with SMTP id t4-v6mr29112911pgi.335.1536041639658;  Mon, 03 Sep 2018 23:13:59 -0700 (PDT)
Received: from aspen.local (216-67-116-106-radius.dynamic.acsalaska.net. [216.67.116.106]) by smtp.gmail.com with ESMTPSA id c1-v6sm41238597pfg.25.2018.09.03.23.13.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 03 Sep 2018 23:13:59 -0700 (PDT)
To: Nathan Aw <nathan.mk.aw@gmail.com>, din@irtf.org, ietf@dkutscher.net
References: <CA+p-ctbRBxpFdy6jXbjxVBdu0Zm0Ko2p_i6LOWBPgRq4_z9hdA@mail.gmail.com>
From: Melinda Shore <melinda.shore@nomountain.net>
Message-ID: <4611fa28-322f-ed2a-022e-d92afc710467@nomountain.net>
Date: Mon, 3 Sep 2018 22:13:57 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CA+p-ctbRBxpFdy6jXbjxVBdu0Zm0Ko2p_i6LOWBPgRq4_z9hdA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/_eimO5jcuRrMJvb0aArqIHL1rMw>
Subject: Re: [Din] Using Decentralized Identifiers (DIDs) to enable Decentralized Single Sign across different blockchains thereby enabling Interoperability - Nathan Aw from Singapore
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, 04 Sep 2018 06:14:02 -0000

On 9/2/18 6:09 AM, Nathan Aw wrote:
> Is there someone in this mailing list who is keen on sharing inputs into
> this model so that we all could move towards a standard-based
> decentralized identity model/foundation? 

Hi, Nathan -

I think this is clearly in scope for the research group, if
we're chartered, but please note that IRTF research groups
don't produce standards.  However, a number of people have
found that the discussion and work on building agreement
around output from research projects can sometimes translate
into standards work further down the line.

What you're describing sounds orthogonal to the work on
distributed mapping that's been presented at the interim and
then at the most recent RG meeting (in Montreal).  Am I
correct in remembering that you're doing some work with
the blockchain group at RMIT?

I'm also curious on what you see as the tradeoffs with
the sort of hierarchical decentralized identity work being
done at Project LIGHTest.

Anyway, I'd personally be very interested in seeing a draft
or other paper.

Melinda

-- 
Software longa, hardware brevis


From nobody Wed Sep 19 11:17:31 2018
Return-Path: <session-request@ietf.org>
X-Original-To: din@irtf.org
Delivered-To: din@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 42A8F130F59; Wed, 19 Sep 2018 11:17:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: dinrg-chairs@ietf.org, melinda.shore@nomountain.net, din@irtf.org, irtf-chair@irtf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.84.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153738104218.21466.16282415953398270585.idtracker@ietfa.amsl.com>
Date: Wed, 19 Sep 2018 11:17:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/u7oG3Pi-20xbL1rhl_bp668MaHM>
Subject: [Din] dinrg - New Meeting Session Request for IETF 103
X-BeenThere: din@irtf.org
X-Mailman-Version: 2.1.29
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: Wed, 19 Sep 2018 18:17:29 -0000

A new meeting session request has just been submitted by Melinda Shore, a Chair of the dinrg working group.


---------------------------------------------------------
Working Group Name: Decentralized Internet Infrastructure Proposed RG
Area Name: IRTF
Session Requester: Melinda Shore

Number of Sessions: 1
Length of Session(s):  2 Hours
Number of Attendees: 70
Conflicts to Avoid: 
 First Priority: icnrg trans 
 Second Priority: ace tls saag



People who must be present:
  Melinda Shore
  Dirk Kutscher
  Allison Mankin

Resources Requested:

Special Requests:
  Please avoid conflict with the rats BOF (first priority) should it be approved
---------------------------------------------------------


From nobody Thu Sep 20 06:40:37 2018
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 6DF6F130EA3 for <din@ietfa.amsl.com>; Thu, 20 Sep 2018 06:40:36 -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 J2YCWlHLT0_N for <din@ietfa.amsl.com>; Thu, 20 Sep 2018 06:40:35 -0700 (PDT)
Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (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 DA578130DE8 for <din@irtf.org>; Thu, 20 Sep 2018 06:40:34 -0700 (PDT)
Received: by mail-lf1-x12a.google.com with SMTP id z186-v6so8387849lfa.5 for <din@irtf.org>; Thu, 20 Sep 2018 06:40:34 -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=3+RSDfZ+SWuvnlqLovOZYa0SUCnpZ6zT3EU0Efa0FL0=; b=jFzDvyy9QVTTk6mgL5XzGnbGAb0+hxCyNh8P3HY21mwJtoUc/oMutGL8n+bdg4btSm ltqSpls/tlsQLU/osHonVeD0wuixFVVFIfw0aqOrMTCKOb78fCHG01+bvpKvKlQO+ygH XOdKRN777E41B42HvhVmYDsmLmt4gU0onRyY3O/pLxIVbjwUJKbaToeN1blOsb4ec+G/ nVTHTaN0srR/kMMa0gvR15flOxKe1ekFAsC3/+DiN/K2/3++dliYOQxNH5sQQz0JwOS4 fNPsAU37cECdJpI1JxNFijMLND3MMZA5+N4P8FzHqHpP91kffVRiRMM2uphzCgmomDHS Y/Qg==
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=3+RSDfZ+SWuvnlqLovOZYa0SUCnpZ6zT3EU0Efa0FL0=; b=YeK1VHJZyEyfmjkgea2oBRQ81x/kOzRlUXusQ0LT63ds/Bd0YZjOgbfm/2Pp2A/OVL wFr+pZHZdUq/JkRmLIGjpqgnU30M5gC4TuhnKcEkzFzXYUx0LryRh1XnDTt3FgIw309a MKGWHuTi1WkfBKOtSe7BckQp0qyfIRpBT5/kkV6fROH48ILxZ1Px89//ZU0/5IJE8qUd KsW0Vg5eVfqgvqDYNxporWW3sxtTr+pDz+Xq5JZ9bIx1OE5mzW7U6N904tgOLwN6jVVO pwjuyDvVNNCWcV8KffTBkM/Q/fR4vFFoFkkJfFpINmNDOphPEmyMlpn+nkl4UnDkk70r VT/g==
X-Gm-Message-State: APzg51CkY4WN1bWruDT8K/X0TOMmDjUPRwFxFCWei+J+Orcgf16xdwgS y9okyagzEiqzTNOxLqwj6b0WpfvMLWeZddCac7fxptYy
X-Google-Smtp-Source: ANB0VdagJkToa6ruHTnBvUwbFFb0C/mYUlep0e1lWSFH/SrmOASok6wdcKPULCa3Q/45Gr+75QqcT4pyPoOjwWwKVc0=
X-Received: by 2002:a19:1b14:: with SMTP id b20-v6mr12921864lfb.12.1537450832798;  Thu, 20 Sep 2018 06:40:32 -0700 (PDT)
MIME-Version: 1.0
From: Piers Powlesland <pierspowlesland@gmail.com>
Date: Thu, 20 Sep 2018 14:40:21 +0100
Message-ID: <CAFXacXn+SW9qx8gzqL2tC3biEvejYiDtuikDOVQ56LUE-UNTOw@mail.gmail.com>
To: din@irtf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/IPs1I90QGimqzYT4ffnhslPETQg>
Subject: [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:40:37 -0000

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?


From nobody Thu Sep 20 06:44:26 2018
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?


From nobody Fri Sep 21 06:58:39 2018
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


From nobody Fri Sep 21 11:19:22 2018
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 3EE0C130EE1 for <din@ietfa.amsl.com>; Fri, 21 Sep 2018 11:19:20 -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 S-5rJdv_FyqJ for <din@ietfa.amsl.com>; Fri, 21 Sep 2018 11:19:18 -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 4918B130E42 for <din@irtf.org>; Fri, 21 Sep 2018 11:19:18 -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 w8LIJFD6067101;  Fri, 21 Sep 2018 11:19:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=scs.stanford.edu; s=scs; t=1537553955; bh=QNTCFsgth6nBAaWLWwPrR+7RIRDedRxpMcetfkUTmAs=; h=From:To:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version; b=R7/Rx7/JYOTh9cPDe/8+pyDpLTla0FsHiUzMIwo74XoN7P566nT1R/aHoKxOSG6i1 PYUjtOXGygTvGng9eaGBChB8aXdzNrOvU9kUq7ZUaSVuLDhWntR+UUPqV05xy4l2wn KD2H04MxFzZnQRpU5HX4S/ArjAqet5yzqVV8PdzU=
Received: (from dm@localhost) by market.scs.stanford.edu (8.16.0.21/8.16.0.21/Submit) id w8LIJFfi093020; Fri, 21 Sep 2018 11:19:15 -0700 (PDT)
From: David Mazieres <dm-list-ietf-ilc@scs.stanford.edu>
To: Piers Powlesland <pierspowlesland@gmail.com>, din@irtf.org
In-Reply-To: <CAFXacXkriN-4OukQw43msZ74VZ9tecNAnPbC8sukmizAHOaxew@mail.gmail.com>
References: <CAFXacXkriN-4OukQw43msZ74VZ9tecNAnPbC8sukmizAHOaxew@mail.gmail.com>
Reply-To: David Mazieres expires 2018-12-20 PST <mazieres-tsedsc249e7i52hwi8j75gexwe@temporary-address.scs.stanford.edu>
Date: Fri, 21 Sep 2018 11:19:15 -0700
Message-ID: <878t3upvbw.fsf@ta.scs.stanford.edu>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/9t2mG1wKQLHIskI88IQoyWdlj5Y>
Subject: Re: [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 18:19:21 -0000

Piers Powlesland <pierspowlesland@gmail.com> writes:

> 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?

If you increase the ballot counter, this messes up the timing.  SCP
depends on the fact that eventually all intact nodes will sit at the
same counter for sufficiently long to exchange a bunch of messages.
That in turn depends on starting a timer only when a quorum hits a
particular counter, and short-circuiting the timer and immediately
bumping the counter if you fall behind a blocking set.  If you add other
criteria for bumping the counter, you no longer have this property.
Also, the timeout lengthens with each counter, so you don't want to run
it up gratuitously.

> 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?

It's new, because of the tweaks we needed to be able to end the
nomination protocol.  The whitepaper version assumed that nomination
continued in the background in perpetuity, which is not practical.  In
the whitepaper version, if you come online after a week of being off and
only have access to externalize messages, then even a v-blocking set of
externalize messages is not actionable if you are still stuck in the
balloting phase (you can't vote to confirm the highest confirmed
prepared ballot).

In general, where there are conflicts, the internet draft takes
precedence over the whitepaper.  We are actively working on the draft
and getting good feedback in response to implementation efforts.  Once
the draft stabilizes, we will have to go back and produce a revised
whitepaper.  Nothing we are doing should invalidate any of the proofs,
but we'll still need to update things.

David


From nobody Thu Sep 27 01:40:12 2018
Return-Path: <ivan@w3.org>
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 A7EE3130E6B for <din@ietfa.amsl.com>; Thu, 27 Sep 2018 01:40:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 PWrb53R_XaIf for <din@ietfa.amsl.com>; Thu, 27 Sep 2018 01:40:09 -0700 (PDT)
Received: from isaac.sophia.w3.org (isaac.sophia.w3.org [193.51.208.85]) (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 CC9AA130E13 for <din@irtf.org>; Thu, 27 Sep 2018 01:40:08 -0700 (PDT)
Received: from ax213-3-82-234-30-238.fbx.proxad.net ([82.234.30.238] helo=[192.168.0.8]) by isaac.sophia.w3.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <ivan@w3.org>) id 1g5Rq9-0005Bg-Iu; Thu, 27 Sep 2018 08:40:05 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_B2D63557-1024-43D6-B91F-F8DBA8A6ADF6"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Ivan Herman <ivan@w3.org>
In-Reply-To: <CA+p-ctZ4GqGML0X0=3NCptzcxt-yKOFeE1XLJdDuvjDvZF+3pw@mail.gmail.com>
Date: Thu, 27 Sep 2018 10:40:04 +0200
Cc: din@irtf.org, W3C Publishing Working Group <public-publ-wg@w3.org>
X-Mao-Original-Outgoing-Id: 559730404.572401-45cee8f513163e898fe9b04bc19431cf
Message-Id: <B3AF3C22-C416-473B-B85A-D87B2C808112@w3.org>
References: <CA+p-ctZdDocdGpN4U44KyvEXWEeDgxiZypR26fBh4x08e4N14Q@mail.gmail.com> <CA+p-ctZ4GqGML0X0=3NCptzcxt-yKOFeE1XLJdDuvjDvZF+3pw@mail.gmail.com>
To: Nathan Aw <nathan.mk.aw@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/2uoN4XbhR8Gg4kYWTNx3xrkrDVc>
Subject: Re: [Din] Exploring possible synergies between W3C verifiable claims working group and DIN IETF
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, 27 Sep 2018 08:40:11 -0000

--Apple-Mail=_B2D63557-1024-43D6-B91F-F8DBA8A6ADF6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Nathan,

the address you used is for the Publishing Working Group, whose members =
do not necessarily have an expertise in this area. I will forward this =
mail to my colleague at W3C who should know more about this=E2=80=A6

Sincerely

Ivan Herman

> On 27 Sep 2018, at 02:42, Nathan Aw <nathan.mk.aw@gmail.com =
<mailto:nathan.mk.aw@gmail.com>> wrote:
>=20
> Hi all,
>=20
> Would like to explore if possible synergies could be realized between =
W3C verifiable claims working group and DIN IETF?
>=20
> Thank you.
>=20
> Nathan Aw
>=20
> On Thu, 27 Sep 2018, 08:42 Nathan Aw, <nathan.mk.aw@gmail.com =
<mailto:nathan.mk.aw@gmail.com>> wrote:
> Hi all,
>=20
> Would like to explore if possible synergies could be realized between =
W3C verifiable claims working group and DIN IETF?
>=20
> Thank you.
>=20
> Nathan Aw


----
Ivan Herman, W3C=20
Publishing@W3C Technical Lead
Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
mobile: +31-641044153
ORCID ID: https://orcid.org/0000-0003-0782-2704 =
<https://orcid.org/0000-0003-0782-2704>


--Apple-Mail=_B2D63557-1024-43D6-B91F-F8DBA8A6ADF6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Nathan,<div class=3D""><br class=3D""></div><div class=3D"">the=
 address you used is for the Publishing Working Group, whose members do =
not necessarily have an expertise in this area. I will forward this mail =
to my colleague at W3C who should know more about this=E2=80=A6</div><div =
class=3D""><br class=3D""></div><div class=3D"">Sincerely</div><div =
class=3D""><br class=3D""></div><div class=3D"">Ivan Herman<br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 27 Sep 2018, at 02:42, Nathan Aw &lt;<a =
href=3D"mailto:nathan.mk.aw@gmail.com" =
class=3D"">nathan.mk.aw@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"auto" =
class=3D""><div class=3D""><span style=3D"font-family:sans-serif" =
class=3D"">Hi all,</span><div dir=3D"auto" =
style=3D"font-family:sans-serif" class=3D""><br class=3D""></div><div =
dir=3D"auto" style=3D"font-family:sans-serif" class=3D"">Would like to =
explore if possible synergies could be realized between W3C verifiable =
claims working group and DIN IETF?</div><div dir=3D"auto" =
style=3D"font-family:sans-serif" class=3D""><br class=3D""></div><div =
dir=3D"auto" style=3D"font-family:sans-serif" class=3D"">Thank =
you.</div><br class=3D""><div data-smartmail=3D"gmail_signature" =
class=3D"">Nathan Aw</div><br class=3D""><div class=3D"gmail_quote"><div =
dir=3D"ltr" class=3D"">On Thu, 27 Sep 2018, 08:42 Nathan Aw, &lt;<a =
href=3D"mailto:nathan.mk.aw@gmail.com" =
class=3D"">nathan.mk.aw@gmail.com</a>&gt; wrote:<br =
class=3D""></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto" =
class=3D"">Hi all,<div dir=3D"auto" class=3D""><br class=3D""></div><div =
dir=3D"auto" class=3D"">Would like to explore if possible synergies =
could be realized between W3C verifiable claims working group and DIN =
IETF?</div><div dir=3D"auto" class=3D""><br class=3D""></div><div =
dir=3D"auto" class=3D"">Thank you.<br class=3D""><br class=3D""><div =
data-smartmail=3D"gmail_signature" dir=3D"auto" class=3D"">Nathan =
Aw</div></div></div>
</blockquote></div></div></div>
</div></blockquote></div><br class=3D""><div class=3D"">
<div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div class=3D""><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D"">----<br class=3D"">Ivan Herman, W3C&nbsp;<br =
class=3D"">Publishing@W3C Technical Lead</div><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Home: <a href=3D"http://www.w3.org/People/Ivan/" =
class=3D"">http://www.w3.org/People/Ivan/</a><br class=3D"">mobile: =
+31-641044153</div><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">ORCID=
 ID:&nbsp;<a href=3D"https://orcid.org/0000-0003-0782-2704" =
class=3D"">https://orcid.org/0000-0003-0782-2704</a><br =
class=3D""></div></div></div>
</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_B2D63557-1024-43D6-B91F-F8DBA8A6ADF6--


From nobody Thu Sep 27 06:55:00 2018
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 2B7B7130E8F for <din@ietfa.amsl.com>; Thu, 27 Sep 2018 06:54:58 -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 AtkR6nCm-dDz for <din@ietfa.amsl.com>; Thu, 27 Sep 2018 06:54:56 -0700 (PDT)
Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::22a]) (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 86301130E23 for <din@irtf.org>; Thu, 27 Sep 2018 06:54:56 -0700 (PDT)
Received: by mail-lj1-x22a.google.com with SMTP id r83-v6so2495830ljr.7 for <din@irtf.org>; Thu, 27 Sep 2018 06:54:56 -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=+q+6XO9d6pBAZCWnvJcy/iIqaJZyc5SDw0iVlyrUIkU=; b=ruFTx+Niqa6ER2p/JuZAlPqG8dIrkf+5FSP4DutlfWKQQ7unffH6O7o4/V84g8s4Fr SMrvzIgMIXP45+vpejQqJIGsDMPEhkNlXKa17qnqAkYinJGwx+4SMw2FL+hgDuAB1kmh NYaGP2b8rt1F2fYS+bfILv9Cv0/uilUgFHBvHEiT3hUvRdUguDuB/RHx3+syiaWKpDTs s8cKW5u6gQlwNVsGP1dp2VrPDz4bctiE2v0WNGa5PIT7VMcVRluqN4niKikmInTKTgKt YkxSjJwWXmqMG5xEgB+XqCSI2DZM4Kdh6m7iukShWzHlKA14iVM6iww/G5lhlhjOqQFs KH1g==
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=+q+6XO9d6pBAZCWnvJcy/iIqaJZyc5SDw0iVlyrUIkU=; b=Jm+uaScNfboyp7UZYtE0Mwg0sFL9UrTfaFQXLHJKo/lU9OoNqgzxeLnyuJxV1w6NHt MkaQl9PJmqCNQNzZuBZcqzPz9AFLu5YES0NxlhzCx0m3TI/aKkE0B4nMhGuHGRKhym0m wwjGU3BvM3Xqfb+Su7qX5oRrMH04ENP2GytOYS/cwpMGVWu5RsQqaR6XLC0Bo/w1LLR/ qY36LAeaYWScLiCehWvfZZRvSVeBKZUIgqnMF6P0E5O9NsY2NoH7CJgQG9WwPJPlUYrN 8gek3cgypadQ5rU87o3kf6k5Q6VwyzIkqPLwW5my3GwvC5EBqpyyfuWhqHrjxjsD7iv+ +6Rw==
X-Gm-Message-State: ABuFfojpQlPKNgR8ydLy9EE1S5xW+lQxot6y1i5DPMGOt6F6Xty7rxUG ZU+hMcsQkdVi4UqI4NfEDCq+QR4y0GjAEMK+8dwAAznxvKI=
X-Google-Smtp-Source: ACcGV615TgWrYOitntDdlir4QIhvgI3BGayDM7QNg0edRfdZuq1DU5vHtr0RBiZxa9ris/tMazhbefoq30rL43T0980=
X-Received: by 2002:a2e:5586:: with SMTP id g6-v6mr2954872lje.75.1538056494127;  Thu, 27 Sep 2018 06:54:54 -0700 (PDT)
MIME-Version: 1.0
From: Piers Powlesland <pierspowlesland@gmail.com>
Date: Thu, 27 Sep 2018 14:54:43 +0100
Message-ID: <CAFXacXk5KeMbSWfgUvi7LL+Ca64HD30vwA-iAi_QcCZmtDWqvw@mail.gmail.com>
To: din@irtf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/c90B9FIq1Ut20RppgBAXjnqkfAs>
Subject: [Din] draft-mazieres-dinrg-scp-04 (page 16) setting preparedPrime
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, 27 Sep 2018 13:54:58 -0000

In the section "preparedPrime", I'm wondering if the "highest accepted prepared
ballot", is referring to a concrete ballot that has been seen or a ballot
within the conceptual space of ballots?

For example, if we consider a system with 3 possible values x, y and z and
x<y<z. If you imagine we have p == (4,z) and we see blocking threshold for
(3,x) and so set p' == (3,x) if you consider the ballots that have been
accepted aborted through p and p', you can see that all the ballots required to
be aborted in order for (3,y) to be considered prepared have been aborted. Do
we now set p' to (3,y) since (3,y) is greater than (3,x) ?


From nobody Fri Sep 28 18:46:13 2018
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 10115130DEB for <din@ietfa.amsl.com>; Fri, 28 Sep 2018 18:46:12 -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 5w1Yexl3KF3o for <din@ietfa.amsl.com>; Fri, 28 Sep 2018 18:46:10 -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 91F28130DD7 for <din@irtf.org>; Fri, 28 Sep 2018 18:46:10 -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 w8T1k7wr058495;  Fri, 28 Sep 2018 18:46:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=scs.stanford.edu; s=scs; t=1538185567; bh=xnV5dpm/dDlzymH66+CZRA/cnh0ttRLEX5UQP/ar0sY=; h=From:To:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version; b=DNiY2FsQ5/caTzWjs6oC3ADwklNvIz3+qlPlqGC2BAi88XA643DZXSRWNW8/RJETs 37RllQnSTYwgerJW0Y786cmkeMkFk9vluJmUflTwj2nn5oD/om7ZTqMs0GrN+J7w5j 21kp1AxIDbaG2h0jSLSuwdhs5ZYOBmR01ecHhjHU=
Received: (from dm@localhost) by market.scs.stanford.edu (8.16.0.21/8.16.0.21/Submit) id w8T1k7uJ064928; Fri, 28 Sep 2018 18:46:07 -0700 (PDT)
From: David Mazieres <dm-list-ietf-ilc@scs.stanford.edu>
To: Piers Powlesland <pierspowlesland@gmail.com>, din@irtf.org
In-Reply-To: <CAFXacXk5KeMbSWfgUvi7LL+Ca64HD30vwA-iAi_QcCZmtDWqvw@mail.gmail.com>
References: <CAFXacXk5KeMbSWfgUvi7LL+Ca64HD30vwA-iAi_QcCZmtDWqvw@mail.gmail.com>
Reply-To: David Mazieres expires 2018-12-27 PST <mazieres-fev3hh3q6e9d3mijfy7x2ybtk6@temporary-address.scs.stanford.edu>
Date: Fri, 28 Sep 2018 18:46:06 -0700
Message-ID: <87k1n53wkh.fsf@ta.scs.stanford.edu>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/Ss1pt1g798sv4MTu3K2Cb2X2Ve8>
Subject: Re: [Din] draft-mazieres-dinrg-scp-04 (page 16) setting preparedPrime
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: Sat, 29 Sep 2018 01:46:12 -0000

Piers Powlesland <pierspowlesland@gmail.com> writes:

> In the section "preparedPrime", I'm wondering if the "highest accepted
> prepared ballot", is referring to a concrete ballot that has been seen
> or a ballot within the conceptual space of ballots?
>
> For example, if we consider a system with 3 possible values x, y and z and
> x<y<z. If you imagine we have p == (4,z) and we see blocking threshold for
> (3,x) and so set p' == (3,x) if you consider the ballots that have been
> accepted aborted through p and p', you can see that all the ballots required to
> be aborted in order for (3,y) to be considered prepared have been aborted. Do
> we now set p' to (3,y) since (3,y) is greater than (3,x) ?

Thanks for raising the point.  The short answer is that it doesn't
matter--the protocol works either way.

The slightly longer answer, which someone recently pointed out to me, is
that because of this fact, it is actually wasteful to send around the
value of preparedPrime, rather than just the counter.  So the next
revision of the draft will probably address this question...

David

