David Kaiser <dkai...@cdk.com> wrote:

> Welcome to one of the obvious reasons to be in support of net
> neutrality.  [...]
> (I don't think any
> ISP understands the concept of not biting the hands that feed it.)

<soapbox>

This sort of BS on the part of "consumer" ISPs is exactly the reason why
I am very happy with my business SDSL @ 384 kbps and why I will never
switch to a "fast" and cheap "residential" type of service.  Yes, I am
paying about $180/month for 384 kbps symmetric, but I am very, very,
very happy with it and I will never, ever, ever switch to ACF.

My new slogan is "say no to ACF!", where ACF stands for "ADSL, cable and
FiOS", i.e., the residential consumer-oriented Internet services where
the ISPs routinely pull shit like restricting ports, prohibiting you
from running servers, hijacking outbound connections to their proxy, and
other non-neutral behavior.  *REAL* Internet services, the kind that
cost $180/month for 384 kbps and go up from there, never do any such
shit!

My ISP is Verizon Business, former UUNet, and with my SDSL I am tied
directly into the Tier 1 backbone.  It is a true business service of the
old-fashioned clueful-user kind.  They provide only raw bandwidth and
nothing else, total neutrality.  I've got a /24 IP netblock with this
service - back when I first signed up, it was given standard with
certain business services with no justification required.  Whatever
packets the Big Bad Internet sends to my /24, they get routed down my
SDSL/ATM pipe in the standard RFC 1483 routed encapsulation, none of
that MAC or "bridged" encapsulation stuff, true L3 IP routing.  No
filtering of any kind; if I want filtering, it is my responsibility to
configure it on my own router.

And yes, I am responsible for maintaining my own router, a true router
with a non-Ethernet WAN interface.  Now that I've got a CSU/DSU for SDSL
of my own design and make, I will soon be replacing the stupid Netopia
with a real Cisco router (Ethernet LAN on one side, non-Ethernet WAN on
the other side), attached to the SDSL copper pair via my very own DSU.

Oh, and there is absolutely no need for me to hide what I am doing
(using SDSL CPE of my own design and make) from my ISP: all major SDSL
DSLAM operators in the country are already very familiar with my project
and even had discussions with me about the possibility of my little
company supplying CPE to them.  And my SDSL work has got a decent Google
search rank too: if one searches for "Nokia SDSL" or "Copper Mountain
SDSL" (these are the two dominant flavors), my site will be the very
first hit in the Google search results - try it!  Oh, and the site in
question (both authoritative DNS servers for the domain and the actual
HTTP server) is served via my SDSL pipe - no problem with that
whatsoever, that's the whole point of a *REAL* business Internet
service.

Say no ACF!  T1s and SDSL rule!  Screw the "residential consumer" crap,
business Internet rules!  Yes, it's a little slow at 384 kbps and a
little on the expensive side at $180/month, but I would much rather put
up with a little slowness and pay a little extra to have *REAL* Internet
service, not this neutrality-challenged ADSL/cable/FiOS stuff you all
are using.

</soapbox>

MS
_______________________________________________
LinuxUsers mailing list
LinuxUsers@socallinux.org
http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers

Reply via email to