RE: [wss] IPR statements up-to-date?

["Srinivas, Davanum M" <Davanum.Srinivas@ca.com>]

Title: RE: [wss] IPR statements up-to-date?

Got a pointer from Tony - Here's IBM's license page:
http://www.ibm.com/ibm/licensing/977Q/2112.shtml

thanks,
dims

-----Original Message-----
From:   Srinivas, Davanum M
Sent:   Tue 6/21/2005 11:13 AM
To:     'wss@lists.oasis-open.org'
Cc:    
Subject:        RE: [wss] IPR statements up-to-date?

Haven't heard from anyone yet. Can the chair(s), please help?

  _____ 

From: Srinivas, Davanum M
Sent: Friday, June 17, 2005 9:04 AM
To: wss@lists.oasis-open.org
Subject: [wss] IPR statements up-to-date?



Hi all,

Can everyone please confirm that the IPR statements are up-to-date on the OASIS WSS TC IPR page? (http://www.oasis-open.org/committees/wss/ipr.php <http://www.oasis-open.org/committees/wss/ipr.php> )

Here's a list of problems that I see.
- In April 2003, Hemma from Verisign and Kelvin from IBM, hinted that there are licenses available (http://lists.oasis-open.org/archives/wss/200304/msg00056.html <http://lists.oasis-open.org/archives/wss/200304/msg00056.html> ). Yet, there is no mention of these on the IPR page.

- Microsoft's last update to the IPR page is dated "January 2003", mentions "pending patents" and that "Microsoft will update this statement if and when such pending patent application(s) issue". Has there been any change in the situation?

- Am specifically interested in what one would have to do specifically for implementing the Interop scenarios for various profiles. Only ContentGuard's statement has this information.

- Can folks please be specific about which patents are in question in any future IPR statements?

Stating the obvious, WS-Security is a major cornerstone for building the web services stack. I hope you agree that open source implementations can/will help increase adoption. At Apache, we are working on Apache WSS4J (no releases yet, may release a milestone/beta soon and there are companies willing to donate/share their code using the Apache incubation process). We are getting some traction for using WSS4J with Apache Axis and we'd like to know what we have to do to conform to everyone's expectations moving forward.

Thanks,
dims

PS: we'd like to avoid the Sender-ID situation (http://www.apache.org/foundation/docs/sender-id-position.html <http://www.apache.org/foundation/docs/sender-id-position.html> )