IETF Logo Mail Archive

Re: [Trans] duplicate 0x0403 in signature scheme registry

"Salz, Rich" <rsalz@akamai.com> Tue, 30 March 2021 16:55 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D4CF3A1AF4 for <trans@ietfa.amsl.com>; Tue, 30 Mar 2021 09:55:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level:
X-Spam-Status: No, score=-2.799 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, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 YF63WYuHjgrC for <trans@ietfa.amsl.com>; Tue, 30 Mar 2021 09:55:11 -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 7FDFB3A1AF3 for <trans@ietf.org>; Tue, 30 Mar 2021 09:55:11 -0700 (PDT)
Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.16.0.43/8.16.0.43) with SMTP id 12UGkZmM025588; Tue, 30 Mar 2021 17:55:09 +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 : mime-version; s=jan2016.eng; bh=v6nL0s3XrBVOn3JdFd0AxyVoV9rrFw6En1/8nwomFh8=; b=E/l+PuJcROK3QttBTZNRGGKoqOi5QX9ec+fW2YtFjqK8mtXCZ7Mr5q+2rs8p3TF0g8QS QbKGGkYEHk4QdKD9kzRFCaZcrGeVlGjX5xre5ImpxMIDq6q8Vj8B/wFnxTdYSwoYEe+j eqjP/DhcW9MsVnkH4rwXC+pHMWptzKZQ7FM9ZXp3+tFggmUqKCyUrq7eCgVZnb7PoS/s Lzg4wLotwQP+euQLNrmddI5CqQjLiaKmHK6CFazAhpAK8i1xuRYQQV3UZ9JXstRaabx8 DmOyU9zDF6Fq5BunhxFlYxaIIzBl6kHb7W0yuYECyZmXmvVefJHkyRYsf8SqT/ldaVYQ JA==
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 37m59dnkjf-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 30 Mar 2021 17:55:09 +0100
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.0.43/8.16.0.43) with SMTP id 12UGo3vX026021; Tue, 30 Mar 2021 12:55:08 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.33]) by prod-mail-ppoint1.akamai.com with ESMTP id 37j01ygnp7-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 30 Mar 2021 12:55:08 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb4.msg.corp.akamai.com (172.27.123.104) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 30 Mar 2021 12:55:07 -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.1497.012; Tue, 30 Mar 2021 12:55:07 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Rob Stradling <rob@sectigo.com>, "trans@ietf.org" <trans@ietf.org>
Thread-Topic: duplicate 0x0403 in signature scheme registry
Thread-Index: AQHXJBAqA2znVXZUyECcvT9HmadRT6qbOGeLgAGKWIA=
Date: Tue, 30 Mar 2021 16:55:07 +0000
Message-ID: <7FEA0790-F768-487C-A08F-F0151DCE8150@akamai.com>
References: <1E0248E8-A269-4C00-A0CA-60D4F89639A4@akamai.com> <MW3PR17MB4122D493F93E58FB545ECA3AAA7E9@MW3PR17MB4122.namprd17.prod.outlook.com>
In-Reply-To: <MW3PR17MB4122D493F93E58FB545ECA3AAA7E9@MW3PR17MB4122.namprd17.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.47.21031401
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.118.139]
Content-Type: multipart/alternative; boundary="_000_7FEA0790F768487CA08FF0151DCE8150akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-03-30_08:2021-03-30, 2021-03-30 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=920 bulkscore=0 malwarescore=0 mlxscore=0 phishscore=0 adultscore=0 spamscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2103250000 definitions=main-2103300121
X-Proofpoint-GUID: heRNTp1XmFPfwbiMfUHi8NIkY0MyxFwW
X-Proofpoint-ORIG-GUID: heRNTp1XmFPfwbiMfUHi8NIkY0MyxFwW
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-03-30_08:2021-03-30, 2021-03-30 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 clxscore=1015 bulkscore=0 malwarescore=0 suspectscore=0 spamscore=0 mlxlogscore=852 mlxscore=0 phishscore=0 impostorscore=0 priorityscore=1501 lowpriorityscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2103250000 definitions=main-2103300121
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 184.51.33.18) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint1
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/IxNiLGNNT8hlxXbCXdE9DDcDo8g>
Subject: Re: [Trans] duplicate 0x0403 in signature scheme registry
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Mar 2021 16:55:17 -0000

>> The duplicate 0x0403 seems a bug. Any implementor care to clarify


  *   The duplicate 0x0403 is deliberate, because Deterministic and Non-Deterministic ECDSA have different References (RFC6979 and FIPS186-4).

How does a relying party know which one is actually being used?  (I am sure I am missing something obvious.)

> As for why this registry, I assume it’s to be a subset of the TLS registry “just because”  Are there any other reasons?

Yes, this was re-wording Mirja’s question. I understand the reasoning; is it worth putting something into the draft?

v2.23.0 | Report a Bug | By Email