[178582] in North American Network Operators' Group
Re: Verizon Policy Statement on Net Neutrality
daemon@ATHENA.MIT.EDU (Lyndon Nerenberg)
Sat Feb 28 19:20:17 2015
X-Original-To: nanog@nanog.org
From: Lyndon Nerenberg <lyndon@orthanc.ca>
Date: Sat, 28 Feb 2015 16:17:33 -0800
To: "North American Network Operators' Group" <nanog@nanog.org>
In-Reply-To: <21746.17258.270398.162820@world.std.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--Apple-Mail=_A8CAC1C7-7684-48BD-BDC6-62E20DC815C5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
> It's not about "that's all they need", "that's all they want", etc.
Whenever any vendor spouts "this is what our customers want" you know =
they are talking pure bullshit. The only customers who know what they =
"want" are the microscopic percentage who know what's actually possible, =
and we are dismissed as cranks. Even though they keep hiring us to run =
their networks.
In the spirit of adding real data to the symmetry conversation, let me =
describe why I would prefer symmetric.
Currently I have all-copper DSL running at 3 Mb/s down and about 640 =
Kb/s up. There are days I wish I had 1.5 Mb each way, as there are =
times when I need to push large files out (well in excess of 1 GB each). =
Doing that now is painfully slow, but I can live with the long transfer =
times because I'm not doing it every day. Where it is painful is how =
the clogged pipe breaks other things. The big one is my SIP phone =
service. Because the ACKs on the file upload come back faster than the =
data can leave, it's almost impossible to avoid queueing delays in my =
border router, despite it being a real UNIX box vs. a cheap appliance =
NAT router with buffer bloat. TCP doesn't deal well with the asymmetry, =
so the only way to address this is to drastically reduce the sendspace =
window on my uploading box in order to throttle it back to where TCP's =
flow control works as designed. So do I hack FTP and ssh on my machines =
to take a command line option to squash the sendspace? Or worse, do I =
use the existing knobs to turn sendspace down for the entire host?
Neither one is pleasant, and I shouldn't have to implement either. =
Having a DSL link that allocated bandwidth based on real-time need would =
solve this for me. But since that's not an option, converting the link =
I have from ADSL to SDSL would solve my problem. I would gladly trade =
in a portion of my downstream *bandwidth* for a corresponding reduction =
in my upstream *latency*.
And I suspect a lot of those bullshitting ISPs would find this is "what =
our customers want" if their customers ever learned that it is this =
asymmetry that underlies many of their perceived performance issues.
Mind you, the truly annoying part of this story (for me) is knowing =
Telus has fibre pedestals not a block away, with enough bandwidth to =
serve up IPTV to all the condos in the neighbourhood. But I'm in the =
marina across the street. Since there are only a handful of us here =
with service of any sort, they aren't about to come out and reroute us =
to the fibre pedestal. So I get to stay on the very long and corroded =
copper circuit back to one of the original downtown Vancouver exchanges. =
As one of the Telus techs said when he came out to help troubleshoot a =
failing DSL modem: I am amazed it works at all :-) And he's right -- =
the dB line losses are horrific.
--lyndon
--Apple-Mail=_A8CAC1C7-7684-48BD-BDC6-62E20DC815C5
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
iQIcBAEBAgAGBQJU8lqdAAoJEG8PnXiV/JnUqa4QAJr19HHZltOez09uxxQFsy14
zGyZ7Kc4RbYWu+1tTn1OpbuzHYhkAM1DQ5TjUlrr04pN/oy5bu473A+pwBcZrVoY
eyFWND8QZAecDW9C+usl8UftX1nK0EERpI4SJ4VaxqvxiOJMSd1v2mXJIjWi5888
AMCrBOo4lFTIbKumn/SIQ/9Ul7asjDHNtdGce2qhcp6gfap7LPVZdBFfwSyyOipD
9eb+MkLro3OnWZjoGmZb0t6YDPyJRQW8Fs1nc97G1Ik8+BQcsYrEQnxecU3LYZrL
FhWSegUgZTVAEDJEWEZ8JH8iyoHyvY+EG18OsjhITIdbJy6s8kNXkuYi4D361rvV
ltUZnlzLEGZG5zt4g9ybW0/3c/IqPPB+pG7HO5V9GZ1opkGH73DhGfmsgKdF6cmC
FcW4pHhkAwR8ju8jSWrRm+zQgbUSdfYRwNfBAJOSfk9AZARPDEc9W81yq988hdtg
SZnL0h1+WZA2Vzp3QCqnik3PSp7Q7gIuQftrC472cw+w/WAjXKs0VkBa2r/0ae+5
jXPMO1KY1Xar2WzRPCTLhnUbBQ5Op48Ep+kxh71BBhPQphfmaFBKPTjB6uQ6Rpru
9agAt/pmZULWzG+5yf76ftoqXjoNBI4ugzzpl6eDlQlTLohQeigVEcNkMyZsv+ZR
nMe6GmJPMpGOFSOLYv6j
=HNIw
-----END PGP SIGNATURE-----
--Apple-Mail=_A8CAC1C7-7684-48BD-BDC6-62E20DC815C5--