IBM Z Software
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).
Shape the future of IBM!
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:
Search existing ideas
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 your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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.
IBM does not intend to implement this in the foreseeable future.
We recently reviewed the RFE related to having multiple server certificates for a single HTTP server / port. One of the reasons this became important in the distributed world is because having a separate HTTP or Apache server would require an entire separate long running process. So, on say a Linux system, having three separate server certificates required resources for 3 different HTTP server processes and the resources those servers would consume. So this really became a problem of resource consumption on a given server platform.
However, in TPF this is not an issue. Creating a separate server listening on its own IP address does not consume any resources at all. In fact, a long running process wouldn't even exist. So, the need for having a single TPF server with the ability to define multiple server certificates becomes less important.
In addition, this is not a trivial effort for us to implement and there is concern about the performance implications this change may have. Today, we read in the server certificate as part of the CTX created for the server, so this is done once at server startup. The performance concern is the model would have to change to read in the correct certificate each time a new session is started to the server. Meaning we cannot pre-read the certificate for a given server, because that server can technically handle multiple certificates. This would require us to go down to the file system for SSL session created to the server, which would have a significant performance impact.
The lab believes the better solution for this is having multiple HTTP server processes listening on their own IP address (can be the same port but doesn't have to). Each of these IP addresses defined for HTTP would correspond to a particular hostname being accessed on TPF. This way you don't have multiple host names resolving to the same TPF IP address. Hostname sha.svcs.entsvcs.net would resolve to VIPA 1 on TPF and hostname shares.ual.com would resolve to VIPA 2. A separate server would be defined for each and those servers would be listening on port 443 but listening on a specific IP address for each hostname.