jlivingood / IETF-L4S-Deployment

IETF L4S Deployment Design Recommendations
15 stars 3 forks source link

draft-livingood-low-latency-deployment-03 edits and comments #55

Closed gregbo closed 6 months ago

gregbo commented 1 year ago

Here are a few comments on the draft:

I've also attached a unified diff of the text version of the draft and my edits.

draft-livingood-low-latency-deployment-03.diff.txt

jlivingood commented 6 months ago

Why is the draft called Comcast ISP Low Latency Deployment Design Recommendations? Aside from the Lotus report, I didn't see anything in the draft that was specific to Comcast ISPs.

Ack. Updating that in -05

jlivingood commented 6 months ago

Some of the language in §5.1 seems a bit strong. For example, I'd rephrase "will always make mistakes" as "could make mistakes."

Ack. Updating to soften.

jlivingood commented 6 months ago

A citation for the "majority of traffic is now encrypted" claim would strengthen it. For example, a 2020 Fortinet study gives a figure of 85% web traffic. A 2020 VMware study gives a figure of 80-90% web traffic.

Ack - will add cites

jlivingood commented 6 months ago

THANK YOU! Made changes from the diff file as well.