This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
z/TPF supports public key cryptography keys (RSA-2048) that the industry says will still be valid for more than a decade (until the year 2030). The industry direction is to shift to a newer public key cryptography algorithm, ECC; therefore, we expect that well before 2030 platforms, including, z/TPF will support newer public key algorithms. For these reasons, z/TPF does not plan on adding support for larger RSA keys.
If z/TPF cannot generate the key size we need then we need some way to securely generate and share keys within our enterprise that includes z/TPF. The z/TPF product should have an interface that allows us to do this. Should this be a requirement on it's own?
RSA usage by SSL is to create a session key that is only used for the life of that one session. z/TPF currently supports up to 2048-bit RSA keys which are expected to be usable for another 13 years (until the year 2030). The question becomes once we get closer to 2030, what will be the preferred and most widely used public key crypto algorithm for SSL - will it be RSA with longer keys, or will it be a different standard such as ECC. It is premature at this point to know what the needed ciphers will be more than a decade in the future.
This is needed for SSL.