What relevance does this have to the NANOG community?
rob
I thought someone here might be interested, even just for
informational purposes, in the operational problems Sprint is causing
in the north american network with their negligent and/or incompetent
network administration.
As of 20:27 EST that mailer loop was still running full bore, about 6
hours after Sprint acknowledged the specific problem report (which
they waffled on), and documentably over 24 hours after their staff
acknowledged the general problem in public (that is, the specific
incident was no surprise, they've been talking about this site's
outrageous behavior for at least a full day, I have the mail.)
But go ahead, tell your customers that slow-downs and congestion on
the net are due to mere demand, and we'll all keep conspiratorially
quiet about how arrogant, incompetent billion dollar plus corporations
refuse to lift a finger to resolve egregious problems even when it's
laid out to them as clearly as can be and theyre given 24+ hours to
respond. It's better PR, huh, <wink wink>? Let's keep up that illusion
of all being good-spirited and pulling our weight for the common good
of the net, even if it is just bullshit (at least in part), otherwise,
who knows, someone might lose faith and someone like Bob Metcalfe
might write another article just scaring people...can't have that,
must keep up appearances! Must hold firm to the claim that we're all
rowing as fast as we can! (Some of us certainly are, not my point.)
As I write this it's *conceivable* the loop has been stopped, I just
checked, but how many here think this development might have just a
tiny bit to do with embarrassing Sprint in public? Hands? Yeah, I
thought so.
I dunno what the hell else to do, to be frank, I really don't. Maybe
public embarrassment will work, at least I was decent enough to try to
keep my first shot in front of a highly technical audience who can
understand exactly what's going on here and keep it all in
perspective.
If I upset anyone (outside of Sprint), I apologize.
Barry Shein writes:
As I write this it's *conceivable* the loop has been stopped, I just
checked, but how many here think this development might have just a
tiny bit to do with embarrassing Sprint in public? Hands? Yeah, I
thought so.
How about a dose of realism here:
The people that need to make the decision to act on this kind of
situation probably do not read the nanog mailing list. The people
that do read the nanog mailing list have most likely already brought
the situation to the right folks attention if what you say is true.
So an attempt at embarrasing Sprint here will most likely have no
effect.
-Hank
*speaking for myself and not my employer*
Let me propose a different reason for posting this here. I recognize this
is not the stop-spam list. It is, however, operational. Barry originally
raised the issue Sprint was "trying to read the mind of their client." Two
people responded they had been spammed heavily from the same source, two
people not at world.std.com. I just got hit again; the addressee list, I
think, is recent posters on comp.dcom.sys.cisco.
These reports help give ammunition to pass back to Sprint that this is not
an isolated incident.
> Barry Shein writes:
> >As I write this it's *conceivable* the loop has been stopped, I just
> >checked, but how many here think this development might have just a
> >tiny bit to do with embarrassing Sprint in public? Hands? Yeah, I
> >thought so.
>
> How about a dose of realism here:
>
> The people that need to make the decision to act on this kind of
> situation probably do not read the nanog mailing list. The people
> that do read the nanog mailing list have most likely already brought
> the situation to the right folks attention if what you say is true.
> So an attempt at embarrasing Sprint here will most likely have no
> effect.
You forgot the part about this going on for the past 48 hours with no
action, then suddenly on a Friday night the dams break.
Ok, have it your way if you like your story better.
Right, exactly, it's possible that someone's attempt at spam can
become an out of control operational problem when thousands of mail
msgs are looping uncontrollably and non-stop for 48+ hours. That's
all, that's what happened, the guy crossed a line from simple spamming
to obviously out of control behavior. What's the rationale, that he
likes to get thousands of mail bounces? That this is his business?
I brought this here precisely because it had become, in my opinion, an
operational problem and had ceased to be a simple spam, and Sprint was
being non-responsive AS A MATTER OF POLICY. That's a problem.
Ya know, folks, this isn't the only spam I've ever encountered,
believe it or not.