- From: Andrei Besleaga <andrei.besleaga@ieee.org>
- Date: Sun, 22 Mar 2026 13:55:43 +0200
- To: Michael Sweet <msweet=40msweet.org@dmarc.ietf.org>
- Cc: green@ietf.org, ietf-http-wg@w3.org
Received on Sunday, 22 March 2026 11:56:00 UTC
Yes, I think having the basic/extended capabilities and schema versioning would allow any further improvements (even after/if becomes a standard). Thank you, Andrei. On Sat, Mar 21, 2026, 22:13 Michael Sweet <msweet= 40msweet.org@dmarc.ietf.org> wrote: > Andrei, > > > On Mar 21, 2026, at 12:02 PM, Andrei Besleaga <andrei.besleaga= > 40ieee.org@dmarc.ietf.org> wrote: > > > > Thanks Michael, > > > > About the Quarterly I removed it since I thought would be better for the > standard to cover "normal dates" (from the RFC datetime format and easier > for implementing technically in some universal SQL/NoSQL formats). > > > > Also was thinking if there is already a yearly query param period (with > monthly granularity), and is in recommendations to have the yearly stuff > cached, then maybe this would suffice to have only yearly, monthly, daily > (with monthly/daily granularity), would cover all cases (up to a year), and > optimized enough for same further queries (and if an auditor would want a > larger period than monthly or some days, they probably would want longer > periods, they would derive easily from 12 months result, the 4 quarters). > > That will probably be sufficient, but we can always extend things later as > needed... > > ________________________ > Michael Sweet > >
Received on Sunday, 22 March 2026 11:56:00 UTC