Re: [OCCAID] Proposal for EINTAP

["Scott J. Clifford" <clifford@cnacs.occaid.org>]

On Fri, Jan 07, 2005 at 02:16:41PM -0500, Tom McNeely wrote:
> The Joint Technical Coordination members would like to propose 
> Experimental Internet Transit Access Point program on behalf of the 
> OCCAID community this year.
> 
> The following URL is the link to the initial proposal. We would 
> appreciate anyone's comments and constructive criticisms to the 
> discussion table.
> 
> http://www.occaid.org/proposals/eintap.txt
> 
> -Tom

The OCCAID Joint Tech Coordination members collectively agree to proceed and
move forward with the transition to EINTAP framework.

Many people have viewed EINTAP favorably in their opinion due to oppurtunities
for EINTAPs to pursue more collaborations amongst themselves and end-sites and
also because EINTAP framework offloads significant amount of load from JTC
group's administrative overhead.

Some folks on this mailing list have voiced concerns about the anti DNS spam
measures being part of the framework. JTC members have internally discussed
this issue on our table in the past two days and we have come to conclusion
that spamatized DNS hostnames will play no beneficial role whatsoever in the
spirit of maintaining a network that is academic in its purpose. Because OCCAID
does not filter nor censor activities on traffic which transit the network,
unless required by the authorities, we've come to our conclusion to agree and
move forward with the anti-DNS-spam policy in our original EINTAP proposal.
OCCAID's generaly policy will be that while transit traffic should be set free
as possible, the use and activities under our address space must remain
academically focused.

The following language in the EINTAP proposal must be changed to move forward..

"5. Must Run IPv6
Each EINTAP SHOULD provide IPv6 transit service to its END-SITEs."

Change to:

5. Must Run IPv6
Each EINTAP MUST provide IPv6 transit service to its END-SITEs.

****

"13. Network Abuse Prohibited
Both the EINTAP and END-SITE SHOULD NOT abuse their connection(s)
by performing malicious activities, including intrusion and
denial of service attempts. Disciplinary actions MUST BE
taken by the EINTAP or OCCAID as appropriate in response to a
network abuse."

13. Network Abuse Prohibited
Both the EINTAP and END-SITE MUST NOT abuse their connection(s)
by performing malicious activities, including intrusion and
denial of service attempts. Disciplinary actions MUST BE
taken by the EINTAP or OCCAID as appropriate in response to a
network abuse.

****
"14. No Abuse of IPv6 Reverse DNS Delegation
Upon discovery of "DNS spam" by an END-SITE, the upstream
EINTAP SHOULD require its END-SITE to stop using polluting
reverse DNS mappings in its IPv6 address space. If the
END-SITE refuses to cease its "DNS spam" activities, the
EINTAP MUST revoke the reverse DNS delegation.

http://spamcalc.net SHOULD be used to validate whether a
specific reverse DNS hostname violates spamcalc guidelines
or is otherwise improper."

Change to:
14. No Abuse of IPv6 Reverse DNS Delegation
Upon discovery of "DNS spam" by an END-SITE, the upstream
EINTAP SHOULD require its END-SITE to stop using polluting
reverse DNS mappings in its IPv6 address space. If the
END-SITE refuses to cease its "DNS spam" activities, the
EINTAP SHOULD revoke the reverse DNS delegation.

http://spamcalc.net SHOULD be used to validate whether a
specific reverse DNS hostname violates spamcalc guidelines
or is otherwise improper.
_______________________________________________
OCCAID Mailing List: http://www.occaid.org
schednetisr(NETISR_COFFEE); inq=&coffeebreak_intrq;

Occaid@cnacs.occaid.org is the list posting address.
db-admin@cnacs.occaid.org is the human contact address.
See below URL for subscribe/unsubscribe and list options:
http://mailman.twdx.net/mailman/listinfo/occaid