[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: avoiding conflicting vendor extensions
I don't think we ever settled on a process (as simple as possible!) for avoiding conflict in vendor extensions. How about something like this:
The goal here is not to have the KMIP TC become an extension registry – just to make it simpler for organizations who are creating extensions to have some level of confidence that their enumerations etc don’t conflict with someone else’s. For organizations that are not part of the TC, we can include a short doc in the extensions directory that invites them to send their proposed extensions to the KMIP TC chairs for distribution to the interop team etc in the process above.
What do you think?