IETF Logo Mail Archive

[Trans] duplicate 0x0403 in signature scheme registry

"Salz, Rich" <rsalz@akamai.com> Sun, 28 March 2021 20:23 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 630493A257C for <trans@ietfa.amsl.com>; Sun, 28 Mar 2021 13:23:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_NONE=-0.0001, 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 YtvEu5jBbO_1 for <trans@ietfa.amsl.com>; Sun, 28 Mar 2021 13:23:13 -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 2F49F3A2578 for <trans@ietf.org>; Sun, 28 Mar 2021 13:23:12 -0700 (PDT)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.43/8.16.0.43) with SMTP id 12SKFDkW011682 for <trans@ietf.org>; Sun, 28 Mar 2021 21:23:11 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : content-type : mime-version; s=jan2016.eng; bh=9p7VAQKzaamTWO5MhdmAHAPUzPDug4l6I1wqoCdibNQ=; b=MN2e66xASIdOW022Ptje/q/Sx5GW/g5Z8HhFA8PrZekLj8erhCvXQdl8nswnQPLLDIuV M8hN3gABQwgd3sqEvyBXTv6+WIcuaISbaqlSwqh39stTflbBiL1Sr7VawD6//jFBltpA IBFNQLDlvlf0QjSOW5Z57F9HyCDGsH3bkvaXtgEn88NU/88dgCtqytAneP6l3ySzInTZ EPqS3rpdi19FJwHv2qRpcVg8jbvJZczoJdkYB7r4wvukq/yUQguXdD6xbSBNXz25bBW+ aDwLqV1t2ND3VabEq9dyLFFhXJeS1rfTvkYs65BPfGWoKKwcIxkfMU7Y/DieRqMA1AfC Ng==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18] (may be forged)) by m0050102.ppops.net-00190b01. with ESMTP id 37htnsm6pr-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <trans@ietf.org>; Sun, 28 Mar 2021 21:23:11 +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 12SKJOo4027839 for <trans@ietf.org>; Sun, 28 Mar 2021 16:23:09 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.57]) by prod-mail-ppoint1.akamai.com with ESMTP id 37j01ybqnm-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <trans@ietf.org>; Sun, 28 Mar 2021 16:23:09 -0400
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com (172.27.123.105) by usma1ex-dag1mb4.msg.corp.akamai.com (172.27.123.104) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sun, 28 Mar 2021 16:23:09 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb5.msg.corp.akamai.com (172.27.123.105) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sun, 28 Mar 2021 16:23:09 -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; Sun, 28 Mar 2021 16:23:08 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: "trans@ietf.org" <trans@ietf.org>
Thread-Topic: duplicate 0x0403 in signature scheme registry
Thread-Index: AQHXJBAqA2znVXZUyECcvT9HmadRTw==
Date: Sun, 28 Mar 2021 20:23:08 +0000
Message-ID: <1E0248E8-A269-4C00-A0CA-60D4F89639A4@akamai.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_1E0248E8A2694C00A0CA60D4F89639A4akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-03-28_12:2021-03-26, 2021-03-28 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=811 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-2103280155
X-Proofpoint-ORIG-GUID: 7HWrK_EX3EZKjC6xLC6MlYhX3OSWzD71
X-Proofpoint-GUID: 7HWrK_EX3EZKjC6xLC6MlYhX3OSWzD71
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-03-28_12:2021-03-26, 2021-03-28 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 clxscore=1015 adultscore=0 mlxscore=0 spamscore=0 impostorscore=0 mlxlogscore=743 lowpriorityscore=0 priorityscore=1501 phishscore=0 bulkscore=0 suspectscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2103250000 definitions=main-2103280155
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/mNPW1xqVhtuy0QG6VlTC9IiP5eM>
Subject: [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: Sun, 28 Mar 2021 20:23:17 -0000

>Section 10.3
>
>I'm confused by this registry.  Is the SignatureScheme value required to
>come from/match the TLS SignatureScheme registry?  Is anything going to
>key off that value or otherwise use the value in a protocol data
>structure?  (Why are there two entries for 0x0403?)

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

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

v2.23.0 | Report a Bug | By Email