Rename P256-M when we add P-384 support #734

Open
opened 2026-03-30 07:56:54 -05:00 by davidhorstmann-arm · 0 comments
davidhorstmann-arm commented 2026-03-30 07:56:54 -05:00 (Migrated from github.com)

When we add support for P-384 to the P256-M driver, its existing name is likely to become a source of tremendous confusion for users.

As such, we should probably rename it. This task involves the following steps:

  1. Decide on a new name. Appropriate levels of discussion and bikeshedding are encouraged, but final say is given to @mpg as the original author or P256-M
  2. Perform the renaming operation. This is probably easiest either before or after the rest of the P-384 support work to avoid conflicts.
When we add support for P-384 to the P256-M driver, its existing name is likely to become a source of tremendous confusion for users. As such, we should probably rename it. This task involves the following steps: 1. Decide on a new name. Appropriate levels of discussion and bikeshedding are encouraged, but final say is given to @mpg as the original author or P256-M 2. Perform the renaming operation. This is probably easiest either before or after the rest of the P-384 support work to avoid conflicts.
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gh-Mbed-TLS/TF-PSA-Crypto#734
No description provided.