[payload] Fwd: I-D Action: draft-lennox-payload-ulp-ssrc-mux-00.txt

Jonathan Lennox <jonathan@vidyo.com> Mon, 18 February 2013 23:07 UTC

Return-Path: <jonathan@vidyo.com>
X-Original-To: payload@ietfa.amsl.com
Delivered-To: payload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C787621F8778 for <payload@ietfa.amsl.com>; Mon, 18 Feb 2013 15:07:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.473
X-Spam-Level:
X-Spam-Status: No, score=-2.473 tagged_above=-999 required=5 tests=[AWL=0.126, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CrWXWjSdBpLU for <payload@ietfa.amsl.com>; Mon, 18 Feb 2013 15:07:38 -0800 (PST)
Received: from mxout.myoutlookonline.com (mxout.myoutlookonline.com [64.95.72.241]) by ietfa.amsl.com (Postfix) with ESMTP id 2BF4921F8788 for <payload@ietf.org>; Mon, 18 Feb 2013 15:07:38 -0800 (PST)
Received: from mxout.myoutlookonline.com (localhost [127.0.0.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id CC9518BF006 for <payload@ietf.org>; Mon, 18 Feb 2013 18:07:37 -0500 (EST)
X-Virus-Scanned: by SpamTitan at mail.lan
Received: from HUB015.mail.lan (unknown [10.110.2.1]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mxout.myoutlookonline.com (Postfix) with ESMTPS id E1D6D8BEF9B for <payload@ietf.org>; Mon, 18 Feb 2013 18:07:32 -0500 (EST)
Received: from BE235.mail.lan ([10.110.32.235]) by HUB015.mail.lan ([10.110.17.15]) with mapi; Mon, 18 Feb 2013 18:07:32 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: "payload@ietf.org" <payload@ietf.org>
Date: Mon, 18 Feb 2013 18:07:31 -0500
Thread-Topic: I-D Action: draft-lennox-payload-ulp-ssrc-mux-00.txt
Thread-Index: Ac4OLLg3u78rusOXT1udSw5FPXiOQg==
Message-ID: <CCDF0FE8-B4B8-4885-80BA-FB5288D420E3@vidyo.com>
References: <20130218225054.23444.52245.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [payload] Fwd: I-D Action: draft-lennox-payload-ulp-ssrc-mux-00.txt
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Payloads working group discussion list <payload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/payload>, <mailto:payload-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/payload>
List-Post: <mailto:payload@ietf.org>
List-Help: <mailto:payload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/payload>, <mailto:payload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Feb 2013 23:07:38 -0000

Hi, all --

Discussions at previous IETFs pointed out to me that RFC 5109 (the RTP Generic FEC payload) forbids using it in SSRC-multiplexing, even though RFC 5576 (SSRC attributes/groups) defines a semantic to permit exactly that.

This document updates RFC 5109 to permit source-multiplexing of FEC streams with the payloads they protect, so long as the associations between the FEC and original SSRCs are properly signaled.  This not only fixes the inconsistency between RFC 5109 and RFC 5576, but also permits FEC's use with other mechanisms for associating SSRCs in an RTP session, such as BUNDLE or SRCNAME.

Comments are welcome.

Begin forwarded message:

> From: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
> Subject: I-D Action: draft-lennox-payload-ulp-ssrc-mux-00.txt
> Date: February 18, 2013 5:50:54 PM EST
> To: "i-d-announce@ietf.org" <i-d-announce@ietf.org>
> Reply-To: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
> 	Title           : Supporting Source-Multiplexing of the Real-Time Transport Protocol (RTP) Payload for Generic Forward Error Correction
> 	Author(s)       : Jonathan Lennox
> 	Filename        : draft-lennox-payload-ulp-ssrc-mux-00.txt
> 	Pages           : 6
> 	Date            : 2013-02-18
> 
> Abstract:
>   The Real-Time Transport Protocol (RTP) Payload format for Generic
>   Forward Error Correction (FEC), specified in RFC 5109, forbids
>   transmitting FEC repair flows as separate sources in the same RTP
>   session as the flows being repaired.  This document updates RFC 5109
>   to lift that restriction, as long as the association between original
>   and repair flows is properly signaled and negotiated.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-lennox-payload-ulp-ssrc-mux
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-lennox-payload-ulp-ssrc-mux-00
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 

--
Jonathan Lennox
jonathan@vidyo.com