Network Working Group R. Thurlow
Request for Comments: 5531 Sun Microsystems
Obsoletes: 1831 May 2009
Category: Standards Track
Network Working Group R. Thurlow
Request for Comments: 5531 Sun Microsystems
Obsoletes: 1831 May 2009
Category: Standards Track
RPC: Remote Procedure Call Protocol Specification Version 2
RPC：远程过程调用协议规范版本2
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2009 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
本文件受BCP 78和IETF信托在本文件出版之日生效的与IETF文件有关的法律规定的约束(http://trustee.ietf.org/license-info). 请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。
Abstract
摘要
This document describes the Open Network Computing (ONC) Remote Procedure Call (RPC) version 2 protocol as it is currently deployed and accepted. This document obsoletes RFC 1831.
本文档描述了当前部署和接受的开放网络计算（ONC）远程过程调用（RPC）版本2协议。本文件废除了RFC 1831。
Table of Contents
目录
1. Introduction ....................................................3
1.1. Requirements Language ......................................3
2. Changes since RFC 1831 ..........................................3
3. Terminology .....................................................3
4. The RPC Model ...................................................4
5. Transports and Semantics ........................................5
6. Binding and Rendezvous Independence .............................7
7. Authentication ..................................................7
8. RPC Protocol Requirements .......................................7
8.1. RPC Programs and Procedures ................................8
8.2. Authentication, Integrity, and Privacy .....................9
8.3. Program Number Assignment .................................10
8.4. Other Uses of the RPC Protocol ............................10
8.4.1. Batching ...........................................10
8.4.2. Broadcast Remote Procedure Calls ...................11
9. The RPC Message Protocol .......................................11
10. Authentication Protocols ......................................15
10.1. Null Authentication ......................................15
11. Record Marking Standard .......................................16
12. The RPC Language ..............................................16
12.1. An Example Service Described in the RPC Language .........17
12.2. The RPC Language Specification ...........................18
12.3. Syntax Notes .............................................18
13. IANA Considerations ...........................................19
13.1. Numbering Requests to IANA ...............................19
13.2. Protecting Past Assignments ..............................19
13.3. RPC Number Assignment ....................................19
13.3.1. To be assigned by IANA ............................20
13.3.2. Defined by Local Administrator ....................20
13.3.3. Transient Block ...................................20
13.3.4. Reserved Block ....................................21
13.3.5. RPC Number Sub-Blocks .............................21
13.4. RPC Authentication Flavor Number Assignment ..............22
13.4.1. Assignment Policy .................................22
13.4.2. Auth Flavors vs. Pseudo-Flavors ...................23
13.5. Authentication Status Number Assignment ..................23
13.5.1. Assignment Policy .................................23
14. Security Considerations .......................................24
Appendix A: System Authentication .................................25
Appendix B: Requesting RPC-Related Numbers from IANA .............26
Appendix C: Current Number Assignments ...........................27
Normative References .............................................62
Informative References ...........................................62
1. Introduction ....................................................3
1.1. Requirements Language ......................................3
2. Changes since RFC 1831 ..........................................3
3. Terminology .....................................................3
4. The RPC Model ...................................................4
5. Transports and Semantics ........................................5
6. Binding and Rendezvous Independence .............................7
7. Authentication ..................................................7
8. RPC Protocol Requirements .......................................7
8.1. RPC Programs and Procedures ................................8
8.2. Authentication, Integrity, and Privacy .....................9
8.3. Program Number Assignment .................................10
8.4. Other Uses of the RPC Protocol ............................10
8.4.1. Batching ...........................................10
8.4.2. Broadcast Remote Procedure Calls ...................11
9. The RPC Message Protocol .......................................11
10. Authentication Protocols ......................................15
10.1. Null Authentication ......................................15
11. Record Marking Standard .......................................16
12. The RPC Language ..............................................16
12.1. An Example Service Described in the RPC Language .........17
12.2. The RPC Language Specification ...........................18
12.3. Syntax Notes .............................................18
13. IANA Considerations ...........................................19
13.1. Numbering Requests to IANA ...............................19
13.2. Protecting Past Assignments ..............................19
13.3. RPC Number Assignment ....................................19
13.3.1. To be assigned by IANA ............................20
13.3.2. Defined by Local Administrator ....................20
13.3.3. Transient Block ...................................20
13.3.4. Reserved Block ....................................21
13.3.5. RPC Number Sub-Blocks .............................21
13.4. RPC Authentication Flavor Number Assignment ..............22
13.4.1. Assignment Policy .................................22
13.4.2. Auth Flavors vs. Pseudo-Flavors ...................23
13.5. Authentication Status Number Assignment ..................23
13.5.1. Assignment Policy .................................23
14. Security Considerations .......................................24
Appendix A: System Authentication .................................25
Appendix B: Requesting RPC-Related Numbers from IANA .............26
Appendix C: Current Number Assignments ...........................27
Normative References .............................................62
Informative References ...........................................62
This document specifies version 2 of the message protocol used in ONC Remote Procedure Call (RPC). The message protocol is specified with the eXternal Data Representation (XDR) language [RFC4506]. This document assumes that the reader is familiar with XDR. It does not attempt to justify remote procedure call systems or describe their use. The paper by Birrell and Nelson [XRPC] is recommended as an excellent background for the remote procedure call concept.
本文档指定了ONC远程过程调用（RPC）中使用的消息协议的版本2。使用外部数据表示（XDR）语言[RFC4506]指定消息协议。本文档假定读者熟悉XDR。它不试图证明远程过程调用系统的合理性或描述它们的使用。Birrell和Nelson[XRPC]的论文被推荐为远程过程调用概念的优秀背景。
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]中所述进行解释。
This document obsoletes [RFC1831] as the authoritative document describing RPC, without introducing any over-the-wire protocol changes. The main changes from RFC 1831 are:
本文件废除了[RFC1831]作为描述RPC的权威性文件，没有引入任何在线协议更改。RFC 1831的主要变化是：
o Addition of an Appendix that describes how an implementor can request new RPC program numbers, authentication flavor numbers, and authentication status numbers from IANA, rather than from Sun Microsystems
o 添加了一个附录，该附录描述了实现者如何从IANA而不是Sun Microsystems请求新的RPC程序号、身份验证风格号和身份验证状态号
o Addition of an "IANA Considerations" section that describes past number assignment policy and how IANA is intended to assign them in the future
o 增加了“IANA注意事项”部分，该部分描述了过去的号码分配政策以及IANA将来打算如何分配号码
o Clarification of the RPC Language Specification to match current usage
o 说明RPC语言规范以匹配当前使用
o Enhancement of the "Security Considerations" section to reflect experience with strong security flavors
o 增强“安全注意事项”部分，以反映具有强烈安全风格的经验
o Specification of new authentication errors that are in common use in modern RPC implementations
o 现代RPC实现中常用的新身份验证错误规范
o Updates for the latest IETF intellectual property statements
o 最新IETF知识产权声明的更新
This document discusses clients, calls, servers, replies, services, programs, procedures, and versions. Each remote procedure call has two sides: an active client side that makes the call to a server side, which sends back a reply. A network service is a collection of
本文档讨论客户端、呼叫、服务器、回复、服务、程序、过程和版本。每个远程过程调用都有两个方面：一个活动的客户端向服务器端发出调用，服务器端发回应答。网络服务是
one or more remote programs. A remote program implements one or more remote procedures; the procedures, their parameters, and results are documented in the specific program's protocol specification. A server may support more than one version of a remote program in order to be compatible with changing protocols.
一个或多个远程程序。远程程序实现一个或多个远程过程；程序、参数和结果记录在特定程序的协议规范中。为了与不断变化的协议兼容，服务器可以支持远程程序的多个版本。
For example, a network file service may be composed of two programs. One program may deal with high-level applications such as file system access control and locking. The other may deal with low-level file input and output and have procedures like "read" and "write". A client of the network file service would call the procedures associated with the two programs of the service on behalf of the client.
例如，网络文件服务可以由两个程序组成。一个程序可以处理高级应用程序，如文件系统访问控制和锁定。另一个可以处理低级文件输入和输出，并具有“读取”和“写入”等过程。网络文件服务的客户端将代表客户端调用与该服务的两个程序相关联的过程。
The terms "client" and "server" only apply to a particular transaction; a particular hardware entity (host) or software entity (process or program) could operate in both roles at different times. For example, a program that supplies remote execution service could also be a client of a network file service.
术语“客户机”和“服务器”仅适用于特定交易；特定的硬件实体（主机）或软件实体（进程或程序）可以在不同的时间以两种角色运行。例如，提供远程执行服务的程序也可以是网络文件服务的客户端。
The ONC RPC protocol is based on the remote procedure call model, which is similar to the local procedure call model. In the local case, the caller places arguments to a procedure in some well-specified location (such as a register window). It then transfers control to the procedure, and eventually regains control. At that point, the results of the procedure are extracted from the well-specified location, and the caller continues execution.
ONC-RPC协议基于远程过程调用模型，与本地过程调用模型类似。在本地情况下，调用方将过程的参数放置在指定的位置（如寄存器窗口）。然后，它将控制权转移到过程，并最终重新获得控制权。此时，将从指定的位置提取过程的结果，调用方继续执行。
The remote procedure call model is similar. One thread of control logically winds through two processes: the caller's process and a server's process. The caller first sends a call message to the server process and waits (blocks) for a reply message. The call message includes the procedure's parameters, and the reply message includes the procedure's results. Once the reply message is received, the results of the procedure are extracted, and the caller's execution is resumed.
远程过程调用模型与此类似。一个控制线程逻辑上通过两个进程：调用方进程和服务器进程。调用者首先向服务器进程发送一条呼叫消息，并等待（阻塞）回复消息。调用消息包括过程的参数，应答消息包括过程的结果。收到回复消息后，将提取过程的结果，并恢复调用方的执行。
On the server side, a process is dormant awaiting the arrival of a call message. When one arrives, the server process extracts the procedure's parameters, computes the results, sends a reply message, and then awaits the next call message.
在服务器端，进程处于休眠状态，等待调用消息的到来。当到达时，服务器进程提取过程参数，计算结果，发送回复消息，然后等待下一个调用消息。
In this model, only one of the two processes is active at any given time. However, this model is only given as an example. The ONC RPC protocol makes no restrictions on the concurrency model implemented, and others are possible. For example, an implementation may choose
在该模型中，在任何给定时间，两个进程中只有一个处于活动状态。然而，该模型仅作为示例给出。ONC-RPC协议对实现的并发模型没有任何限制，其他的也是可能的。例如，一个实现可以选择
to have RPC calls be asynchronous so that the client may do useful work while waiting for the reply from the server. Another possibility is to have the server create a separate task to process an incoming call so that the original server can be free to receive other requests.
使RPC调用是异步的，以便客户端在等待服务器的答复时可以执行有用的工作。另一种可能是让服务器创建一个单独的任务来处理传入呼叫，以便原始服务器可以自由接收其他请求。
There are a few important ways in which remote procedure calls differ from local procedure calls.
远程过程调用与本地过程调用之间存在一些重要的区别。
o Error handling: failures of the remote server or network must be handled when using remote procedure calls.
o 错误处理：使用远程过程调用时，必须处理远程服务器或网络的故障。
o Global variables and side effects: since the server does not have access to the client's address space, hidden arguments cannot be passed as global variables or returned as side effects.
o 全局变量和副作用：由于服务器无权访问客户机的地址空间，因此无法将隐藏参数作为全局变量传递或作为副作用返回。
o Performance: remote procedures usually operate at one or more orders of magnitude slower than local procedure calls.
o 性能：远程过程的运行速度通常比本地过程调用慢一个或多个数量级。
o Authentication: since remote procedure calls can be transported over unsecured networks, authentication may be necessary. Authentication prevents one entity from masquerading as some other entity.
o 身份验证：由于远程过程调用可以通过不安全的网络传输，因此可能需要身份验证。身份验证防止一个实体伪装成其他实体。
The conclusion is that even though there are tools to automatically generate client and server libraries for a given service, protocols must still be designed carefully.
结论是，即使有工具可以为给定的服务自动生成客户机和服务器库，协议仍然必须仔细设计。
The RPC protocol can be implemented on several different transport protocols. The scope of the definition of the RPC protocol excludes how a message is passed from one process to another, and includes only the specification and interpretation of messages. However, the application may wish to obtain information about (and perhaps control over) the transport layer through an interface not specified in this document. For example, the transport protocol may impose a restriction on the maximum size of RPC messages, or it may be stream-oriented like TCP [RFC0793] with no size limit. The client and server must agree on their transport protocol choices.
RPC协议可以在几种不同的传输协议上实现。RPC协议定义的范围不包括消息如何从一个进程传递到另一个进程，只包括消息的规范和解释。然而，应用程序可能希望通过本文档中未指定的接口获得关于传输层的信息（并且可能控制传输层）。例如，传输协议可以对RPC消息的最大大小施加限制，或者它可以像TCP[RFC0793]一样面向流，没有大小限制。客户端和服务器必须就其传输协议选择达成一致。
It is important to point out that RPC does not try to implement any kind of reliability and that the application may need to be aware of the type of transport protocol underneath RPC. If it knows it is running on top of a reliable transport such as TCP, then most of the work is already done for it. On the other hand, if it is running on
需要指出的是，RPC并不试图实现任何类型的可靠性，应用程序可能需要知道RPC下面的传输协议类型。如果它知道它是在可靠的传输（如TCP）上运行的，那么大部分工作已经完成。另一方面，如果它正在运行
top of an unreliable transport such as UDP [RFC0768], it must implement its own time-out, retransmission, and duplicate detection policies as the RPC protocol does not provide these services.
除了UDP[RFC0768]等不可靠传输之外，它还必须实现自己的超时、重传和重复检测策略，因为RPC协议不提供这些服务。
Because of transport independence, the RPC protocol does not attach specific semantics to the remote procedures or their execution requirements. Semantics can be inferred from (but should be explicitly specified by) the underlying transport protocol. For example, consider RPC running on top of an unreliable transport such as UDP. If an application retransmits RPC call messages after time-outs, and does not receive a reply, it cannot infer anything about the number of times the procedure was executed. If it does receive a reply, then it can infer that the procedure was executed at least once.
由于传输独立性，RPC协议不会将特定语义附加到远程过程或其执行要求。语义可以从底层传输协议推断（但应明确指定）。例如，考虑在不可靠传输（如UDP）之上运行的RPC。如果应用程序在超时后重新传输RPC调用消息，并且没有收到回复，则无法推断该过程的执行次数。如果它确实收到回复，则可以推断该过程至少执行了一次。
A server may wish to remember previously granted requests from a client and not regrant them, in order to insure some degree of execute-at-most-once semantics. A server can do this by taking advantage of the transaction ID that is packaged with every RPC message. The main use of this transaction ID is by the client RPC entity in matching replies to calls. However, a client application may choose to reuse its previous transaction ID when retransmitting a call. The server may choose to remember this ID after executing a call and not execute calls with the same ID, in order to achieve some degree of execute-at-most-once semantics. The server is not allowed to examine this ID in any other way except as a test for equality.
服务器可能希望记住来自客户机的先前授予的请求，而不是对它们进行重新分配，以确保某种程度的最多执行一次语义。服务器可以通过利用每个RPC消息打包的事务ID来实现这一点。此事务ID的主要用途是由客户端RPC实体在匹配对调用的响应时使用。但是，客户端应用程序在重新传输调用时可以选择重用其以前的事务ID。服务器可以选择在执行调用后记住该ID，而不是使用相同ID执行调用，以实现某种程度的最多执行一次语义。服务器不允许以任何其他方式检查此ID，除非作为平等性测试。
On the other hand, if using a "reliable" transport such as TCP, the application can infer from a reply message that the procedure was executed exactly once, but if it receives no reply message, it cannot assume that the remote procedure was not executed. Note that even if a connection-oriented protocol like TCP is used, an application still needs time-outs and reconnections to handle server crashes.
另一方面，如果使用“可靠”传输（如TCP），则应用程序可以从回复消息推断该过程只执行了一次，但如果未收到回复消息，则无法假定远程过程未执行。请注意，即使使用了面向连接的协议（如TCP），应用程序仍然需要超时和重新连接来处理服务器崩溃。
There are other possibilities for transports besides datagram- or connection-oriented protocols. For example, a request-reply protocol such as [VMTP] is perhaps a natural transport for RPC. ONC RPC currently uses both TCP and UDP transport protocols. Section 11 ("Record Marking Standard") describes the mechanism employed by ONC RPC to utilize a connection-oriented, stream-oriented transport such as TCP. The mechanism by which future transports having different structural characteristics should be used to transfer ONC RPC messages should be specified by means of a Standards Track RFC, once such additional transports are defined.
除了面向数据报或连接的协议之外，还有其他传输的可能性。例如，像[VMTP]这样的请求-应答协议可能是RPC的自然传输。ONC RPC当前使用TCP和UDP传输协议。第11节（“记录标记标准”）描述了ONC RPC利用面向连接、面向流的传输（如TCP）所采用的机制。一旦定义了此类附加传输，应通过标准跟踪RFC指定具有不同结构特征的未来传输用于传输ONC RPC消息的机制。
The act of binding a particular client to a particular service and transport parameters is NOT part of this RPC protocol specification. This important and necessary function is left up to some higher-level software.
将特定客户端绑定到特定服务和传输参数的行为不属于此RPC协议规范的一部分。这个重要而必要的功能留给一些更高级别的软件来完成。
Implementors could think of the RPC protocol as the jump-subroutine instruction (JSR) of a network; the loader (binder) makes JSR useful, and the loader itself uses JSR to accomplish its task. Likewise, the binding software makes RPC useful, possibly using RPC to accomplish this task.
实现者可以将RPC协议视为网络的跳转子例程指令（JSR）；加载器（绑定器）使JSR变得有用，加载器本身使用JSR来完成其任务。同样，绑定软件使RPC变得有用，可能使用RPC来完成此任务。
The RPC protocol provides the fields necessary for a client to identify itself to a service, and vice-versa, in each call and reply message. Security and access control mechanisms can be built on top of this message authentication. Several different authentication protocols can be supported. A field in the RPC header indicates which protocol is being used. More information on specific authentication protocols is in Section 8.2, "Authentication, Integrity and Privacy".
RPC协议在每个调用和应答消息中提供客户端向服务标识自身所需的字段，反之亦然。安全和访问控制机制可以建立在该消息身份验证之上。可以支持几种不同的身份验证协议。RPC标头中的字段指示正在使用的协议。有关特定认证协议的更多信息，请参见第8.2节“认证、完整性和隐私”。
The RPC protocol must provide for the following:
RPC协议必须提供以下功能：
o Unique specification of a procedure to be called
o 要调用的过程的唯一规范
o Provisions for matching response messages to request messages
o 将响应消息与请求消息匹配的规定
o Provisions for authenticating the caller to service and vice-versa
o 验证呼叫者服务和呼叫者服务的规定
Besides these requirements, features that detect the following are worth supporting because of protocol roll-over errors, implementation bugs, user error, and network administration:
除了这些要求之外，由于协议滚动错误、实现错误、用户错误和网络管理，检测以下内容的功能也值得支持：
o RPC protocol mismatches
o RPC协议不匹配
o Remote program protocol version mismatches
o 远程程序协议版本不匹配
o Protocol errors (such as misspecification of a procedure's parameters)
o 协议错误（例如错误指定过程参数）
o Reasons why remote authentication failed
o 远程身份验证失败的原因
o Any other reasons why the desired procedure was not called
o 未调用所需过程的任何其他原因
The RPC call message has three unsigned-integer fields -- remote program number, remote program version number, and remote procedure number -- that uniquely identify the procedure to be called. Program numbers are administered by a central authority (IANA). Once implementors have a program number, they can implement their remote program; the first implementation would most likely have the version number 1 but MUST NOT be the number zero. Because most new protocols evolve, a "version" field of the call message identifies which version of the protocol the caller is using. Version numbers enable support of both old and new protocols through the same server process.
RPC调用消息有三个无符号整数字段——远程程序号、远程程序版本号和远程过程号——它们唯一地标识要调用的过程。项目编号由中央管理局（IANA）管理。一旦实现者有了程序编号，他们就可以实现他们的远程程序；第一个实现很可能具有版本号1，但不能为零。由于大多数新协议不断发展，调用消息的“版本”字段会标识调用方正在使用的协议版本。版本号支持通过同一服务器进程支持新旧协议。
The procedure number identifies the procedure to be called. These numbers are documented in the specific program's protocol specification. For example, a file service's protocol specification may state that its procedure number 5 is "read" and procedure number 12 is "write".
过程编号标识要调用的过程。这些编号记录在特定程序的协议规范中。例如，文件服务的协议规范可以声明其过程编号5为“读取”，过程编号12为“写入”。
Just as remote program protocols may change over several versions, the actual RPC message protocol could also change. Therefore, the call message also has in it the RPC version number, which is always equal to 2 for the version of RPC described here.
正如远程程序协议可能在多个版本中发生变化一样，实际的RPC消息协议也可能发生变化。因此，调用消息中还包含RPC版本号，对于此处描述的RPC版本，该版本号始终等于2。
The reply message to a request message has enough information to distinguish the following error conditions:
请求消息的回复消息具有足够的信息来区分以下错误情况：
o The remote implementation of RPC does not support protocol version 2. The lowest and highest supported RPC version numbers are returned.
o RPC的远程实现不支持协议版本2。返回支持的最低和最高RPC版本号。
o The remote program is not available on the remote system.
o 远程程序在远程系统上不可用。
o The remote program does not support the requested version number. The lowest and highest supported remote program version numbers are returned.
o 远程程序不支持请求的版本号。返回支持的最低和最高远程程序版本号。
o The requested procedure number does not exist. (This is usually a client-side protocol or programming error.)
o 请求的过程编号不存在。（这通常是客户端协议或编程错误。）
o The parameters to the remote procedure appear to be garbage from the server's point of view. (Again, this is usually caused by a disagreement about the protocol between client and service.)
o 从服务器的角度来看，远程过程的参数似乎是垃圾。（同样，这通常是由于客户机和服务之间的协议不一致造成的。）
Provisions for authentication of caller to service and vice-versa are provided as a part of the RPC protocol. The call message has two authentication fields: the credential and the verifier. The reply message has one authentication field: the response verifier. The RPC protocol specification defines all three fields to be the following opaque type (in the eXternal Data Representation (XDR) language [RFC4506]):
作为RPC协议的一部分，提供了调用方到服务的身份验证规定，反之亦然。呼叫消息有两个身份验证字段：凭证和验证器。回复消息有一个身份验证字段：响应验证器。RPC协议规范将所有三个字段定义为以下不透明类型（在外部数据表示（XDR）语言[RFC4506]中）：
enum auth_flavor {
AUTH_NONE = 0,
AUTH_SYS = 1,
AUTH_SHORT = 2,
AUTH_DH = 3,
RPCSEC_GSS = 6
/* and more to be defined */
};
enum auth_flavor {
AUTH_NONE = 0,
AUTH_SYS = 1,
AUTH_SHORT = 2,
AUTH_DH = 3,
RPCSEC_GSS = 6
/* and more to be defined */
};
struct opaque_auth {
auth_flavor flavor;
opaque body<400>;
};
struct opaque_auth {
auth_flavor flavor;
opaque body<400>;
};
In other words, any "opaque_auth" structure is an "auth_flavor" enumeration followed by up to 400 bytes that are opaque to (uninterpreted by) the RPC protocol implementation.
换句话说，任何“不透明的auth”结构都是一个“auth\u风格”枚举，后跟对RPC协议实现不透明（未解释）的400字节。
The interpretation and semantics of the data contained within the authentication fields are specified by individual, independent authentication protocol specifications.
身份验证字段中包含的数据的解释和语义由独立的身份验证协议规范指定。
If authentication parameters were rejected, the reply message contains information stating why they were rejected.
如果身份验证参数被拒绝，则回复消息将包含说明拒绝原因的信息。
As demonstrated by RPCSEC_GSS, it is possible for an "auth_flavor" to also support integrity and privacy.
正如RPCSEC_GSS所展示的，“auth_风格”也可以支持完整性和隐私。
Program numbers are given out in groups according to the following chart:
根据下表分组给出程序编号：
0x00000000 Reserved 0x00000001 - 0x1fffffff To be assigned by IANA 0x20000000 - 0x3fffffff Defined by local administrator (some blocks assigned here) 0x40000000 - 0x5fffffff Transient 0x60000000 - 0x7effffff Reserved 0x7f000000 - 0x7fffffff Assignment outstanding 0x80000000 - 0xffffffff Reserved
0x00000000保留0x00000001-0x1FFFFFF由IANA分配0x20000000-0x3fffffff由本地管理员定义（此处分配的某些块）0x40000000-0x5fffffff瞬态0x60000000-0x7FFFFFF保留0x7f000000-0x7FFFFFFFFF分配未完成0x8000000-0xffffffff保留
The first group is a range of numbers administered by IANA and should be identical for all sites. The second range is for applications peculiar to a particular site. This range is intended primarily for debugging new programs. When a site develops an application that might be of general interest, that application should be given an assigned number in the first range. Application developers may apply for blocks of RPC program numbers in the first range by methods described in Appendix B. The third group is for applications that generate program numbers dynamically. The final groups are reserved for future use, and should not be used.
第一组是IANA管理的一系列数字，所有站点的数字应相同。第二个范围适用于特定站点特有的应用程序。此范围主要用于调试新程序。当一个站点开发一个可能引起普遍关注的应用程序时，应该在第一个范围内为该应用程序分配一个编号。应用程序开发人员可以通过附录B中描述的方法申请第一个范围内的RPC程序编号块。第三组用于动态生成程序编号的应用程序。最后一组保留供将来使用，不应使用。
The intended use of this protocol is for calling remote procedures. Normally, each call message is matched with a reply message. However, the protocol itself is a message-passing protocol with which other (non-procedure-call) protocols can be implemented.
此协议的预期用途是调用远程过程。通常，每个呼叫消息都与应答消息相匹配。然而，该协议本身是一个消息传递协议，其他（非过程调用）协议可以通过它来实现。
Batching is useful when a client wishes to send an arbitrarily large sequence of call messages to a server. Batching typically uses reliable byte stream protocols (like TCP) for its transport. In the case of batching, the client never waits for a reply from the server, and the server does not send replies to batch calls. A sequence of batch calls is usually terminated by a legitimate remote procedure call operation in order to flush the pipeline and get positive acknowledgement.
当客户端希望向服务器发送任意大的调用消息序列时，批处理非常有用。批处理通常使用可靠的字节流协议（如TCP）进行传输。在批处理的情况下，客户机从不等待服务器的回复，服务器也不发送对批处理调用的回复。批处理调用序列通常由合法的远程过程调用操作终止，以便刷新管道并获得肯定的确认。
In broadcast protocols, the client sends a broadcast call to the network and waits for numerous replies. This requires the use of packet-based protocols (like UDP) as its transport protocol. Servers that support broadcast protocols usually respond only when the call is successfully processed and are silent in the face of errors, but this varies with the application.
在广播协议中，客户端向网络发送广播呼叫，并等待大量回复。这需要使用基于数据包的协议（如UDP）作为其传输协议。支持广播协议的服务器通常仅在呼叫成功处理时响应，并且在遇到错误时保持沉默，但这随应用程序而异。
The principles of broadcast RPC also apply to multicasting -- an RPC request can be sent to a multicast address.
广播RPC的原理也适用于多播——RPC请求可以发送到多播地址。
This section defines the RPC message protocol in the XDR data description language [RFC4506].
本节使用XDR数据描述语言[RFC4506]定义RPC消息协议。
enum msg_type {
CALL = 0,
REPLY = 1
};
enum msg_type {
CALL = 0,
REPLY = 1
};
A reply to a call message can take on two forms: the message was either accepted or rejected.
对呼叫消息的回复可以采取两种形式：消息被接受或拒绝。
enum reply_stat {
MSG_ACCEPTED = 0,
MSG_DENIED = 1
};
enum reply_stat {
MSG_ACCEPTED = 0,
MSG_DENIED = 1
};
Given that a call message was accepted, the following is the status of an attempt to call a remote procedure.
假设接受了调用消息，下面是尝试调用远程过程的状态。
enum accept_stat {
SUCCESS = 0, /* RPC executed successfully */
PROG_UNAVAIL = 1, /* remote hasn't exported program */
PROG_MISMATCH = 2, /* remote can't support version # */
PROC_UNAVAIL = 3, /* program can't support procedure */
GARBAGE_ARGS = 4, /* procedure can't decode params */
SYSTEM_ERR = 5 /* e.g. memory allocation failure */
};
enum accept_stat {
SUCCESS = 0, /* RPC executed successfully */
PROG_UNAVAIL = 1, /* remote hasn't exported program */
PROG_MISMATCH = 2, /* remote can't support version # */
PROC_UNAVAIL = 3, /* program can't support procedure */
GARBAGE_ARGS = 4, /* procedure can't decode params */
SYSTEM_ERR = 5 /* e.g. memory allocation failure */
};
Reasons why a call message was rejected:
呼叫消息被拒绝的原因：
enum reject_stat {
RPC_MISMATCH = 0, /* RPC version number != 2 */
AUTH_ERROR = 1 /* remote can't authenticate caller */
};
enum reject_stat {
RPC_MISMATCH = 0, /* RPC version number != 2 */
AUTH_ERROR = 1 /* remote can't authenticate caller */
};
Why authentication failed:
身份验证失败的原因：
enum auth_stat {
AUTH_OK = 0, /* success */
/*
* failed at remote end
*/
AUTH_BADCRED = 1, /* bad credential (seal broken) */
AUTH_REJECTEDCRED = 2, /* client must begin new session */
AUTH_BADVERF = 3, /* bad verifier (seal broken) */
AUTH_REJECTEDVERF = 4, /* verifier expired or replayed */
AUTH_TOOWEAK = 5, /* rejected for security reasons */
/*
* failed locally
*/
AUTH_INVALIDRESP = 6, /* bogus response verifier */
AUTH_FAILED = 7, /* reason unknown */
/*
* AUTH_KERB errors; deprecated. See [RFC2695]
*/
AUTH_KERB_GENERIC = 8, /* kerberos generic error */
AUTH_TIMEEXPIRE = 9, /* time of credential expired */
AUTH_TKT_FILE = 10, /* problem with ticket file */
AUTH_DECODE = 11, /* can't decode authenticator */
AUTH_NET_ADDR = 12, /* wrong net address in ticket */
/*
* RPCSEC_GSS GSS related errors
*/
RPCSEC_GSS_CREDPROBLEM = 13, /* no credentials for user */
RPCSEC_GSS_CTXPROBLEM = 14 /* problem with context */
};
enum auth_stat {
AUTH_OK = 0, /* success */
/*
* failed at remote end
*/
AUTH_BADCRED = 1, /* bad credential (seal broken) */
AUTH_REJECTEDCRED = 2, /* client must begin new session */
AUTH_BADVERF = 3, /* bad verifier (seal broken) */
AUTH_REJECTEDVERF = 4, /* verifier expired or replayed */
AUTH_TOOWEAK = 5, /* rejected for security reasons */
/*
* failed locally
*/
AUTH_INVALIDRESP = 6, /* bogus response verifier */
AUTH_FAILED = 7, /* reason unknown */
/*
* AUTH_KERB errors; deprecated. See [RFC2695]
*/
AUTH_KERB_GENERIC = 8, /* kerberos generic error */
AUTH_TIMEEXPIRE = 9, /* time of credential expired */
AUTH_TKT_FILE = 10, /* problem with ticket file */
AUTH_DECODE = 11, /* can't decode authenticator */
AUTH_NET_ADDR = 12, /* wrong net address in ticket */
/*
* RPCSEC_GSS GSS related errors
*/
RPCSEC_GSS_CREDPROBLEM = 13, /* no credentials for user */
RPCSEC_GSS_CTXPROBLEM = 14 /* problem with context */
};
As new authentication mechanisms are added, there may be a need for more status codes to support them. IANA will hand out new auth_stat numbers on a simple First Come First Served basis as defined in the "IANA Considerations" and Appendix B.
随着新的身份验证机制的添加，可能需要更多的状态代码来支持它们。IANA将按照“IANA注意事项”和附录B中的定义，以简单的先到先得的方式发放新的认证统计号。
The RPC message:
RPC消息：
All messages start with a transaction identifier, xid, followed by a two-armed discriminated union. The union's discriminant is a msg_type that switches to one of the two types of the message. The xid of a REPLY message always matches that of the initiating CALL message. NB: The "xid" field is only used for clients matching reply messages with call messages or for servers detecting retransmissions; the service side cannot treat this id as any type of sequence number.
所有消息都以事务标识符xid开头，后面是一个两臂歧视联合。工会的判别式是一种msg_类型，可切换到两种消息类型之一。回复消息的xid始终与发起呼叫消息的xid匹配。注意：“xid”字段仅用于将应答消息与呼叫消息匹配的客户端或用于检测重传的服务器；服务方不能将此id视为任何类型的序列号。
struct rpc_msg {
unsigned int xid;
union switch (msg_type mtype) {
case CALL:
call_body cbody;
case REPLY:
reply_body rbody;
} body;
};
struct rpc_msg {
unsigned int xid;
union switch (msg_type mtype) {
case CALL:
call_body cbody;
case REPLY:
reply_body rbody;
} body;
};
Body of an RPC call:
RPC调用的主体：
In version 2 of the RPC protocol specification, rpcvers MUST be equal to 2. The fields "prog", "vers", and "proc" specify the remote program, its version number, and the procedure within the remote program to be called. After these fields are two authentication parameters: cred (authentication credential) and verf (authentication verifier). The two authentication parameters are followed by the parameters to the remote procedure, which are specified by the specific program protocol.
在RPC协议规范的版本2中，rpcvers必须等于2。字段“prog”、“vers”和“proc”指定远程程序、其版本号以及要调用的远程程序中的过程。在这些字段之后是两个身份验证参数：cred（身份验证凭据）和verf（身份验证验证器）。这两个身份验证参数之后是远程过程的参数，这些参数由特定的程序协议指定。
The purpose of the authentication verifier is to validate the authentication credential. Note that these two items are historically separate, but are always used together as one logical entity.
身份验证验证器的目的是验证身份验证凭据。请注意，这两项在历史上是分开的，但始终作为一个逻辑实体一起使用。
struct call_body {
unsigned int rpcvers; /* must be equal to two (2) */
unsigned int prog;
unsigned int vers;
unsigned int proc;
opaque_auth cred;
opaque_auth verf;
/* procedure-specific parameters start here */
};
struct call_body {
unsigned int rpcvers; /* must be equal to two (2) */
unsigned int prog;
unsigned int vers;
unsigned int proc;
opaque_auth cred;
opaque_auth verf;
/* procedure-specific parameters start here */
};
Body of a reply to an RPC call:
RPC调用的答复正文：
union reply_body switch (reply_stat stat) {
case MSG_ACCEPTED:
accepted_reply areply;
case MSG_DENIED:
rejected_reply rreply;
} reply;
union reply_body switch (reply_stat stat) {
case MSG_ACCEPTED:
accepted_reply areply;
case MSG_DENIED:
rejected_reply rreply;
} reply;
Reply to an RPC call that was accepted by the server:
答复服务器接受的RPC调用：
There could be an error even though the call was accepted. The first field is an authentication verifier that the server generates in order to validate itself to the client. It is followed by a union whose discriminant is an enum accept_stat. The SUCCESS arm of the union is protocol-specific. The PROG_UNAVAIL, PROC_UNAVAIL, GARBAGE_ARGS, and SYSTEM_ERR arms of the union are void. The PROG_MISMATCH arm specifies the lowest and highest version numbers of the remote program supported by the server.
即使呼叫已被接受，也可能出现错误。第一个字段是服务器生成的身份验证程序，用于向客户端验证自身。它后面是一个联合，其判别式是enum accept_stat。联合的成功部分是协议特定的。联盟的程序无效、程序无效、垃圾无效和系统错误武器无效。PROG_arm指定服务器支持的远程程序的最低和最高版本号。
struct accepted_reply {
opaque_auth verf;
union switch (accept_stat stat) {
case SUCCESS:
opaque results[0];
/*
* procedure-specific results start here
*/
case PROG_MISMATCH:
struct {
unsigned int low;
unsigned int high;
} mismatch_info;
default:
/*
* Void. Cases include PROG_UNAVAIL, PROC_UNAVAIL,
* GARBAGE_ARGS, and SYSTEM_ERR.
*/
void;
} reply_data;
};
struct accepted_reply {
opaque_auth verf;
union switch (accept_stat stat) {
case SUCCESS:
opaque results[0];
/*
* procedure-specific results start here
*/
case PROG_MISMATCH:
struct {
unsigned int low;
unsigned int high;
} mismatch_info;
default:
/*
* Void. Cases include PROG_UNAVAIL, PROC_UNAVAIL,
* GARBAGE_ARGS, and SYSTEM_ERR.
*/
void;
} reply_data;
};
Reply to an RPC call that was rejected by the server:
答复被服务器拒绝的RPC调用：
The call can be rejected for two reasons: either the server is not running a compatible version of the RPC protocol (RPC_MISMATCH) or the server rejects the identity of the caller (AUTH_ERROR). In case of an RPC version mismatch, the server returns the lowest and highest supported RPC version numbers. In case of invalid authentication, failure status is returned.
拒绝调用可能有两个原因：服务器未运行兼容版本的RPC协议（RPC_不匹配），或者服务器拒绝调用方的标识（AUTH_错误）。如果RPC版本不匹配，服务器将返回支持的最低和最高RPC版本号。如果验证无效，则返回失败状态。
union rejected_reply switch (reject_stat stat) {
case RPC_MISMATCH:
struct {
unsigned int low;
unsigned int high;
} mismatch_info;
case AUTH_ERROR:
auth_stat stat;
};
union rejected_reply switch (reject_stat stat) {
case RPC_MISMATCH:
struct {
unsigned int low;
unsigned int high;
} mismatch_info;
case AUTH_ERROR:
auth_stat stat;
};
As previously stated, authentication parameters are opaque, but open-ended to the rest of the RPC protocol. This section defines two standard flavors of authentication. Implementors are free to invent new authentication types, with the same rules of flavor number assignment as there are for program number assignment. The flavor of a credential or verifier refers to the value of the "flavor" field in the opaque_auth structure. Flavor numbers, like RPC program numbers, are also administered centrally, and developers may assign new flavor numbers by methods described in Appendix B. Credentials and verifiers are represented as variable-length opaque data (the "body" field in the opaque_auth structure).
如前所述，身份验证参数是不透明的，但对RPC协议的其余部分是开放的。本节定义了两种标准的身份验证。实现者可以自由地发明新的身份验证类型，使用与程序编号分配相同的味道编号分配规则。凭证或验证器的风格是指不透明的身份验证结构中“风格”字段的值。风味编号，如RPC程序编号，也是集中管理的，开发人员可以通过附录B中描述的方法分配新的风味编号。凭证和验证器表示为可变长度不透明数据（不透明认证结构中的“主体”字段）。
In this document, two flavors of authentication are described. Of these, Null authentication (described in the next subsection) is mandatory -- it MUST be available in all implementations. System authentication (AUTH_SYS) is described in Appendix A. Implementors MAY include AUTH_SYS in their implementations to support existing applications. See "Security Considerations" for information about other, more secure, authentication flavors.
在本文档中，描述了两种类型的身份验证。其中，空身份验证（在下一小节中描述）是强制性的——它必须在所有实现中都可用。系统认证（AUTH_SYS）在附录A中进行了描述。实现者可以在其实现中包括AUTH_SYS，以支持现有的应用程序。有关其他更安全的身份验证方式的信息，请参阅“安全注意事项”。
Often, calls must be made where the client does not care about its identity or the server does not care who the client is. In this case, the flavor of the RPC message's credential, verifier, and reply verifier is "AUTH_NONE". Opaque data associated with "AUTH_NONE" is undefined. It is recommended that the length of the opaque data be zero.
通常，必须在客户机不关心其身份或服务器不关心客户机是谁的情况下进行调用。在本例中，RPC消息的凭证、验证器和回复验证器的风格是“AUTH_NONE”。与“AUTH_NONE”关联的不透明数据未定义。建议不透明数据的长度为零。
When RPC messages are passed on top of a byte stream transport protocol (like TCP), it is necessary to delimit one message from another in order to detect and possibly recover from protocol errors. This is called record marking (RM). One RPC message fits into one RM record.
当在字节流传输协议（如TCP）上传递RPC消息时，有必要将一条消息与另一条消息分隔开来，以便检测并可能从协议错误中恢复。这称为记录标记（RM）。一条RPC消息适合一条RM记录。
A record is composed of one or more record fragments. A record fragment is a four-byte header followed by 0 to (2**31) - 1 bytes of fragment data. The bytes encode an unsigned binary number; as with XDR integers, the byte order is from highest to lowest. The number encodes two values -- a boolean that indicates whether the fragment is the last fragment of the record (bit value 1 implies the fragment is the last fragment) and a 31-bit unsigned binary value that is the length in bytes of the fragment's data. The boolean value is the highest-order bit of the header; the length is the 31 low-order bits. (Note that this record specification is NOT in XDR standard form!)
记录由一个或多个记录片段组成。记录片段是一个四字节的头，后跟0到（2**31）-1字节的片段数据。字节编码一个无符号二进制数；与XDR整数一样，字节顺序从高到低。该数字编码两个值——一个布尔值，指示该片段是否为记录的最后一个片段（位值1表示该片段为最后一个片段），一个31位无符号二进制值，表示该片段数据的字节长度。布尔值是报头的最高阶位；长度为31个低阶位。（请注意，此记录规范不是XDR标准格式！）
Just as there was a need to describe the XDR data-types in a formal language, there is also need to describe the procedures that operate on these XDR data-types in a formal language as well. The RPC language is an extension to the XDR language, with the addition of "program", "procedure", and "version" declarations. The keywords "program" and "version" are reserved in the RPC language, and implementations of XDR compilers MAY reserve these keywords even when provided with pure XDR, non-RPC, descriptions. The following example is used to describe the essence of the language.
正如需要用正式语言描述XDR数据类型一样，也需要用正式语言描述操作这些XDR数据类型的过程。RPC语言是XDR语言的扩展，添加了“程序”、“过程”和“版本”声明。关键字“program”和“version”在RPC语言中保留，XDR编译器的实现可能保留这些关键字，即使提供了纯XDR、非RPC描述。以下示例用于描述该语言的本质。
Here is an example of the specification of a simple ping program.
下面是一个简单ping程序规范的示例。
program PING_PROG {
/*
* Latest and greatest version
*/
version PING_VERS_PINGBACK {
void
PINGPROC_NULL(void) = 0;
/*
* Ping the client, return the round-trip time
* (in microseconds). Returns -1 if the operation
* timed out.
*/
int
PINGPROC_PINGBACK(void) = 1;
} = 2;
program PING_PROG {
/*
* Latest and greatest version
*/
version PING_VERS_PINGBACK {
void
PINGPROC_NULL(void) = 0;
/*
* Ping the client, return the round-trip time
* (in microseconds). Returns -1 if the operation
* timed out.
*/
int
PINGPROC_PINGBACK(void) = 1;
} = 2;
/*
* Original version
*/
version PING_VERS_ORIG {
void
PINGPROC_NULL(void) = 0;
} = 1;
} = 1;
/*
* Original version
*/
version PING_VERS_ORIG {
void
PINGPROC_NULL(void) = 0;
} = 1;
} = 1;
const PING_VERS = 2; /* latest version */
const PING_VERS = 2; /* latest version */
The first version described is PING_VERS_PINGBACK with two procedures: PINGPROC_NULL and PINGPROC_PINGBACK. PINGPROC_NULL takes no arguments and returns no results, but it is useful for computing round-trip times from the client to the server and back again. By convention, procedure 0 of any RPC protocol should have the same semantics and never require any kind of authentication. The second procedure is used for the client to have the server do a reverse ping operation back to the client, and it returns the amount of time (in microseconds) that the operation used. The next version, PING_VERS_ORIG, is the original version of the protocol, and it does not contain the PINGPROC_PINGBACK procedure. It is useful for compatibility with old client programs, and as this program matures, it may be dropped from the protocol entirely.
描述的第一个版本是PING_VERS_PINGBACK，有两个过程：PINGPROC_NULL和PINGPROC_PINGBACK。PINGPROC_NULL不接受任何参数，也不返回任何结果，但它对于计算从客户端到服务器的往返时间非常有用。按照约定，任何RPC协议的过程0都应该具有相同的语义，并且不需要任何类型的身份验证。第二个过程用于客户端让服务器将反向ping操作返回给客户端，并返回操作使用的时间量（以微秒为单位）。下一个版本PING_VERS_ORIG是协议的原始版本，它不包含PINGPROC_PINGBACK过程。它有助于与旧客户端程序的兼容性，随着该程序的成熟，它可能会完全从协议中删除。
The RPC language is identical to the XDR language defined in RFC 4506, except for the added definition of a "program-def", described below.
RPC语言与RFC 4506中定义的XDR语言相同，只是添加了“程序定义”的定义，如下所述。
program-def: "program" identifier "{" version-def version-def * "}" "=" constant ";"
程序定义：“程序”标识符“{”版本定义版本定义*“}”=“常量”
version-def: "version" identifier "{" procedure-def procedure-def * "}" "=" constant ";"
版本定义：“版本”标识符“{”过程定义过程定义*“}”=“常数”
procedure-def:
proc-return identifier "(" proc-firstarg
("," type-specifier )* ")" "=" constant ";"
procedure-def:
proc-return identifier "(" proc-firstarg
("," type-specifier )* ")" "=" constant ";"
proc-return: "void" | type-specifier
过程返回：“void”|类型说明符
proc-firstarg: "void" | type-specifier
proc firstarg：“void”|类型说明符
o The following keywords are added and cannot be used as identifiers: "program" and "version".
o 添加了以下关键字，不能用作标识符：“程序”和“版本”。
o A version name cannot occur more than once within the scope of a program definition. Neither can a version number occur more than once within the scope of a program definition.
o 版本名称在程序定义的范围内不能出现多次。版本号在程序定义的范围内不能出现多次。
o A procedure name cannot occur more than once within the scope of a version definition. Neither can a procedure number occur more than once within the scope of version definition.
o 在版本定义的范围内，过程名称不能出现多次。在版本定义范围内，过程编号不能出现多次。
o Program identifiers are in the same name space as constant and type identifiers.
o 程序标识符与常量标识符和类型标识符位于相同的名称空间中。
o Only unsigned constants can be assigned to programs, versions, and procedures.
o 只能将未签名常量分配给程序、版本和过程。
o Current RPC language compilers do not generally support more than one type-specifier in procedure argument lists; the usual practice is to wrap arguments into a structure.
o 当前的RPC语言编译器通常不支持过程参数列表中的多个类型说明符；通常的做法是将参数封装到结构中。
The assignment of RPC program numbers, authentication flavor numbers, and authentication status numbers has in the past been performed by Sun Microsystems, Inc (Sun). This is inappropriate for an IETF Standards Track protocol, as such work is done well by the Internet Assigned Numbers Authority (IANA). This document proposes the transfer of authority over RPC program numbers, authentication flavor numbers, and authentication status numbers described here from Sun Microsystems, Inc. to IANA and describes how IANA will maintain and assign these numbers. Users of RPC protocols will benefit by having an independent body responsible for these number assignments.
RPC程序编号、认证风格编号和认证状态编号的分配过去由Sun Microsystems，Inc（Sun）执行。这对于IETF标准跟踪协议是不合适的，因为这样的工作是由互联网分配号码管理局（IANA）完成的。本文件建议将此处所述的RPC程序编号、认证风格编号和认证状态编号的权限从Sun Microsystems，Inc.转移至IANA，并说明IANA将如何维护和分配这些编号。RPC协议的用户将受益于由一个独立机构负责这些数字分配。
Appendix B of this document describes the information to be sent to IANA to request one or more RPC numbers and the rules that apply. IANA will store the request for documentary purposes and put the following information into the public registry:
本文件附录B描述了发送给IANA以请求一个或多个RPC编号的信息以及适用的规则。IANA将出于文件目的存储请求，并将以下信息放入公共注册表：
o The short description of purpose and use
o 对目的和用途的简短描述
o The program number(s) assigned
o 分配的程序编号
o The short identifier string(s)
o 短标识符字符串
Sun has made assignments in both the RPC program number space and the RPC authentication flavor number space since the original deployment of RPC. The assignments made by Sun Microsystems are still valid, and will be preserved. Sun has communicated all current assignments in both number spaces to IANA and final handoff of number assignment is complete. Current program and auth number assignments are provided in Appendix C. Current authentication status numbers are listed in Section 9 of this document in the "enum auth_stat" definition.
自最初部署RPC以来，Sun已在RPC程序编号空间和RPC身份验证风格编号空间中进行分配。Sun Microsystems所做的分配仍然有效，并将予以保留。Sun已将两个号码空间中的所有当前分配传达给IANA，号码分配的最终移交完成。附录C中提供了当前程序和认证编号分配。本文件第9节“enum auth_stat”定义中列出了当前认证状态编号。
Future IANA practice will deal with the following partitioning of the 32-bit number space as listed in Section 8.3. Detailed information for the administration of the partitioned blocks in Section 8.3 is given below.
未来的IANA实践将处理第8.3节中列出的32位数字空间的以下分区。下文给出了第8.3节中分区块管理的详细信息。
The first block will be administered by IANA, with previous assignments by Sun protected. Previous assignments were restricted to the range decimal 100000-399999 (0x000186a0 to 0x00061a7f); therefore, IANA will begin assignments at decimal 400000. Individual numbers should be grated on a First Come First Served basis, and blocks should be granted under rules related to the size of the block.
第一个区块将由IANA管理，之前的作业由Sun Protect负责。以前的分配限制在十进制100000-399999（0x000186a0到0x00061a7f）范围内；因此，IANA将从十进制400000开始分配作业。应按照先到先得的原则对单个号码进行分级，并应根据与区块大小相关的规则授予区块。
The "Defined by local administrator" block is available for any local administrative domain to use, in a similar manner to IP address ranges reserved for private use. The expected use would be through the establishment of a local domain "authority" for assigning numbers from this range. This authority would establish any policies or procedures to be used within that local domain for use or assignment of RPC numbers from the range. The local domain should be sufficiently isolated that it would be unlikely that RPC applications developed by other local domains could communicate with the domain. This could result in RPC number contention, which would cause one of the applications to fail. In the absence of a local administrator, this block can be utilized in a "Private Use" manner per [RFC5226].
“由本地管理员定义”块可供任何本地管理域使用，其方式与保留供私人使用的IP地址范围类似。预期的用途是通过建立一个本地域“机构”来分配该范围内的号码。该机构将建立在该本地域内使用的任何策略或程序，以使用或分配范围内的RPC编号。本地域应充分隔离，以便由其他本地域开发的RPC应用程序不可能与该域通信。这可能会导致RPC号码争用，从而导致其中一个应用程序失败。在没有本地管理员的情况下，可以按照[RFC5226]以“私人使用”的方式使用此块。
The "Transient" block can be used by any RPC application on an "as available" basis. This range is intended for services that can communicate a dynamically selected RPC program number to clients of the service. Any mechanism can be used to communicate the number. For example, either shared memory when the client and server are located on the same system or a network message (either RPC or otherwise) that disseminates the selected number can be used.
任何RPC应用程序都可以在“可用”的基础上使用“瞬态”块。此范围适用于可以将动态选择的RPC程序编号传递给服务客户端的服务。任何机制都可以用来传递号码。例如，当客户端和服务器位于同一系统上时，可以使用共享内存，也可以使用传播所选号码的网络消息（RPC或其他）。
The transient block is not administered. An RPC service uses this range by selecting a number in the transient range and attempting to register that number with the local system's RPC bindery (see the RPCBPROC_SET or PMAPPROC_SET procedures in "Binding Protocols for ONC RPC Version 2", [RFC1833]). If successful, no other RPC service was using that number and the RPC Bindery has assigned that number to the requesting RPC application. The registration is valid until the RPC Bindery terminates, which normally would only happen if the system reboots, causing all applications, including the RPC service using the transient number, to terminate. If the transient number registration fails, another RPC application is using the number and
暂时性阻滞不实施。RPC服务通过在临时范围内选择一个数字并尝试向本地系统的RPC绑定库注册该数字来使用此范围（请参阅“ONC RPC版本2的绑定协议”[RFC1833]中的RPCBPROC_集或PMAPPROC_集过程）。如果成功，则没有其他RPC服务使用该号码，并且RPC绑定库已将该号码分配给请求的RPC应用程序。注册在RPC Bindery终止之前是有效的，通常只有在系统重新启动导致所有应用程序（包括使用临时号码的RPC服务）终止时才会发生这种情况。如果临时号码注册失败，则另一个RPC应用程序正在使用该号码和
the requestor must select another number and try again. To avoid conflicts, the recommended method is to select a number randomly from the transient range.
请求者必须选择其他号码，然后重试。为避免冲突，建议的方法是从瞬态范围中随机选择一个数字。
The "Reserved" blocks are available for future use. RPC applications must not use numbers in these ranges unless their use is allowed by future action by the IESG.
“保留”块可供将来使用。RPC应用程序不得使用这些范围内的数字，除非IESG未来的行动允许使用这些数字。
RPC numbers are usually assigned for specific RPC services. Some applications, however, require multiple RPC numbers for a service. The most common example is an RPC service that needs to have multiple instances of the service active simultaneously at a specific site. RPC does not have an "instance identifier" in the protocol, so either a mechanism must be implemented to multiplex RPC requests amongst various instances of the service or unique RPC numbers must be used by each instance.
RPC编号通常分配给特定的RPC服务。但是，有些应用程序要求服务具有多个RPC编号。最常见的示例是RPC服务，它需要在特定站点上同时激活该服务的多个实例。RPC在协议中没有“实例标识符”，因此必须实现一种机制在服务的各个实例之间多路传输RPC请求，或者每个实例必须使用唯一的RPC编号。
In these cases, the RPC protocol used with the various numbers may be different or the same. The numbers may either be assigned dynamically by the application, or as part of a site-specific administrative decision. If possible, RPC services that dynamically assign RPC numbers should use the "Transient" RPC number block defined in Section 13.3.3. If not possible, RPC number sub-blocks may be requested.
在这些情况下，使用不同号码的RPC协议可能不同或相同。这些号码可以由应用程序动态分配，也可以作为特定于站点的管理决策的一部分。如果可能，动态分配RPC编号的RPC服务应使用第13.3.3节中定义的“瞬态”RPC编号块。如果不可能，可请求RPC编号子块。
Assignment of RPC Number Sub-Blocks is controlled by the size of the sub-block being requested. "Specification Required" and "IESG Approval" are used as defined by Section 4.1 of [RFC5226].
RPC编号子块的分配由所请求的子块的大小控制。按照[RFC5226]第4.1节的定义使用“所需规范”和“IESG批准”。
Size of sub-block Assignment Method Authority
----------------- ----------------- ---------
Up to 100 numbers First Come First Served IANA
Up to 1000 numbers Specification Required IANA
More than 1000 numbers IESG Approval required IESG
Size of sub-block Assignment Method Authority
----------------- ----------------- ---------
Up to 100 numbers First Come First Served IANA
Up to 1000 numbers Specification Required IANA
More than 1000 numbers IESG Approval required IESG
Note: sub-blocks can be any size. The limits given above are maximums, and smaller size sub-blocks are allowed.
注意：子块可以是任何大小。上述限值为最大值，允许使用较小尺寸的子块。
Sub-blocks sized up to 100 numbers may be assigned by IANA on a First Come First Served basis. The RPC Service Description included in the range must include an indication of how the sub-block is managed. At a minimum, the statement should indicate whether the sub-block is
IANA可按照先到先得的原则分配大小不超过100个编号的子区块。范围中包含的RPC服务描述必须包括子块管理方式的指示。该语句至少应指明子块是否为
used with a single RPC protocol or multiple RPC protocols, and whether the numbers are dynamically assigned or statically (through administrative action) assigned.
用于单个RPC协议或多个RPC协议，以及数字是动态分配还是静态分配（通过管理操作）。
Sub-blocks of up to 1000 numbers must be documented in detail. The documentation must describe the RPC protocol or protocols that are to be used in the range. It must also describe how the numbers within the sub-block are to be assigned or used.
必须详细记录多达1000个数字的子块。文档必须描述在该范围内使用的一个或多个RPC协议。它还必须描述如何分配或使用子块中的数字。
Sub-blocks sized over 1000 numbers must be documented as described above, and the assignment must be approved by the IESG. It is expected that this will be rare.
尺寸超过1000个数字的子区块必须如上所述进行记录，且分配必须经IESG批准。预计这将是罕见的。
In order to avoid multiple requests of large blocks of numbers, the following rule is proposed.
为了避免多次请求大数据块，提出了以下规则。
Requests up to and including 100 RPC numbers are handled via the First Come First Served assignment method. This 100 number threshold applies to the total number of RPC numbers assigned to an individual or entity. For example, if an individual or entity first requests, say, 70 numbers, and then later requests 40 numbers, then the request for the 40 numbers will be assigned via the Specification Required method. As long as the total number of numbers assigned does not exceed 1000, IANA is free to waive the Specification Required assignment for incremental requests of less than 100 numbers.
最多100个RPC号码（含100个）的请求通过先到先得的分配方法处理。此100个数字阈值适用于分配给个人或实体的RPC编号总数。例如，如果个人或实体首先请求（例如）70个号码，然后再请求40个号码，那么对40个号码的请求将通过规范要求的方法分配。只要分配的总数量不超过1000个，IANA可自由放弃对少于100个数量的增量请求所需分配的规范。
If an individual or entity has under 1000 numbers and later requests an additional set of numbers such that the individual or entity would be granted over 1000 numbers, then the additional request will require IESG Approval.
如果个人或实体拥有1000个以下的号码，并且之后要求额外的号码集，以便个人或实体可以获得1000个以上的号码，那么额外的请求将需要IESG批准。
The second number space is the authentication mechanism identifier, or "flavor", number. This number is used to distinguish between various authentication mechanisms that can be optionally used with an RPC message. An authentication identifier is used in the "flavor" field of the "opaque_auth" structure.
第二个数字空间是身份验证机制标识符，或“flavor”，数字。此数字用于区分可选择性地与RPC消息一起使用的各种身份验证机制。身份验证标识符用于“不透明认证”结构的“风味”字段中。
Appendix B of this document describes the information to be sent to IANA to request one or more RPC auth numbers and the rules that apply. IANA will store the request for documentary purposes and put the following information into the public registry:
本文件的附录B描述了发送给IANA以请求一个或多个RPC认证号的信息以及适用的规则。IANA将出于文件目的存储请求，并将以下信息放入公共注册表：
o The short identifier string(s)
o 短标识符字符串
o The auth number(s) assigned
o 分配的身份验证号
o The short description of purpose and use
o 对目的和用途的简短描述
Recent progress in RPC security has moved away from new auth flavors as used by AUTH_DH [DH], and has focused on using the existing RPCSEC_GSS [RFC2203] flavor and inventing novel GSS-API (Generic Security Services Application Programming Interface) mechanisms that can be used with it. Even though RPCSEC_GSS is an assigned authentication flavor, use of a new RPCSEC_GSS mechanism with the Network File System (NFS) ([RFC1094] [RFC1813], and [RFC3530]) will require the registration of 'pseudo-flavors' that are used to negotiate security mechanisms in an unambiguous way, as defined by [RFC2623]. Existing pseudo-flavors have been granted in the decimal range 390000-390255. New pseudo-flavor requests will be granted by IANA within this block on a First Come First Served basis.
RPC安全性的最新进展已经从auth_DH[DH]使用的新auth风格转移到使用现有的RPCSEC_GSS[RFC2203]风格，并发明了可与之一起使用的新型GSS-API（通用安全服务应用程序编程接口）机制。尽管RPCSEC_GSS是一种指定的身份验证风格，但在网络文件系统（NFS）（[RFC1094][RFC1813]和[RFC3530]）中使用新的RPCSEC_GSS机制需要注册用于以明确方式协商安全机制的“伪风格”，如[RFC2623]所定义。已授予十进制范围390000-390255的现有伪风格。新的伪风格请求将由IANA在此块内以先到先得的方式授予。
For non-pseudo-flavor requests, IANA will begin granting RPC authentication flavor numbers at 400000 on a First Come First Served basis to avoid conflicts with currently granted numbers.
对于非伪风格请求，IANA将以先到先得的方式开始授予40万个RPC身份验证风格编号，以避免与当前授予的编号发生冲突。
For authentication flavors or RPCSEC_GSS mechanisms to be used on the Internet, it is strongly advised that an Informational or Standards Track RFC be published describing the authentication mechanism behaviour and parameters.
对于要在Internet上使用的身份验证方式或RPCSEC_GSS机制，强烈建议发布一份信息或标准跟踪RFC，描述身份验证机制的行为和参数。
The final number space is the authentication status or "auth_stat" values that describe the nature of a problem found during an attempt to authenticate or validate authentication. The complete initial list of these values is found in Section 9 of this document, in the "auth_stat" enum listing. It is expected that it will be rare to add values, but that a small number of new values may be added from time to time as new authentication flavors introduce new possibilities. Numbers should be granted on a First Come First Served basis to avoid conflicts with currently granted numbers.
最后一个数字空间是身份验证状态或“auth_stat”值，用于描述在尝试身份验证或验证身份验证期间发现的问题的性质。这些值的完整初始列表可在本文档第9节的“auth_stat”枚举列表中找到。预计很少会添加值，但随着新的身份验证风格引入新的可能性，可能会不时添加少量新值。应以先到先得的方式授予号码，以避免与当前授予的号码发生冲突。
Appendix B of this document describes the information to be sent to IANA to request one or more auth_stat values and the rules that apply. IANA will store the request for documentary purposes, and put the following information into the public registry:
本文件附录B描述了发送给IANA以请求一个或多个auth_stat值的信息以及适用的规则。IANA将出于文件目的存储请求，并将以下信息放入公共注册表：
o The short identifier string(s)
o 短标识符字符串
o The auth_stat number(s) assigned
o 分配的身份验证统计号
o The short description of purpose and use
o 对目的和用途的简短描述
AUTH_SYS as described in Appendix A is known to be insecure due to the lack of a verifier to permit the credential to be validated. AUTH_SYS SHOULD NOT be used for services that permit clients to modify data. AUTH_SYS MUST NOT be specified as RECOMMENDED or REQUIRED for any Standards Track RPC service.
众所周知，附录A中所述的认证系统是不安全的，因为缺少允许验证凭证的验证器。AUTH_SYS不应用于允许客户端修改数据的服务。对于任何标准跟踪RPC服务，都不能将AUTH_SYS指定为建议的或必需的。
AUTH_DH as mentioned in Sections 8.2 and 13.4.2 is considered obsolete and insecure; see [RFC2695]. AUTH_DH SHOULD NOT be used for services that permit clients to modify data. AUTH_DH MUST NOT be specified as RECOMMENDED or REQUIRED for any Standards Track RPC service.
第8.2节和第13.4.2节中提到的AUTH_DH被认为是过时和不安全的；见[RFC2695]。AUTH_DH不应用于允许客户端修改数据的服务。对于任何标准跟踪RPC服务，都不得将AUTH_DH指定为建议的或必需的。
[RFC2203] defines a new security flavor, RPCSEC_GSS, which permits GSS-API [RFC2743] mechanisms to be used for securing RPC. All non-trivial RPC programs developed in the future should implement RPCSEC_GSS-based security appropriately. [RFC2623] describes how this was done for a widely deployed RPC program.
[RFC2203]定义了一种新的安全特性RPCSEC_GSS，它允许使用GSS-API[RFC2743]机制来保护RPC。将来开发的所有非平凡RPC程序都应该适当地实现基于RPCSEC_GSS的安全性。[RFC2623]描述了如何为广泛部署的RPC程序执行此操作。
Standards Track RPC services MUST mandate support for RPCSEC_GSS, and MUST mandate support for an authentication pseudo-flavor with appropriate levels of security, depending on the need for simple authentication, integrity (a.k.a. non-repudiation), or data privacy.
标准跟踪RPC服务必须强制支持RPCSEC_GSS，并且必须强制支持具有适当安全级别的身份验证伪风格，这取决于对简单身份验证、完整性（又称不可否认性）或数据隐私的需要。
Appendix A: System Authentication
附录A：系统认证
The client may wish to identify itself, for example, as it is identified on a UNIX(tm) system. The flavor of the client credential is "AUTH_SYS". The opaque data constituting the credential encodes the following structure:
客户机可能希望识别自己，例如，在UNIX（tm）系统上识别自己。客户端凭证的风格是“AUTH_SYS”。构成凭证的不透明数据编码以下结构：
struct authsys_parms {
unsigned int stamp;
string machinename<255>;
unsigned int uid;
unsigned int gid;
unsigned int gids<16>;
};
struct authsys_parms {
unsigned int stamp;
string machinename<255>;
unsigned int uid;
unsigned int gid;
unsigned int gids<16>;
};
The "stamp" is an arbitrary ID that the caller machine may generate. The "machinename" is the name of the caller's machine (like "krypton"). The "uid" is the caller's effective user ID. The "gid" is the caller's effective group ID. "gids" are a counted array of groups that contain the caller as a member. The verifier accompanying the credential should have "AUTH_NONE" flavor value (defined above). Note that this credential is only unique within a particular domain of machine names, uids, and gids.
“戳记”是调用方机器可能生成的任意ID。“machinename”是调用方机器的名称（如“krypton”）。“uid”是呼叫者的有效用户ID。“gid”是呼叫者的有效组ID。“gid”是包含呼叫者作为成员的组的计数数组。凭证附带的验证器应具有“AUTH_NONE”风格值（定义见上文）。请注意，此凭据仅在计算机名、UID和GID的特定域中是唯一的。
The flavor value of the verifier received in the reply message from the server may be "AUTH_NONE" or "AUTH_SHORT". In the case of "AUTH_SHORT", the bytes of the reply verifier's string encode an opaque structure. This new opaque structure may now be passed to the server instead of the original "AUTH_SYS" flavor credential. The server may keep a cache that maps shorthand opaque structures (passed back by way of an "AUTH_SHORT" style reply verifier) to the original credentials of the caller. The caller can save network bandwidth and server cpu cycles by using the shorthand credential.
在来自服务器的回复消息中接收的验证器的味道值可以是“AUTH_NONE”或“AUTH_SHORT”。在“AUTH_SHORT”的情况下，应答验证器字符串的字节编码为不透明结构。这个新的不透明结构现在可以传递给服务器，而不是原始的“AUTH_SYS”风格的凭证。服务器可以保留一个缓存，该缓存将速记不透明结构（通过“AUTH_SHORT”样式的回复验证器传回）映射到调用方的原始凭证。通过使用速记凭证，调用者可以节省网络带宽和服务器cpu周期。
The server may flush the shorthand opaque structure at any time. If this happens, the remote procedure call message will be rejected due to an authentication error. The reason for the failure will be "AUTH_REJECTEDCRED". At this point, the client may wish to try the original "AUTH_SYS" style of credential.
服务器可以随时刷新速记不透明结构。如果发生这种情况，由于身份验证错误，远程过程调用消息将被拒绝。失败的原因将是“AUTH_REJECTEDCRED”。此时，客户机可能希望尝试原始的“AUTH_SYS”凭证样式。
It should be noted that use of this flavor of authentication does not guarantee any security for the users or providers of a service, in itself. The authentication provided by this scheme can be considered legitimate only when applications using this scheme and the network can be secured externally, and privileged transport addresses are used for the communicating end-points (an example of this is the use of privileged TCP/UDP ports in UNIX systems -- note that not all systems enforce privileged transport address mechanisms).
应该注意的是，使用这种风格的身份验证本身并不能保证服务的用户或提供者的任何安全性。只有当使用此方案的应用程序和网络可以在外部进行安全保护，并且通信端点使用特权传输地址时，此方案提供的身份验证才被认为是合法的（UNIX系统中使用特权TCP/UDP端口就是一个例子——请注意，并非所有系统都强制使用特权传输地址机制）。
Appendix B: Requesting RPC-Related Numbers from IANA
附录B：向IANA请求RPC相关编号
RPC program numbers, authentication flavor numbers, and authentication status numbers that must be unique across all networks are assigned by the Internet Assigned Number Authority. To apply for a single number or a block of numbers, electronic mail must be sent to IANA <iana@iana.org> with the following information:
RPC程序编号、身份验证样式编号和身份验证状态编号必须在所有网络中都是唯一的，这些编号由Internet assigned Number Authority分配。要申请单个号码或一组号码，必须向IANA发送电子邮件<iana@iana.org>提供以下信息：
o The type of number(s) (program number or authentication flavor number or authentication status number) sought
o 所寻求的编号类型（程序编号或认证风味编号或认证状态编号）
o How many numbers are sought
o 需要多少个数字
o The name of the person or company that will use the number
o 将使用该号码的个人或公司的名称
o An "identifier string" that associates the number with a service
o 将号码与服务关联的“标识符字符串”
o Email address of the contact person for the service that will be using the number
o 将使用该号码的服务联系人的电子邮件地址
o A short description of the purpose and use of the number
o 简要说明该号码的用途和用途
o If an authentication flavor number is sought, and the number will be a 'pseudo-flavor' intended for use with RPCSEC_GSS and NFS, mappings analogous to those in Section 4.2 of [RFC2623]
o 如果寻求认证风格编号，且该编号将是一个“伪风格”，用于RPCSEC_GSS和NFS，映射类似于[RFC2623]第4.2节中的映射
Specific numbers cannot be requested. Numbers are assigned on a First Come First Served basis.
无法请求特定号码。号码以先到先得的方式分配。
For all RPC authentication flavor and authentication status numbers to be used on the Internet, it is strongly advised that an Informational or Standards Track RFC be published describing the authentication mechanism behaviour and parameters.
对于要在Internet上使用的所有RPC身份验证样式和身份验证状态号，强烈建议发布信息性或标准跟踪RFC，描述身份验证机制行为和参数。
Appendix C: Current Number Assignments
附录C：当前编号分配
#
# Sun-assigned RPC numbers
#
# Description/Owner RPC Program Number Short Name
# -----------------------------------------------------------------
portmapper 100000 pmapprog portmap rpcbind
remote stats 100001 rstatprog
remote users 100002 rusersprog
nfs 100003 nfs
yellow pages (NIS) 100004 ypprog ypserv
mount demon 100005 mountprog
remote dbx 100006 dbxprog
yp binder (NIS) 100007 ypbindprog ypbind
shutdown msg 100008 wall
yppasswd server 100009 yppasswdprog yppasswdd
ether stats 100010 etherstatprog
disk quotas 100011 rquota
spray packets 100012 spray
3270 mapper 100013 ibm3270prog
RJE mapper 100014 ibmrjeprog
selection service 100015 selnsvcprog
remote database access 100016 rdatabaseprog
remote execution 100017 rexec
Alice Office Automation 100018 aliceprog
scheduling service 100019 schedprog
local lock manager 100020 lockprog llockmgr
network lock manager 100021 netlockprog nlockmgr
x.25 inr protocol 100022 x25prog
status monitor 1 100023 statmon1
status monitor 2 100024 statmon2
selection library 100025 selnlibprog
boot parameters service 100026 bootparam
mazewars game 100027 mazeprog
yp update (NIS) 100028 ypupdateprog ypupdate
key server 100029 keyserveprog
secure login 100030 securecmdprog
nfs net forwarder init 100031 netfwdiprog
nfs net forwarder trans 100032 netfwdtprog
sunlink MAP 100033 sunlinkmap
network monitor 100034 netmonprog
lightweight database 100035 dbaseprog
password authorization 100036 pwdauthprog
translucent file svc 100037 tfsprog
nse server 100038 nseprog
nse activate daemon 100039 nse_activate_prog
sunview help 100040 sunview_help_prog
#
# Sun-assigned RPC numbers
#
# Description/Owner RPC Program Number Short Name
# -----------------------------------------------------------------
portmapper 100000 pmapprog portmap rpcbind
remote stats 100001 rstatprog
remote users 100002 rusersprog
nfs 100003 nfs
yellow pages (NIS) 100004 ypprog ypserv
mount demon 100005 mountprog
remote dbx 100006 dbxprog
yp binder (NIS) 100007 ypbindprog ypbind
shutdown msg 100008 wall
yppasswd server 100009 yppasswdprog yppasswdd
ether stats 100010 etherstatprog
disk quotas 100011 rquota
spray packets 100012 spray
3270 mapper 100013 ibm3270prog
RJE mapper 100014 ibmrjeprog
selection service 100015 selnsvcprog
remote database access 100016 rdatabaseprog
remote execution 100017 rexec
Alice Office Automation 100018 aliceprog
scheduling service 100019 schedprog
local lock manager 100020 lockprog llockmgr
network lock manager 100021 netlockprog nlockmgr
x.25 inr protocol 100022 x25prog
status monitor 1 100023 statmon1
status monitor 2 100024 statmon2
selection library 100025 selnlibprog
boot parameters service 100026 bootparam
mazewars game 100027 mazeprog
yp update (NIS) 100028 ypupdateprog ypupdate
key server 100029 keyserveprog
secure login 100030 securecmdprog
nfs net forwarder init 100031 netfwdiprog
nfs net forwarder trans 100032 netfwdtprog
sunlink MAP 100033 sunlinkmap
network monitor 100034 netmonprog
lightweight database 100035 dbaseprog
password authorization 100036 pwdauthprog
translucent file svc 100037 tfsprog
nse server 100038 nseprog
nse activate daemon 100039 nse_activate_prog
sunview help 100040 sunview_help_prog
pnp install 100041 pnp_prog
ip addr allocator 100042 ipaddr_alloc_prog
show filehandle 100043 filehandle
MVS NFS mount 100044 mvsnfsprog
remote user file operations 100045 rem_fileop_user_prog
batched ypupdate 100046 batch_ypupdateprog
network execution mgr 100047 nem_prog
raytrace/mandelbrot remote daemon 100048 raytrace_rd_prog
raytrace/mandelbrot local daemon 100049 raytrace_ld_prog
remote group file operations 100050 rem_fileop_group_prog
remote system file operations 100051 rem_fileop_system_prog
remote system role operations 100052 rem_system_role_prog
gpd lego fb simulator 100053 [unknown]
gpd simulator interface 100054 [unknown]
ioadmd 100055 ioadmd
filemerge 100056 filemerge_prog
Name Binding Program 100057 namebind_prog
sunlink NJE 100058 njeprog
MVSNFS get attribute service 100059 mvsattrprog
SunAccess/SunLink resource manager 100060 rmgrprog
UID allocation service 100061 uidallocprog
license broker 100062 lbserverprog
NETlicense client binder 100063 lbbinderprog
GID allocation service 100064 gidallocprog
SunIsam 100065 sunisamprog
Remote Debug Server 100066 rdbsrvprog
Network Directory Daemon 100067 [unknown]
Network Calendar Program 100068 cmsd cm
ypxfrd 100069 ypxfrd
rpc.timed 100070 timedprog
bugtraqd 100071 bugtraqd
100072 [unknown]
Connectathon Billboard - NFS 100073 [unknown]
Connectathon Billboard - X 100074 [unknown]
Sun tool for scheduling rooms 100075 schedroom
Authentication Negotiation 100076 authnegotiate_prog
Database manipulation 100077 attribute_prog
Kerberos authentication daemon 100078 kerbprog
Internal testing product (no name) 100079 [unknown]
Sun Consulting Special 100080 autodump_prog
Event protocol 100081 event_svc
bugtraq_qd 100082 bugtraq_qd
ToolTalk and Link Service Project 100083 database service
Consulting Services 100084 [unknown]
Consulting Services 100085 [unknown]
Consulting Services 100086 [unknown]
Jupiter Administration 100087 adm_agent admind
100088 [unknown]
pnp install 100041 pnp_prog
ip addr allocator 100042 ipaddr_alloc_prog
show filehandle 100043 filehandle
MVS NFS mount 100044 mvsnfsprog
remote user file operations 100045 rem_fileop_user_prog
batched ypupdate 100046 batch_ypupdateprog
network execution mgr 100047 nem_prog
raytrace/mandelbrot remote daemon 100048 raytrace_rd_prog
raytrace/mandelbrot local daemon 100049 raytrace_ld_prog
remote group file operations 100050 rem_fileop_group_prog
remote system file operations 100051 rem_fileop_system_prog
remote system role operations 100052 rem_system_role_prog
gpd lego fb simulator 100053 [unknown]
gpd simulator interface 100054 [unknown]
ioadmd 100055 ioadmd
filemerge 100056 filemerge_prog
Name Binding Program 100057 namebind_prog
sunlink NJE 100058 njeprog
MVSNFS get attribute service 100059 mvsattrprog
SunAccess/SunLink resource manager 100060 rmgrprog
UID allocation service 100061 uidallocprog
license broker 100062 lbserverprog
NETlicense client binder 100063 lbbinderprog
GID allocation service 100064 gidallocprog
SunIsam 100065 sunisamprog
Remote Debug Server 100066 rdbsrvprog
Network Directory Daemon 100067 [unknown]
Network Calendar Program 100068 cmsd cm
ypxfrd 100069 ypxfrd
rpc.timed 100070 timedprog
bugtraqd 100071 bugtraqd
100072 [unknown]
Connectathon Billboard - NFS 100073 [unknown]
Connectathon Billboard - X 100074 [unknown]
Sun tool for scheduling rooms 100075 schedroom
Authentication Negotiation 100076 authnegotiate_prog
Database manipulation 100077 attribute_prog
Kerberos authentication daemon 100078 kerbprog
Internal testing product (no name) 100079 [unknown]
Sun Consulting Special 100080 autodump_prog
Event protocol 100081 event_svc
bugtraq_qd 100082 bugtraq_qd
ToolTalk and Link Service Project 100083 database service
Consulting Services 100084 [unknown]
Consulting Services 100085 [unknown]
Consulting Services 100086 [unknown]
Jupiter Administration 100087 adm_agent admind
100088 [unknown]
100089 [unknown]
Dual Disk support 100090 libdsd/dsd
DocViewer 1.1 100091 [unknown]
ToolTalk 100092 remote_activation_svc
Consulting Services 100093 host_checking
SNA peer-to-peer 100094 [unknown]
Roger Riggs 100095 searchit
Robert Allen 100096 mesgtool
SNA 100097 [unknown]
SISU 100098 networked version of CS5
NFS Automount File System 100099 autofs
100100 msgboard
event dispatching agent [eventd] 100101 netmgt_eventd_prog
statistics/event logger [netlogd] 100102 netmgt_netlogd_prog
topology display manager [topology]100103 netmgt_topology_prog
syncstat agent [syncstatd] 100104 netmgt_syncstatd_prog
ip packet stats agent [ippktd] 100105 netmgt_ippktd_prog
netmgt config agent [configd] 100106 netmgt_configd_prog
restat agent [restatd] 100107 netmgt_restatd_prog
lpq agent [lprstatd] 100108 netmgt_lprstatd_prog
netmgt activity agent [mgtlogd] 100109 netmgt_mgtlogd_prog
proxy DECnet NCP agent [proxydni] 100110 netmgt_proxydni_prog
topology mapper agent [mapperd] 100111 netmgt_mapperd_prog
netstat agent [netstatd] 100112 netmgt_netstatd_prog
sample netmgt agent [sampled] 100113 netmgt_sampled_prog
X.25 statistics agent [vcstatd] 100114 netmgt_vcstatd_prog
Frame Relay 100128 [unknown]
PPP agent 100129 [unknown]
localhad 100130 rpc.localhad
layers2 100131 na.layers2
token ring agent 100132 na.tr
related to lockd and statd 100133 nsm_addr
Kerberos project 100134 kwarn
ertherif2 100135 na.etherif2
hostmem2 100136 na.hostmem2
iostat2 100137 na.iostat2
snmpv2 100138 na.snmpv2
Cooperative Console 100139 cc_sender
na.cpustat 100140 na.cpustat
Sun Cluster SC3.0 100141 rgmd_receptionist
100142 fed
Network Storage 100143 rdc
Sun Cluster products 100144 nafo
SunCluster 3.0 100145 scadmd
ASN.1 100146 amiserv
100147 amiaux # BER and DER
encode and decode
Delegate Management Server 100148 dm
100089 [unknown]
Dual Disk support 100090 libdsd/dsd
DocViewer 1.1 100091 [unknown]
ToolTalk 100092 remote_activation_svc
Consulting Services 100093 host_checking
SNA peer-to-peer 100094 [unknown]
Roger Riggs 100095 searchit
Robert Allen 100096 mesgtool
SNA 100097 [unknown]
SISU 100098 networked version of CS5
NFS Automount File System 100099 autofs
100100 msgboard
event dispatching agent [eventd] 100101 netmgt_eventd_prog
statistics/event logger [netlogd] 100102 netmgt_netlogd_prog
topology display manager [topology]100103 netmgt_topology_prog
syncstat agent [syncstatd] 100104 netmgt_syncstatd_prog
ip packet stats agent [ippktd] 100105 netmgt_ippktd_prog
netmgt config agent [configd] 100106 netmgt_configd_prog
restat agent [restatd] 100107 netmgt_restatd_prog
lpq agent [lprstatd] 100108 netmgt_lprstatd_prog
netmgt activity agent [mgtlogd] 100109 netmgt_mgtlogd_prog
proxy DECnet NCP agent [proxydni] 100110 netmgt_proxydni_prog
topology mapper agent [mapperd] 100111 netmgt_mapperd_prog
netstat agent [netstatd] 100112 netmgt_netstatd_prog
sample netmgt agent [sampled] 100113 netmgt_sampled_prog
X.25 statistics agent [vcstatd] 100114 netmgt_vcstatd_prog
Frame Relay 100128 [unknown]
PPP agent 100129 [unknown]
localhad 100130 rpc.localhad
layers2 100131 na.layers2
token ring agent 100132 na.tr
related to lockd and statd 100133 nsm_addr
Kerberos project 100134 kwarn
ertherif2 100135 na.etherif2
hostmem2 100136 na.hostmem2
iostat2 100137 na.iostat2
snmpv2 100138 na.snmpv2
Cooperative Console 100139 cc_sender
na.cpustat 100140 na.cpustat
Sun Cluster SC3.0 100141 rgmd_receptionist
100142 fed
Network Storage 100143 rdc
Sun Cluster products 100144 nafo
SunCluster 3.0 100145 scadmd
ASN.1 100146 amiserv
100147 amiaux # BER and DER
encode and decode
Delegate Management Server 100148 dm
100149 rkstat 100150 ocfserv 100151 sccheckd 100152 autoclientd 100153 sunvts 100154 ssmond 100155 smserverd 100156 test1 100157 test2 100158 test3 100159 test4 100160 test5 100161 test6 100162 test7 100163 test8 100164 test9 100165 test10 100166 nfsmapid 100167 SUN_WBEM_C_CIMON_HANDLE 100168 sacmmd 100169 fmd_adm 100170 fmd_api 100171 [unknown] 100172 idmapd unassigned 100173 - 100174 snmptrap 100175 na.snmptrap unassigned 100176-100199
100149 rkstat 100150 ocfserv 100151 sccheckd 100152自动客户端100153 sunvts 100154 ssmond 100155 smserverd 100156测试1 100157测试2 100158测试3 100159测试4 100160测试5 100161测试6 100162测试7 100163测试8 100164测试9 100165测试10 100166 nfsmapid 100167 SUN_WBEM_C_CIMON____(处理100168 SACMDD 100169 fmd(adm 100170 fmd(api 100171[未知]100172 idmapd未分配100173-100174 snmptrap 100175 na.snmptrap未分配100176-100199
unassigned 100200
MVS/NFS Memory usage stats server 100201 [unknown]
Netapp 100202-100207
unassigned 100208-100210
8.0 SunLink SNA RJE 100211 [unknown]
8.0 SunLink SNA RJE 100212 [unknown]
100213 ShowMe
100214 [unknown]
100215 [unknown]
AUTH_RSA Key service 100216 keyrsa
SunSelect PC license service 100217 [unknown]
WWCS (Corporate) 100218 sunsolve
100219 cstatd
X/Open Federated Naming 100220 xfn_server_prog
Kodak Color Management System 100221 kcs_network_io kcs
HA-DBMS 100222 ha_dbms_serv
100223-100225 [unknown]
100226 hafaultd
NFS ACL Service 100227 nfs_acl
distributed lock manager 100228 dlmd
unassigned 100200
MVS/NFS Memory usage stats server 100201 [unknown]
Netapp 100202-100207
unassigned 100208-100210
8.0 SunLink SNA RJE 100211 [unknown]
8.0 SunLink SNA RJE 100212 [unknown]
100213 ShowMe
100214 [unknown]
100215 [unknown]
AUTH_RSA Key service 100216 keyrsa
SunSelect PC license service 100217 [unknown]
WWCS (Corporate) 100218 sunsolve
100219 cstatd
X/Open Federated Naming 100220 xfn_server_prog
Kodak Color Management System 100221 kcs_network_io kcs
HA-DBMS 100222 ha_dbms_serv
100223-100225 [unknown]
100226 hafaultd
NFS ACL Service 100227 nfs_acl
distributed lock manager 100228 dlmd
100229 metad 100230 metamhd 100231 nfsauth 100232 sadmind 100233 ufsd 100234 grpservd 100235 cachefsd 100236 msmprog Media_Server 100237 ihnamed 100238 ihnetd 100239 ihsecured 100240 ihclassmgrd 100241 ihrepositoryd 100242 metamedd rpc.metamedd 100243 contentmanager cm 100244 symon 100245 pld genesil 100246 ctid cluster_transport_interface 100247 ccd cluster_configuration_db 100248 pmfd 100249 dmi2_client 100250 mfs_admin 100251 ndshared_unlink 100252 ndshared_touch 100253 ndshared_slink 100254 cbs control_board_server 100255 skiserv 100256 nfsxa nfsxattr 100257 ndshared_disable 100258 ndshared_enable 100259 sms_account_admin 100260 sms_modem_admin 100261 sms_r_login 100262 sms_r_subaccount_mgt 100263 sms_service_admin 100264 session_admin 100265 canci_ancs_program 100266 canci_sms_program 100267 msmp 100268 halck 100269 halogmsg 100270 nfs_id_map 100271 ncall 100272 hmip 100273 repl_mig 100274 repl_mig_cb
100229 metad 100230 metamhd 100231 nfsauth 100232 sadmind 100233 ufsd 100234 grpservd 100235缓存FSD 100236 MSPROG媒体服务器100237 IHNATED 100238 ihnetd 100239 ihsecured 100240 ihclassmgrd 100241 IHREPORATORYD 100242 metamedd rpc.metamedd 100243 contentmanager cm 100244 symon 100245 pld genesil 100246 ctid CLUSER传输接口100247ccd群集配置\u db 100248 pmfd 100249 dmi2\u客户端100250 mfs\u admin 100251 ndshared\u unlink 100252 ndshared\u touch 100253 ndshared\u slink 100254 cbs控制板\u服务器100255 skiserv 100256 nfsxa nfsxattr 100257 ndshared\u禁用100258 ndshared\u启用100259 sms\u帐户\u admin 100260 sms\u调制解调器\u admin 100261 sms\u r\u登录100262sms_r_子账户管理100263 sms_服务管理100264会话管理100265 canci_ancs_计划100266 canci_sms_计划100267 msmp 100268 halck 100269 halogmsg 100270 nfs_id_map 100271 ncall 100272 hmip 100273 repl_mig 100274 repl_cb
NIS+ 100300 nisplus
NIS+ 100301 nis_cachemgr
NIS+ call back protocol 100302 [unknown]
NIS+ Password Update Daemon 100303 nispasswdd
FNS context update in NIS 100304 fnsypd
100305 [unknown]
100306 [unknown]
100307 [unknown]
100308 [unknown]
100309 [unknown]
unassigned 100310 - 100398
nfscksum 100399 nfscksum
network utilization agent 100400 netmgt_netu_prog
network rpc ping agent 100401 netmgt_rping_prog
100402 na.shell
picsprint 100403 na.picslp
100404 traps
100405 - 100409 [unknown]
100410 jdsagent
100411 na.haconfig
100412 na.halhost
100413 na.hadtsrvc
100414 na.hamdstat
100415 na.neoadmin
100416 ex1048prog
rdmaconfig 100417 rpc.rdmaconfig
IETF NFSv4 Working Group - FedFS 100418 - 100421
100422 mdcommd
100423 kiprop krb5_iprop
100424 stsf
unassigned 100425 - 100499
Sun Microsystems 100500 - 100531 [unknown]
100532 ucmmstate
100533 scrcmd
unassigned 100534 - 100999
nse link daemon 101002 nselinktool
nse link application 101003 nselinkapp
unassigned 101004 - 101900
101901 [unknown]
unassigned 101902 - 101999
AssetLite 102000 [unknown]
PagerTool 102001 [unknown]
Discover 102002 [unknown]
unassigned 102003 - 105000
ShowMe 105001 sharedapp
Registry 105002 REGISTRY_PROG
Print-server 105003 print-server
Proto-server 105004 proto-server
NIS+ 100300 nisplus
NIS+ 100301 nis_cachemgr
NIS+ call back protocol 100302 [unknown]
NIS+ Password Update Daemon 100303 nispasswdd
FNS context update in NIS 100304 fnsypd
100305 [unknown]
100306 [unknown]
100307 [unknown]
100308 [unknown]
100309 [unknown]
unassigned 100310 - 100398
nfscksum 100399 nfscksum
network utilization agent 100400 netmgt_netu_prog
network rpc ping agent 100401 netmgt_rping_prog
100402 na.shell
picsprint 100403 na.picslp
100404 traps
100405 - 100409 [unknown]
100410 jdsagent
100411 na.haconfig
100412 na.halhost
100413 na.hadtsrvc
100414 na.hamdstat
100415 na.neoadmin
100416 ex1048prog
rdmaconfig 100417 rpc.rdmaconfig
IETF NFSv4 Working Group - FedFS 100418 - 100421
100422 mdcommd
100423 kiprop krb5_iprop
100424 stsf
unassigned 100425 - 100499
Sun Microsystems 100500 - 100531 [unknown]
100532 ucmmstate
100533 scrcmd
unassigned 100534 - 100999
nse link daemon 101002 nselinktool
nse link application 101003 nselinkapp
unassigned 101004 - 101900
101901 [unknown]
unassigned 101902 - 101999
AssetLite 102000 [unknown]
PagerTool 102001 [unknown]
Discover 102002 [unknown]
unassigned 102003 - 105000
ShowMe 105001 sharedapp
Registry 105002 REGISTRY_PROG
Print-server 105003 print-server
Proto-server 105004 proto-server
Notification-server 105005 notification-server
Transfer-agent-server 105006 transfer-agent-server
unassigned 105007 - 110000
110001 tsolrpcb
110002 tsolpeerinfo
110003 tsolboot
120001 cmip na.cmip
120002 na.osidiscover
120003 cmiptrap
unassigned 120004 - 120099
120100 eserver
120101 repserver
120102 swserver
120103 dmd
120104 ca
unassigned 120105 - 120125
120126 nf_fddi
120127 nf_fddismt7_2
unassigned 120128 - 150000
pc passwd authorization 150001 pcnfsdprog
TOPS name mapping 150002 [unknown]
TOPS external attribute storage 150003 [unknown]
TOPS hierarchical file system 150004 [unknown]
TOPS NFS transparency extensions 150005 [unknown]
PC NFS License 150006 pcnfslicense
RDA 150007 rdaprog
WabiServer 150008 wsprog
WabiServer 150009 wsrlprog
unassigned 150010 - 160000
160001 nihon-cm
160002 nihon-ce
unassigned 160003 - 170099
170100 domf_daemon0
170101 domf_daemon1
170102 domf_daemon2
170103 domf_daemon3
170104 domf_daemon4
170105 domf_daemon5
unassigned 170106 - 179999
180000 cecprog
180001 cecsysprog
180002 cec2cecprog
180003 cesprog
180004 ces2cesprog
180005 cet2cetprog
180006 cet2cetdoneprog
180007 cetcomprog
180008 cetsysprog
Notification-server 105005 notification-server
Transfer-agent-server 105006 transfer-agent-server
unassigned 105007 - 110000
110001 tsolrpcb
110002 tsolpeerinfo
110003 tsolboot
120001 cmip na.cmip
120002 na.osidiscover
120003 cmiptrap
unassigned 120004 - 120099
120100 eserver
120101 repserver
120102 swserver
120103 dmd
120104 ca
unassigned 120105 - 120125
120126 nf_fddi
120127 nf_fddismt7_2
unassigned 120128 - 150000
pc passwd authorization 150001 pcnfsdprog
TOPS name mapping 150002 [unknown]
TOPS external attribute storage 150003 [unknown]
TOPS hierarchical file system 150004 [unknown]
TOPS NFS transparency extensions 150005 [unknown]
PC NFS License 150006 pcnfslicense
RDA 150007 rdaprog
WabiServer 150008 wsprog
WabiServer 150009 wsrlprog
unassigned 150010 - 160000
160001 nihon-cm
160002 nihon-ce
unassigned 160003 - 170099
170100 domf_daemon0
170101 domf_daemon1
170102 domf_daemon2
170103 domf_daemon3
170104 domf_daemon4
170105 domf_daemon5
unassigned 170106 - 179999
180000 cecprog
180001 cecsysprog
180002 cec2cecprog
180003 cesprog
180004 ces2cesprog
180005 cet2cetprog
180006 cet2cetdoneprog
180007 cetcomprog
180008 cetsysprog
180009 cghapresenceprog
180010 cgdmsyncprog
180011 cgdmcnscliprog
180012 cgdmcrcscliprog
180013 cgdmcrcssvcproG
180014 chmprog
180015 chmsysprog
180016 crcsapiprog
180017 ckptmprog
180018 crimcomponentprog
180019 crimqueryprog
180020 crimsecondaryprog
180021 crimservicesprog
180022 crimsyscomponentprog
180023 crimsysservicesprog
180024 csmagtapiprog
180025 csmagtcallbackprog
180026 csmreplicaprog
180027 csmsrvprog
180028 cssccltprog
180029 csscsvrprog
180030 csscopresultprog
unassigned 180031 - 199999
200000 pyramid_nfs
200001 pyramid_reserved
200002 cadds_image
200003 stellar_name_prog
200004 [unknown]
200005 [unknown]
200006 pacl
200007 lookupids
200008 ax_statd_prog
200009 ax_statd2_prog
200010 edm
200011 dtedirwd
200012 [unknown]
200013 [unknown]
200014 [unknown]
200015 [unknown]
200016 easerpcd
200017 rlxnfs
200018 sascuiddprog
200019 knfsd
200020 ftnfsd ftnfsd_program
200021 ftsyncd ftsyncd_program
200022 ftstatd ftstatd_program
200023 exportmap
200024 nfs_metadata
180009 cghapresenceprog
180010 cgdmsyncprog
180011 cgdmcnscliprog
180012 cgdmcrcscliprog
180013 cgdmcrcssvcproG
180014 chmprog
180015 chmsysprog
180016 crcsapiprog
180017 ckptmprog
180018 crimcomponentprog
180019 crimqueryprog
180020 crimsecondaryprog
180021 crimservicesprog
180022 crimsyscomponentprog
180023 crimsysservicesprog
180024 csmagtapiprog
180025 csmagtcallbackprog
180026 csmreplicaprog
180027 csmsrvprog
180028 cssccltprog
180029 csscsvrprog
180030 csscopresultprog
unassigned 180031 - 199999
200000 pyramid_nfs
200001 pyramid_reserved
200002 cadds_image
200003 stellar_name_prog
200004 [unknown]
200005 [unknown]
200006 pacl
200007 lookupids
200008 ax_statd_prog
200009 ax_statd2_prog
200010 edm
200011 dtedirwd
200012 [unknown]
200013 [unknown]
200014 [unknown]
200015 [unknown]
200016 easerpcd
200017 rlxnfs
200018 sascuiddprog
200019 knfsd
200020 ftnfsd ftnfsd_program
200021 ftsyncd ftsyncd_program
200022 ftstatd ftstatd_program
200023 exportmap
200024 nfs_metadata
unassigned 200025 - 200200
200201 ecoad
200202 eamon
200203 ecolic
200204 cs_printstatus_svr
200205 ecodisc
unassigned 200206 - 300000
300001 adt_rflockprog
300002 columbine1
300003 system33_prog
300004 frame_prog1
300005 uimxprog
300006 rvd
300007 entombing daemon
300008 account mgmt system
300009 frame_prog2
300010 beeper access
300011 dptuprog
300012 mx-bcp
300013 instrument-file-access
300014 file-system-statistics
300015 unify-database-server
300016 tmd_msg
300017 [unknown]
300018 [unknown]
300019 automounter access
300020 lock server
300021 [unknown]
300022 office-automation-1
300023 office-automation-2
300024 office-automation-3
300025 office-automation-4
300026 office-automation-5
300027 office-automation-6
300028 office-automation-7
300029 local-data-manager
300030 chide
300031 csi_program
300032 [unknown]
300033 online-help
300034 case-tool
300035 delta
300036 rgi
300037 instrument-config-server
300038 [unknown]
300039 [unknown]
300040 dtia-rpc-server
300041 cms
unassigned 200025 - 200200
200201 ecoad
200202 eamon
200203 ecolic
200204 cs_printstatus_svr
200205 ecodisc
unassigned 200206 - 300000
300001 adt_rflockprog
300002 columbine1
300003 system33_prog
300004 frame_prog1
300005 uimxprog
300006 rvd
300007 entombing daemon
300008 account mgmt system
300009 frame_prog2
300010 beeper access
300011 dptuprog
300012 mx-bcp
300013 instrument-file-access
300014 file-system-statistics
300015 unify-database-server
300016 tmd_msg
300017 [unknown]
300018 [unknown]
300019 automounter access
300020 lock server
300021 [unknown]
300022 office-automation-1
300023 office-automation-2
300024 office-automation-3
300025 office-automation-4
300026 office-automation-5
300027 office-automation-6
300028 office-automation-7
300029 local-data-manager
300030 chide
300031 csi_program
300032 [unknown]
300033 online-help
300034 case-tool
300035 delta
300036 rgi
300037 instrument-config-server
300038 [unknown]
300039 [unknown]
300040 dtia-rpc-server
300041 cms
300042 viewer
300043 aqm
300044 exclaim
300045 masterplan
300046 fig_tool
300047 [unknown]
300048 [unknown]
300049 [unknown]
300050 remote-lock-manager
300051 [unknown]
300052 gdebug
300053 ldebug
300054 rscanner
300055 [unknown]
300056 [unknown]
300057 [unknown]
300058 [unknown]
300059 [unknown]
300060 [unknown]
300061 [unknown]
300062 [unknown]
300063 [unknown]
300064 [unknown]
300065 [unknown]
300066 nSERVER
300067 [unknown]
300068 [unknown]
300069 [unknown]
300070 [unknown]
300071 BioStation
300072 [unknown]
300073 NetProb
300074 Logging
300075 Logging
300076 [unknown]
300077 [unknown]
300078 [unknown]
300079 [unknown]
300080 [unknown]
300081 [unknown]
300082 sw_twin
300083 remote_get_login
300084 odcprog
300085 [unknown]
300086 [unknown]
300087 [unknown]
300088 [unknown]
300089 [unknown]
300042 viewer
300043 aqm
300044 exclaim
300045 masterplan
300046 fig_tool
300047 [unknown]
300048 [unknown]
300049 [unknown]
300050 remote-lock-manager
300051 [unknown]
300052 gdebug
300053 ldebug
300054 rscanner
300055 [unknown]
300056 [unknown]
300057 [unknown]
300058 [unknown]
300059 [unknown]
300060 [unknown]
300061 [unknown]
300062 [unknown]
300063 [unknown]
300064 [unknown]
300065 [unknown]
300066 nSERVER
300067 [unknown]
300068 [unknown]
300069 [unknown]
300070 [unknown]
300071 BioStation
300072 [unknown]
300073 NetProb
300074 Logging
300075 Logging
300076 [unknown]
300077 [unknown]
300078 [unknown]
300079 [unknown]
300080 [unknown]
300081 [unknown]
300082 sw_twin
300083 remote_get_login
300084 odcprog
300085 [unknown]
300086 [unknown]
300087 [unknown]
300088 [unknown]
300089 [unknown]
300090 [unknown]
300091 smartdoc
300092 superping
300093 distributed-chembench
300094 uacman/alfil-uacman
300095 ait_rcagent_prog
300096 ait_rcagent_appl_prog
300097 smart
300098 ecoprog
300099 leonardo
300100 [unknown]
300101 [unknown]
300102 [unknown]
300103 [unknown]
300104 [unknown]
300105 [unknown]
300106 [unknown]
300107 [unknown]
300108 wingz
300109 teidan
300110 [unknown]
300111 [unknown]
300112 [unknown]
300113 [unknown]
300114 [unknown]
300115 [unknown]
300116 cadc_fhlockprog
300117 highscan
300118 [unknown]
300119 [unknown]
300120 [unknown]
300121 opennavigator
300122 aarpcxfer
300123 [unknown]
300124 [unknown]
300125 [unknown]
300126 groggs
300127 licsrv
300128 issdemon
300129 [unknown]
300130 maximize
300131 cgm_server
300132 [unknown]
300133 agent_rpc
300134 docmaker
300135 docmaker
300136 [unknown]
300137 [unknown]
300090 [unknown]
300091 smartdoc
300092 superping
300093 distributed-chembench
300094 uacman/alfil-uacman
300095 ait_rcagent_prog
300096 ait_rcagent_appl_prog
300097 smart
300098 ecoprog
300099 leonardo
300100 [unknown]
300101 [unknown]
300102 [unknown]
300103 [unknown]
300104 [unknown]
300105 [unknown]
300106 [unknown]
300107 [unknown]
300108 wingz
300109 teidan
300110 [unknown]
300111 [unknown]
300112 [unknown]
300113 [unknown]
300114 [unknown]
300115 [unknown]
300116 cadc_fhlockprog
300117 highscan
300118 [unknown]
300119 [unknown]
300120 [unknown]
300121 opennavigator
300122 aarpcxfer
300123 [unknown]
300124 [unknown]
300125 [unknown]
300126 groggs
300127 licsrv
300128 issdemon
300129 [unknown]
300130 maximize
300131 cgm_server
300132 [unknown]
300133 agent_rpc
300134 docmaker
300135 docmaker
300136 [unknown]
300137 [unknown]
300138 [unknown]
300139 iesx
300140 [unknown]
300141 [unknown]
300142 [unknown]
300143 [unknown]
300144 smart-mbs
300145 [unknown]
300146 [unknown]
300147 docimage
300148 [unknown]
300149 dmc-interface
300150 [unknown]
300151 jss
300152 [unknown]
300153 arimage
300154 xdb-workbench
300155 frontdesk
300156 dmc
300157 expressight-6000
300158 graph service program
300159 [unknown]
300160 [unknown]
300161 [unknown]
300162 [unknown]
300163 [unknown]
300164 [unknown]
300165 [unknown]
300166 [unknown]
300167 [unknown]
300168 [unknown]
300169 [unknown]
300170 [unknown]
300171 [unknown]
300172 [unknown]
300173 [unknown]
300174 [unknown]
300175 [unknown]
300176 rlpr
300177 nx_hostdprog
300178 netuser-x
300179 rmntprog
300180 [unknown]
300181 mipe
300182 [unknown]
300183 collectorprog
300184 uslookup_PROG
300185 viewstation
300138 [unknown]
300139 iesx
300140 [unknown]
300141 [unknown]
300142 [unknown]
300143 [unknown]
300144 smart-mbs
300145 [unknown]
300146 [unknown]
300147 docimage
300148 [unknown]
300149 dmc-interface
300150 [unknown]
300151 jss
300152 [unknown]
300153 arimage
300154 xdb-workbench
300155 frontdesk
300156 dmc
300157 expressight-6000
300158 graph service program
300159 [unknown]
300160 [unknown]
300161 [unknown]
300162 [unknown]
300163 [unknown]
300164 [unknown]
300165 [unknown]
300166 [unknown]
300167 [unknown]
300168 [unknown]
300169 [unknown]
300170 [unknown]
300171 [unknown]
300172 [unknown]
300173 [unknown]
300174 [unknown]
300175 [unknown]
300176 rlpr
300177 nx_hostdprog
300178 netuser-x
300179 rmntprog
300180 [unknown]
300181 mipe
300182 [unknown]
300183 collectorprog
300184 uslookup_PROG
300185 viewstation
300186 iate
300187 [unknown]
300188 [unknown]
300189 [unknown]
300190 imsvtprog
300191 [unknown]
300192 [unknown]
300193 [unknown]
300194 pmdb
300195 pmda
300196 [unknown]
300197 [unknown]
300198 trend_idbd
300199 rres
300200 sd.masterd
300201 sd.executiond
300202 sd.listend
300203 sd.reserve1
300204 sd.reserve2
300205 msbd
300206 stagedprog
300207 mountprog
300208 watchdprog
300209 pms
300210 [unknown]
300211 session_server_program
300212 session_program
300213 debug_serverprog
300214 [unknown]
300215 [unknown]
300216 paceprog
300217 [unknown]
300218 mbus
300219 aframes2ps
300220 npartprog
300221 cm1server
300222 cm1bridge
300223 sailfrogfaxprog
300224 sailfrogphoneprog
300225 sailfrogvmailprog
300226 wserviceprog arcstorm
300227 hld
300228 alive
300229 radsp
300230 radavx
300231 radview
300232 rsys_prog
300233 rsys_prog
300186 iate
300187 [unknown]
300188 [unknown]
300189 [unknown]
300190 imsvtprog
300191 [unknown]
300192 [unknown]
300193 [unknown]
300194 pmdb
300195 pmda
300196 [unknown]
300197 [unknown]
300198 trend_idbd
300199 rres
300200 sd.masterd
300201 sd.executiond
300202 sd.listend
300203 sd.reserve1
300204 sd.reserve2
300205 msbd
300206 stagedprog
300207 mountprog
300208 watchdprog
300209 pms
300210 [unknown]
300211 session_server_program
300212 session_program
300213 debug_serverprog
300214 [unknown]
300215 [unknown]
300216 paceprog
300217 [unknown]
300218 mbus
300219 aframes2ps
300220 npartprog
300221 cm1server
300222 cm1bridge
300223 sailfrogfaxprog
300224 sailfrogphoneprog
300225 sailfrogvmailprog
300226 wserviceprog arcstorm
300227 hld
300228 alive
300229 radsp
300230 radavx
300231 radview
300232 rsys_prog
300233 rsys_prog
300234 fm_rpc_prog
300235 aries
300236 uapman
300237 ddman
300238 top
300239 [unknown]
300240 trendlink
300241 licenseprog
300242 statuslicenseprog
300243 oema_rmpf_svc
300244 oema_smpf_svc
300245 oema_rmsg_svc
300246 grapes-sd
300247 ds_master
300248 ds_transfer
300249 ds_logger
300250 ds_query
300251 [unknown]
300252 [unknown]
300253 nsd_prog
300254 browser
300255 epoch
300256 floorplanner
300257 reach
300258 tactic
300259 cachescientific1
300260 cachescientific2
300261 desksrc_prog
300262 photo3d1
300263 photo3d2
300264 [unknown]
300265 soundmgr
300266 s6k
300267 aims_referenced_
text_processor
300268 xess
300269 ds_queue
300270 [unknown]
300271 orionscanplus
300272 openlink-xx
300273 kbmsprog
300274 [unknown]
300275 futuresource
300276 the_xprt
300277 cmg_srvprog
300278 [unknown]
300279 [unknown]
300280 front
300234 fm_rpc_prog
300235 aries
300236 uapman
300237 ddman
300238 top
300239 [unknown]
300240 trendlink
300241 licenseprog
300242 statuslicenseprog
300243 oema_rmpf_svc
300244 oema_smpf_svc
300245 oema_rmsg_svc
300246 grapes-sd
300247 ds_master
300248 ds_transfer
300249 ds_logger
300250 ds_query
300251 [unknown]
300252 [unknown]
300253 nsd_prog
300254 browser
300255 epoch
300256 floorplanner
300257 reach
300258 tactic
300259 cachescientific1
300260 cachescientific2
300261 desksrc_prog
300262 photo3d1
300263 photo3d2
300264 [unknown]
300265 soundmgr
300266 s6k
300267 aims_referenced_
text_processor
300268 xess
300269 ds_queue
300270 [unknown]
300271 orionscanplus
300272 openlink-xx
300273 kbmsprog
300274 [unknown]
300275 futuresource
300276 the_xprt
300277 cmg_srvprog
300278 [unknown]
300279 [unknown]
300280 front
300281 [unknown]
300282 [unknown]
300283 [unknown]
300284 conmanprog
300285 jincv2
300286 isls
300287 systemstatprog
300288 fxpsprog
300289 callpath
300290 axess
300291 armor_rpcd
300292 armor_dictionary_rpcd
300293 armor_miscd
300294 filetransfer_prog
300295 bl_swda
300296 bl_hwda
300297 [unknown]
300298 [unknown]
300299 [unknown]
300300 filemon
300301 acunetprog
300302 rbuild
300303 assistprog
300304 tog
300305 [unknown]
300306 sns7000
300307 igprog
300308 tgprog
300309 plc
300310 pxman pxlsprog
300311 hde_server hdeserver
300312 tsslicenseprog
300313 rpc.explorerd
300314 chrd
300315 tbisam
300316 tbis
300317 adsprog
300318 sponsorprog
300319 querycmprog
300320 [unknown]
300321 [unknown]
300322 mobil1
300323 sld
service_locator_daemon
300324 linkprog
300325 codexdaemonprog
300326 drprog
300327 ressys_commands
300281 [unknown]
300282 [unknown]
300283 [unknown]
300284 conmanprog
300285 jincv2
300286 isls
300287 systemstatprog
300288 fxpsprog
300289 callpath
300290 axess
300291 armor_rpcd
300292 armor_dictionary_rpcd
300293 armor_miscd
300294 filetransfer_prog
300295 bl_swda
300296 bl_hwda
300297 [unknown]
300298 [unknown]
300299 [unknown]
300300 filemon
300301 acunetprog
300302 rbuild
300303 assistprog
300304 tog
300305 [unknown]
300306 sns7000
300307 igprog
300308 tgprog
300309 plc
300310 pxman pxlsprog
300311 hde_server hdeserver
300312 tsslicenseprog
300313 rpc.explorerd
300314 chrd
300315 tbisam
300316 tbis
300317 adsprog
300318 sponsorprog
300319 querycmprog
300320 [unknown]
300321 [unknown]
300322 mobil1
300323 sld
service_locator_daemon
300324 linkprog
300325 codexdaemonprog
300326 drprog
300327 ressys_commands
300328 stamp
300329 matlab
300330 sched1d
300331 upcprog
300332 xferbkch
300333 xfer
300334 qbthd
300335 qbabort
300336 lsd
300337 geomgrd
300338 generic_fts
300339 ft_ack
300340 lymb
300341 vantage
300342 cltstd clooptstdprog
300343 clui clui_prog
300344 testerd tstdprog
300345 extsim
300346 cmd_dispatch maxm_ems
300347 callpath_receive_program
300348 x3270prog
300349 sbc_lag
300350 sbc_frsa
300351 sbc_frs
300352 atommgr
300353 geostrat
300354 dbvialu6.2
300355 [unknown]
300356 fxncprog
300357 infopolic
300358 [unknown]
300359 aagns
300360 aagms
300361 [unknown]
300362 clariion_mgr
300363 setcimrpc
300364 virtual_protocol_adapter
300365 unibart
300366 uniarch
300367 unifile
300368 unisrex
300369 uniscmd
300370 rsc
300371 set
300372 desaf-ws/key
300373 reeldb
300374 nl
300375 rmd
300328 stamp
300329 matlab
300330 sched1d
300331 upcprog
300332 xferbkch
300333 xfer
300334 qbthd
300335 qbabort
300336 lsd
300337 geomgrd
300338 generic_fts
300339 ft_ack
300340 lymb
300341 vantage
300342 cltstd clooptstdprog
300343 clui clui_prog
300344 testerd tstdprog
300345 extsim
300346 cmd_dispatch maxm_ems
300347 callpath_receive_program
300348 x3270prog
300349 sbc_lag
300350 sbc_frsa
300351 sbc_frs
300352 atommgr
300353 geostrat
300354 dbvialu6.2
300355 [unknown]
300356 fxncprog
300357 infopolic
300358 [unknown]
300359 aagns
300360 aagms
300361 [unknown]
300362 clariion_mgr
300363 setcimrpc
300364 virtual_protocol_adapter
300365 unibart
300366 uniarch
300367 unifile
300368 unisrex
300369 uniscmd
300370 rsc
300371 set
300372 desaf-ws/key
300373 reeldb
300374 nl
300375 rmd
300376 agcd 300377 rsynd 300378 rcnlib 300379 rcnlib_attach 300380 evergreen_mgmt_agent 300381 fx104prog 300382 rui remote_user_interface 300383 ovomd 300384 [unknown] 300385 [unknown] 300386 system_server 300387 pipecs cs_pipeprog ppktrpc 300388 uv-net univision 300389 auexe 300390 audip 300391 mqi 300392 eva 300393 eeei_reserved_1 300394 eeei_reserved_2 300395 eeei_reserved_3 300396 eeei_reserved_4 300397 eeei_reserved_5 300398 eeei_reserved_6 300399 eeei_reserved_7 300400 eeei_reserved_8 300401 cprlm 300402 wg_idms_manager 300403 timequota 300404 spiff 300405-300414 ov_oem_svc 300415 ov_msg_ctlg_svc 300416 ov_advt_reg_svc 300417-300424 showkron 300425 daatd 300426 swiftnet 300427 ovomdel 300428 ovomreq 300429 msg_dispatcher 300430 pcshare server 300431 rcvs 300432 fdfserver 300433 bssd 300434 drdd 300435 mif_gutsprog 300436 mif_guiprog 300437 twolfd
300376 agcd 300377 rsynd 300378 rcnlib 300379 rcnlib_附件300380常青管理代理300381 fx104prog 300382 rui远程用户界面300383 ovomd 300384[未知]300385[未知]300386系统服务器300387管道cs_pipeprog ppktrpc 300388 uv net univision 300389 auexe 300390 audip 300391 mqi 300392 eva 300393 eeei_保留1 300394 eeei_保留2 300395 eeei_保留3 300396 eeei_保留4 300397 eeei_保留5 300398 eeei_保留6 300399 eeei_保留7 300400 eeei_保留8 300402; CPRU管理器300403时间配额300404 spiff 300405-300414 ov_oem_svc 300415 ov_msg_ctlg_svc 300416 ov_advt_reg_svc 300417-300424 showkron 300425 daatd 300426 swiftnet 300427 ovomdel 300428 ovomreq 300429 msg调度程序300430 pcshare服务器300431 RCV 300432 fdfserver 300433 bssd 300434 drdd 300435 mif\U gutsprog 300436 mif 300437
300438 twscd 300439 nwsbumv 300440 dgux_mgr 300441 pfxd 300442 tds 300443 ovomadmind 300444 ovomgate 300445 omadmind 300446 nps 300447 npd 300448 tsa 300449 cdaimc unassigned 300450-300452 300453 ckt_implementation 300454 mda-tactical unassigned 300455-300458 300459 atrrun 300460 RoadRunner 300461 nas 300462 undelete 300463 ovacadd 300464 tbdesmai 300465 arguslm 300466 dmd 300467 drd 300468 fm_help 300469 ftransrpc_prog 300470 finrisk 300471 dg_pc_idisched 300472 dg_pc_idiserv 300473 apd 300474 ap_sspd 300475 callpatheventrecorder 300476 flc 300477 dg_osm 300478 dspnamed 300479 iqddsrv 300480 iqjobsrv 300481 tacosxx 300482 wheeldbmg 300483 cnxmgr_nm_prog 300484 cnxmgr_cfg_prog 300485 3dsmapper 300486 ids 300487 imagine_rpc_svc 300488 lfn 300489 salesnet 300490 defaxo
300438 twscd 300439 nwsbumv 300440 dgux_经理300441 pfxd 300442 tds 300443 ovomadmind 300444 ovomgate 300445 omadmind 300446 nps 300447 npd 300448 tsa 300449 cdaimc未分配300450-300452 300453 ckt_实施300454 mda战术未分配300455-300458 300459 ATRUN 300460 Roadrun 300461 nas 300462未删除300463 ovacadd 300464 tbdesmai300465 arguslm 300466 dmd 300467 drd 300468 fm_帮助300469 FTransrc_项目300470; 300470 finrisk 300471 dg_pc_idisched 300472 dg_pc_IDisserv 300473 apd 300474 ap_sspd 300475呼叫路径事件记录器300476 flc 300477 dg_osm 300478 dspnamed 300479 iqddsrv 300480 IQJOBSR 300481 Tacoxx 300482 Wheelg 300483 cnxmgr_项目300484 CNGR cfg 30048; cfg项目3dsmapper 300486 ids 300487 imagine_rpc_svc 300488 lfn 300489 salesnet 300490 defaxo
300491 dbqtsd 300492 kms 300493 rpc.iced 300494 calc2s 300495 ptouidprog 300496 docsls 300497 new 300498 collagebdg 300499 ars_server 300500 ars_client 300501 vr_catalog 300502 vr_tdb 300503 ama 300504 evama 300505 conama 300506 service_process 300507 reuse_proxy 300508 mars_ctrl 300509 mars_db 300510 mars_com 300511 mars_admch 300512 tbpipcip 300513 top_acs_svc 300514 inout_svc 300515 csoft_wp 300516 mcfs 300517 eventprog 300518 dg_pc_idimsg 300519 dg_pc_idiaux 300520 atsr_gc 300521 alarm alarm_prog 300522 fts_prog 300523 dcs_prog 300524 ihb_prog 300525 [unknown] 300526 [unknown] 300527 clu_info_prog 300528 rmfm 300529 c2sdocd 300530 interahelp 300531 callpathasyncmsghandler 300532 optix_arc 300533 optix_ts 300534 optix_wf 300535 maxopenc 300536 cev cev_server 300537 sitewideprog 300538 drs
300491 dbqtsd 300492 kms 300493 rpc.iced 300494 calc2s 300495 PTOIDPROG 300496 docsls 300497新建300498拼贴BDG 300499 ars_服务器300500 ars_客户端300501 vr_目录300502 vr_tdb 300503 ama 300504 evama 300505 conama 300506服务流程300507重用_代理300508 mars_ctrl 300509 mars_db 300510 mars_com 300511 mars_CH 300512 TBPIP300513顶部空调svc 300514输入svc 300515软件包300516 mcfs 300517事件程序300518 dg_pc_IDIMG 300519 dg_pc_idiaux 300520 atsr_gc 300521报警程序300522 fts_程序300523 dcs_程序300524 ihb_程序300525[未知]300526300527俱乐部信息项目300528 rmfm 300529 c2sdocd 300530内部帮助300531呼叫路径异步MSGhandler 300532 optix_arc 300533 optix_ts 300534 optix_wf 300535 maxopenc 300536 cev cev_服务器300537站点范围的项目300538 drs
300539 drsdm 300540 dasgate 300541 dcdbd 300542 dcpsd 300543 supportlink_prog 300544 broker 300545 listner 300546 multiaccess 300547 spai_interface 300548 spai_adaption 300549 chimera_ci chimera_clientinterface 300550 chimera_pi chimera_processinvoker 300551 teamware_fl teamware_foundationlevel 300552 teamware_sl teamware_systemlevel 300553 teamware_ui teamware_userinterface 300554 lprm 300555 mpsprog Mensuration_Proxy_Server 300556 mo_symdis 300557 retsideprog 300558 slp 300559 slm-api 300560 im_rpc teamconference 300561 license_prog license 300562 stuple stuple_prog 300563 upasswd_prog 300564 gentranmentorsecurity 300565 gentranmentorprovider 300566 latituded latitude_license_server 300567 gentranmentorreq1 300568 gentranmentorreq2 300569 gentranmentorreq3 300570 rj_server 300571 gws-rdb 300572 gws-mpmd 300573 gws-spmd 300574 vwcalcd 300575 vworad 300576 vwsybd 300577 vwave 300578 online_assistant 300579 internet_assistant
300539 drsdm 300540 dasgate 300541 dcdbd 300542 dcpsd 300543 supportlink_prog 300544 broker 300545 listner 300546多址300547 spai_接口300548 spai_适配300549 chimera_ci chimera_客户端接口300550 chimera_pi chimera_处理器调用器300551 teamware_fl teamware_基础级300552 teamware_sl teamware_系统级300553teamware\u ui teamware\u用户界面300554 lprm 300555 MPS日志测量\u代理\u服务器300556 mo\u symdis 300557 retsideprog 300558 slp 300559 slm api 300560 im\u rpc teamconference 300561许可证\u程序许可证300562 stuple stuple\u程序300563 upasswd\u程序300564 Gentran导师安全300565 Gentran导师提供商300566latitude_license_服务器300567 gentranmentorreq1 300568 gentranmentorreq2 300569 gentranmentorreq3 300570 rj_服务器300571 gws rdb 300572 gws mpmd 300573 gws spmd 300574 vwcalcd 300575 vworad 300576 vwsybd 300577 vwave 300578在线_助手300579 internet_助手
300580 spawnd 300581 procmgrg 300582 cfgdbd 300583 logutild 300584 ibis 300585 ibisaux 300586 aapi 300587 rstrt 300588 hbeat 300589 pcspu 300590 empress 300591 sched_server LiveScheduler 300592 path_server LiveScheduler 300593 c2sdmd 300594 c2scf 300595 btsas 300596 sdtas 300597 appie 300598 dmi 300599 pscd panther software corp daemon 300600 sisd 300601 cpwebserver 300602 wwcommo 300603 mx-mie 300604 mx-mie-debug 300605 idmn 300606 ssrv 300607 vpnserver 300608 samserver 300609 sams_server 300610 chrysalis 300611 ddm 300612 ddm-is 300613 mx-bcp-debug 300614 upmrd 300615 upmdsd 300616 res 300617 colortron 300618 zrs 300619 afpsrv 300620 apxft 300621 nrp 300622 hpid 300623 mailwatch 300624 fos bc_fcrb_receiver
300580派生300581 procmgrg 300582 cfgdbd 300583 logutild 300584 ibis 300585 ibisaux 300586 aapi 300587 rstrt 300588 hbeat 300589 pcspu 300590 empress 300591 sched_server LiveScheduler 300592 path_server LiveScheduler 300593 c2sdmd 300594 c2scf 300595 btsas 300596 sdtas 300597 appie 300598 dmi 300599 pscd panther software corp 300600 sisd300601 cpwebserver 300602 wwcommo 300603 mx mie 300604 mx mie debug 300605 idmn 300606 ssrv 300607 VPN服务器300608 samserver 300609 sams_服务器300610 chrysalis 300611 ddm 300612 ddm是300613 mx bcp debug 300614 upmrd 300615 upmdsd 300616 res 300617 colortron 300618 zrs 300619 afpsrv 300620 apxft 300621 nrp 300622 hpid 300623 mailwatch 300624fos bc_fcrb_接收机
300625 cs_sysadmin_svr 300626 cs_controller_svr 300627 nokia_nms_eai 300628 dbg 300629 remex 300630 cs_bind 300631 idm 300632 prpasswd 300633 iw-pw 300634 starrb 300635 Impress_Server 300636 colorstar 300637 gwugui 300638 gwsgui 300639 dai_command_proxy 300640 dai_alarm_server 300641 dai_fui_proxy 300642 spai_command_proxy 300643 spai_alarm_server 300644 iris 300645 hcxttp 300646 updatedb rsched 300647 urnd urn 300648 iqwpsrv 300649 dskutild 300650 online 300651 nlserv 300652 acsm 300653 dg_clar_sormsg 300654 wwpollerrpc 300655 wwmodelrpc 300656 nsprofd 300657 nsdistd 300658 recollect 300659 lssexecd lss_res 300660 lssagend lss_rea 300661 cdinfo 300662 sninsr_addon 300663 mm-sap 300664 ks 300665 psched 300666 tekdvfs 300667 storxll 300668 nisse 300669 lbadvise 300670 atcinstaller 300671 atntstarter 300672 NetML
300625 cs_sysadmin_svr 300626 cs_controller_svr 300627 nokia_nms_eai 300628 dbg 300629 remex 300630 cs_bind 300631 idm 300632 prpasswd 300633 iw pw 300634 starrb 300635 Impress_服务器300636 colorstar 300637 gwugui 300638 gwsgui 300639 dai_命令代理300640 dai_报警服务器300641 dai_fui_代理300642 spai_命令300643 spai报警服务器300644 iris 300645 hcxttp 300646更新版rsched 300647 urnd urn urn 300648 iqwpsrv 300649 dskutild 300650在线300651 nlserv 300652 acsm 300653 dg_clar_sormsg 300654 wwpollerrpc 300655 wwmodelrpc 300656 nsprofd 300657 nsdistd 300658回收300659 lssexecd lss res 300660 lssagend lss rea 300661 cdinfo 300662 SNU addon 300663 mm sap 300664 ks300665 psched 300666 tekdvfs 300667 storxll 300668 nisse 300669 lbadvise 300670 atcinstaller 300671 atntstarter 300672 NetML
300673 tdmesmge 300674 tdmesmgd 300675 tdmesmgt 300676 olm 300677 mediamanagement 300678 rdbprog fieldowsrv 300679 rpwdprog rpwd 300680 sapi-trace 300681 sapi-master-daemon 300682 omdcuprog om-dcu 300683 wwprocmon 300684 tndidprog 300685 rkey_setsecretprog 300686 asdu_server_prog 300687 pwrcntrl 300688 siunixd 300689 wmapi 300690 cross_reference_ole 300691 rtc 300692 disp 300693 sql_compilation_agent 300694 tnsysprog 300695 ius-sapimd 300696 apteam-dx 300697 rmsrpc 300698 seismic_system 300699 remote 300700 tt1_ts_event nokia_nms 300701 fxrs 300702 onlicense 300703 vxkey 300704 dinis 300705 sched2d schedule-2 300706 sched3d schedule-3 300707 sched4d schedule-4 300708 sched5d schedule-5 300709 sched6d schedule-6 300710 sched7d schedule-7 300711 sched8d schedule-8 300712 sched9d schedule-9 300713 adtsqry 300714 adserv 300715 adrepserv 300716 [unknown] 300717 caad 300718 caaui 300719 cescda 300720 vcapiadmin
300673 tdmesmge 300674 tdmesmgd 300675 tdmesmgt 300676 olm 300677媒体管理300678 rdbprog fieldowsrv 300679 rpwdprog rpwd 300680 sapi trace 300681 sapi主守护程序300682 OMDCUROG om dcu 300683 wwprocmon 300684 tndidprog 300685 rkey设置加密程序300686 asdu服务器程序300687 pwrcntrl 300688 siunixd 300689 wmapi 300690交叉参考\u ole 300691 rtc 300692 disp 300693 sql\u编译\u代理300694 tnsysprog 300695 ius sapimd 300696 apteam dx 300697 rmsrpc 300698地震\u系统300699远程300700 tt1\u事件nokia\u nms 300701 fxrs 300702 onlicense 300703 vxkey 300704 dinis 300705 sched2d schedule-2 300706 Sched3 Sched7 Sched4 300708附表5D附表-5 300709附表6D附表-6 300710附表7D附表-7 300711附表8D附表-8 300712附表9D附表-9 300713 adtsqry 300714 adserv 300715 adrepserv 300716[未知]300717 caad 300718 caaui 300719 cescda 300720 vcapiadmin
300721 vcapi20
300722 tcfs
300723 csed
300724 nothand
300725 hacb
300726 nfauth
300727 imlm
300728 bestcomm
300729 lprpasswd
300730 rprpasswd
300731 proplistd
300732 mikomomc
300733 arepa-cas
300734 [unknown]
300735 [unknown]
300736 ando_ts
300737 intermezzo
300738 ftel-sdh-request
300739 ftel-sdh-response
300740 [unknown]
300741 [unknown]
300742 [unknown]
300743 [unknown]
300744 [unknown]
300745 vrc_abb
300746 vrc_comau
300747 vrc_fanuc
300748 vrc_kuka
300749 vrc_reis
300750 hp_sv6d
300751 correntmgr01
300752 correntike
300753 [unknown]
300754 [unknown]
300755 intransa_location
300756 intransa_management
300757 intransa_federation
300758 portprot
300759 ipmiprot
300760 aceapi
300761 f6000pss
300762 vsmapi_program
300763 ubertuple
300764 ctconcrpcif
300765 mfuadmin
300766 aiols
300767 dsmrootd
300768 htdl
300721 vcapi20
300722 tcfs
300723 csed
300724 nothand
300725 hacb
300726 nfauth
300727 imlm
300728 bestcomm
300729 lprpasswd
300730 rprpasswd
300731 proplistd
300732 mikomomc
300733 arepa-cas
300734 [unknown]
300735 [unknown]
300736 ando_ts
300737 intermezzo
300738 ftel-sdh-request
300739 ftel-sdh-response
300740 [unknown]
300741 [unknown]
300742 [unknown]
300743 [unknown]
300744 [unknown]
300745 vrc_abb
300746 vrc_comau
300747 vrc_fanuc
300748 vrc_kuka
300749 vrc_reis
300750 hp_sv6d
300751 correntmgr01
300752 correntike
300753 [unknown]
300754 [unknown]
300755 intransa_location
300756 intransa_management
300757 intransa_federation
300758 portprot
300759 ipmiprot
300760 aceapi
300761 f6000pss
300762 vsmapi_program
300763 ubertuple
300764 ctconcrpcif
300765 mfuadmin
300766 aiols
300767 dsmrootd
300768 htdl
300769 caba
300770 vrc_cosimir
300771 cmhelmd
300772 polynsm
300773 [unknown]
300774 [unknown]
300775 [unknown]
300776 [unknown]
300777 [unknown]
300778 [unknown]
300779 [unknown]
300780 [unknown]
300781 dsmrecalld
300782 [unknown]
300783 [unknown]
300784 twrgcontrol
300785 twrled
300786 twrcfgdb
BMC software 300787-300886
unassigned 300887 - 300999
Sun Microsystems 301000-302000 [ 2000 numbers ]
unassigned 302001-349999
American Airlines 350000 - 350999
Acucobol Inc. 351000 - 351099
The Bristol Group 351100 - 351249
Amteva Technologies 351250 - 351349
351350 wfmMgmtApp
351351 wfmMgmtDataSrv
351352 wfmMgmtFut1
351353 wfmMgmtFut1
351354 wfmAPM
351355 wfmIAMgr
351356 wfmECMgr
351357 wfmLookOut
351358 wfmAgentFut1
351359 wfmAgentFut2
unassigned 351360 - 351406
Sterling Software ITD 351407 csed
351360 sched10d
351361 sched11d
351362 sched12d
351363 sched13d
351364 sched14d
351365 sched15d
351366 sched16d
351367 sched17d
351368 sched18d
351369 sched19d
300769 caba
300770 vrc_cosimir
300771 cmhelmd
300772 polynsm
300773 [unknown]
300774 [unknown]
300775 [unknown]
300776 [unknown]
300777 [unknown]
300778 [unknown]
300779 [unknown]
300780 [unknown]
300781 dsmrecalld
300782 [unknown]
300783 [unknown]
300784 twrgcontrol
300785 twrled
300786 twrcfgdb
BMC software 300787-300886
unassigned 300887 - 300999
Sun Microsystems 301000-302000 [ 2000 numbers ]
unassigned 302001-349999
American Airlines 350000 - 350999
Acucobol Inc. 351000 - 351099
The Bristol Group 351100 - 351249
Amteva Technologies 351250 - 351349
351350 wfmMgmtApp
351351 wfmMgmtDataSrv
351352 wfmMgmtFut1
351353 wfmMgmtFut1
351354 wfmAPM
351355 wfmIAMgr
351356 wfmECMgr
351357 wfmLookOut
351358 wfmAgentFut1
351359 wfmAgentFut2
unassigned 351360 - 351406
Sterling Software ITD 351407 csed
351360 sched10d
351361 sched11d
351362 sched12d
351363 sched13d
351364 sched14d
351365 sched15d
351366 sched16d
351367 sched17d
351368 sched18d
351369 sched19d
351370 sched20d
351371 sched21d
351372 sched22d
351373 sched23d
351374 sched24d
351375 sched25d
351376 sched26d
351377 sched27d
351378 sched28d
351379 sched29d
351380 sched30d
351381 sched31d
351382 sched32d
351383 sched33d
351384 sched34d
351385 sched35d
351386 sched36d
351387 sched37d
351388 sched38d
351389 sched39d
351390 consoleserver
351391 scheduleserver
351392 RDELIVER
351393 REVENTPROG
351394 RSENDEVENTPROG
351395 snapp
351396 snapad
351397 sdsoodb
351398 sdsmain
351399 sdssrv
351400 sdsclnt
351401 sdsreg
351402 fsbatch
351403 fsmonitor
351404 fsdisp
351405 fssession
351406 fslog
351407 svdpappserv
351408 gns
351409 [unkonwn]
351410 [unkonwn]
351411 [unkonwn]
351412 axi
351413 rpcxfr
351414 slm
351415 smbpasswdd
351416 tbdbserv
351417 tbprojserv
351370 sched20d
351371 sched21d
351372 sched22d
351373 sched23d
351374 sched24d
351375 sched25d
351376 sched26d
351377 sched27d
351378 sched28d
351379 sched29d
351380 sched30d
351381 sched31d
351382 sched32d
351383 sched33d
351384 sched34d
351385 sched35d
351386 sched36d
351387 sched37d
351388 sched38d
351389 sched39d
351390 consoleserver
351391 scheduleserver
351392 RDELIVER
351393 REVENTPROG
351394 RSENDEVENTPROG
351395 snapp
351396 snapad
351397 sdsoodb
351398 sdsmain
351399 sdssrv
351400 sdsclnt
351401 sdsreg
351402 fsbatch
351403 fsmonitor
351404 fsdisp
351405 fssession
351406 fslog
351407 svdpappserv
351408 gns
351409 [unkonwn]
351410 [unkonwn]
351411 [unkonwn]
351412 axi
351413 rpcxfr
351414 slm
351415 smbpasswdd
351416 tbdbserv
351417 tbprojserv
351418 genericserver 351419 dynarc_ds 351420 dnscmdr 351421 ipcmdr 351422 faild 351423 failmon 351424 faildebug 351425 [unknown] 351426 [unknown] 351427 siemens_srs 351428 bsproxy 351429 ifsrpc 351430 CesPvcSm 351431 FrPvcSm 351432 AtmPvcSm 351433 radius 351434 auditor 351435 sft 351436 voicemail 351437 kis 351438 SOFTSERV_NOTIFY 351439 dynarpc 351440 hc 351441 iopas 351442 iopcs 351443 iopss 351444 spcnfs 351445 spcvss 351446 matilda_sms 351447 matilda_brs 351448 matilda_dbs 351449 matilda_sps 351450 matilda_svs 351451 matilda_sds 351452 matilda_vvs 351453 matilda_stats 351454 xtrade 351455 mapsvr 351456 hp_graphicsd 351457 berkeley_db berkeley_db_svc 351458 io_server 351459 rpc.niod 351460 rpc.kill 351461 hmdisproxy 351462 smdisproxy 351463 avatard 351464 namu
351418 genericserver 351419 dynarc_ds 351420 dnscmdr 351421 ipcmdr 351422故障351423故障Mon 351424故障调试351425[未知]351426[未知]351427西门子srs 351428 bsproxy 351429 ifsrpc 351430 CesPvcSm 351431 FrPvcSm 351432 AtmPvcSm 351433 radius 351434审计员351435 sft 351436语音信箱351437 kis 351438软件服务通知351439 dynarpc 351440 hc 351441 iopas 351442 iopcs 351443 IOPS351444 spcnfs 351445 SPCVSS351446 matilda\u sms 351447 matilda\u brs 351448 matilda\dbs 351449matilda_sps 351450 matilda_svs 351451 matilda_sds 351452 matilda_vvs 351453 matilda_stats 351454 xtrade 351455 mapsvr 351456 hp_graphicsd 351457 berkeley_db berkeley_db_svc 351458 io_服务器351459 rpc.niod 351460 rpc.kill 351461 hmdiscrypxy 351462 SMdiscrypxy 351463 RD 351464 namu
351465 BMCSess 351466 FENS_Sport 351467 EM_CONFIG 351468 EM_CONFIG_RESP 351469 lodge_proof 351470 ARCserveIT-Queue 351471 ARCserveIT-Device 351472 ARCserveIT-Discover 351473 ARCserveIT-Alert 351474 ARCserveIT-Database 351475 scand1 351476 scand2 351477 scand3 351478 scand4 351479 scand5 351480 dscv 351481 cb_svc 351482 [unknown] 351483 iprobe 351484 omniconf 351485 isan BG Partners 351486 - 351500 351501 mond 351502 iqlremote 351503 iqlalarm unassigned 351504 - 351599 Orion Multisystems 351600-351855 unassigned 351856 - 351899 NSP lab 351900 - 351999 unassigned 351999 - 352232 352233 asautostart 352234 asmediad1 352235 asmediad2 352236 asmediad3 352237 asmediad4 352238 asmediad5 352239 asmediad6 352240 asmediad7 352241 asmediad8 352242 asmediad9 352243 asmediad10 352244 asmediad11 352245 asmediad12 352246 asmediad13 352247 asmediad14 352248 asmediad15 352249 asmediad16 352250 waruser
351465 BMCSess 351466 FENS_Sport 351467 EM_CONFIG 351468 EM_CONFIG RESP 351469 lodge_proof 351470 ARCserveIT队列351471 ARCserveIT设备351472 ARCserveIT发现351473 ARCserveIT警报351474 ARCserveIT数据库351475 scand1 351476 scand2 351477 scand3 351478 scand4 351479 scand5 351480 dscv 351481 cb_svc 351482[未知]351483 iprobe 351484 omniconf 351485 isan BG Partners 351486-351500 351501 mond 351502 iqlremote 351503 iqlalarm未分配351504-351599猎户座多系统351600-351855未分配351856-351899 NSP实验室351900-351999未分配351999-352232 352233作为自动启动352234 asmediad1 352235 asmediad2 352236 asmediad3 352237 asmediad4 352238asmediad5 352239 asmediad6 352240 asmediad7 352241 asmediad8 352242 asmediad9 352243 asmediad10 352244 asmediad12 352246 asmediad13 352247 asmediad14 352248 asmediad15 352249 asmediad16 352250 waruser
352251 warlogd
352252 warsvrmgr
352253 warvfsysd
352254 warftpd
352255 warnfsd
352256 bofproxyc0
352257 bofproxys0
352258 bofproxyc1
352259 bofproxys1
352260 bofproxyc2
352261 bofproxys2
352262 bofproxyc3
352263 bofproxys3
352264 bofproxyc4
352265 bofproxys4
352266 bofproxyc5
352267 bofproxys5
352268 bofproxyc6
352269 bofproxys6
352270 bofproxyc7
352271 bofproxys7
352272 bofproxyc8
352273 bofproxys8
352274 bofproxyc9
352275 bofproxys9
352276 bofproxyca
352277 bofproxysa
352278 bofproxycb
352279 bofproxysb
352280 bofproxycc
352281 bofproxysc
352282 bofproxycd
352283 bofproxysd
352284 bofproxyce
352285 bofproxyse
352286 bofproxycf
352287 bofproxysf
352288 bofproxypo0
352289 bofproxypo1
352290 bofproxypo2
352291 bofproxypo3
352292 bofproxypo4
unassigned 352293-370000
370001 [unknown]
370002 [unknown]
370003 [unknown]
370004 [unknown]
370005 [unknown]
352251 warlogd
352252 warsvrmgr
352253 warvfsysd
352254 warftpd
352255 warnfsd
352256 bofproxyc0
352257 bofproxys0
352258 bofproxyc1
352259 bofproxys1
352260 bofproxyc2
352261 bofproxys2
352262 bofproxyc3
352263 bofproxys3
352264 bofproxyc4
352265 bofproxys4
352266 bofproxyc5
352267 bofproxys5
352268 bofproxyc6
352269 bofproxys6
352270 bofproxyc7
352271 bofproxys7
352272 bofproxyc8
352273 bofproxys8
352274 bofproxyc9
352275 bofproxys9
352276 bofproxyca
352277 bofproxysa
352278 bofproxycb
352279 bofproxysb
352280 bofproxycc
352281 bofproxysc
352282 bofproxycd
352283 bofproxysd
352284 bofproxyce
352285 bofproxyse
352286 bofproxycf
352287 bofproxysf
352288 bofproxypo0
352289 bofproxypo1
352290 bofproxypo2
352291 bofproxypo3
352292 bofproxypo4
unassigned 352293-370000
370001 [unknown]
370002 [unknown]
370003 [unknown]
370004 [unknown]
370005 [unknown]
370006 [unknown]
370007 [unknown]
370008 [unknown]
370009 [unknown]
370010 [unknown]
370011 [unknown]
370012 [unknown]
370013 [unknown]
370014 [unknown]
370015 [unknown]
370016 [unknown]
370017 [unknown]
370018 [unknown]
370019 [unknown]
370020 [unknown]
370021 [unknown]
370022 [unknown]
370023 [unknown]
370024 [unknown]
370025 [unknown]
370026 [unknown]
370027 [unknown]
unassigned 370028 - 379999
380000 opensna
380001 probenet
380002 [unknown]
380003 license
380004 na.3com-remote
380005 na.ntp
380006 probeutil
380007 na.vlb
380008 cds_mhs_agent
380009 cds_x500_agent
380010 cds_mailhub_agent
380011 codex_6500_proxy
380012 codex_6500_trapd
380013 na.nm212
380014 cds_mta_metrics_agent
380015 [unkonwn]
380016 na.caple
380017 codexcapletrap
Swiss Re 380018-380028
380029 ncstat
380030 ncnfsstat
380031 ftams
380032 na.isotp
380033 na.rfc1006
unassigned 380034 - 389999
370006 [unknown]
370007 [unknown]
370008 [unknown]
370009 [unknown]
370010 [unknown]
370011 [unknown]
370012 [unknown]
370013 [unknown]
370014 [unknown]
370015 [unknown]
370016 [unknown]
370017 [unknown]
370018 [unknown]
370019 [unknown]
370020 [unknown]
370021 [unknown]
370022 [unknown]
370023 [unknown]
370024 [unknown]
370025 [unknown]
370026 [unknown]
370027 [unknown]
unassigned 370028 - 379999
380000 opensna
380001 probenet
380002 [unknown]
380003 license
380004 na.3com-remote
380005 na.ntp
380006 probeutil
380007 na.vlb
380008 cds_mhs_agent
380009 cds_x500_agent
380010 cds_mailhub_agent
380011 codex_6500_proxy
380012 codex_6500_trapd
380013 na.nm212
380014 cds_mta_metrics_agent
380015 [unkonwn]
380016 na.caple
380017 codexcapletrap
Swiss Re 380018-380028
380029 ncstat
380030 ncnfsstat
380031 ftams
380032 na.isotp
380033 na.rfc1006
unassigned 380034 - 389999
Epoch Systems 390000 - 390049 Quickturn Systems 390050 - 390065 Team One Systems 390066 - 390075 General Electric CRD 390076 - 390085 TSIG NFS subcommittee 390086 - 390089 SoftLab ab 390090 - 390099 Legato Network Services 390100 - 390115 390116 cdsmonitor 390117 cdslock 390118 cdslicense 390119 shm 390120 rws 390121 cdc Data General 390122 - 390141 Perfect Byte 390142 - 390171 JTS Computer Systems 390172 - 390181 Parametric Technology 390182 - 390191 Voxem 390192 - 390199 Effix Systems 390200 - 390299 Motorola 390300 - 390309 Mobile Data Intl. 390310 - 390325 Physikalisches Institut 390326 - 390330 Ergon Informatik AG 390331 - 390340 Analog Devices Inc. 390341 - 390348 Interphase Corporation 390349 - 390358 NeWsware 390359 - 390374 Qualix Group 390375 - 390379 Xerox Imaging Systems 390380 - 390389 Noble Net 390390 - 390399 Legato Network Services 390400 - 390499 Client Server Tech. 390500 - 390511 Atria 390512 - 390517 GE NMR Instruments 390518 - 390525 Harris Corp. 390526 - 390530 Unisys 390531 - 390562 Aggregate Computing 390563 - 390572 Interactive Data 390573 - 390580 OKG AB 390581 - 390589 K2 Software 390591 - 390594 Collier Jackson 390595 - 390599 Remedy Corporation 390600 - 390699 Mentor Graphics 390700 - 390799 AT&T Bell Labs (Lucent) 390800 - 390899 Xerox 390900 - 390999 Silicon Graphics 391000 - 391063 Data General 391064 - 391095 Computer Support Corp. 391096 - 391099 Quorum Software Systems 391100 - 391199
Epoch Systems 390000-390049 Quickturn Systems 390050-390065 Team One Systems 390066-390075 General Electric CRD 390076-390085 TSIG NFS子委员会390086-390089 SoftLab ab 390090-390099 Legato Network Services 390100-390115 390116 cdsmonitor 390117 cdslock 390118 cdslicense 390119 shm 390120 rws 390121 cdc Data General 390122-390141完美字节390142-390171 JTS计算机系统390172-390181参数化技术390182-390191 Voxem 390192-390199 Effix系统390200-390299摩托罗拉390300-390309移动数据国际390310-390325物理研究所390326-390330 Ergon Informatik AG 390331-390340模拟设备公司390341-390348相间公司390349-390358 NeWsware 390359-390374 Qualix Group 390375-390379 Xerox成像系统390380-390389 Noble Net 390390-390399 Legato网络服务390400-390499客户端服务器技术390500-390511 Atria 390512-390517 GE NMR仪器390518-390525 Harris公司390526-390530 Unisys 390531-390562聚合计算390563-390572交互数据390573-390580 OKG AB 390581-390589 K2软件390591-390594高力杰克逊390595-390599补救公司390600-390699导师图形390700-390799 AT&T贝尔实验室（朗讯）390800-390899施乐390900-390999硅图形391000-391063数据通用391064-391095计算机支持公司391096-391099仲裁软件系统391100-391199
InterLinear Technology 391200 - 391209 Highland Software 391210 - 391229 Boeing Comp. Svcs. 391230 - 391249 IBM Sweden 391250 - 391259 Signature Authority Svc 391260 - 391271 ZUMTOBEL Licht GmbH 391272 - 391283 NOAA/ERL 391284 - 391299 NCR Corp. 391300 - 391399 FTP Software 391400 - 391409 Cadre Technologies 391410 - 391433 Visionware Ltd (UK) 391434 - 391439 IBR-Partner AG 391440 - 391449 CAP Programator AB 391450 - 391459 Reichle+De-Massari AG 391460 - 391474 Swiss Bank Corp (London) 391475 - 391484 Unisys Enterprise Svr 391485 - 391489 Intel - Test Dev. Tech. 391490 - 391499 Ampex 391500 - 391755 391756 naas-spare 391757 naas-admin 391758 isps 391759 isps-admin 391760 mars 391761 mars-admin 391762 attcis_spare0 391763 attcis_spare1 391764 mail-server 391765 mail-server-spare 391766 attcis_spare2 391767 attcis_spare3 391768 attcis_spare4 391769 attcis_spare5 391770 attcis_spare6 391771 attcis_spare7 Integrated Systems, Inc. 391772 - 391779 Parametric Tech., Inc. 391780 - 391789 Ericsson Telecom AB 391790 - 391799 SLAC 391800 - 391849 391850 qhrdata 391851 qhrbackup 391852 minutedata 391853 prefecture 391854 supc 391855 suadmincrw 391856 suadminotas 391857 sumessage 391858 sublock 391859 sumotd
跨线技术391200-391209高地软件391210-391229波音公司。Svcs。391230-391249 IBM瑞典391250-391259签名机构Svc 391260-391271 ZUMTOBEL Licht GmbH 391272-391283 NOAA/ERL 391284-391299 NCR公司391300-391399 FTP软件391400-391409干部技术391410-391433 Visionware有限公司（英国）391434-391439 IBR Partner AG 391440-391449 CAP Programator AB 391450-391459 Reichle+De Massari AG 391460-391474瑞士银行公司（伦敦）391475-391484 Unisys Enterprise Svr 391485-391489英特尔-测试开发技术391490-391499 Ampex 391500-391755 391756 naas备件391757 naas管理员391758 isps 391759 isps管理员391760 mars 391761 mars管理员391762 attcis_spare0 391763 attcis_spare1 391764邮件服务器391765邮件服务器备件391766 attcis_spare2 391767 attcis_spare3 391768attcis_spare4 391769 attcis_spare5 391770 attcis_spare6 391771 attcis_spare7集成系统公司391772-391779参数技术。，公司391780-391789爱立信电信AB 391790-391799 SLAC 391800-391849 391850 qhrdata 391851 qhrbackup 391852分钟数据391853州391854 supc 391855 suadmincrw 391856 suadminotas 391857 SumMessage 391858子区块391859 sumotd
staffware dev. (uk) 391860 - 391869 Staffware Dev. (UK) 391870 - 391879 391880 namesrvr 391881 disksrvr 391882 tapesrvr 391883 migsrvr 391884 pdmsrvr 391885 pvrsrvr 391886 repacksrvr 391887 [unknown] Convex Computer Corp. 391888 - 391951 391952 lookoutsrv 391953 lookoutagnt 391954 lookoutprxy 391955 lookoutsnmp 391956 lookoutrmon 391957 lookoutfut1 391958 lookoutfut2 windward 391959 - 391967 391968 sra_legato 391969 sra_legato_imgsvr 391970 sra_legato_0 391971 sra_legato_1 391972 sra_legato_2 391973 sra_legato_3 391974 sra_legato_4 391975 sra_legato_5 391976 sra_legato_6 391977 sra_legato_7 391978 sra_legato_8 391979 sra_legato_9 Brooktree Corp. 391980 - 391989 Cadence Design Systems 391990 - 391999 J. Frank & Associates 392000 - 392999 Cooperative Solutions 393000 - 393999 Xerox Corp. 394000 - 395023 395024 odbc_sqlretriever 3M 395025 - 395091 Digital Zone Intl. 395092 - 395099 Software Professionals 395100 - 395159 Del Mar Solutions 395160 - 395164 395165 ife-es 395166 ife-resmgr 395167 ife-aes 395168 ife-bite 395169 ife-loader 395170 ife-satcom 395171 ife-seat
staffware dev.（英国）391860-391869 staffware dev.（英国）391870-391879 391880 namesrvr 391881 disksrvr 391882 tapesrvr 391883 Migsrrvr 391884 pdmsrvr 391885 pvrsrvr 391886 repacksrvr 391887[未知]凸形计算机公司391888-391951 391952 lookoutsrv 391953 lookoutagnt 391954 lookoutprxy 391955 lookoutsnmp 391956 Lookoutermon 391957 Lookoutput 391958 Lookoutput 391959-391967 391968 sra_legato 391969 sra_legato_imgsvr 391970 sra_legato_0 391971 sra_legato___1 391972 sra_legato_2 391973 sra_legato_3 39; 1974 sra_legato_legato'1975sra_legato_5 391976 sra_legato_6 391977 sra_legato_7 391978 sra_legato_8 391979 sra_legato_9 Brooktree Corp.391980-391989 Cadence Design Systems 391990-391999 J.Frank&Associates 392000-392999合作解决方案393000-3939393939393999 Xerox Corp.394000-395023 395024 odbc_sqlretriever 3M 395025-395091数字区域国际395092-395099软件专业人士395100-395159 Del Mar Solutions 395160-395164 395165 ife es 395166 ife resmgr 395167 ife aes 395168 ife bite 395169 ife装载机395170 ife卫星通信395171 ife座椅
395172 ife-dbmgr 395173 ife-testmgr 395174 atrium_server 395175 ase_director 395176 ase_agent 395177 ase_hsm 395178 ase_mgr 395179 ase_sim Hewlett-Packard 395180 - 395194 XES, Inc. 395195 - 395199 Unitech Products 395200 - 395249 TransSys 395250 - 395505 Unisys Govt Systems 395506 - 395519 Bellcore 395520 - 395529 IBM 395530 - 395561 AT&T Network Services 395562 - 395571 Data General 395572 - 395577 Swiss Bank Corp 395578 - 395597 Swiss Bank Corp 395598 - 395637 Novell 395638 - 395643 Computer Associates 395644 - 395650 Omneon Video Networks 395651 - 395656 unassigned 395657 - 395908 UK Post Office 395909 - 395924 AEROSPATIALE 395925 - 395944 Result d.o.o. 395945 - 395964 DataTools, Inc. 395965 - 395980 CADIS, Inc. 395981 - 395990 Cummings Group, Inc. 395991 - 395994 Cadre Technologies 395995 - 395999 American Airlines 396000 - 396999 Ericsson Telecom TM Div 397000 - 398023 IBM 398024 - 398028 Toshiba OME Works 398029 - 398033 TUSC Computer Systems 398034 - 398289 AT&T 398290 - 398320 Ontario Hydro 398321 - 398346 Micrion Corporation 398347 - 398364 unassigned 398365 - 398591 Pegasystems, Inc. 398592 - 399616 Spectra Securities Soft 399617 - 399850 QualCom 399851 - 399866 unassigned 399867 - 399884 Altris Software Ltd. 399885 - 399899 ISO/IEC WG11 399900 - 399919 Parametric Technology 399920 - 399949 Dolby Laboratories 399950 - 399981 unassigned 399982 - 399991
395172 ife dbmgr 395173 ife testmgr 395174 atrium_server 395175 ase_director 395176 ase_agent 395177 ase_hsm 395178 ase_mgr 395179 ase_sim Hewlett-Packard 395180-395194 XES，公司395195-395199 Unitech产品395200-395249 TransSys 395250-395505 Unisys政府系统395506-395519 Bellcore 395520-395529 IBM 395530-395561 AT&T网络服务395562-395571数据通用395572-395577瑞士银行395578-395597瑞士银行395598-395637 Novell 395638-395643计算机协会395644-395650 Omnon视频网络395651-395656未分配395657-395908英国邮政局395909-395924 Aerospaceale 395925-395944结果d.o.o.395945-395964数据工具公司395965-395980 CADIS，Inc.395981-395990 Cummings Group，公司395991-395994干部技术395995-395999美国航空公司396000-396999爱立信电信技术分部397000-398023 IBM 398024-398028东芝OME Works 398029-398033 TUSC计算机系统398034-398289 AT&T 398290-398320安大略水电398321-398346密歇根州公司398347-398364未分配398365-398591 Pegaystems，公司398592-399616 Spectra Securities Soft 399617-399850 QualCom 399851-399866未分配399867-399884 Altris Software Ltd.399885-399899 ISO/IEC WG11 399900-399919参数化技术399920-399949杜比实验室399950-399981未分配399982-399991
Xerox PARC 399992 - 399999
#
Next Inc. 200100000 - 200199999
Netwise (RPCtool) 200200000
Concurrent Computer Corp 200200001 - 200200007
AIM Technology 200300000 - 200399999
TGV 200400000 - 200499999
#
# Sun-assigned authentication flavor numbers
#
AUTH_NONE 0 /* no authentication, see RFC 1831 */
/* a.k.a. AUTH_NULL */
AUTH_SYS 1 /* unix style (uid+gids), RFC 1831 */
/* a.k.a. AUTH_UNIX */
AUTH_SHORT 2 /* short hand unix style, RFC 1831 */
AUTH_DH 3 /* des style (encrypted timestamp) */
/* a.k.a. AUTH_DES, see RFC 2695 */
AUTH_KERB 4 /* kerberos auth, see RFC 2695 */
AUTH_RSA 5 /* RSA authentication */
RPCSEC_GSS 6 /* GSS-based RPC security for auth,
integrity and privacy, RPC 5403 */
Xerox PARC 399992 - 399999
#
Next Inc. 200100000 - 200199999
Netwise (RPCtool) 200200000
Concurrent Computer Corp 200200001 - 200200007
AIM Technology 200300000 - 200399999
TGV 200400000 - 200499999
#
# Sun-assigned authentication flavor numbers
#
AUTH_NONE 0 /* no authentication, see RFC 1831 */
/* a.k.a. AUTH_NULL */
AUTH_SYS 1 /* unix style (uid+gids), RFC 1831 */
/* a.k.a. AUTH_UNIX */
AUTH_SHORT 2 /* short hand unix style, RFC 1831 */
AUTH_DH 3 /* des style (encrypted timestamp) */
/* a.k.a. AUTH_DES, see RFC 2695 */
AUTH_KERB 4 /* kerberos auth, see RFC 2695 */
AUTH_RSA 5 /* RSA authentication */
RPCSEC_GSS 6 /* GSS-based RPC security for auth,
integrity and privacy, RPC 5403 */
AUTH_NW 30001 NETWARE AUTH_SEC 200000 TSIG NFS subcommittee AUTH_ESV 200004 SVr4 ES
认证NW 30001 NETWARE认证SEC 200000 TSIG NFS子委员会认证ESV 200004 SVr4 ES
AUTH_NQNFS 300000 Univ. of Guelph - Not Quite NFS
AUTH_GSSAPI 300001 OpenVision <john.linn@ov.com>
AUTH_ILU_UGEN 300002 Xerox <janssen@parc.xerox.com>
- ILU Unsecured Generic Identity
#
# Small blocks are assigned out of the 39xxxx series of numbers
#
AUTH_SPNEGO 390000
390000 - 390255 NFS 'pseudo' flavors for RPCSEC_GSS
390003 - kerberos_v5 authentication, RFC 2623
390004 - kerberos_v5 with data integrity, RFC 2623
390005 - kerberos_v5 with data privacy, RFC 2623
AUTH_NQNFS 300000 Univ. of Guelph - Not Quite NFS
AUTH_GSSAPI 300001 OpenVision <john.linn@ov.com>
AUTH_ILU_UGEN 300002 Xerox <janssen@parc.xerox.com>
- ILU Unsecured Generic Identity
#
# Small blocks are assigned out of the 39xxxx series of numbers
#
AUTH_SPNEGO 390000
390000 - 390255 NFS 'pseudo' flavors for RPCSEC_GSS
390003 - kerberos_v5 authentication, RFC 2623
390004 - kerberos_v5 with data integrity, RFC 2623
390005 - kerberos_v5 with data privacy, RFC 2623
200000000 Reserved 200100000 NeXT Inc.
200000000预留200100000 NeXT公司。
Normative References
规范性引用文件
[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月。
[RFC2203] Eisler, M., Chiu, A., and L. Ling, "RPCSEC_GSS Protocol Specification", RFC 2203, September 1997.
[RFC2203]Eisler，M.，Chiu，A.，和L.Ling，“RPCSEC_GSS协议规范”，RFC 2203，1997年9月。
[RFC4506] Eisler, M., Ed., "XDR: External Data Representation Standard", STD 67, RFC 4506, May 2006.
[RFC4506]艾斯勒，M.，编辑，“XDR：外部数据表示标准”，STD 67，RFC 4506，2006年5月。
Informative References
资料性引用
[DH] Diffie & Hellman, "New Directions in Cryptography", IEEE Transactions on Information Theory IT-22, November 1976.
[DH]Diffie&Hellman，“密码学的新方向”，IEEE信息论交易IT-22，1976年11月。
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, August 1980.
[RFC0768]Postel，J.，“用户数据报协议”，STD 6，RFC 768，1980年8月。
[RFC0793] Postel, J., "Transmission Control Protocol", STD 7, RFC 793, September 1981.
[RFC0793]Postel，J.，“传输控制协议”，标准7，RFC 793，1981年9月。
[RFC1094] Sun Microsystems, "NFS: Network File System Protocol specification", RFC 1094, March 1989.
[RFC1094]Sun Microsystems，“NFS：网络文件系统协议规范”，RFC10941989年3月。
[RFC1813] Callaghan, B., Pawlowski, B., and P. Staubach, "NFS Version 3 Protocol Specification", RFC 1813, June 1995.
[RFC1813]Callaghan，B.，Pawlowski，B.，和P.Staubach，“NFS版本3协议规范”，RFC 1813，1995年6月。
[RFC1831] Srinivasan, R., "RPC: Remote Procedure Call Protocol Specification Version 2", RFC 1831, August 1995.
[RFC1831]Srinivasan，R.，“RPC：远程过程调用协议规范版本2”，RFC18311995年8月。
[RFC1833] Srinivasan, R., "Binding Protocols for ONC RPC Version 2", RFC 1833, August 1995.
[RFC1833]Srinivasan，R.，“ONC RPC版本2的绑定协议”，RFC 1833，1995年8月。
[RFC2623] Eisler, M., "NFS Version 2 and Version 3 Security Issues and the NFS Protocol's Use of RPCSEC_GSS and Kerberos V5", RFC 2623, June 1999.
[RFC2623]Eisler，M.，“NFS版本2和版本3的安全问题以及NFS协议对RPCSEC_GSS和Kerberos V5的使用”，RFC 2623，1999年6月。
[RFC2695] Chiu, A., "Authentication Mechanisms for ONC RPC", RFC 2695, September 1999.
[RFC2695]Chiu，A.，“ONC RPC的认证机制”，RFC 26951999年9月。
[RFC2743] Linn, J., "Generic Security Service Application Program Interface Version 2, Update 1", RFC 2743, January 2000.
[RFC2743]Linn，J.，“通用安全服务应用程序接口版本2，更新1”，RFC 2743，2000年1月。
[RFC3530] Shepler, S., Callaghan, B., Robinson, D., Thurlow, R., Beame, C., Eisler, M., and D. Noveck, "Network File System (NFS) version 4 Protocol", RFC 3530, April 2003.
[RFC3530]Shepler，S.，Callaghan，B.，Robinson，D.，Thurlow，R.，Beame，C.，Eisler，M.，和D.Noveck，“网络文件系统（NFS）版本4协议”，RFC 3530，2003年4月。
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月。
[VMTP] Cheriton, D., "VMTP: Versatile Message Transaction Protocol", Preliminary Version 0.3, Stanford University, January 1987.
[VMTP]Cheriton，D.，“VMTP：通用消息事务协议”，初步版本0.3，斯坦福大学，1987年1月。
[XRPC] Birrell, A. D. & B. J. Nelson, "Implementing Remote Procedure Calls", XEROX CSL-83-7, October 1983.
[XRPC]Birrell，A.D.和B.J.Nelson，“实现远程过程调用”，施乐CSL-83-71983年10月。
Author's Address
作者地址
Robert Thurlow Sun Microsystems, Inc. 500 Eldorado Boulevard, UBRM05-171 Broomfield, CO 80021
Robert Thurlow Sun Microsystems，Inc.美国科罗拉多州布鲁姆菲尔德市埃尔多拉多大道500号，UBRM05-171，邮编80021
Phone: 877-718-3419 EMail: robert.thurlow@sun.com
电话：877-718-3419电子邮件：罗伯特。thurlow@sun.com