[OCCAID] RE: EINTAP policy (DNS-spam)

[Cook, Timothy C.]

Wow, I don't read my email for a few days and my inbox has become flame
central :)  I think the new policy (copied below) sounds much better James,
since nobody else seems to be speaking up, and the whole topic has turned
into mish-mash.  Since the real issue you're trying to deal with obviously
is keeping away ddos/kiddies, this seems a more effective way.  It's quite
obvious not all kiddies use dns-spam hosts, and not all people using
dns-spam hosts are kiddies, and this policy does a better job of reflecting
that.

The one thing I'd like to point out though, is there are way too many people
just chomping at the bit to insult and attack people on this mailing list.
You make a post about policy, people reply, and are attacked... not exactly
conducive to an "educational" experience.  It was so many emails ago I don't
even remember if you asked for feedback on the original policy or if people
just started speaking up on their own.  Regardless, if policies you guys
make are non-negotiable, perhaps you should clue us all in now and just let
us know when they've gone into effect.  If they are up for discussion,
perhaps the attacks could be put to rest when people speak up with differing
ideas since attacks aren't helping the situation at all and they DEFINITELY
aren't making this a better community or a stronger network.

Anyways, I think this proposal is much better than the first.  As for nobody
coming up with ideas of their own, if the others were anything like me,
after the repeated attacks I just decided it wasn't worth the effort since
it was clear that anything I replied with was only going to fall on deaf
ears or be met with defiance.


----------------------------------------------------------------------------
------

Obviously, the current policy component of EINTAP demanding each TAP to
revoke dns spam is too politically harsh as felt by a few people.

I think what could be better for the overall community however, is to
not set anti-dns as a policy, BUT do the following:

1. Each new downstream member, whether directly connected to OCCAID
or via EINTAP, *must* introduce itself to the mailing list, and be placed
on the 60-day trial membership period.

2. After 60 days of trial, if the member has not done all of the following:
a) network abuse
b) getting OCCAID DDoSed due to "hiding in IPv6 because it is dos
safeheaven"
c) host adult or illegal content

Then membership is granted. If the new member has failed any one of the
above during its 60 day trial, he will be disconnected at the time of the
abuse. There shouldn't be policies about how the member uses reverse dns
capability, however if an abuse report is received by JTC that member is
causing offensive activities in IRC using dns-abuse, situation should be
investigated and appropriate response should be made, as being a good
netizen.

In addition, if an EINTAP in particular, feels that dns spam is
unacceptable, such EINTAP is certainly welcome to make rules and polices
as hard as completely blocking IRC protocol or however they see fit as
appropriate policy. However, all EINTAP connectivity policies should be
documented for new users to understand before signing up. 

----------------------------------------------------------------------------
-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 4241 bytes
Desc: not available
Url : http://mailman.twdx.net/pipermail/occaid/attachments/20050114/925d5d66/attachment.bin