throbber
4/29/2021
`
`Planetlab: Consortium
`
`The Wayback Machine - https:/ /web.archive.org/web/20061007234024/http://www.planet-lab.org/consorti .. .
`I
`I
`
`Login
`
`p A NET AB
`
`An open ploriorm for developing, depl.oying~ o·nd access ing planet.a ry-sc:o le services
`
`About I Status I Contact Us
`
`Community
`Consortium
`Institutions
`Projects
`Working Groups
`Mailing Lists
`Courseware
`Meetings
`
`Joining
`Institutions
`Users
`Acceptable Use Policy
`
`News
`Press Releases
`Links
`Historical Timeline
`
`Documentation
`Design Notes (PDNs)
`Annotated Bibliography
`Guides
`FAQ
`Presentations
`Wiki
`
`Software
`Services
`User Tools
`Roadmap
`Download
`CVS
`
`Planetlab Consortium
`
`The PlanetLab Consortium is a collection of academic, industrial, and government
`institutions cooperating to support and enhance the PlanetLab overlay network. It is
`responsible for overseeing the long-term growth of PlanetLab's hardware
`infrastructure; designing and evolving its software architecture; providing day-to-day
`operational support; and defining policies that govern appropriate use.
`
`Institutions join the Consortium by signing a membership agreement and connecting
`two or more nodes to the PlanetLab infrastructure. Individuals that want to use
`PlanetLab should arrange to do so through their home institution.
`
`The PlanetLab Consortium is managed by Princeton University, the University of
`California at Berkeley, and the University of Washington. Princeton currently hosts
`the Consortium. Larry Peterson currently serves as the Consortium's Director. A
`Governance Document describes how the Consortium is organized. This page
`highlights the main points.
`
`Steering Committee
`
`A Steering Committee sets the overall policy and provides strategic guidance and
`review of the Consortium's activities. The Steering Committee currently includes the
`following members:
`
`• Tom Anderson, University of Washington (chair)
`• Jon Crowcroft, Cambridge University
`• David Culler, University of California at Berkeley
`• Rick McGeer, HP Labs
`• Larry Peterson, Princeton University
`• Timothy Roscoe, Intel Research
`
`Staff
`
`The Consortium employs a support staff that is responsible for providing operational
`stability of the PlanetLab infrastructure; developing, hardening, and deploying
`software that enables the research community to contribute to PlanetLab; pushing
`the PlanetLab architecture with an eye towards longevity; and promoting continued
`growth of the PlanetLab infrastructure and community. The staff includes:
`
`• Princeton University
`o Faiyaz Ahmed
`o Andy Bavier
`o Marc Fiuczynski
`o Mark Huang
`o Tony Mack
`o Reid Moran
`
`https://web.archive.org/web/20061007234024/http://www.planet-lab.org/consortium/overview.php
`
`1/3
`
`Microsoft Ex. 1030, p. 1
`Microsoft v. Daedalus Blue
`IPR2021-00832
`
`

`

`4/29/2021
`
`Planetlab: Consortium
`
`Policies
`
`The Planetlab Consortium currently publishes three policy documents. Institutions
`that join Planetlab agree to abide by these policies.
`
`• Hosting a Node: This documents outlines the responsibilities of a site that
`hosts Planetlab nodes. All Consortium members (except at the Sponsor level)
`are expected to host Planetlab nodes.
`
`• Accegtable Use Policy:: This document outlines permitted uses of Planetlab,
`and the role each site plays in enforcing these rules.
`
`• Mission and Goals: This document is a statement of the Consortium's mission
`and goals. It is an evolving document that communicate's the Steering
`Committee's vision for Planetlab to the membership.
`
`Membership
`
`The Consortium includes five membership levels, as summarized below. See the
`Governance Document for full details.
`
`• Charter ($300k annual dues)
`o Permanent seat on Steering Committee.
`o Unlimited number of slices.
`o Access to Planetlab events, research papers, and working groups.
`• Full ($75k annual dues)
`o Rotating seat on Steering Committee.
`o 10 slices.
`o Access to Planetlab events, research papers, and working groups.
`• Associate ($25k annual dues)
`o 2 slices.
`o Access to Planetlab events, research papers, and working groups.
`• Sponsor ($10k annual dues)
`o Access to Planetlab events and research papers.
`• Academic (no annual dues)
`o Seat on Steering Committee by invitation.
`o 10 slices.
`o Access to Planetlab events, research papers, and working groups.
`
`Current corporate members include:
`
`Intel, Charter
`•
`• Hewlett Packard, Charter
`• Google, Full
`• AT&T, Associate
`• France Telecom, Associate
`• AT Corporation, Associate
`• NEC Laboratories, Associate
`• Telecom Italia, Associate
`
`The full list of institutions participating in Planetlab, including Academic institutions,
`can be found here. Planetlab also receives support from the National Science
`Foundation.
`
`Working Groups
`
`The Consortium has established a set of working groups that carry on the technical
`work of the Consortium. Individuals from any member institution are encouraged to
`participate in one or more of these working groups. Click here for information about
`the currently active working groups.
`
`Additional Information
`
`https:l/web.archive.org/web/20061007234024/http:l/www.planet-lab.org/consortium/overview.php
`
`2/3
`
`Microsoft Ex. 1030, p. 2
`Microsoft v. Daedalus Blue
`IPR2021-00832
`
`

`

`4/29/2021
`
`Planetlab: Consortium
`If you have additional questions about the Planetlab Consortium, please send mail to
`info@glanet-lab.org.
`
`Copyright ©2004-2005 Planetlab Consortium
`
`https:l/web.archive.org/web/20061007234024/http:l/www.planet-lab.org/consortium/overview.php
`
`3/3
`
`Microsoft Ex. 1030, p. 3
`Microsoft v. Daedalus Blue
`IPR2021-00832
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket