Network Working Group J. Vinocur
Request for Comments: 4644 Cornell University
Updates: 2980 K. Murchison
Category: Standards Track Carnegie Mellon University
October 2006
Network Working Group J. Vinocur
Request for Comments: 4644 Cornell University
Updates: 2980 K. Murchison
Category: Standards Track Carnegie Mellon University
October 2006
Network News Transfer Protocol (NNTP) Extension for Streaming Feeds
流媒体源的网络新闻传输协议（NNTP）扩展
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
Abstract
摘要
This memo defines an extension to the Network News Transfer Protocol (NNTP) to provide asynchronous (otherwise known as "streaming") transfer of articles. This allows servers to transfer articles to other servers with much greater efficiency.
此备忘录定义了网络新闻传输协议（NNTP）的扩展，以提供文章的异步（也称为“流”）传输。这允许服务器以更高的效率将文章传输到其他服务器。
This document updates and formalizes the CHECK and TAKETHIS commands specified in RFC 2980 and deprecates the MODE STREAM command.
本文档更新并正式定义RFC 2980中指定的CHECK和TAKETHIS命令，并弃用MODE STREAM命令。
Table of Contents
目录
1. Introduction ....................................................2
1.1. Conventions Used in this Document ..........................2
2. The STREAMING Extension .........................................3
2.1. Streaming Article Transfer .................................3
2.2. Advertising the STREAMING Extension ........................4
2.3. MODE STREAM Command ........................................5
2.3.1. Usage ...............................................5
2.3.2. Description .........................................5
2.3.3. Examples ............................................5
2.4. CHECK Command ..............................................6
2.4.1. Usage ...............................................6
2.4.2. Description .........................................6
2.4.3. Examples ............................................6
2.5. TAKETHIS Command ...........................................7
1. Introduction ....................................................2
1.1. Conventions Used in this Document ..........................2
2. The STREAMING Extension .........................................3
2.1. Streaming Article Transfer .................................3
2.2. Advertising the STREAMING Extension ........................4
2.3. MODE STREAM Command ........................................5
2.3.1. Usage ...............................................5
2.3.2. Description .........................................5
2.3.3. Examples ............................................5
2.4. CHECK Command ..............................................6
2.4.1. Usage ...............................................6
2.4.2. Description .........................................6
2.4.3. Examples ............................................6
2.5. TAKETHIS Command ...........................................7
2.5.1. Usage ...............................................7
2.5.2. Description .........................................7
2.5.3. Examples ............................................8
3. Augmented BNF Syntax for the STREAMING Extension ................9
3.1. Commands ...................................................9
3.2. Command Datastream .........................................9
3.3. Responses .................................................10
3.4. Capability Entries ........................................10
4. Summary of Response Codes ......................................10
5. Security Considerations ........................................11
6. IANA Considerations ............................................11
7. Acknowledgements ...............................................12
8. References .....................................................12
8.1. Normative References ......................................12
8.2. Informative References ....................................12
2.5.1. Usage ...............................................7
2.5.2. Description .........................................7
2.5.3. Examples ............................................8
3. Augmented BNF Syntax for the STREAMING Extension ................9
3.1. Commands ...................................................9
3.2. Command Datastream .........................................9
3.3. Responses .................................................10
3.4. Capability Entries ........................................10
4. Summary of Response Codes ......................................10
5. Security Considerations ........................................11
6. IANA Considerations ............................................11
7. Acknowledgements ...............................................12
8. References .....................................................12
8.1. Normative References ......................................12
8.2. Informative References ....................................12
According to the NNTP specification [NNTP], a peer uses the IHAVE command to query whether a server wants a particular article. Because the IHAVE command cannot be pipelined, the need to stop and wait for the remote end's response greatly restricts the throughput that can be achieved.
根据NNTP规范[NNTP]，对等方使用IHAVE命令查询服务器是否需要特定的文章。由于IHAVE命令无法管道化，因此需要停止并等待远程端的响应极大地限制了可以实现的吞吐量。
The ad-hoc CHECK and TAKETHIS commands, originally documented in [NNTP-COMMON], provide an alternative method of peer-to-peer article transfer that permits a more effective use of network bandwidth. Due to their proven usefulness and wide deployment, they are formalized in this specification.
最初记录在[NNTP-COMMON]中的ad-hoc CHECK和TAKETHIS命令提供了一种对等文章传输的替代方法，允许更有效地使用网络带宽。由于它们被证明是有用的，并且部署范围很广，因此在本规范中对它们进行了形式化描述。
The ad-hoc MODE STREAM command, also documented in [NNTP-COMMON], is deprecated by this specification, but due to its ubiquity is documented here for backwards compatibility.
本规范不推荐使用[NNTP-COMMON]中记录的ad-hoc MODE STREAM命令，但由于其普遍性，此处记录了向后兼容性。
The notational conventions used in this document are the same as those in [NNTP] and any term not defined in this document has the same meaning as in that one.
本文件中使用的符号约定与[NNTP]中的符号约定相同，本文件中未定义的任何术语的含义与[NNTP]中的相同。
The key words "REQUIRED", "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", "MAY", and "OPTIONAL" in this document are to be interpreted as described in "Key words for use in RFCs to Indicate Requirement Levels" [KEYWORDS].
本文件中的关键词“必需”、“必须”、“不得”、“应该”、“不应该”、“可能”和“可选”应按照“RFC中用于指示需求水平的关键词”[关键词]中的描述进行解释。
This document assumes you familiarity with NNTP [NNTP]. In general, the connections described below are from one peer to another, but we will continue to use "client" to mean the initiator of the NNTP connection, and "server" to mean the other endpoint.
本文档假设您熟悉NNTP[NNTP]。通常，下面描述的连接是从一个对等点到另一个对等点的连接，但我们将继续使用“client”表示NNTP连接的发起方，“server”表示另一个端点。
In the examples, commands from the client are indicated with [C], and responses from the server are indicated with [S].
在示例中，来自客户端的命令用[C]表示，来自服务器的响应用[S]表示。
This extension provides three new commands: MODE STREAM, CHECK, and TAKETHIS. The capability label for this extension is STREAMING.
这个扩展提供了三个新命令：modestream、CHECK和TAKETHIS。此扩展的功能标签为流。
The STREAMING extension provides the same functionality as the IHAVE command ([NNTP] section 6.3.2) but splits the query and transfer functionality into the CHECK and TAKETHIS commands respectively. This allows the CHECK and TAKETHIS commands to be pipelined ([NNTP] section 3.5) and provides for "streaming" article transfer.
流媒体扩展提供与IHAVE命令相同的功能（[NNTP]第6.3.2节），但将查询和传输功能分别拆分为CHECK和TAKETHIS命令。这允许CHECK和TAKETHIS命令以流水线方式进行（[NNTP]第3.5节），并提供“流式”文章传输。
A streaming client will often pipeline many CHECK commands and use the responses to construct a list of articles to be sent by a pipelined sequence of TAKETHIS commands, thus increasing the fraction of time spent transferring articles. The CHECK and TAKETHIS commands utilize distinct response codes so that these commands can be intermingled in a pipeline and the response to any single command can be definitively identified by the client.
流式客户端通常会通过管道传输许多CHECK命令，并使用响应来构造一个项目列表，这些项目将通过管道化的TAKETHIS命令序列发送，从而增加传输项目所花费的时间。CHECK和TAKETHIS命令使用不同的响应代码，因此这些命令可以在管道中混合使用，对任何单个命令的响应都可以由客户端确定。
The client MAY send articles via TAKETHIS without first querying the server with CHECK. The client SHOULD NOT send every article in this fashion unless explicitly configured to do so by the site administrator based on out-of-band information. However, the client MAY use an adaptive strategy where it initially sends CHECK commands for all articles, but switches to using TAKETHIS without CHECK if most articles are being accepted (over 95% acceptance might be a reasonable metric in some configurations). If the client uses such a strategy, it SHOULD also switch back to using CHECK on all articles if the acceptance rate ever falls much below the threshold.
客户端可以通过TAKETHIS发送文章，而无需首先使用CHECK查询服务器。客户端不应该以这种方式发送每一篇文章，除非站点管理员根据带外信息明确配置为这样做。但是，客户机可以使用自适应策略，在该策略中，它最初为所有项目发送检查命令，但如果大多数项目都被接受，则会切换到使用TAKETHIS而不进行检查（在某些配置中，接受率超过95%可能是一个合理的指标）。如果客户使用这样的策略，那么如果接受率远远低于阈值，它也应该切换回对所有文章使用检查。
A server supporting the streaming commands described in this document will advertise the "STREAMING" capability label in response to the CAPABILITIES command ([NNTP] section 5.2). The server MUST continue to advertise this capability after a client has issued the MODE STREAM command. This capability MAY be advertised both before and after any use of the MODE READER command ([NNTP] section 5.3), with the same semantics.
支持本文件中所述流式命令的服务器将公布“流式”能力标签，以响应能力命令（[NNTP]第5.2节）。在客户端发出MODE STREAM命令后，服务器必须继续公布此功能。在使用模式读取器命令之前和之后（[NNTP]第5.3节），可以使用相同的语义公布此功能。
Example of a client using CAPABILITIES and MODE STREAM on a mode-switching server:
在模式切换服务器上使用功能和模式流的客户端示例：
[C] CAPABILITIES
[S] 101 Capability list:
[S] VERSION 2
[S] MODE-READER
[S] IHAVE
[S] LIST ACTIVE
[S] STREAMING
[S] .
[C] MODE STREAM
[S] 203 Streaming permitted
[C] CAPABILITIES
[S] 101 Capability list:
[S] VERSION 2
[S] MODE-READER
[S] IHAVE
[S] LIST ACTIVE
[S] STREAMING
[S] .
[C] MODE READER
[S] 200 Posting allowed
[C] CAPABILITIES
[S] 101 Capability list:
[S] VERSION 2
[S] READER
[S] POST
[S] LIST ACTIVE NEWSGROUPS HEADERS
[S] HDR
[S] .
[C] CAPABILITIES
[S] 101 Capability list:
[S] VERSION 2
[S] MODE-READER
[S] IHAVE
[S] LIST ACTIVE
[S] STREAMING
[S] .
[C] MODE STREAM
[S] 203 Streaming permitted
[C] CAPABILITIES
[S] 101 Capability list:
[S] VERSION 2
[S] MODE-READER
[S] IHAVE
[S] LIST ACTIVE
[S] STREAMING
[S] .
[C] MODE READER
[S] 200 Posting allowed
[C] CAPABILITIES
[S] 101 Capability list:
[S] VERSION 2
[S] READER
[S] POST
[S] LIST ACTIVE NEWSGROUPS HEADERS
[S] HDR
[S] .
Historically this command was used by a client to discover if a server supported the CHECK and TAKETHIS commands. This command is deprecated in favor of the CAPABILITIES discovery command and is only provided here for compatibility with legacy implementations [NNTP-COMMON] of these transport commands.
历史上，客户机使用此命令来发现服务器是否支持CHECK和TAKETHIS命令。此命令已弃用，取而代之的是CAPABILITIES discovery命令，此处仅提供此命令是为了与这些传输命令的旧式实现[NNTP-COMMON]兼容。
New clients SHOULD use the CAPABILITIES command to check a server for support of the STREAMING extension but MAY use the MODE STREAM command for backwards compatibility with legacy servers that don't support the CAPABILITIES discovery command. Servers MUST accept the MODE STREAM command for backwards compatibility with legacy clients that don't use the CAPABILITIES discovery command.
新客户端应使用CAPABILITIES命令检查服务器是否支持流扩展，但也可以使用MODE STREAM命令与不支持CAPABILITIES discovery命令的旧服务器向后兼容。服务器必须接受MODE STREAM命令，以便与不使用CAPABILITIES discovery命令的旧客户端向后兼容。
NOTE: This command may be removed from a future version of this specification, therefore clients are urged to transition to the CAPABILITIES command wherever possible.
注意：此命令可能会从本规范的未来版本中删除，因此敦促客户机尽可能转换到“能力”命令。
Syntax MODE STREAM
语法模式流
Responses 203 Streaming permitted
允许答复203流媒体
If a server supports this extension, it MUST return a 203 response to the MODE STREAM command (or 501 if an argument is given). The MODE STREAM command MUST NOT affect the server state in any way (that is, it is not a mode change despite the name), therefore this command MAY be pipelined. A server MUST NOT require that the MODE STREAM command be issued by the client before accepting the CHECK or TAKETHIS commands.
如果服务器支持此扩展，则必须返回203对MODE STREAM命令的响应（如果给定参数，则返回501）。MODE STREAM命令不得以任何方式影响服务器状态（即，不管名称如何，它都不是模式更改），因此此命令可以管道化。在接受CHECK或TAKETHIS命令之前，服务器不得要求客户机发出MODE STREAM命令。
Example of a client checking the ability to stream articles on a server which does not support this extension:
客户端检查在不支持此扩展的服务器上对项目进行流式处理的能力的示例：
[C] MODE STREAM [S] 501 Unknown MODE variant
[C] 模式流501未知模式变量
Example of a client checking the ability to stream articles on a server which supports this extension:
客户端检查在支持此扩展的服务器上对文章进行流式处理的能力的示例：
[C] MODE STREAM [S] 203 Streaming permitted
[C] 模式流[S]203允许流式传输
Syntax CHECK message-id
语法检查消息id
Responses 238 message-id Send article to be transferred 431 message-id Transfer not possible; try again later 438 message-id Article not wanted
响应238消息id发送要传输的文章431消息id传输不可能；请稍后重试438邮件id文章不需要
Parameters message-id = Article message-id
参数消息id=文章消息id
The first parameter of the 238, 431, and 438 responses MUST be the message-id provided by the client as the parameter to CHECK.
238、431和438响应的第一个参数必须是客户端提供的消息id，作为要检查的参数。
The CHECK command informs the server that the client has an article with the specified message-id. If the server desires a copy of that article, a 238 response MUST be returned, indicating that the client may send the article using the TAKETHIS command. If the server does not want the article (if, for example, the server already has a copy of it), a 438 response MUST be returned, indicating that the article is not wanted. Finally, if the article isn't wanted immediately but the client should retry later if possible (if, for example, another client has offered to send the same article to the server), a 431 response MUST be returned.
CHECK命令通知服务器客户端有一个具有指定message-id的项目。如果服务器需要该项目的副本，则必须返回238响应，指示客户端可以使用TAKETHIS命令发送该项目。如果服务器不需要该文章（例如，如果服务器已经有该文章的副本），则必须返回438响应，指示不需要该文章。最后，如果不立即需要该文章，但如果可能，客户机应该稍后重试（例如，如果另一个客户机提供将同一文章发送到服务器），则必须返回431响应。
NOTE: The responses to CHECK are advisory; the server MUST NOT rely on the client to behave as requested by these responses.
注：对检查的响应是建议性的；服务器不能依赖客户端按照这些响应的请求进行操作。
Example of a client checking whether the server would like a set of articles and getting a mixture of responses:
客户端检查服务器是否需要一组文章并获得混合响应的示例：
[C] CHECK <i.am.an.article.you.will.want@example.com>
[S] 238 <i.am.an.article.you.will.want@example.com>
[C] CHECK <i.am.an.article.you.have@example.com>
[S] 438 <i.am.an.article.you.have@example.com>
[C] CHECK <i.am.an.article.you.defer@example.com>
[S] 431 <i.am.an.article.you.defer@example.com>
[C] CHECK <i.am.an.article.you.will.want@example.com>
[S] 238 <i.am.an.article.you.will.want@example.com>
[C] CHECK <i.am.an.article.you.have@example.com>
[S] 438 <i.am.an.article.you.have@example.com>
[C] CHECK <i.am.an.article.you.defer@example.com>
[S] 431 <i.am.an.article.you.defer@example.com>
Example of pipelining the CHECK commands in the previous example:
上一示例中的CHECK命令管道化示例：
[C] CHECK <i.am.an.article.you.will.want@example.com>
[C] CHECK <i.am.an.article.you.have@example.com>
[C] CHECK <i.am.an.article.you.defer@example.com>
[S] 238 <i.am.an.article.you.will.want@example.com>
[S] 438 <i.am.an.article.you.have@example.com>
[S] 431 <i.am.an.article.you.defer@example.com>
[C] CHECK <i.am.an.article.you.will.want@example.com>
[C] CHECK <i.am.an.article.you.have@example.com>
[C] CHECK <i.am.an.article.you.defer@example.com>
[S] 238 <i.am.an.article.you.will.want@example.com>
[S] 438 <i.am.an.article.you.have@example.com>
[S] 431 <i.am.an.article.you.defer@example.com>
A client MUST NOT use this command unless the server advertises the STREAMING capability or returns a 203 response to the MODE STREAM command.
客户端不得使用此命令，除非服务器播发流功能或返回对MODE STREAM命令的203响应。
Syntax TAKETHIS message-id
此消息id的语法
Responses 239 message-id Article transferred OK 439 message-id Transfer rejected; do not retry
响应239消息id文章传输OK 439消息id传输被拒绝；不要重试
Parameters message-id = Article message-id
参数消息id=文章消息id
The first parameter of the 239 and 439 responses MUST be the message-id provided by the client as the parameter to TAKETHIS.
239和439响应的第一个参数必须是客户端提供的消息id，作为执行此操作的参数。
The TAKETHIS command is used to send an article with the specified message-id to the server. The article is sent immediately following the CRLF at the end of the TAKETHIS command line. The client MUST send the entire article, including headers and body, to the server as a multi-line data block ([NNTP] section 3.1.1). Thus, a single dot (".") on a line indicates the end of the text, and lines starting with a dot in the original text have that dot doubled during transmission. The server MUST return either a 239 response, indicating that the article was successfully transferred, or a 439 response, indicating that the article was rejected. If the server encounters a temporary error that prevents it from processing the article but does not want to reject the article, it MUST reply with a 400 response to the client and close the connection.
TAKETHIS命令用于将具有指定消息id的文章发送到服务器。文章将在TAKETHIS命令行末尾的CRLF之后立即发送。客户端必须将整篇文章（包括标题和正文）作为多行数据块发送到服务器（[NNTP]第3.1.1节）。因此，一行上的一个单点（“.”）表示文本的结尾，而以原始文本中的一个点开头的行在传输过程中使该点加倍。服务器必须返回239响应（表示文章已成功传输）或439响应（表示文章已被拒绝）。如果服务器遇到临时错误，无法处理该文章，但不想拒绝该文章，则必须向客户端回复400响应并关闭连接。
This function differs from the POST command in that it is intended for use in transferring already-posted articles between hosts. It
此函数与POST命令的不同之处在于，它用于在主机之间传输已发布的文章。信息技术
SHOULD NOT be used when the client is a personal news-reading program, since use of this command indicates that the article has already been posted at another site and is simply being forwarded from another host. However, despite this, the server MAY elect not to post or forward the article if, after further examination of the article, it deems it inappropriate to do so. Reasons for such subsequent rejection of an article may include problems such as inappropriate newsgroups or distributions, disk space limitations, article lengths, garbled headers, and the like. These are typically restrictions enforced by the server host's news software and not necessarily by the NNTP server itself.
当客户端是个人新闻阅读程序时，不应使用此命令，因为使用此命令表示文章已在另一个站点发布，并且只是从另一个主机转发。然而，尽管如此，如果在对文章进行进一步检查后，服务器认为不适合发布或转发文章，服务器可能会选择不发布或转发文章。此类后续拒绝文章的原因可能包括诸如不适当的新闻组或发行版、磁盘空间限制、文章长度、乱码标题等问题。这些限制通常由服务器主机的新闻软件强制执行，而不一定由NNTP服务器本身强制执行。
The client SHOULD NOT assume that the article has been successfully transferred unless it receives an affirmative response from the server. A lack of response (such as a dropped network connection or a network timeout) or a 400 response SHOULD be treated as a temporary failure and cause the transfer to be tried again later if possible.
除非已成功地从服务器接收到肯定的响应，否则假定该文章未被成功传输。缺少响应（如断开的网络连接或网络超时）或400响应应视为临时故障，并在可能的情况下导致稍后再次尝试传输。
Because some news server software may not immediately be able to determine whether an article is suitable for posting or forwarding, an NNTP server MAY acknowledge the successful transfer of the article (with a 239 response) but later silently discard it.
由于某些新闻服务器软件可能无法立即确定文章是否适合发布或转发，NNTP服务器可能会确认文章的成功传输（带有239响应），但稍后会自动放弃。
Example of streaming two articles to another site (the first article is accepted and the second is rejected):
将两篇文章流式传输到另一个站点的示例（第一篇文章被接受，第二篇文章被拒绝）：
[C] TAKETHIS <i.am.an.article.you.will.want@example.com>
[C] Path: pathost!demo!somewhere!not-for-mail
[C] From: "Demo User" <nobody@example.com>
[C] Newsgroups: misc.test
[C] Subject: I am just a test article
[C] Date: 6 Oct 1998 04:38:40 -0500
[C] Organization: An Example Com, San Jose, CA
[C] Message-ID: <i.am.an.article.you.will.want@example.com>
[C]
[C] This is just a test article.
[C] .
[C] TAKETHIS <i.am.an.article.you.have@example.com>
[C] Path: pathost!demo!somewhere!not-for-mail
[C] From: "Demo User" <nobody@example.com>
[C] Newsgroups: misc.test
[C] Subject: I am just a test article
[C] Date: 6 Oct 1998 04:38:40 -0500
[C] Organization: An Example Com, San Jose, CA
[C] Message-ID: <i.am.an.article.you.have@example.com>
[C]
[C] TAKETHIS <i.am.an.article.you.will.want@example.com>
[C] Path: pathost!demo!somewhere!not-for-mail
[C] From: "Demo User" <nobody@example.com>
[C] Newsgroups: misc.test
[C] Subject: I am just a test article
[C] Date: 6 Oct 1998 04:38:40 -0500
[C] Organization: An Example Com, San Jose, CA
[C] Message-ID: <i.am.an.article.you.will.want@example.com>
[C]
[C] This is just a test article.
[C] .
[C] TAKETHIS <i.am.an.article.you.have@example.com>
[C] Path: pathost!demo!somewhere!not-for-mail
[C] From: "Demo User" <nobody@example.com>
[C] Newsgroups: misc.test
[C] Subject: I am just a test article
[C] Date: 6 Oct 1998 04:38:40 -0500
[C] Organization: An Example Com, San Jose, CA
[C] Message-ID: <i.am.an.article.you.have@example.com>
[C]
[C] This is just a test article.
[C] .
[S] 239 <i.am.an.article.you.will.want@example.com>
[S] 439 <i.am.an.article.you.have@example.com>
[C] This is just a test article.
[C] .
[S] 239 <i.am.an.article.you.will.want@example.com>
[S] 439 <i.am.an.article.you.have@example.com>
Example of sending an article to a site where the transfer fails:
向传输失败的站点发送文章的示例：
[C] TAKETHIS <i.am.an.article.you.will.want@example.com>
[C] Path: pathost!demo!somewhere!not-for-mail
[C] From: "Demo User" <nobody@example.com>
[C] Newsgroups: misc.test
[C] Subject: I am just a test article
[C] Date: 6 Oct 1998 04:38:40 -0500
[C] Organization: An Example Com, San Jose, CA
[C] Message-ID: <i.am.an.article.you.will.want@example.com>
[C]
[C] This is just a test article.
[C] .
[S] 400 Service temporarily unavailable
[Server closes connection.]
[C] TAKETHIS <i.am.an.article.you.will.want@example.com>
[C] Path: pathost!demo!somewhere!not-for-mail
[C] From: "Demo User" <nobody@example.com>
[C] Newsgroups: misc.test
[C] Subject: I am just a test article
[C] Date: 6 Oct 1998 04:38:40 -0500
[C] Organization: An Example Com, San Jose, CA
[C] Message-ID: <i.am.an.article.you.will.want@example.com>
[C]
[C] This is just a test article.
[C] .
[S] 400 Service temporarily unavailable
[Server closes connection.]
This section describes the formal syntax of the STREAMING extension using ABNF [ABNF]. It extends the syntax in section 9 of [NNTP], and non-terminals not defined in this document are defined there. The [NNTP] ABNF should be imported first before attempting to validate these rules.
本节介绍使用ABNF[ABNF]的流扩展的正式语法。它扩展了[NNTP]第9节中的语法，本文件中未定义的非终端在此处定义。在尝试验证这些规则之前，应首先导入[NNTP]ABNF。
This syntax extends the non-terminal "command", which represents an NNTP command.
此语法扩展了表示NNTP命令的非终端“命令”。
command =/ check-command / mode-stream-command / takethis-command
command=/check command/mode stream command/takethis命令
check-command = "CHECK" WS message-id mode-stream-command = "MODE" WS "STREAM" takethis-command = "TAKETHIS" WS message-id
check command=“check”WS message id mode stream command=“mode”WS“stream”takethis command=“takethis”WS message id
This syntax extends the non-terminal "command-datastream", which represents the further material sent by the client in the case of streaming commands.
此语法扩展了非终端的“命令数据流”，它表示在流式命令的情况下客户端发送的进一步资料。
command-datastream =/ takethis-datastream
命令datastream=/takethis datastream
takethis-datastream = encoded-article
takethis-datastream = encoded-article
This syntax extends the non-terminal "initial-response-content", which represents an initial response line sent by the server.
此语法扩展了非终端“初始响应内容”，它表示服务器发送的初始响应行。
initial-response-content =/ response-238-content / response-239-content / response-431-content / response-438-content / response-439-content
初始响应内容=/response-238-content/response-239-content/response-431-content/response-438-content/response-439-content
response-238-content = "238" SP message-id response-239-content = "239" SP message-id response-431-content = "431" SP message-id response-438-content = "438" SP message-id response-439-content = "439" SP message-id
response-238-content=“238”SP message id response-239-content=“239”SP message id response-431-content=“431”SP message id response-438-content=“438”SP message id response-439-content=“439”SP message id
This syntax extends the non-terminal "capability-entry", which represents a capability that may be advertised by the server.
此语法扩展了非终端“能力条目”，它表示可能由服务器公布的能力。
capability-entry =/ streaming-capability
功能条目=/流媒体功能
streaming-capability = "STREAMING"
streaming-capability = "STREAMING"
This section contains a list of each new response code defined in this document and indicates whether it is multi-line, which commands can generate it, what arguments it has, and what its meaning is.
本节包含本文档中定义的每个新响应代码的列表，并指出它是否为多行代码、哪些命令可以生成它、它有哪些参数以及它的含义。
Response code 203 Generated by: MODE STREAM Meaning: streaming permitted.
响应代码203由：模式流生成，意思是：允许流。
Response code 238 Generated by: CHECK 1 argument: message-id Meaning: send article to be transferred.
响应代码238由以下参数生成：CHECK 1参数：message id含义：发送要传输的文章。
Response code 239 Generated by: TAKETHIS 1 argument: message-id Meaning: article transferred OK.
响应代码239生成者：TAKETHIS 1参数：message id含义：article transfered OK。
Response code 431 Generated by: CHECK 1 argument: message-id Meaning: transfer not possible; try again later.
响应代码431生成者：CHECK 1参数：message id含义：无法传输；请稍后再试。
Response code 438 Generated by: CHECK 1 argument: message-id Meaning: article not wanted.
响应代码438由：CHECK 1参数：message id含义：不需要物品生成。
Response code 439 Generated by: TAKETHIS 1 argument: message-id Meaning: transfer rejected; do not retry.
响应代码439生成者：takethis1参数：消息id含义：传输被拒绝；不要重试。
No new security considerations are introduced by this extension, beyond those already described in the core specification [NNTP].
除了核心规范[NNTP]中已经描述的安全注意事项外，此扩展没有引入新的安全注意事项。
This section gives a formal definition of the STREAMING extension as required by Section 3.3.3 of [NNTP] for the IANA registry.
本节给出了IANA注册表[NNTP]第3.3.3节要求的流媒体扩展的正式定义。
o The STREAMING extension provides for streaming transfer of articles.
o 流媒体扩展提供了文章的流媒体传输。
o The capability label for this extension is "STREAMING".
o 此扩展的功能标签为“流”。
o The capability label has no arguments.
o 功能标签没有参数。
o The extension defines three new commands, MODE STREAM, CHECK, and TAKETHIS, whose behavior, arguments, and responses are defined in Sections 2.3, 2.4, and 2.5 respectively.
o 扩展定义了三个新命令，MODE STREAM、CHECK和TAKETHIS，其行为、参数和响应分别在第2.3、2.4和2.5节中定义。
o The extension does not associate any new responses with pre-existing NNTP commands.
o 扩展不会将任何新响应与预先存在的NNTP命令相关联。
o The extension does not affect the behavior of a server or client other than via the new commands.
o 除了通过新命令外，扩展不会影响服务器或客户端的行为。
o The extension does not affect the maximum length of commands or initial response lines.
o 扩展不影响命令或初始响应行的最大长度。
o The extension does not alter pipelining, and the MODE STREAM, CHECK, and TAKETHIS commands can be pipelined.
o 扩展不改变管道，模式流、CHECK和TAKETHIS命令可以管道化。
o Use of this extension does not alter the capabilities list.
o 使用此扩展不会更改功能列表。
o The extension does not cause any pre-existing command to produce a 401, 480, or 483 response.
o 扩展不会导致任何预先存在的命令生成401、480或483响应。
o Use of the MODE READER command on a mode-switching server may disable this extension.
o 在模式切换服务器上使用模式读取器命令可能会禁用此扩展。
o Published Specification: This document.
o 已发布规范：本文件。
o Contact for Further Information: Authors of this document.
o 更多信息请联系：本文件作者。
o Change Controller: IESG <iesg@ietf.org>.
o 更改控制器：IESG<iesg@ietf.org>.
This document is based heavily on the relevant sections of RFC 2980 [NNTP-COMMON], by Stan Barber.
本文件主要基于Stan Barber的RFC 2980[NNTP-COMMON]的相关章节。
Special acknowledgement also goes to Russ Allbery, Clive Feather, Andrew Gierth, and others who commented privately on intermediate revisions of this document, as well as the members of the IETF NNTP Working Group for continual (yet sporadic) insight in discussion.
特别感谢Russ Allbery、Clive Feather、Andrew Gierth和其他私下评论本文件中间版本的人，以及IETF NNTP工作组成员在讨论中不断（但零星）的见解。
[ABNF] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 4234, October 2005.
[ABNF]Crocker，D.，Ed.和P.Overell，“语法规范的扩充BNF:ABNF”，RFC 42342005年10月。
[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[关键词]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[NNTP] Feather, C., "Network News Transfer Protocol (NNTP)", RFC 3977, October 2006.
[NNTP]Feather，C.，“网络新闻传输协议（NNTP）”，RFC 3977，2006年10月。
[NNTP-COMMON] Barber, S., "Common NNTP Extensions", RFC 2980, October 2000.
[NNTP-COMMON]Barber，S.，“通用NNTP扩展”，RFC 29802000年10月。
Authors' Addresses
作者地址
Jeffrey M. Vinocur Department of Computer Science Upson Hall Cornell University Ithaca, NY 14853
Jeffrey M.Vinocur纽约州伊萨卡康奈尔大学厄普森霍尔分校计算机科学系，邮编14853
EMail: vinocur@cs.cornell.edu
EMail: vinocur@cs.cornell.edu
Kenneth Murchison Carnegie Mellon University 5000 Forbes Avenue Cyert Hall 285 Pittsburgh, PA 15213 USA
肯尼斯·默奇森卡内基梅隆大学福布斯大道5000号塞尔特大厅美国宾夕法尼亚州匹兹堡285号15213
EMail: murch@andrew.cmu.edu
EMail: murch@andrew.cmu.edu
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
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 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.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
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.
Acknowledgement
确认
Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).
RFC编辑器功能的资金由IETF行政支持活动（IASA）提供。