3 ms·

While I suppose if you are in to nitpicking it's technically wrong but it's a generalisation that is excusable. It's not as if they are saying something inexcus

by rijoja 9y ago

While I suppose if you are in to nitpicking it's technically wrong but it's a generalisation that is excusable. It's not as if they are saying something inexcusably erroneous, like for example that JSON is the protocol used to route packets. In effect I'm pretty certain that the vast majority of ISPs are running their own DNS servers. Making this point rather unimportant. Any other technical inaccuracies?

betterunix2 9y ago
"It's not as if they are saying something inexcusably erroneous, like for example that JSON is the protocol used to route packets." They also suggested the DNS is like a proxy server (in their words, a "gateway") rather than a directory service. Does that count? "Any other technical inaccuracies?" That consumers continue to rely on transparent caching and that caching is a core ISP service. The FCC dismissed comments pointing out that TLS breaks transparent caching on the basis that there are websites that do not use TLS. The order also claims that because people are able to access websites via an ISP network, the ISP provides people with the capability of whatever those websites do (e.g. under the order's reasoning, Verizon is providing me with the capability to have this conversation with you). You can argue that is an opinion and not a fact, but the order does not apply it consistently; for example, it does not assert that a phone company is providing an information service by virtue of its customers' ability to use a dialup ISP. The order claims that by connecting to your ISP's network, you are receiving, "...computer access by multiple users to a computer server...that provides access to the Internet." Maybe that is just how the FCC interprets routers, but again it is not being consistently applied e.g. to the phone system. If you want more, go read the order; the technical analysis is not very long.
- rijoja 9y ago
  Yes referring to a DNS server as a gateway is obviously wrong. I'm not aware of how much caching is used, but to my knowledge is not that common as it would introduce a lot of problems for developers. This is also wrong. How much of their arguments are based on DNS and caching?

by rijoja 9y ago

betterunix2 9y ago

"It's not as if they are saying something inexcusably erroneous, like for example that JSON is the protocol used to route packets." They also suggested the DNS is like a proxy server (in their words, a "gateway") rather than a directory service. Does that count? "Any other technical inaccuracies?" That consumers continue to rely on transparent caching and that caching is a core ISP service. The FCC dismissed comments pointing out that TLS breaks transparent caching on the basis that there are websites that do not use TLS. The order also claims that because people are able to access websites via an ISP network, the ISP provides people with the capability of whatever those websites do (e.g. under the order's reasoning, Verizon is providing me with the capability to have this conversation with you). You can argue that is an opinion and not a fact, but the order does not apply it consistently; for example, it does not assert that a phone company is providing an information service by virtue of its customers' ability to use a dialup ISP. The order claims that by connecting to your ISP's network, you are receiving, "...computer access by multiple users to a computer server...that provides access to the Internet." Maybe that is just how the FCC interprets routers, but again it is not being consistently applied e.g. to the phone system. If you want more, go read the order; the technical analysis is not very long.

rijoja 9y ago
Yes referring to a DNS server as a gateway is obviously wrong. I'm not aware of how much caching is used, but to my knowledge is not that common as it would introduce a lot of problems for developers. This is also wrong. How much of their arguments are based on DNS and caching?