Spring 2002 Internet2 Member Meeting

1. Spring 2002 Internet2 Member Meeting Internet2 Business Meeting Internet2 Intellectual Property Framework

2. Internet2 Intellectual Property Framework • Development Overview • Experience in Pilot Implementation • Key Elements of the IP Framework • What’s Next?

3. Internet2 Intellectual Property Framework • Development Overview • Experience in Pilot Implementation • Key Elements of the IP Framework • What’s Next?

4. Development Overview • 2001 • April: Board of Trustees Approves Framework Approach and Plan for Development • May – Sept: Initial IP Framework Developed • Input from NPPAC, ISC, Corporate Partners • Informed by Internet2 Middleware Initiative • October: Board of Trustees Approves Internet2 Pilot Intellectual Property Framework and Pilot Implementation.

5. Development Overview • 2002 • Jan – March: Pilot Implementation • April: Internet2 IP Framework approved by Board of Trustees • May – Oct: Implementation

6. Intellectual Property Framework • Supports Internet2 Goals • Addresses Key Organizational Objectives • Based on Principles of Open Access • Comprehensive yet Flexible Implementation

7. Supports Internet2 Goals • Enable new generation of applications • Re-create leading edge R&E network capability • Transfer technology and experience to the global production Internet

8. Addresses Key Objectives • Encourages Innovation and Collaboration • Provides adequate control and protection • Does not create disincentives for participation • Ensures Ability to Access and Use Innovations • Provides appropriate rewards • Precludes wrongful use and exploitation • Avoids excessive costs and complexities

9. Consistent with Internet2 Principles • Maintain and contribute to the accessible, standards-based character of the Internet. • Encourage broadest possible distribution. • Encourage rapid deployment. • Promote further innovation. • Allow collaborators to retain principal voice. • Encourage terms and conditions that reflect contributions of project participants and of Internet2 community.

10. Comprehensive/Flexible Implementation • Comprehensive Application • Internet2 Initiatives and Projects • Flexible Implementation • “COU-like” Statement • Innovators/Participants take responsibility • General rule: IP will reside with members • Multiple Vehicles for Implementation

11. Internet2 Intellectual Property • Development Overview • Experience in Pilot Implementation • Key Elements of the IP Framework • What’s Next?

12. Pilot Implementation • Real Experience with the IP Framework • Internet2 Middleware activity • Extensive interaction with IBM legal staff • Convergence of needs and interests with collegial organizations with regard to Open Source: • Association of University Technology Management • Global Grid Forum • Government Labs • Member Universities • Continued work with counsel to Finalize • Posted on web site.

13. What We Learned • Not Simple. • Background IP requires clarity. • Management Practices are important for Community-Based Projects. • Internet2 ownership of IP may be appropriate. • Modified BSD license becoming an Open Source standard: balances academic tradition with technology transfer goals.

14. What We Learned • Capability for flexible implementations important • Implementation requires integration with Working Group processes • Continued congruence with collegial organizations important • Confidence in approach • Evolutionary process: principles constant yet continued refinement expected

15. Internet2 Intellectual Property Framework • Development Overview • Experience in Pilot Implementation • Key Elements of the IP Framework • What’s Next?

16. IP Developed by Internet2 ProjectsShould: • Maintain and contribute to the accessible, standards-based character of the Internet, and promote appropriate, flexible, and easily administered open source arrangements.

17. IP Developed by Internet2 ProjectsShould: • Where open source or royalty-free arrangements are unworkable, encourage members to make intellectual property developed as part of an Internet2 effort available to UCAID and members of the Internet2 community.

18. IP Developed by Internet2 ProjectsShould: • Terms and conditions should promote further innovation and reflect the contributions of the community and its members to the development of that intellectual property.

19. IP Developed by Internet2 ProjectsShould: • Encourage the broadest possible distribution of the technology. • Encourage rapid deployment of the technology.

20. IP Framework Applicability • Deliverables generated by any activity that has been designated by its participants as an Internet2 activity in accordance with criteria developed by the Internet2 community.

21. IP Framework Applicability • They do not apply where organizations are merely making use of the Internet2 network and associated communications resources (such as the Abilene network), or where participants do not intend the activity to be an Internet2 activity.

22. IP Framework Applicability • Deliverables of Internet2 projects and initiatives must carry a standardized disclaimer shielding Internet2 from liability.

23. IP Framework Process Considerations • Implementation through royalty-free or open source licenses wherever possible • Agreement by participants on the intellectual property approach to be taken before commencing work • Disclosure/Release of IP: obligation for participants – at beginning of project and ongoing. • When open source or royalty-free license approach not practical, IP to be made available to UCAID members on RAND basis.

24. Suggested Standard Internet2 “Open Source” License • “Best of Breed” Hybrid Friendly: Takes a “Revised” BSD-style approach that maximizes freedom for users, companies and research institutions Easy: Has “default” grant-back rights for voluntary improvements for easy management of contributions Flexible: Does NOT force improvements to be Open Source, meaning industry can work with the community, the code or both! Responsible: Requires 3rd parties to mark modified versions as “Modified”

25. What’s Next? • Implementation • Continue to use the IP Framework • Integration with Working Group processes • Develop software distribution models • Continue to “Check” and Validate • How is it working? • Are improvements/changes needed? • Review of evolving best practices, work of collegial organizations. • Evolution of IP Framework • Principles constant • Specific implementation expected to evolve

26. Internet2Intellectual Property Framework • For More Information: • http://www.internet2.edu/members/html/intellectualproperty.html • Comments and Questions? • Jillar@internet2.edu

27. www.internet2.edu