Re: [Trans] Add get_entries_max_limit attribute to get-sth request

Paul Wouters <paul@nohats.ca> Fri, 22 February 2019 15:12 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A765130DC4 for <trans@ietfa.amsl.com>; Fri, 22 Feb 2019 07:12:28 -0800 (PST)
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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 NLdKX_OEPGar for <trans@ietfa.amsl.com>; Fri, 22 Feb 2019 07:12:26 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 2DCCC130DC2 for <trans@ietf.org>; Fri, 22 Feb 2019 07:12:26 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 445ZZb6gQSzJhv; Fri, 22 Feb 2019 16:12:23 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1550848343; bh=MV2q4gO2sYXADi9iI1XOc60nRXYs81ks6RLu9fnhdxY=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=kW7FHLHfrhaPderTfyW9qc6Iy8NK/g9PcpvD85M/BZGkecmCu4+6taPdgclwNlQAK UzeQjQuy2y2R8cRDVJMNCiIpFyzlRKgQsC1KXFeC+bWiuhn8ZjUKSC0jCU/qixvtxR 4hs7LUGqqgp6H2EMcHbdt4oS43Vx8aC4iaeL2yys=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id 6J-eqDENIFOb; Fri, 22 Feb 2019 16:12:22 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri, 22 Feb 2019 16:12:21 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 02EE9379D; Fri, 22 Feb 2019 10:12:20 -0500 (EST)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 02EE9379D
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id EB4A540D358A; Fri, 22 Feb 2019 10:12:20 -0500 (EST)
Date: Fri, 22 Feb 2019 10:12:20 -0500
From: Paul Wouters <paul@nohats.ca>
To: Václav Jirovský <vaclav.jirovsky@gmail.com>
cc: trans@ietf.org
In-Reply-To: <CAAuMfY_2fxJO1mAQS0=pOgmGvNa5AtmZp3TZPvndoLngjVZyrw@mail.gmail.com>
Message-ID: <alpine.LRH.2.21.1902221010280.12674@bofh.nohats.ca>
References: <CAAuMfY_2fxJO1mAQS0=pOgmGvNa5AtmZp3TZPvndoLngjVZyrw@mail.gmail.com>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/8l5OfYi_YU7wusiMaLlkpqIJ7PY>
Subject: Re: [Trans] Add get_entries_max_limit attribute to get-sth request
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Feb 2019 15:12:28 -0000

On Mon, 4 Feb 2019, Václav Jirovský wrote:

[chair hat on]

We are in the final stages of the bis document, so changing anything
at this point requires a high bar. I haven't seen anyone replying to
this, so that would suggst to me that this is not an item that is that
important to fix right now. If you disagree, please speak out.
Especially those who are implementing this document.

Paul

> Date: Mon, 4 Feb 2019 05:09:35
> From: Václav Jirovský <vaclav.jirovsky@gmail.com>
> To: trans@ietf.org
> Subject: [Trans] Add get_entries_max_limit attribute to get-sth request
> 
> Hello all, 
> I would like to propose modification Retrieve Latest Signed Tree Head section of RFC6962 - adding new attribute get_entries_max_limit.
> 
> Reason for this change - 4.6 section actual version:
>
>  Logs MAY restrict the number of entries that can be retrieved per
>    "get-entries" request.  If a client requests more than the permitted
>    number of entries, the log SHALL return the maximum number of entries
>    permissible.  These entries SHALL be sequential beginning with the
>    entry specified by "start".
> 
> If you want to download all entries from CT server, you don't what number of entries will server return to you by request - so you have to
> process, count real number of returned entries and after that, you can do another request. This is not efficient, you could do these request
> in parallel, if you would have garanteed number of returned entries.
> 
> Proposed modification:
> 
> 4.3.  Retrieve Latest Signed Tree Head
> 
> 
> GET https://<log server>/ct/v1/get-sth
> No inputs.
> 
> Outputs:
>       tree_size:  The size of the tree, in entries, in decimal.
>       timestamp:  The timestamp, in decimal.
>       sha256_root_hash:  The Merkle Tree Hash of the tree, in base64.
>       get_entries_max_limit: Maximum entries count provided by server get-entries method.
>       tree_head_signature:  A TreeHeadSignature for the above data.
> 
> 4.6.  Retrieve Entries from Log
> 
> GET https://<log server>/ct/v1/get-entries
> Inputs:
>       start:  0-based index of first entry to retrieve, in decimal.
>       end:  0-based index of last entry to retrieve, in decimal.
> .....
>
>    Logs MAY restrict the number of entries that can be retrieved per
>    "get-entries" request.  If a client requests more than the permitted
>    number of entries ("get_entries_max_limit" output of "get-sth" request),
>    the log SHALL return the maximum number of entries
>    permissible. If a client requests less or equal than the permitted
>    number of entries ("get_entries_max_limit" output of "get-sth" request),
>    the log MUST return the maximum number of entries permissible.
>    These entries SHALL be sequential beginning with the
>    entry specified by "start".
> Best,
> Vaclav Jirovsky
> 
> 
>