RFC 5761 on Multiplexing RTP Data and Control Packets on a Single Port
rfc-editor@rfc-editor.org Thu, 29 April 2010 23:36 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 D6DC43A6C17; Thu, 29 Apr 2010 16:36:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.99
X-Spam-Level:
X-Spam-Status: No, score=-1.99 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
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 HnghkepARCkx; Thu, 29 Apr 2010 16:36:07 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id BD56C3A6C11; Thu, 29 Apr 2010 16:36:06 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C8AB1E07E5; Thu, 29 Apr 2010 16:35:53 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5761 on Multiplexing RTP Data and Control Packets on a Single Port
From: rfc-editor@rfc-editor.org
Message-Id: <20100429233553.C8AB1E07E5@rfc-editor.org>
Date: Thu, 29 Apr 2010 16:35:53 -0700
Cc: avt@ietf.org, 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: Thu, 29 Apr 2010 23:36:07 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 5761
Title: Multiplexing RTP Data and Control
Packets on a Single Port
Author: C. Perkins, M. Westerlund
Status: Standards Track
Stream: IETF
Date: April 2010
Mailbox: csp@csperkins.org,
magnus.westerlund@ericsson.com
Pages: 13
Characters: 31778
Updates: RFC3550, RFC3551
I-D Tag: draft-ietf-avt-rtp-and-rtcp-mux-07.txt
URL: http://www.rfc-editor.org/rfc/rfc5761.txt
This memo discusses issues that arise when multiplexing RTP data
packets and RTP Control Protocol (RTCP) packets on a single UDP port.
It updates RFC 3550 and RFC 3551 to describe when such multiplexing
is and is not appropriate, and it explains how the Session
Description Protocol (SDP) can be used to signal multiplexed
sessions. [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-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