[AVT] RFC 5219 on A More Loss-Tolerant RTP Payload Format for MP3 Audio
rfc-editor@rfc-editor.org Fri, 15 February 2008 02:09 UTC
Return-Path: <avt-bounces@ietf.org>
X-Original-To: ietfarch-avt-archive@core3.amsl.com
Delivered-To: ietfarch-avt-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E86EE28CE5E; Thu, 14 Feb 2008 18:09:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.589
X-Spam-Level:
X-Spam-Status: No, score=-0.589 tagged_above=-999 required=5 tests=[AWL=-0.752, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_93=0.6, RDNS_NONE=0.1]
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 aG2dakHHwCIm; Thu, 14 Feb 2008 18:09:48 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 85E183A70C1; Thu, 14 Feb 2008 18:09:41 -0800 (PST)
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3E6A53A7091; Thu, 14 Feb 2008 18:09:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 BRrYvJUujRli; Thu, 14 Feb 2008 18:09:39 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 45A7028C14D; Thu, 14 Feb 2008 18:09:36 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id F4230113E52; Thu, 14 Feb 2008 18:10:57 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20080215021057.F4230113E52@bosco.isi.edu>
Date: Thu, 14 Feb 2008 18:10:57 -0800
Cc: avt@ietf.org, rfc-editor@rfc-editor.org
Subject: [AVT] RFC 5219 on A More Loss-Tolerant RTP Payload Format for MP3 Audio
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries.
RFC 5219
Title: A More Loss-Tolerant RTP Payload
Format for MP3 Audio
Author: R. Finlayson
Status: Standards Track
Date: February 2008
Mailbox: finlayson@live555.com
Pages: 22
Characters: 42830
Obsoletes: RFC3119
I-D Tag: draft-ietf-avt-rfc3119bis-05.txt
URL: http://www.rfc-editor.org/rfc/rfc5219.txt
This document describes an RTP (Real-Time Protocol) payload format for
transporting MPEG (Moving Picture Experts Group) 1 or 2, layer III
audio (commonly known as "MP3"). This format is an alternative to
that described in RFC 2250, and performs better if there is packet
loss. This document obsoletes RFC 3119, correcting
typographical errors in the "SDP usage" section and pseudo-code
appendices. [STANDARDS TRACK]
This document is a product of the Audio/Video Transport
Working Group of the IETF.
This is now a Proposed Standard Protocol.
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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
...
_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
http://www.ietf.org/mailman/listinfo/avt