[Trans] Add get_entries_max_limit attribute to get-sth request

Václav Jirovský <vaclav.jirovsky@gmail.com> Mon, 04 February 2019 10:09 UTC

Return-Path: <vaclav.jirovsky@gmail.com>
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 4E428130E3F for <trans@ietfa.amsl.com>; Mon, 4 Feb 2019 02:09:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.02
X-Spam-Level:
X-Spam-Status: No, score=-1.02 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, FROM_EXCESS_BASE64=0.979, HTML_MESSAGE=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 ua22PyghWzwk for <trans@ietfa.amsl.com>; Mon, 4 Feb 2019 02:09:47 -0800 (PST)
Received: from mail-ot1-x32c.google.com (mail-ot1-x32c.google.com [IPv6:2607:f8b0:4864:20::32c]) (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 4765B130E2E for <trans@ietf.org>; Mon, 4 Feb 2019 02:09:47 -0800 (PST)
Received: by mail-ot1-x32c.google.com with SMTP id v23so11988814otk.9 for <trans@ietf.org>; Mon, 04 Feb 2019 02:09:47 -0800 (PST)
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=tumspwJwX2LVH2wqZoxGuEilOHYixxHuzg3nYtY72fQ=; b=l9vOEuBQ4/t3fCCSbUZ1lCnSLBs4wQPqhcxJuqpxqnWY42dUXKpPCX7F/Nt4dZkQiq eZmggyDvvDz0T+F8fZUETpZK97R7TX5Y7H1N64Ln+d+AvtB6+LergibIosSh66TElx0P 0tCKmeCyq9+2EHazunGEK85r+XwvgMjM4RMJBbiR7a1ADo+uCDsaM9neazvUvIJaNaFK YLqf6XvbEZldeXba2TdgLfQcEoXNvBdWpWdzTACYAqAGb5Q8DOdY7Zd9ZVeMDAKphK/i yFOgznR9Hqz2m+F0NXMud240NJa0/1KjGaObz5266fK4m8baIql6e9XssKPX2jSDA6Dw /lJA==
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=tumspwJwX2LVH2wqZoxGuEilOHYixxHuzg3nYtY72fQ=; b=MI2NK10d3rjjNifoxL1iv5rhG5uMih5hmRJ8TWULU7PYwQ0ONcuwf44TK0EU1XMlZx sJlIQzOAC5eRZX0JtOqhM7PW/E0R99yD2PKk8Cq2Pymx5SoLvFtbgQb6W39dO+cPz8uB uQ1DKs7FXDJXiO8cexXv6TwNl0VNoRqKcIq0FrDYbSVA0UJ+J1Cpj/ckz0LnK3dQGGaI uiPec4x1bGUSG+7q3cLO6xbioiR8pNbUnWp3/BT4Q1Xmq5ut4yNfnEyouJrTLSbN0RNX FNg9PuVmzaYBgg6P7dI9gEJXTiJimuGkvEGshIj8+YDuvY8XVSd71r+ygwb3AMLcJQk8 Hfrg==
X-Gm-Message-State: AJcUukdFD+tcmqlSJFBu2BPTfaH9dJk8yNhxXS7XXvZOvhu+WjM5p+wD epGkKw9mq0opKtvX+cG3GDJX3w2ti/uxsuQQWLzv6G/z
X-Google-Smtp-Source: ALg8bN5ck81styF/aXclIaPUoLBqTzCfZG1Gks1NCpDkX9HX3CltnTs5/Jrn0r+iIvXMAUJz4plaIMyi1IdKUuxe134=
X-Received: by 2002:aca:f553:: with SMTP id t80mr26658661oih.358.1549274986024; Mon, 04 Feb 2019 02:09:46 -0800 (PST)
MIME-Version: 1.0
From: Václav Jirovský <vaclav.jirovsky@gmail.com>
Date: Mon, 04 Feb 2019 11:09:35 +0100
Message-ID: <CAAuMfY_2fxJO1mAQS0=pOgmGvNa5AtmZp3TZPvndoLngjVZyrw@mail.gmail.com>
To: trans@ietf.org
Content-Type: multipart/alternative; boundary="0000000000003395e005810eb1c1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/TCNK5bB90w-pfUoq5LwjtuJ6e3c>
Subject: [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: Mon, 04 Feb 2019 10:18:51 -0000

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 <https://tools.ietf.org/html/rfc6962#section-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 <https://tools.ietf.org/html/rfc6962#section-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