Jump to content

Clean-room design

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Kaze757 (talk | contribs) at 08:20, 22 August 2024 (Kaze757 moved page Clean room design to Clean-room design: MOS:HYPHEN). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

This article is about the design-copying technique. For the manufacturing or research environment, see clean room. For the software development methodology, see cleanroom software engineering.

Clean-room design (also known as the Chinese wall technique) is the method of copying a design by reverse engineering and then recreating it without infringing any of the copyrights associated with the original design. Clean-room design is useful as a defense against copyright infringement because it relies on independent creation. However, because independent invention is not a defense against patents, clean-room designs typically cannot be used to circumvent patent restrictions.

The term implies that the design team works in an environment that is "clean" or demonstrably uncontaminated by any knowledge of the proprietary techniques used by the competitor.

Typically, a clean-room design is done by having someone examine the system to be reimplemented and having this person write a specification. This specification is then reviewed by a lawyer to ensure that no copyrighted material is included. The specification is then implemented by a team with no connection to the original examiners.

Examples

Phoenix Technologies sold its clean-room implementation of the IBM-compatible BIOS to various PC clone manufacturers.[1][2]

Several other PC clone companies, including Corona Data Systems, Eagle Computer, and Handwell Corporation, were litigated by IBM for copyright infringement, and were forced to re-implement their BIOS in a way which did not infringe IBM's copyrights.[3][4] The legal precedent for firmware being protected by copyright, however, hadn't been established until Apple Computer, Inc. v. Franklin Computer Corp., 714 F.2d 1240 (3rd Circuit Court 1983). The three settlements by IBM, and the legal clean-room PC BIOS designs of Compaq and Columbia Data Products, happened before Phoenix announced, in July 1984, that they were licensing their own BIOS code. Phoenix expressly emphasized the clean-room process through which their BIOS code had been written by a programmer who did not even have prior exposure to Intel microprocessors, himself having been a TMS9900 programmer beforehand.[5] As late as the early 1990s, IBM was winning millions of dollars from settling BIOS copyright infringement lawsuits against some other PC clone manufacturers like Matsushita/Panasonic (1987)[6] and Kyocera (1993–1994), although the latter suit was for infringements between 1985 and 1990.[7][8]

Another clean-room design example is VTech's successful clones of the Apple II ROMs for the Laser 128, the only computer model, among dozens of Apple II compatibles, which survived litigation brought by Apple Computer. The "Laser 128 story" is in contrast to the Franklin Ace 1000, which lost in the 1983 decision, Apple Computer, Inc. v. Franklin Computer Corporation. The previous PC "clone" examples are notable for not daring to fight IBM in court, even before the legal precedent for copyrighting firmware had been made.[9][10][11][12]

Other examples include ReactOS, an open source operating system made from clean-room reverse-engineered components of Windows,[13] and Coherent operating system, a clean room re-implementation of version 7 Unix.[14] In the early years of its existence, Coherent's developer Mark Williams Company received a visit from an AT&T delegation looking to determine whether MWC was infringing on AT&T Unix property.[15] It has been released as open source.[14]

Case law

Clean room design is usually employed as best practice, but not strictly required by law. In NEC Corp. v Intel Corp. (1990), NEC sought declaratory judgment against Intel's charges that NEC's engineers simply copied the microcode of the 8086 processor in their NEC V20 clone. A US judge ruled that while the early, internal revisions of NEC's microcode were indeed a copyright violation, the later one, which actually went into NEC's product, although derived from the former, were sufficiently different from the Intel microcode it could be considered free of copyright violations. While NEC themselves did not follow a strict clean room approach in the development of their clone's microcode, during the trial, they hired an independent contractor who was only given access to specifications but ended up writing code that had certain similarities to both NEC's and Intel's code. From this evidence, the judge concluded that similarity in certain routines was a matter of functional constraints resulting from the compatibility requirements, and thus were likely free of a creative element.[16] Although the clean room approach had been used as preventative measure in view of possible litigation before (e.g. in the Phoenix BIOS case), the NEC v. Intel case was the first time that the clean room argument was accepted in a US court trial. A related aspect worth mentioning here is that NEC did have a license for Intel's patents governing the 8086 processor.[17]

Sony Computer Entertainment, Inc. v. Connectix Corp. was a 1999 lawsuit which established an important precedent in regard to reverse engineering.[18][19] Sony sought damages for copyright infringement over Connectix's Virtual Game Station emulator, alleging that its proprietary BIOS code had been copied into Connectix's product without permission. Sony won the initial judgment, but the ruling was overturned on appeal. Sony eventually purchased the rights to Virtual Game Station to prevent its further sale and development. This established a precedent addressing the legal implications of commercial reverse engineering efforts.

During production, Connectix unsuccessfully attempted a Chinese wall approach to reverse engineer the BIOS, so its engineers disassembled the object code directly. Connectix's successful appeal maintained that the direct disassembly and observation of proprietary code was necessary because there was no other way to determine its behavior. From the ruling:

