Profile

A more urgent question perhaps is what the overlap is between EKMI and the existing W3C XKMS 2.0 standard, Kerberos and WS-Trust. XKMS/XKISS provides all the protocol you need to locate symmetric or public keys from a client application. There is a significant overlap between WS-Trust and XKMS/XKISS. ...

The question seems to be whether a symmetric key infrastructure should be built from the ground up building on specific applications or from the top down working from a master architecture. I have seen both approaches succeed and both approaches fail. >

Well lets try to work together then. We may not be able to share protocols if you are serious about the concern that public key crypto might be broken but you might well find the Private Key Container format useful. The areas of overlap with 1619.3 are likely to be rather wider

It may or it may not be necessary to develop a symmetric key infrastructure designed to meet such a threat model. Neither KEYPROV nor IEEE 1619.3 consider the possibility of public key systems being compromised as part of their threat model so to that extent there is no overlap. Whether or not EKMI ...

It does not appear to me from reading the charter that there is an overlap here with the IETF KEYPROV work which is concerned with the Provisioning of symmetric keys for use as trust anchors. Such provisioning is by necessity a rather specialised process requiring the ability to make us of out of band ...