IBM J9's cipher suites are all prefixed with "SSL_" . This is different than the standard JSSE cipher suite names  which generally follow the cipher names as defined in their respective RFCs. J9's custom naming convention for ciphers necessitates that applications which want to run on J9 and other JVM implementations must account for this custom naming convention.
FWIW this may have originated from the following text in the standard JSSE cipher suite names :
> The following list contains the standard JSSE cipher suite names. Over time, various groups have added additional cipher suites to the SSL/TLS namespace. Some JSSE cipher suite names were defined before TLSv1.0 was finalized, and were therefore given the
SSL_ prefix. The names mentioned in the TLS RFCs prefixed with
TLS_ are functionally equivalent to the JSSE cipher suites prefixed with
However my interpretation of this statement doesn't allow JVM implementations to required the "SSL_" prefix for all ciphers and push this naming convention on applications. The JVM should be allowed to accept "SSL_" prefixed ciphers but should also handle the "TLS_" ciphers as defined in the JSSE cipher suite names  and the respective TLS RFCs .
Can someone from IBM J9's team clarify the following:
- rational behind the custom cipher names and expected implications on applications which run on JVMs other than J9
- if support can be added for standard cipher names (I'm assuming support for existing "SSL_" prefix wouldn't be impacted)
For additional application layer context see .