- From: Ben Wilson <ben@digicert.com>
- Date: Tue, 27 Apr 2010 16:44:55 -0600
- To: "'Bajaj, Siddharth'" <SBajaj@verisign.com>, "'McClure, Allan H.'" <amcclure@mitre.org>, "'Thomas Hardjono'" <hardjono@MIT.EDU>, "'Shan, Jeff'" <JShan@etrade.com>, <gpercivall@opengeospatial.org>, <rsingh@opengeospatial.org>, <public-xg-mashssl@w3.org>, "'Ravi Ganesan'" <ravi@findravi.com>
- Message-ID: <011b01cae65b$42042220$c60c6660$@com>
Regarding my assignment to work on the IPR Statement, as assigned below, I've looked at the W3C's web site, and I didn't see much in the way of any IPR Policy sections in reports. However, I did come across this guidance-- <http://www.w3.org/2005/07/13-pubrules-src.html> http://www.w3.org/2005/07/13-pubrules-src.html. >From the above, here is an example: Copyright C YYYY ...copyright holder information .... This document is available under the <http://www.w3.org/Consortium/Legal/copyright-documents> W3C Document License. See the W3C <http://www.w3.org/Consortium/Legal/ipr-notice#Copyright> Intellectual Rights Notice and Legal Disclaimers for additional information. Copyright C YYYY W3CR (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark document use rules apply. Moreover, under "Status of this Document" some Reports have said, "Incubator Groups have as a goal to produce work that can be implemented on a Royalty Free basis, as defined in the W3C Patent Policy. Participants in this Incubator Group have made no statements about whether they will offer licenses according to the licensing requirements of the W3C Patent Policy for portions of this Incubator Group Report that are subsequently incorporated in a W3C Recommendation." This is consistent with the Charters for Incubator Groups that also contain this Royalty-Free licensing language. Do we need to have anything more than these statements? Ben Copyright C YYYY ...copyright holder information .... This document is available under the W3C Document <http://www.w3.org/Consortium/Legal/copyright-documents> License. See the W3C Intellectual <http://www.w3.org/Consortium/Legal/ipr-notice#Copyright> Rights Notice and Legal Disclaimers for additional information. Copyright <http://www.w3.org/Consortium/Legal/ipr-notice#Copyright> C YYYY <http://www.w3.org/> W3CR ( <http://www.csail.mit.edu/> MIT, <http://www.ercim.eu/> ERCIM, Keio <http://www.keio.ac.jp/> ), All Rights Reserved. W3C liability <http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer> , trademark <http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks> document use <http://www.w3.org/Consortium/Legal/copyright-documents> rules apply. From: public-xg-mashssl-request@w3.org [mailto:public-xg-mashssl-request@w3.org] On Behalf Of Bajaj, Siddharth Sent: Monday, April 12, 2010 7:42 PM To: Bajaj, Siddharth; McClure, Allan H.; Thomas Hardjono; ben@digicert.com; Shan, Jeff; gpercivall@opengeospatial.org; rsingh@opengeospatial.org; public-xg-mashssl@w3.org; Ravi Ganesan Subject: Updated XG Report Outline with assignments - Introduction (Siddharth) + Motivation - Use Cases/Scenarios (Siddharth) + 3-party generic scenario + 2-party generic scenario + Real-world use cases - map the generic scenario to a couple of real world use cases - Solution Overview (Ravi) - Detailed protocol specification (Ravi) + Client Hello + Server Hello + Client Key Exchange + Server Finished - Abbreviated Handshake/optimizations (Ravi) - Extension points (maybe this is part of the protocol spec above). - Leveraging Existing Trust Framework (Ben) + Discussion on different forms of certificates - Leveraging MashSSL for other protocols (need to discuss) + OpenID + OAUTH + Encryption - Implementation Considerations - Security Considerations - Acknowledgements (Ben) - Author/Editor information - IPR statement (Ben) - Appendix + Definition of terms (Ben) + References (Ben)
Received on Tuesday, 27 April 2010 22:40:40 UTC