d on the technology they are working on. The areas are managed by Area Directors (ADs). The IETF structure is depicted in Figure 2.2. The ADs form a group called the Internet Engineering Steering Group (IESG) headed by the IETF chair who is also the AD for the General Area. Currently, all other areas have two ADs. The General Area is a non-technical area responsible for the evolution of processes and the general structure of the IETF. All the other areas are technical. The Internet Architecture Board (IAB) is responsible for the architectural guidance of the IETF. If the IESG is a very operational body, the IAB is very strategic with few short-term goals. The administrative part includes making sure the IETF organization has adequate funds and tools, and that it is capable to organizing its meetings; this is the responsibility of the IETF Administrative Oversight Committee (IAOC). The interesting part of the IETF organization is that it has no membership. The idea is that the process is as inclusive as possible, and anybody and everybody can join to participate in the IETF process. The IETF participants are supposed to represent only themselves, and their best technical judgement. However, it is clear that most of the participants do work for organizations that have an interest for the IETF process. To make sure that the barrier for entry to the IETF is as low as possible, most of the work and all of its decisions are conducted in the WG mailing lists. The IETF does hold Basics of the 3GPP Technologies three meetings a year, but according to the procedures it is not mandatory to participate in the physical meetings to participate in the technical process. The decisions in the standards process are based on so-called 'rough consensus'. As the IETF has no membership, and the decisions are done on the mailing lists, the IETF cannot really vote. Instead, the WG chairperson or chairpersons try to understand using the mailing list discussions as their guide, which direction the consensus of the WG is going. The 'rough'