This is the public portal for all IBM Z Hardware and Operating System related offerings. 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.
Cloud service providers can provide multiple instances of the same service behind an ingres node that can be addressed by specifying their individual virtual host names for each instance in the SNI headers (server name indicator).
Multiple virtual host names (each representing a different service or instance) can resolve to the same IP address. Each virtual host name however can also resolve to multiple IP addresses if load requires to provide multiple service nodes.
AT-TLS allows specification of SNI headers when initiating outgoing connections through ClientHandshakeSNIList. This ClientHandshakeSNIList can be activated for example for a specific RemoteAddr. However it is not possible to connect to different virtual hosts at the same RemoteAddr with different SNI headers if there is no other unique identifier (like different remote or local ports).
Since the original host name is no longer available in the filtering done by AT-TLS (based on IP address and port), the target SNI needs to be passed by the application when the connection is initiated and the socket is created.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
When using AT-TLS for CICS outbound connections we found that there was no way to distinguish between connections for different virtual host to the same cloud services provider from the same CICS region (i.e. jobname). CICS TS 5.6 provided SNI support so we have stopped using AT-TLS because it is of no use for this kind of connection unless this enhancement is implemented.