IETF Logo Mail Archive

Re: [Trans] Bad Technical Decision: Closing out the SCT encoding discussion

Stephen Farrell <stephen.farrell@cs.tcd.ie> Fri, 13 March 2015 21:05 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81A0D1A879C for <trans@ietfa.amsl.com>; Fri, 13 Mar 2015 14:05:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 ILHL9v99CRex for <trans@ietfa.amsl.com>; Fri, 13 Mar 2015 14:05:34 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CEC61A86F3 for <trans@ietf.org>; Fri, 13 Mar 2015 14:05:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id EDD2FBEAF; Fri, 13 Mar 2015 21:05:32 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vAblIRvQS08w; Fri, 13 Mar 2015 21:05:31 +0000 (GMT)
Received: from [10.87.48.73] (unknown [86.46.19.44]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id C9E9ABE59; Fri, 13 Mar 2015 21:05:31 +0000 (GMT)
Message-ID: <5503511B.6000709@cs.tcd.ie>
Date: Fri, 13 Mar 2015 21:05:31 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Rob Stradling <rob.stradling@comodo.com>, Russ Housley <housley@vigilsec.com>
References: <550257A0.8050401@gmail.com> <B87AFA6C-2B9F-474C-AE0F-BF07829CD139@vigilsec.com> <550347A0.6070005@cs.tcd.ie> <55034F89.4060501@comodo.com>
In-Reply-To: <55034F89.4060501@comodo.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/trans/leqVAvVNjs-hcWX3dJMUAsqcFsg>
Cc: Paul Wouters <paul@nohats.ca>, trans@ietf.org, Melinda Shore <melinda.shore@gmail.com>
Subject: Re: [Trans] Bad Technical Decision: Closing out the SCT encoding discussion
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 13 Mar 2015 21:05:35 -0000


On 13/03/15 20:58, Rob Stradling wrote:
> On 13/03/15 20:25, Stephen Farrell wrote:
> <snip>
>> And if we interpret 5280 strictly and conclude that is still a
>> good plan then the question would be what to do about the SCT
>> encoding, which could be to do something hacky like prepending
>> another OCTET STRING tag and a length I suppose,
> 
> Stephen, RFC6962 does precisely that, and the current 6962-bis text aims
> to do the same.

Really?

I though the extnValue was just the SignedCertificateTimestampList
and did not contain yet another OCTET STRING tag? That how I read
6962 anyway.

S.

> 
> Adding yet another OCTET STRING would turn it into an OCTET STRING
> inside an OCTET STRING inside an OCTET STRING!
> 
> I'd be surprised if Russ or Steve Kent would consider that to be any
> better than the current plan (an OCTET STRING inside an OCTET STRING).
>

v2.23.0 | Report a Bug | By Email