idnits 2.17.1 draft-moonesamy-ietf-conduct-3184bis-03.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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document obsoletes RFC3184, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 15, 2013) is 3840 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2418' is defined on line 176, but no explicit reference was found in the text == Unused Reference: 'RFC3683' is defined on line 179, but no explicit reference was found in the text == Unused Reference: 'RFC3934' is defined on line 182, but no explicit reference was found in the text Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT S. Moonesamy, Ed. 3 Obsoletes: 3184 (if approved) 4 Intended Status: Best Current Practice 5 Expires: April 18, 2014 October 15, 2013 7 IETF Guidelines for Conduct 8 draft-moonesamy-ietf-conduct-3184bis-03 10 Abstract 12 This document provides a set of guidelines for personal interaction 13 in the Internet Engineering Task Force. The Guidelines recognize the 14 diversity of IETF participants, emphasize the value of mutual 15 respect, and stress the broad applicability of our work. 17 Status of this Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF), its areas, and its working groups. Note that 24 other groups may also distribute working documents as 25 Internet-Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/1id-abstracts.html 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html 38 Copyright Notice 40 Copyright (c) 2013 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 50 S. Moonesamy IETF Guidelines for Conduct October 15, 2013 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 This document may contain material from IETF Documents or IETF 57 Contributions published or made publicly available before November 58 10, 2008. The person(s) controlling the copyright in some of this 59 material may not have granted the IETF Trust the right to allow 60 modifications of such material outside the IETF Standards Process. 61 Without obtaining an adequate license from the person(s) controlling 62 the copyright in such materials,this document may not be modified 63 outside the IETF Standards Process, and derivative works of it may 64 not be created outside the IETF Standards Process, except to format 65 it for publication as an RFC or to translate it into languages other 66 than English. 68 1. Introduction 70 The work of the IETF relies on collaboration among a diverse range of 71 people, ideas, and communication styles. The Guidelines for Conduct 72 inform our interaction as we work together to develop interoperable 73 technologies for the Internet. All IETF participants aim to abide by 74 these Guidelines as we build consensus in person and through email 75 discussions. If conflicts arise they are resolved according to the 76 procedures outlined in RFC 2026 [RFC2026]. 78 This document obsoletes RFC 3184. 80 2. Principles of Conduct 82 1. IETF participants extend respect and courtesy to their colleagues 83 at all times. 85 IETF participants come from diverse origins and backgrounds and 86 are equipped with multiple capabilities and ideals. Regardless of 87 these individual differences, participants treat their colleagues 88 with respect as persons especially when it is difficult to agree 89 with them. Seeing from another's point of view is often revealing 90 even when it fails to be compelling. 92 English is the de facto language of the IETF. However, it is not 93 the native language of many IETF participants. All participants, 94 particularly those with English as a first language, attempt to 95 accommodate the needs of other participants by communicating 96 clearly. When faced with English that is difficult to understand 97 IETF participants make a sincere effort to understand each other 98 and engage in conversation to clarify what was meant. 100 S. Moonesamy IETF Guidelines for Conduct October 15, 2013 102 2. IETF participants discuss ideas impersonally without finding fault 103 with the person proposing the idea. 105 We dispute ideas by using reasoned argument rather than through 106 intimidation or personal attack. Or, to say it differently: 108 Cool off, take the intensity out of the discussion and try to 109 provide data and facts for your standpoints so the rest of the 110 participants who are sitting on the sidelines watching the 111 fireworks can form an opinion [SQPA]. 113 3. IETF participants devise solutions for the Internet that meet the 114 needs of diverse technical and operational environments. 116 The goal of the IETF is to maintain and enhance a working, 117 viable, scalable, global Internet, and the problems we 118 encounter are genuinely very difficult. We understand that 119 "scaling is the ultimate problem" and that many ideas quite 120 workable in the small fail this crucial test. 122 IETF participants use their best engineering judgment to find 123 the best solution for the whole Internet, not just the best 124 solution for any particular network, technology, vendor, or 125 user. While we all have ideas that may stand improvement from 126 time to time, no one shall ever knowingly contribute advice or 127 text that would make a standard technically inferior. 129 4. Individuals are prepared to contribute to the ongoing work of the 130 group. 132 IETF participants read the relevant Internet-Drafts, RFCs, and 133 email archives beforehand, in order to familiarize themselves 134 with the technology under discussion. This may represent a 135 challenge when attending a new working group without knowing 136 the history of longstanding Working Group debates. Information 137 about a working group including its charter and milestones is 138 available on the IETF Tools web site [TOOLS] or from the 139 working group chair. 141 3. Security Considerations 143 Guidelines about IETF conduct do not affect the security of the 144 Internet in any way. 146 4. Acknowledgements 148 Most of the text in this document is based on RFC 3184 which was 149 written by Susan Harris. The author would like to acknowledge that 151 S. Moonesamy IETF Guidelines for Conduct October 15, 2013 153 this document would not exist without her contribution. Mike O'Dell 154 wrote the first draft of the Guidelines for Conduct, and many of his 155 thoughts, statements, and observations are included in this version. 156 Many useful editorial comments were supplied by Dave Crocker. 157 Members of the POISSON Working Group provided many significant 158 additions to the text. 160 The author would like to thank Jari Arkko, Dave Crocker, Spencer 161 Dawkins, Lars Eggert, Adrian Farrel, Stephen Farrell, Eliot Lear, 162 Barry Leiba, Ines Robles, Eduardo A. Suarez and Brian Trammell for 163 contributing towards the improvement of the document. 165 5. IANA Considerations 167 [RFC Editor: please remove this section] 169 6. References 171 6.1. Informative References 173 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 174 3", BCP 9, RFC 2026, October 1996. 176 [RFC2418] Bradner, S., "IETF Working Group Guidelines and 177 Procedures", BCP 25, RFC 2418, September 1998. 179 [RFC3683] Rose, M., "A Practice for Revoking Posting Rights to IETF 180 Mailing Lists", BCP 83, RFC 3683, March 2004. 182 [RFC3934] Wasserman, M., "Updates to RFC 2418 Regarding the 183 Management of IETF Mailing Lists", BCP 25, RFC 3934, 184 October 2004. 186 [TOOLS] 188 [SQPA] 191 Appendix A: Reporting transgressions of the guidelines 193 An individual can report transgressions of the guidelines for conduct 194 to the IETF Chair or the IESG. 196 Appendix B: Consequences of transgressing the guidelines 198 This document does not discuss about measures that can be taken 199 against a participant transgressing the guidelines for conduct. 201 S. Moonesamy IETF Guidelines for Conduct October 15, 2013 203 RFC 2418 describes a measure where a Working Group Chair has the 204 authority to refuse to grant the floor to any individual who is 205 unprepared or otherwise covering inappropriate material, or who, in 206 the opinion of the Chair is disrupting the Working Group process. 208 RFC 3683 describes "posting rights" action to remove the posting 209 rights of an individual. RFC 3934 describes a measure where a Working 210 Group Chair can suspend posting privileges of a disruptive individual 211 for a short period of time. 213 Appendix C: Changes from RFC 3184 215 o The text about intellectual property guidelines was removed as it 216 relates to intellectual property instead of guidelines for 217 conduct. 219 o The recommendation that newcomers should not interfere with the 220 ongoing process in Section 2 was removed as it can be read as 221 discouraging newcomers from participating in discussions. 223 o The text about "think globally" was not removed as the meaning was 224 not clear. 226 o The text about language was clarified. 228 7. Author's Address 230 S. Moonesamy (editor) 231 76, Ylang Ylang Avenue 232 Quatres Bornes 233 Mauritius 235 Email: sm+ietf@elandsys.com