by people who have never met. This story has a happy ending. The ARPANET grew unchecked. All of the individuals within the community had open access to all of the protocol specifications and other technical documents. Access to these documents enabled the rapid implementation of new applications that could readily interoperate with existing and emerging applications. Coordination Bodies By this point, the ARPANET's pace of growth necessitated some kind of coordination. In the late 1970s, some bodies were loosely formed for this purpose: the International Cooperation Board (ICB), the Internet Research Group (IRG), and the Internet Configuration Control Board (ICCB). These bodies coped with the growth for some time, but were soon over- whelmed. That's when the task forces were first created; each task force consisted of people working on a well-specified problem area, and each had a chair to oversee progress. The Internet Activities Board (IAB) was formed next; its membership consisted of all the chairmen from the various task forces. One of these Packet Switching, IP, and the IETF early task forces was the Internet Engineering Task Force (IETF). Fig- ure 2-12 illustrates the original structure of the IAB. In the mid 1980s, public interest in the engineering of the Internet grew dramatically. More and more people started attending IETF meetings. In response, the IETF was divided into working groups. Every working group had one or more chairs and a predefined scope. These working groups were grouped together forming areas-each area under the jurisdiction of an area director or directors. Collectively, the area directors formed the Inter- net Engineering Steering Group (IESG). The remaining task forces were collapsed into the Internet Research Task Force (IRTF). The Internet Society (ISOC) was created in 1991 to administer the stan- dardization process itself rather than any specific technology. In 1992, the IAB was rechristened the Internet Architecture Board, and we arrived at the current configuration of Internet 