Re: [V3] RIPT BoF approved for IETF 107 - Draft charter below

["Asveren, Tolga" <[e-mail]>]

“Firstly, we assume that all of the servers sit behind HTTP load balancers, and are not reachable directly. This is standard practice.”

I would like to point out that this is an important assumption and does not entirely overlap with reality. Application specific and L4 load balancers are used widely in Cloud deployments for real-time sessions. I doubt standard HTTP  load balancers can be used as is even if all real time session messaging (signaling, media, …) is HTTP based. Required semantics, e.g. different treatment based on RPH, overload control etc…,  are simply different than what is needed/used/sufficient for standard Web applications.

On another note, a core issue for Cloud load balancing is failure detection/failover time for back ends servers. This again is an area where “just using HTTP” wouldn’t help.

Having “HTTP only” as a core principle is fine but I think the rationale for that should be articulated more in detail and clarity.

Thanks,
Tolga

From: V3 <[e-mail]> On Behalf Of Ross Finlayson
Sent: Wednesday, February 19, 2020 9:52 AM
To: Jonathan Rosenberg <[e-mail]>
Cc: Cullen Jennings (fluffy) <[e-mail]>; Jonathan Rosenberg <[e-mail]>; [e-mail]; Spencer Dawkins at IETF <[e-mail]>; Justin Uberti <[e-mail]>
Subject: Re: [V3] RIPT BoF approved for IETF 107 - Draft charter below

________________________________
NOTICE: This email was received from an EXTERNAL sender
________________________________



> On Feb 20, 2020, at 3:01 AM, Jonathan Rosenberg <[e-mail]<mailto:[e-mail]>> wrote:
>
> Firstly, we assume that all of the servers sit behind HTTP load balancers, and are not reachable directly. This is standard practice. That means that clients have to send media through HTTP. Secondly, we assume that sticky routing happens in these load balancers the ‘normal’ way – through a combo of hashing of 5-tuples and usage of session cookies. That means that, in order to get the media to the server handling the signaling (which is what we want), the media needs to come in the same connection, and use cookies. This further ties it to HTTP. In order to deal with failures of those servers and enable mid-call recovery without loss of media packets, we also need the transport to contain call identifiers. This way, media can just ‘be sent’ to a new server in the pool behind the load balancer, and it can pick up where things left off in the previous server without losing any media packets (like - not one). In RIPT this happens because all media are PUT/GET from the call URI.

OK, thanks - this explanation makes it very clear that what you’re planning is a protocol for audio/video calls *over HTTP* - and over HTTP only. A lot of the confusion (largely on my part, I admit) about what you’re proposing would have been avoided if this had been clearer in the name of the protocol (and BOF) - i.e., if there had been an “H” in there (I would have preferred something like MoH: “Media over HTTP” :-)

And grandiose statements about this protocol "replacing SIP, RTP and SDP” don’t help either - unless you really see the “HTTP Internet” (hourglass) becoming the entire Internet. (Not all of us are ready to concede that, just yet ;-)


Ross Finlayson
Live Networks, Inc.
http://www.live555.com/<http://www.live555.com/>

--
V3 mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/v3<https://www.ietf.org/mailman/listinfo/v3>


-----------------------------------------------------------------------------------------------------------------------
Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. that
is confidential and/or proprietary for the sole use of the intended recipient.  Any review, disclosure, reliance or
distribution by others or forwarding without express permission is strictly prohibited.  If you are not the intended
recipient, please notify the sender immediately and then delete all copies, including any attachments.
-----------------------------------------------------------------------------------------------------------------------