Re: [Trans] [Public Notary Transparency Wiki] #163: The entire STH history of the log must be accessible
"trans issue tracker" <trac+trans@ietf.org> Thu, 04 May 2017 12:31 UTC
Return-Path: <trac+trans@ietf.org>
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 D694912948B for <trans@ietfa.amsl.com>; Thu, 4 May 2017 05:31:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.02
X-Spam-Level:
X-Spam-Status: No, score=0.02 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_20=-0.001, MISSING_HEADERS=1.021] autolearn=no 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 PVLJlh75iqvu; Thu, 4 May 2017 05:31:59 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 28B01126E01; Thu, 4 May 2017 05:31:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: trans issue tracker <trac+trans@ietf.org>
X-Trac-Version: 1.0.10
Precedence: bulk
Cc: trans@ietf.org
Auto-Submitted: auto-generated
X-Mailer: Trac 1.0.10, by Edgewall Software
X-Trac-Project: Public Notary Transparency Wiki
Date: Thu, 04 May 2017 12:31:59 -0000
X-URL:
X-Trac-Ticket-URL: https://trac.ietf.org/trac/trans/ticket/163#comment:4
Message-ID: <037.acf46427135f40b4e8f605d34ae20197@ietf.org>
References: <022.7da86585e9c171aeb8d893a2431c2e8c@ietf.org>
X-Trac-Ticket-ID: 163
In-Reply-To: <022.7da86585e9c171aeb8d893a2431c2e8c@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/BrI_cSsOkuL5e7NDH6fuWgeFXzA>
Subject: Re: [Trans] [Public Notary Transparency Wiki] #163: The entire STH history of the log must be accessible
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.22
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:32:00 -0000
#163: The entire STH history of the log must be accessible -------------------------+----------------------- Reporter: rlb@… | Owner: eranm@… Type: defect | Status: assigned Priority: major | Milestone: Component: rfc6962-bis | Version: Severity: - | Resolution: Keywords: | -------------------------+----------------------- Comment (by eranm@…): (alternative discussed out-of-band with colleagues): Allow requesting STHs by specification of time range. Similar to get-entries, the log would return a list of STHs issued on that time range (capped by an amount chosen by the log). The problem it solves is the lack of ability to verify that the log did not breach the MMD throughout its lifetime: A submission's timestamp is available via get-entries, but unless a monitor has observed STHs issued by the log around the time an entry was created for it, there's no proof that the entry was incorporated within the MMD. -- Ticket URL: <https://trac.ietf.org/trac/trans/ticket/163#comment:4> Public Notary Transparency Wiki <https://trac.ietf.org/trac/trans> My example project
- Re: [Trans] [Public Notary Transparency Wiki] #16… trans issue tracker
- Re: [Trans] [Public Notary Transparency Wiki] #16… trans issue tracker
- Re: [Trans] [Public Notary Transparency Wiki] #16… trans issue tracker