IETF(Internet Engineering Yask Force).

The working and structure of IETF is different from a telecommunication standards body, such as 3GPP and 3GPP2. It is not driven by industry leaders, does not require membership or dues, and is open to any interested individual. This actually benefits the industry by opening up the platform for good ideas and opinions. At the same time, it makes the development of an open protocol slower compared to a telecom standards body.
The actual technical work of the IETF is done in its working groups (WGs), which are organized by topics into several areas. There are eight different areas in the IETF: application area, internet area, operations and management area, routing area, security area, sub-ip area, transport area, and user services area. Each WG has a charter and a set of work items. One chairperson (sometimes two), manages the WGs. The area directors (AD), who are collectively called IESGs, oversee the WGs. The WGs or areas are also overseen by the Internet Architecture Board (IAB), which is responsible for providing architectural oversight and focuses on long-range planning and coordination among the various areas. When members are interested in starting a new WG, they can form a "Birds of a Feather" (BOF) session. This is taken from the saying, "Birds of a feather flock together." If the BOF gathers sufficient interest and is thought to be working on a useful and solvable problem, a WG is formed.
WGs do most of their work using the e-mail distribution list. They meet three times a year for face-to-face meetings. Usually, a participant submits an Internet draft (ID) containing a solution for any of the WG's work items. The ID is discussed and its contents are agreed on by rough consensus. A WG may merge multiple solutions for different issues or the same issue into a WG ID. When all the issues are addressed, the WG chair calls for a last call for comments on the WG ID. After the comments are successfully addressed, the ID is sent to the IESG. The IESG also issues the last call for comments on the ID, but from all IETF participants. After all the comments are considered, the draft is sent to the request for comments (RFC) editor for publication as an RFC. RFCs are permanent IETF publications available as specifications to the users.

In addition to the liaisons and BOFs, there is a lot of focus inside IETF on developing protocols/recommendations that are also friendly to different wireless technology. Individuals from 3GPP, 3GPP2, Bluetooth, and the WLAN industry are working in different WGs to get solutions that would help in bringing IP to their technologies. Examples of such WGs are Performance Implications of Link Characteristics (PILC), Seamless Mobility (SEAMOBY), Session Initiation Protocol (SIP), Mobile Ad-Hoc Networks (MANET), Mobile IP, Zero Configuration Networks (ZeroConf), and Robust Header Compression (ROHC). This trend will increase due to the open nature of IETF.