idnits 2.17.1 draft-moonesamy-ietf-conduct-3184bis-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 : ---------------------------------------------------------------------------- -- 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 17, 2013) is 3904 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: February 18, 2014 August 17, 2013 7 IETF Guidelines for Conduct 8 draft-moonesamy-ietf-conduct-3184bis-00 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 17, 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 17, 2013 103 intimidation or personal attack. 105 3. IETF participants think globally, devising solutions that meet the 106 needs of diverse technical and operational environments. 108 The goal of the IETF is to maintain and enhance a working, viable, 109 scalable, global Internet, and the problems we encounter are 110 genuinely very difficult. We understand that "scaling is the 111 ultimate problem" and that many ideas quite workable in the small 112 fail this crucial test. IETF participants use their best 113 engineering judgment to find the best solution for the whole 114 Internet, not just the best solution for any particular network, 115 technology, vendor, or user. 117 4. Individuals are prepared to contribute to the ongoing work of the 118 group. 120 IETF participants read the relevant Internet-Drafts, RFCs, and 121 email archives beforehand, in order to familiarize themselves with 122 the technology under discussion. This may represent a challenge 123 for newcomers, as email archives can be difficult to locate and 124 search, and it may not be easy to trace the history of 125 longstanding Working Group debates. 127 3. Security Considerations 129 Guidelines about IETF conduct do not affect the security of the 130 Internet in any way. 132 4. Acknowledgements 134 Most of the text in this document is based on RFC 3184 which was 135 written by Sandy Harris. Mike O'Dell wrote the first draft of the 136 Guidelines for Conduct, and many of his thoughts, statements, and 137 observations are included in this version. Many useful editorial 138 comments were supplied by Dave Crocker. Members of the POISSON 139 Working Group provided many significant additions to the text. 141 5. IANA Considerations 143 [RFC Editor: please remove this section] 145 6. References 147 6.1 Informative References 149 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 150 3", BCP 9, RFC 2026, October 1996. 152 S. Moonesamy IETF Guidelines for Conduct August 17, 2013 154 7. Author's Address 156 S. Moonesamy (editor) 157 76, Ylang Ylang Avenue 158 Quatres Bornes 159 Mauritius 161 Email: sm+ietf@elandsys.com