IETF Logo Mail Archive

Re: [TLS] comments on draft-ietf-tls-tls13-19

"Salz, Rich" <rsalz@akamai.com> Mon, 24 April 2017 13:21 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 4D0E21294CE for <tls@ietfa.amsl.com>; Mon, 24 Apr 2017 06:21:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham 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 KXLqCb4Xpx5X for <tls@ietfa.amsl.com>; Mon, 24 Apr 2017 06:21:57 -0700 (PDT)
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 3453C1294B5 for <tls@ietf.org>; Mon, 24 Apr 2017 06:21:57 -0700 (PDT)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.21/8.16.0.21) with SMTP id v3ODGhar012686; Mon, 24 Apr 2017 14:21:54 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=jan2016.eng; bh=MKNG5nsHEfez7wDCqanALVeLwfKXNElV7Kszc5L+wYI=; b=Ma2F2nMoWzfx6ngnhJohaqWUVRLooAHqvx8cprHPY8HIJA/V9yx2csHWMU3uqcjXsNTS fZHTJtk4wz9uymhquIz4rJv0XRA8zk1AAgfQM96R049IirKcA4hKMppqPC7EWcXRGGD9 QiNDShhAw0WlE6jF6myZntTPRdIk8WVwmM+/Q2/pFYSv/M1yN9jqijVPo+lG7oU5BF6l yV3lSoLsS9a39sC2y0HJtO0NZVIuBlZfbN+j8sbs4PBg1HvuJfen5XkgEVSv1Csfht9e P37NyF2GWwwPysPJjHaY2OK2dlxCMY2k+1WGTmuM0fz7hVdCM83mUvUNQztBfvKOxsXJ Ow==
Received: from prod-mail-ppoint1 (a184-51-33-18.deploy.static.akamaitechnologies.com [184.51.33.18] (may be forged)) by m0050102.ppops.net-00190b01. with ESMTP id 29yv8b3a9b-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 24 Apr 2017 14:21:54 +0100
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.0.17/8.16.0.17) with SMTP id v3ODLEFP018685; Mon, 24 Apr 2017 09:21:53 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.32]) by prod-mail-ppoint1.akamai.com with ESMTP id 2a02gvjdjc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 24 Apr 2017 09:21:53 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb1.msg.corp.akamai.com (172.27.123.101) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Mon, 24 Apr 2017 09:21:52 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1263.000; Mon, 24 Apr 2017 09:21:52 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Brian Smith <brian@briansmith.org>, Ryan Sleevi <ryan-ietftls@sleevi.com>
CC: "tls@ietf.org" <tls@ietf.org>
Thread-Topic: [TLS] comments on draft-ietf-tls-tls13-19
Thread-Index: AQHSqJjSCranHeW0Kkim8uZ5ZLnDdaGsJHyAgBTntQCAD0N5gIABYGgAgAABzoCAAKKPAIAASFmAgAH7pACAABGIgA==
Date: Mon, 24 Apr 2017 13:21:52 +0000
Message-ID: <839a775972954f5ba56f251b53e1feed@usma1ex-dag1mb1.msg.corp.akamai.com>
References: <1490797726.28079.18.camel@redhat.com> <1490797957.28079.20.camel@redhat.com> <CABcZeBMCZrVKM959F3ycKN_WAky2NAZTy9OOetnC+KJAj3L+Pw@mail.gmail.com> <1492786351.14070.2.camel@redhat.com> <CABcZeBOe4-yEW8r15fsOtHJbQrnqGJ6oUaGYjoUwYS0MQE-rHQ@mail.gmail.com> <20170422120017.GA4201@LK-Perkele-V2.elisa-laajakaista.fi> <20170422214205.bxu5whfqzy5kshsw@roeckx.be> <CAErg=HGLD_Xvu1BJG-J1TNbPMx2bH0t=+EFfQRFEpMa01-bJVQ@mail.gmail.com> <CAFewVt6dth_bw+MRhqH62v7RBNj4WWP3mNvVTWQg9mV1d3a3Jg@mail.gmail.com>
In-Reply-To: <CAFewVt6dth_bw+MRhqH62v7RBNj4WWP3mNvVTWQg9mV1d3a3Jg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.32.168]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-04-24_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1704240235
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-04-24_10:, , 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=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1704240234
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/RX5JyK9V7USuwWd3KV4TDdgytIw>
Subject: Re: [TLS] comments on draft-ietf-tls-tls13-19
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: Mon, 24 Apr 2017 13:21:58 -0000

> The TLS 1.3 specification isn't the right place to specify what to do with OCSP responses that do not have a nextUpdate field.

When phrased like this, it seems completely obvious to me that this correct.

v2.23.0 | Report a Bug | By Email