idnits 2.17.1 draft-moonesamy-ietf-conduct-3184bis-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? 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 directly say this. It does mention RFC3184 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (December 18, 2013) is 3779 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 183, but no explicit reference was found in the text == Unused Reference: 'RFC3683' is defined on line 189, but no explicit reference was found in the text == Unused Reference: 'RFC3934' is defined on line 192, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 3184 (Obsoleted by RFC 7154) Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 3 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: June 21, 2014 December 18, 2013 7 IETF Guidelines for Conduct 8 draft-moonesamy-ietf-conduct-3184bis-05 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 This document provides an updated version of the guidelines for 18 conduct originally published in RFC 3184. 20 Status of this Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF), its areas, and its working groups. Note that 27 other groups may also distribute working documents as 28 Internet-Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 The list of current Internet-Drafts can be accessed at 36 http://www.ietf.org/1id-abstracts.html 38 The list of Internet-Draft Shadow Directories can be accessed at 39 http://www.ietf.org/shadow.html 41 Copyright Notice 43 Copyright (c) 2013 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 50 S. Moonesamy IETF Guidelines for Conduct December 18, 2013 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 This document may contain material from IETF Documents or IETF 60 Contributions published or made publicly available before November 61 10, 2008. The person(s) controlling the copyright in some of this 62 material may not have granted the IETF Trust the right to allow 63 modifications of such material outside the IETF Standards Process. 64 Without obtaining an adequate license from the person(s) controlling 65 the copyright in such materials,this document may not be modified 66 outside the IETF Standards Process, and derivative works of it may 67 not be created outside the IETF Standards Process, except to format 68 it for publication as an RFC or to translate it into languages other 69 than English. 71 1. Introduction 73 The work of the IETF relies on cooperation among a diverse range of 74 people, ideas, and communication styles. The IETF strives, through 75 the guidelines for conduct, to create and maintain an environment in 76 which every person is treated with dignity, decency, and respect. 77 People who participate in the IETF are expected to behave in a 78 professional manner as we work together to develop interoperable 79 technologies for the Internet. We aim to abide by these guidelines 80 as we build consensus in person and through email discussions. If 81 conflicts arise they are resolved according to the procedures 82 outlined in RFC 2026 [RFC2026]. 84 This document obsoletes RFC 3184 [RFC3184] and reclassifies it as 85 Historic. 87 2. Guidelines for Conduct 89 1. IETF participants extend respect and courtesy to their colleagues 90 at all times. 92 IETF participants come from diverse origins and backgrounds; there 93 can be different expectations or assumptions. Regardless of these 94 individual differences, participants treat their colleagues with 95 respect as persons especially when it is difficult to agree with 96 them; treat other participants as you would like to be treated. 98 English is the de facto language of the IETF. However, it is not 99 the native language of many IETF participants. All participants, 101 S. Moonesamy IETF Guidelines for Conduct December 18, 2013 103 particularly those with English as a first language, attempt to 104 accommodate the needs of other participants by communicating 105 clearly. When faced with English that is difficult to understand 106 IETF participants make a sincere effort to understand each other 107 and engage in conversation to clarify what was meant. 109 2. IETF participants have impersonal discussions. 111 We dispute ideas by using reasoned argument rather than through 112 intimidation or personal attack. Try to provide data and facts 113 for your standpoints so the rest of the participants who are 114 sitting on the sidelines watching the discussion can form an 115 opinion. The discussion is easier when the response to a simple 116 question is a polite answer [SQPA]. 118 3. IETF participants devise solutions for the Internet that meet the 119 needs of diverse technical and operational environments. 121 The IETF puts its emphasis on technical competence, rough 122 consensus and individual participation, and needs to be open to 123 competent input from any source. We understand that "scaling is 124 the ultimate problem" and that many ideas quite workable in the 125 small fail this crucial test. 127 IETF participants use their best engineering judgment to find the 128 best solution for the whole Internet, not just the best solution 129 for any particular network, technology, vendor, or user. While we 130 all have ideas that may stand improvement from time to time, no 131 one shall ever knowingly contribute advice or text that would make 132 a standard technically inferior. 134 4. Individuals are prepared to contribute to the ongoing work of the 135 group. 137 IETF participants read the relevant Internet-Drafts, RFCs, and 138 email archives in order to familiarize themselves with the 139 technology under discussion. Working Group sessions run on a 140 very limited time schedule, and sometimes participants have to 141 limit their questions. The work of the group will continue on the 142 mailing list, and questions can be asked and answered on the 143 mailing list. It can be a challenge to participate in a working 144 group without knowing the history of longstanding working group 145 debates. Information about a working group including its charter 146 and milestones is available on the IETF Tools web site [TOOLS] or 147 from the working group chair. 149 3. Security Considerations 150 S. Moonesamy IETF Guidelines for Conduct December 18, 2013 152 Guidelines about IETF conduct do not directly affect the security of 153 the Internet. 155 4. Acknowledgements 157 Most of the text in this document is based on RFC 3184 which was 158 written by Susan Harris. The author would like to acknowledge that 159 this document would not exist without her contribution. Mike O'Dell 160 wrote the first draft of the Guidelines for Conduct, and many of his 161 thoughts, statements, and observations are included in this version. 162 Many useful editorial comments were supplied by Dave Crocker. 163 Members of the POISSON Working Group provided many significant 164 additions to the text. 166 The editor would like to thank Jari Arkko, Brian Carpenter, Dave 167 Cridland, Dave Crocker, Spencer Dawkins, Alan DeKok, Lars Eggert, 168 David Farmer, Adrian Farrel, Stephen Farrell, Eliot Lear, Barry 169 Leiba, Ines Robles, Eduardo A. Suarez and Brian Trammell for 170 contributing towards the improvement of the document. 172 5. IANA Considerations 174 [RFC Editor: please remove this section] 176 6. References 178 6.1. Informative References 180 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 181 3", BCP 9, RFC 2026, October 1996. 183 [RFC2418] Bradner, S., "IETF Working Group Guidelines and 184 Procedures", BCP 25, RFC 2418, September 1998. 186 [RFC3184] Harris, S., "IETF Guidelines for Conduct", BCP 54, RFC 187 3184, October 2001. 189 [RFC3683] Rose, M., "A Practice for Revoking Posting Rights to IETF 190 Mailing Lists", BCP 83, RFC 3683, March 2004. 192 [RFC3934] Wasserman, M., "Updates to RFC 2418 Regarding the 193 Management of IETF Mailing Lists", BCP 25, RFC 3934, 194 October 2004. 196 [TOOLS] 198 [SQPA] 201 S. Moonesamy IETF Guidelines for Conduct December 18, 2013 203 Appendix A: Reporting transgressions of the guidelines 205 An individual can report transgressions of the guidelines for conduct 206 to the IETF Chair or the IESG. 208 Appendix B: Consequences of transgressing the guidelines 210 This document does not discuss about measures that can be taken 211 against a participant transgressing the guidelines for conduct. 213 RFC 2418 describes a measure where a Working Group Chair has the 214 authority to refuse to grant the floor to any individual who is 215 unprepared or otherwise covering inappropriate material, or who, in 216 the opinion of the Chair is disrupting the Working Group process. 218 RFC 3683 describes "posting rights" action to remove the posting 219 rights of an individual. RFC 3934 describes a measure where a Working 220 Group Chair can suspend posting privileges of a disruptive individual 221 for a short period of time. 223 Appendix C: Changes from RFC 3184 225 o Added text about the IETF striving to create an environment in 226 which every person is treated with dignity, decency, and respect. 228 o The text about intellectual property guidelines was removed as it 229 relates to intellectual property instead of guidelines for 230 conduct. 232 o The recommendation that newcomers should not interfere with the 233 ongoing process in Section 2 was removed as it can be read as 234 discouraging newcomers from participating in discussions. 236 o The text about the goal of the IETF was replaced with text about 237 what the IETF puts its emphasis on. 239 o The text about "think globally" was removed as the meaning was not 240 clear. 242 o The text about language was clarified. 244 o The guideline about impersonal discussions was reworded as a 245 positive statement. 247 7. Author's Address 249 S. Moonesamy (editor) 251 S. Moonesamy IETF Guidelines for Conduct December 18, 2013 253 76, Ylang Ylang Avenue 254 Quatres Bornes 255 Mauritius 257 Email: sm+ietf@elandsys.com