idnits 2.17.1 draft-odell-code-of-conduct-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 1995) is 10390 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 7 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Mike O'Dell 3 Internet-Draft UUNET Technologies 4 November 1995 6 Some Thoughts on the Importance of Modesty and Decorum 7 and the Need for an IETF Code of Conduct 9 11 Status of this Memo 12 This document is an Internet-Draft. Internet-Drafts are working 13 documents of the Internet Engineering Task Force (IETF), its areas, 14 and its working groups. Note that other groups may also distribute 15 working documents as Internet-Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet-Drafts as reference 20 material or to cite them other than as ``work in progress.'' 22 To learn the current status of any Internet-Draft, please check the 23 1id-abstracts.txt listing contained in the Internet-Drafts Shadow 24 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 25 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 26 ftp.isi.edu (US West Coast). 28 Abstract 29 Because of the importance of the work done in the IETF, and because 30 of the increasing cultural diversity of the participants, some of 31 whom find our most-unrestrained "style" hard to accommodate, I 32 believe the time has come for the IETF to adopt a Code of Conduct to 33 govern our interactions. 35 1.0 Background 36 The Internet Engineering Task Force is the unique, all-volunteer 37 organization promulgating the standards which make the global 38 Internet viable. As such, the participants who do this critical work 39 are very bright, usually quite passionate individuals, often with 40 strong opinions which are equally strongly held. 42 The IETF has a long tradition of evolving ideas forged in the fires 43 of impassioned analysis which then go on to be tempered by 44 confrontation with real-world operational deployment before they are 45 deemed "a standard." 47 The very nature of this process of vigorous debate and evaluation 48 makes for the occasionally over-animated interchange between well- 49 intentioned people. A free-ranging exchange of ideas and viewpoints 50 is critical to the success of the process, but when it oversteps the 51 bounds of modesty and decorum, it is to the detriment of the process. 53 2.0 Codes of Conduct 54 Historically, many great deliberative bodies, attempting to wrestle 55 with the conflicting demands of passion and reason, have established 56 a "code of conduct" which serves to remind the deliberants of their 57 obligations to their colleagues. While the antiquarian honorifics 58 such as "The Gentleman from Upper Lowerville" and "The Honorable 59 Senator from East Noseblow" strike the modern ear with some humor, 60 the underlying agreement to treat each other with a respectable level 61 of civility is the critical matter. 63 Such codes of conduct reinforce the tenets of honest debate and 64 create a bond of honor which can and does get called when the heat of 65 passion overtakes the machinery of reason. This provides an agreed- 66 upon obligation to pull back from the brink of personal insult and 67 affront, allowing reason an opportunity to salvage honor. 69 3.0 The Need for a Code of Conduct in the IETF 70 Because of the importance of the work done in the IETF, and because 71 of the increasing cultural diversity of the participants, some of 72 whom find our most-unrestrained "style" hard to accommodate, I 73 believe the time has come for the IETF to adopt a Code of Conduct to 74 govern our interactions. It would apply to in-person interactions 75 like those at the IETF Meetings, but also in Email exchanges as well, 76 where the level of invective tends to escalate even faster than in 77 face-to-face interactions. 79 It has become clear that the IETF is missing opportunities to review 80 some very important technology because the creators chose to go 81 elsewhere to define these technologies. We are also denied the 82 expertise of smart people who could otherwise contribute 83 significantly to what we do, but chose not to subject themselves to 84 behavior we have previously excused as "unrefined advocacy." 86 Note carefully that the goal is not to proscribe any particular 87 behavior, but rather to affirm a commitment to a course of action and 88 an attitude toward each other which will maximize the effectiveness 89 of our deliberations. Or said in a more IETF-oriented style: 91 "Increase the light and reduce the heat." 93 4.0 Precepts of the IETF Code of Conduct. 94 What follows is a list of precepts which form the IETF Code of 95 Conduct. Adherence to these in both action and spirit will promote 96 the general welfare of the IETF community and promote more productive 97 deliberations. Variance from them should provoke a gentle reminder 98 of what they have been agreed upon, not provide grounds for 99 flamewars. 101 (1a) The IETF is composed of many people from many cultures and does 102 work having global scope and importance. 103 (1b) An IETF Member honors the organization by extending his 104 colleagues respect and honest courtesy at all times, especially 105 when it is difficult to agree with them. Seeing from another's 106 point of view is often revealing, even if it fails to be 107 compelling. 109 (2a) The business of the IETF is the development and testing of 110 Ideas. 111 (2b) An IETF Member disputes an idea with reasoned argument rather 112 than the colleague proposing the idea. Intimidation and Ad 113 Homonym attack have no place in reasoned deliberations. 114 (2c) Likewise, "witty repartee'" and rhetorical one-upsmanship have 115 scant use in technical discussions. While spirited word-play may 116 be an emotionally satisfying diversion, and may occasionally 117 provide much-needed comic relief, it is at best only a diversion 118 and does not advance the real business of the IETF. Worse, when 119 done badly or to intentionally prickle another, it serves only to 120 increase contentiousness and breed rancor. 122 (3a) The goal of the IETF is a working, viable, scalable global 123 Internet, and the concomitant problems are honestly very hard. 124 (3b) An IETF Member always proceeds based on Right Reason and strives 125 to be as intellectually honest as she knows how to be. Further, 126 she dedicates her intellect to solving the problems in the best 127 way, not just the most expedient. 128 (3c) An IETF Member strives to find the best solution for the whole 129 Internet, not the best solution for any particular vendor, 130 operator or user. 132 (4a) "Best" is a very tricky concept, fluid and dynamic. 133 (4b) An IETF Member understands change is one of the few certainties, 134 and that without the exercise of supreme discipline, one can spend 135 eternity working for unknowable perfection, while the real-world 136 problems languish, denied adequate attention. 138 (5a) An IETF Member strives at all times to abide by this code and 139 the spirit it embodies. 140 (5b) When someone suffers a lapse in adherence to this spirit, an 141 IETF Member offers a gentle but forthright reminder of their 142 agreement to honor this spirit. Castigation and remonstration are 143 inappropriate in all except the the most refractory situations, 144 and even then, never cross the line into personal invective and 145 dishonor. 147 (5c) An IETF Member apologizes in private or in public for any 148 offense caused to other members. 150 5.0 Conclusion 151 By every IETF member adhering to this code of conduct, we can promote 152 the vigorous but measured exchanges required for the work we pursue 153 without unrequired incursions into the realm of personal invective. 155 6.0 Security Considerations 156 Security (other than personal) is not addressed in this memo. 158 7.0 Author's Address 160 Mike O'Dell 161 UUNET Technologies, Inc. 162 3060 Williams Drive 163 Fairfax, VA 22030 164 voice: 703-206-5890 165 fax: 703-641-7704 166 email: mo@uunet.uu.net