Return-Path: <era@x500.eu>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id D3CF8126DEE
 for <cfrg@ietfa.amsl.com>; Fri,  8 Dec 2017 01:02:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.101
X-Spam-Level: 
X-Spam-Status: No, score=0.101 tagged_above=-999 required=5
 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7]
 autolearn=ham autolearn_force=no
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 spy3-MPD5aBx for <cfrg@ietfa.amsl.com>;
 Fri,  8 Dec 2017 01:02:53 -0800 (PST)
Received: from mail04.dandomain.dk (mail04.dandomain.dk [194.150.112.204])
 (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 1FEC2124319
 for <cfrg@irtf.org>; Fri,  8 Dec 2017 01:02:52 -0800 (PST)
Received: from Morten ([62.44.135.202])
 by mail04.dandomain.dk (DanDomain Mailserver) with ASMTP id
 4201712081002471840; Fri, 08 Dec 2017 10:02:47 +0100
From: "Erik Andersen" <era@x500.eu>
To: "Cfrg" <cfrg@irtf.org>
Cc: "Carsten Strunge" <CAS@energinet.dk>
Date: Fri, 8 Dec 2017 10:02:47 +0100
Message-ID: <000801d37003$5165df80$f4319e80$@x500.eu>
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="----=_NextPart_000_0009_01D3700B.B32C9170"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AdNwAj7rtSh6exWUShSQuW95dPBnSg==
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/o19PYzJL7JC5IHNtQl3j8-9FwXU>
Subject: [Cfrg] Use of the term "deprecated"
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/cfrg>,
 <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/cfrg>,
 <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Dec 2017 09:02:56 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0009_01D3700B.B32C9170
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

In the smart grid security standards the term deprecated is used for certain
cryptographic algorithms, such as SHA-1, instead of disallowing them. NIST
in SP 800-57, Part 1 Revision 4 has stopped using the term deprecated.

 

What is the general feeling among  list members on using the term deprecated
on cryptographic algorithms?

 

Erik


------=_NextPart_000_0009_01D3700B.B32C9170
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB =
link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoNormal>In the smart grid security standards the term =
deprecated is used for certain cryptographic algorithms, such as SHA-1, =
instead of disallowing them. NIST in SP 800-57, Part 1 Revision 4 has =
stopped using the term deprecated.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>What is the =
general feeling among &nbsp;list members on using the term deprecated on =
cryptographic algorithms?<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Erik<o:p></o:p></p></div></body></html>
------=_NextPart_000_0009_01D3700B.B32C9170--

