RFC 7310 on RTP Payload Format for Standard apt-X and Enhanced apt-X Codecs
rfc-editor@rfc-editor.org Tue, 29 July 2014 22:21 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B65F1B2987 for <ietf-announce@ietfa.amsl.com>; Tue, 29 Jul 2014 15:21:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.903
X-Spam-Level:
X-Spam-Status: No, score=-101.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ck1StbazejQF for <ietf-announce@ietfa.amsl.com>; Tue, 29 Jul 2014 15:20:59 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id F1A4F1B2972 for <ietf-announce@ietf.org>; Tue, 29 Jul 2014 15:20:58 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D523A18B57F; Tue, 29 Jul 2014 15:19:54 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7310 on RTP Payload Format for Standard apt-X and Enhanced apt-X Codecs
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140729221954.D523A18B57F@rfc-editor.org>
Date: Tue, 29 Jul 2014 15:19:54 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/3dZSzQ5l7PHfGhe8zhmv23pn3iE
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 29 Jul 2014 22:21:05 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7310
Title: RTP Payload Format for Standard
apt-X and Enhanced apt-X Codecs
Author: J. Lindsay, H. Foerster
Status: Standards Track
Stream: IETF
Date: July 2014
Mailbox: lindsay@worldcastsystems.com,
foerster@worldcastsystems.com
Pages: 16
Characters: 32743
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-payload-rtp-aptx-05.txt
URL: https://www.rfc-editor.org/rfc/rfc7310.txt
This document specifies a scheme for packetizing Standard apt-X or
Enhanced apt-X encoded audio data into Real-time Transport Protocol
(RTP) packets. The document describes a payload format that permits
transmission of multiple related audio channels in a single RTP
payload and a means of establishing Standard apt-X and Enhanced
apt-X connections through the Session Description Protocol (SDP).
This document is a product of the Audio/Video Transport Payloads Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements. Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://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