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

From: "Ali C. Begen (abegen)" <[email-masked]>
Date: Fri, 8 Mar 2013 22:17:02 +0000

I read the draft, it clearly does what it intends to do.

But note that the documents resulting from FECFRAME explicitly allowed for SSRC muxing. I am not sure how widely 5109 is implemented given that FECFRAME specified bunch of alternatives.

-acbegen 

On Feb 18, 2013, at 3:07 PM, Jonathan Lennox <[email-masked]> wrote:

> 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: "[email-masked]" <[email-masked]>
>> Subject: I-D Action: draft-lennox-payload-ulp-ssrc-mux-00.txt
>> Date: February 18, 2013 5:50:54 PM EST
>> To: "[email-masked]" <[email-masked]>
>> Reply-To: "[email-masked]" <[email-masked]>
>> 
>> 
>> 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
>> [email-masked]
>> 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
> [email-masked]
> 
> 
> _______________________________________________
> payload mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/payload