Change Reference of ECDH Key Encoding to IETF document

[janklaussner]

Russ on IETF LAMPS 09.03.2026:

I am concerned with this paragraph:

• ECDH: public key MUST be encoded as an uncompressed X9.62
  [X9.62_2005], including the leading byte 0x04 indicating
  uncompressed. This is consistent with the encoding of ECPoint as
  specified in section 2.2 of [RFC5480] when no ASN.1 OCTET STRING
  wrapping is present. The private key MUST be encoded as
  ECPrivateKey specified in [RFC5915] with 'NamedCurve' parameter
  set to the OID of the curve, but without the 'publicKey' field.
  The ciphertext MUST be encoded in the same manner as the public
  key.

The MUST statement refers to [X9.62_2005], which is not a readily available specification.

I suggest that the MUST statement point to Section 2.2 of [RFC5480], and then provide an informative statement that it is consistent with [X9.62_2005]. In this way, all normative references are publicly available.

[janklaussner]

further comments from Russ:

• Unused Reference to 'Aviram22'; please remove it.
• Obsolete informational reference to RFC 4210; it is Obsoleted by RFC 9810.
• Obsolete informational reference RFC 5990; it is Obsoleted by RFC 9690.
• Reference to RFC 8411 should be informative, not normative.