RE: [security-services] RE: Minutes for Telecon, Tuesday 30 Septe mber 2003

["Philpott, Robert" <rphilpott@rsasecurity.com>]

Folks, let's please stop discussing motivations, etc.

Tony, as I stated in a separate message, the chairs believe we are operating
within the TC process and that the TC is clearly free to modify our charter
per that process. If you believe we are not entitled to make such changes or
believe there is ambiguity in the TC process that needs to be clarified,
then would you please take that up with TC Administration and off this list?

This co-chair took an action item to draft proposed charter clarifications,
which I've done.  If you have specific comments on the proposed
clarifications, I encourage you to please make them known to this list.  If,
following debate on those items, you wish to vote against the charter
change, please make sure to attend the next meeting where that vote will be
on the agenda.

Rob Philpott 
RSA Security Inc. 
The Most Trusted Name in e-Security 
Tel: 781-515-7115 
Mobile: 617-510-0893 
Fax: 781-515-7020 
mailto:rphilpott@rsasecurity.com 


> -----Original Message-----
> From: Anthony Nadalin [mailto:drsecure@us.ibm.com]
> Sent: Wednesday, October 01, 2003 8:28 PM
> To: oasis sstc (E-mail)
> Subject: RE: [security-services] RE: Minutes for Telecon, Tuesday 30 Septe
> mber 2003
> 
> 
> 
> 
> 
> Prateek,
> You have twisted/ misunderstood the issue, I did NOT indicate that the
> work
> in the SS-TC was NOT valuable/required and did NOT indicate that IBM did
> NOT support the work in the SS-TC  but there are rules to follow in OASIS
> and I'm pointing out these rules. Is there a problem in doing so or are we
> NOT supposed to do this ?
> 
> Are there reasons why you would not want to create a new charter (per
> rules) for the new work that goes beyond the scope of the original charter
> ? Maybe you can clarify as I think its valuable to make sure that everyone
> has a equal chance to participate in the formation of specifications in an
> open standards body.
> 
> I also want to understand you statement "your statement has been made on a
> public forum and therefore available to press and analysts, I wanted to
> confirm with you before calling further attention to it in the broader
> media" as I think that this is not the proper behavior for an OASIS
> co-chair !
> 
> 
> Anthony Nadalin | work 512.436.9568 | cell 512.289.4122
> 
> 
> |---------+---------------------------->
> |         |           "Mishra, Prateek"|
> |         |           <pmishra@netegrit|
> |         |           y.com>           |
> |         |                            |
> |         |           10/01/2003 11:00 |
> |         |           AM               |
> |---------+---------------------------->
>   >-----------------------------------------------------------------------
> -----------------------------------------------------------------------|
>   |
> |
>   |       To:       Anthony Nadalin/Austin/IBM@IBMUS, "oasis sstc (E-
> mail)" <security-services@lists.oasis-open.org>
> |
>   |       cc:
> |
>   |       Subject:  RE: [security-services] RE: Minutes for Telecon,
> Tuesday 30 Septe       mber 2003
> |
>   >-----------------------------------------------------------------------
> -----------------------------------------------------------------------|
> 
> 
> 
> 
> 
> Hmmm, I don't really get this:
> 
> [quote]
> 
> > Rob to draft charter changes
> I will have to object to this Action Item as the SS-TC needs to re-charter
> from scratch since they have completed their original deliverables. The TC
> process states this at:
> http://www.oasis-open.org/committees/process.php#closing.
> 
> [end-quote]
> 
> So is it IBM's official position that the SSTC should be dissolved and the
> SAML effort halted?
> 
> As your statement has been made on a public forum and therefore available
> to
> press and analysts, I wanted to confirm with you before calling further
> attention to it in the broader media.
> 
> 
> Thanks,
> 
> Prateek Mishra
> Co-Chair, SSTC
> Netegrity
> 
> 
> 
> To unsubscribe from this mailing list (and be removed from the roster of
> the OASIS TC), go to http://www.oasis-
> open.org/apps/org/workgroup/security-services/members/leave_workgroup.php.