Networking/DNS/Prefetching: Difference between revisions

m
(Created page with "Prefetching-related bugs * {{Bug|40082}} - Domain Guessing: should call resolver explicitly (and not trigger DNS search domains) * {{Bug|481503}} - do DNS prefetch for awesomebar...")
 
 
Line 20: Line 20:


=== Suggestions for moving forward ===
=== Suggestions for moving forward ===
* User Study
* Categorize prefetching options according to privacy-risk.
 
* User Study for grey areas
Find out about users' comfort level with DNS prefetching; speed versus leaking tracking information.
Find out about users' comfort level with DNS prefetching; speed versus leaking tracking information.
* Telemetry Data
* Telemetry Data for Measurable Improvements
Put together some math theory to describe variables etc. and get telemetry based on this for real world, useful values.  This data may be more helpful for the user study to present hard numbers for consideration.
** Put together some math theory to describe variables etc. and get telemetry based on this for real world, useful values.
* Once both of those are done, an informed decision can be made and referred to in the future.
** Modeling (using Tp list of sites - getting DNS depends on DNS server, but each site will have a different number of DNS RTT depending on number of links etc.) Different models depending on different solutions.
** May be overkill to get too much data: basic knowledge of HTTP networking is enough to show that getting DNS results earlier is better.  But, it would be good to have some data to measure and present improvement (or potential improvement if a user study were needed).
88

edits