Network Working Group P. Grau
Request for Comments: 4707 V. Heinau
Category: Experimental H. Schlichting
R. Schuettler
Freie Universitaet Berlin
October 2006
Network Working Group P. Grau
Request for Comments: 4707 V. Heinau
Category: Experimental H. Schlichting
R. Schuettler
Freie Universitaet Berlin
October 2006
Netnews Administration System (NAS)
网络新闻管理系统（NAS）
Status of This Memo
关于下段备忘
This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited.
这份备忘录为互联网社区定义了一个实验性协议。它没有规定任何类型的互联网标准。要求进行讨论并提出改进建议。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
IESG Note
IESG注释
This RFC is not a candidate for any level of Internet Standard. The IETF disclaims any knowledge of the fitness of this RFC for any purpose, and in particular notes that the decision to publish is not based on IETF review for such things as security, congestion control or inappropriate interaction with deployed protocols. The RFC Editor has chosen to publish this document at its discretion. Readers of this document should exercise caution in evaluating its value for implementation and deployment.
本RFC不适用于任何级别的互联网标准。IETF不承认本RFC适用于任何目的的任何知识，特别注意到，发布决定并非基于IETF对安全、拥塞控制或与已部署协议的不当交互等事项的审查。RFC编辑已自行决定发布本文件。本文档的读者在评估其实施和部署价值时应谨慎。
Abstract
摘要
The Netnews Administration System (NAS) is a framework to simplify the administration and usage of network news (also known as Netnews) on the Internet. Data for the administration of newsgroups and hierarchies are kept in a distributed hierarchical database and are available through a client-server protocol.
网络新闻管理系统（NAS）是一个简化互联网上网络新闻（也称为网络新闻）管理和使用的框架。用于管理新闻组和层次结构的数据保存在分布式层次结构数据库中，并通过客户机-服务器协议提供。
The database is accessible by news servers, news administrators, and news readers. News servers can update their configuration automatically; administrators are able to get the data manually. News reader programs are able to get certain information from an NAS server, automatically or at a user's discretion, which provides detailed information about groups and hierarchies to the user.
新闻服务器、新闻管理员和新闻阅读器可以访问该数据库。新闻服务器可以自动更新其配置；管理员可以手动获取数据。新闻阅读器程序能够自动或由用户自行决定从NAS服务器获取某些信息，从而向用户提供有关组和层次结构的详细信息。
NAS is usable in coexistence with the current, established process of control messages; an unwanted interference is impossible. Furthermore, NAS is able to reflect the somewhat chaotic structure of Usenet in a hierarchical database. NAS can be used without modification of existing news relay, news server, or news reader software; however, some tasks will be better accomplished with NAS-compliant software.
NAS可与当前已建立的控制消息过程共存使用；不必要的干扰是不可能的。此外，NAS能够在分层数据库中反映出Usenet有些混乱的结构。NAS可以在不修改现有新闻中继、新闻服务器或新闻阅读器软件的情况下使用；但是，使用NAS兼容软件可以更好地完成某些任务。
Table of Contents
目录
1. Introduction ....................................................3
2. Overview ........................................................4
3. Protocol Level ..................................................5
4. Description of Functions ........................................6
5. Definitions .....................................................7
6. Specification of the NAS Protocol (TCP) .........................8
6.1. Responses ..................................................8
6.1.1. Overview ............................................8
6.1.2. Response Code Values, Structure, and Meaning ........8
6.2. Connection Setup ...........................................9
6.3. Commands ..................................................10
6.3.1. Structure ..........................................10
6.3.2. Overview ...........................................10
6.3.3. Detailed Description ...............................10
6.3.3.1. HELP ......................................11
6.3.3.2. INFO ......................................12
6.3.3.3. DATE ......................................13
6.3.3.4. VERS ......................................14
6.3.3.5. QUIT ......................................15
6.3.3.6. LIST ......................................16
6.3.3.7. LSTR ......................................18
6.3.3.8. HIER ......................................19
6.3.3.9. DATA ......................................21
6.3.3.10. GETP .....................................22
6.3.3.11. GETA .....................................25
6.3.3.12. Unknown Commands and Syntax Errors .......27
6.3.4. Data Headers .......................................27
6.4. Status Indicators .........................................41
6.5. Newsgroup Types ...........................................41
6.6. Hierarchy Types ...........................................42
6.7. PGP Keys ..................................................42
7. Specification of the NAS Protocol (UDP) ........................44
8. IANA Considerations ............................................44
9. Security Considerations ........................................44
10. Response Codes (Overview) .....................................45
11. Data Headers for DATA and HIER Commands (Overview) ............45
1. Introduction ....................................................3
2. Overview ........................................................4
3. Protocol Level ..................................................5
4. Description of Functions ........................................6
5. Definitions .....................................................7
6. Specification of the NAS Protocol (TCP) .........................8
6.1. Responses ..................................................8
6.1.1. Overview ............................................8
6.1.2. Response Code Values, Structure, and Meaning ........8
6.2. Connection Setup ...........................................9
6.3. Commands ..................................................10
6.3.1. Structure ..........................................10
6.3.2. Overview ...........................................10
6.3.3. Detailed Description ...............................10
6.3.3.1. HELP ......................................11
6.3.3.2. INFO ......................................12
6.3.3.3. DATE ......................................13
6.3.3.4. VERS ......................................14
6.3.3.5. QUIT ......................................15
6.3.3.6. LIST ......................................16
6.3.3.7. LSTR ......................................18
6.3.3.8. HIER ......................................19
6.3.3.9. DATA ......................................21
6.3.3.10. GETP .....................................22
6.3.3.11. GETA .....................................25
6.3.3.12. Unknown Commands and Syntax Errors .......27
6.3.4. Data Headers .......................................27
6.4. Status Indicators .........................................41
6.5. Newsgroup Types ...........................................41
6.6. Hierarchy Types ...........................................42
6.7. PGP Keys ..................................................42
7. Specification of the NAS Protocol (UDP) ........................44
8. IANA Considerations ............................................44
9. Security Considerations ........................................44
10. Response Codes (Overview) .....................................45
11. Data Headers for DATA and HIER Commands (Overview) ............45
12. References ....................................................46
12.1. Normative References .....................................46
12.2. Informative References ...................................47
12. References ....................................................46
12.1. Normative References .....................................46
12.2. Informative References ...................................47
An increasing number of newsgroups, hierarchies, and articles has made the administration of news servers a complex and time-consuming task. The tools for the administration have remained unchanged for ten years and are no longer appropriate. Many hierarchies are inconsistent; many new newsgroups are not created or only with a large delay; removed groups keep lurking in the configuration files for a long period of time. There is no administration tool that utilizes the power of the Internet, and it is not possible to check the consistency of the news server at a given point of time.
越来越多的新闻组、层次结构和文章使得管理新闻服务器成为一项复杂而耗时的任务。10年来，政府的工具一直没有改变，不再合适。许多层级不一致；许多新的新闻组没有创建，或者只是延迟了很长时间；删除的组在配置文件中潜伏了很长一段时间。没有利用互联网功能的管理工具，也不可能在给定时间点检查新闻服务器的一致性。
Users find it difficult to get an overview of the newsgroups, the charter of a particular one, which language is preferred, or whether a group is moderated. Renaming, the status change from moderated to unmoderated or vice versa, and the splitting of a group into several others are dynamic processes. These processes are in common use, but it takes a long time until every news server is aware of these changes.
用户发现很难了解新闻组的概况、特定新闻组的章程、首选哪种语言，或者某个新闻组是否有主持人。重命名、状态从“已调节”更改为“未调节”，或反之亦然，以及将一个组拆分为多个其他组都是动态过程。这些过程是常用的，但需要很长时间才能让每个新闻服务器都知道这些更改。
An increasing number of faked control messages has appeared in the last few years. Purposely or accidentally, control messages were sent to foreign news servers to create or remove a certain group, although this was not approved according to the rules of the hierarchy in question. Due to this fact, automatic creation and removal are disabled on many news servers, and several dead groups have not been deleted. It is very difficult for users to determine the current status of a group, and in some cases they simply cannot tell that the group they are posting to is not an active group but a dead or invalid one.
在过去几年中，出现了越来越多的伪造控制消息。控制消息被有意或无意地发送到外国新闻服务器，以创建或删除某个组，尽管根据相关层次结构的规则，这未得到批准。由于这一事实，许多新闻服务器上都禁用了自动创建和删除功能，并且还没有删除几个死组。用户很难确定组的当前状态，在某些情况下，他们根本无法判断他们发布的组不是活动组，而是死亡或无效组。
It is the design goal of Netnews Administration System (NAS) to provide an out-of-band system that helps to maintain, propagate, and deliver the required information. There will not be any interference with current protocols and standards. It is not intended to make use of control messages or some special Network News Transfer Protocol (NNTP) commands. The advantage of NAS is that it provides more information in a more structured format than that of control messages. Not only news server administrators but also Usenet users can get more detailed information about newsgroups and hierarchies.
Netnews管理系统（NAS）的设计目标是提供带外系统，帮助维护、传播和交付所需信息。不会对当前协议和标准产生任何干扰。它不打算使用控制消息或某些特殊的网络新闻传输协议（NNTP）命令。NAS的优势在于，它以比控制消息更结构化的格式提供更多的信息。不仅新闻服务器管理员，而且Usenet用户都可以获得有关新闻组和层次结构的更详细信息。
Due to the fact that a client connects to a server and the server asks for authentication, this is a more reasonable procedure for transmitting information than that for control messages.
由于客户机连接到服务器，而服务器要求进行身份验证，因此与控制消息相比，这是一种更合理的信息传输过程。
Furthermore, it is possible to check for changes on a regular basis at customized intervals to keep local data up-to-date.
此外，还可以按定制的时间间隔定期检查更改，以保持本地数据的最新状态。
NAS is based on a database that contains information about certain groups and hierarchies. This database is structured in a hierarchical manner and distributed to various servers, and it is able to receive queries at any time. The service is comparable to directory services like DNS, Lightweight Directory Access Protocol (LDAP), or Network Information Service (NIS). The NAS protocol is inspired by protocols like NNTP and SMTP. The port 991 is reserved for NAS and registered by the Internet Assigned Numbers Authority (IANA) [IANA-PN].
NAS基于包含特定组和层次结构信息的数据库。该数据库以分层方式构建，并分布到各个服务器，它能够随时接收查询。该服务与DNS、轻量级目录访问协议（LDAP）或网络信息服务（NIS）等目录服务相当。NAS协议受NNTP和SMTP等协议的启发。端口991为NAS保留，并由互联网分配号码管理局（IANA）[IANA-PN]注册。
The organizational structure of NAS is hierarchical; this means that a NAS root server collects data from the sub-servers that are authoritative for certain hierarchies. The root server signs the data and distributes it authoritatively. Replication of database entries is possible. The hierarchical structure can consist of multiple levels. Usage of the database is possible for news servers, news readers, and special client programs. The communication is based on TCP and UDP.
NAS的组织结构是分层的；这意味着NAS根服务器从对某些层次结构具有权威性的子服务器收集数据。根服务器对数据进行签名并以授权方式分发数据。可以复制数据库条目。层次结构可以由多个层次组成。数据库可以用于新闻服务器、新闻阅读器和特殊的客户端程序。通信是基于TCP和UDP的。
Taking the real world into account, there might be some policy problems with a single root server. But it is possible to establish a structure like that of the current Usenet system, where some hierarchies have a good administration with a well-defined system of rules, and where some are not well maintained. The goal is to get as much information as possible under one hat, but there can be no "official" force to achieve this.
考虑到现实世界，单个根服务器可能存在一些策略问题。但是可以建立一个类似于当前Usenet系统的结构，其中一些层次结构具有良好的管理和定义良好的规则系统，而有些层次结构没有得到很好的维护。目标是在一顶帽子下获得尽可能多的信息，但不可能有“官方”力量来实现这一目标。
During the startup phase, it is quite likely that there will be a root server, handling just hierarchies with strict rules and accepted authorities (e.g., BIG8, de.*, us.*, bln.*, fr.*, it.*).
在启动阶段，很可能会有一个根服务器，只处理具有严格规则和公认权限的层次结构（例如BIG8、de.*、us.*、bln.*、fr.*、it.*）。
However, it is also imaginable to have some NAS servers providing data on, for example, alt.!binaries, some providing data on alt.*, and even some providing alt.* following special policies or sets of rules.
但是，也可以想象一些NAS服务器提供数据，例如alt。！二进制文件，有些提供alt.*上的数据，甚至有些提供遵循特殊策略或规则集的alt.*。
An administrator using NAS will have the choice to use just one root server (and all its data) or to use another NAS server for special hierarchies.
使用NAS的管理员可以选择仅使用一台根服务器（及其所有数据），也可以选择使用另一台NAS服务器进行特殊层次结构。
.............. .............. ...................
. NAS server. . NAS server. . NAS server .
. . . . . alt.*, .
. alt.* . . Big8 . . !alt.binaries.*.
.............. .............. ...................
. database . . database . . database .
.............. .............. ...................
^ ^ ^ ^
`--+ +--' `------+ +----'
| | | |
.------------. .------------.
| NAS client | | NAS client |
+------------+ +------------+
| netnews | | netnews |
| server | | server |
.------------. .------------.
.............. .............. ...................
. NAS server. . NAS server. . NAS server .
. . . . . alt.*, .
. alt.* . . Big8 . . !alt.binaries.*.
.............. .............. ...................
. database . . database . . database .
.............. .............. ...................
^ ^ ^ ^
`--+ +--' `------+ +----'
| | | |
.------------. .------------.
| NAS client | | NAS client |
+------------+ +------------+
| netnews | | netnews |
| server | | server |
.------------. .------------.
Configuration A Configuration B
配置A配置B
Figure 1
图1
NAS contains information about newsgroups and complete hierarchies. Furthermore, it contains information about the hierarchies' inheritable entries and default values for a single newsgroup.
NAS包含有关新闻组和完整层次结构的信息。此外，它还包含有关层次结构的可继承项和单个新闻组的默认值的信息。
It is expected that the real-life use of NAS will change the requirements for the Netnews Administration System. On the one hand, the protocol has to be extensible and flexible in order to implement improvements; on the other hand, it must ensure compatibility between different versions. A simultaneous migration of all sites using NAS to a new protocol version is not likely to happen. To solve this problem, NAS has a protocol level. This protocol level describes the current functionality. The protocol level, being a number between 1 and 32767, is negotiated at connection setup. Enhancements and modifications must use a different protocol level than that of their predecessors. (Usually the protocol level is incremented by 1 with every new version of the protocol specification.) Every current or future implementation MUST be compatible with protocol level 1 in order to fall back to this level if communication on a higher level fails.
预计NAS的实际使用将改变Netnews管理系统的要求。一方面，为了实现改进，协议必须具有可扩展性和灵活性；另一方面，它必须确保不同版本之间的兼容性。不太可能同时将所有使用NAS的站点迁移到新的协议版本。为了解决这个问题，NAS有一个协议级别。此协议级别描述当前功能。协议级别是介于1和32767之间的数字，在连接设置时协商。增强和修改必须使用与先前版本不同的协议级别。（通常，协议级别随着协议规范的每一个新版本而增加1。）如果更高级别的通信失败，每个当前或未来的实现必须与协议级别1兼容，以便返回到该级别。
An implementation of higher protocol levels should be able to emulate the behavior of lower levels, even if this implies a loss of features. The negotiation of the protocol level between client and server is described in the specification of the command VERS. If there is no agreement on the protocol level, only commands of the
较高协议级别的实现应该能够模拟较低级别的行为，即使这意味着功能丢失。命令VERS的规范中描述了客户端和服务器之间协议级别的协商。如果在协议级别上没有一致意见，则只使用
protocol level 1 MUST be used. Documents enhancing or modifying the NAS standard MUST specify on which level these changes take place and how the behavior should be in other protocol levels.
必须使用协议级别1。增强或修改NAS标准的文档必须指定这些更改发生在哪个级别，以及行为在其他协议级别上应如何。
This document describes protocol level 1.
本文档描述协议级别1。
In order to use an NAS server, a connection must be opened by the client. The NAS server can be located in the same domain or somewhere else on the Internet.
要使用NAS服务器，客户端必须打开连接。NAS服务器可以位于同一域或Internet上的其他位置。
The NAS system is hierarchical. The idea is to have an NAS root server like the DNS root servers. The root server distributes the data collected from client NAS servers that are authoritative servers for their hierarchy. The maintenance of the authoritative data is possible on any system. The root server collects the data and makes them available to other servers, which can in turn distribute these data to other servers. The administrator has the opportunity to make use of either all data or only parts of the database. NAS servers can ask multiple NAS servers for data. An attached time stamp makes it possible to distinguish between new and old data and to avoid loops in the propagation.
NAS系统是分层的。其想法是拥有一个类似DNS根服务器的NAS根服务器。根服务器分发从客户端NAS服务器收集的数据，这些服务器是其层次结构的权威服务器。在任何系统上都可以维护权威数据。根服务器收集数据并将其提供给其他服务器，而其他服务器又可以将这些数据分发给其他服务器。管理员有机会使用所有数据或仅使用数据库的一部分。NAS服务器可以向多个NAS服务器请求数据。附加的时间戳可以区分新数据和旧数据，并避免传播中的循环。
To describe the NAS in greater detail, it is necessary to emphasize the hierarchical design of the NAS system. The following figure shows the propagation of data along the server hierarchy.
为了更详细地描述NAS，有必要强调NAS系统的分层设计。下图显示了数据沿服务器层次结构的传播。
Authoritative data for a newsgroup or a hierarchy are collected and written into a database. These data are available through a local NAS server and are collected from this authoritative server by upstream NAS servers.
新闻组或层次结构的权威数据被收集并写入数据库。这些数据可通过本地NAS服务器获得，并由上游NAS服务器从此权威服务器收集。
There may also be NAS servers that are not authoritative servers; these servers merely provide the information they collect from other NAS servers to clients such as news servers, administration programs, and news readers.
也可能存在不是权威服务器的NAS服务器；这些服务器仅将从其他NAS服务器收集的信息提供给客户端，如新闻服务器、管理程序和新闻阅读器。
............ collects from >
. root NAS.-------------------------+
. server .----------------+ |
............ | |
. database. | |
............ | |
^ v | ..........................
| | | . NAS server .
| |distributes | . authoritative for de.*.
queries| | | ..........................
| | | . database .
^ v | ..........................
.............. |
. NAS server. `--------+
.............. |
. database . ...........................
.............. . NAS server .
^ ^ ^ . authoritative for bln.*.
| | | .---------. ...........................
q | | `--| netnews | . database .
u | | | server | ...........................
e | | .---------.
r | |
i | | .---------.
e | `--| admin |
s | | program |
| .---------.
|
| .---------.
`--| news |
| reader |
.---------.
............ collects from >
. root NAS.-------------------------+
. server .----------------+ |
............ | |
. database. | |
............ | |
^ v | ..........................
| | | . NAS server .
| |distributes | . authoritative for de.*.
queries| | | ..........................
| | | . database .
^ v | ..........................
.............. |
. NAS server. `--------+
.............. |
. database . ...........................
.............. . NAS server .
^ ^ ^ . authoritative for bln.*.
| | | .---------. ...........................
q | | `--| netnews | . database .
u | | | server | ...........................
e | | .---------.
r | |
i | | .---------.
e | `--| admin |
s | | program |
| .---------.
|
| .---------.
`--| news |
| reader |
.---------.
Figure 2
图2
Requests to an NAS server originating at a client (as well as at another server) are accomplished in several steps: establishing a connection, authentication (optional), negotiating a protocol level (optional), queries on the database, and termination.
从客户端（以及另一台服务器）发出的对NAS服务器的请求通过以下几个步骤完成：建立连接、身份验证（可选）、协商协议级别（可选）、查询数据库和终止。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
An answer starts with a response code (a three-digit number), optionally followed by white space and a textual message. Then the actual text/data follows. Text is sent as a series of successive lines of textual matter, each terminated with CRLF. A single line containing only a single period ('.') is sent to indicate the end of the text (i.e., the server will send a CRLF at the end of the last line of text, a period, and another CRLF).
答案以响应代码（一个三位数）开始，可选地后跟空白和文本消息。然后实际的文本/数据如下。文本作为一系列连续的文本行发送，每行以CRLF结尾。发送仅包含单个句点（'.'）的单行，以指示文本的结尾（即，服务器将在最后一行文本的结尾处发送一个CRLF、一个句点和另一个CRLF）。
Answer = response-code [answertext] CRLF text CRLF "." CRLF
应答=应答码[answertext]CRLF text CRLF.“CRLF”
If the original text contains a period as the first character of the text line, that first period is doubled. Therefore, the client must examine the first character of each line received and, for those beginning with a period, determine either that this is the end of the text or that it should collapse the doubled period to a single one.
如果原始文本包含句点作为文本行的第一个字符，则第一个句点将加倍。因此，客户必须检查收到的每行的第一个字符，对于以句点开头的字符，确定这是文本的结尾，或者应该将加倍的句点折叠为单个句点。
Example
实例
<-- INFO --> 101 Information follows Server: nas.example.org (192.0.2.100) Uptime: 2 weeks, 3 days, 5 hours, 9 minutes Software: NAS 1.0 Client: client.example.org (192.0.2.123) Connection: 9 minutes Highest protocol level supported: 1 Requested protocol level: 1 Protocol level used: 1 .
<--INFO-->101信息如下服务器：nas.example.org（192.0.2.100）正常运行时间：2周3天5小时9分钟软件：nas 1.0客户端：Client.example.org（192.0.2.123）连接：9分钟支持的最高协议级别：1请求的协议级别：1使用的协议级别：1。
The first digit of the response code indicates the message type (i.e., information, success, warning, error, or data):
响应代码的第一位数字表示消息类型（即信息、成功、警告、错误或数据）：
1xx Information 2xx Request successful 3xx Request successful, data follow 4xx Request accepted, but no operation possible
1xx信息2xx请求成功3xx请求成功，数据跟随4xx请求已接受，但无法操作
5xx Request is wrong (syntax error), is not implemented, or leads to an internal error 6xx Request successful, data follow until end mark
5xx请求错误（语法错误）、未实现或导致内部错误6xx请求成功，数据跟随直到结束标记
The second digit specifies the message category:
第二位数字指定消息类别：
x0x Connection-related stuff x1x Queries, answers, or data x2x Server-server communication x3x Authentication, authorization x8x Non-standard extensions x9x Debugging output
x0x连接相关内容x1x查询、答案或数据x2x服务器通信x3x身份验证、授权x8x非标准扩展x9x调试输出
The actual response code for a specific command is listed in the description of the commands. Answers of the type 1xx, 2xx, 4xx, and 5xx can have a text after the numerical code. 3xx answers contain one or more parameters with data; the exact format is explained in the description of the commands.
命令说明中列出了特定命令的实际响应代码。1xx、2xx、4xx和5xx类型的答案可以在数字代码后有文本。3xx答案包含一个或多个带有数据的参数；命令说明中解释了确切的格式。
An answer to an incorrect request may be longer than one line.
对错误请求的答复可能超过一行。
NAS typically uses port 991, which is reserved by IANA [IANA-PN]. If a connection is set up by the client, the server answers immediately (without a request) with the greeting message, which will start with code 200:
NAS通常使用IANA[IANA-PN]保留的端口991。如果客户端建立了连接，服务器将立即（无需请求）回复问候消息，该消息将以代码200开头：
--> 200 Welcome! nas.example.org ready .
-->200欢迎！nas.example.org准备就绪。
If a connection is refused because the client has no permission to access the server, the answer code is 434. That decision can be made on connection startup based on the client's IP address. When the server is currently out of service, the answer code is 404.
如果由于客户端没有访问服务器的权限而拒绝连接，则回答代码为434。可以根据客户端的IP地址在连接启动时做出该决定。当服务器当前停止服务时，应答码为404。
Examples:
示例：
--> 434 You have no permission to retrieve data. Good bye. .
-->434您没有检索数据的权限。再见。
--> 404 Maintenance time .
-->404维护时间。
After sending a 404 or 434 message, the connection will be closed.
发送404或434消息后，连接将关闭。
A command consists of a command word, sometimes followed by a parameter. Parameters are separated from the command word by white space.
命令由命令字组成，有时后跟参数。参数与命令字之间用空格隔开。
Commands used in the NAS protocol are not case sensitive. A command word or parameter may be uppercase, lowercase, or any mixture of upper- and lowercase.
NAS协议中使用的命令不区分大小写。命令字或参数可以是大写、小写或任意大小写混合。
The length of a command line is not limited. If the need to limit the length of command lines in real-life implementations arises, answer code 513 (line too long) should be returned.
命令行的长度不受限制。如果在实际实现中需要限制命令行的长度，则应返回应答代码513（行太长）。
The protocol level described in this document uses command words with a length of exactly four characters each.
本文档中描述的协议级别使用的命令字每个字的长度正好为四个字符。
In examples, octets sent to the NAS server are preceded by "<-- " and those sent by the NAS server by "--> ". The indicator is omitted if the direction of the dialog does not change.
在示例中，发送到NAS服务器的八位字节前面是“<--”，而由NAS服务器发送的八位字节前面是“-->”。如果对话框的方向不变，则省略该指示器。
The commands described below are defined using the Augmented Backus-Naur Form (ABNF) defined in [RFC4234]. The definitions for 'ALPHA', 'CRLF', 'DIGIT', 'WSP' and 'VCHAR' are taken from appendix B of [RFC4234] and not repeated here.
下面描述的命令是使用[RFC4234]中定义的扩充巴科斯诺尔表（ABNF）定义的。“ALPHA”、“CRLF”、“DIGIT”、“WSP”和“VCHAR”的定义取自[RFC4234]的附录B，此处不再重复。
The following ABNF definitions constitute the set of NAS commands that can be sent from the client to an NAS server.
以下ABNF定义构成了可以从客户端发送到NAS服务器的NAS命令集。
Some overall definitions follow:
以下是一些总体定义：
text = %d1-9 / ; all octets except
%d11-12 / ; US-ASCII NUL, CR and LF
%d14-255
text = %d1-9 / ; all octets except
%d11-12 / ; US-ASCII NUL, CR and LF
%d14-255
answertext = WSP *( ALPHA / DIGIT / "+" / "-" / "/" / "_" /
"." / "," / ":" / "=" / "?" / "!" / SP )
answertext = WSP *( ALPHA / DIGIT / "+" / "-" / "/" / "_" /
"." / "," / ":" / "=" / "?" / "!" / SP )
utc-time = 14DIGIT ; the date and time of the server in UTC ; YYYYMMDDhhmmss
utc时间=14位；服务器的日期和时间（UTC）；YYYYMMDDhhmmss
response-code = 3DIGIT ; three digit number
响应代码=3DIGIT；三位数
Newsgroup names and hierarchy names are defined according to the following ABNF definitions. Since a hierarchy name can be the same as a newsgroup name (e.g., hierarchy bln.announce.fub.* and newsgroup name bln.announce.fub), there is no difference between the two.
新闻组名称和层次结构名称是根据以下ABNF定义定义的。由于层次结构名称可以与新闻组名称相同（例如，层次结构bln.announce.fub.*和新闻组名称bln.announce.fub），因此两者之间没有区别。
name = plain-component *("." component)
component = plain-component / encoded-word
encoded-word = 1*( lowercase / DIGIT /
"+" / "-" / "/" / "_" / "=" / "?" )
plain-component = component-start *component-rest
component-start = lowercase / DIGIT
lowercase = %x61-7A ; letter a-z lowercase
component-rest = component-start / "+" / "-" / "_"
name = plain-component *("." component)
component = plain-component / encoded-word
encoded-word = 1*( lowercase / DIGIT /
"+" / "-" / "/" / "_" / "=" / "?" )
plain-component = component-start *component-rest
component-start = lowercase / DIGIT
lowercase = %x61-7A ; letter a-z lowercase
component-rest = component-start / "+" / "-" / "_"
NOTE: This definition of newsgroup name is in reference to "News Article Format and Transmission" [SON1036]. When the document "News Article Format" [USEFOR] is established as an RFC, its definitions should be integrated into a higher protocol level of NAS.
注：新闻组名称的定义参考“新闻文章格式和传输”[SON1036]。当文档“新闻文章格式”[USEFOR]被确定为RFC时，其定义应集成到NAS的更高协议级别。
Description
描述
This command prints a short help text on a given command. If called without parameters, it will display a complete list of commands.
此命令在给定命令上打印简短的帮助文本。如果在没有参数的情况下调用，它将显示命令的完整列表。
help-cmd = "HELP" [WSP commandname] CRLF
help cmd=“help”[WSP commandname]CRLF
commandname = "DATA" / "DATE" / "GETP" / "GETA" /
"HELP" / "HIER" / "INFO" / "LIST" /
"LSTR" / "QUIT" / "VERS"
commandname = "DATA" / "DATE" / "GETP" / "GETA" /
"HELP" / "HIER" / "INFO" / "LIST" /
"LSTR" / "QUIT" / "VERS"
Possible answers
可能的答案
100: Command overview, command description 410: Indicates that the server is not giving any information
100：命令概述，命令说明410：表示服务器未提供任何信息
help-answer = "410" [answertext] CRLF text CRLF "." CRLF help-answer =/ "100" [answertext] CRLF text CRLF "." CRLF
help answer=“410”[answertext]CRLF text CRLF“。CRLF help answer=/“100”[answertext]CRLF text CRLF“。CRLF
Examples
例子
<-- HELP
<--救命
--> 100 NAS server nas.example.org - Version 1.0
-->100 NAS服务器NAS.example.org-版本1.0
Supported commands: DATA - data for a newsgroup DATE - show time of server in UTC GETP - get package GETA - get data from an authoritative server HELP - show this help HIER - data for a hierarchy INFO - show info on current connection LIST - list newsgroups or hierarchies LSTR - recursive list newsgroups or hierarchies QUIT - close the connection VERS - show or set current protocol level
支持的命令：数据-新闻组日期的数据-在UTC GETP中显示服务器的时间-获取包GETA-从权威服务器获取数据帮助-显示此帮助HIER-层次结构的数据信息-显示当前连接列表的信息-列出新闻组或层次结构LSTR-递归列出新闻组或层次结构退出-关闭连接VERS-显示或设置当前协议级别
Contact address nas@example.org .
联系地址nas@example.org .
<-- HELP LIST --> 100 LIST LIST - list newsgroups or hierarchies Syntax: LIST hierarchy ... Get a list of newsgroups and sub-hierarchies directly under the parameter hierarchy .
<--帮助列表-->100列表-列表新闻组或层次结构语法：列表层次结构。。。直接在参数层次结构下获取新闻组和子层次结构的列表。
<-- HELP NOOP --> 410 unknown command "NOOP" .
<--HELP NOOP-->410未知命令“NOOP”。
Description
描述
Prints information about the current connection, the server, and the client.
打印有关当前连接、服务器和客户端的信息。
info-cmd = "INFO" CRLF
info cmd=“info”CRLF
Possible answers
可能的答案
101: Normal answer; prints some information about client and server
101：正常回答；打印有关客户端和服务器的一些信息
400: Indicates that the server is not giving any information
400：表示服务器未提供任何信息
info-answer = "400" [answertext] CRLF text CRLF "." CRLF info-answer =/ "101" [answertext] CRLF text CRLF "." CRLF
info answer=“400”[answertext]CRLF text CRLF“。CRLF info answer=/“101”[answertext]CRLF text CRLF“。CRLF
Examples
例子
<-- INFO --> 101 Information follows Server: nas.example.org (192.0.2.100) Uptime: 2 weeks, 3 days, 5 hours, 9 minutes Software: NAS 1.0 Client: client.example.org (192.0.2.123) Connection: 9 minutes Highest protocol level supported: 1 Requested protocol level: 1 Protocol level used: 1
<--INFO-->101信息如下服务器：nas.example.org（192.0.2.100）正常运行时间：2周3天5小时9分钟软件：nas 1.0客户端：Client.example.org（192.0.2.123）连接：9分钟支持的最高协议级别：1请求的协议级别：1使用的协议级别：1
End .
终止
<-- INFO --> 400 No information available. .
<--INFO-->400无可用信息。
Description
描述
Prints the current time of the server in UTC (Universal Coordinated Time) in the format YYYYMMDDhhmmss, followed by an optional comment. The DATE command is only for informational use and to check the server time. For regular transmission of time over the network, the Network Time Protocol (NTP) [RFC1305] should be used.
以UTC（世界协调时间）为单位，以YYYYMMDDhhmmss格式打印服务器的当前时间，后跟可选注释。DATE命令仅用于提供信息和检查服务器时间。对于通过网络定期传输时间，应使用网络时间协议（NTP）[RFC1305]。
date-cmd = "DATE" CRLF
date cmd=“date”CRLF
Possible answers
可能的答案
300: Print the UTC time in specified format; see below
511: Error; print an error message
300: Print the UTC time in specified format; see below
511: Error; print an error message
date-answer = "511" [answertext] CRLF text CRLF "." CRLF
date answer=“511”[answertext]CRLF text CRLF.“CRLF”
date-answer =/ "300" [answertext] CRLF utc-time [answertext] CRLF "." CRLF
回答日期=/“300”[answertext]CRLF utc时间[answertext]CRLF.“CRLF”
Examples
例子
<-- DATE --> 300 19990427135230 UTC .
<--日期-->300 19990427135230 UTC。
<-- DATE --> 511 Time is unknown .
<--日期-->511时间未知。
Description
描述
The VERS command is used to determine the protocol level to use between client and server. The parameter is a protocol level that the client supports and wants to use. The server will respond with the highest level accepted. This version number MUST not be higher than that requested by the client. Client and server MUST only use commands from the level that the server has confirmed. It is possible, but seldom necessary, to change the protocol level during a session by client request (VERS [protocol level]). When no option is given, the current protocol level will be printed. When no protocol level is negotiated, the protocol level 1 will be used. Commands of a higher level are not allowed without successful negotiation. The protocol level can be followed by an optional comment.
VERS命令用于确定客户端和服务器之间要使用的协议级别。参数是客户端支持并希望使用的协议级别。服务器将以接受的最高级别响应。此版本号不得高于客户端请求的版本号。客户端和服务器只能使用服务器已确认的级别的命令。通过客户端请求（VERS[协议级别]）在会话期间更改协议级别是可能的，但很少有必要。如果未给出任何选项，将打印当前协议级别。当没有协商协议级别时，将使用协议级别1。未经协商成功，不允许使用更高级别的命令。协议级别后面可以跟一条可选注释。
vers-cmd = "VERS" [WSP level] CRLF
vers cmd=“vers”[WSP级别]CRLF
level = 1*5DIGIT ; the valid range is 1 - 32767
level = 1*5DIGIT ; the valid range is 1 - 32767
Possible answers
可能的答案
202: Returns current protocol level 302: Requested level accepted 402: Requested level too high; falling back to lower level 510: Syntax error
202：返回当前协议级别302：请求级别已接受402：请求级别过高；返回到较低级别510：语法错误
vers-answer = "202" [answertext] CRLF level [answertext] CRLF "." CRLF
vers answer=“202”[answertext]CRLF级别[answertext]CRLF“。CRLF
vers-answer =/ "302" [answertext] CRLF level [answertext] WSP level CRLF "." CRLF vers-answer =/ "402" [answertext] CRLF level [answertext] WSP level CRLF "." CRLF vers-answer =/ "510" [answertext] CRLF level [answertext] CRLF "." CRLF
vers ANSWERT=/“302”[answertext]CRLF级别[answertext]WSP级别CRLF.“CRLF vers ANSWERT=/“402”[answertext]CRLF级别[answertext]WSP级别CRLF.“CRLF vers ANSWERT=/“510”[answertext]CRLF级别[answertext]CRLF.“CRLF
Examples
例子
<-- VERS --> 202 2 Current protocol level is 2 .
<--VERS-->202 2当前协议级别为2。
<-- VERS 2 --> 302 2 My max protocol level is 10 .
<--VERS 2-->302 2我的最大协议级别为10。
<-- VERS 11 --> 402 10 Falling back to level 10 .
<--VERS 11-->402 10回落到10级。
<-- VERS BAL --> 510 1 Syntax error .
<--VERS BAL-->510 1语法错误。
Description
描述
Terminates the connection.
终止连接。
quit-cmd = "QUIT" CRLF
quit cmd=“quit”CRLF
Possible answers
可能的答案
201: Termination of the connection
201：连接的终止
quit-answer = "201" [answertext] CRLF
退出answer=“201”[answertext]CRLF
Example
实例
<-- QUIT --> 201 Closing connection. Bye.
<--退出-->201关闭连接。再见
Description
描述
To obtain a list of newsgroups and sub-hierarchies in the requested hierarchies, the command LIST is used. The status of the hierarchies is also given. The highest level consists of all top-level hierarchies and is labeled "*". It can be obtained this way, too.
要获取所请求层次结构中的新闻组和子层次结构列表，请使用命令列表。还给出了层次结构的状态。最高级别由所有顶级层次结构组成，标记为“*”。它也可以通过这种方式获得。
The data consist of a newsgroup- or hierarchy-name/status indicator pair per line. Name and status indicator must be separated by at least one white space. The status indicator is a single word (see Section 6.4). The interpretation is not case sensitive.
数据由每行的新闻组或层次结构名称/状态指示器对组成。名称和状态指示器必须至少用一个空格分隔。状态指示器是一个单词（见第6.4节）。解释不区分大小写。
list-cmd = "LIST" ( WSP "*" / 1*(WSP name)) CRLF
list-cmd = "LIST" ( WSP "*" / 1*(WSP name)) CRLF
Possible answers
可能的答案
401: Permission denied 510: Syntax error 610: Normal response with all requested data
401:权限被拒绝510:语法错误610:对所有请求数据的正常响应
list-answer = "610" [answertext] CRLF *(listdata CRLF) "." CRLF list-answer =/ "401" [answertext] CRLF text CRLF "." CRLF list-answer =/ "510" [answertext] CRLF text CRLF "." CRLF
list ANSWERT=“610”[answertext]CRLF*（listdata CRLF）”.“CRLF list ANSWERT=/“401”[answertext]CRLF text CRLF.“CRLF list answertext=/“510”[answertext]CRLF text CRLF.“CRLF”
listdata = name WSP list-status
listdata = name WSP list-status
The list-status is the status of a newsgroup or hierarchy according to Section 6.4.
根据第6.4节，列表状态是新闻组或层次结构的状态。
list-status = "Complete" / "Incomplete" / "Obsolete" / "Unknown" / "Unmoderated" / "Readonly" /
列表状态=“完成”/“不完整”/“过时”/“未知”/“未减额”/“只读”/
"Moderated" / "Removed" ; list-status is case-insensitive
“已缓和”/“已删除”；列表状态不区分大小写
Examples
例子
<-- LIST * --> 610 data follow alt Incomplete comp Complete de Incomplete rec Complete sub Obsolete .
<--LIST*-->610数据遵循alt comp Complete de Complete de Complete rec Complete sub OPERATE。
<-- LIST de --> 610 data follow de.admin Complete de.alt Incomplete de.comm Complete de.comp Complete de.etc Complete de.markt Complete de.newusers Complete de.org Complete de.rec Complete de.sci Complete de.soc Complete de.answers Moderated de.test Unmoderated .
<--列表de-->610数据遵循de.admin完成de.alt不完整de.comm完成de.comp完成de.etc完成de.markt完成de.newusers完成de.org完成de.rec完成de.sci完成de.soc完成de.answers主持de.test未降额。
<-- LIST foo --> 610 data follow foo Unknown .
<--列出foo-->610数据跟随foo未知。
<-- LIST --> 510 Syntax error missing parameter hierarchy .
<--列表-->510语法错误缺少参数层次结构。
<-- LIST de --> 401 Something is wrong Permission denied .
<--LIST de-->401某些错误权限被拒绝。
Description
描述
To obtain a recursive list of newsgroups and sub-hierarchies in the named hierarchy, the command LSTR is used. The status of the hierarchies is also given. The highest level consists of all top-level hierarchies and is labeled "*". It can be obtained this way, too.
要获取命名层次结构中新闻组和子层次结构的递归列表，请使用命令LSTR。还给出了层次结构的状态。最高级别由所有顶级层次结构组成，标记为“*”。它也可以通过这种方式获得。
The use of "*" as a wildcard pattern following the beginning of a hierarchy name is also possible; so a "LSTR de.a*" would return a list of all newsgroups and hierarchies starting with "de.a".
也可以在层次结构名称的开头使用“*”作为通配符模式；因此，“LSTR de.a*”将返回以“de.a”开头的所有新闻组和层次结构的列表。
lstr-cmd = "LSTR" ( WSP "*" / 1*(WSP name ["*" / ".*"]) ) CRLF
lstr-cmd = "LSTR" ( WSP "*" / 1*(WSP name ["*" / ".*"]) ) CRLF
Possible answers
可能的答案
401: Permission denied 510: Syntax error 610: Normal answer with all requested data
401:权限被拒绝510:语法错误610:所有请求数据的正常回答
lstr-answer = "610" [answertext] CRLF *(listdata CRLF) "." CRLF lstr-answer =/ "401" [answertext] CRLF text CRLF "." CRLF lstr-answer =/ "510" [answertext] CRLF text CRLF "." CRLF
lstr answer=“610”[answertext]CRLF*（列表数据CRLF）”。“CRLF lstr answer=/“401”[answertext]CRLF text CRLF”。“CRLF lstr answer=/“510”[answertext]CRLF text CRLF”。“CRLF”
listdata = name WSP list-status
listdata = name WSP list-status
The list-status is the status of a newsgroup or hierarchy according to Section 6.4.
根据第6.4节，列表状态是新闻组或层次结构的状态。
list-status = "Complete" / "Incomplete" / "Obsolete" / "Unknown" / "Unmoderated" / "Readonly" / "Moderated" / "Removed" ; list-status is case-insensitive
列表状态=“完成”/“未完成”/“过时”/“未知”/“未减额”/“只读”/“已缓和”/“已删除”；列表状态不区分大小写
Example
实例
<-- LSTR de.admin --> 610 recursive mode de.admin Complete de.admin.infos Moderated de.admin.lists Moderated de.admin.misc Unmoderated de.admin.net-abuse Complete de.admin.net-abuse.announce Moderated de.admin.net-abuse.mail Unmoderated de.admin.net-abuse.misc Unmoderated de.admin.net-abuse.news Unmoderated de.admin.news Complete de.admin.news.announce Moderated de.admin.news.groups Unmoderated de.admin.news.misc Unmoderated de.admin.news.nocem Unmoderated de.admin.news.regeln Unmoderated .
<--LSTR de.admin-->610递归模式de.admin Complete de.admin.infos demediated de.admin.lists demediated de.admin.misc underated de.admin.net-rause Complete de.admin.net-rause.annound demediated de.admin.net-rause.mail underated de.admin.net-rause.misc underated de.admin.net-rause.news underated de.admin.news Completede.admin.news.annound主持de.admin.news.groups未降额de.admin.news.misc未降额de.admin.news.nocem未降额de.admin.news.regeln未降额。
Description
描述
The command HIER lists all information available about the hierarchy. With the data header "Name", a new data block for each hierarchy is started. The header "Name" gives the name of the hierarchy. The data headers are described in Section 6.3.4. The default is to transmit all available information. It can be limited to a list of desired headers ("Name" and "Status" are always given). A set of comma-separated headers, as an option to the HIER command, will return the requested header fields.
命令HIER列出了有关层次结构的所有可用信息。使用数据头“Name”，为每个层次结构启动一个新的数据块。标题“Name”给出了层次结构的名称。第6.3.4节描述了数据标题。默认情况下，传输所有可用信息。可以将其限制为所需标题的列表（“始终提供名称”和“状态”）。作为HIER命令的一个选项，一组逗号分隔的标题将返回请求的标题字段。
hier-cmd = "HIER" 1*(WSP name) [WSP selection] CRLF
hier cmd=“hier”1*（WSP名称）[WSP选择]CRLF
selection = *( "," header ) ; Describes the data fields
; that are requested
header = ALPHA *( ALPHA / "-" ) ; According to section 6.3.4
selection = *( "," header ) ; Describes the data fields
; that are requested
header = ALPHA *( ALPHA / "-" ) ; According to section 6.3.4
Example for selection
选择示例
,Followup,Description : For all entries list Name, Status, Followup and Description
，Followup，Description：对于所有条目，请列出名称、状态、Followup和Description
Possible answers
可能的答案
401: Permission denied
401：拒绝许可
510: Syntax error 611: Regular answer with all requested data
510:语法错误611:包含所有请求数据的常规答案
hier-answer = "611" [answertext] CRLF *(hierdata CRLF) "." CRLF hier-answer =/ "510" [answertext] CRLF *(text CRLF) "." CRLF hier-answer =/ "401" [answertext] CRLF *(text CRLF) "." CRLF
hier answer=“611”[answertext]CRLF*（hierdata CRLF）”。“CRLF hier ANSWERT=/“510”[answertext]CRLF*（text CRLF）”。“CRLF hier ANSWERT=/“401”[answertext]CRLF*（text CRLF）”。“CRLF”
hierdata = "Name:" WSP text CRLF
"Status:" WSP text CRLF
*(header ":" WSP text CRLF)
[("Ctl-PGP-Key:" CRLF PGP-answer /
"Mod-PGP-Key:" CRLF PGP-answer)]
hierdata = "Name:" WSP text CRLF
"Status:" WSP text CRLF
*(header ":" WSP text CRLF)
[("Ctl-PGP-Key:" CRLF PGP-answer /
"Mod-PGP-Key:" CRLF PGP-answer)]
PGP-answer: The exact format is described in Section 6.7.
PGP回答：具体格式见第6.7节。
Examples
例子
<-- HIER de
--> 611 Data coming
Name: de
Status: Complete
Serial: 20020823120306
Description: Internationale deutschsprachige Newsgruppen
Netiquette: http://www.kirchwitz.de.example/~amk/dni/netiquette
FAQ: http://www.kirchwitz.de.example/~amk/dai/einrichtung
Ctl-Send-Adr: moderator@dana.de.example
Ctl-Newsgroup: de.admin.news.announce
Mod-Wildcard: %s@moderators.dana.de.example
Language: DE
Charset: ISO-8859-1
Encoding: text/plain
Newsgroup-Type: Discussion
Hier-Type: Global
Comp-Length: 14
Date-Create: 19920106000000
<-- HIER de
--> 611 Data coming
Name: de
Status: Complete
Serial: 20020823120306
Description: Internationale deutschsprachige Newsgruppen
Netiquette: http://www.kirchwitz.de.example/~amk/dni/netiquette
FAQ: http://www.kirchwitz.de.example/~amk/dai/einrichtung
Ctl-Send-Adr: moderator@dana.de.example
Ctl-Newsgroup: de.admin.news.announce
Mod-Wildcard: %s@moderators.dana.de.example
Language: DE
Charset: ISO-8859-1
Encoding: text/plain
Newsgroup-Type: Discussion
Hier-Type: Global
Comp-Length: 14
Date-Create: 19920106000000
.
.
<-- HIER bln --> 401 Permission denied .
<--HIER bln-->401权限被拒绝。
<-- HIER --> 510 Syntax error missing parameter hierarchy .
<--HIER-->510语法错误缺少参数层次结构。
Description
描述
The DATA command corresponds to the HIER command, as explained in 6.3.3.8, but it is used for information about a newsgroup. A summary of codes can be found in Section 6.3.4.
DATA命令对应于HIER命令，如6.3.3.8所述，但它用于提供有关新闻组的信息。代码摘要见第6.3.4节。
data-cmd = "DATA" 1*(WSP name) [WSP selection] CRLF
data cmd=“data”1*（WSP名称）[WSP选择]CRLF
Possible answers
可能的答案
401: Permission denied 510: Syntax error 612: Regular answer with all requested data
401:权限被拒绝510:语法错误612:包含所有请求数据的常规答案
data-answer = "612" [answertext] CRLF *(datadata CRLF) "." CRLF data-answer =/ "510" [answertext] CRLF text CRLF "." CRLF data-answer =/ "401" [answertext] CRLF text CRLF "." CRLF
数据回答=“612”[answertext]CRLF*（数据数据CRLF）”。“CRLF数据回答=/“510”[answertext]CRLF文本CRLF”。“CRLF数据回答=/“401”[answertext]CRLF文本CRLF”。“CRLF”
datadata = "Name:" WSP text CRLF
"Status:" WSP text CRLF
*(header ":" WSP text CRLF)
[("Ctl-PGP-Key:" CRLF PGP-answer /
"Mod-PGP-Key:" CRLF PGP-answer)]
datadata = "Name:" WSP text CRLF
"Status:" WSP text CRLF
*(header ":" WSP text CRLF)
[("Ctl-PGP-Key:" CRLF PGP-answer /
"Mod-PGP-Key:" CRLF PGP-answer)]
Examples
例子
<-- DATA de.comp.os.unix.linux.moderated
--> 612 data follow
Name: de.comp.os.unix.linux.moderated
Status: Moderated
Serial: 20020823120312
Description: Linux und -Distributionen.
<dcoulm-moderators@linux-config.de.example>
Charter: http://www.dana.de.example/mod/chartas/de.html
Netiquette: http://www.kirchwitz.de.example/~amk/dni/netiquette
<-- DATA de.comp.os.unix.linux.moderated
--> 612 data follow
Name: de.comp.os.unix.linux.moderated
Status: Moderated
Serial: 20020823120312
Description: Linux und -Distributionen.
<dcoulm-moderators@linux-config.de.example>
Charter: http://www.dana.de.example/mod/chartas/de.html
Netiquette: http://www.kirchwitz.de.example/~amk/dni/netiquette
Netiquette: ftp://ftp.fu-berlin.de.example/doc/usenet/german
/Netiquette
Mod-Sub-Adr: dcoulm-moderators@linux-config.de.example
Mod-Group-Info: http://wpxx02.toxi.uni-wuerzburg.de.example
/~dcoulmod/
Newsgroup-Type: Discussion
Netiquette: ftp://ftp.fu-berlin.de.example/doc/usenet/german
/Netiquette
Mod-Sub-Adr: dcoulm-moderators@linux-config.de.example
Mod-Group-Info: http://wpxx02.toxi.uni-wuerzburg.de.example
/~dcoulmod/
Newsgroup-Type: Discussion
.
.
<-- DATA de.foo --> 612 data follow Name: de.foo Status: Unknown
<--DATA de.foo-->612数据跟随名称：de.foo状态：未知
.
.
<-- DATA de --> 401 Permission denied .
<--数据删除-->401权限被拒绝。
<-- DATA --> 510 Syntax error missing parameter newsgroup .
<--数据-->510语法错误缺少参数新闻组。
Description
描述
GETP is used for server-server communication. It requests the data for the hierarchy specified by the parameter "name". The format of the data is the same as for the commands "HIER" and "LIST". If "*" is given as hierarchy name, all data the server is offering will be transmitted.
GETP用于服务器通信。它请求参数“name”指定的层次结构的数据。数据格式与命令“HIER”和“LIST”的格式相同。如果以“*”作为层次结构名称，则将传输服务器提供的所有数据。
The "timestamp" attached to a package consists of the date and time that the package was created. The timestamp for a package is transmitted together with the package data by the server and marks a specific revision for the package data.
附加到包的“时间戳”包括创建包的日期和时间。服务器将包的时间戳与包数据一起传输，并标记包数据的特定修订。
When a client requests a package with GETP, it transmits the timestamp attached to the package in its database so that the server can check whether the data on the client side is still valid or if it is too old. If the data on the client side is still valid, a 213 answer is sent, so the client knows that its data is OK. If the timestamp is "0", the server is forced to transmit the data.
当客户端使用GETP请求包时，它会在其数据库中传输附加到包的时间戳，以便服务器可以检查客户端的数据是否仍然有效或是否太旧。如果客户端上的数据仍然有效，则发送213应答，以便客户端知道其数据正常。如果时间戳为“0”，服务器将被迫传输数据。
Timestamps set by the server must be increasing and may not be more than 12 hours in the future.
服务器设置的时间戳必须增加，并且在将来不能超过12小时。
The data for a successful request are signed and sent in ASCII armor according to [RFC2440], so a client can check the signature or ignore it. The actual data will be surrounded by the armor start and end sections, according to Section 6.2 of [RFC2440].
成功请求的数据根据[RFC2440]以ASCII格式签名和发送，因此客户端可以检查签名或忽略签名。根据[RFC2440]第6.2节，实际数据将由装甲开始和结束部分包围。
getp-cmd = "GETP" WSP username WSP password WSP timestamp WSP ( name / "*" ) CRLF
getp cmd=“getp”WSP username WSP password WSP timestamp WSP（name/“*”）CRLF
username = *1( VCHAR ) / "0" ; Length of VCHAR >= 1
username = *1( VCHAR ) / "0" ; Length of VCHAR >= 1
password = *1( VCHAR ) / "0" ; Length of VCHAR >= 1
password = *1( VCHAR ) / "0" ; Length of VCHAR >= 1
timestamp = utc-time / ; date and time of the last retrieval
"0" ; force the transmission of data
timestamp = utc-time / ; date and time of the last retrieval
"0" ; force the transmission of data
Possible answers
可能的答案
213: Current data at the client side 411: No hierarchy with that name 430: Permission denied 510: Syntax error 613: Hierarchy data
213:客户端的当前数据411:没有该名称的层次结构430:权限被拒绝510:语法错误613:层次结构数据
getp-answer = "613" [answertext] CRLF pgp-ascii-armor-start ; this is according to [RFC2440] *(getpdata CRLF) pgp-ascii-armor-end ; this is according to [RFC2440] "." CRLF getp-answer =/ "213" [answertext] CRLF text CRLF "." CRLF getp-answer =/ "430" [answertext] CRLF text CRLF "." CRLF getp-answer =/ "411" [answertext] CRLF text CRLF "." CRLF getp-answer =/ "510" [answertext] CRLF text CRLF "." CRLF
getp answer=“613”[answertext]CRLF pgp ascii装甲开始；这是根据[RFC2440]*（getpdata CRLF）pgp ascii铠装端；这是根据[RFC2440]“CRLF getp ANSWERT=/”213“[answertext]CRLF text CRLF”。“CRLF getp ANSWERT=/”430“[answertext]CRLF text CRLF”。“CRLF getp ANSWERT=/”411“[answertext]CRLF text CRLF CRLF”。“CRLF getp ANSWERT=/”510“[answertext]
pgp-ascii-armor-start and the pgp-ascii-armor-end are built according to [RFC2440], Section 6.2., "Forming ASCII Armor".
pgp ascii装甲起点和pgp ascii装甲终点根据[RFC2440]第6.2节“形成ascii装甲”构建。
getpdata = "Name:" WSP text CRLF
"Status:" WSP text CRLF
"Serial:" WSP timestamp CRLF
*(header ":" WSP text CRLF)
[("Ctl-PGP-Key:" CRLF PGP-answer /
"Mod-PGP-Key:" CRLF PGP-answer)]
getpdata = "Name:" WSP text CRLF
"Status:" WSP text CRLF
"Serial:" WSP timestamp CRLF
*(header ":" WSP text CRLF)
[("Ctl-PGP-Key:" CRLF PGP-answer /
"Mod-PGP-Key:" CRLF PGP-answer)]
Examples
例子
<-- GETP 0 0 0 humanities
--> 615 data follow
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
<-- GETP 0 0 0 humanities
--> 615 data follow
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Name: humanities
Status: Complete
Serial: 20020821094529
Description: Branches of learning that investigate human
constructs and concerns as opposed to natural processes.
Netiquette: ftp://rtfm.mit.edu.example/pub/usenet
/news.announce.newusers
/A_Primer_on_How_to_Work_With_the_Usenet_Community
Rules: http://www.uvv.org.example/docs/howto.txt
Ctl-Send-Adr: group-admin@isc.org.example
Ctl-Newsgroup: news.announce.newgroup
Language: EN
Charset: US-ASCII
Encoding: text/plain
Newsgroup-Type: Discussion
Hier-Type: Global
Comp-Length: 14
Date-Create: 19950417143009
Name: humanities
Status: Complete
Serial: 20020821094529
Description: Branches of learning that investigate human
constructs and concerns as opposed to natural processes.
Netiquette: ftp://rtfm.mit.edu.example/pub/usenet
/news.announce.newusers
/A_Primer_on_How_to_Work_With_the_Usenet_Community
Rules: http://www.uvv.org.example/docs/howto.txt
Ctl-Send-Adr: group-admin@isc.org.example
Ctl-Newsgroup: news.announce.newgroup
Language: EN
Charset: US-ASCII
Encoding: text/plain
Newsgroup-Type: Discussion
Hier-Type: Global
Comp-Length: 14
Date-Create: 19950417143009
Name: humanities.answers
Status: Moderated
Serial: 20020821094533
Description: Repository for periodic USENET articles. (Moderated)
Mod-Sub-Adr: news-answers@mit.edu.example
Mod-Adm-Adr: news-answers-request@mit.edu.example
Newsgroup-Type: Announce
Date-Create: 19950725182040
Name: humanities.classics
[...]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (IRIX64)
Name: humanities.answers
Status: Moderated
Serial: 20020821094533
Description: Repository for periodic USENET articles. (Moderated)
Mod-Sub-Adr: news-answers@mit.edu.example
Mod-Adm-Adr: news-answers-request@mit.edu.example
Newsgroup-Type: Announce
Date-Create: 19950725182040
Name: humanities.classics
[...]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (IRIX64)
iD8DBQE9Zj/Wn13IYldLZg8RAhWiAJ4y7o+3FzBpRjYJj2HWwXyG2g8FoQCfeEsH
rRynPhhjveiY/XBkkrrZFho=
iD8DBQE9Zj/Wn13IYldLZg8RAhWiAJ4y7o+3FzBpRjYJj2HWwXyG2g8FoQCfeEsH
rRynPhhjveiY/XBkkrrZFho=
=muK4
-----END PGP SIGNATURE-----
.
=muK4
-----END PGP SIGNATURE-----
.
<-- GETP 0 0 19990909101000 de --> 213 You are up-to-date .
<--GETP 0 0 19990909101000 de-->213您是最新的。
<-- GETP foo --> 510 Syntax error Missing parameters .
<--GETP foo-->510语法错误缺少参数。
<-- GETP guest test 0 de --> 430 You have no permission to retrieve the data .
<--GETP guest test 0 de-->430您没有检索数据的权限。
Description
描述
The GETA command is used for server-server communication; it is used to collect authoritative data and will request packages that the server is authoritative for. A package is the authoritative data either for a newsgroup or a hierarchy. Each package has a "timestamp" attached to mark the revision of the package. This timestamp is set by the server to the date of the last modification of the package data in UTC format. A timestamp of "0" indicates that the package MUST be retrieved. If the retrieving client has a recent package (i.e., no modification on the authoritative server), the server sends only a 215 response. The format of the data is the same as that for the commands "HIER" and "LIST".
GETA命令用于服务器通信；它用于收集权威数据，并将请求服务器具有权威的包。包是新闻组或层次结构的权威数据。每个包都有一个“时间戳”，用于标记包的修订。服务器将此时间戳设置为UTC格式的包数据最后一次修改的日期。时间戳“0”表示必须检索包。如果检索客户端有一个最近的包（即，权威服务器上没有修改），服务器只发送215响应。数据格式与命令“HIER”和“LIST”的格式相同。
geta-cmd = "GETA" WSP username WSP password WSP timestamp WSP name CRLF
geta cmd=“geta”WSP用户名WSP密码WSP时间戳WSP名称CRLF
Possible answers
可能的答案
215: The client already has the current data 430: Permission denied 411: No hierarchy with that name 510: Syntax error 615: Regular answer with all requested data
215:客户端已具有当前数据430:权限被拒绝411:没有该名称的层次结构510:语法错误615:对所有请求的数据进行常规回答
geta-answer = "615" [answertext] CRLF pgp-ascii-armor-start ; this is according to [RFC2440] *(getadata CRLF) pgp-ascii-armor-end ; this is according to [RFC2440] "." CRLF geta-answer =/ "215" [answertext] CRLF text CRLF "." CRLF geta-answer =/ "430" [answertext] CRLF text CRLF "." CRLF geta-answer =/ "411" [answertext] CRLF text CRLF "." CRLF geta-answer =/ "510" [answertext] CRLF text CRLF "." CRLF
geta answer=“615”[answertext]CRLF pgp ascii装甲开始；这是根据[RFC2440]*（getadata CRLF）pgp ascii铠装端；这是根据[RFC2440]“CRLF geta answer]CRLF text CRLF”；“CRLF geta answer]CRLF text CRLF”；“CRLF geta answer]CRLF text CRLF”；“CRLF geta answer]CRLF text CRLF”；“CRLF geta answer=/“215”；“CRLF geta answer]CRLF text CRLF”；“CRLF geta answer]CRLF text CRLF”；“CRLF
getadata = "Name:" WSP text CRLF
"Status:" WSP text CRLF
"Serial:" WSP timestamp CRLF
*(header ":" WSP text CRLF)
[("Ctl-PGP-Key:" CRLF PGP-answer/
"Mod-PGP-Key:" CRLF PGP-answer)]
getadata = "Name:" WSP text CRLF
"Status:" WSP text CRLF
"Serial:" WSP timestamp CRLF
*(header ":" WSP text CRLF)
[("Ctl-PGP-Key:" CRLF PGP-answer/
"Mod-PGP-Key:" CRLF PGP-answer)]
Example
实例
<-- GETA 0 0 0 humanities
--> 613 data follow
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
<-- GETA 0 0 0 humanities
--> 613 data follow
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Name: humanities
Status: Complete
Serial: 20020821094529
Description: Branches of learning that investigate human
constructs and concerns as opposed to natural processes.
Netiquette: ftp://rtfm.mit.edu.example/pub/usenet
/news.announce.newusers
/A_Primer_on_How_to_Work_With_the_Usenet_Community
Rules: http://www.uvv.org.example/docs/howto.txt
Ctl-Send-Adr: group-admin@isc.org.example
Ctl-Newsgroup: news.announce.newgroup
Language: EN
Charset: US-ASCII
Encoding: text/plain
Newsgroup-Type: Discussion
Hier-Type: Global
Name: humanities
Status: Complete
Serial: 20020821094529
Description: Branches of learning that investigate human
constructs and concerns as opposed to natural processes.
Netiquette: ftp://rtfm.mit.edu.example/pub/usenet
/news.announce.newusers
/A_Primer_on_How_to_Work_With_the_Usenet_Community
Rules: http://www.uvv.org.example/docs/howto.txt
Ctl-Send-Adr: group-admin@isc.org.example
Ctl-Newsgroup: news.announce.newgroup
Language: EN
Charset: US-ASCII
Encoding: text/plain
Newsgroup-Type: Discussion
Hier-Type: Global
Comp-Length: 14 Date-Create: 19950417143009
薪酬长度：14创建日期：19950417143009
Name: humanities.answers
Status: Moderated
Serial: 20020821094533
Description: Repository for periodic USENET articles. (Moderated)
Mod-Sub-Adr: news-answers@mit.edu.example
Mod-Adm-Adr: news-answers-request@mit.edu.example
Newsgroup-Type: Announce
Date-Create: 19950725182040
Name: humanities.answers
Status: Moderated
Serial: 20020821094533
Description: Repository for periodic USENET articles. (Moderated)
Mod-Sub-Adr: news-answers@mit.edu.example
Mod-Adm-Adr: news-answers-request@mit.edu.example
Newsgroup-Type: Announce
Date-Create: 19950725182040
Name: humanities.classics
[...]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (IRIX64)
Name: humanities.classics
[...]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (IRIX64)
iD8DBQE9Zj/Wn13IYldLZg8RAhWiAJ4y7o+3FzBpRjYJj2HWwXyG2g8FoQCfeEsH
rRynPhhjveiY/XBkkrrZFho=
=muK4
-----END PGP SIGNATURE-----
.
iD8DBQE9Zj/Wn13IYldLZg8RAhWiAJ4y7o+3FzBpRjYJj2HWwXyG2g8FoQCfeEsH
rRynPhhjveiY/XBkkrrZFho=
=muK4
-----END PGP SIGNATURE-----
.
If a command is recognized as unknown, a 519 return code (unknown command) is given. If an error occurs after the command string (e.g., a missing parameter), a 510 return code (Syntax error: Missing parameter) is given.
如果命令被识别为未知，则给出519返回码（未知命令）。如果在命令字符串之后发生错误（例如，缺少参数），则给出510返回码（语法错误：缺少参数）。
The following paragraphs describe key words and key terms that support retrieval and storing of information. Every header has a unique English name.
以下段落描述了支持信息检索和存储的关键词和关键词。每个标题都有一个唯一的英文名称。
The content of a header is inheritable within a hierarchy, as long as
头的内容可以在层次结构中继承，只要
the header is marked as inheritable. The content is the default value for all downstream newsgroups and sub-hierarchies. For example, in the hierarchy "de", the language header has the value "DE" (German); therefore, this value is "DE" for all newsgroups in this hierarchy, except for those that explicitly define a language code of their own.
标题被标记为可继承。内容是所有下游新闻组和子层次结构的默认值。例如，在层次结构“de”中，语言标题的值为“de”（德语）；因此，对于此层次结构中的所有新闻组，此值都为“DE”，但明确定义自己语言代码的新闻组除外。
Hierarchies and newsgroups must have at least values for the headers "Name" and "Status". Unknown hierarchies or groups get the status "Unknown".
层次结构和新闻组必须至少具有标题“Name”和“Status”的值。未知层次结构或组的状态为“未知”。
The header used in the NAS protocol are not case sensitive. A header may be uppercase, lowercase, or any mixture of upper- and lowercase. It is recommended that the first letter of the header and the first letter after a dash be uppercase and that all other characters be lowercase.
NAS协议中使用的标头不区分大小写。标题可以是大写、小写，也可以是大写和小写的任意组合。建议页眉的第一个字母和破折号后的第一个字母为大写，所有其他字符为小写。
Name
名称
Header: Name
标题：名称
Used for: hierarchy Mandatory: yes Inheritable: no Repeatable: no Description: Name of a hierarchy. Comment: Start of a new data block. Example: Name: comp
用于：层次结构必需：是可继承：否可重复：否说明：层次结构的名称。注释：新数据块的开始。示例：名称：comp
Used for: newsgroup Mandatory: yes Repeatable: no Description: Name of a newsgroup Comment: Start of a new data block. Example: Name: de.admin.news.announce
用于：新闻组必填：是可重复：否说明：新闻组名称注释：新数据块的开始。示例：名称：de.admin.news.announce
Status
地位
Header: Status
标题：状态
Used for: hierarchy Mandatory: yes Inheritable: no Repeatable: no Description: Status of a hierarchy. Comment: For a detailed description, see Section 6.4. Example: Status: Hierarchy-Complete
用于：层次结构必需：是可继承：否可重复：否说明：层次结构的状态。注释：有关详细说明，请参见第6.4节。示例：状态：层次结构完成
Used for: newsgroup Mandatory: yes Repeatable: no Description: Status of a newsgroup. Comment: For a detailed description, see Section 6.4. Example: Status: Group-Moderated
用于：新闻组必填：是可重复：否说明：新闻组的状态。注释：有关详细说明，请参见第6.4节。示例：状态：组主持
Serial
电视连续剧
Header: Serial
标题：序列号
Used for: hierarchy Mandatory: no Inheritable: no Repeatable: no Description: Timestamp for hierarchy data. Comment: For a detailed description, see Section 6.4. Example: Serial: 20020821102413
用于：层次结构必需：无可继承：无可重复：无描述：层次结构数据的时间戳。注释：有关详细说明，请参见第6.4节。示例：序列号：20020821102413
Used for: newsgroup Mandatory: no Inheritable: no Repeatable: no Description: Timestamp for newsgroup data. Comment: For a detailed description, see Section 6.4. Example: Serial: 20020821102413
用于：新闻组必填：无可继承：无可重复：无描述：新闻组数据的时间戳。注释：有关详细说明，请参见第6.4节。示例：序列号：20020821102413
Group for followup
跟进小组
Header: Followup
标题：后续
Used for: newsgroup Mandatory: no Repeatable: no Description: Name of the newsgroup that will take the followup postings of a moderated group. Comment: The value can be used as default value for the "Followup-To:" header on postings to a moderated group. This value is only useful on groups that are moderated (Status Group-Moderated) and have a dedicated discussion group.
用于：新闻组必填项：无可重复项：无说明：将接收主持人组后续帖子的新闻组的名称。备注：该值可用作发布到受审核组时“Followup To:”标题的默认值。此值仅对已主持（状态组主持）且具有专用讨论组的组有用。
Example: Followup: bln.announce.fub.zedat.d (for the moderated group bln.announce.fub.zedat)
示例：Followup:bln.announce.fub.zedat.d（针对版主组bln.announce.fub.zedat）
Short description
简短描述
Header: Description
标题：说明
Used for: hierarchy Mandatory: no Inheritable: no Repeatable: no Description: Short description of a hierarchy. Example: Description: Angelegenheiten, die den Grossraum Berlin betreffen (for the hierarchy bln)
用于：层次结构必需：无可继承：无可重复：无描述：层次结构的简短描述。示例：描述：Angelegenheiten，die den Grossraum Berlin betreffen（用于层次结构bln）
Used for: newsgroup Mandatory: no Repeatable: no Description: Short description of a newsgroup. Comment: This information is often presented to the news reader upon selection of the newsgroup, and it should be a brief but meaningful description of the topic. Example: Description: Technisches zur Newssoftware (for de.admin.news.software)
用于：新闻组必填：无可重复：无描述：新闻组的简短描述。评论：这些信息通常在选择新闻组时呈现给新闻读者，并且应该是对主题的简短但有意义的描述。示例：描述：Technisches zur新闻软件（用于de.admin.news.software）
Charter-URL
特许网址
Header: Charter
标题：宪章
Used for: hierarchy
Mandatory: no
Inheritable: no
Repeatable: yes
Description: URL that points to the charter of a hierarchy.
Example: Charter: ftp://ftp.fu-berlin.de.example/doc/news/bln/bln
(for the hierarchy bln)
Used for: hierarchy
Mandatory: no
Inheritable: no
Repeatable: yes
Description: URL that points to the charter of a hierarchy.
Example: Charter: ftp://ftp.fu-berlin.de.example/doc/news/bln/bln
(for the hierarchy bln)
Used for: newsgroup
Mandatory: no
Repeatable: yes
Description: URL that points to the charter of a newsgroup.
Comment: This information should be presented to the
news reader upon selection of the newsgroup.
Example: Charter: ftp://ftp.fu-berlin.de.example/doc/news/bln
/bln.markt.arbeit
Used for: newsgroup
Mandatory: no
Repeatable: yes
Description: URL that points to the charter of a newsgroup.
Comment: This information should be presented to the
news reader upon selection of the newsgroup.
Example: Charter: ftp://ftp.fu-berlin.de.example/doc/news/bln
/bln.markt.arbeit
Netiquette-URL
网络礼仪网址
Header: Netiquette
标题：网络礼仪
Used for: hierarchy
Mandatory: no
Inheritable: yes
Repeatable: yes
Description: URL that points to the netiquette of a hierarchy.
Comment: Since the netiquettes are often valid for
a complete hierarchy, this is inheritable.
Example: Netiquette:
http://www.kirchwitz.de.example/~amk/dni/netiquette
Used for: hierarchy
Mandatory: no
Inheritable: yes
Repeatable: yes
Description: URL that points to the netiquette of a hierarchy.
Comment: Since the netiquettes are often valid for
a complete hierarchy, this is inheritable.
Example: Netiquette:
http://www.kirchwitz.de.example/~amk/dni/netiquette
Used for: newsgroup
Mandatory: no
Repeatable: yes
Description: URL for Netiquette.
Comment: If a group has some special rules, this is the
pointer to these rules.
Example: Netiquette: http://go.to.example/bln.markt
(for bln.markt)
Used for: newsgroup
Mandatory: no
Repeatable: yes
Description: URL for Netiquette.
Comment: If a group has some special rules, this is the
pointer to these rules.
Example: Netiquette: http://go.to.example/bln.markt
(for bln.markt)
Frequently Asked Questions (FAQ)
常见问题（FAQ）
Header: FAQ
标题：常见问题
Used for: Newsgroup
Mandatory: no
Repeatable: yes
Description: URL for the FAQ of a newsgroup.
Example: FAQ: http://www.dard.de.example/
Used for: Newsgroup
Mandatory: no
Repeatable: yes
Description: URL for the FAQ of a newsgroup.
Example: FAQ: http://www.dard.de.example/
Administration rules
管理规则
Header: Rules
标题：规则
Used for: hierarchy Mandatory: no Inheritable: yes Repeatable: yes Description: URL pointing to a document that describes the rules for creating, deleting, or renaming newsgroups in this hierarchy. Comment: Normally inherited from the toplevel hierarchy.
用于：层次结构必需：否可继承：是可重复：是描述：指向文档的URL，该文档描述了在此层次结构中创建、删除或重命名新闻组的规则。注释：通常从顶级层次结构继承。
Example: Rules: http://www.kirchwitz.de.example/~amk/dai
/einrichtung
Example: Rules: http://www.kirchwitz.de.example/~amk/dai
/einrichtung
Control Email
控制电子邮件
Header: Ctl-Send-Adr
标题：Ctl发送Adr
Used for: hierarchy
Mandatory: no
Inheritable: yes
Repeatable: yes
Description: Email address of the sender of control messages.
Comment: Multiple addresses are valid.
Example: Ctl-Send-Adr: group-admin@isc.org.example
Used for: hierarchy
Mandatory: no
Inheritable: yes
Repeatable: yes
Description: Email address of the sender of control messages.
Comment: Multiple addresses are valid.
Example: Ctl-Send-Adr: group-admin@isc.org.example
Control newsgroup
控制新闻组
Header: Ctl-Newsgroup
标题：Ctl新闻组
Used for: hierarchy Mandatory: no Inheritable: yes Repeatable: yes Description: Name of the newsgroup that will get the postings for checkgroups, rmgroup, and newsgroup control messages. Example: Ctl-Newsgroup: de.admin.news.groups
用于：层次结构必需：否可继承：是可重复：是描述：将获取checkgroups、rmgroup和newsgroup控件消息的发布的新闻组的名称。示例：Ctl新闻组：de.admin.news.groups
Moderators
主持人
Header: Mod-Wildcard
标题：Mod通配符
Used for: hierarchy Mandatory: no Inheritable: yes Repeatable: no Description: Moderator wildcard for this hierarchy. Comment: This information can be used for the configuration of the news software, for example, to configure the moderators file in INN. Example: Mod-Wildcard: %s@moderators.dana.de.example (for the hierarchy de)
用于：层次结构必需：否可继承：是可重复：否说明：此层次结构的版主通配符。备注：此信息可用于配置新闻软件，例如，在INN中配置主持人文件。示例：Mod通配符：%s@moderators.dana.de.example（对于层次结构de）
Submission address
提交地址
Header: Mod-Sub-Adr
标题：Mod Sub Adr
Used for: newsgroup Mandatory: no Repeatable: yes Description: Email address for submissions to the newsgroup. Comment: If there is no "Mod-Sub-Adr" for a moderated newsgroup, "Mod-Wildcard" of the hierarchy is used. This is useful only for moderated groups (Status Group-Moderated). Example: Mod-Sub-Adr: news-answers@mit.edu.example (for the newsgroup news.answers)
用于：新闻组必填：否可重复：是说明：提交到新闻组的电子邮件地址。注释：如果没有“Mod Sub Adr”用于受审核的新闻组，则使用层次结构的“Mod通配符”。这仅适用于主持组（状态组主持）。示例：Mod Sub Adr:news-answers@mit.edu.example（新闻组新闻。答案）
Moderator's address (email)
主持人地址（电子邮件）
Header: Mod-Adm-Adr
标题：Mod Adm Adr
Used for: newsgroup Mandatory: no Repeatable: yes Description: Email address of the moderator of the newsgroup. Comment: If there is no code "Mod-Adm-Adr" for a moderated newsgroup, "Mod-Wildcard" of the hierarchy is used. This is useful only for moderated groups (Status Group-Moderated). Example: Mod-Adm-Adr: news-answers-request@mit.edu.example (for the newsgroup news.answers)
用于：新闻组必填：否可重复：是说明：新闻组主持人的电子邮件地址。注释：如果没有版主新闻组的代码“Mod Adm Adr”，则使用层次结构的“Mod Wildcard”。这仅适用于主持组（状态组主持）。示例：Mod Adm Adr:news answers-request@mit.edu.example（新闻组新闻。答案）
Info-URL
信息网址
Header: Mod-Group-Info
标题：模块组信息
Used for: newsgroup
Mandatory: no
Repeatable: yes
Description: URL that points to a document where the moderator
presents information about the newsgroup and the
submission of articles.
Example: Mod-Group-Info: http://www.example.org/cola-submit.html
(for comp.os.linux.announce)
Used for: newsgroup
Mandatory: no
Repeatable: yes
Description: URL that points to a document where the moderator
presents information about the newsgroup and the
submission of articles.
Example: Mod-Group-Info: http://www.example.org/cola-submit.html
(for comp.os.linux.announce)
Language
语言
Header: Language
标题：语言
Used for: hierarchy Mandatory: no Inheritable: yes Repeatable: yes Description: The language that will normally be used in postings. Comment: The notation is according to the "Content-Language" field of [RFC2616]. The languages not preferred are enclosed in parentheses. Example: Language: DE (for the hierarchy de)
用于：层次结构必填：否可继承：是可重复：是说明：通常用于发布的语言。注释：符号与[RFC2616]的“内容语言”字段一致。非首选语言用括号括起来。示例：语言：DE（用于层次结构DE）
Used for: newsgroup Mandatory: no Repeatable: yes Description: The language that will normally be used in postings. Comment: The notation is according to the "Content-Language" field of [RFC2616]. The languages not preferred are enclosed in parentheses. Example: Language: TR Language: DE Language: (EN) (for the newsgroup bln.kultur.tuerkisch)
用于：新闻组必填：否可重复：是描述：通常用于发布的语言。注释：符号与[RFC2616]的“内容语言”字段一致。非首选语言用括号括起来。示例：Language:TR Language:DE Language：（EN）（用于bln.kultur.tuerkisch新闻组）
Charset
字符集
Header: Charset
标题：字符集
Used for: hierarchy Mandatory: no Inheritable: yes Repeatable: yes Description: Charset that will normally be used in postings in this hierarchy. Comment: The complete set of charset names is defined by [RFC2277] and the IANA Character Set registry [IANA-CS]. The charsets that are not the preferred charsets are enclosed in parentheses. Example: Charset: ISO-8859-1 (for the hierarchy de)
用于：层次结构必需：否可继承：是可重复：是说明：通常在此层次结构中过帐时使用的字符集。注释：完整的字符集名称集由[RFC2277]和IANA字符集注册表[IANA-CS]定义。不是首选字符集的字符集用括号括起来。示例：字符集：ISO-8859-1（用于层次结构de）
Used for: newsgroup Mandatory: no Repeatable: yes Description: Charset that will normally be used in postings in this group. Comment: The complete set of charset names is defined by [RFC2277] and the IANA Character Set registry [IANA-CS]. The charsets that are not the preferred charsets are enclosed in parentheses. Example: Charset: ISO-8859-9 Charset: ISO-8859-1 (for the newsgroup bln.kultur.tuerkisch)
用于：新闻组必填：否可重复：是描述：通常用于此组中发布的字符集。注释：完整的字符集名称集由[RFC2277]和IANA字符集注册表[IANA-CS]定义。不是首选字符集的字符集用括号括起来。示例：字符集：ISO-8859-9字符集：ISO-8859-1（用于bln.kultur.tuerkisch新闻组）
Encoding
编码
Header: Encoding
标题：编码
Used for: hierarchy Mandatory: no Inheritable: yes Repeatable: yes Description: Encoding for this hierarchy according to MIME [RFC2045]. Comment: This is the media type used in this hierarchy; a list of registered media types can be found at [IANA-MT]. The encodings not preferred are enclosed in parentheses. Example: Encoding text/plain
用于：层次结构必需：否可继承：是可重复：是说明：根据MIME[RFC2045]对此层次结构进行编码。注释：这是此层次结构中使用的媒体类型；注册媒体类型列表可在[IANA-MT]中找到。非首选编码用括号括起来。示例：编码文本/纯文本
Used for: newsgroup Mandatory: no Repeatable: yes Description: Encoding for this newsgroup according to MIME [RFC2045]. Comment This is the media type used in this newsgroup; a list of registered media types can be found at [IANA-MT]. The encodings not preferred are enclosed in parentheses. Example: Encoding: text/plain
用于：新闻组必填：否可重复：是描述：根据MIME[RFC2045]对此新闻组进行编码。注释这是此新闻组中使用的媒体类型；注册媒体类型列表可在[IANA-MT]中找到。非首选编码用括号括起来。示例：编码：文本/普通
Type of newsgroup
新闻组类型
Header: Newsgroup-Type
标题：新闻组类型
Used for: hierarchy Mandatory: no Inheritable: yes Repeatable: yes Description: Default newsgroup type in this hierarchy. Comment: This header has no concrete meaning for a hierarchy but is used for the inheritance to newsgroups in the hierarchy. Specification of the types can be found in Section 6.5. Example: Newsgroup-Type: Discussion (for the hierarchy de)
用于：层次结构必需：否可继承：是可重复：是说明：此层次结构中的默认新闻组类型。注释：此标题对于层次结构没有具体意义，但用于继承层次结构中的新闻组。类型规范见第6.5节。示例：新闻组类型：讨论（用于层次结构de）
Used for: newsgroup Mandatory: no Repeatable: yes Description: Type of newsgroup. Comment: Specification of the types can be found in Section 6.5. Example: Newsgroup-Type: Announce (for de.admin.news.announce)
用于：新闻组必填：否可重复：是说明：新闻组类型。注释：类型规范见第6.5节。示例：新闻组类型：Announce（用于de.admin.news.Announce）
Type of hierarchy
层次结构类型
Header: Hier-Type
标题：Hier类型
Used for: hierarchy Mandatory: no Inheritable: yes Repeatable: yes Description: Type of hierarchy. Comment: Specification of the types can be found in Section 6.6. Example: Hier-Type: Regional (for hierarchy bln)
用于：层次结构必需：否可继承：是可重复：是说明：层次结构类型。注释：类型规范见第6.6节。示例：层次结构类型：区域（用于层次结构bln）
Regional or Organizational Area
Regional or Organizational Areatranslate error, please retry
Header: Area
标题：区域
Used for: hierarchy Mandatory: no Inheritable: yes Repeatable: yes Description: Description of the geographical region or organization of this hierarchy. Comment: This code is useful when the hierarchy type (Hier-Type) is "Regional" or "Organization". Example: Area: Grossraum Berlin (for the hierarchy bln)
用于：层次结构必需：否可继承：是可重复：是说明：此层次结构的地理区域或组织的说明。注释：当层次结构类型（层次结构类型）为“区域”或“组织”时，此代码非常有用。示例：区域：格罗斯劳姆柏林（用于bln层级）
Name length of group names
名称组名称的长度
Header: Name-Length
标题：名称长度
Used for: hierarchy Mandatory: no Inheritable: yes Repeatable: no Description: Maximum length of a newsgroup name. Example: Name-Length: 72 (for the hierarchy bln)
用于：层次结构必填：否可继承：是可重复：否说明：新闻组名称的最大长度。示例：名称长度：72（对于层次结构bln）
Component length of group names
组名的组件长度
Header: Comp-Length
标题：Comp长度
Used for: hierarchy Mandatory: no Inheritable: yes Repeatable: no Description: Maximum length of a single component in the newsgroup name. Example: Comp-Length: 14 (for the hierarchy de)
用于：层次结构必填：否可继承：是可重复：否说明：新闻组名称中单个组件的最大长度。示例：组件长度：14（对于层次结构de）
Article length
文章长度
Header: Article-Length
标题：文章长度
Used for: hierarchy Mandatory: no Inheritable: yes Repeatable: no Description: Maximum length of an article in bytes. Comment: This header has no concrete meaning for a hierarchy but is used for the inheritance to newsgroups in the hierarchy. Example: Article-Length: 50000
用于：层次结构必需：否可继承：是可重复：否说明：文章的最大长度（字节）。注释：此标题对于层次结构没有具体意义，但用于继承层次结构中的新闻组。示例：文章长度：50000
Used for: newsgroup Mandatory: no Repeatable: no Description: Maximum length of an article in bytes. Example: Article-Length: 50000
用于：新闻组必填：无可重复：无说明：文章的最大长度（字节）。示例：文章长度：50000
Date of creation
创建日期
Header: Date-Create
标题：创建日期
Used for: hierarchy
Mandatory: no
Inheritable: yes
Repeatable: no
Description: Creation date of a hierarchy; can even be in the future.
Comment: The format is the same as in the DATE command.
Example: Date-Create: 19970330101514
Used for: hierarchy
Mandatory: no
Inheritable: yes
Repeatable: no
Description: Creation date of a hierarchy; can even be in the future.
Comment: The format is the same as in the DATE command.
Example: Date-Create: 19970330101514
Used for: newsgroup
Mandatory: no
Repeatable: no
Description: Creation date of a newsgroup; can even be in the future.
Comment: The format is the same as in the DATE command.
Example: Date-Create: 19970330101514
Used for: newsgroup
Mandatory: no
Repeatable: no
Description: Creation date of a newsgroup; can even be in the future.
Comment: The format is the same as in the DATE command.
Example: Date-Create: 19970330101514
Date of removal
免职日期
Header: Date-Delete
标题：日期删除
Used for: hierarchy Mandatory: no Inheritable: yes Repeatable: no Description: Date of removal of a hierarchy; can even be in the future. Comment: The format is the same as in the DATE command. Example: Date-Delete: 19970330101514
用于：层次结构必需：否可继承：是可重复：否说明：删除层次结构的日期；甚至可以在将来。注释：格式与DATE命令中的格式相同。示例：日期删除：199703301011514
Used for: newsgroup Mandatory: no Repeatable: no Description: Date of removal of a newsgroup; can even be in the future. Comment: The format is the same as in the DATE command. Example: Date-Delete: 19970330101514
用于：新闻组必填：无可重复：无说明：删除新闻组的日期；甚至可以在将来。注释：格式与DATE命令中的格式相同。示例：日期删除：199703301011514
Successor
继承人
Header: Replacement
标题：替换
Used for: hierarchy Mandatory: no Inheritable: no Repeatable: yes Description: Name of the hierarchy that replaced a removed hierarchy if status is "Hierarchy-Obsolete" or will replace a hierarchy if the date of removal is in the future. Example: Replacement: de (for the hierarchy sub)
用于：层次结构必需：否可继承：否可重复：是说明：如果状态为“层次结构已过时”，则替换已删除层次结构的层次结构的名称；如果删除日期在将来，则替换层次结构的名称。示例：替换：de（用于层次结构子结构）
Used for: newsgroup Mandatory: no Repeatable: yes Description: Name of the newsgroup or newsgroups that will replace a removed newsgroup if status is "Group-Removed" or will replace the newsgroup if the date of removal is in the future. Example: Replacement: bln.markt.arbeit (for bln.jobs)
用于：新闻组必填：否可重复：是说明：如果状态为“Group removed”（组已删除），则将替换已删除新闻组的新闻组的名称；如果删除日期是将来，则将替换已删除新闻组的新闻组的名称。示例：替换：bln.markt.arbeit（用于bln.jobs）
Source
来源
Header: Source
标题：源
Used for: hierarchy
Mandatory: no
Inheritable: yes
Repeatable: no
Description: Pointer to an organization or person responsible
for this hierarchy. SHOULD be a URL or an email
address.
Example: Source: http://www.dana.de.example/mod/
(for the hierarchy de)
Used for: hierarchy
Mandatory: no
Inheritable: yes
Repeatable: no
Description: Pointer to an organization or person responsible
for this hierarchy. SHOULD be a URL or an email
address.
Example: Source: http://www.dana.de.example/mod/
(for the hierarchy de)
E: This is for tracking the maintainer of a hierarchy.
E：这是为了跟踪层次结构的维护者。
Control PGP key
控制PGP密钥
Header: Ctl-PGP-Key
标题：Ctl PGP密钥
Used for: hierarchy
Mandatory: no
Inheritable: yes
Repeatable: yes
Description: PGP key (with additional information: key owner, key-id,
etc.) of the sender of control messages in this
hierarchy.
Comment: The exact format is described in Section 6.7.
Example: Ctl-PGP-Key:
U de.admin.news.announce
B 1024
I D3033C99
L http://www.dana.de.example/mod/pgp/dana.asc
L ftp://ftp.isc.org.example/pub/pgpcontrol/PGPKEYS.gz
F 5B B0 52 88 BF 55 19 4F 66 7D C2 AE 16 26 28 25
V 2.6.3ia
K------BEGIN PGP PUBLIC KEY BLOCK-----
K-Version: 2.6.3ia
K-
K-mQCNEALZ+Xfm/WDCEMXM48gK1PlKG6TkV3SLbXt4CnzpGM0tOMa
K-HjlHqM1wEGUHD5hw/BL/heR5Tq+C5IEyXQQmYwkrgeVFMOz/rAQ
[...]
K-SDw+iQgAAtN6zrYOhHFBp+
K-VpvRovMz+lSOy9Zcsbs+5t8Pj9ZVAQyfxBkqD5A=
K-=Xwgc
K -----END PGP PUBLIC KEY BLOCK-----
Used for: hierarchy
Mandatory: no
Inheritable: yes
Repeatable: yes
Description: PGP key (with additional information: key owner, key-id,
etc.) of the sender of control messages in this
hierarchy.
Comment: The exact format is described in Section 6.7.
Example: Ctl-PGP-Key:
U de.admin.news.announce
B 1024
I D3033C99
L http://www.dana.de.example/mod/pgp/dana.asc
L ftp://ftp.isc.org.example/pub/pgpcontrol/PGPKEYS.gz
F 5B B0 52 88 BF 55 19 4F 66 7D C2 AE 16 26 28 25
V 2.6.3ia
K------BEGIN PGP PUBLIC KEY BLOCK-----
K-Version: 2.6.3ia
K-
K-mQCNEALZ+Xfm/WDCEMXM48gK1PlKG6TkV3SLbXt4CnzpGM0tOMa
K-HjlHqM1wEGUHD5hw/BL/heR5Tq+C5IEyXQQmYwkrgeVFMOz/rAQ
[...]
K-SDw+iQgAAtN6zrYOhHFBp+
K-VpvRovMz+lSOy9Zcsbs+5t8Pj9ZVAQyfxBkqD5A=
K-=Xwgc
K -----END PGP PUBLIC KEY BLOCK-----
Moderator's PGP key
主持人的PGP密钥
Header: Mod-PGP-Key
标题：Mod PGP键
Used for: newsgroup Mandatory: no Repeatable: yes Description: Public PGP key (with additional information: key owner, key-id, etc.) of this newsgroup's moderator. Comment: The exact format is described in Section 6.7 Example: See Section 6.7.
用于：新闻组强制：否可重复：是描述：此新闻组的主持人的公共PGP密钥（带有附加信息：密钥所有者、密钥id等）。注释：具体格式见第6.7节示例：见第6.7节。
The status indicator uniquely determines the status of a hierarchy or newsgroup. The indicator is case insensitive.
状态指示器唯一地确定层次结构或新闻组的状态。指示器不区分大小写。
Indicator Type Description
----------- --------- -------------------------------------------
Complete hierarchy Authorized, complete known hierarchy
Incomplete hierarchy Not completely known hierarchy (like free.*)
Obsolete hierarchy Obsolete hierarchy; should contain only
newsgroups with status "Removed"
Unknown hierarchy No information available; unknown hierarchy
Unmoderated newsgroup Posting allowed; unmoderated
Readonly newsgroup Posting not allowed
Moderated newsgroup Moderated group; articles must be sent to
the moderator
Removed newsgroup Deleted or renamed newsgroup; no posting or
transport
Unknown newsgroup Unknown group; no information available
----------- --------- -------------------------------------------
Indicator Type Description
----------- --------- -------------------------------------------
Complete hierarchy Authorized, complete known hierarchy
Incomplete hierarchy Not completely known hierarchy (like free.*)
Obsolete hierarchy Obsolete hierarchy; should contain only
newsgroups with status "Removed"
Unknown hierarchy No information available; unknown hierarchy
Unmoderated newsgroup Posting allowed; unmoderated
Readonly newsgroup Posting not allowed
Moderated newsgroup Moderated group; articles must be sent to
the moderator
Removed newsgroup Deleted or renamed newsgroup; no posting or
transport
Unknown newsgroup Unknown group; no information available
----------- --------- -------------------------------------------
A Newsgroup Type is a comprehensive overview about some characteristics of a newsgroup, being a test group, a binary group, or some other kind. The Newsgroup Type is case insensitive.
新闻组类型是关于新闻组某些特征的综合概述，包括测试组、二进制组或其他类型。新闻组类型不区分大小写。
Type Meaning
----------- ------------------------------------------------------
Discussion Discussion (text postings)
Binary (Encoded) binary postings
Sources Source postings (e.g., comp.unix.sources)
Announce Announcements, press releases, RfD/CfV
Test Test postings, sometimes reflectors (e.g., de.test)
Type Meaning
----------- ------------------------------------------------------
Discussion Discussion (text postings)
Binary (Encoded) binary postings
Sources Source postings (e.g., comp.unix.sources)
Announce Announcements, press releases, RfD/CfV
Test Test postings, sometimes reflectors (e.g., de.test)
Robots Automatic postings (like the former comp.mail.maps)
Experiment Experimental, other
----------- ------------------------------------------------------
Robots Automatic postings (like the former comp.mail.maps)
Experiment Experimental, other
----------- ------------------------------------------------------
To describe a hierarchy, the following Hierarchy Types are used. These Types are used to mark some properties of a news hierarchy. They are case insensitive.
要描述层次结构，请使用以下层次结构类型。这些类型用于标记新闻层次结构的某些属性。它们不区分大小写。
Type Meaning
-------------- ---------------------------------------------------
Global International, global hierarchy
(e.g., the hierarchies comp, de, rec)
Regional Regional hierarchy
(e.g., the hierarchies ba, bln, tor)
Alt Alternative hierarchy, simpler rules for
creating a group, no formal structure
(e.g., the hierarchy alt)
Non-commercial Only for personal use; commercial use is prohibited
(e.g., the hierarchy de)
Commercial Commercial use permitted (e.g., the hierarchy biz)
Organization Hierarchy bound to an organization
(e.g., the hierarchy gnu)
-------------- ---------------------------------------------------
Type Meaning
-------------- ---------------------------------------------------
Global International, global hierarchy
(e.g., the hierarchies comp, de, rec)
Regional Regional hierarchy
(e.g., the hierarchies ba, bln, tor)
Alt Alternative hierarchy, simpler rules for
creating a group, no formal structure
(e.g., the hierarchy alt)
Non-commercial Only for personal use; commercial use is prohibited
(e.g., the hierarchy de)
Commercial Commercial use permitted (e.g., the hierarchy biz)
Organization Hierarchy bound to an organization
(e.g., the hierarchy gnu)
-------------- ---------------------------------------------------
PGP keys for Ctrl-PGP-Key and Mod-PGP-Key are transmitted in the following structure:
Ctrl PGP键和Mod PGP键的PGP键按以下结构传输：
PGP-answer = "V" SP Version CRLF "U" SP User-ID CRLF "B" SP Bits CRLF "I" SP Key-ID CRLF "F" SP Finger CRLF *("L" SP Location CRLF) *("K-" Keyblock CRLF) "K" SP Keyblock CRLF
PGP answer=“V”SP Version CRLF“U”SP用户ID CRLF“B”SP位CRLF“I”SP键ID CRLF“F”SP手指CRLF*（“L”SP位置CRLF）*（“K-“键块CRLF）”K”SP键块CRLF
Version = text User-ID = text Bits = text Key-ID = text Finger = text Location = text Keyblock = text
版本=文本用户ID=文本位=文本键ID=文本手指=文本位置=文本键块=文本
Key Name Mandatory Description
--- --------- --------- --------------------------------------
K Keyblock yes Public key block in ASCII armor format
[RFC2440]
V Version yes PGP-Version
U User-ID no Key user id
B Bits no Number of bits
I Key-ID no Key id, without leading "0x"
F Finger no Fingerprint
L Location no URL that points to the public key
--- --------- --------- --------------------------------------
Key Name Mandatory Description
--- --------- --------- --------------------------------------
K Keyblock yes Public key block in ASCII armor format
[RFC2440]
V Version yes PGP-Version
U User-ID no Key user id
B Bits no Number of bits
I Key-ID no Key id, without leading "0x"
F Finger no Fingerprint
L Location no URL that points to the public key
--- --------- --------- --------------------------------------
A hyphen following the code indicates that the block is continued on the next line. In the last message row, there MUST be white space after the code; this is also true for a single line code.
代码后面的连字符表示块在下一行继续。在最后一个消息行中，代码后必须有空格；对于单行代码也是如此。
Example
实例
<-- HIER de
--> 611 Data coming
Name: de
Status: Hierarchy
[...]
Ctl-PGP-Key:
U de.admin.news.announce
B 1024
I D3033C99
L http://www.dana.de.example/mod/pgp/dana.asc
L ftp://ftp.fu-berlin.de.example/unix/news/pgpcontrol/PGPKEYS.gz
F 5B B0 52 88 BF 55 19 4F 66 7D C2 AE 16 26 28 25
V 2.6.3ia
K------BEGIN PGP PUBLIC KEY BLOCK-----
K-Version: 2.6.3ia
K-
K-mQCNAzGeB/YAAAEEALZ+Xfm/WDCEMXM48gK1PlKG6TkV3SLbXt4CnzpGMtOM
K-HjlHaU6Xco5ijAuqM1wEGUHD5hw/BL/heR5Tq+C5IEyXQQmYwkrgeVFMO/rA
[...]
K-SDw+Id0JPFO9AWOiQgAAtN6zrYOhHFBp+68h9k674Yg9IHqj3BWdRjJF6PKo
K-VpvRovMz+lSOy9Zcsbs+5t8Pj9ZVAQyfxBkqD5A=
K-=Xwgc
K -----END PGP PUBLIC KEY BLOCK-----
[...]
<-- HIER de
--> 611 Data coming
Name: de
Status: Hierarchy
[...]
Ctl-PGP-Key:
U de.admin.news.announce
B 1024
I D3033C99
L http://www.dana.de.example/mod/pgp/dana.asc
L ftp://ftp.fu-berlin.de.example/unix/news/pgpcontrol/PGPKEYS.gz
F 5B B0 52 88 BF 55 19 4F 66 7D C2 AE 16 26 28 25
V 2.6.3ia
K------BEGIN PGP PUBLIC KEY BLOCK-----
K-Version: 2.6.3ia
K-
K-mQCNAzGeB/YAAAEEALZ+Xfm/WDCEMXM48gK1PlKG6TkV3SLbXt4CnzpGMtOM
K-HjlHaU6Xco5ijAuqM1wEGUHD5hw/BL/heR5Tq+C5IEyXQQmYwkrgeVFMO/rA
[...]
K-SDw+Id0JPFO9AWOiQgAAtN6zrYOhHFBp+68h9k674Yg9IHqj3BWdRjJF6PKo
K-VpvRovMz+lSOy9Zcsbs+5t8Pj9ZVAQyfxBkqD5A=
K-=Xwgc
K -----END PGP PUBLIC KEY BLOCK-----
[...]
.
.
UDP is intended for reading programs (news readers); it is not in the scope of this document. The use of UDP for NAS will be described in a separate paper.
UDP用于阅读程序（新闻阅读器）；它不在本文件的范围内。UDP在NAS中的使用将在另一篇文章中介绍。
The IANA has registered the application/nasdata media type as defined by the following information:
IANA已注册应用程序/nasdata媒体类型，定义如下：
Media type name: application Media subtype name: nasdata Required parameters: none Optional parameters: level
媒体类型名称：应用程序媒体子类型名称：nasdata必需参数：无可选参数：级别
The NAS protocol level number for the enclosed NAS data package. If not present, the protocol level defaults to 1.
随附NAS数据包的NAS协议级别号。如果不存在，则协议级别默认为1。
Encoding scheme: NAS data is plain text; no special encodings are needed.
编码方案：NAS数据为纯文本；不需要特殊编码。
Security considerations: see below
安全注意事项：见下文
Security issues are only addressed in respect to server-server communication in this protocol level. Username and password combinations in the GETA and GETP commands can be used to make sure that connections are only accepted from authorized clients. PGP keys according to [RFC2440] are used to sign NAS data in server-server communication in order to validate that the data is authentic and has not been tampered with.
安全问题仅针对此协议级别的服务器通信解决。GETA和GETP命令中的用户名和密码组合可用于确保只接受来自授权客户端的连接。根据[RFC2440]的PGP密钥用于在服务器通信中对NAS数据进行签名，以验证数据是否真实且未被篡改。
Every server does have the possibility (in both server-server and server-client communication) to deny some commands or the whole connection according to the client's IP number.
每个服务器都有可能（在服务器和服务器-客户端通信中）根据客户端的IP号拒绝某些命令或整个连接。
No mechanisms are defined in the current protocol level to allow a client to validate that it is talking to a legitimate server or that the data it receives is authentic.
当前协议级别中未定义任何机制，以允许客户端验证它是否正在与合法服务器通信，或者它接收的数据是否真实。
A stronger authentication scheme will be provided in a higher protocol level.
在更高的协议级别将提供更强的身份验证方案。
Code Description
---- --------------------------------------------------------------
100 Command overview, Information, command description (HELP)
101 Information about connection, client and server (INFO)
200 Greeting message (Connection Setup)
201 Termination of the connection (QUIT)
202 Returns current protocol level (VERS)
213 Valid data at the client side (GETP)
215 The client already has the current data (GETA)
300 Time in UTC (DATE)
302 Answer to a successful request (VERS)
400 Indicates that the server is not giving any information (INFO)
401 Permission denied (LIST, LSTR, HIER, DATA)
402 Requested level too high; falling back to lower level (VERS)
404 Server currently out of service (Connection Setup)
410 Indicates that the server is not giving any information (HELP)
411 No hierarchy with that name (GETP, GETA)
430 Permission denied (GETP, GETA)
434 Client has no permission to talk to server (Connection Setup)
510 Syntax error
511 Internal error (TIME)
513 Line too long
519 Unknown command
610 Regular answer with all requested data (LIST, LSTR)
611 Regular answer with all requested data (HIER)
612 Regular answer with all requested data (DATA)
613 hierarchy data (GETP)
615 Regular answer with all requested data (GETA)
---- --------------------------------------------------------------
Code Description
---- --------------------------------------------------------------
100 Command overview, Information, command description (HELP)
101 Information about connection, client and server (INFO)
200 Greeting message (Connection Setup)
201 Termination of the connection (QUIT)
202 Returns current protocol level (VERS)
213 Valid data at the client side (GETP)
215 The client already has the current data (GETA)
300 Time in UTC (DATE)
302 Answer to a successful request (VERS)
400 Indicates that the server is not giving any information (INFO)
401 Permission denied (LIST, LSTR, HIER, DATA)
402 Requested level too high; falling back to lower level (VERS)
404 Server currently out of service (Connection Setup)
410 Indicates that the server is not giving any information (HELP)
411 No hierarchy with that name (GETP, GETA)
430 Permission denied (GETP, GETA)
434 Client has no permission to talk to server (Connection Setup)
510 Syntax error
511 Internal error (TIME)
513 Line too long
519 Unknown command
610 Regular answer with all requested data (LIST, LSTR)
611 Regular answer with all requested data (HIER)
612 Regular answer with all requested data (DATA)
613 hierarchy data (GETP)
615 Regular answer with all requested data (GETA)
---- --------------------------------------------------------------
Header Mandatory Use Multiple Description
------------- --------- --- -------- ---------------------
Name yes H/N no Name of a hierarchy
or newsgroup (Start
of a new data block)
Status yes H/N no Status of hierarchy
or newsgroup
Serial no H/N no Revision of hierarchy
/newsgroup data
Followup no N no Group for followup
Description no H/N no Short description of
a hierarchy/newsgroup
Charter no H/N yes Charter-URL
Netiquette no H/N yes Netiquette-URL
Header Mandatory Use Multiple Description
------------- --------- --- -------- ---------------------
Name yes H/N no Name of a hierarchy
or newsgroup (Start
of a new data block)
Status yes H/N no Status of hierarchy
or newsgroup
Serial no H/N no Revision of hierarchy
/newsgroup data
Followup no N no Group for followup
Description no H/N no Short description of
a hierarchy/newsgroup
Charter no H/N yes Charter-URL
Netiquette no H/N yes Netiquette-URL
FAQ no N yes FAQ-URL
Rules no H yes Administration rules
URL
Ctl-Send-Adr no H yes Control email
Ctl-Newsgroup no H yes Control newsgroup
Mod-Wildcard no H no Moderator wildcard
Mod-Sub-Adr no N no Submission address
Mod-Adm-Adr no N yes Moderator's address
(email)
Mod-Group-Info no N yes Info-URL
Language no H/N yes Language
Charset no H/N yes Charset
Encoding no H/N yes Encoding
Newsgroup-Type no H/N yes Type of newsgroup
Hier-Type no H yes Type of hierarchy
Area no H yes Regional or
organizational area
Name-Length no H no Total length of group
names
Comp-Length no H no Component length of
group names
Article-Length no H no Article length
Date-Create no H/N no Date of creation
Date-Delete no H/N no Date of removal
Replacement no H/N yes Successor
Source no H yes Source of data
Ctl-PGP-Key no H yes Control PGP key
Mod-PGP-Key no N yes Moderator's PGP key
------------- --------- --- -------- ---------------------
FAQ no N yes FAQ-URL
Rules no H yes Administration rules
URL
Ctl-Send-Adr no H yes Control email
Ctl-Newsgroup no H yes Control newsgroup
Mod-Wildcard no H no Moderator wildcard
Mod-Sub-Adr no N no Submission address
Mod-Adm-Adr no N yes Moderator's address
(email)
Mod-Group-Info no N yes Info-URL
Language no H/N yes Language
Charset no H/N yes Charset
Encoding no H/N yes Encoding
Newsgroup-Type no H/N yes Type of newsgroup
Hier-Type no H yes Type of hierarchy
Area no H yes Regional or
organizational area
Name-Length no H no Total length of group
names
Comp-Length no H no Component length of
group names
Article-Length no H no Article length
Date-Create no H/N no Date of creation
Date-Delete no H/N no Date of removal
Replacement no H/N yes Successor
Source no H yes Source of data
Ctl-PGP-Key no H yes Control PGP key
Mod-PGP-Key no N yes Moderator's PGP key
------------- --------- --- -------- ---------------------
N: Newsgroup, H: Hierarchy
N:新闻组，H:层次结构
[IANA-CS] IANA: Character Sets, <http://www.iana.org/assignments/character-sets>.
[IANA-CS]IANA:字符集<http://www.iana.org/assignments/character-sets>.
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, November 1996.
[RFC2045]Freed，N.和N.Borenstein，“多用途Internet邮件扩展（MIME）第一部分：Internet邮件正文格式”，RFC 20451996年11月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2277] Alvestrand, H., "IETF Policy on Character Sets and Languages", BCP 18, RFC 2277, January 1998.
[RFC2277]Alvestrand，H.，“IETF字符集和语言政策”，BCP 18，RFC 2277，1998年1月。
[RFC2440] Callas, J., Donnerhacke, L., Finney, H., and R. Thayer, "OpenPGP Message Format", RFC 2440, November 1998.
[RFC2440]Callas，J.，Donnerhacke，L.，Finney，H.，和R.Thayer，“OpenPGP消息格式”，RFC 24401998年11月。
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[RFC2616]菲尔丁，R.，盖蒂斯，J.，莫卧儿，J.，弗莱斯蒂克，H.，马斯特，L.，利奇，P.，和T.伯纳斯李，“超文本传输协议——HTTP/1.1”，RFC 2616，1999年6月。
[RFC4234] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 4234, October 2005.
[RFC4234]Crocker，D.和P.Overell，“语法规范的扩充BNF:ABNF”，RFC 4234，2005年10月。
[IANA-MT] IANA: Media Types, <http://www.iana.org/assignments/>.
[IANA-MT]IANA：媒体类型<http://www.iana.org/assignments/>.
[IANA-PN] IANA: Assigned Port Numbers, <http://www.iana.org/assignments/port-numbers>.
[IANA-PN]IANA：分配的端口号<http://www.iana.org/assignments/port-numbers>.
[RFC1305] Mills, D., "Network Time Protocol", RFC 1305, University of Delaware, March 1992.
[RFC1305]米尔斯，D，“网络时间协议”，RFC 1305，德拉瓦大学，1992年3月。
[SON1036] H. Spencer, "News Article Format and Transmission", A Draft for an RFC 1036 Successor, <ftp://zoo.toronto.edu/pub/news.txt.Z>.
[SON1036]H.Spencer，“新闻文章格式和传输”，RFC 1036继任者的草案<ftp://zoo.toronto.edu/pub/news.txt.Z>.
[USEFOR] USEFOR Working Group, "News Article Format", Work in Progress.
[USEFOR]USEFOR工作组，“新闻文章格式”，正在进行中。
Acknowledgement
确认
This work has been supported by the German Academic Network Organization (DFN-Verein) with funds from the German Federal Ministry of Education and Research (Bundesministerium fuer Bildung und Forschung).
这项工作得到了德国学术网络组织（DFN Verein）的支持，资金来自德国联邦教育和研究部（Bundesministerium fuer Bildung und Forschung）。
Authors' Addresses
作者地址
Philipp Grau Vera Heinau Heiko Schlichting Robert Schuettler
菲利普·格拉·维拉·海诺·海科·施利什廷·罗伯特·舒特勒
Freie Universitaet Berlin ZEDAT Fabeckstr. 32 14195 Berlin Germany
柏林弗雷大学。3214195德国柏林
Phone: +49 30 838-74707
Fax: +49 30 838-56721
Phone: +49 30 838-74707
Fax: +49 30 838-56721
EMail: nas@fu-berlin.de
URL: http://nas.fu-berlin.de/
EMail: nas@fu-berlin.de
URL: http://nas.fu-berlin.de/
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 at www.rfc-editor.org/copyright.html, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78和www.rfc-editor.org/copyright.html中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
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）提供。