[avtext] RFC 6465 on A Real-time Transport Protocol (RTP) Header Extension for Mixer-to-Client Audio Level Indication

rfc-editor@rfc-editor.org Fri, 16 December 2011 20:53 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: avtext@ietfa.amsl.com
Delivered-To: avtext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0A201F0C3F; Fri, 16 Dec 2011 12:53:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.178
X-Spam-Level:
X-Spam-Status: No, score=-105.178 tagged_above=-999 required=5 tests=[AWL=-0.101, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TDlWTp9Z-90g; Fri, 16 Dec 2011 12:53:27 -0800 (PST)
Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id 1EC421F0C7C; Fri, 16 Dec 2011 12:53:22 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 39EAA72E010; Fri, 16 Dec 2011 12:52:15 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20111216205215.39EAA72E010@rfc-editor.org>
Date: Fri, 16 Dec 2011 12:52:15 -0800
Cc: avtext@ietf.org, rfc-editor@rfc-editor.org
Subject: [avtext] RFC 6465 on A Real-time Transport Protocol (RTP) Header Extension for Mixer-to-Client Audio Level Indication
X-BeenThere: avtext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Extensions working group discussion list <avtext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avtext>, <mailto:avtext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avtext>
List-Post: <mailto:avtext@ietf.org>
List-Help: <mailto:avtext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avtext>, <mailto:avtext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2011 20:53:27 -0000

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

        
        RFC 6465

        Title:      A Real-time Transport Protocol (RTP) 
                    Header Extension for Mixer-to-Client Audio Level 
                    Indication 
        Author:     E. Ivov, Ed.,
                    E. Marocco, Ed.,
                    J. Lennox
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2011
        Mailbox:    emcho@jitsi.org, 
                    enrico.marocco@telecomitalia.it, 
                    jonathan@vidyo.com
        Pages:      15
        Characters: 30154
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avtext-mixer-to-client-audio-level-06.txt

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

This document describes a mechanism for RTP-level mixers in audio
conferences to deliver information about the audio level of
individual participants.  Such audio level indicators are transported
in the same RTP packets as the audio data they pertain to.
[STANDARDS-TRACK]

This document is a product of the Audio/Video Transport Extensions 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-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