This is an IBM Automation portal for Integration 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.
While we recognise this as something that might be useful, we do not think the development work would be prioritised to implement it. Instead, we would recommend using TLS1.3 where key reset is part of the base protocol, and which is fully supported in MQ and IPT.
Hi Mark,
Is it possible that we have an email discussion quickly? It's going to be easier to discuss a technical implication around that and then we could update the ticket if that's okay.
Key reset will be enabled as part of the TLS 1.3 support that we hope to release for IPT to match other MQ components. It is not likely that we would enable key reset for older protocols/ciphersuites.