RFC 5456 on IAX: Inter-Asterisk eXchange Version 2

rfc-editor@rfc-editor.org Sat, 27 February 2010 03:49 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1761128C2B4 for <ietf-announce@core3.amsl.com>; Fri, 26 Feb 2010 19:49:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.984
X-Spam-Level:
X-Spam-Status: No, score=-1.984 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NpkXlZt8DOty for <ietf-announce@core3.amsl.com>; Fri, 26 Feb 2010 19:49:46 -0800 (PST)
Received: from rfc-editor.org (rfcpa [64.170.98.47]) by core3.amsl.com (Postfix) with ESMTP id 493C728C292 for <ietf-announce@ietf.org>; Fri, 26 Feb 2010 19:49:46 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 9D14E130010; Fri, 26 Feb 2010 19:52:03 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5456 on IAX: Inter-Asterisk eXchange Version 2
From: rfc-editor@rfc-editor.org
Message-Id: <20100227035203.9D14E130010@rfc-editor.org>
Date: Fri, 26 Feb 2010 19:52:03 -0800
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Feb 2010 03:49:47 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5456

        Title:      IAX: Inter-Asterisk eXchange Version 2 
        Author:     M. Spencer, B. Capouch,
                    E. Guy, Ed.,
                    F. Miller, K. Shumard
        Status:     Informational
        Date:       February 2010
        Mailbox:    markster@digium.com, 
                    brianc@saintjoe.edu, 
                    edguy@emcsw.com,  mail@frankwmiller.net, 
                    kshumard@gmail.com
        Pages:      101
        Characters: 226083
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-guy-iax-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5456.txt

This document describes IAX, the Inter-Asterisk eXchange protocol, an
application-layer control and media protocol for creating, modifying,
and terminating multimedia sessions over Internet Protocol (IP)
networks.  IAX was developed by the open source community for the
Asterisk Private Branch Exchange (PBX) and is targeted primarily at
Voice over Internet Protocol (VoIP) call control, but it can be used
with streaming video or any other type of multimedia.

IAX is an "all in one" protocol for handling multimedia in IP
networks.  It combines both control and media services in the same
protocol.  In addition, IAX uses a single UDP data stream on a static
port greatly simplifying Network Address Translation (NAT) gateway
traversal, eliminating the need for other protocols to work around
NAT, and simplifying network and firewall management.  IAX employs a
compact encoding that decreases bandwidth usage and is well suited
for Internet telephony service.  In addition, its open nature permits
new payload type additions needed to support additional services.  
This document is not an Internet Standards Track specification; it is
published for informational purposes.

This document is an Independent Submission.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC