RIPT is trying to move real-time communiction off of SIP to HTTP, and this document gives some of the reasonings.
Sections 2.2 and 2.5 I have definitely felt the pain of in SIP.
Another useful RFC is this one on RIPP, which seems to be an extension of.
Specifically, RIPT runs on HTTP/3 (QUIC) which is itself pretty new and (AFAIK) not yet very widely deployed or supported. RIPT looks interesting, and it’s easy for me to believe that it would be a technical improvement over SIP, but I predict a long uphill slog to actually replace such an old and entrenched legacy protocol.
Yes, I completely agree. I am always surprised how non-technical people after they have a mobile app and/or web app for receiving and making calls, still ask for a regular desk phone too. I have experienced this many times. That’s one of your “long uphill slog”s right there. And I’m not trying to say it’s a bad thing. I understand the motive.