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

Benjamin Kaduk <> Fri, 16 March 2018 20:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 10E501252BA for <>; Fri, 16 Mar 2018 13:07:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Q2kRuQMc4idz for <>; Fri, 16 Mar 2018 13:07:28 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9F2FB124217 for <>; Fri, 16 Mar 2018 13:07:28 -0700 (PDT)
X-AuditID: 12074425-f35ff700000032c4-ed-5aac23fcbd53
Received: from ( []) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id 4E.54.12996.CF32CAA5; Fri, 16 Mar 2018 16:07:25 -0400 (EDT)
Received: from (OUTGOING-AUTH-1.MIT.EDU []) by (8.13.8/8.9.2) with ESMTP id w2GK7NsH018530; Fri, 16 Mar 2018 16:07:23 -0400
Received: from ( []) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by (8.13.8/8.12.4) with ESMTP id w2GK7K4D011327 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 16 Mar 2018 16:07:22 -0400
Date: Fri, 16 Mar 2018 15:07:19 -0500
From: Benjamin Kaduk <>
To: Sean Turner <>
Cc: "<>" <>
Message-ID: <>
References: <>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <>
User-Agent: Mutt/1.9.1 (2017-09-22)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprGKsWRmVeSWpSXmKPExsUixCmqrftXeU2UQc90EYsrqxqZLT6d72J0 YPJYsuQnk8fBg4wBTFFcNimpOZllqUX6dglcGRPmWBecYq+4duw5cwPjKrYuRk4OCQETiRMz V7B3MXJxCAksZpKYcugLM0hCSGAjo8S92VEQiatAiS03gRIcHCwCqhLHZhSC1LAJqEg0dF8G qxcRUJBoOvqAFcRmFlCWmNW1HMwWFvCTOHn0FCtIKy/Qsq7WIIjxNhLfv/wCa+UVEJQ4OfMJ C0SrusSfeZfANjELSEss/8cBEZaXaN46G6ycU8BWYs9SiCtFgTbt7TvEPoFRcBaSSbOQTJqF MGkWkkkLGFlWMcqm5Fbp5iZm5hSnJusWJyfm5aUW6Vro5WaW6KWmlG5iBAUzu4vqDsY5f70O MQpwMCrx8FpcWB0lxJpYVlyZe4hRkoNJSZTX+ThQiC8pP6UyI7E4I76oNCe1+BCjBAezkgjv n99AOd6UxMqq1KJ8mJQ0B4uSOK+HiXaUkEB6YklqdmpqQWoRTFaGg0NJglcaGLVCgkWp6akV aZk5JQhpJg5OkOE8QMMjQGp4iwsSc4sz0yHypxgtOdpWPmlj5tj16CWQvPHidRuzEEtefl6q lDjveyWgBgGQhozSPLiZoOQkkb2/5hWjONCLwrxSIFU8wMQGN/UV0EImoIWZ21aALCxJREhJ NTC6nw/symK9tC7glMq7wEfMVQ8mVkQ1tCw0VzWJ/LTg7q55KzhnVT08u7L3bcakghc84alV bM91C66ZWv/f37+7J1/NXEfJIFyAr2uS67oF7ZzKtT5MPjPnqvmGJMx7er1/1++oraypmk4q unKrGcXr06ZVKkkLZU+u2RP02GfO5KJdv3ed7FNiKc5INNRiLipOBAApolzkKQMAAA==
Archived-At: <>
Subject: Re: [TLS] Additional changes for draft-ietf-tls-iana-registry-updates
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." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 16 Mar 2018 20:07:30 -0000

On Fri, Mar 16, 2018 at 02:01:48PM +0000, Sean Turner wrote:
> During Adam Roach’s AD review of draft-ietf-tls-tls13, he noted something about the HashAlgorithm and that made me go look at what was said in draft-ietf-tls-iana-registry-updates.  Turns out that 4492bis assigned some values draft-ietf-tls-iana-registry-updates was marking as reserved.  I have fixed that up in:
> One further point brought out in discussions with Adam was that if we’re really closing the HashAlgorithm and SignatureAlgorithms registry we need to also mark 224-255 as deprecated.  Currently these are marked as Reserved for Private Use.  So the question is should we mark 224-255 as deprecated in these two registries?

With no hats, yes, we should mark those ranges as deprecated, since
there is no warning about them in the SignatureScheme registry and
the latter is the way of the future.