[httpapi] Re: httpapi - New Meeting Session Request for IETF 127

[Jaime Jiménez <[e-mail]>]

Hi chairs and Wg,

In relation to signs of interest in draft-gupta-httpapi-events-query before IETF 127.

I am using the draft in this API sandbox https://camara.jaime.win, as described in section 11.2 of the draft. We worked on it during the Vienna hackathon. My implementaiton now covers QUERY on the resource itself with Accept-Query discovery (section 7) on five resources, the three response modes (single notification in section 8, notifications stream in section 9, representation plus stream in section 10), negotiation of the carrier from Accept (multipart/mixed, application/json-seq, application/x-ndjson) and of the notification format from the events member of the subscription (section 6), and the Events header field (section 5).

Rahul wrote a confomance client against it (https://github.com/CxRes/CAMARA-events-query-client) If you use Agents you can try it, details are in https://camara.jaime.win/SKILL.md., logs are at https://camara.jaime.win/eqp-log. Details are in https://camara.jaime.win/SKILL.md.

I saw another thread here about the bounded duration as the only keep alive, for me that was not an issue but maybe there could be more guidance about that in the draft. 

My use case is mainly for AI Agents that need a lightweight observe mechanism on an async resource but that don't want to configure a public https callback uri, and want to use a simpler short-term observation mechanism. 

We had the same problem in RESTful IoT many years ago. CoAP now has Observe (RFC 7641) option for those in-band notifications, I was looking for the equivalent over HTTP, which -to my limited HTTP knowledge- httpapi-events-query seems to be the closest thing. Since the client is already authorized to access a resource, Events Query gives them also a uniform way to ask that resource for its current state and subsequent state changes.

So: I support adopting Events Query as a WG document. IMO it would be good to have it on the IETF 127 agenda and get more feedback and discussion from the group.

Ciao!
Jaime Jiménez