From 1d55881a320c34f33b49e436999893ea98a0f7ba Mon Sep 17 00:00:00 2001
From: "Arnaud (Arno) Mandy"
Date: Fri, 3 Nov 2023 13:33:11 +0200
Subject: [PATCH] Provide guidelines for mitigation algorithms (#241)
Provide parameter values for mitigation algorithms
This patch is providing normative and non-normative numerical values for
the mitigation algorithms parameters. [1]
[1] https://github.com/w3c/compute-pressure/issues/197#issuecomment-1698413311
Fixes: #240
---
index.html | 50 +++++++++++++++++++++++++++++++++++++++++++++++---
1 file changed, 47 insertions(+), 3 deletions(-)
diff --git a/index.html b/index.html
index fedc478..ce37f76 100644
--- a/index.html
+++ b/index.html
@@ -883,7 +883,7 @@
Supporting algorithms
set |observer|.{{PressureObserver/[[ObservationWindow]]}} to an [=implementation-defined=] randomized integer value in
- milliseconds within an [=implementation-defined=] range, e.g., random between 300000 and 600000 (5 and 10 minutes).
+ milliseconds within an [=implementation-defined=] range.
set |observer|.{{PressureObserver/[[MaxChangesThreshold]]}} to an [=implementation-defined=] randomized integer
@@ -1429,6 +1429,39 @@
Rate obfuscation
received from the platform collector during this penalty.
+
+
Rate obfuscation normative parameters
+
+ Based on implementation experience, implementers must use:
+
+
+ a range in between 50 and 100 changes for PressureObserver's {{PressureObserver/[[MaxChangesThreshold]]}} internal slot.
+
+
+ a range in between 5000 milliseconds and 10000 milliseconds for PressureObserver's {{PressureObserver/[[PenaltyDuration]]}} internal slot.
+
+
+
+
+
+
+
Rate obfuscation non-normative parameters
+
This section is non-normative.
+
+ Based on implementation experience, implementers are advised to use:
+
+
+ a range in between 300000 milliseconds (5 minutes) and 600000 milliseconds (10 minutes) for PressureObserver's
+ {{PressureObserver/[[ObservationWindow]]}} internal slot.
+
+
+
+
+
Break calibration
@@ -1442,14 +1475,25 @@
Break calibration
at runtime when this mitigation is running continuously. Any attempts to recalibrate
will similarly be mitigated against.
-
+
+
+
+
+
Break calibration parameters
+
This section is non-normative.
+
+ Based on implementation experience, implementers are advised to apply the mitigation
+ to a randomized time value within a range between 120000 milliseconds (2 minutes) and 240000 milliseconds (4 minutes).
+