IETF Logo Mail Archive

Re: [TLS] IANA Considerations for draft-ietf-tls-dtls-connection-id

"Salz, Rich" <rsalz@akamai.com> Thu, 27 June 2019 01:33 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 47B121203D1 for <tls@ietfa.amsl.com>; Wed, 26 Jun 2019 18:33:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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 AT_qFDi3Ke_B for <tls@ietfa.amsl.com>; Wed, 26 Jun 2019 18:33:00 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::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 1A960120288 for <tls@ietf.org>; Wed, 26 Jun 2019 18:33:00 -0700 (PDT)
Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.16.0.27/8.16.0.27) with SMTP id x5R1WxOE010911; Thu, 27 Jun 2019 02:32:59 +0100
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=BiyaAcRRgdLXWjU57mLFglRUOfCgN4ueQMwu/rT8sNY=; b=Jtj0+5aMsSc5jfXMFLIpCD45O1dlQE9Veh8CYCxjCjsui7OL88vRIEecHngndi7OBrsg g7pZN3MZxZvDbRE/18d5+2khHKNKUYcoLlNBK2RQYv1J+tcUj6yiGI2szry3ktBpyJNk TaybVgnrthyhJB199HtPADjDuUfsIOMN0EPBMlc1TULZi6pU8Uhu8R59/7vTbOQRVIfp ZhCzuGeyqc+gIrFJj/cegZA5DnPy9kwX6hUSLbK3XjWX8r+RyKv1mepeC3hDD9SMNqh2 nzM5v6Htmui4uhuf8/cW7Q3eyQir7SMMrsVLGlGeN7SncOZ5f8byn79tzoi/I6K5ZtUP 0Q==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18] (may be forged)) by m0050095.ppops.net-00190b01. with ESMTP id 2tcf2dh088-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 27 Jun 2019 02:32:59 +0100
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.0.27/8.16.0.27) with SMTP id x5R1Vp2W008168; Wed, 26 Jun 2019 21:32:58 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.33]) by prod-mail-ppoint1.akamai.com with ESMTP id 2tccwp4ede-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 26 Jun 2019 21:32:58 -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.1473.3; Wed, 26 Jun 2019 21:32:57 -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.1473.004; Wed, 26 Jun 2019 21:32:57 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Martin Thomson <mt@lowentropy.net>, "tls@ietf.org" <tls@ietf.org>
Thread-Topic: [TLS] IANA Considerations for draft-ietf-tls-dtls-connection-id
Thread-Index: AQHVJ9M8OcMtUDLH60W4+usGlPOS8qaufZWAgACEtgD//76LgA==
Date: Thu, 27 Jun 2019 01:32:56 +0000
Message-ID: <31CE7B50-C603-4296-A9A4-336CE6A20DB1@akamai.com>
References: <C31B22F0-1AD6-4CBA-AA75-082F940A81CE@sn3rd.com> <34DC165A-B219-418D-8609-C63424E912C7@sn3rd.com> <f14815b0-31e8-4d6d-a1fc-bf05447a6e48@www.fastmail.com>
In-Reply-To: <f14815b0-31e8-4d6d-a1fc-bf05447a6e48@www.fastmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1a.0.190609
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.33.3]
Content-Type: text/plain; charset="utf-8"
Content-ID: <DA51D010295E0D4D8378A2333C1BB48B@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-06-26_14:, , 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=834 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1906270016
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-06-26_14:, , 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=878 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1906270016
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/EqlRe2zvfEnEXV2Z33ko_yWFqZ4>
Subject: Re: [TLS] IANA Considerations for draft-ietf-tls-dtls-connection-id
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: Thu, 27 Jun 2019 01:33:01 -0000

>    Let's look at something less interesting than this, like the use_srtp extension.

No, let's stick with the interesting case before us because, well, it shows a problem.  We have a problem and lack of clarity in the registries, which can even be misleading. Yes the spec is definitive, and maybe a prolog in each TLS registry should state that.  But implementors and reviewers sometimes need a checklist.

v2.23.0 | Report a Bug | By Email