[httpapi] Fw: New Version Notification for draft-gupta-httpapi-events-query-03.txt

[Rahul Gupta <[e-mail]>]

HTTPAPI Participants,

I have submitted -03 of the Events Query draft.

I would like to thank Jaime Jiménez for his independent implementation at <https://camara.jaime.win>.

Notable changes since -02:

+ Added agents as a use-case in intro.
+ A server implementing access control stops serving notifications if the request authorization is revoked or it expires. Response duration should try and take authorization duration into account.  

+ Out-of-Scope has been reorganized into three buckets. Rather than merely identifying items as out of scope, we explain how these can be extended.
+ A requested `duration = 0` now means that a server decides the duration. The concept of infinite duration has been removed.

All changes except the last address feedback from Jaime Jimenez.

As always, please keep the feedback coming!

Best Regards,
Rahul

------- Forwarded Message -------
From: [e-mail] <[e-mail]>
Date: On Monday, July 6th, 2026 at 12:08 AM
Subject: New Version Notification for draft-gupta-httpapi-events-query-03.txt
To: Rahul Gupta <[e-mail]>


> A new version of Internet-Draft draft-gupta-httpapi-events-query-03.txt has
> been successfully submitted by Rahul Gupta and posted to the
> IETF repository.
> 

> Name:     draft-gupta-httpapi-events-query
> Revision: 03
> Title:    HTTP Events Query
> Date:     2026-07-05
> Group:    Individual Submission
> Pages:    33
> URL:      https://www.ietf.org/archive/id/draft-gupta-httpapi-events-query-03.txt
> Status:   https://datatracker.ietf.org/doc/draft-gupta-httpapi-events-query/
> HTML:     https://www.ietf.org/archive/id/draft-gupta-httpapi-events-query-03.html
> HTMLized: https://datatracker.ietf.org/doc/html/draft-gupta-httpapi-events-query
> Diff:     https://author-tools.ietf.org/iddiff?url2=draft-gupta-httpapi-events-query-03
> 

> Abstract:
> 

>    Events Query is a minimal protocol built on top of HTTP that allows
>    user agents to receive event notifications directly from any resource
>    of interest.  It uses the QUERY method [RFC10008] to request
>    (optionally) the current representation and subsequent event
>    notifications within a single response.  The Events Query Protocol
>    (EQP) is predicated on the idea that the most intuitive source for
>    event notifications is the resource itself.
> 

> 

> 

> The IETF Secretariat
> 

> 

>