Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Would be nice to see TLS 1.3 in version 12, now that Domino v11 has come and gone.
TLS1.3 and/or HTTP/2 (or even QUIC) makes any HTTP server respond faster (end-to-end).
This is a cheap low-hanging fruit...
[ Toni Feric, Belsoft Collaboration ]
Fully agree: modern standards should be implemented asap!
HCL, please stop IBM's low performance.
Be ahead this time. We all remember POODLE
I wish I could vote for this 11 times. This kind of thing is critical to Domino's image as a secure product.
Version 11 is definitely to late. Version 10 or 9 would be good
Clients wants to introduce TLS v1.3 protocol and will be using it as the only supported protocol.
Their dedicated NotesClient on the Archiving Bridge host uses currently the version 901FP8SHF244.
Their End-user-clients can use any NotesClient version e.g. 901FP10.
They want 901FPxx-NotesClient to support TLS v1.3(basically client and Domino)
This is necessary so that IBM/HCL don’t find themselves in another embarrassing POODLE situation like with SSLv3 (where for years TLS was rejected as being needed as SSLv3 was deemed sufficient by IBM). Domino should be leading the way in security.
I agree. Slowness to adopt TLS 1.3 is not good for the image of the product. It would help if it could be seen as on top of such changes.