From firstname.lastname@example.org Mon Sep 30 19:05 PDT 1996
>I didn't know access service providers are not paid by their
>web browsing clients.
The cost of transaction is split between content providers and
clients. Is this that hard to understand?
I guess you missed the sarcasm. Try applying your statement
to your own argument and see who is trying to fleece whom? This is
homework. No need to fill up my mailbox anymore.
Heh. That's an example of how stupid technology is being
preserved by stupid legistlation. The laws regarding POTS are
generally legal fixes for techincal problems (like inability
to block annoying calls).
Forgotten the syn flood attack so quickly? Heard of IP spoofing?
FYI -- i had a more than an engineering role in service providers
covering together all time zones on this planet. One of them
was the first ISP in 16-odd countries. Another was the first
commercial DS-3 backbone in the world.
That does not make your one sided arguments stand any more than
they did. Goes to prove experience does not necessarily equate
insight into all aspects of the business. You have a stake in
perpetuating the status quo. Me in changing it because it
doesn't make sense.
So why you just don't learn why the present system is here,
and why it delivers while others only promise.
No, it is beginning to suck. Have you checked reliability
of the backbones lately? Sigh.. old hats like you have a
hard time realizing that old models have to, and will,
PS. This is my last email on this topic.
==>That does not make your one sided arguments stand any more than
==>they did. Goes to prove experience does not necessarily equate
==>insight into all aspects of the business. You have a stake in
==>perpetuating the status quo. Me in changing it because it
==>doesn't make sense.
Unfortunately, you can't change it unless you understand how the
OPERATIONAL aspects work. Vadim, Avi, Sean, Curtis, et al. have been
running networks for _years_ and understand what something means as an
impact. These are people who can fine-tune a little bit, and make a world
of difference with performance. Obviously a lot of the ideas in the mail
flood today were not thought up by people who run networks; just people
who want free connectivity everywhere. A few years ago it could be
understood that the "network engineer" you were talking to on the phone
was TRULY a network "engineer"--he/she understood impact and operational
aspects of everything; and also had half a clue when it came to working
with equipment. After all, most network engineers didn't have the
mentality that "the net" was this utopia, where everyone could do whatever
they wanted to, like some think of it today.
BGP was designed to give network operators control over how traffic goes
out of _AND_ into their networks. Which also means that if I want your
traffic to come in over what I have designed as the best route
into/through my network, so be it. It also means if I don't want your
traffic, so be it. I don't have to take it.
==>> So why you just don't learn why the present system is here,
==>> and why it delivers while others only promise.
==>No, it is beginning to suck. Have you checked reliability
==>of the backbones lately? Sigh.. old hats like you have a
Unfortunately, people who think non-operationally tend to have their heads
in the clouds. People who think both operationally and developmentally
are hard to find, but are the best at realizing better methods that are
"Old hats" might have a problem accepting some change, but they are a bit
wiser. Most "old hats" at least know what an RFC is. Or can at least
pass up marketing hype and find real-world results as a basis for judging
performance within a network (and I'm not just referring to hardware).
The problem is that "new hats" tend to re-invent the wheel way too many