Logistics
Roll-call
Other Business
Business In Order
Action Items & Motions
References
| Meeting Date | 09/19/2002 |
| Meeting Time | Time: 12 Noon EDT |
| Location |
Phone: 404-774-4109 Call host: HP |
| Duration | 1 Hour |
| Chair | Phil Griffin |
| Recording Secretary | Darran Rolls |
| Agenda | Agenda available in [1] |
| (PG) | Phil Griffin, Griffin Consulting | OASIS XCBF TC | Present |
| (KB) | Karl Best, OASIS | OASIS | Present |
| (HL) | Hal Lockhart, Entegrity | OASIS XACML TC | Present |
| (JP) | Joe Pato, HP Labs | OASIS SS TC | Present |
| (HR) | Hari Reddy, ContentGuard | OASIS RL TC | Present |
| (MM) | Monca Martin, Certivo | OASIS XCBF TC | Present |
| (DR) | Darran Rolls, Waveset | OASIS PS TC | Present |
| (TH) | Thomas Hardjono, Verisign | OASIS RL TC | Present |
| (CA) | Carlisle Adams, Entrust | OASIS XACML TC | Present |
| PG | None |
| 2 | Voting results on proposed SJC charter |
|
HR
|
May be issues re interpretation of the charter: 1. Is the voting process for the JC majority or consensus based? 2. What is the purpose and status of any "deliverables" from the JC, would member TC's be bound by these document? Does this introduce issues with TC sovereignty? Would the committee consider making clear statement on both of these questions in the charter? |
|
HL
|
Re 1. Majority v consensus. We should strive for consensus but operate on majority. |
|
PG
|
General agreement that all voting on such issues would strive for consensus but operate on majority. |
|
JP
|
Re 2, deliverables. A JC's is not supposed to have any deliverables and if it does they need to be qualified by the member TC's. Any documents/deliverables from the JC would be considered non-normative. |
|
TH
|
Is the reference model mentioned in the charter binding to the TC's in any way? |
|
DR
|
Prior agreement was that it would not be, lets call them "Informational Documents" |
|
JP
|
Re 2. Sovereignty. Suggest using the sovereignty statements from the new TC process document. JP action item to send this to DR for inclusion in an updated charter statement. |
|
HR
|
We should consider producing an FAQ on all this? |
|
CA
|
Seems redundant if we are simple implementing known OASIS policy. |
|
PG
|
General agreement to circulate questions for a possible FAQ section for the web site and to work through the answers on the web site. DR to post to the site when we have something to build upon. |
| PG | General agreement that we would make a clear statement on issues 1 & 2 (above) in an update to the charter and get this ratified by the committee before the next meeting. |
| 3 | Classes of membership & invite letter for other TC's to join the SJC |
| HL | Thought it was assumed that the membership was for TC's that have security as a primary objective or part of their (planned) specifications. How many more "security related TC's" are there likely to be? |
| KB | Another one coming soon. FYI, the new JC process calls for majority of the JC members have to agree to another TC joining a JC. |
| DR | Propose we do not call for participation in the planned letter to TC chairs and instead call for liaisons or observers. |
| KB | JC's have no official provision for observers. |
| DR | At last weeks TAB meeting I took an action item to ask the JC to ask the TAB for a permanent liaison to the SJC. Is this therefore invalid? |
| KB | No, not in that context. This refers to the automatic movement from observer to member based on registration and waiting on three meeting. |
| JP | We should make this directly security related only and invite others as lesions. Concern over our ability to carry out JC business if we have transient involvement from less security targeted TC's. Based on the new OASIS process, if a new TC dropped out we would have to dissolve and re-form the JC. |
| PG | Will hold on sending the "call for involvement" letter proposed in [2] pending further discussion at or prior to the next committee meeting. |
| HL | The membership of the WSS TC should be a given. |
| ALL | The JC agrees to consider admission of TCs into the JC only on the basis of an agreed process that is applied to all TCs, and treats each TC the same. |
| 5 | Motion to adjourn |
| Meeting adjourned at 12:59 EDT to reconvene October 3rd at 12 noon EDT |
| Owner | Action Item | |
| 1 | HL | To create a statement on document status and send to list for inclusion in updated charter. |
| 2 | JP | To send "sovereignty statement" to DR for inclusion in an updated charter statement. |
| 3 | DR | To post an updated charter statement for approval on the list. |
| Motions | ||
| PG | Motion to adjourned and reconvene October 3rd at 12 noon EDT. | Passed unanimously |
[1] http://lists.oasis-open.org/archives/security-jc/200209/msg00014.html
[2] http://lists.oasis-open.org/archives/security-jc/200209/msg00017.html