Calculation of ECC public key from private key

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - z Systems Hardware
Product - z Systems Hardware
Component - Crypto HW

For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - z Systems Hardware
Product - z Systems Hardware
Component - Security / Crypto

Not in plan.

Is this still a requirement?

This is our current understanding of your requirement:
Needed by: October 2017, better June
UDX Solution Acceptable: UDX only as a temporary solution, possible would also be some C-Source that does the job outside the card/ICSF, based on a development contract to deliver a piece of software
- Needed only on mainframe (ICSF) (z13 w/CEX5)
- Only Prime Curve P256 so far
Your comments concerning performance:
For one calculation not more than 400ms, the less the better.
Until Mid 2018 I expect not more than 40 calculations per day.
Until Mid 2019 I expect 5 calculations per minute.
After that is unpredictable, but not more than 10 per second (spread over two physical mainframes).

Based on your schedule, initially we would not be able to provide the support through base z13 MCLs, however another solution path is possible via UDX and we can work with you and the ECCC team in Denmark on the solution until we can make it available in the z13.

One additional comment. You mentioned the following: "Lately somebody told me that not every random number can be a private key for an elliptic curve, but that both private and public key can be generated from a random number, similar to a seed. A solution like this would be possible also."
It is our understanding that the ECC private key is a random number bounded by ECC bit length. Then only after knowing ECC Private key can the ECC Public Key be calculated. Elliptic curve cryptography, consisting of a private key d (a randomly selected integer in the interval [1,n-1]) and a public key Q (where Q=dG).

Sorry for the delay. What month/year do you need the support? Are you open to a UDX as a solution?

Yes, the private key will be created outside the adapter.
It will be provided in the clear.
You can choose the format for the input, maybe a special kind of key token.

As output a CCA ECC public key token would be possible. It can also be a private key token containing private and public key in the clear - if this exists. In this case your function could just complete the input token.
We need to be able to extract the public key part from the token. The public key can also be returned just as a byte array if this is easier for you.

We will create certificates out of the public key under some CA chain later on.

Please let me know your considerations in short time. We need to decide soon if we wait for an adapter or ICSF solution or look for a third party lib to do the job.

Are we correct in understanding that you would like to create your own ECC private key outside the adapter have the adapter create the public key?
If so, will the private key be provided encrypted or in the clear? Do you want the public key returned in a CCA ECC public key token? What is the expected output format?