Re: [rtcweb] Same location media

Hadriel Kaplan <HKaplan@acmepacket.com> Thu, 20 October 2011 17:16 UTC

Return-Path: <HKaplan@acmepacket.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF51D21F8C0D for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 10:16:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.476
X-Spam-Level:
X-Spam-Status: No, score=-2.476 tagged_above=-999 required=5 tests=[AWL=0.123, BAYES_00=-2.599]
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 uBIQfcpKZyBz for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 10:16:55 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id DF95B21F8C0A for <rtcweb@ietf.org>; Thu, 20 Oct 2011 10:16:54 -0700 (PDT)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 20 Oct 2011 13:16:53 -0400
Received: from MAIL1.acmepacket.com ([169.254.1.230]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Thu, 20 Oct 2011 13:16:53 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Matthew Kaufman <matthew.kaufman@skype.net>
Thread-Topic: [rtcweb] Same location media
Thread-Index: AQHMj0wPU0CJsEVX60m8ZdgWcrqP2w==
Date: Thu, 20 Oct 2011 17:16:52 +0000
Message-ID: <BE42107B-AD91-4770-A88C-8A1F6899ADB5@acmepacket.com>
References: <CAD5OKxuJi_VS9fRc4P6GN-StWzMhMHAQ2MyO8zJVsMfEeQRftg@mail.gmail.com> <4EA050E9.6000705@skype.net>
In-Reply-To: <4EA050E9.6000705@skype.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.0.0.30]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <F0675EDE2671AB44A7F787086AAF305D@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Same location media
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Oct 2011 17:16:55 -0000

I may be mis-understanding what type of consent you folks are talking about, but RTMP is over TCP.  
For any TCP-based mechanism, you get some "consent" from the TCP SYN/ACK you get back from the far end, as opposed to say an ICMP port error.  Since the TCP layer won't send data until that, it's a natural consent gate.

RTMFP uses UDP but I believe there is in fact a handshake required in the beginning and that's effectively consent.
 
-hadriel


On Oct 20, 2011, at 12:48 PM, Matthew Kaufman wrote:

> Flash can send media to ANY server that accepts the RTMP or RTMFP connection. (And obviously it can attempt to open a connection to any address using these protocols.)
> 
> The server can then examine headers to determine where the SWF file came from, etc.
> 
> The "consent" model for Flash is that if you speak RTMP or RTMFP, you understand what that is... and neither protocol looks like anything else on the wire.
> 
> Matthew Kaufman
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb