[zAy0LfpBZLC8mAC]

Oh, I certainly didn't mean to imply that SIP was somehow particularly efficient - I was just surprised that anyone would think HTTP was an improvement over SIP, in particular given that you just swap the SIP stack for an HTTP stack and the torture testing of SIP parsers for torture testing of HTTP parsers, especially so if you consider the history of SIP where people originally intended SIP to be parsable using HTTP parsers.

As for the huge number of RFCs: Well, those do cover a whole lot more than passing blobs around? That aspect is fully covered by the SIP RFC, and only a relatively small part of it, the rest is concerned with session establishment and teardown, which HTTP obviously isn't concerned with at all.

Which is why I am wondering: What is the point of using HTTP? What is the functionality that it provides you with that would justify requiring an HTTP stack in every endpoint, including the security risk from all that complexity?

As for RESTfulness: REST is in conflict with a fixed URI scheme, REST allows only for a fixed entry point, beyond that, all other relevant URIs should be discoverable from the returned representations. And no, I am not saying, your stuff should be RESTful, I'm just saying that it's not.