Hi Experts,
The customer is CHARGEX from Germany, and they are currently developing an EVSE communication controller targeting the ISO 15118-20 (V2G) standard. Their host MCU communicates via I2C with the EdgeLock SE050E (Specific OPN: SE050E2HQ1/Z01Z3Z, running IoT Applet 7.2).
They are attempting to implement "Cipher Suite 2" requirements, which necessitate 448-bit Edwards curves. However, they have encountered a discrepancy between the SE050E marketing documentation and the provided Plug & Trust middleware (Simw-top) headers, and we need clarification on the hardware's exact capabilities.
Application Note AN13014 states that the SE050E and SE051 add "support for Edwards Curve448." However, looking at the middleware header se05x_enums.h, only definitions for the Montgomery form for key exchange (kSE05x_ECCurve_ECC_MONT_DH_448 = 0x43) and no definitions for Ed448 EdDSA signing.
Is this a doc issue here? I also find https://www.nxp.com.cn/docs/en/application-note/AN13645.pdf which states "EdgeLock SE05x supports ECC keys with future proof curves and high key length:
Brainpool (160 to 512 bits), NIST (192 to 521 bits), Edwards (curve 25519 and curve
448), Montgomery (curve 25519 and curve 448) and Koblitz (160 to 256 bits).", but both the APDU spec and SE05x configuration (https://www.nxp.com.cn/docs/en/application-note/AN12973.pdf https://www.nxp.com.cn/docs/en/application-note/AN12436.pdf ) just have Montgomery (curve 25519 and curve 448) supported.
Please kindly clarify.
Best Regards,
Kan
Hi @nxg11900 ，
Thanks for the clarification! I will share this info with the customer.
Have a great day!
Best Regards,
Kan
Hi Kan,
we don't support Edwards Curve448. this is documentation error in 2 docs and we will update the docs. and in An13014 it is support for Montgomery curve 448 which is added and not edwards curve 448. We willl correct this in doc
kind regards,
Parth