idnits 2.17.1 draft-moonesamy-mail-list-protocol-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (December 4, 2012) is 4160 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC1855' is defined on line 156, but no explicit reference was found in the text Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT S. Moonesamy 3 Intended Status: Informational 4 Expires: June 7, 2013 December 4, 2012 6 Mailing list protocol 7 draft-moonesamy-mail-list-protocol-00 9 Abstract 11 This document discusses about a mailing list protocol. This protocol is 12 not a protocol for communication devices. It is a code of courtesy that 13 the reader may wish to extend to others to facilitate the exchange of 14 opinions and ideas, and to facilitate mailing list discussions. 16 Status of this Memo 18 This Internet-Draft is submitted to IETF in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering Task 22 Force (IETF), its areas, and its working groups. Note that other groups 23 may also distribute working documents as Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference material 28 or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/1id-abstracts.html 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html 36 Copyright Notice 38 Copyright (c) 2012 IETF Trust and the persons identified as the document 39 authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal Provisions 42 Relating to IETF Documents (http://trustee.ietf.org/license-info) in 43 effect on the date of publication of this document. Please review these 44 documents carefully, as they describe your rights and restrictions with 45 respect to this document. Code Components extracted from this document 46 must include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 This document may contain material from IETF Documents or IETF 51 Contributions published or made publicly available before November 10, 52 2008. The person(s) controlling the copyright in some of this material 53 may not have granted the IETF Trust the right to allow modifications of 54 such material outside the IETF Standards Process. Without obtaining an 55 adequate license from the person(s) controlling the copyright in such 56 materials,this document may not be modified outside the IETF Standards 57 Process, and derivative works of it may not be created outside the IETF 58 Standards Process, except to format it for publication as an RFC or to 59 translate it into languages other than English. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 2. Mailing list protocol . . . . . . . . . . . . . . . . . . . . . 3 65 3. Internationalization Considerations . . . . . . . . . . . . . . 4 66 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 67 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 68 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 69 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 72 1. Introduction 74 Since the last century people participating in the IETF indulged 75 themselves by sending messages to mailing list. These messages can 76 still be read as they are publicly accessible. Some of these message 77 document the war of words and the numerous personal disagreements 78 that happened during the development of Internet protocols. 80 This document discusses about a mailing list protocol. This protocol 81 is not a protocol for communication devices. It is a code of 82 courtesy that the reader may wish to extend to others to facilitate 83 the exchange of opinions and ideas, and to facilitate mailing list 84 discussions. 86 2. Mailing list protocol 88 When you write a message to a mailing list, remember that anyone in 89 the world can read it. 91 It is better not to send heated messages ("flames") to a mailing list 92 even if you are provoked. Wait a day before sending a response to a 93 mailing list if you strongly disagree. 95 If you are forwarding a message to a mailing list, do not change the 96 wording. If the message was a personal message to you and you are 97 sending it to a mailing list, ask for permission first. 99 It is a good idea to at least check all the mailing list messages 100 about the subject before responding to a message. 102 Trim the email addresses to which the message is addressed when 103 replying if the messages have become a two-way conversation. 105 Be brief without being overly terse. When replying to a message, 106 include enough original material to be understood but no more. It is 107 easier to read a message when a quote indicator (>) is used to 108 indicate quoted lines. 110 It is bad form to simply reply to a message by including all the 111 previous message: edit out all the irrelevant material. 113 Use subject heading which reflects the content of the message. 115 The people with whom you communicate are located across the world. 116 Give them the time to read their email before assuming the email 117 didn't arrive or that they don't care. If you think the importance 118 of a message justifies it, immediately reply briefly to a message to 119 let the sender know you got it, even if you will send a longer reply 120 later. 122 Read the mailing lists for a few weeks before you post anything. 123 This helps you to get an understanding of the culture of the group. 125 3. Internationalization Considerations 127 The recipient is a human being whose culture, language, and humor is 128 different from your own. Date formats, measurements, and idioms can 129 easily be misunderstood. Be especially careful with sarcasm. 131 "Reasonable" expectations for conduct via email depend on your 132 relationship to a person and the context of the communication. Norms 133 learned in a particular email environment may not apply in general to 134 your email communication with people across the Internet. Be careful 135 with slang or local acronyms. 137 4. Security Considerations 139 It is not possible to recall or delete a message once it has been 140 posted to a mailing list. Think carefully before sending private or 141 confidential information to a mailing list. 143 5. IANA Considerations 145 This document does not request any action from IANA. 147 6. Acknowledgements 149 Most of the text in Sections 2 and 3 of this document is based on RFC 150 1855 authored by Sally Hambridge. 152 7. References 154 7.1. Informative References 156 [RFC1855] Hambridge, S., "Netiquette Guidelines", FYI 28, RFC 1855, 157 October 1995. 159 Authors' Addresses 161 S. Moonesamy 162 76, Ylang Ylang Avenue 163 Quatre Bornes 164 Mauritius 166 EMail: sm+ietf@elandsys.com