分享
 
 
 

RFC3184 - IETF Guidelines for Conduct

王朝other·作者佚名  2008-05-31
窄屏简体版  字體: |||超大  

Network Working Group S. Harris

Request for Comments: 3184 Merit Network

BCP: 54 October 2001

Category: Best Current Practice

IETF Guidelines for CondUCt

Status of this Memo

This document specifies an Internet Best Current Practices for the

Internet Community, and requests discussion and suggestions for

improvements. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2001). All Rights Reserved.

Abstract

This document provides a set of guidelines for personal interaction

in the Internet Engineering Task Force. The Guidelines recognize the

diversity of IETF participants, emphasize the value of mutual

respect, and stress the broad applicability of our work.

1. Introduction

The work of the IETF relies on cooperation among a broad cultural

diversity of peoples, ideas, and communication styles. The

Guidelines for Conduct inform our interaction as we work together to

develop multiple, interoperable technologies for the Internet. All

IETF participants aim to abide by these Guidelines as we build

consensus in person, at IETF meetings, and in e-mail. If conflicts

arise, we resolve them according to the procedures outlined in BCP

25.[1]

2. Principles of Conduct

1. IETF participants extend respect and courtesy to their colleagues

at all times.

IETF participants come from diverse origins and backgrounds and

are equipped with multiple capabilities and ideals. Regardless of

these individual differences, participants treat their colleagues

with respect as persons--especially when it is difficult to agree

with them. Seeing from another's point of view is often

revealing, even when it fails to be compelling.

English is the de facto language of the IETF, but it is not the

native language of many IETF participants. Native English

speakers attempt to speak clearly and a bit slowly and to limit

the use of slang in order to accommodate the needs of all

listeners.

2. IETF participants develop and test ideas impartially, without

finding fault with the colleague proposing the idea.

We dispute ideas by using reasoned argument, rather than through

intimidation or ad hominem attack. Or, said in a somewhat more

IETF-like way:

"Reduce the heat and increase the light"

3. IETF participants think globally, devising solutions that meet the

needs of diverse technical and operational environments.

The goal of the IETF is to maintain and enhance a working, viable,

scalable, global Internet, and the problems we encounter are

genuinely very difficult. We understand that "scaling is the

ultimate problem" and that many ideas quite workable in the small

fail this crucial test. IETF participants use their best

engineering judgment to find the best solution for the whole

Internet, not just the best solution for any particular network,

technology, vendor, or user. We follow the intellectual property

guidelines outlined in BCP 9.[2]

4. Individuals who attend Working Group meetings are prepared to

contribute to the ongoing work of the group.

IETF participants who attend Working Group meetings read the

relevant Internet-Drafts, RFCs, and e-mail archives beforehand, in

order to familiarize themselves with the technology under

discussion. This may represent a challenge for newcomers, as e-

mail archives can be difficult to locate and search, and it may

not be easy to trace the history of longstanding Working Group

debates. With that in mind, newcomers who attend Working Group

meetings are encouraged to observe and absorb whatever material

they can, but should not interfere with the ongoing process of the

group. Working Group meetings run on a very limited time

schedule, and are not intended for the education of individuals.

The work of the group will continue on the mailing list, and many

questions would be better eXPressed on the list in the months that

follow.

3. Security Considerations

IETF participants review each Internet protocol for security

concerns, and these concerns are incorporated in the description of

each protocol.

4. Acknowledgements

Mike O'Dell wrote the first draft of the Guidelines for Conduct, and

many of his thoughts, statements, and observations are included in

this version. Many useful editorial comments were supplied by Dave

Crocker. Members of the POISSON Working Group provided many

significant additions to the text.

5. References

[1] Bradner, S., "IETF Working Group Guidelines and Procedures",

BCP 25, RFC2418, September 1998.

[2] Bradner, S., "The Internet Standards Process -- Revision 3",

BCP 9, RFC2026, October 1996.

6. Author's Address

Susan Harris

Merit Network, Inc.

4251 Plymouth Rd., Suite 2000

Ann Arbor, MI 48105-2785

EMail: srh@merit.edu

Phone: (734) 936-2100

7. Full Copyright Statement

Copyright (C) The Internet Society (2001). All Rights Reserved.

This document and translations of it may be copied and furnished to

others, and derivative works that comment on or otherwise explain it

or assist in its implementation may be prepared, copied, published

and distributed, in whole or in part, without restriction of any

kind, provided that the above copyright notice and this paragraph are

included on all such copies and derivative works. However, this

document itself may not be modified in any way, such as by removing

the copyright notice or references to the Internet Society or other

Internet organizations, except as needed for the purpose of

developing Internet standards in which case the procedures for

copyrights defined in the Internet Standards process must be

followed, or as required to translate it into languages other than

English.

The limited permissions granted above are perpetual and will not be

revoked by the Internet Society or its successors or assigns.

This document and the information contained herein is provided on an

"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING

TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING

BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION

HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

Funding for the RFCEditor function is currently provided by the

Internet Society.

 
 
 
免责声明:本文为网络用户发布,其观点仅代表作者个人观点,与本站无关,本站仅提供信息存储服务。文中陈述内容未经本站证实,其真实性、完整性、及时性本站不作任何保证或承诺,请读者仅作参考,并请自行核实相关内容。
2023年上半年GDP全球前十五强
 百态   2023-10-24
美众议院议长启动对拜登的弹劾调查
 百态   2023-09-13
上海、济南、武汉等多地出现不明坠落物
 探索   2023-09-06
印度或要将国名改为“巴拉特”
 百态   2023-09-06
男子为女友送行,买票不登机被捕
 百态   2023-08-20
手机地震预警功能怎么开?
 干货   2023-08-06
女子4年卖2套房花700多万做美容:不但没变美脸,面部还出现变形
 百态   2023-08-04
住户一楼被水淹 还冲来8头猪
 百态   2023-07-31
女子体内爬出大量瓜子状活虫
 百态   2023-07-25
地球连续35年收到神秘规律性信号,网友:不要回答!
 探索   2023-07-21
全球镓价格本周大涨27%
 探索   2023-07-09
钱都流向了那些不缺钱的人,苦都留给了能吃苦的人
 探索   2023-07-02
倩女手游刀客魅者强控制(强混乱强眩晕强睡眠)和对应控制抗性的关系
 百态   2020-08-20
美国5月9日最新疫情:美国确诊人数突破131万
 百态   2020-05-09
荷兰政府宣布将集体辞职
 干货   2020-04-30
倩女幽魂手游师徒任务情义春秋猜成语答案逍遥观:鹏程万里
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案神机营:射石饮羽
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案昆仑山:拔刀相助
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案天工阁:鬼斧神工
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案丝路古道:单枪匹马
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:与虎谋皮
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:李代桃僵
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:指鹿为马
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案金陵:小鸟依人
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案金陵:千金买邻
 干货   2019-11-12
 
推荐阅读
 
 
 
>>返回首頁<<
 
靜靜地坐在廢墟上,四周的荒凉一望無際,忽然覺得,淒涼也很美
© 2005- 王朝網路 版權所有