IETF Logo Mail Archive

Re: [TLS] TLS DNSSEC chain consensus text, please speak up...

Peter Gutmann <pgut001@cs.auckland.ac.nz> Thu, 17 May 2018 05:32 UTC

Return-Path: <pgut001@cs.auckland.ac.nz>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0EB912E8D0 for <tls@ietfa.amsl.com>; Wed, 16 May 2018 22:32:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=auckland.ac.nz
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 gHJgG981lNAY for <tls@ietfa.amsl.com>; Wed, 16 May 2018 22:31:58 -0700 (PDT)
Received: from mx4-int.auckland.ac.nz (mx4-int.auckland.ac.nz [130.216.125.246]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB9F712E8CE for <tls@ietf.org>; Wed, 16 May 2018 22:31:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=mail; t=1526535117; x=1558071117; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=0sxRG1YOjWmSx10ceJjxsp07Ru94WqIN+xpavkWV+9A=; b=kqpmIYC1hBJoLkez5xnSGlVE2RebHr23cCs7PbSM2ukOKD0UJLeHPP2w U1LjN8fHBqEGhujrjSpaslTNnJE4EinqpuXEvqtebvs0eT7TwNFGc1Nn4 /AP8zuq/JckF8b8MuXBdEvPUQntQLWrD5BNQNcrF7Q23TM6Km0TAHkZyq 0l4G4n6Tr26fDfEssPM1zQ7GXXo6Qh3Mcgp6KhoVXbTmEO2mCPposRSFg PyGSAL+o41iRSpsshq4QN9BEqS25klCQGBt127TnbgvWpyk0qTXt5FsRD P9tCExyj8GpLNxnVe9XSLCcy8qAD/823tAEBkw9QKePsbir3csfzKcApg g==;
X-IronPort-AV: E=Sophos;i="5.49,409,1520852400"; d="scan'208";a="11633691"
X-Ironport-HAT: MAIL-SERVERS - $RELAYED
X-Ironport-Source: 10.6.3.2 - Outgoing - Outgoing
Received: from uxcn13-tdc-a.uoa.auckland.ac.nz ([10.6.3.2]) by mx4-int.auckland.ac.nz with ESMTP/TLS/AES256-SHA; 17 May 2018 17:31:54 +1200
Received: from uxcn13-tdc-d.UoA.auckland.ac.nz (10.6.3.5) by uxcn13-tdc-a.UoA.auckland.ac.nz (10.6.3.2) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 17 May 2018 17:31:53 +1200
Received: from uxcn13-tdc-d.UoA.auckland.ac.nz ([fe80::9f5:baf3:43e7:a6e6]) by uxcn13-tdc-d.UoA.auckland.ac.nz ([fe80::9f5:baf3:43e7:a6e6%14]) with mapi id 15.00.1263.000; Thu, 17 May 2018 17:31:53 +1200
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: Melinda Shore <melinda.shore@nomountain.net>, "tls@ietf.org" <tls@ietf.org>
Thread-Topic: [TLS] TLS DNSSEC chain consensus text, please speak up...
Thread-Index: AQHT7QmJ5pwEX58AHEq2b2dh7XH0EKQxqj4AgAFEADL//zipAIABP1kU
Date: Thu, 17 May 2018 05:31:52 +0000
Message-ID: <1526535112699.78173@cs.auckland.ac.nz>
References: <CADyc_gYyyOiBPTMvfm4EkmN3z+8QjzC6WGjzXeEmnXGgKiP_qA@mail.gmail.com> <CAPt1N1kv2S+0ZfdXR4DKJphC4O7xruNdB-rGEBO=N8PzwnSucQ@mail.gmail.com> <m3tvr7450c.fsf@carbon.jhcloos.org>, <ac51696a-f4b3-eebb-828e-1d1a73addcb0@nomountain.net>
In-Reply-To: <ac51696a-f4b3-eebb-828e-1d1a73addcb0@nomountain.net>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [130.216.158.4]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/W8f0VirLbKbnCy0Z1VMcrA7fVuQ>
Subject: Re: [TLS] TLS DNSSEC chain consensus text, please speak up...
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2018 05:32:01 -0000

Melinda Shore <melinda.shore@nomountain.net> writes:

>And again, nobody has said that they intend to implement the proposed 
>mechanism - indeed, when asked, people have said that they won't. 

Doesn't that resolve the issue then?  If no-one's going to implement it 
then it doesn't matter how many bits you use.  Make it one bit, 128 bits,
-1 bits, e^i{pi} bits, it won't matter.

In fact, you could leave the whole RFC blank except for the title, to save
anyone having to sit down and write it.  Like this paper:

https://arxiv.org/abs/1603.09526

Peter.

v2.23.0 | Report a Bug | By Email