[Trans] Providing the history of STHs a log has issued (in 6962-bis)

Eran Messeri <eranm@google.com> Thu, 04 May 2017 12:42 UTC

Return-Path: <eranm@google.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 0509E126E01 for <trans@ietfa.amsl.com>; Thu, 4 May 2017 05:42:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.802
X-Spam-Level:
X-Spam-Status: No, score=-0.802 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 dnjU1pGHc65p for <trans@ietfa.amsl.com>; Thu, 4 May 2017 05:42:30 -0700 (PDT)
Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (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 6E0681292F5 for <trans@ietf.org>; Thu, 4 May 2017 05:42:30 -0700 (PDT)
Received: by mail-it0-x22f.google.com with SMTP id o5so15381486ith.1 for <trans@ietf.org>; Thu, 04 May 2017 05:42:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=X+MzadfZABHa8ovp0ULhRo4SsxNcO5U+R4jY8rndmLk=; b=eVOj86kr+yHHc3sXFv3UTGjm1p7/PxluQkk2PrDizFnaN+2qu0AmPgznKAukXxlx8j po6gVfahy0eTB7kSjmdWrtVVkt+rsHJHNtydKfMmPOCHx3dnvgBRGdRNeyTJqnEZEocY 3jGVrEP09hCmSQPddZX9l0anhOGgE/YTPjnHDrddB9SGYlLqQhqyc4K0bw6j/Qq39FJY ZcNYaugPQuIn8KKLGeU5nAIkGs4UptR/RBK5h2KoEddz7vOgjUVKYP0vWwce5eaT6FIl dVWg3bcYhzb+TlaaiBFowDbg/GfNk7hE/7rfpB5ZuBU+vTp01t99+iuGs2uLwzJbb1aB zarQ==
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=X+MzadfZABHa8ovp0ULhRo4SsxNcO5U+R4jY8rndmLk=; b=J8JZ3PZ62SzRMn6PYYEzEyUmVEAf8UrM/sC/ronZeVCLYkh+986wwRMXhp4JZTxcDg qAs4+/Hgj2SLs95+z8ffSoSupVEdYDzozvfKEwvbJ0vMssTRvmp8tMTcXcmTCnIgXLOX 6kPO+x2dc1omk0q85MHZZ10Gea8Zf452vKmN8C0uSzfOHHUryTOHJAr6Pe4g6Zh3Uni1 XgSitbXYxvCvclZSvvIroHfXItwYnKvf+qCnUM3qTk3SMbxlA0WfGj576KzL1Dw9GGtb 2r1YwJi9UsxuekLrNPcpFghVRoNZdM7pmVm08hNhmC5/2h61Pra+W2SwduqyJguUEdOg Vt0A==
X-Gm-Message-State: AN3rC/7/C0HYBIIz+wRy5VGIKcxoykosMaG8vbDJ0fQG+xaPCVYMYYeW VR39sgxliHPQ9cYnZhSkb53JIJgZUS8O4FJQng==
X-Received: by 10.36.3.13 with SMTP id e13mr1657028ite.112.1493901749575; Thu, 04 May 2017 05:42:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.47.41 with HTTP; Thu, 4 May 2017 05:41:59 -0700 (PDT)
From: Eran Messeri <eranm@google.com>
Date: Thu, 04 May 2017 13:41:59 +0100
Message-ID: <CALzYgEe+PbYJN6Zz4NnPXBnnhYCi8Op-WmSzFKGxRv+uf+b=sA@mail.gmail.com>
To: "trans@ietf.org" <trans@ietf.org>
Content-Type: multipart/alternative; boundary="001a11419bfa1d2391054eb21b17"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/ONyGZlzn1-NyPsMKB58JeQF9-NU>
Subject: [Trans] Providing the history of STHs a log has issued (in 6962-bis)
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 04 May 2017 12:42:32 -0000

I'm looking for feedback on the proposal to add an API endpoint which would
provide access to historical STHs issued by the log (
https://trac.ietf.org/trac/trans/ticket/163).

I personally think it's a good idea to have such an API since it'd allow
auditing a log for past compliance with the MMD requirement.

Rob Stradling has sent a PR
<https://github.com/google/certificate-transparency-rfcs/pull/200/> for
this.

Eran