RE: [security-jc] adding WSS to the JC

["Karl F. Best" <karl.best@oasis-open.org>]

Joe:

> I suspect that this was simply not completely thought out -

That's probably a good assessment.

> so the right
> action is to clarify the text of clause (o) so that it is
> in line with a
> more flexible mechanism for TCs to join and exit JCs.

Yes, we need to do some more work on this.

</karl>
=================================================================
Karl F. Best
OASIS - Director, Technical Operations
+1 978.667.5115 x206
karl.best@oasis-open.org  http://www.oasis-open.org


> -----Original Message-----
> From: PATO,JOE (HP-PaloAlto,ex1) [mailto:joe_pato@hp.com]
> Sent: Saturday, October 05, 2002 4:54 PM
> To: 'Darran Rolls'; 'Karl F. Best';
> 'security-jc@lists.oasis-open.org'
> Subject: RE: [security-jc] adding WSS to the JC
>
>
> Darran & Karl,
>
> I think it makes perfect sense to proceed this way, but I
> also think that
> clause (o) should be cleaned up. In particular, the text says:
>
> >>Membership in a JC after its first meeting shall be
> governed by the same
> rules governing membership in a TC, with the added
> requirement that any
> prospective member of a JC must first be a member of a
> liaison subcommittee
> appointed for this purpose by one of the *cooperating TCs*.
>
> Members come from the *cooperating TCs* which are
> identified earlier as
> being the list of TCs that formed the JC. I see nowhere in
> the text how a
> new TC is admitted to the JC.
>
>
> Secondly, Darran states that when a TC drops out of the JC
> it does not cause
> the JC to collapse. However the text of clause (o) clearly states:
>
> >>If a still-existing TC in breach of its obligation to
> contribute to a JC
> fails to appoint a liaison subcommittee within the time
> stated, then all
> activities and mailing lists of that JC shall cease until
> its successor, if
> any, can be organized according to the provisions for starting a JC.
>
>
> There are no provisions in clause (o) for a "still
> existing" TC to be
> removed from the JC. Failure to participate by a member TC
> is clearly
> spelled out - and the TC has a time limit within which it
> must repair its
> participation. If it does not (and presumably one who
> wishes to drop out
> will not), the JC is dissolved.
>
> I suspect that this was simply not completely thought out -
> so the right
> action is to clarify the text of clause (o) so that it is
> in line with a
> more flexible mechanism for TCs to join and exit JCs.
>
> I do not, however, believe that any and all TCs should be
> eligible to join a
> JC.
>
> - joe
>
> -----Original Message-----
> From: Darran Rolls [mailto:Darran.Rolls@waveset.com]
> Sent: Saturday, October 05, 2002 7:43 AM
> To: Karl F. Best; security-jc@lists.oasis-open.org
> Subject: RE: [security-jc] adding WSS to the JC
>
>
> Karl
>
> Thanks for the clarification.  I think it's also worth
> pointing out to
> the current JC members that the perceived "if a TC pulls
> out we have to
> collapse the JC..." is not a part of the new process.  In
> summary, our
> JC is governed by pretty much the same rules as a TC with regard to
> participation.  The JC chair has a little more "weight"
> when it comes to
> nudging a TC->JC liaisons that their participation is lacking.
> Otherwise...
>
> I've added a link to the coordination section of the
> process document
> from the membership section of the JC site.
>
> --------------------------------------------------------
> Darran Rolls                      http://www.waveset.com
> Waveset Technologies Inc          drolls@waveset.com
> (512) 657 8360
> --------------------------------------------------------
>
>
> > -----Original Message-----
> > From: Karl F. Best [mailto:karl.best@oasis-open.org]
> > Sent: Thursday, October 03, 2002 1:14 PM
> > To: security-jc@lists.oasis-open.org
> > Cc: klawrenc@us.ibm.com; ckaler@microsoft.com
> > Subject: [security-jc] adding WSS to the JC
> >
> > JC members:
> >
> > I looked again at the TC Process to see if it says anything about
> > adding new members to an existing JC. It does:
> >
> > http://www.oasis-open.org/committees/process.shtml#coordination
> >
> > "Membership in a JC after its first meeting shall be
> governed by the
> > same rules governing membership in a TC, with the added
> requirement
> > that any prospective member of a JC must first be a member of a
> > liaison subcommittee appointed for this purpose by one of the
> > cooperating TCs."
> >
> > I would interpret this to say that *any* OASIS TC can join the JC
> > simply by selecting liaison members and notifying the JC
> chair that
> > they would like to become JC members. The usual
> probationary period
> > would apply to the new members.
> >
> > So, the WSS co-chairs should simply notify the JC chair
> that they have
> > selected liaisons, and those liaisons should become voting members
> > after 60 days or three meetings.
> >
> >
> > </karl>
> > =================================================================
> > Karl F. Best
> > OASIS - Director, Technical Operations
> > +1 978.667.5115 x206
> > karl.best@oasis-open.org  http://www.oasis-open.org
> >
> >
> > ----------------------------------------------------------------
> > To subscribe or unsubscribe from this elist use the subscription
> > manager: <http://lists.oasis-open.org/ob/adm.pl>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>