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.
So perhaps the question is, do EKMI and 1619.3 overlap with what already exists? That is probably where a collision is more likely to occur as people build out from existing infrastructures rather than abandon them for a new one.
> -----Original Message-----
> From: Russ Housley [mailto:housley@vigilsec.com]
> Sent: Thursday, April 26, 2007 11:09 AM
> To: Abbie Barbir; Arshad Noor; John Messing
> Cc: Dee Schur; idtrust-sc@lists.oasis-open.org;
> Hannes.Tschofenig@siemens.com; tim.polk@nist.gov;
> hvantilb@visa.com; James Bryce Clark; Terwilliger,Ann;
> Hallam-Baker, Phillip
> Subject: RE: RE: [idtrust-sc] RE: RE: Concerns with OASIS
> EKMI TC charter
>
> That seems to be the case. I hope we still have that belief
> a year or two from now.
>
> Russ
>
> At 10:07 PM 4/25/2007, Abbie Barbir wrote:
> >Unless someone can identify specific areas in which there is an
> >overlap, can we put this issue to bed and carry on with the
> interesting
> >work to which we volunteered to do? Thanks.
>
>