--
You received this message because you are subscribed to the Google Groups "blink-network-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-network-...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-network-dev/932783a5-d2cf-4f6a-b7a0-88d7212d9ec1%40igalia.com.
Hi,
For reference, here is the original design doc for the WebTransport throttling: https://docs.google.com/document/d/1u2kcv3YjvxMc91xylGAyhP1UhxAr2ZobgvCaL37AOUM/edit
I don't think I envisioned the P2P use case.
I believe that for the P2P use case the implementation of fine-grained penalties is the measure that would have more impact. We can agree that sending multiple connection requests to unrelated targets (different subnet) is not an attack and could be considered as a legit scenario, even if the failure rate is high. We can discuss in the design document about the numbers or different strategies, but I think we can start prototyping the idea and iterate from that.
About the rest of the mitigation strategies defined in the
document, we can implement it independently and evaluate later how
they work together and their impact on the P2P use cases and the
demos we have.
Best,
--
javi
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-network-dev/CAC_ixdwnpaa156XDoJfnrnVQe82qdU_R_xfxfDO2jXc34bk8KA%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "blink-network-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-network-...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-network-dev/c6e381ad-7ea7-4511-a81d-c9d10160f10a%40igalia.com.