[ RFC Index | RFC Search | Usenet FAQs | Web FAQs | Documents | Cities ]

    Search the Archives
Display RFC by number
    


RFC 2979: This RFC is worded far too broadly. In particular, the...

<< Back to: RFC 2979

 
Reader comments:
 

Comment by Geoff Kuenning
Submitted on 12/18/2003
Related RFC: RFC 2979
Rating: Rate this comment: Vote
  This RFC is worded far too broadly.  In particular, the phrase "afirewall is entitled to block any sort of access that a site deemsillegitimate" allows complete freedom to censor.  In combination withthe ability to act as a protocol endpoint, and with RFC 2821'sdefinition of an SMTP "gateway", any SMTP relay anywhere in theInternet can arbitrarily redefine itself as a gateway and beginchanging how it handles mail based on the content of that mail.This danger is not a theoretical one.  There are already sites (e.g.,smtp.ucla.edu) that are content-filtering e-mail and justifying itbased on the wording of RFC 2979.  I believe that the wording must berewritten to make it clear that a TCP-based SMTP site MUST NOT alterits behavior in relaying to other TCP-based SMTP sites based on thecontent of the message body.  Otherwise, the firewalling language willbe used by totalitarian governments to justify blocking messages theyfind objectionable.

 
 
FAQS.ORG makes no guarantees as to the accuracy of the posts. Each post is the personal opinion of the poster. These posts are not intended to substitute for medical, tax, legal, investment, accounting, or other professional advice. FAQS.ORG does not endorse any opinion or any product or service mentioned mentioned in these posts.

<< Back to: RFC 2979


© 2008 FAQS.ORG. All rights reserved.