Some works are closer to the core of intended copyright protection than others. Sony's BIOS lay at a distance from the core because it contains unprotected aspects that cannot be examined without copying. The court of appeal therefore accorded it a lower degree of protection than more traditional literary works.

  • In the first season of the 2014 TV show Halt and Catch Fire, a key plot point from the second episode is how the fictional Cardiff Electric computer company placed an engineer in a clean room to reverse engineer a BIOS for its PC clone, to provide cover and protection from IBM lawsuits for a previous probably-illegal hacking of the BIOS code others at the company had performed. It reminded many critics of Compaq's million dollar clean-room engineering, but a contemporary, but far less successful company, Columbia Data Products, also used such an approach.[20] The reaction of IBM's legal department, like other plot points, echoed the experiences of Corona Data Systems more closely.[21]

See also

References

  1. ^ Schwartz, Mathew (2001-11-12). "Reverse-Engineering". computerworld.com. Retrieved 2013-06-23. To protect against charges of having simply (and illegally) copied IBM's BIOS, Phoenix reverse-engineered it using what's called a "clean room," or "Chinese wall," approach. First, a team of engineers studied the IBM BIOS—about 8KB of code—and described everything it did as completely as possible without using or referencing any actual code. Then Phoenix brought in a second team of programmers who had no prior knowledge of the IBM BIOS and had never seen its code. Working only from the first team's functional specifications, the second team wrote a new BIOS that operated as specified.
  2. ^ Bernard A. Galler (1995). Software and Intellectual Property Protection: Copyright and Patent Issues for Computer and Legal Professionals. Greenwood Publishing Group. p. 130. ISBN 978-0-89930-974-3.
  3. ^ Caruso, Denise (February 27, 1984), "IBM Wins Disputes Over PC Copyrights", InfoWorld, p. 15, retrieved February 28, 2011
  4. ^ Sanger, David E. (9 June 1984). "EAGLE'S BATTLE FOR SURVIVAL". The New York Times.
  5. ^ "Phoenix Says Its BIOS May Foil IBM's Lawsuits". PC Magazine: The Independent Guide to IBM-Standard Personal Computing. Ziff Davis, Inc.: 56 10 July 1984. ISSN 0888-8507.
  6. ^ "Matsushita, IBM settle BIOS copyright infringement dispute". Computerworld: The Newspaper for IT Leaders. Computerworld: 67. 2 March 1987. ISSN 0010-4841.
  7. ^ Pollack, Andrew (2 February 1993). "COMPANY NEWS; Japanese Company Is Sued By I.B.M. Over Copyrights". The New York Times.
  8. ^ Joseph W. S. Davis; Hiroshi Oda; Yoshikazu Takaishi (1996). Dispute resolution in Japan. Kluwer Law International. pp. 248–254. ISBN 978-90-411-0974-3.
  9. ^ "A brief recap of the lawsuit". coolcopyright.com. Archived from the original on 2008-07-03. Retrieved 9 April 2021.
  10. ^ "IMPACT OF APPLE VS. FRANKLIN DECISION By Rob Hassett". internetlegal.com. 18 December 2012. Retrieved 9 April 2021.
  11. ^ "Refusal of Apple's injunction request". The New York Times. 4 August 1982. Retrieved 9 April 2021.
  12. ^ "The Making of a Computer by Perry Greenberg" (PDF). classiccmp.org. Retrieved 9 April 2021.
  13. ^ "A dumb hypothetical about the legality of someone documenting Windows XP - ReactOS Forum".
  14. ^ a b "Coherent sources released under a 3-clause BSD license – Virtually Fun". virtuallyfun.com. 8 January 2015. Retrieved 20 September 2018.
  15. ^ Dennis Ritchie (April 10, 1998). "Re: Coherent". Newsgroup: alt.folklore.computers. Usenet: 352DC4B7.3030@bell-labs.com.
  16. ^ Jorge Contreras, Laura Handley, and Terrence Yang, "NEC v. Intel: Breaking New Ground in the Law of Copyright, Harvard Journal of Law & Technology, Volume 3, Spring Issue, 1990, pp. 209–222 (particularly p. 213)
  17. ^ David S. Elkins, “NEC v. Intel: A Guide to Using "Clean Room" Procedures as Evidence”, Computer Law Journal, vol. 4, issue 10, (Winter 1990) pp. 453–481
  18. ^ Sony Computer Entertainment, Inc. v. Connectix Corporation, 203 F.3d 596 (9th Cir. 2000).
  19. ^ Sony Computer Entertainment, Inc. v. Connectix Corporation, 203 F.3d 596 (9th Cir. 2000). Web Archive.org copy, Feb 28, 2007.
  20. ^ Aboard the Columbia, By Bill Machrone, Page 451, Jun 1983, PC Mag
  21. ^ "Price Cut Pressure on Compatible Makers". InfoWorld: 49. 16 July 1984. ISSN 0199-6649.

Further reading

Retrieved from "https://en.wikipedia.org/w/index.php?title=Clean-room_design&oldid=1241626336"