Point of clarification on OASIS process

[Arshad Noor <arshad.noor@strongauth.com>]

Jamie/Mary/Dee,

As Robin may have indicated to you all, there is near unanimous
consensus in the EKMI TC (one member withheld his opinion because
he hadn't read the KMIP TC charter yet) that the KMIP TC charter
overlaps the EKMI TC's charter (the meeting notes should be out
as soon as Anil posts them).

While OASIS process may allow the release of any new TC's charter
for discussion, the EKMI TC is, obviously, disappointed that this
new charter was released without any discussion with the EKMI TC
before-hand, to avoid potential embarrassment to EKMI TC members
and OASIS in the public arena.  After all, OASIS EKMI TC members
have only been working on this for 2+ years with laser-like vision
and focus and reached Committee Specification status, while the
IEEE effort has been floundering for lack of vision and the IETF
work is reviewing its own focus as it starts to overlap with the
EKMI work (they are even incorporating some SKSML concepts into
their own schema now).

Now that the cat is out of the bag, the TC is interested in
understanding OASIS policy/process wrt duplicate/overlapping
charters of an existing TC and a potential new TC.  What is
legally possible now?

Do OASIS rules permit the creation of the KMIP TC despite the
near-unanimous consensus amongst EKMI TC members that the KMIP
TC charter overlaps the EKMI TC's?

Your answers will help the EKMI TC in understand what its options
are.

Thank you.

Arshad Noor
StrongAuth, Inc.