Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions schema/cryptography-defs.json
Original file line number Diff line number Diff line change
Expand Up @@ -123,6 +123,21 @@
}
]
},
{
"family": "HPKE",
"standard": [
{
"name": "RFC 9180",
Copy link

Copilot AI Jan 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The RFC name should be "RFC9180" without a space to maintain consistency with the predominant naming pattern used in this file. Most RFC entries use the format "RFCnnnn" without a space, such as "RFC8017", "RFC8032", "RFC7919", "RFC5869", etc.

Suggested change
"name": "RFC 9180",
"name": "RFC9180",

Copilot uses AI. Check for mistakes.
"url": "https://doi.org/10.17487/RFC9180"
}
],
"variant": [
{
"pattern": "HPKE[-{mode}]-{kem}-{kdf}-{aead}",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the modes are well-defined by the RFC, I'd suggest the following pattern:
HPKE[-(mode_base|mode_psk|mode_auth|mode_auth_psk)]-{kem}-{kdf}-{aead}

"primitive": "pke"
}
]
},
Copy link

Copilot AI Jan 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is trailing whitespace after the closing brace and comma. This should be removed to maintain consistent formatting.

Suggested change
},
},

Copilot uses AI. Check for mistakes.
{
"family": "MQV",
"standard": [
Expand Down