Adding the support of SSE

[edsummit]

Hi CAMARA API Working Group,

I would like to suggest that the CAMARA specifications consider Server-Sent Events (SSE) as an alternative to WebSockets.

Why SSE may be a better fit than WebSockets for many CAMARA use cases:

1.	Native browser support – SSE works out-of-the-box in all major browsers via the EventSource API. No extra libraries or polyfills are required, which lowers integration friction for developers building web apps that consume CAMARA events.

2.	Simplicity of the protocol – SSE is just an HTTP connection with text/event-stream. It's far easier to implement and debug than WebSockets, both on the client and server side.

3.	Built-in reconnection and event IDs – SSE supports automatic reconnection and last-event ID tracking without requiring custom logic, which is ideal for long-lived telecom event streams such as QoD updates, device location events, or SMS delivery notifications.

4.	Better fit for unidirectional notifications – Many CAMARA APIs push events from operator → application only. WebSocket's bidirectional complexity adds unnecessary overhead in cases where the client does not need to send messages back. SSE aligns naturally with this one-way communication pattern.

5.	Interoperability with existing webhook model – Since CAMARA already delivers asynchronous events via HTTP callbacks, adding SSE would be a lightweight, complementary approach. Operators can still support webhooks for backend systems, while frontend developers can directly subscribe with SSE without standing up additional infrastructure.

6.	Easier scaling and deployment – SSE works over standard HTTP/2/3, fits within CDN/proxy infrastructure, and avoids the connection management complexity that WebSockets often face in enterprise and telco environments.

Introduce SSE as a supported notification channel in CAMARA APIs (e.g., alongside webhooks). This would give developers flexibility to choose between:

•	Webhooks for backend event ingestion
•	SSE for lightweight, browser-friendly consumption
•	WebSockets only where true bidirectional communication is required

This addition would make CAMARA APIs more accessible, particularly for frontend and real-time web developers, while reducing integration barriers.

Thank you for considering this proposal. I'd be happy to provide further technical details or examples if helpful.