RE: [Asrg] Spam, defined, and permissions
2004-12-28 08:51:05
-----Original Message-----
From: asrg-bounces(_at_)ietf(_dot_)org
[mailto:asrg-bounces(_at_)ietf(_dot_)org]On Behalf Of
Devdas Bhagat
Sent: Tuesday, December 28, 2004 10:06 AM
To: asrg(_at_)ietf(_dot_)org
Subject: Re: [Asrg] Spam, defined, and permissions
On 28/12/04 09:46 -0500, Hannigan, Martin wrote:
<snip>
And exactly how does the telco propose to enforce my
usage of their
server? Post 25 blocks? I just use another port, or I VPN.
We could play this circle game all day. At some point you're
going port 25. If you VPN to someone elses system, fine, but they
end up paying for your traffic if you break their cap.
My point is that I control both ends of the VPN, and I have no caps at
either end.
So what?
We can play this game all day. Try to
understand where I am coming from before you decide to continue
to play this losing game and waste both of our efforts:
1. The rest of the world is the target, the 99.99999% of
people who simply use Windows and browsers for most of
what they need. Not the .00000001% who are unix genii,
illuminati, or other highly sophisticated users of the network.
They have their place, but it's not dictating the market.
[ BTW: For the non MSEX users, Devdas has a cute "flag" that
notes "Friends protect friends from Microsoft" it shows up
like an advertising banner (spam) in my client - this is fine
for egocentric discussion, but it's not a realists view -M< ]
2. Spending time developing client side fixes outside of secure systems
is a waste of time. Market force already handles the secure systems
aspect.
3. Most of the solutions out there today, RBL, xBL, DNSBL,
etc. are well intentioned but misplaced shows of strength and would've
been better served higher up in the network and more effective in
the hands of business people i.e. understands how nsp's work, capex,
opex, operations, etc. Most do not. The frothy (well intentioned) people
of the early years hurt us all and made it near impossible to make
any progress any higher up in the network as a result.
4. The Internet is _still_ in it's infancy and it's made it past the
"interesting toy" stage to a fully ingrained commerce network.
5. Anything that has the potential to impact a providers bottom
line _and_ improve service capability will get attention. Most
will fail. Some will be taken serious. One may even make it into
serious consideration.
How much more do I need to explain to you, Devdas? Every scenario you
brought up, and can bring up, is resolvable through billing, operational
approach, or regulatory action.
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Asrg] Spam, defined, and permissions, (continued)
- RE: [Asrg] Spam, defined, and permissions, Hannigan, Martin
- RE: [Asrg] Spam, defined, and permissions, Hannigan, Martin
- Re: [Asrg] Spam, defined, and permissions, Devdas Bhagat
- Re: [Asrg] Spam, defined, and permissions, Barry Shein
- Re: [Asrg] Spam, defined, and permissions, James Lick
- Re: [Asrg] Spam, defined, and permissions, Barry Shein
- Re: [Asrg] Spam, defined, and permissions, Daniel Feenberg
- Re: [Asrg] Spam, defined, and permissions, Laird Breyer
RE: [Asrg] Spam, defined, and permissions,
Hannigan, Martin <=
Re: [Asrg] mail metering, was Spam, defined, and permissions, John Levine
RE: [Asrg] Spam, defined, and permissions, Hannigan, Martin
RE: [Asrg] Spam, defined, and permissions, Hannigan, Martin
Re: [Asrg] Spam, defined, and permissions, gep2
|
Previous by Date: |
Re: [Asrg] Spam, defined, and permissions, Devdas Bhagat |
Next by Date: |
Re: [Asrg] Spam, defined, and permissions, Devdas Bhagat |
Previous by Thread: |
Re: [Asrg] Spam, defined, and permissions, Laird Breyer |
Next by Thread: |
Re: [Asrg] Spam, defined, and permissions, Devdas Bhagat |
Indexes: |
[Date]
[Thread]
[Top]
[All Lists] |
|
|