idnits 2.17.1 draft-moonesamy-ietf-conduct-3184bis-01.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 (August 30, 2013) is 3891 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 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: March 3, 2014 August 30, 2013 7 IETF Guidelines for Conduct 8 draft-moonesamy-ietf-conduct-3184bis-01 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 August 30, 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 cooperation among a broad cultural 71 diversity of peoples, ideas, and communication styles. The 72 Guidelines for Conduct inform our interaction as we work together to 73 develop multiple, interoperable technologies for the Internet. All 74 IETF participants aim to abide by these Guidelines as we build 75 consensus in person and through email discussions. If conflicts 76 arise they are resolved according to the procedures outlined in RFC 77 2026 [RFC2026]. 79 2. Principles of Conduct 81 1. IETF participants extend respect and courtesy to their colleagues 82 at all times. 84 IETF participants come from diverse origins and backgrounds and 85 are equipped with multiple capabilities and ideals. Regardless of 86 these individual differences, participants treat their colleagues 87 with respect as persons especially when it is difficult to agree 88 with them. Seeing from another's point of view is often 89 revealing, even when it fails to be compelling. 91 English is the de facto language of the IETF. However, it is not 92 the native language of many IETF participants. Native English 93 speakers will limit the use of slang in order to accommodate the 94 needs of all listeners. 96 2. IETF participants develop and test ideas impartially without 97 finding fault with the colleague proposing the idea. 99 We dispute ideas by using reasoned argument rather than through 101 S. Moonesamy IETF Guidelines for Conduct August 30, 2013 103 intimidation or personal attack. Or, to say it differently: 105 Cool off, take the intensity out of the discussion and try to 106 provide data and facts for your standpoints so the rest of the 107 participants who are sitting on the sidelines watching the 108 fireworks can form an opinion. 110 3. IETF participants devise solutions for the Internet that meet the 111 needs of diverse technical and operational environments. 113 The goal of the IETF is to maintain and enhance a working, 114 viable, scalable, global Internet, and the problems we 115 encounter are genuinely very difficult. We understand that 116 "scaling is the ultimate problem" and that many ideas quite 117 workable in the small fail this crucial test. IETF 118 participants use their best engineering judgment to find the 119 best solution for the whole Internet, not just the best 120 solution for any particular network, technology, vendor, or 121 user. 123 4. Individuals are prepared to contribute to the ongoing work of the 124 group. 126 IETF participants read the relevant Internet-Drafts, RFCs, and 127 email archives beforehand, in order to familiarize themselves 128 with the technology under discussion. This may represent a 129 challenge for newcomers as it may not be easy to trace the 130 history of longstanding Working Group debates. Information 131 about a working group including its charter and milestones is 132 available on the IETF Tools web site [TOOLS]. 134 3. Security Considerations 136 Guidelines about IETF conduct do not affect the security of the 137 Internet in any way. 139 4. Acknowledgements 141 Most of the text in this document is based on RFC 3184 which was 142 written by Susan Harris. The author would like to acknowledge that 143 this document would not exist without her contribution. Mike O'Dell 144 wrote the first draft of the Guidelines for Conduct, and many of his 145 thoughts, statements, and observations are included in this version. 146 Many useful editorial comments were supplied by Dave Crocker. 147 Members of the POISSON Working Group provided many significant 148 additions to the text. 150 The text replacement for "Reduce the heat and increase the light" was 152 S. Moonesamy IETF Guidelines for Conduct August 30, 2013 154 suggested by Lars Eggert. 156 5. IANA Considerations 158 [RFC Editor: please remove this section] 160 6. References 162 6.1. Informative References 164 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 165 3", BCP 9, RFC 2026, October 1996. 167 [TOOLS] 169 Appendix A: Reporting violating of the guidelines 171 An individual can report violations of the guidelines for conduct to 172 the IETF Chair or the IESG. 174 Appendix B: Measures against a participant violating of the guidelines 176 This document does not discuss about measures that can be taken 177 against a participant violating the guidelines for conduct. 179 RFC 2418 describes a measure where a Working Group Chair has the 180 authority to refuse to grant the floor to any individual who is 181 unprepared or otherwise covering inappropriate material, or who, in 182 the opinion of the Chair is disrupting the Working Group process. 184 RFC 3683 describes "posting rights" action to remove the posting 185 rights of an individual. RFC 3934 describes a measure where a Working 186 Group Chair can suspend posting privileges of a disruptive individual 187 for a short period of time. 189 Appendix C: Changes from RFC 3184 191 o The text about intellectual property guidelines was removed as it 192 relates to intellectual property instead of guidelines for 193 conduct. 195 o The recommendation that newcomers should not interfere with the 196 ongoing process in Section 2 was removed as it can be read as 197 discouraging newcomers from participating in discussions. 199 o As the meaning of "think globally" was not clear that text was 200 removed. 202 S. Moonesamy IETF Guidelines for Conduct August 30, 2013 204 7. Author's Address 206 S. Moonesamy (editor) 207 76, Ylang Ylang Avenue 208 Quatres Bornes 209 Mauritius 211 Email: sm+ietf@elandsys.com