Re: [TLS] some thoughts on dnssec-chain-extension, pinning, and broader semantics

"Salz, Rich" <rsalz@akamai.com> Mon, 05 November 2018 14:40 UTC

Return-Path: <rsalz@akamai.com>
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 8A06D1298C5 for <tls@ietfa.amsl.com>; Mon, 5 Nov 2018 06:40:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.172
X-Spam-Level:
X-Spam-Status: No, score=-1.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, KHOP_DYNAMIC=1.999, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 VRmdlO7gc3_w for <tls@ietfa.amsl.com>; Mon, 5 Nov 2018 06:40:38 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 51852128BCC for <tls@ietf.org>; Mon, 5 Nov 2018 06:40:38 -0800 (PST)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.27/8.16.0.27) with SMTP id wA5EebTn021610 for <tls@ietf.org>; Mon, 5 Nov 2018 14:40:37 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=SSkno2jP4AYQ00lzik33emHY+aIg5BYU+IgDRCLDfDk=; b=c7U9KYsE59t2yERUlluLL89/9kMrurGqT2pGQso0UHJ+c3Th4d+lkm5UyEdWBUNPB5/8 Q9sSA1YxGiRjk33q0L7Nare0tTvcsZiVIKln6E43JN39c8Wvv5r3PSYAT7Uh1VCUOnl6 Q7bSvNSAfYHkM5/yQEBXOxnuGyGW28tOVofgVqf+pcMKDmollnO7+AUsdqAkJlWoewxI fnmiC8+ayIYHSLydFIYCN9QtK7YTpW3Lmx+D6VEOeEmoFU7X9yYOSgNtd6+rtoHcvPkO JPAxx1bKC6w9CdPn6Bv0471uMPK6dPM2rGOffNHSsxeki12uzuSyB/OBg5O+ma7x28jj +w==
Received: from prod-mail-ppoint3 (a96-6-114-86.deploy.static.akamaitechnologies.com [96.6.114.86] (may be forged)) by m0050102.ppops.net-00190b01. with ESMTP id 2njqu8g005-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <tls@ietf.org>; Mon, 05 Nov 2018 14:40:36 +0000
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.21/8.16.0.21) with SMTP id wA5EZP3x018204 for <tls@ietf.org>; Mon, 5 Nov 2018 09:40:35 -0500
Received: from email.msg.corp.akamai.com ([172.27.27.21]) by prod-mail-ppoint3.akamai.com with ESMTP id 2nh70wsdb6-18 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <tls@ietf.org>; Mon, 05 Nov 2018 09:40:35 -0500
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com (172.27.27.101) by ustx2ex-dag1mb5.msg.corp.akamai.com (172.27.27.105) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Mon, 5 Nov 2018 08:37:27 -0600
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com ([172.27.6.131]) by ustx2ex-dag1mb1.msg.corp.akamai.com ([172.27.6.131]) with mapi id 15.00.1365.000; Mon, 5 Nov 2018 08:37:27 -0600
From: "Salz, Rich" <rsalz@akamai.com>
To: "<tls@ietf.org>" <tls@ietf.org>
Thread-Topic: [TLS] some thoughts on dnssec-chain-extension, pinning, and broader semantics
Thread-Index: AQHUdQhHQHeeEywpzUiXrHdyTpFMNKVBmlaA//+2gIA=
Date: Mon, 05 Nov 2018 14:37:26 +0000
Message-ID: <1450B335-5F7D-43A6-8BC6-181DFE1865C9@akamai.com>
References: <20181105130157.GF54966@kduck.kaduk.org> <2714F93F-3658-4E2E-8390-284C6D401447@dukhovni.org>
In-Reply-To: <2714F93F-3658-4E2E-8390-284C6D401447@dukhovni.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.12.0.181014
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.152.225]
Content-Type: text/plain; charset="utf-8"
Content-ID: <E958DFA92D2CDB4C9563BDFF4D7E21D7@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-11-05_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=848 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1811050134
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-11-05_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=848 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1811050134
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/dNgQbi01DBcrFjr4HcZIInpePDM>
Subject: Re: [TLS] some thoughts on dnssec-chain-extension, pinning, and broader semantics
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 05 Nov 2018 14:40:40 -0000

Is it fair to describe the draft as enabling a trust model based on DNSSEC, rather than the default X.509 hierarchy and trust store which is implemented by default?

Please try very hard to keep the answer brief.