W3C home > Mailing lists > Public > public-webrtc@w3.org > October 2012

RE: Proposal for support of RTMP

From: Matthew Kaufman <matthew.kaufman@skype.net>
Date: Wed, 17 Oct 2012 21:01:38 +0000
To: Alexey Aylarov <alexey@zingaya.com>, Harald Alvestrand <harald@alvestrand.no>
CC: "bouras@cti.gr" <bouras@cti.gr>, "public-webrtc@w3.org" <public-webrtc@w3.org>, Vaggelis Kapoulas <kapoulas@cti.gr>, Andreas Papazois <papazois@ceid.upatras.gr>, "AShani@exent.com" <AShani@exent.com>
Message-ID: <AE1A6B5FD507DC4FB3C5166F3A05A484160ED675@tk5ex14mbxc272.redmond.corp.microsoft.com>
RTMFP is complicated. But I wouldn't say "too complicated"... in fact it is probably less complicated than SDP O/A + RTP + SRTP + DTLS-SRTP + ICE + SCTP, which you'd need all of and then some to replicate what it does.

Also, I don't know why you'd say "offers too big overhead (compared to RTP)"... in fact, the overhead for transmitting media streams over RTMFP is lower than an equivalent RTP session.

As for it being a proprietary protocol, this is true, but something Adobe could remedy if they so desired.

Matthew Kaufman

-----Original Message-----
From: Alexey Aylarov [mailto:alexey@zingaya.com] 
Sent: Tuesday, October 16, 2012 10:05 AM
To: Harald Alvestrand
Cc: bouras@cti.gr; public-webrtc@w3.org; Vaggelis Kapoulas; Andreas Papazois; AShani@exent.com
Subject: Re: Proposal for support of RTMP

RTMP is out of date already, using TCP-based protocol for real time audio and video communication isn't a good idea

Adobe has implemented RTMFP protocol in Flash (ver. higher or equal to 10), it is UDP-based and supports p2p, but it's proprietary protocol that can't be use as a standard for W3C and IETF. More of that, it's too complicated and offers too big overhead (compared to RTP)

It's better to focus on WebRTC development

Best Regards,

Oct 16, 2012, Χ 8:01 PM, Harald Alvestrand <harald@alvestrand.no> ΞΑΠΙΣΑΜ(Α):

> Sorry to be discouraging, but I think this is outside the scope of our present work.
> As presented in your document, RTMP is a server-based protocol. The charter of this WG is for peer-to-peer work.
> Also, protocol work should go to the IETF, not to the W3C.
> If the group is rechartered to take on server-based work, it is possible that we may return to this issue.
>                   Harald Alvestrand
> On 10/16/2012 02:51 PM, bouras@cti.gr wrote:
>> Dear Working Group Members,
>> I send you this email on behalf of Computer Technology Institute and Press (CTI) "Diophantus" (http://www.cti.gr/) a member of "The Community Network Game" (CNG) project's consortium (http://www.cng-project.eu/). CNG is a research and development project funded by European Commission under FP7/ICT programme.
>> During our research and development work in CNG, one of the activities we are responsible for is the identification of possible contribution to standards. Given that our work also included research and development activities on Web Technologies we have the following interesting idea that may contribute to your standardization processes within W3C.
>> Our idea is the support of Real-Time Messaging Protocol (RTMP) in the future JavaScript standard. RTMP is a protocol developed by Adobe for the support of a higher-level multimedia stream.
>> Kindly find more information in the attached document.
>> I am available to provide you any further information on this.
>> Sincerely,
>> Christos J. Bouras
Received on Wednesday, 17 October 2012 21:02:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:34 UTC