Re: [TLS] Additional changes for draft-ietf-tls-iana-registry-updates

"Salz, Rich" <rsalz@akamai.com> Mon, 26 March 2018 17:24 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 735F9120227 for <tls@ietfa.amsl.com>; Mon, 26 Mar 2018 10:24:59 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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 o4sFip3cn3rs for <tls@ietfa.amsl.com>; Mon, 26 Mar 2018 10:24:58 -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 2A2AE1201F2 for <tls@ietf.org>; Mon, 26 Mar 2018 10:24:58 -0700 (PDT)
Received: from pps.filterd (m0122331.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w2QHOoLj021142 for <tls@ietf.org>; Mon, 26 Mar 2018 18:24:56 +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-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=TDLXd48wuPwRlmrOAXrACTcTJWGmwucp89GdPzgmgDA=; b=HqvvV4XlIp10K+ZOvIhHJjqI41rAQb+0fQ/Uz9LDD1hzYDrtI3lVXWJ4e6RnX+GlBIz7 slY6rCtK0a+7BAoZS7Hp3lpqn58zhQs6tTmppLBpIb9LB66MKZ1JfzItTmGQJVvWmH4s k/X4zRyyog0qmVQEpTLHns3u6IvFdP2hQaXvHfyNC+jRNxW/QK5JWCWyNteUcSrc+moo 8ZntnrhQuoyIKG/DIsodficdszN4Fp6jnFk9FopEb6R6DyPVQjk0/oO7szE4vrbuNXC6 2FWtBj3VuH+QDpvXgl8UyGb/Rfc18LAg3kRh/w3XMEXXn4CHog5SmuJbY/0hCm/0dzjw lg==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18]) by mx0b-00190b01.pphosted.com with ESMTP id 2gwjufcgbu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <tls@ietf.org>; Mon, 26 Mar 2018 18:24:55 +0100
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w2QHL37C032196 for <tls@ietf.org>; Mon, 26 Mar 2018 13:24:55 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.57]) by prod-mail-ppoint1.akamai.com with ESMTP id 2gwj0vdf3c-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <tls@ietf.org>; Mon, 26 Mar 2018 13:24:55 -0400
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com (172.27.123.103) by usma1ex-dag3mb5.msg.corp.akamai.com (172.27.123.55) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Mon, 26 Mar 2018 10:24:54 -0700
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com ([172.27.123.103]) by usma1ex-dag1mb3.msg.corp.akamai.com ([172.27.123.103]) with mapi id 15.00.1263.000; Mon, 26 Mar 2018 13:24:54 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: "Kaduk, Ben" <bkaduk@akamai.com>
CC: "<tls@ietf.org>" <tls@ietf.org>
Thread-Topic: [TLS] Additional changes for draft-ietf-tls-iana-registry-updates
Thread-Index: AQHTvS9f2MtPAwaKqkerIh0KjwjgpqPcU8sAgAAA7gCAABmKAP//0OGAgAHWroD//71/gIAFQi0A//++14A=
Date: Mon, 26 Mar 2018 17:24:54 +0000
Message-ID: <51277A20-589E-472C-8069-F5B666373F45@akamai.com>
References: <505FCF83-C92E-4A90-83BF-4B2C4796EBE6@sn3rd.com> <77875DAA-EE63-4EBA-8951-61F89D9FBAD8@sn3rd.com> <1521713417877.45777@cs.auckland.ac.nz> <21D7BBB3-5B19-4721-B08A-9AD887F37F99@sn3rd.com> <EBD5C0A9-FE81-4823-BDBA-88F575467B97@akamai.com> <20180323125758.GE25919@kduck.kaduk.org> <FE8B999F-6A3D-4E7F-93A2-A8A2A20C5BED@akamai.com> <ef364e4b-d8bc-c8fe-5d2a-0e78fb30631c@akamai.com>
In-Reply-To: <ef364e4b-d8bc-c8fe-5d2a-0e78fb30631c@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.b.0.180311
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.36.187]
Content-Type: text/plain; charset="utf-8"
Content-ID: <EC277A61138DDF4F87BF17EC9723E03B@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-26_07:, , 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=920 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803260180
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-26_07:, , 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 mlxscore=0 impostorscore=0 mlxlogscore=853 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803260180
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/TbtQtcTKrEDqpVjiOI2rpWKSnow>
Subject: Re: [TLS] Additional changes for draft-ietf-tls-iana-registry-updates
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, 26 Mar 2018 17:24:59 -0000

Is it now impossible adding new things to TLS 1.2?  I don't believe the WG understood that this would be the situation.  So I disagree with your claim that this was our understanding of the situation.

Okay, it turns out that David's neat hack make some things harder. So what?