Re: New Draft: The Sustainability Well-Know URI

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).

Let me know if this would be ok.

Thanks,
Andrei.

On Sat, Mar 21, 2026, 16:34 Michael Sweet <msweet@msweet.org> wrote:

> Andrei,
>
> > On Mar 21, 2026, at 6:26 AM, Andrei Besleaga <andrei.besleaga@ieee.org>
> wrote:
> >
> > Hi everyone,
> > ​I have just uploaded version -03 of "The 'sustainability' Well-Known
> URI" (draft-besleaga-green-sustainability-wellknown-03).
> >
> > I am unsure if the generic 'Sustainability' naming would suffice or it
> should be changed to something like 'Environmental-impact' ?
>
> I am more OK with "sustainability" as IMHO "environmental-impact" places
> the emphasis on emissions over energy usage - both have a long-term impact
> on sustainability while energy usage may not have a
> direct/easily-reportable environmental impact.
>
> > ​This update incorporates several feedback and other issues found.
> Changes in this version include:
> >     • ​Privacy Protections: Explicit requirements for 1% noise injection
> (fuzzing) to prevent hardware fingerprinting.
> >     • ​Temporal Privacy: A new requirement that reporting granularity
> must not be finer than 24 hours to prevent real-time traffic correlation.
> >     • ​Security (DoS) Mitigation: Implementation of a 366-object cap for
> array responses and mandatory rate-limiting for query parameters.
> >     • ​Schema Alignment: Full synchronization between the JTD and CDDL
> formal definitions to ensure machine-readability.
> >     • ​Energy Metrics: Refined mandatory fields for energy-unit and
> carbon-unit to ensure global interoperability.
> > ​The draft aims to provide a standardized, out-of-band discovery
> mechanism for sustainability metrics (aligning it also with frameworks like
> the EU-CSRD and the GHG Protocol).
>
> I like all of these changes.
>
> I noticed that the quarterly reporting period syntax has been removed, but
> hadn't seen any discussion of the change? Just wondering since there isn't
> a "changes" section at the end of your drafts...
>
> ________________________
> Michael Sweet
>
>