Re: [payload] Self-describing streams?
"Dave Satterlee (Vocal)" <Dave.Satterlee@vocal.com> Wed, 02 May 2018 18:45 UTC
Return-Path: <Dave.Satterlee@vocal.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 B8969126C22 for <payload@ietfa.amsl.com>; Wed, 2 May 2018 11:45:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yluHEF6k8RJX for <payload@ietfa.amsl.com>; Wed, 2 May 2018 11:45:15 -0700 (PDT)
Received: from host105.olm1.com (host105.olm1.com [72.236.255.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEBF312DA01 for <payload@ietf.org>; Wed, 2 May 2018 11:45:14 -0700 (PDT)
Received: from [192.168.11.222] (rrcs-72-43-202-98.nys.biz.rr.com [72.43.202.98]) by host105.olm1.com (Postfix) with ESMTPSA id DD530B47B3C for <payload@ietf.org>; Wed, 2 May 2018 14:45:13 -0400 (EDT)
To: "payload@ietf.org" <payload@ietf.org>
References: <4C57D680-D676-45AA-8510-31A22EAC57CF@foxeg.com>
From: "Dave Satterlee (Vocal)" <Dave.Satterlee@vocal.com>
Openpgp: preference=signencrypt
Organization: Vocal Technologies
Message-ID: <e81f7bbc-6b33-0c55-4d91-1ae4740b2941@vocal.com>
Date: Wed, 02 May 2018 14:45:14 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <4C57D680-D676-45AA-8510-31A22EAC57CF@foxeg.com>
Content-Type: multipart/alternative; boundary="------------8D003FCEC25DF762D08F58A5"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/payload/R5mEeebwMnO7RMlPmduDa5Z4JAw>
Subject: Re: [payload] Self-describing streams?
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 02 May 2018 18:45:18 -0000
Hi Thomas, I find your question interesting as well. I think at least some of the history that you are looking for can be found here: https://datatracker.ietf.org/doc/draft-ietf-avt-issues/ This document certainly gives a lot of context regarding what the authors of RTP were thinking while designing it. It seems that much of what they were concerned with was keeping it light, and giving the applications flexibility. This document, referenced by the RFC1889 also helps paint the picture: https://groups.csail.mit.edu/ana/Publications/PubPDFs/Architectural%20Considerations%20for%20a%20New%20Generation%20of%20Protocols.pdf I too would be interested in the input/opinions of others who have some knowledge of the history. Regards, Dave Satterlee VOCAL Technologies On 2/28/2018 2:45 PM, Thomas Edwards wrote: > > I have a historical/theory question. > > > > It is clear that IETF has chosen to separate the data of RTP streams from their > technical metadata (generally found in SDP). > > > > Does anyone have the ability to sum up the reason for this decision? > > > > Thanks! > > > > -- > > Thomas Edwards > > FOX Networks Engineering & Operations > > VP Engineering & Development > > thomas.edwards@fox.com > > +1-310-369-6696 > > 10201 W Pico Blvd > > Los Angeles, CA 90035 > > > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > Virus-free. www.avg.com > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > > _______________________________________________ > payload mailing list > payload@ietf.org > https://www.ietf.org/mailman/listinfo/payload
- [payload] Self-describing streams? Thomas Edwards
- Re: [payload] Self-describing streams? Dave Satterlee (Vocal)