Re: [payload] I-D Action: draft-lennox-payload-ulp-ssrc-mux-00.txt
"Ali C. Begen (abegen)" <abegen@cisco.com> Fri, 08 March 2013 22:17 UTC
Return-Path: <abegen@cisco.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 64C5421F85B8 for <payload@ietfa.amsl.com>; Fri, 8 Mar 2013 14:17:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.399
X-Spam-Level:
X-Spam-Status: No, score=-10.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 zDku6k6YR+Yt for <payload@ietfa.amsl.com>; Fri, 8 Mar 2013 14:17:03 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id C0BE721F8598 for <payload@ietf.org>; Fri, 8 Mar 2013 14:17:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3107; q=dns/txt; s=iport; t=1362781023; x=1363990623; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=WkTnMPbO8gRU9/1J4lH4mlbVymNR7pJmrDnzjfMd+20=; b=B/PgloStAfZyKn15um8JmXzPFoS1TORTWLeMeXf3WNO7efTf8P5RP4sB bScIFw9/3Zy2MtgXGncmDitdy+2Ym8tpFJZ1co3YqfDixGwZk5kKOtZ7d 0BzLI36deTBx57Y8pW6y4w5UIPv5rida5u3O02vMzG3QaqqV3ir4MHgU5 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAE1iOlGtJV2d/2dsb2JhbABDhDjAF4FdFnSCLAEBAQMBAQEBNzQLBQsCAQgRAwECCxQQJwsUCQgBAQQOBQgBiAQGAQu7eI5ZAiYLAgUGgllhA5dxij+FFYMKgic
X-IronPort-AV: E=Sophos;i="4.84,810,1355097600"; d="scan'208";a="185507398"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-6.cisco.com with ESMTP; 08 Mar 2013 22:17:03 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r28MH3GE005334 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 8 Mar 2013 22:17:03 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0318.004; Fri, 8 Mar 2013 16:17:03 -0600
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: Jonathan Lennox <jonathan@vidyo.com>
Thread-Topic: [payload] I-D Action: draft-lennox-payload-ulp-ssrc-mux-00.txt
Thread-Index: Ac4OLLg3u78rusOXT1udSw5FPXiOQgN9cqiA
Date: Fri, 08 Mar 2013 22:17:02 +0000
Message-ID: <C15918F2FCDA0243A7C919DA7C4BE9940CF4DA0B@xmb-aln-x01.cisco.com>
References: <20130218225054.23444.52245.idtracker@ietfa.amsl.com> <CCDF0FE8-B4B8-4885-80BA-FB5288D420E3@vidyo.com>
In-Reply-To: <CCDF0FE8-B4B8-4885-80BA-FB5288D420E3@vidyo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.155.152.107]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BDE10A9D831BE843939C0CECD2011AAC@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "payload@ietf.org" <payload@ietf.org>
Subject: Re: [payload] 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: Fri, 08 Mar 2013 22:17:04 -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 <jonathan@vidyo.com> 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: "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 > > > _______________________________________________ > payload mailing list > payload@ietf.org > https://www.ietf.org/mailman/listinfo/payload
- [payload] Fwd: I-D Action: draft-lennox-payload-u… Jonathan Lennox
- Re: [payload] I-D Action: draft-lennox-payload-ul… Ali C. Begen (abegen)