Re: [rtcweb] Same location media

[Michael Thornburgh <[e-mail]>]

correct. RTMP is over TCP to a server, and has the TCP handshake *plus* the RTMP handshake *plus* any application-level authentication required by the RTMP server.

RTMP can also be tunneled over HTTP.

RTMFP is over UDP and has its own 4-way handshake (see Matthew's presentation to tsv-area at IETF 77 for what that handshake looks like). when communicating with a server, a client must perform the RTMFP handshake plus any application-level authentication required by the server. to communicate with a peer (another client), a client must perform the RTMFP handshake with that peer, which requires knowing that peer's unique cryptographic peer ID. the handshake won't work if the destination doesn't speak RTMFP or if the destination isn't the peer that the initiator is trying to reach.

-mike

On Oct 20, 2011, at 10:17 AM, Hadriel Kaplan wrote:

> 
> 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