PlanetLab: An Overlay Testbed for Broad-Coverage Services
ACM SIGCOMM Computer Communication Review, 2003 · paper · Computer science
Describes the initial implementation of PlanetLab, a global overlay network testbed for developing broad-coverage network services. Multiple services run concurrently, each in its own slice, with the paper covering virtualization mechanisms and core management services.
Checked: PDF from cs.cornell.edu, fetched 4 Oct 2026. Page numbers are those of that PDF.
2 findings
Reference or label The reference list contains two works twice: [1] and [2] are both "Resilient overlay networks" (Andersen et al., 18th SOSP, October 2001), and [27] and [28] are both "An Integrated Experimental Environment for Distributed Systems and Networks" (White et al., 5th OSDI, December 2002). The text cites NetBed as both [27] and [28].
- p. 8 References, entry [1]
[1] D. Andersen, H. Balakrishnan, F. Kaashoek, and
- p. 9 References, entry [2]
[2] D. Andersen, H. Balakrishnan, M. F. Kaashoek, and
- p. 4 Section 3.1.2
NetBed [28] and RON [1]
- p. 1 Introduction
robust routing overlays [20, 2]
Judge's note: Page 8/9 images: [1] and [2] have the same authors, title, venue and date, and differ only in capitalisation, the initial 'F.' against 'M. F.' Kaashoek, and page/location detail. Page 10 image: [27] and [28] have the same authors, title, 5th OSDI and December 2002. The extracted text has 'NetBed [28] and RON [1]' in Section 3.1.2 and the page 6 image has 'NetBed CD [27]', so NetBed is cited under both numbers. I did not open page 1 to check the reviewers' statement that the introduction cites RON as [2]; the duplicate entries stand without it.
Second check: another model agreed
Report a problem with this finding
Reference or label Reference list gives the same paper twice: '[27] B. White, J. Lepreau, L. Stoller, R. Ricci, S. Guruprasad, M. Newbold, M. Hibler, C. Barb, and A. Joglekar. An Integrated Experimental Environment for Distributed Systems and Networks. In Proceedings of the 5th Symposium on Operating System Design and Implementatio (OSDI), Boston, MA, December 2002.' and '[28] B. White, J. Lepreau, ... An integrated experimental environment for distributed systems and networks. In Proceedings of the 5th USENIX Symposium on Operating Systems Design and Implementation, December 2002.'; NetBed is cited as 'NetBed [28]' (Sec. 3.1.2) and 'NetBed CD [27]' (Sec. 4.1.1). Entry [27] also misspells the venue ('Operating System Design and Implementatio').
- p. 10 References, entry [27]
[27] B. White, J. Lepreau, L. Stoller, R. Ricci,
- p. 10 References, entry [28]
[28] B. White, J. Lepreau, L. Stoller, R. Ricci,
- p. 6 Section 4.1.1
BSD-based NetBed CD [27]
- p. 4 Section 3.1.2
NetBed [28] and RON [1]
Judge's note: Viewed the reference-list crop on page 10: entries [27] and [28] have the same nine authors, the same title (differing only in capitalisation) and the same conference and date (5th OSDI, December 2002), so they are one paper listed twice. Viewed the page 4 and page 6 crops: NetBed is cited as [28] in 3.1.2 and as [27] in 4.1.1. The duplication is evident from the page itself and needs no outside knowledge. Fix: merge into one entry and renumber. Entry [27] also has the typo 'Implementatio' and 'Operating System' (singular) against 'Operating Systems' in [28]. Both citations still lead to the right paper, so this is a reference-list defect only.
Second check: another model agreed
Report a problem with this finding
26 minor (typos and the like; most checked by the judge only)
Wording Section 3.1.3: "5.9 MB to create 1408 directories (4 KB per directory)". The nominal product 1408 x 4 KB = 5632 KB (about 5.6 MB) is the figure printed for /etc, not 5.9 MB.
- p. 4 Section 3.1.3 Scalability
5.6 MB for a copy of /etc, and 5.9 MB to create 1408 directories (4 KB per directory)
- p. 4 Sec 3.1.3
5.9 MB to create 1408 directories (4 KB per directory)
Judge's note: Checked the page 4 crop. The components do sum to 29 MB, and 29/508 = 5.7%. 5.9 MB / 1408 is about 4.1 KiB (decimal MB) or 4.3 KiB (binary MB), so '4 KB per directory' could be a rounded per-directory figure taken from a measured total. That makes this a small consistency point, not a clear error. A swap with the /etc figure is possible but cannot be shown from the files.
Second check: another model agreed
Report a problem with this finding
Typo Section 2.2: "a resource monitor is an service running on each node" should read "a service".
- p. 2 Section 2.2, 'Second' paragraph
a resource monitor is an service running on each
- p. 2
resource monitor is an service running on each node.
- p. 2
Second, a resource monitor is an service running on each
Judge's note: Checked the page 2 crop. The wrong article is printed exactly as quoted.
Second check: another model agreed
Report a problem with this finding
Typo "In the abstract, this process works as follows; Section 4 described the implementation in Version 0.5." uses the past tense for a later section; should read "describes".
- p. 2 Section 2.2, first paragraph
Section 4 described
Judge's note: Page 2 image, Section 2.2 first paragraph: printed as quoted. Section 4 (Management Services, page 6) comes later and the rest of the sentence is in the present tense. The pointer itself is correct: Section 4.2 covers the Version 0.5 slice-creation implementation.
Second check: none (judge only)
Report a problem with this finding
Typo Section 3.2.1: "protocol can be either IPPROTO_TCP or IPPROTOT_UDP". The constant should be IPPROTO_UDP.
- p. 4 Section 3.2.1, paragraph after socket() prototype
IPPROTOT UDP
- p. 4
can be either IPPROTO TCP or IPPROTOT UDP for
- p. 5 Sec 3.2.2
code fratment
- p. 2 Sec 2.2
is an service running
Judge's note: Checked the page 4 crop: the image shows IPPROTOT_UDP with the extra T, next to IPPROTO_TCP. The other typos listed in this cluster (fratment, an service, developped, recieves) are judged under C011, C002, C014 and C015.
Second check: another model agreed
Report a problem with this finding
Typo Section 3.2: "delivered only the to the service that created the socket" has a stray "the" (should be "delivered only to the service").
- p. 4 Section 3.2, second paragraph
and delivered only the to the service
- p. 4
delivered only the to the service that created the
- p. 4 Sec 3.2
delivered only the to the service
- p. 5 3.2.2
code fratment
Judge's note: Checked the page 4 crop. The stray word is printed. The other typos listed in this cluster are judged under their own clusters (C002, C004, C010, C011, C014, C015, C016, C018, C023).
Second check: another model agreed
Report a problem with this finding
Typo Section 4.2.5 spells the security principal as 'principle' four times ("they are the principle named in the tickets", "to the principle named in the ticket", "which include a principle", "the authorizing principle's RSA signature"), while Sections 2.2 and 4.2.3 spell it 'principal'.
- p. 8 Section 4.2.5
they are the principle named in the tickets
- p. 8 Section 4.2.5
the authorizing principle's RSA signature
- p. 7 Section 4.2.3, third paragraph
the principal named in ticket
- p. 2 Section 2.2, 'Fourth' paragraph
the principal on whose behalf the request is being made
Judge's note: Page 8 image, left column, Section 4.2.5 shows all four 'principle' spellings. The page 7 image shows 'the principal named in ticket' in 4.2.3. The extracted text of Section 2.2 has 'the principal on whose behalf the request is being made'. The Figure 2 tag <principle_sha1> may be the literal element name in the implementation and is not counted as an error; the prose spelling is wrong and inconsistent.
Second check: none (judge only)
Report a problem with this finding
Typo Section 3.1.1: "reduced to just 5.7% of what would be requiring with copying" should read "required".
- p. 3 Section 3.1.1, second paragraph
5.7% of what would be requiring with copy-
- p. 3
reduced to just 5.7% of what would be requiring with
- p. 3 Sec 3.1.1
what would be requiring with copy-
- p. 3
would be requiring with copy- ing
Judge's note: Checked the page 3 crop. The wrong verb form is printed.
Second check: another model agreed
Report a problem with this finding
Typo "to not misuse root priviledge", "normally require root priviledge" and "version of the priviledged service": misspelling of "privilege" / "privileged", three times in Section 3.2.
- p. 4 Section 3.2, first paragraph
to not misuse root priviledge
- p. 4 Section 3.2, first paragraph
mally require root priviledge
- p. 4 Section 3.2, second paragraph
version of the priviledged service
- p. 4
cannot all be trusted to not misuse root priviledge.
Judge's note: Page 4 image, Section 3.2 first and second paragraphs: all three occurrences are printed as quoted. The same page spells the word correctly in Section 3.1.2 ("privileged operations").
Second check: another model agreed
Report a problem with this finding
Typo Section 3.2: "services are forced create sockets" is missing "to" ("forced to create").
- p. 4 Section 3.2, second paragraph
services are forced create sockets
- p. 4
services are forced create sockets that are bound to
- p. 4 Sec 3.2
delivered only the to the service
- p. 6 Sec 4.1.2
ability the remotely power-cycle
Judge's note: Checked the page 4 crop. The word 'to' is missing in the printed text. The other items listed in this cluster are judged under C009, C010 and C016.
Second check: another model agreed
Report a problem with this finding
Typo Section 3.1.2: "running an sshd daemon a different TCP port" is missing "on".
- p. 4 Section 3.1.2, second paragraph
daemon a different TCP port
- p. 4
running an sshd daemon a different TCP port),
- p. 4 Sec 3.1.2
running an sshd daemon a different TCP port
Judge's note: Checked the page 4 crop (left column). The preposition is missing in the printed text.
Second check: another model agreed
Report a problem with this finding
Typo Section 3.2.2: "the following code fratment" should read "fragment".
- p. 5 Section 3.2.2, first paragraph
the following code fratment
- p. 5
For example, the following code fratment
Judge's note: Checked the page 5 crop. The misspelling is printed. Page 4 spells it 'code fragment'.
Second check: another model agreed
Report a problem with this finding
Typo "while resource isolation between vservers protect PlanetLab services from each other": singular subject "resource isolation" with plural verb; should read "protects".
- p. 5 Section 3.3, first paragraph
isolation between vservers protect PlanetLab services
- p. 5 Sec 3.3
resource isolation between vservers protect PlanetLab services
Judge's note: Page 5 image, Section 3.3 first paragraph: printed as quoted. The preceding clause ("resource limits ... protect") has a plural subject, which probably carried over.
Second check: none (judge only)
Report a problem with this finding
Typo "our approach is to unbundled management of the overlay into a set of largely independent services" should read "to unbundle".
- p. 6 Section 4, first paragraph
our approach is to unbundled management
- p. 6
our approach is to unbundled management of the overlay
Judge's note: Page 6 image, Section 4 first paragraph: printed as quoted. Wrong verb form after "to".
Second check: another model agreed
Report a problem with this finding
Typo Section 4.1.1: "The boot environment for PlanetLab was developped from" should read "developed".
- p. 6 Section 4.1.1, first sentence
was developped from
- p. 6
boot environment for PlanetLab was developped from the University
Judge's note: Checked the page 6 crop. The misspelling is printed.
Second check: another model agreed
Report a problem with this finding
Typo Section 4.1.1: "It recieves in return a file encrypted" should read "receives".
- p. 6 Section 4.1.1, second paragraph
It recieves in return a
- p. 6
It recieves in return a file encrypted and signed
- p. 6 Sec 4.1.1
It recieves in return
- p. 6
It recieves in return a file encrypted
Judge's note: Checked the page 6 crop. The misspelling is printed.
Second check: another model agreed
Report a problem with this finding
Typo Section 4.1.2: "In combination with the ability the remotely power-cycle a machine" should read "ability to remotely".
- p. 6 Section 4.1.2, second paragraph
the ability the remotely power-cycle
- p. 6
combination with the ability the remotely power-cycle a machine,
- p. 6
In combination with the ability the remotely power-cycle a
Judge's note: Checked the page 6 crop. The printed text has 'the' where 'to' is needed.
Second check: another model agreed
Report a problem with this finding
Typo Section 4.2.2: "It uses use secure XML-RPC protocols" has a duplicated verb.
- p. 7 Section 4.2.2, across line break
It uses use
- p. 7
It uses use secure XML-RPC protocols to communicate
- p. 7
It uses use secure XML-RPC protocols
Judge's note: Checked the page 7 crop: 'It uses use' sits at the end of the line and 'secure XML-RPC' starts the next.
Second check: another model agreed
Report a problem with this finding
Typo Section 4.2.3: "lease renewals (rewewlease)". The RPC name is presumably renewlease.
- p. 7 Section 4.2.3, second paragraph
rewewlease
- p. 7
lease cancellations (deletelease), lease renewals (rewewlease), and adding
- p. 7 Sec 4.2.3
lease renewals (rewewlease)
Only the authors can say what is right here.
Judge's note: Checked the page 7 crop: 'rewewlease' is printed in monospace. It is almost certainly a typo, given 'renewals' and the parallel names newlease and deletelease. Because it is a code identifier, only the authors can confirm the real RPC name.
Second check: another model agreed
Report a problem with this finding
Typo Section 4.2.4: "Service managers are implemented as executions of as a command-line program" contains a stray 'as' (or 'of as').
- p. 7 Section 4.2.4, first sentence
implemented as executions of as a
- p. 7
implemented as executions of as a command-line program
- p. 7 Sec 4.2.4
executions of as a command-line program
Judge's note: Page 7 image, right column, first sentence of 4.2.4 reads exactly as quoted. It is an editing leftover.
Second check: another model agreed
Report a problem with this finding
Typo Section 4.2.3: "matches the identity of the principal named in ticket" is missing the article ('in the ticket').
- p. 7 Section 4.2.3, third paragraph
the principal named in ticket
Judge's note: Page 7 image, right column, third paragraph of 4.2.3 reads 'the principal named in ticket. Assuming service manager authentication succeeds'. The article is missing.
Second check: none (judge only)
Report a problem with this finding
Typo End of Section 4.1.2: "The only changes we have made to this process is to ensure that all files ... are signed" has a plural subject with a singular verb, and only one change is described.
- p. 7 top of left column (end of Section 4.1.2)
changes we have made to this process is to ensure
- p. 7 Sec 4.1.2
The only changes we have made to this process is
Judge's note: Page 7 image, top of the left column reads as quoted. This is a subject-verb agreement slip; 'The only change ... is' fits the single change described.
Second check: none (judge only)
Report a problem with this finding
Typo Section 4.2.4: "Service managers are implemented as executions of as a command-line program" has a garbled phrase ("of as a").
- p. 7
Service managers are implemented as executions of as a
Judge's note: Checked the page 7 crop (shown as page 9 in the journal footer). The garbled wording is printed.
Second check: none (judge only)
Report a problem with this finding
Typo Section 4.3: "created by any PlanetLab principle investigator" should read 'principal investigator'.
- p. 8 Section 4.3, paragraph after Figure 2
any PlanetLab principle investigator
- p. 8
created by any PlanetLab principle investigator, administrative slices
- p. 8 Sec 4.2.5
they are the principle named in the tickets
Judge's note: Page 8 image, right column below Figure 2 reads 'any PlanetLab principle investigator'. This is the wrong word for the role. This cluster is kept for the 'principal investigator' instance only; the security-principal spellings in Section 4.2.5 are handled in C024.
Second check: another model agreed
Report a problem with this finding
Typo References [25], [26] and [27] print the venue as "Symposium on Operating System Design and Implementatio (OSDI)", with 'Implementation' truncated; [15] and [28] spell it in full.
- p. 9 References, entry [25]
System Design and Implementatio (OSDI)
- p. 10 References, entry [27]
Implementatio (OSDI)
- p. 9
Operating System Design and Implementatio (OSDI), Boston, MA,
- p. 9 Refs [25],[26]
Implementatio (OSDI)
Judge's note: Page 9 image shows 'Implementatio (OSDI)' in entries [25] and [26]; page 10 image shows it in [27]. Entry [28] on page 10 and entry [15] on page 9 have 'Implementation'. The truncation is in the typeset PDF.
Second check: another model agreed
Report a problem with this finding
Typo Reference [7]: the URL "http://www.ensim.com/products/materials/datasheet vps 051003.pdf" runs out of the left column and overprints the first word of the second line of reference [20] ("Selection.").
- p. 9 References, entry [7]
http://www.ensim.com/products/materials/datasheet vps 051003.pdf
Judge's note: Page 9 image: the end of the URL in entry [7] collides with the start of the line 'Selection. In Proceedings of the ACM SIGCOMM' in entry [20], leaving both partly illegible. This is in the typeset layout of this PDF. It is cosmetic.
Second check: none (judge only)
Report a problem with this finding
Typo Reference [12]: "Proceedings of the Ninth international Conference on Architectural Support for Programming Languages and Operating Systems" has a lower-case 'international' inside an otherwise capitalised proceedings title.
- p. 9 Ref [12]
Ninth international Conference
Judge's note: Page 9 image, entry [12] reads 'Ninth international Conference'. Capitalisation is inconsistent within the title. It is a trivial style slip.
Second check: none (judge only)