idnits 2.17.1
draft-moonesamy-ietf-conduct-3184bis-02.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 (September 18, 2013) is 3872 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 22, 2014 September 18, 2013
7 IETF Guidelines for Conduct
8 draft-moonesamy-ietf-conduct-3184bis-02
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 September 18, 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 2. Principles of Conduct
80 1. IETF participants extend respect and courtesy to their colleagues
81 at all times.
83 IETF participants come from diverse origins and backgrounds and
84 are equipped with multiple capabilities and ideals. Regardless of
85 these individual differences, participants treat their colleagues
86 with respect as persons especially when it is difficult to agree
87 with them. Seeing from another's point of view is often revealing
88 even when it fails to be compelling.
90 English is the de facto language of the IETF. However, it is not
91 the native language of many IETF participants. All participants,
92 particularly those with English as a first language, attempt to
93 accommodate the needs of other participants by communicating
94 clearly. When faced with English that is difficult to understand
95 IETF participants make a sincere effort to understand each other
96 and engage in conversation to clarify what was meant.
98 2. IETF participants discuss ideas impersonally without finding fault
99 with the person proposing the idea.
101 S. Moonesamy IETF Guidelines for Conduct September 18, 2013
103 We dispute ideas by using reasoned argument rather than through
104 intimidation or personal attack. Or, to say it differently:
106 Cool off, take the intensity out of the discussion and try to
107 provide data and facts for your standpoints so the rest of the
108 participants who are sitting on the sidelines watching the
109 fireworks can form an opinion [SQPA].
111 3. IETF participants devise solutions for the Internet that meet the
112 needs of diverse technical and operational environments.
114 The goal of the IETF is to maintain and enhance a working,
115 viable, scalable, global Internet, and the problems we
116 encounter are genuinely very difficult. We understand that
117 "scaling is the ultimate problem" and that many ideas quite
118 workable in the small fail this crucial test.
120 IETF participants use their best engineering judgment to find
121 the best solution for the whole Internet, not just the best
122 solution for any particular network, technology, vendor, or
123 user. While we all have ideas that may stand improvement from
124 time to time, no one shall ever knowingly contribute advice or
125 text that would make a standard technically inferior.
127 4. Individuals are prepared to contribute to the ongoing work of the
128 group.
130 IETF participants read the relevant Internet-Drafts, RFCs, and
131 email archives beforehand, in order to familiarize themselves
132 with the technology under discussion. This may represent a
133 challenge when attending a new working group without knowing
134 the history of longstanding Working Group debates. Information
135 about a working group including its charter and milestones is
136 available on the IETF Tools web site [TOOLS] or from the
137 working group chair.
139 3. Security Considerations
141 Guidelines about IETF conduct do not affect the security of the
142 Internet in any way.
144 4. Acknowledgements
146 Most of the text in this document is based on RFC 3184 which was
147 written by Susan Harris. The author would like to acknowledge that
148 this document would not exist without her contribution. Mike O'Dell
149 wrote the first draft of the Guidelines for Conduct, and many of his
150 thoughts, statements, and observations are included in this version.
152 S. Moonesamy IETF Guidelines for Conduct September 18, 2013
154 Many useful editorial comments were supplied by Dave Crocker.
155 Members of the POISSON Working Group provided many significant
156 additions to the text.
158 The author would like to thank Jari Arkko, Dave Crocker, Spencer
159 Dawkins, Lars Eggert, Adrian Farrel, Stephen Farrell, Eliot Lear,
160 Barry Leiba, Eduardo A. Suarez and Brian Trammell for contributing
161 towards the improvement of the document.
163 5. IANA Considerations
165 [RFC Editor: please remove this section]
167 6. References
169 6.1. Informative References
171 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
172 3", BCP 9, RFC 2026, October 1996.
174 [TOOLS]
176 [SQPA]
179 Appendix A: Reporting transgressions of the guidelines
181 An individual can report transgressions of the guidelines for conduct
182 to the IETF Chair or the IESG.
184 Appendix B: Consequences of transgressing the guidelines
186 This document does not discuss about measures that can be taken
187 against a participant transgressing the guidelines for conduct.
189 RFC 2418 describes a measure where a Working Group Chair has the
190 authority to refuse to grant the floor to any individual who is
191 unprepared or otherwise covering inappropriate material, or who, in
192 the opinion of the Chair is disrupting the Working Group process.
194 RFC 3683 describes "posting rights" action to remove the posting
195 rights of an individual. RFC 3934 describes a measure where a Working
196 Group Chair can suspend posting privileges of a disruptive individual
197 for a short period of time.
199 Appendix C: Changes from RFC 3184
201 o The text about intellectual property guidelines was removed as it
203 S. Moonesamy IETF Guidelines for Conduct September 18, 2013
205 relates to intellectual property instead of guidelines for
206 conduct.
208 o The recommendation that newcomers should not interfere with the
209 ongoing process in Section 2 was removed as it can be read as
210 discouraging newcomers from participating in discussions.
212 o The text about "think globally" was not removed as the meaning was
213 not clear.
215 o The text about language was clarified.
217 7. Author's Address
219 S. Moonesamy (editor)
220 76, Ylang Ylang Avenue
221 Quatres Bornes
222 Mauritius
224 Email: sm+ietf@elandsys.com