4/29/2021
`
`About Planetlab I Planetlab
`
`A E.T LAB
`An open platform for developing, deploying, and accessi ng planetary-scale services
`
`About I Status I Support I Documentation I Community I Software
`
`Planetlab
`
`... About
`► Consortium
`o Federation
`o History
`o Impact
`o Sponsors
`o Sites
`o Projects
`
`... Status
`o Security Notice
`o CoMon
`o PlanetFlow
`o MyOps
`
`... Support
`o Site Assistant
`
`... Documentation
`
`► API
`o AUP
`o Bibliography
`o FAQ
`o Tutorial
`o PDNs
`o Guides
`
`... Community
`
`Home
`
`I About Planetlab
`
`There are many facets to PlanetLab. This page outlines
`several of them. In addition to this brief overview, the best
`way to learn about PlanetLab is to read the following three
`papers:
`
`• A Blueprint for Introducing Disruptive Technology
`into the Internet. Larry Peterson, Tom Anderson,
`David Culler, and Timothy Roscoe. Proceedings of the
`First ACM Workshop on Hot Topics in Networking
`(HotNets), October 2002.
`
`• Operating System Support for Planetary-Scale
`Services. Andy Bavier, Mic Bowman, Brent Chun,
`David Culler, Scott Karlin, Steve Muir, Larry Peterson,
`Timothy Roscoe, Tammo Spalink, and Mike
`Wawrzoniak. Proceedings of the First Symposium on
`Network Systems Design and Implementation (NSDI),
`March 2004.
`
`• Experiences Building Planetlab. Larry Peterson,
`Andy Bavier, Marc Fiuczynski, and Steve Muir.
`Proceedings of the Seventh Symposium on Operating
`System Design and Implementation (OSOi),
`November 2006.
`
`The first gives the original vision for PlanetLab, the second
`articulates the design principles that shape its architecture,
`
`Planetlab login
`
`E-mail: *
`I
`
`Password: *
`I
`I Log in I
`
`Forgot your password?
`
`Create an account
`
`I
`
`I
`
`Announcements
`
`o M-Lab answers the question:
`"How fast is my Internet?"
`Measurement-Lab, running
`PlanetLab software on 600 servers
`world-wide, answers 20,000+
`Google querie ...
`o M-Lab Study of ISP
`Interconnection Released
`A Measurement-Lab study of
`o Shellshock bash vulnerability
`Due to the recent Shellshock bash
`vulnerability, slices exposing
`externally accessible interfaces sh ...
`
`https://planetlab.cs.princeton.edu/about.html
`
`1/5
`
`Microsoft Ex. 1026, p. 1
`Microsoft v. Daedalus Blue
`IPR2021-00832
`
`

`

`o Planetlab BootCD updated to
`support latest hardware
`The Planetlab BootCD has been
`updated to use the latest Red Hat
`Enterprise Linux kernel. The new
`ver ...
`o Planetlab Migrating to LXC
`After many years of using Linux
`vserver as Planetlab's node ...
`
`more
`
`4/29/2021
`
`o Courseware
`► Data Sets
`o Mailing Lists
`o Meetings
`o Presentations
`
`..,.. Software
`o Developers
`o Services
`o UserTools
`
`Search
`
`I Search I
`
`About Planetlab I Planetlab
`and the third reports experiences building and operating
`Planetlab. Additional information is available as
`Planetlab Design Notes (PDNs).
`
`A collection of machines distributed over the globe
`Most of the machines are hosted by research institutions,
`although some are located in co-location and routing
`centers (e.g. , on lnternet2's Abilene backbone). All of the
`machines are connected to the Internet. The goal is for
`Planetlab to grow to 1,000 widely distributed nodes that
`peer with the majority of the Internet's regional and long(cid:173)
`haul backbones.
`
`A software package
`All Planetlab machines run a common software package
`that includes a Linux-based operating system;
`mechanisms for bootstrapping nodes and distributing
`software updates; a collection of management tools that
`monitor node health, audit system activity, and control
`system parameters; and a facility for managing user
`accounts and distributing keys. This software is distributed
`as a package, called MyPLC, which others can use to
`build and deploy their own "private Planetlabs."
`
`The key objective of the software is to support distributed
`virtualization-the ability to allocate a slice of Planetlab's
`network-wide hardware resources to an application. This
`allows an application to run across all (or some) of the
`machines distributed over the globe, where at any given
`time, multiple applications may be running in different
`slices of Planetlab.
`
`An overlay network testbed
`One of Planetlab's main purposes is to serve as a testbed
`for overlay networks. Research groups are able to request
`a Planetlab slice in which they can experiment with a
`variety of planetary-scale services, including file sharing
`and network-embedded storage, content distribution
`networks, routing and multicast overlays, QoS overlays,
`scalable object location, scalable event propagation,
`anomaly detection mechanisms, and network
`
`https://planetlab.cs.princeton.edu/about.html
`
`2/5
`
`Microsoft Ex. 1026, p. 2
`Microsoft v. Daedalus Blue
`IPR2021-00832
`
`

