Network Working Group S. Dawkins
Request for Comments: 5078 Huawei (USA)
Updates: 3777 October 2007
Category: Informational
Network Working Group S. Dawkins
Request for Comments: 5078 Huawei (USA)
Updates: 3777 October 2007
Category: Informational
IAB and IESG Selection, Confirmation, and Recall Process: Revision of the Nominating and Recall Committees Timeline
IAB和IESG选择、确认和召回流程：修订提名和召回委员会时间表
Status of This Memo
关于下段备忘
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Abstract
摘要
RFC 3777 defines the Nominations and Recall Committee's (NomCom's) operation, and includes a sample timeline for major steps in the NomCom process that meets the minimum normative requirements for the process. Recent NomComs have been scheduling based on the sample timeline, and the chairs of the last three NomComs -- Danny McPherson (2004-2005), Ralph Droms (2005-2006), and Andrew Lange (2006-2007) -- have all reported that this timeline is very aggressive and suggested starting earlier. This document restructures the sample timeline, but makes no normative process changes.
RFC 3777定义了提名和召回委员会（NomCom）的运作，并包括NomCom流程中满足流程最低规范要求的主要步骤的样本时间表。最近的NOMCOM是根据样本时间安排的，最近三次NOMCOM的主席——丹尼·麦克弗森（2004-2005）、拉尔夫·德罗姆斯（2005-2006）和安德鲁·兰格（2006-2007）——都报告说，这一时间安排非常积极，建议早点开始。本文件对样本时间线进行了重组，但未对规范性流程进行任何更改。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Problem . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Interaction with IETF Face-to-Face Meeting Schedule . . . . . . 3
4. Proposed Solution . . . . . . . . . . . . . . . . . . . . . . . 3
5. Sample Timeline for 2008-2009 NomCom Schedule . . . . . . . . . 4
6. Some Observations from the 2007-2008 NomCom Experience . . . . 6
7. Out-of-Scope Suggestions Requiring Normative Text Changes . . . 6
8. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7
10. Normative References . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Problem . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Interaction with IETF Face-to-Face Meeting Schedule . . . . . . 3
4. Proposed Solution . . . . . . . . . . . . . . . . . . . . . . . 3
5. Sample Timeline for 2008-2009 NomCom Schedule . . . . . . . . . 4
6. Some Observations from the 2007-2008 NomCom Experience . . . . 6
7. Out-of-Scope Suggestions Requiring Normative Text Changes . . . 6
8. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7
10. Normative References . . . . . . . . . . . . . . . . . . . . . 7
RFC 3777 ([RFC3777]) is a complete specification of the process by which members of the IAB and IESG are selected, confirmed, and recalled as of the date of its approval. [RFC3777] includes normative requirements for timing allowed for the various steps, and also includes an informative appendix, Appendix B, that contains a timeline based on the normative text.
RFC 3777（[RFC3777]）是一份完整的流程规范，通过该流程，IAB和IESG的成员在其批准之日被选择、确认和召回。[RFC3777]包括各种步骤所允许的时间安排的规范性要求，还包括信息性附录附录附录B，其中包含基于规范性文本的时间表。
The normative time requirements in [RFC3777] are end-of-task, so adjusting the informative timeline to get an earlier start does not require changes to the normative text in [RFC3777].
[RFC3777]中的规范性时间要求是任务结束，因此调整信息性时间线以提前开始不需要更改[RFC3777]中的规范性文本。
In IETF 68, IETF 65, and IETF 62 plenary reports, NomCom chairs suggested starting the NomCom cycle earlier. This document describes a timeline that meets this need, replacing RFC 3777, Appendix B, and makes no other changes to [RFC3777].
在IETF 68、IETF 65和IETF 62全体会议报告中，NomCom主席建议提前开始NomCom周期。本文件描述了满足这一需求的时间表，取代了RFC 3777附录B，并对[RFC3777]进行了其他更改。
There are several reasons that have been cited for the schedule pressures reported by recent NomComs.
最近的NOMCOM报告的进度压力有几个原因。
o A few common practices are not accounted for in the Appendix B timeline [RFC3777]. For example, it is common to allow a week for notifying unsuccessful nominees before the formal announcement is made. This is not included in the timeline.
o 附录B时间表[RFC3777]中未说明一些常见做法。例如，在正式宣布之前，通常会留出一周时间通知未获得提名的候选人。这不包括在时间线中。
o Some tasks just seem to take longer than the minimum interval. For example, a public "call for volunteers" must be open for 30 days, but the list of voting NomCom participants probably isn't announced at midnight on the 30th day. Anecdotal evidence is that allowing about 6 weeks is more consistent with recent experience.
o 有些任务似乎花费的时间超过了最小间隔。例如，一个公开的“志愿者征集”必须开放30天，但投票的NomCom参与者名单可能不会在30天的午夜宣布。传闻证据表明，允许大约6周的时间与最近的经验更为一致。
o The NomCom, and the community it serves, tends to celebrate a variety of holidays between the third IETF and the first IETF of the next year, so people may be out of the office, may wait to respond, etc.
o NomCom及其服务的社区倾向于在第三届IETF和明年第一届IETF之间庆祝各种节日，因此人们可能不在办公室，可能等待回应，等等。
o The Appendix B timeline does not provide flexibility in case of problems. For example, the NomCom chair "reset" the random selection of volunteers for the 2006-2007 NomCom, requiring another seven-day delay for the announcement of the date of random selection.
o 附录B的时间表在出现问题时不提供灵活性。例如，NomCom主席“重置”2006-2007年NomCom志愿者的随机选择，要求再延迟七天宣布随机选择的日期。
All of these reasons can be accommodated by simply starting earlier than is absolutely required.
所有这些原因都可以通过比绝对需要的更早启动来解决。
In addition to these reasons for schedule pressure, it's worth noting that the NomCom schedule and the IETF face-to-face meeting cycle don't complement each other.
除了这些日程压力的原因外，值得注意的是，NomCom日程和IETF面对面会议周期并不相辅相成。
o When the NomCom volunteers are selected after the second IETF, they don't have an opportunity to meet face-to-face and "get organized" until the third IETF, when they should be winding up their deliberations. This missed opportunity forces them to use teleconferences and other less efficient means of communications to get organized.
o 当第二次IETF后选择NomCom志愿者时，他们没有机会面对面会面并“组织起来”，直到第三次IETF结束他们的讨论。这种错失的机会迫使他们使用电话会议和其他效率较低的通信手段来组织。
o The NomCom volunteers don't have a chance to conduct interviews with the community, or with nominees, until the third IETF, during the height of the NomCom effort. If the NomCom effort took place before the third IETF, the NomCom could work on difficult nominations, and meet face-to-face with nominees under consideration.
o 在第三届IETF之前，在NomCom努力的高潮期间，NomCom志愿者没有机会与社区或被提名者进行访谈。如果NomCom的工作在第三届IETF之前进行，NomCom可以处理困难的提名，并与考虑中的提名人面对面地会面。
o If the NomCom is able to start interviews during the second IETF meeting, starting earlier than is absolutely required may also help NomCom be more effective.
o 如果NomCom能够在第二次IETF会议期间开始面试，那么比绝对要求的时间更早开始面试也可能有助于NomCom更有效。
The high-level description of the proposal is, of course, "start earlier", but more precision would be helpful.
当然，该提案的高层描述是“尽早开始”，但更精确的描述会有所帮助。
A sample, hypothetical timeline that meets these guidelines is shown in Section 5. Please note that, like Appendix B in [RFC3777], this timeline is not normative, but it meets the normative requirements stated in [RFC3777].
第5节显示了符合这些指南的假设时间线示例。请注意，与[RFC3777]中的附录B一样，该时间线不是规范性的，但符合[RFC3777]中规定的规范性要求。
Other timelines are certainly possible, including timelines that allow the NomCom to report its results more than one month before the first IETF, where the slate of nominees is announced. Finishing early may be a good thing.
其他时间表当然是可能的，包括允许NomCom在第一届IETF之前一个多月报告其结果的时间表，届时将公布提名名单。提前完成可能是件好事。
It's worth noting that the first step in the timeline is "ISOC president appoints NomCom chair". This doesn't happen as an IETF responsibility, but the reality is that the ISOC president needs to identify NomCom chair candidates around the time of the first IETF; she needs to have a shortlist 3 or 4 weeks after the first IETF. This document suggests (but does not add a normative requirement to [RFC3777]) that the outgoing NomCom Chair should verify that this process is triggered during the first IETF.
值得注意的是，时间表的第一步是“ISOC主席任命NomCom主席”。这并不是IETF的职责，但现实是，ISOC主席需要在第一次IETF期间确定NomCom主席候选人；她需要在第一次IETF后3或4周有一份入围名单。本文件建议（但未在[RFC3777]中添加规范性要求），即将离任的NomCom主席应验证该过程是否在第一次IETF期间触发。
1. One week is allowed for the NomCom chair to publish milestones.
1. NomCom主席有一周的时间发布里程碑。
2. Six weeks are allowed for solicitation of NomCom participants.
2. NomCom参与者的邀约时间为六周。
3. One week is allowed for confirmation of the selection of voting members -- to allow at least some time for resolution if there is a problem.
3. 有一周的时间来确认投票成员的选择——如果有问题，至少有一段时间来解决。
4. The recommended time for NomCom self-organization is increased to six weeks.
4. NomCom自组织的建议时间增加到六周。
5. One week is allowed for NomCom establishing milestones.
5. NomCom有一周的时间建立里程碑。
6. In the sample timeline (Table 1), an additional five weeks is allowed for the nominating bodies to select candidates.
6. 在抽样时间表（表1）中，提名机构还有五周时间选择候选人。
7. The timeline is adjusted to allow one week at the end of the process for notification of unsuccessful candidates.
7. 对时间表进行了调整，以便在流程结束时有一周的时间通知不合格的候选人。
This significantly increases the amount of time available for NomCom to select candidates while still meeting the normative requirements of [RFC3777].
这大大增加了NomCom选择候选人的可用时间，同时仍然满足[RFC3777]的规范要求。
The following table shows a sample timeline for the 2008-2009 NomCom schedule, based on the IETF dates for the second IETF (72nd IETF, held July 27 - August 1, 2008), third IETF (73rd IETF, held November 16-21, 2008), and first IETF (74 IETF, held March 22-27, 2009).
下表显示了2008-2009年NomCom时间表的样本时间线，基于第二届IETF（第72届IETF，于2008年7月27日至8月1日举行）、第三届IETF（第73届IETF，于2008年11月16日至21日举行）和第一届IETF（74届IETF，于2009年3月22日至27日举行）的IETF日期。
Note that the duration of each milestone step is adjusted as necessary for each NomCom, since the scheduled dates for IETF meetings vary from year to year. This timeline allows the NomCom to begin self organizing at the Second IETF (this is what "on time") means in the table).
请注意，由于IETF会议的预定日期每年不同，因此每个NomCom的每个里程碑步骤的持续时间都会根据需要进行调整。该时间线允许NomCom在第二次IETF时开始自组织（这是表中“准时”的意思）。
+------------+-----------------+----------+--------------+----------+
| RFC 3777 | What happens | new | start date | old |
| Appendix B | | duration | (YYYY/MM/DD) | duration |
| reference | | (weeks) | | (weeks) |
+------------+-----------------+----------+--------------+----------+
| 1 | ISOC president | 0 | 2008/05/25 | 0 |
| | appoints NomCom | | | |
| | chair | | | |
| 2 | NomCom chair | 1 | 2008/05/25 | 0 |
| | publishes | | | |
| | milestones | | | |
| 3 | Solicitation of | 6 | 2008/06/01 | 30 days |
| | NomCom | | | |
| | participants | | | |
| 4 | Announce date | 1 | 2008/07/13 | 1 |
| | of random | | | |
| | selection | | | |
| 5 | Announce NomCom | 1 | 2008/07/20 | 1 |
| | membership, | | | |
| | challenge | | | |
| | period | | | |
| 6 | Verify NomCom | 0 | 2008/07/27 | 0 |
| | membership | | | |
| | during | | | |
| | challenge | | | |
| | period | | | |
| 7 | Confirm NomCom | 1 | 2008/07/27 | 0 |
| | membership | | | |
| 8 | NomCom self | 6 | 2008/08/03 | 4 |
| | organizes (on | | | |
| | time) | | | |
| 9 | END | 0 | 2008/09/14 | 0 |
| | organization, | | | |
| | BEGIN selection | | | |
| 10 | NomCom | 1 | 2008/09/14 | 0 |
| | establishes | | | |
| | milestones | | | |
| 11 | Nominating | 17 | 2008/09/21 | 12 |
| | bodies select | | | |
| | candidates | | | |
| 12 | END selection, | 0 | 2009/01/18 | 0 |
| | BEGIN | | | |
| | confirmation of | | | |
| | candidates | | | |
| 13 | Present slate | 0 | 2009/01/18 | 0 |
| | of candidates | | | |
| | to confirming | | | |
| | bodies | | | |
+------------+-----------------+----------+--------------+----------+
| RFC 3777 | What happens | new | start date | old |
| Appendix B | | duration | (YYYY/MM/DD) | duration |
| reference | | (weeks) | | (weeks) |
+------------+-----------------+----------+--------------+----------+
| 1 | ISOC president | 0 | 2008/05/25 | 0 |
| | appoints NomCom | | | |
| | chair | | | |
| 2 | NomCom chair | 1 | 2008/05/25 | 0 |
| | publishes | | | |
| | milestones | | | |
| 3 | Solicitation of | 6 | 2008/06/01 | 30 days |
| | NomCom | | | |
| | participants | | | |
| 4 | Announce date | 1 | 2008/07/13 | 1 |
| | of random | | | |
| | selection | | | |
| 5 | Announce NomCom | 1 | 2008/07/20 | 1 |
| | membership, | | | |
| | challenge | | | |
| | period | | | |
| 6 | Verify NomCom | 0 | 2008/07/27 | 0 |
| | membership | | | |
| | during | | | |
| | challenge | | | |
| | period | | | |
| 7 | Confirm NomCom | 1 | 2008/07/27 | 0 |
| | membership | | | |
| 8 | NomCom self | 6 | 2008/08/03 | 4 |
| | organizes (on | | | |
| | time) | | | |
| 9 | END | 0 | 2008/09/14 | 0 |
| | organization, | | | |
| | BEGIN selection | | | |
| 10 | NomCom | 1 | 2008/09/14 | 0 |
| | establishes | | | |
| | milestones | | | |
| 11 | Nominating | 17 | 2008/09/21 | 12 |
| | bodies select | | | |
| | candidates | | | |
| 12 | END selection, | 0 | 2009/01/18 | 0 |
| | BEGIN | | | |
| | confirmation of | | | |
| | candidates | | | |
| 13 | Present slate | 0 | 2009/01/18 | 0 |
| | of candidates | | | |
| | to confirming | | | |
| | bodies | | | |
| 14 | Confirming | 4 | 2009/01/18 | 4 |
| | bodies accept | | | |
| | or reject | | | |
| (added | Notify | 1 | 2009/02/15 | |
| step) | unsuccessful | | | |
| | nominees | | | |
| 15 | Slate announced | 4 | 2009/02/22 | 4 |
| | 1 month before | | | |
| | 1st IETF | | | |
| | 1st IETF | | 2009/03/22 | |
+------------+-----------------+----------+--------------+----------+
| 14 | Confirming | 4 | 2009/01/18 | 4 |
| | bodies accept | | | |
| | or reject | | | |
| (added | Notify | 1 | 2009/02/15 | |
| step) | unsuccessful | | | |
| | nominees | | | |
| 15 | Slate announced | 4 | 2009/02/22 | 4 |
| | 1 month before | | | |
| | 1st IETF | | | |
| | 1st IETF | | 2009/03/22 | |
+------------+-----------------+----------+--------------+----------+
New Step 1 Date: 2008/05/25, Old Step 1 Date: 2008/08/29
New Step 1 Date: 2008/05/25, Old Step 1 Date: 2008/08/29
Table 1
表1
Since the timeline described in this specification makes no normative changes to [RFC3777], the 2007-2008 NomCom process started using the new timeline to gain experience and shake out unexpected consequences. We discovered the following things:
由于本规范中描述的时间线未对[RFC3777]进行规范性更改，2007-2008年NomCom流程开始使用新的时间线获得经验并摆脱意外后果。我们发现了以下几点：
1. It is worth pointing out that the [RFC3777] requirement for eligibility, "Members of the IETF community must have attended at least 3 of the last 5 IETF meetings in order to volunteer.", is affected when the NomCom chair issues an earlier call for volunteers. For example, using the 2008-2009 NomCom example in the doc: under the old schedule, a prospective member would need to have attended three of IETF meetings 68-72. Under the new schedule, that becomes three of IETF meetings 67-71.
1. 值得指出的是，[RFC3777]资格要求“IETF社区成员必须至少参加了过去5次IETF会议中的3次，才能成为志愿者。”在NomCom主席提前发出志愿者呼吁时受到影响。例如，使用doc中的2008-2009年NomCom示例：根据旧时间表，潜在成员需要参加IETF会议68-72中的三次。根据新的时间表，这将成为IETF第67-71次会议中的三次。
2. It's worth noting that when NomCom uses the earlier timeline, incumbents under review who were appointed to one-year terms have only one IETF meeting cycle to establish a track record before NomCom begins considering whether they should be retained. This situation is rare but not unknown. The recent split of the RAI area out of TSV created two one-year terms (one in RAI, and one in TSV), and this can also happens if an IESG or IAB member resigns with more than one year remaining in the member's term.
2. 值得注意的是，当NomCom使用较早的时间表时，被任命为一年任期的在任者只有一个IETF会议周期，以便在NomCom开始考虑是否应保留他们之前建立跟踪记录。这种情况很少见，但并非未知。最近将RAI地区从TSV中分离出来，产生了两个为期一年的任期（一个在RAI，一个在TSV），如果IESG或IAB成员在其任期剩余一年以上的情况下辞职，也会发生这种情况。
While there are very few avoidable serialized delays in [RFC3777], we note that the minimum 30-day delay for volunteers is serialized after the NomCom chair is named. This delay accounts for more than half the elapsed time between the NomCom chair being named and the NomCom itself forming. If a future normative revision to [RFC3777] changed
虽然[RFC3777]中很少有可避免的序列化延迟，但我们注意到，志愿者的最小30天延迟是在命名NomCom主席后序列化的。这一延迟占了从提名NomCom主席到NomCom本身形成所用时间的一半以上。如果[RFC3777]的未来规范性修订发生变更
the mechanics for this call for volunteers, this call could be issued while the NomCom chair is still being selected. This would allow the new NomCom chair to begin work by announcing the date of random selection, instead of just waiting for the volunteers to volunteer.
这一呼吁的机制为志愿者，这一呼吁可以在NomCom主席仍然被选中时发出。这将允许新的NomCom主席通过宣布随机选择的日期开始工作，而不是仅仅等待志愿者自愿。
One possible trigger would be to have the outgoing NomCom chair issue the call for volunteers on behalf of the successor NomCom chair, who may not yet be identified, at the first IETF meeting each year.
一个可能的触发因素是，让即将离任的NomCom主席在每年的第一次IETF会议上代表继任的NomCom主席（可能尚未确定继任者）发出志愿者呼吁。
The NomCom timeline changes suggested in this document do not directly affect the security of the Internet.
本文件中建议的NomCom时间线变更不会直接影响互联网的安全。
This draft is based on conversations with the chairs of the last three NomComs: Danny McPherson (2004-2005), Ralph Droms (2005-2006), and Andrew Lange (2006-2007), and on their corresponding plenary NomCom Report presentations at IETF 62, IETF 65, and IETF 68, respectively.
本草案基于与前三届NomCom主席的对话：丹尼·麦克弗森（2004-2005）、拉尔夫·德罗姆斯（2005-2006）和安德鲁·兰格（2006-2007），以及他们分别在IETF 62、IETF 65和IETF 68上的相应全体NomCom报告陈述。
The 2007 IESG discussed Andrew Lange's report at their face-to-face retreat and requested a proposal that adjusted the informative timeline with no normative changes.
2007年IESG在面对面会议上讨论了Andrew Lange的报告，并要求提出一项建议，在不改变规范的情况下调整信息量大的时间表。
Thanks to Russ Housley, current General Area director, for reviewing an early version of this draft.
感谢现任总区域主任Russ Housley审阅了该草案的早期版本。
Thanks to Brian Carpenter, who pointed out that the IETF NomCom portion of the timeline depends on the ISOC president appointing the NomCom chair soon after the first IETF ("NomCom chairs don't appear magically"), and provided a suggestion for ensuring that this happens in a timeframe that allows NomCom to begin self organizing at the Second IETF meeting each year.
感谢Brian Carpenter，他指出IETF NomCom部分的时间表取决于ISOC主席在第一次IETF后不久任命NomCom主席（“NomCom主席不会神奇地出现”），并提出了一项建议，以确保在允许NomCom在每年第二次IETF会议上开始自组织的时间范围内实现这一点。
Thanks to Sam Weiler, who pointed out the shift in meeting attendance requirements described in Section 6.
感谢Sam Weiler，他指出了在满足第6节中描述的出勤要求方面的转变。
We should also thank the editors of previous NomCom procedures for developing a specification that we could "speed up" without changing normative text.
我们还应该感谢先前NomCom程序的编辑，他们制定了一个规范，我们可以在不改变规范文本的情况下“加速”。
[RFC3777] Galvin, J., "IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees", BCP 10, RFC 3777, June 2004.
[RFC3777]Galvin，J.，“IAB和IESG选择、确认和召回流程：提名和召回委员会的运作”，BCP 10，RFC 3777，2004年6月。
Author's Address
作者地址
Spencer Dawkins Huawei Technologies (USA) 1547 Rivercrest Blvd. Allen, TX 75002 USA
斯宾塞·道金斯华为技术（美国）里弗克雷斯特大道1547号。美国德克萨斯州艾伦75002
Phone: +1 469 229 5397
EMail: spencer@mcsr-labs.org
Phone: +1 469 229 5397
EMail: spencer@mcsr-labs.org
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.