[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [security-services] RE: Minutes for Telecon, Tuesday 30 Septe mber2003
Rob, Sorry I take exception to a any co-chair making statements like Prateek has done, this is clearly a political action on his part, this uncalled for. As far as the changes to the charter wording like "Addressing issues and enhancement requests that have arisen from experience with real-world SAML implementations and with standards architectures that use SAML, such as the OASIS WSS and XACML work." does not clarify anything just mystifies things. "Adding support for features that were deferred from previous versions of SAML for schedule reasons, such as session support, the exchange of metadata to ensure more interoperable interactions, and collection of credentials" is far to open. I suggest that the TC have a clear and precise list of "features" so the charter can address these as this leaves it wide open and does not clarify anything just mystifies things. Also the statement "Converging on a unified technology approach for identity federation by integrating the specifications contributed to the TC by the Liberty Alliance" seems like scope creep to me as I don't see anything in the charter about "federation" as federation goes way beyond authentication. So I don't see the updates above clarifying anything, I have no problem with the changes that clarify the dates or clarifying that additional profile documents will be produced. Anthony Nadalin | work 512.436.9568 | cell 512.289.4122 |---------+----------------------------> | | "Philpott, | | | Robert" | | | <rphilpott@rsasec| | | urity.com> | | | | | | 10/01/2003 08:29 | | | PM | |---------+----------------------------> >----------------------------------------------------------------------------------------------------------------------------------------------| | | | 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 | >----------------------------------------------------------------------------------------------------------------------------------------------| 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.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]