Skip to content

Change of PAKE extension status to REL/Final#160

Merged
athoelke merged 1 commit intoARM-software:mainfrom
athoelke:pake-prep-rel.0
Jan 31, 2024
Merged

Change of PAKE extension status to REL/Final#160
athoelke merged 1 commit intoARM-software:mainfrom
athoelke:pake-prep-rel.0

Conversation

@athoelke
Copy link
Copy Markdown
Contributor

Following review of a proof-of-concept implementation of the Beta-2 API specification, I would like to change the status of the PAKE API to 'final'/'release'. This will make the PAKE API subject to the same change control as the main Crypto API specification.

  • Update the configuration for 'Final' status (RC2)
  • Update references to the status
  • Update description of the API status throughout the document
  • Update the introduction text relating to the adoption of J-PAKE and SPAKE2+

Fixes #93

* Update the configuration for 'Final' status (RC2)
* Update references to the status
* Update description of the API status throughout the document
* Update the introduction text relating to the adoption of J-PAKE and SPAKE2+
@athoelke athoelke added Crypto API Issue or PR related to the Cryptography API publication Related to the publication process labels Jan 30, 2024
@athoelke athoelke self-assigned this Jan 30, 2024
@athoelke
Copy link
Copy Markdown
Contributor Author

@silabs-Kusumit, @silabs-hannes, @oberon-sk, @yanesca: please let me know if you approve the change of status for this API.

@oberon-sk
Copy link
Copy Markdown

lgtm, thanks!

@silabs-Kusumit
Copy link
Copy Markdown

LGTM

@yanesca
Copy link
Copy Markdown
Contributor

yanesca commented Jan 31, 2024

Looks good to me

@athoelke athoelke merged commit 71bb75d into ARM-software:main Jan 31, 2024
@athoelke athoelke deleted the pake-prep-rel.0 branch January 31, 2024 13:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Crypto API Issue or PR related to the Cryptography API publication Related to the publication process

Projects

Development

Successfully merging this pull request may close these issues.

Update to the PAKE API - should this remain a Beta?

4 participants