[Trans] 6962-bis: Getting rid of SCTWithProofDataV2 (issue 172)
Eran Messeri <eranm@google.com> Thu, 06 April 2017 10:15 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 61BA21293FB for <trans@ietfa.amsl.com>; Thu, 6 Apr 2017 03:15:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, URIBL_BLOCKED=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 iZyy2_pqTVdg for <trans@ietfa.amsl.com>; Thu, 6 Apr 2017 03:15:51 -0700 (PDT)
Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (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 E434C126C23 for <trans@ietf.org>; Thu, 6 Apr 2017 03:15:49 -0700 (PDT)
Received: by mail-it0-x231.google.com with SMTP id 19so2142815itj.1 for <trans@ietf.org>; Thu, 06 Apr 2017 03:15:49 -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:cc; bh=8p4hFJ1u2APigZQziWS0mM26suFgn9zHj0LoQUjKdWQ=; b=M451hjxR09qy30sjGcYhfv1qp3KCg7NaJtrvgj4plZaTNrlMsoD3E7FD+dXfW7QCAU /h99fnHRt9mj3ZXP/ixb68r37Z/W1FqK3Z8A3+NWo9b2LTm9NvYTHV30LyXzoW5mio4p GOa8P88NREr9KsYhwftDTfJwB1u2HPuH/KPwKLvqlsf/AdebdNTy7ErORFIED6mrI2gC brA07rHJWl2IaGuQiFY2/JL4p6JSAOZAvbygZTgnwSBXpQCrPBmn6x8/5TXawHiinMJx T0prxH1BLAEm536czNxl/koP7YJexlibV8WEvvCm6YYEOROrir2zj8+WbSzPVN2BNzZJ bGLw==
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:cc; bh=8p4hFJ1u2APigZQziWS0mM26suFgn9zHj0LoQUjKdWQ=; b=An0KI7kBRXUsRwOINwG30nYyV0fshsaHblIeQ4+wF/qYkoWEftq3xEgACi+mxL8ttL hRTgE7HtUY7rhqn7O4rdWL8BH4JHIIwyg9EmO0xIGWpRRQSL6RphvxqhsDmYUoOQIwqQ ZnZ7yD3pnq+cie/YMPI7q+oyaMKw9owg/ygyOOBsAVG7KvGHFYqm4h7XnNqo/0Zi/n7+ EBMa6Xhz2NzwkB8Y8zcipor5ee0uZTqX0D9Pi0o8w7zg8HJLSFrdzv2T1z3bNqwHlfst orP3/Fp5JPrqm8ZCJSzl6sdEI9pOSWqT12h+2vZYU6RYhdL/9gFD5uhsvhhOT714lXp7 37Qg==
X-Gm-Message-State: AFeK/H2PLCNPaGQ5XvbDswHCw0lpMS0HhFWm2qgEYQlxUmIiReaj43YxpdjCjDCJqxeObVjJzooLZ90cvKgtOJ/y
X-Received: by 10.36.153.134 with SMTP id a128mr26087722ite.90.1491473749076; Thu, 06 Apr 2017 03:15:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.164.200 with HTTP; Thu, 6 Apr 2017 03:15:18 -0700 (PDT)
From: Eran Messeri <eranm@google.com>
Date: Thu, 06 Apr 2017 11:15:18 +0100
Message-ID: <CALzYgEdBRRg9Sib_7vAVOfnTomKwSn+ED4nEYeWAeqndGEUHVw@mail.gmail.com>
To: "trans@ietf.org" <trans@ietf.org>
Cc: Richard Barnes <rlb@ipv.sx>
Content-Type: multipart/alternative; boundary="94eb2c08cd4401c598054c7ccb63"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/Dv58PvTw5QOFsado0UTCXB3VHy0>
Subject: [Trans] 6962-bis: Getting rid of SCTWithProofDataV2 (issue 172)
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, 06 Apr 2017 10:15:53 -0000
Richard Barnes proposed, and I support, removing the SCTWithProofDataV2 structure from 6962-bis. This structure was used to hold a combination of SCT + STH + inclusion proof to that STH. The same functionality can be achieved with a TransItemList that contains each of those, so it makes sense to remove it (as it would simplify parsing of TransItems without affecting functionality). The change was reviewed and merged in https://github.com/google/certificate-transparency-rfcs/pull/225. Also updated in https://trac.ietf.org/trac/trans/ticket/172. Eran
- [Trans] 6962-bis: Getting rid of SCTWithProofData… Eran Messeri
- Re: [Trans] 6962-bis: Getting rid of SCTWithProof… Rob Stradling