RFC 8067: Updating When Standards Track Documents May Refer Normatively to Documents at a Lower Level 中文翻译

URL : https://datatracker.ietf.org/doc/html/rfc8067
标题 : RFC 8067
翻译类型 : 自动生成

Internet Engineering Task Force (IETF)                          B. Leiba
Request for Comments: 8067                           Huawei Technologies
BCP: 97                                                     January 2017
Updates: 3967
Category: Best Current Practice
ISSN: 2070-1721

Internet Engineering Task Force (IETF)                          B. Leiba
Request for Comments: 8067                           Huawei Technologies
BCP: 97                                                     January 2017
Updates: 3967
Category: Best Current Practice
ISSN: 2070-1721

Updating When Standards Track Documents May Refer Normatively to Documents at a Lower Level

标准跟踪文档时的更新可能会规范性地引用较低级别的文档

Abstract

摘要

RFC 3967 specifies a process for allowing normative references to documents at lower maturity levels ("downrefs"), which involves calling out the downref explicitly in the Last Call notice. That requirement has proven to be unnecessarily strict, and this document updates RFC 3967, allowing the IESG more flexibility in accepting downrefs in Standards Track documents.

RFC 3967规定了允许在较低到期水平（“downref”）上引用规范性文件的流程，其中包括在最后一次催缴通知中明确调用downref。这一要求被证明是不必要的严格，本文件更新了RFC 3967，使IESG在接受标准跟踪文件中的DOWNREF时具有更大的灵活性。

Status of This Memo

关于下段备忘

This memo documents an Internet Best Current Practice.

本备忘录记录了互联网最佳实践。

This document is a product of the Internet Engineering Task Force (IETF). It has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on BCPs is available in Section 2 of RFC 7841.

本文件是互联网工程任务组（IETF）的产品。互联网工程指导小组（IESG）已批准将其出版。有关BCP的更多信息，请参见RFC 7841第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/rfc8067.

有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc8067.

版权公告

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许可证中所述的无担保。

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  The IESG's Responsibility with Respect to Downrefs  . . . . .   2
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   4.  Normative References  . . . . . . . . . . . . . . . . . . . .   3
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   3

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  The IESG's Responsibility with Respect to Downrefs  . . . . .   2
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   4.  Normative References  . . . . . . . . . . . . . . . . . . . .   3
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   3

1. Introduction

1. 介绍

[RFC3967] notes the importance of assuring that normative references from Standards Track and Best Current Practice (BCP) documents are appropriately mature, and specifies a process for allowing normative references to documents at lower maturity levels ("downrefs"). That process starts at IETF Last Call (see Section 3 of [RFC3967]):

[RFC3967]注意到确保标准跟踪和最佳现行做法（BCP）文件中的规范性引用适当成熟的重要性，并规定了允许规范性引用较低成熟度文件的流程（“DOWNREF”）。该过程从IETF最后一次调用开始（见[RFC3967]第3节）：

For Standards Track or BCP documents requiring normative reference to documents of lower maturity, the normal IETF Last Call procedure will be issued, with the need for the downward reference explicitly documented in the Last Call itself. Any community comments on the appropriateness of downward references will be considered by the IESG as part of its deliberations.

对于需要对较低成熟度文件进行规范性引用的标准跟踪或BCP文件，将发布标准IETF最后调用程序，并在最后调用中明确记录向下引用的需要。IESG将考虑社区对向下参考的适当性的任何意见，作为其审议的一部分。

Section 2 of [RFC3967] lists some conditions under which downrefs may make sense. In addition to those, it has become common for working groups to produce foundational documents (which contain important information such as terminology definitions and architectural design and considerations) at Informational status, and those documents are often needed as normative references in the Standards Track protocol documents that follow.

[RFC3967]第2节列出了DOWNREF可能有意义的一些条件。除此之外，工作组在信息状态下编制基础文件（其中包含术语定义、架构设计和考虑事项等重要信息）已变得很常见，这些文件通常需要作为标准跟踪协议文件中的规范性参考。

The requirement to explicitly mention the downrefs and the need for them in the Last Call message has proven to be unnecessarily restrictive and has often resulted in unnecessary repetitions of Last Call, with the corresponding delay and with no real benefit.

事实证明，在最后一次呼叫消息中明确提及downRef的要求以及对它们的需要具有不必要的限制，并且常常导致不必要的最后一次呼叫重复，并伴随相应的延迟，没有实际的好处。

2. The IESG's Responsibility with Respect to Downrefs

2. IESG对Downrefs的责任

The process in RFC 3967 is hereby updated to specify that explicitly documenting the downward references in the Last Call message is strongly recommended but not required. The responsible AD should still check for downrefs before sending out the Last Call notice, but if an undetected downref is noticed during Last Call or IESG review, any need to repeat the Last Call is at the discretion of the IESG. However, the process in RFC 3967 is not fundamentally altered: If the IESG decides not to repeat the Last Call, the status of the affected downrefs is not changed, and the process in RFC 3967 will still apply if those downrefs are used in the future.

特此更新RFC 3967中的流程，以明确说明强烈建议但不要求明确记录最后一次调用消息中的向下引用。在发出最后一次呼叫通知之前，负责的广告仍应检查downref，但如果在最后一次呼叫或IESG审查期间发现未检测到的downref，则IESG可自行决定是否需要重复最后一次呼叫。但是，RFC 3967中的流程没有根本改变：如果IESG决定不重复上一次调用，则受影响的DownRef的状态不会改变，并且如果将来使用这些DownRef，RFC 3967中的流程仍将适用。

This gives the IESG the responsibility to determine the actual maturity level of the downward reference with respect to the document at hand, and to decide whether or not it is necessary to explicitly ask the IETF community for comments on the downref on a case-by-case basis. In making that decision, the IESG should take into account the general discussion in RFC 3967. The responsible AD should make sure that the omission is recorded as a comment in the datatracker.

这使IESG有责任确定与手头文件相关的向下参考的实际成熟度水平，并决定是否有必要在个案基础上明确要求IETF社区对向下参考提出意见。在作出该决定时，IESG应考虑RFC 3967中的一般性讨论。负责的广告应确保遗漏作为评论记录在datatracker中。

3. Security Considerations

3. 安全考虑

Referencing immature protocols can have security and stability implications, and the IESG should take that into account when deciding whether re-consulting the community is useful.

引用不成熟的协议可能会带来安全和稳定性方面的影响，IESG在决定重新咨询社区是否有用时应该考虑到这一点。

4. Normative References

4. 规范性引用文件

[RFC3967] Bush, R. and T. Narten, "Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level", BCP 97, RFC 3967, DOI 10.17487/RFC3967, December 2004, <http://www.rfc-editor.org/info/rfc3967>.

[RFC3967]Bush，R.和T.Narten，“澄清标准跟踪文件何时可以规范地引用较低级别的文件”，BCP 97，RFC 3967，DOI 10.17487/RFC3967，2004年12月<http://www.rfc-editor.org/info/rfc3967>.

Author's Address

作者地址

Barry Leiba Huawei Technologies

巴里·雷巴华为技术有限公司

   Phone: +1 646 827 0648
   Email: barryleiba@computer.org
   URI:   http://internetmessagingtechnology.org/

   Phone: +1 646 827 0648
   Email: barryleiba@computer.org
   URI:   http://internetmessagingtechnology.org/