Hello, everyone, To solve the complex issue caused by the certification, in RFC 7250, it is recommended to use raw public for authentication. However, when using RAW public directly for authentication, identity and public key binding is required. That is, server need to maintain a large table to map the public key and identity. For networks with huge amount of IoT devices, the maintenance of such a huge database might be a challenge issue.
Currently we are thinking to use identity-base public key to solve the issue. Is there any better solution to solve the identity binding issue? Can anyone give us some comments regarding using IBC as raw public key for TLS for massive IoT authentication? Best regards. Haiguang
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
