Well, I prefer tech to legal-ese.. It's just my nature. I don't doubt that
you could make things scary and binding enough (legally speaking), but I
want it backed up with technical measures. I want sender tracability incase
they do send spam anyway. Then you get in a whole new can of worms working
out ways on how you can verify the sender is legit and traceable. Then you
have to be able to make that determination in real-time while you still have
them on a socket, before you accept the message.
Otherwise I'll lie about who I am, and that my message is not spam. Or I'll
agree to the $50,000 spam fee and poof! disappear.
Those are the measures whose defense must be built in as well.
Remember: "Locks only keep honest people honest." Most spammers are not
honest. I doubt Amber is horny for me, wants me to see her naked, or even
that she knows who I am. I bet it's really Frank, who looks like the
uni-bomber that's really typing that in and inviting me over!
Until we eliminate (much less discover) the ways around it, we only create
more work for everyone.
-----Original Message-----
From: Valdis(_dot_)Kletnieks(_at_)vt(_dot_)edu
[mailto:Valdis(_dot_)Kletnieks(_at_)vt(_dot_)edu]
Sent: Monday, March 17, 2003 4:39 PM
To: Jason Hihn
Cc: Asrg(_at_)ietf(_dot_)org
Subject: Re: [Asrg] Giving Public Notice ....
On Mon, 17 Mar 2003 16:22:12 EST, Jason Hihn said:
My points exactly! It would be cool and could be made to work,
but in the
end, it's futile/pointless/a lost cause.
I didn't say it was a lost cause.. ;)
I pointed out that there were problems - many of which are fixable.
For instance, *IF* you have a technically workable SMTP
extension, you could
then conceivably codify that "a UCE sender must check the
extension and pay
any indemnification as a result".
The nice thing there is that if you don't send any UCE, you can
just ignore
the extension and nothing changes. ;)
Yes, this does require some coding, some RFCs, and some legal tapdancing
similar to what's already in 17 USC 512 for an ISP safe-harbor, so if one
of our users does something stupid and relays it through our server, it's
their problem not mine. But not anything fundamentally not fixable.
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg