Internet Engineering Task Force (IETF) L. Eggert
Request for Comments: 6771 NetApp
Category: Informational G. Camarillo
ISSN: 2070-1721 Ericsson
October 2012
Internet Engineering Task Force (IETF) L. Eggert
Request for Comments: 6771 NetApp
Category: Informational G. Camarillo
ISSN: 2070-1721 Ericsson
October 2012
Considerations for Having a Successful "Bar BOF" Side Meeting
成功召开“Bar BOF”侧会的考虑因素
Abstract
摘要
New work is typically brought to the IETF by a group of interested individuals. IETF meetings are a convenient place for such groups to hold informal get-togethers to discuss and develop their ideas. Such side meetings, which are not reflected in the IETF meeting agenda and have no official status, are often half-jokingly referred to as "bar BOF" sessions to acknowledge that some of them may eventually lead to a proposal for an official IETF BOF ("birds of a feather" session) on a given topic.
新的工作通常由一群感兴趣的个人提交给IETF。IETF会议是此类团体举行非正式聚会讨论和发展想法的便利场所。此类会外会议没有反映在IETF会议议程中，也没有正式地位，通常被半开玩笑地称为“bar BOF”会议，以承认其中一些会议可能最终导致就某一特定主题提出正式IETF BOF（“羽毛鸟”会议）的建议。
During recent IETF meetings, many such "bar BOF" get-togethers have been organized and moderated in ways that made them increasingly indistinguishable from official IETF BOFs or sometimes even IETF working group meetings.
在最近的IETF会议期间，许多此类“bar BOF”聚会的组织和主持方式越来越难以与IETF官方BOF或有时甚至IETF工作组会议区分开来。
This document argues that this recent trend is not helpful in reaching the ultimate goal of many of these get-togethers, i.e., to efficiently discuss and develop ideas for new IETF work. It encourages the organizers to consider the benefits of holding them in much less formal settings and to also consider alternative means to develop their ideas. This document also recommends that the community abandon the term "bar BOF" and instead use other terms such as "side meeting", in order to stress the unofficial nature of these get-togethers.
本文件认为，这种最新趋势无助于实现许多此类聚会的最终目标，即有效地讨论和开发新IETF工作的想法。它鼓励组织者考虑在不太正式的场合下持有它们的好处，也考虑其他方法来发展他们的想法。该文件还建议社区放弃“酒吧聚会”这一术语，改用其他术语，如“边聚会”，以强调这些聚会的非官方性质。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6771.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6771.
Copyright Notice
版权公告
Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2012 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
A typical IETF meeting is full of sessions of different kinds. In addition to official IETF and IRTF sessions listed in the meeting agenda (such as working and research group meetings, area meetings, or plenaries), many other unofficial meetings take place. These include meetings between IETF participants from one organization or company, design team meetings, Internet-Draft editing sessions, interoperability testing, directorate lunches, and many others.
一个典型的IETF会议充满了不同类型的会议。除了会议议程中列出的IETF和IRTF正式会议（如工作组和研究组会议、区域会议或全体会议）外，还举行了许多其他非正式会议。其中包括来自一个组织或公司的IETF参与者之间的会议、设计团队会议、互联网草案编辑会议、互操作性测试、董事会午餐以及其他许多会议。
Some of these unofficial get-togethers are organized by individual participants with a common interest in initiating new IETF work of some kind. New IETF work often fits into an existing working group and does not require an official "birds of a feather" (BOF) session [RFC5434] to determine community consensus. Nevertheless, the phrase "bar BOF" has commonly been used in the community when talking about such informal get-togethers that are held to discuss potential new work. [RFC4677] (which has been obsoleted by [RFC6722]) characterizes a "bar BOF" as
其中一些非官方聚会是由个人参与者组织的，他们对发起某种新的IETF工作有共同的兴趣。新的IETF工作通常适合现有的工作组，不需要正式的“羽毛鸟”（BOF）会议[RFC5434]来确定社区共识。尽管如此，在社区中，当谈论此类非正式聚会时，通常会使用“bar BOF”一词来讨论潜在的新工作。[RFC4677]（已被[RFC6722]淘汰）将“棒材转炉”描述为：
an unofficial get-together, usually in the late evening, during which a lot of work gets done over drinks. Bar BOFs spring up in many different places around an IETF meeting, such as restaurants, coffee shops, and (if we are so lucky) pools.
非正式聚会一种非正式的聚会，通常在深夜，其间许多工作都是在喝酒的时候完成的。IETF会议期间，酒吧BOF在许多不同的地方涌现，如餐厅、咖啡馆和（如果我们运气好的话）游泳池。
During recent IETF meetings, "bar BOFs" have become increasingly indistinguishable from official IETF BOFs or sometimes even IETF working group meetings. The symptoms of this trend are unofficial "bar BOFs" that are held in regular IETF meeting rooms with
在最近的IETF会议期间，“bar BOF”与IETF官方BOF或有时甚至IETF工作组会议越来越难以区分。这一趋势的症状是在IETF定期会议室举行的非官方的“酒吧聚会”
classroom-style seating, agendas with lengthy slide presentations, use of microphone lines, and even formal consensus calls. And, perhaps most importantly, such meetings have a distinct lack of drinks.
课堂风格的座位、冗长的幻灯片演示议程、麦克风线路的使用，甚至正式的共识电话。而且，也许最重要的是，此类会议明显缺乏饮料。
This document argues that this trend is not helpful in reaching the ultimate goal of many of these get-togethers, i.e., to brainstorm about a technical topic that may eventually lead to new IETF work. It encourages the organizers of these unofficial get-togethers to consider the benefits of holding them in much less formal settings.
本文件认为，这一趋势无助于实现许多此类聚会的最终目标，即就可能最终导致新IETF工作的技术主题进行头脑风暴。它鼓励这些非正式聚会的组织者考虑在不太正式的场合下举行聚会的好处。
This document also recommends that the community abandon the term "bar BOF". The distinction between a BOF, i.e., an official IETF activity, and a "bar BOF", i.e., an unofficial get-together, is lost on many IETF participants, especially newcomers. The similarity in terms has even caused confusion to the point where some participants believe that a "bar BOF" is a required step in the IETF process in order to apply for an official BOF, which is obviously false. For these reasons, the remainder of this document will use the term "side meeting" instead and recommends that the community do the same, in order to stress the unofficial nature of these get-togethers.
本文件还建议社区放弃“bar BOF”一词。许多IETF参与者，尤其是新来者，忘记了BOF（即正式IETF活动）和“bar BOF”（即非正式聚会）之间的区别。术语上的相似性甚至造成了混淆，一些参与者认为“bar BOF”是IETF流程中申请正式BOF的必要步骤，这显然是错误的。出于这些原因，本文件的其余部分将使用“会外会议”一词，并建议社区也这样做，以强调这些聚会的非官方性质。
Before going into more detailed advice on how to hold side meetings, it is important to remember that many participants are extremely busy during an IETF meeting. Although having a side meeting to discuss an idea in an informal face-to-face setting is attractive, the scheduling of such meetings is very difficult and needs to happen weeks, if not months, prior to the meeting itself. Conference calls, email discussions, wikis, jabber group chats, and other ways for interacting are also effective at developing ideas and easier to schedule.
在讨论关于如何举行边会的更详细建议之前，重要的是要记住，许多参与者在IETF会议期间都非常忙。尽管在非正式的面对面环境中举行一次会外会议讨论一个想法很有吸引力，但此类会议的日程安排非常困难，需要在会议召开前几周甚至几个月进行。电话会议、电子邮件讨论、Wiki、jabber群组聊天和其他互动方式也能有效地发展想法，更容易安排日程。
A good rule of thumb is that a side meeting to discuss and develop a proposal for new IETF work should include the necessary participants to achieve that purpose and no more. Smaller meetings are usually more successful than larger meetings.
一个好的经验法则是，讨论和制定新IETF工作提案的会外会议应包括实现该目的所需的参与者，而不是更多。小型会议通常比大型会议更成功。
Hence, it is often useful to limit attendance carefully. Publicly broadcasting an announcement for a side meeting on a particular topic, e.g., on an IETF mailing list, is therefore not usually a good method of inviting the desired set of participants.
因此，谨慎限制出勤率通常是有用的。因此，在IETF邮件列表上公开播放关于特定主题的会外会议公告通常不是邀请所需参与者的好方法。
One reason is that if the announcement happens to attract a large response, the logistics of organizing a side meeting for a larger group quickly becomes very difficult. Small groups fit comfortably around a table at a bar or a restaurant or can find a quiet corner in
一个原因是，如果这一宣布碰巧吸引了大量的回应，那么为一个更大的团体组织一次会外会议的后勤工作很快就会变得非常困难。在酒吧或餐馆里，一小群人舒适地围坐在桌子旁，或者可以在房间里找到一个安静的角落
an IETF hallway for a discussion. Larger groups require dedicated meeting facilities, which are limited during IETF meetings, and they generally require much more careful planning in order to get work done.
用于讨论的IETF走廊。较大的团队需要专用的会议设施，这在IETF会议期间是有限的，为了完成工作，他们通常需要更仔细的规划。
When publicly announcing a side meeting, it is often not even possible for the organizers to determine how large the resulting get-together will be, forcing them to over-provision for the "best case" of a substantial attendance, even in cases where this turns out to be not necessary. And even when a large group comes together, it often mostly consists of "tourists". Tourists usually do not actively participate in the get-together at all, or they participate with an intent to learn about a topic, which can derail a planned discussion of specific issues and turn it into a tutorial. The attendance of tourists requires finding a larger room and makes the interactions between the active participants more cumbersome, e.g., because microphones need to be used in larger rooms. There are times to expose new ideas to a broader community, but think carefully before publicly announcing a side meeting.
在公开宣布会外会议时，组织者往往甚至无法确定由此产生的聚会规模，迫使他们为大量出席的“最佳情况”提供过多的准备，即使事实证明这是不必要的。即使是一个大的群体聚集在一起，也往往由“游客”组成。游客通常根本不积极参加聚会，或者他们参加聚会的目的是了解某个主题，这可能会破坏对特定问题的计划讨论，并将其转化为教程。游客的出席需要找到一个更大的房间，并使活动参与者之间的互动更加繁琐，例如，因为需要在更大的房间使用麦克风。有时会向更广泛的社区展示新想法，但在公开宣布会外会议之前要仔细考虑。
So while publicly announcing a side meeting can be useful in order to gather interested people for a discussion, it often makes sense to still limit attendance. For example, an announcement could say, "We have a table reserved at restaurant X for Y people. If you are interested in attending, please briefly explain how you will contribute to the discussion we are planning to have". If more than Y people respond, the organizers make a selection.
因此，虽然公开宣布会外会议对于聚集感兴趣的人进行讨论是有用的，但仍然限制出席人数通常是有意义的。例如，一则公告可能会说，“我们在X餐厅为Y人预订了一张桌子。如果您有兴趣参加，请简要说明您将如何为我们计划的讨论做出贡献”。如果超过Y人回应，组织者会做出选择。
Selecting or specifically inviting IESG or IAB members is not necessary and may not even be advisable in many cases. Some ideas need time to form before they result in anything cohesive, and a side meeting is a good time to develop new ideas. It is usually most useful to approach Area Directors (ADs) and IAB members for comments after an idea has solidified enough so that an elevator pitch can be given. Also, it should be clear that if an AD or IAB member attends a side meeting, it is not necessarily a show of support. They may simply be interested or often may be concerned or troubled with some aspect of the potential work and relation to existing work. On the other hand, when an AD or IAB member declines to attend a side meeting, that is usually not a sign of disinterest or disapproval -- these people have busy schedules, especially during an IETF week.
选择或特别邀请IESG或IAB成员不是必要的，在许多情况下甚至不可取。有些想法需要时间形成，然后才能产生任何有凝聚力的结果，而会外会议是发展新想法的好时机。通常，在一个想法变得足够坚定后，与区域总监（ADs）和IAB成员联系征求意见是最有用的，这样可以进行电梯宣传。此外，应该清楚的是，如果广告或国际广告协会成员出席会外会议，不一定表示支持。他们可能只是对潜在工作的某些方面以及与现有工作的关系感兴趣，或者经常关心或困扰。另一方面，当AD或IAB成员拒绝参加旁听会议时，这通常不是不感兴趣或不赞成的迹象——这些人的日程安排很忙，尤其是在IETF周。
In the initial stages of developing a proposal for new IETF work, the ability for interested and experienced participants to brainstorm is tremendously important. Brainstorming is facilitated by direct, interactive, and high-bandwidth discussions. This is clearly much more easily achieved in a smaller setting, where half-baked ideas can be dissected and developed. This is often not possible in a larger
在制定新IETF工作提案的初始阶段，有兴趣和经验的参与者进行头脑风暴的能力非常重要。通过直接、交互式和高带宽的讨论，可以促进头脑风暴。这显然更容易在一个较小的环境中实现，在这个环境中，不成熟的想法可以被剖析和发展。在更大的环境中，这通常是不可能的
group. Even worse, a badly run large meeting can sometimes "poison the waters" for a proposed idea by convincing the broader community that the proposal is confused, not ready, or otherwise uninteresting.
组更糟糕的是，一场运作不善的大型会议有时会让更广泛的社区相信提案混乱、没有准备好或无趣，从而“毒害”提议的想法。
Another reason to discuss new work proposals in smaller groups is scope creep, i.e., the tendency of an initially rather tightly scoped area of new work to expand, because people will argue that whatever the initial topic was, it should be expanded to include their particular item of interest. This is harder to control in larger groups. Keeping the scope of new work items narrow is important, because eventual chartering decisions are often much more difficult for larger items of new work than for smaller ones.
在小组中讨论新工作提案的另一个原因是范围蔓延，即一个最初范围相当狭窄的新工作领域有扩大的趋势，因为人们会争辩说，无论最初的主题是什么，都应该扩大到包括他们感兴趣的特定项目。在较大的群体中，这更难控制。保持新工作项目的范围狭窄很重要，因为对于较大的新工作项目，最终的租船决定往往比较小的项目困难得多。
It is important to understand that in the IETF, proposals for new work are judged based on their technical merits and on whether there is enough energy and interest in the community to complete the work in a timely manner. This happens in the relevant working group, if one exists, or else during an official BOF session. How many warm bodies fill a room during an unofficial side meeting has no influence on this decision and is not a good metric for reporting interest in a topic to the community or to employers. Discussions about new work are often controversial, and people will show up just to watch the fireworks, learn about a new topic, or make sure the new work does not interfere with work they are already pursuing, without being interested contributing in some way to the actual proposal itself.
重要的是要了解，在IETF中，新工作的提案是根据其技术优势以及社区是否有足够的精力和兴趣及时完成工作来判断的。如果存在相关工作组，则在相关工作组中进行，或者在BOF正式会议期间进行。在非正式的会外会议期间，有多少温暖的身体填满了一个房间对这个决定没有影响，也不是向社区或雇主报告对某个主题的兴趣的好指标。关于新工作的讨论往往是有争议的，人们会出现只是为了观看焰火，了解新的话题，或者确保新工作不会干扰他们已经在从事的工作，而不会对实际提案本身产生任何兴趣。
Some side meetings are organized to discuss a topic that is also being discussed in an existing working group, either before or after the working group itself meets. Some working groups call these side meetings "ad hoc sessions". The fact that a side meeting is organized by a chair or key participant of a working group in order to discuss topics related to the working group does not make it any more official than other side meetings. An "ad hoc session" is not an official working group session, and no decisions relevant to a working group can be made. Working group consensus can only be established during official sessions or on the mailing list [RFC2418].
一些会外会议是为了讨论现有工作组也正在讨论的一个议题，无论是在工作组开会之前还是之后。一些工作组称这些会外会议为“特别会议”。会外会议由工作组的主席或主要参与者组织，以讨论与工作组有关的议题，这一事实并不意味着会外会议比其他会外会议更正式。“特设会议”不是工作组的正式会议，也不能作出与工作组有关的决定。工作组共识只能在正式会议期间或在邮件列表[RFC2418]上建立。
As the colloquial name "bar BOF" implied, such side meetings are traditionally held in bars or restaurants. Recently, there has been a distinct shift towards holding such get-togethers in regular IETF meeting rooms. One reason for this trend has been discussed in Section 2, namely, that an uncontrolled broadcast announcement requires over-provisioning of facilities.
正如俗称“bar BOF”所暗示的那样，此类会外会议通常在酒吧或餐厅举行。最近，有一个明显的转变，就是在IETF的常规会议室里举行这样的聚会。第2节讨论了这种趋势的一个原因，即不受控制的广播公告要求过度提供设施。
A second reason for this trend is that some participants, e.g., non-native English speakers or participants with hearing difficulties, find it difficult to interact or follow a discussion in noisy environments, such as restaurants and especially bars. The organizers of side meetings are encouraged to take this factor into consideration when finding a meeting place. Quiet restaurants are not hard to find, and many offer private dining rooms at no extra charge for larger parties.
这一趋势的第二个原因是，一些参与者，例如非英语母语人士或听力有困难的参与者，发现在嘈杂的环境中，如餐馆，尤其是酒吧，很难进行互动或跟踪讨论。建议会外会议的组织者在寻找会议地点时考虑到这一因素。安静的餐馆并不难找到，许多餐馆为大型聚会提供免费的私人餐厅。
A likely third reason why side meetings are increasingly held in IETF rooms is that the booking of such a room currently requires approval by an Area Director. The reason for this practice is simply to make sure that IETF-paid rooms are used for meetings that are in the widest sense IETF-related. However, the approval of a room request for a side meeting has been known to sometimes be reported as Area Director "support" for the topic of the meeting to the community or to employers. No such support is expressed or implied when Area Directors approve room requests! Many routinely say "yes" to every incoming request as long as there are meeting rooms available (and there are typically lots of meeting rooms available outside of normal working group meeting slots).
IETF会议室越来越多地举行会外会议的第三个原因可能是，预订此类会议室目前需要区域总监的批准。这种做法的原因只是为了确保IETF付费房间用于最广泛意义上与IETF相关的会议。然而，据了解，批准旁听会议的会议室请求有时会被报告为区域主管对社区或雇主会议主题的“支持”。当区域主管批准房间请求时，不会明示或暗示此类支持！只要有可用的会议室（通常在正常工作组会议时间之外有很多可用的会议室），许多人都会对每个传入的请求例行地说“是”。
Holding side meetings in IETF meeting rooms does not make them any more official or valid than get-togethers that happen in other places. Participants have recently begun to list the times and locations of some side meetings on a wiki page, but that does not make them part of the official IETF agenda or otherwise change their unofficial status.
在IETF会议室举行边会并不比在其他地方举行的聚会更正式或有效。参与者最近开始在维基页面上列出一些会外会议的时间和地点，但这并不能使它们成为IETF官方议程的一部分，也不能改变它们的非官方状态。
IETF meeting rooms clearly do not provide the most supportive environment for side meetings that require brainstorming on a new technical proposal. One reason is that the classroom-style seating often present in IETF meeting rooms tends to spread people out in rows, all facing towards a front presenter, which is good for presentations but bad for discussion. Because IETF meeting rooms tend to be large and people have a natural tendency to spread out, holding a meeting in one often requires microphone use, which is cumbersome, slows a discussion down, and leads to "question-answer" dialogs between two people, which is much less effective than a group discussion around a restaurant table.
IETF会议室显然不能为需要就新技术提案进行头脑风暴的会外会议提供最有利的环境。一个原因是，IETF会议室中经常出现的教室式座位往往会让人排成一行，所有人都面向前面的演示者，这对演示很有好处，但对讨论很不利。由于IETF会议室往往很大，而且人们自然会分散开来，因此在一个会议室中举行会议通常需要使用麦克风，这很麻烦，会减慢讨论速度，并导致两人之间的“问答”对话，这比在餐厅桌子周围进行小组讨论的效果要差得多。
Another reason is more pragmatic. Because the organizers of unofficial get-togethers can only use IETF meeting rooms during times when they are not otherwise in use, such side meetings often happen during breakfast, lunch, dinner, or later in the evening. This prolongs the time during which IETF participants are stuck in the same rooms they're stuck in for the rest of the day, and it prevents them from having a regular and at least somewhat relaxed meal.
另一个原因是更加务实。由于非官方聚会的组织者只能在不使用IETF会议室的情况下使用IETF会议室，因此此类会外会议通常在早餐、午餐、晚餐或晚些时候举行。这延长了IETF参与者在一天剩下的时间里被困在同一个房间里的时间，并使他们无法有规律地、至少在某种程度上放松地用餐。
Anecdotal evidence exists that at least one Area Director has not been able to set foot outside the IETF hotel for a stretch of several days during IETF 77. (IETF 77 was held in Anaheim, CA, and the food options in and near the hotel were, let's say, of severely limited quality.) It is unlikely that participants in the consequential mental and bodily state will make productive contributions to a side meeting or, in the case of Area Directors, will be extremely receptive towards new work proposals.
有传闻证据表明，在IETF 77期间，至少有一位区域主管在几天的时间里未能走出IETF酒店。（IETF 77在加利福尼亚州阿纳海姆举行，酒店内和附近的食物选择，比如说，质量非常有限。）因此，精神和身体状态的参与者不太可能对会外会议做出有成效的贡献，或者，如果是区域主管，则不太可能接受新的工作建议。
Food, drink, and a relaxed atmosphere in which to have a discussion are an essential part of a successful side meeting, because they often need to happen during meal times. IETF meeting rooms offer neither.
食物、饮料和轻松的讨论氛围是成功的会外会议的重要组成部分，因为它们通常需要在用餐时间进行。IETF会议室两者都不提供。
Several of the recent side meetings that were held in IETF meeting rooms emulated official IETF meetings to a degree that made them indistinguishable from a regular working group meeting for the average IETF attendee. This included detailed agendas, lengthy presentations, organizers who refer to themselves as "bar BOF chairs", emulating blue sheets (see Section 4.5 of [RFC4677]), and even hums and other consensus calls (see Section 5.2 of [RFC4677]).
最近在IETF会议室举行的几次会外会议模拟了IETF官方会议，使其与IETF普通与会者的常规工作组会议难以区分。这包括详细的议程、冗长的演讲、自称为“bar BOF主席”的组织者、模仿蓝纸（见[RFC4677]第4.5节），甚至HUM和其他共识呼吁（见[RFC4677]第5.2节）。
It is not clear as to why this has been happening. One attempt at an explanation may be that holding a get-together in an IETF room and having the organizers behave like chairs behave during regular IETF sessions is causing a Pavlovian stimulus in the attendees. Another explanation attempt is that an IETF meeting room simply does not allow many other forms of discussion. Finally, some organizers may find the process to apply for an official BOF too complex or troublesome (and probably rightfully so) and so decide to simply mimic one, or they had applied for an official BOF, got turned down, and then decided to hold the same meeting as a side meeting.
目前尚不清楚为什么会发生这种情况。一种解释可能是，在IETF会议室举行聚会，让组织者在IETF常规会议期间表现得像椅子一样，会在与会者中引起巴甫洛夫式的刺激。另一种解释是IETF会议室不允许其他形式的讨论。最后，一些组织者可能会发现申请正式BOF的过程太复杂或麻烦（可能是理所当然的），于是决定简单地模仿一个，或者他们申请了正式BOF，但遭到拒绝，然后决定举行与会外会议相同的会议。
Whatever the reason for this development, it is reasonably obvious that running a side meeting with a focus on making quick progress on a technical proposal in a way that emulates running a working group session is not very productive. Working group sessions follow certain procedures due to larger audiences, the need to establish formal consensus, etc., that a side meeting can do without.
无论这种发展的原因是什么，很明显，以模拟工作组会议的方式，召开一次侧重于在技术提案上取得快速进展的会外会议并不是很有成效。工作组会议遵循某些程序，因为听众较多，需要建立正式共识等，而会外会议可以不采用这些程序。
Having side meetings mimic working group meetings is also confusing to attendees. In at least one case, some side meeting participants believed that they were attending an actual working group meeting, and incorrect press announcements were generated. When side meetings take place at restaurants or elsewhere away from IETF meeting rooms, the chance for confusion is much lower.
让旁听会议模仿工作组会议也会让与会者感到困惑。至少在一个案例中，一些会外会议参与者认为他们正在参加一次实际的工作组会议，并发布了不正确的新闻公告。如果在餐厅或IETF会议室以外的其他地方举行旁听会议，则产生混淆的可能性要小得多。
Because the reasons for organizing such a get-together are diverse, this section is not making more specific suggestions, other than to note that meeting outside of an IETF meeting room is likely going to shift the dynamics sufficiently so that better interactions and results become possible.
由于组织此类聚会的原因多种多样，本节不提供更具体的建议，只需注意在IETF会议室外举行的会议可能会充分改变动态，从而使更好的互动和结果成为可能。
Side meetings are often scheduled following IETF evening plenaries, which sometimes end before the time indicated on the meeting agenda but have in the past also ended much later. It is therefore useful to avoid scheduling side meetings that follow IETF plenaries at a fixed time. Instead, it is recommended to schedule them relative to the end of the plenary, i.e., "X minutes after the end of the plenary". That way, attendees do not need to wait around if a plenary finishes early and do not need to leave a plenary should it run late.
会外会议通常安排在IETF晚间全体会议之后，有时会在会议议程上指定的时间之前结束，但过去也会晚很多。因此，避免在固定时间安排IETF全体会议之后的会外会议是很有用的。相反，建议将其安排在全体会议结束后，即“全体会议结束后X分钟”。这样，如果全体会议提前结束，与会者就不需要等待，如果全体会议晚了，也不需要离开。
Section 3 of [RFC5434] raises the issue that it is essential to understand all angles of a given problem for which IETF work is proposed. This means that input from the community that can be found at IETF meetings is not all that should be considered. It can be argued that input from other communities -- operator, research, regulatory, etc. -- is at least as important. Hence, organizers should consider the value of holding side meetings at venues where such input can be more easily gathered, such as operator fora (RIPE, NANOG, etc.), research conferences, or other events.
[RFC5434]的第3节提出了一个问题，即必须从各个角度理解提出IETF工作的给定问题。这意味着，在IETF会议上可以找到的来自社区的输入并不是应该考虑的全部。可以说，来自其他社区的投入——运营商、研究机构、监管机构等——至少同样重要。因此，组织者应考虑在更容易收集此类输入的场馆举行会议的价值，如运营商FARA（成熟、NANOG等）、研究会议或其他事件。
Side meeting organizers are encouraged to rekindle the original spirit behind them and organize them outside IETF meeting rooms, at venues with food and drink, for smaller groups, and in a way that does not needlessly mimic the way official IETF sessions are conducted.
鼓励会外会议组织者重新燃起他们背后的原始精神，在IETF会议室外、有食物和饮料的场所为小团体组织会议，并且以不必要模仿IETF正式会议进行方式的方式组织会议。
It can often be useful to discuss proposals for new IETF work face-to-face in an informal setting, but conference calls, email discussions, wikis, and other means for interactions are also effective at developing ideas, especially given the scheduling difficulties when busy individuals are involved during an IETF meeting.
在非正式环境中面对面讨论新IETF工作的建议通常是有用的，但电话会议、电子邮件讨论、Wiki和其他互动方式也能有效地发展想法，特别是考虑到在IETF会议期间忙碌的个人参与时，日程安排的困难。
Finally, it is important to remember that all side meetings during an IETF week are purely informal and have no official status whatsoever.
最后，重要的是要记住，IETF周内的所有会外会议都是纯粹的非正式会议，没有任何官方身份。
A security AD pointed out that people have been known to forget their laptops after side meetings held in real bars. The organizers of side meetings should therefore remind any attending security ADs (and possibly others) to take their belongings with them after the side meeting ends or the bar closes, whichever happens first.
一则安全广告指出，众所周知，人们在真正的酒吧里开完会后会忘记带笔记本电脑。因此，会外会议的组织者应提醒所有出席安全广告的人（可能还有其他人）在会外会议结束或酒吧关门后随身携带物品，以先到者为准。
The name and title of this document have been chosen to resemble those used by Thomas Narten for his guidelines document on holding a successful BOF [RFC5434], as a sign of appreciation for a document that has proven to be invaluable many times over.
本文件的名称和标题与托马斯·纳滕（Thomas Narten）在其关于成功举办BOF的指导文件[RFC5434]中使用的名称和标题相似，作为对一份被多次证明具有宝贵价值的文件的赞赏。
Several folks provided feedback and input on this document, including Jari Arkko, Fred Baker, Scott Bradner, Ben Campbell, Jorge Contreras, Spencer Dawkins, Ralph Droms, Wesley Eddy, Frank Ellermann, Adrian Farrel, Stephen Farrell, David Harrington, Russ Housley, Cullen Jennings, John Klensin, Al Morton, Robert Sparks, and Dan Wing.
一些人就这份文件提供了反馈和意见，包括贾里·阿克科、弗雷德·贝克、斯科特·布拉德纳、本·坎贝尔、豪尔赫·孔特雷拉斯、斯宾塞·道金斯、拉尔夫·德罗姆斯、卫斯理·艾迪、弗兰克·埃勒曼、阿德里安·法雷尔、斯蒂芬·法雷尔、大卫·哈林顿、罗斯·霍斯利、卡伦·詹宁斯、约翰·克莱辛、艾尔·莫顿、罗伯特·斯帕克斯和丹·温。
Lars Eggert was partly funded by [TRILOGY], a research project supported by the European Commission under its Seventh Framework Program.
拉尔斯·艾格特（Lars Eggert）的部分资金来自于[三部曲]，这是一个由欧盟委员会第七框架计划支持的研究项目。
[RFC2418] Bradner, S., "IETF Working Group Guidelines and Procedures", BCP 25, RFC 2418, September 1998.
[RFC2418]Bradner，S.，“IETF工作组指南和程序”，BCP 25，RFC 2418，1998年9月。
[RFC4677] Hoffman, P. and S. Harris, "The Tao of IETF - A Novice's Guide to the Internet Engineering Task Force", RFC 4677, September 2006.
[RFC4677]Hoffman，P.和S.Harris，“IETF之道-互联网工程任务组新手指南”，RFC 4677，2006年9月。
[RFC5434] Narten, T., "Considerations for Having a Successful Birds-of-a-Feather (BOF) Session", RFC 5434, February 2009.
[RFC5434]Narten，T.，“成功举行羽鸟（BOF）会议的考虑因素”，RFC 5434，2009年2月。
[RFC6722] Hoffman, P., "Publishing the "Tao of the IETF" as a Web Page", RFC 6722, August 2012.
[RFC6722]Hoffman，P.，“将“IETF之道”发布为网页”，RFC 6722，2012年8月。
[TRILOGY] "Trilogy Project", <http://www.trilogy-project.org/>.
[三部曲]“三部曲项目”<http://www.trilogy-project.org/>.
Authors' Addresses
作者地址
Lars Eggert NetApp Sonnenallee 1 Kirchheim 85551 Germany
德国基尔希海姆1号拉尔斯·埃格特·内塔普·索内纳利85551
Phone: +49 151 12055791
EMail: lars@netapp.com
URI: http://eggert.org/
Phone: +49 151 12055791
EMail: lars@netapp.com
URI: http://eggert.org/
Gonzalo Camarillo Ericsson Hirsalantie 11 Jorvas 02420 Finland
Gonzalo Camarillo Ericsson Hirsalantie 11 Jorvas 02420芬兰
EMail: Gonzalo.Camarillo@ericsson.com
EMail: Gonzalo.Camarillo@ericsson.com