idnits 2.17.1 draft-ietf-run-adverts-02.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 FYI 38 4 RFC 3098 6 Title: How to Advertise Responsibly Using E-Mail and 7 Newsgroups or - how NOT to 8 $$$$$ MAKE ENEMIES FAST! $$$$$ 9 Author(s): E. Gavin, D. Eastlake 3rd, S. Hambridge 10 Status: Informational 11 Date: April 2001 12 Mailbox: tedgavin@newsguy.com, Donald.Eastlake@motorola.com 13 sallyh@ludwig.sc.intel.com 14 Pages: 26 15 Characters: 64687 16 SeeAlso: FYI38 18 I-D Tag: draft-ietf-run-adverts-02.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3098.txt 22 This memo offers useful suggestions for responsible advertising 23 techniques that can be used via the internet in an 24 environment where the advertiser, recipients, and the Internet 25 Community can coexist in a productive and mutually respectful fashion. 26 Some measure of clarity will also be added to the definitions, 27 dangers, and details inherent to Internet Marketing. 29 This document is a product of the Responsible Use of the Network 30 Working Group of the IETF. 32 This memo provides information for the Internet community. It does 33 not specify an Internet standard of any kind. Distribution of this 34 memo is unlimited. 36 This announcement is sent to the IETF list and the RFC-DIST list. 37 Requests to be added to or deleted from the IETF distribution list 38 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 39 added to or deleted from the RFC-DIST distribution list should 40 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 42 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 43 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 44 help: ways_to_get_rfcs. For example: 46 To: rfc-info@RFC-EDITOR.ORG 47 Subject: getting rfcs 49 help: ways_to_get_rfcs 51 Requests for special distribution should be addressed to either the 52 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 53 specifically noted otherwise on the RFC itself, all RFCs are for 54 unlimited distribution.echo 55 Submissions for Requests for Comments should be sent to 56 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 57 Authors, for further information.