Internet Engineering Task Force

Standards body for Internet protocols and services.
The keeper of RFCs.

IETF Working Groups related to VOIP

  • SIP Working group
    • The Session Initiation Protocol (SIP) working group is chartered to continue the development of SIP, currently specified as proposed standard RFC 2543. SIP is a text-based protocol, similar to HTTP and SMTP, for initiating interactive communication sessions between users. Such sessions include voice, video, chat, interactive games, and virtual reality. The main work of the group involves bringing SIP from proposed to draft standard, in addition to specifying and developing proposed extensions that arise out of strong requirements. The SIP working group will concentrate on the specification of SIP and its extensions, and will not explore the use of SIP for specific environments or applications. It will, however respond to general-purpose requirements for changes to SIP provided by other working groups, including the SIPPING working group, when those requirements are within the scope and charter of SIP.
  • SIPPING Working Group
    • The Session Initiation Protocol Project INvestiGation (SIPPING) working group is chartered to document the use of SIP for several applications related to telephony and multimedia, and to develop requirements for any extensions to SIP needed for those applications. Such requirements will be referred to the SIP working group for development of any new SIP method or header.
  • SIGTRAN Working Group
    • The primary purpose of this working group will be to address the transport of packet-based PSTN signaling over IP Networks, taking into account functional and performance requirements of the PSTN signaling.
  • SIMPLE: SIP for instant messaging and precense
    • This working group focuses on the application of the Session Initiation Protocol (SIP, RFC 3261) to the suite of services collectively known as instant messaging and presence (IMP). The IETF has committed to producing an interoperable standard for these services compliant to the requirements for IM outlined in RFC 2779 (including the security and privacy requirements there) and in the Common Presence and Instant Messaging (CPIM) specification, developed within the IMPP working group. As the most common services for which SIP is used share quite a bit in common with IMP, the adaptation of SIP to IMP seems a natural choice given the widespread support for (and relative maturity of) the SIP standard.
  • VPIM: Voice Profile for Internet Mail
    • how to get interoperability between voice mail systems
  • ENUM: Telephone number mapping ENUM
    • This working group has defined a DNS-based architecture and protocol RFC 2916 by which an E.164 number, as defined in ITU Recommendation E.164, can be expressed as a Fully Qualified Domain Name in a specific Internet Infrastructure domain defined for this purpose ( The result of the ENUM query is a series of DNS NAPTR resource records RFC2915 which can be used to contact a resource (e.g.URI) associated with that number.
  • IPTEL Working group
    • The focus of the IP Telephony (iptel) group is on the problems related to naming and routing for Voice over IP (VoIP) protocols. Naming is accomplished through the use of the tel URI, which specifies a URI for telephone numbers. The tel URI was originally defined in RFC 2806, which was developed outside of any IETF working group. The iptel working group is responsible for updating the specification based on extensive experience with the tel URI. It is chartered to develop any extensions to the tel URI, such as support for number portability indicators and trunk groups.
    • Additional home page for IPTEL wg
  • MEGACO Working group
    • The Megaco media gateway control protocol, RFC 3015 (also published as ITU-T Recommendation H.248), was developed by the Megaco Working Group in close cooperation with ITU-T Study Group 16. The protocol responds to the requirements documented in RFC 2805. The Megaco Working Group has identified a large number of corrections to the protocol specification in the year and a half since RFC 3015/Rec. H.248 was approved. As guardians of the protocol specification, Study Group 16 maintains a record of these corrections in the form of an "Implementor's Guide". Study Group 16 now proposes to issue a new version of Recommendation H.248 incorporating these corrections and a limited number of new protocol features. The current charter includes one package, on naming patterns. If the WG determines that other packages are of general usefulness, an AD and IESG review is needed to permit addition of the package to the charter.
  • MIDCOM Working Group
    • As trusted third parties are increasingly being asked to make policy decisions on behalf of the various entities participating in an application's operation, a need has developed for applications to be able to communicate their needs to the devices in the network that provide transport policy enforcement. Examples of these devices include firewalls, network address translators (both within and between address families), signature management for intrusion detection systems, and multimedia buffer management. These devices are a subset of what can be referred to as 'middleboxes.' This working group will focus its attention on communication with firewalls and network address translators. The intention is to provide a generalized communications interface that will serve as a new home for application-specific firewall functionality for communications protocols such as SIP and H.323. The STUN RFC (RFC3489) was delivered by this group.
  • MMUSIC Working Group
    • 'The Multiparty MUltimedia SessIon Control (MMUSIC) Working Group (WG) was chartered to develop protocols to support Internet teleconferencing and multimedia communications. These protocols are now reasonably mature, and many have received widespread deployment. The group is now focussed on the revisions of these protocols in the light of implementation experience and additional demands that have arisen from other WGs (such as AVT, SIP, SIPPING, and MEGACO ).

See also

Created by: jht2, Last modification: Mon 25 of Jun, 2012 (20:56 UTC) by admin
Please update this page with new information, just login and click on the "Edit" or "Discussion" tab. Get a free login here: Register Thanks! - Find us on Google+