`

`4/29/2021
`
`About Planetlab I Planetlab
`measurement tools. There are currently over 600 active
`research projects running on Planetlab.
`
`The advantage to researchers in using Planetlab is that
`they are able to experiment with new services under real(cid:173)
`world conditions, and at large scale. The example services
`outlined above all benefit from being widely distributed
`over the Internet: from having multiple vantage points from
`which applications can observe and react to the network's
`behavior, from being in close proximity to many data
`sources and data sinks, and from being distributed across
`multiple administrative boundaries.
`
`A deployment platform
`In addition to supporting short-term experiments,
`Planetlab is also designed to support long-running
`services that support a client base. That is, rather than
`view Planetlab strictly as a testbed, we take the long-term
`view in which the overlay is both a research testbed and a
`deployment platform, thereby supporting the seamless
`migration of an application from early prototype, through
`multiple design iterations, to a popular service that
`continues to evolve.
`
`Using an overlay as both a research testbed and a
`deployment platform is synergistic. As a testbed, the
`overlay's value is to give researchers access to
`
`1. A large set of geographically distributed machines.
`2. A realistic network substrate that experiences
`congestion, failures, and diverse link behaviors.
`3. The potential for a realistic client workload.
`
`Its value as a deployment platform is to provide
`researchers with a direct technology transfer path for
`popular new services, and users with access to those new
`services. We believe that supporting both roles is critical to
`the success of the system.
`
`Services currently running continuously on Planetlab
`include the CoDeeN and Coral CDNs; the ScriptRoute
`network measurement service; the Chord and OpenDHT a
`
`https:1/planetlab.cs.princeton.edu/about.html
`
`3/5
`
`Microsoft Ex. 1026, p. 3
`Microsoft v. Daedalus Blue
`IPR2021-00832
`
`

`

`4/29/2021
`
`About Planetlab I Planetlab
`scalable object location services; and the PIER, Trumpet,
`and CoMon network monitoring services.
`
`A microcosm of the next Internet
`Not only are researchers evaluating and deploying end(cid:173)
`user services on top of PlanetLab, but we also expect
`them to develop foundational sub-services that can be
`folded back in to PlanetLab, thereby enhancing the facility
`for others. Our long-term goal is to identify the common
`building block services upon which other services and
`applications can be constructed, or said another way, our
`goal is to understand how the Internet can be architected
`to better support overlays.
`
`This perspective is motivated by the general question of
`how the networking research community can best impact
`the global Internet. Unfortunately, the very commercial
`success that has fueled our increased dependency on the
`Internet has also reduced our ability to evolve its
`underlying architecture to meet new demands and correct
`emerging vulnerabilities. This is because, as a recent
`National Research Council report notes,
`
`... successful and widely adopted technologies
`are subject to ossification, which makes it hard
`to introduce new capabilities or, if the current
`technology has run its course, to replace it with
`something better. Existing industry players are
`not generally motivated to develop or deploy
`disruptive technologies ...
`
`Overlay networks provide an opportunity to introduce
`disruptive technologies. Overlay nodes can be
`programmed to support the new capability or feature, and
`then depend on conventional nodes to provide the
`underlying connectivity. Over time, if the idea deployed in
`the overlay proves useful, there may be economic
`motivation to migrate the functionality into the base
`system, that is, add it to the feature set of commercial
`routers. On the other hand, the functionality may be
`complex enough that an overlay layer may be exactly
`
`https:1/planetlab.cs.princeton.edu/about.html
`
`4/5
`
`Microsoft Ex. 1026, p. 4
`Microsoft v. Daedalus Blue
`IPR2021-00832
`
`

`

`4/29/2021
`
`About Planetlab I Planetlab
`where it belongs. Our overarching goal is to support the
`introduction of disruptive technologies into the Internet
`through the use of overlay networks. Planetlab is an
`essential element of this vision.
`
`A consortium
`The Planetlab Consortium is a collection academic,
`industrial, and government institutions cooperating to
`support and enhance the Planetlab overlay network. It is
`responsible for 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.
`For more information about the Planetlab Consortium,
`click here.
`
`Andy
`
`Copyright© 2007-2019 The Trustees of Princeton University
`
`https://planetlab.cs.princeton.edu/about.html
`
`5/5
`
`Microsoft Ex. 1026, p. 5
`Microsoft v. Daedalus Blue
`IPR2021-00832
`
`