HPKE codepoint and don't jump the gun on IETF recommendations

dconnolly · Oct 20, 2024 · 6c4363a · 6c4363a
1 parent 0b34cad
commit 6c4363a
Showing 1 changed file with 8 additions and 3 deletions.
diff --git a/draft-connolly-cfrg-xwing-kem.md b/draft-connolly-cfrg-xwing-kem.md
@@ -543,7 +543,7 @@ This document requests/registers a new entry to the "HPKE KEM Identifiers"
 registry.
 
  Value:
- : TBD (please)
+ : 26287 (0x66af, please)
 
  KEM:
  : X-Wing
@@ -571,7 +571,7 @@ Named Group (or Supported Group) registry, according to the procedures
 in {{Section 6 of TLSIANA}}.
 
  Value:
- : 26287 (please)
+ : 26287 (0x66af, please)
 
  Description:
  : X-Wing
@@ -580,7 +580,7 @@ in {{Section 6 of TLSIANA}}.
  : Y
 
  Recommended:
- : Y
+ : N
 
  Reference:
  : This document
@@ -663,6 +663,11 @@ TODO acknowledge.
   in both cases is 832, which gives a security of 416 bits. It does require
   less thought from anyone analysing X-Wing in a rush.
 
+- Add HPKE codepoint.
+
+- Don't mark TLS entry as recommended before it has been through the
+  IETF consensus process. (Obviously the authors recommend X-Wing.)
+
 ## Since draft-connolly-cfrg-xwing-kem-03
 
 - Mandate ML-KEM encapsulation key check, and stipulate effect