idnits 2.17.1 draft-ietf-nfsv4-rfc1831bis-13.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.i or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? -- It seems you're using the 'non-IETF stream' Licence Notice instead Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([RFC1831]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. -- The abstract seems to indicate that this document obsoletes RFC1831, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 5, 2009) is 5531 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Draft Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '0' on line 618 ** Downref: Normative reference to an Proposed Standard RFC: RFC 2203 -- Obsolete informational reference (is this intentional?): RFC 793 (Obsoleted by RFC 9293) -- Obsolete informational reference (is this intentional?): RFC 1831 (Obsoleted by RFC 5531) -- Obsolete informational reference (is this intentional?): RFC 3530 (Obsoleted by RFC 7530) -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network File System Version 4 Working Group R. Thurlow 3 Internet-Draft Sun Microsystems 4 Intended status: Draft Standard 5 Obsoletes: 1831 6 Expires: September 5, 2009 March 5, 2009 8 RPC: Remote Procedure Call Protocol Specification Version 2 9 draft-ietf-nfsv4-rfc1831bis-13.txt 11 Status of this Memo 13 This Internet-Draft is submitted to IETF in full conformance with the 14 provisions of BCP 78 and BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/1id-abstracts.html 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html 32 This document will expire in July, 2009. 34 Copyright Notice 36 Copyright (c) 2009 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. 46 Abstract 48 This document describes the ONC (Open Network Computing) Remote 49 Procedure Call (ONC RPC Version 2) protocol as it is currently 50 deployed and accepted. This document obsoletes [RFC1831]. 52 Requirements Language 54 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 55 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 56 document are to be interpreted as described in [RFC2119]. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 1 61 2. Changes since RFC 1831 . . . . . . . . . . . . . . . . . . . 1 62 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 1 63 4. The RPC Model . . . . . . . . . . . . . . . . . . . . . . . 1 64 5. Transports and Semantics . . . . . . . . . . . . . . . . . . 1 65 6. Binding and Rendezvous Independence . . . . . . . . . . . . 1 66 7. Authentication . . . . . . . . . . . . . . . . . . . . . . . 1 67 8. RPC Protocol Requirements . . . . . . . . . . . . . . . . . 1 68 8.1. RPC Programs and Procedures . . . . . . . . . . . . . . . 1 69 8.2. Authentication, Integrity and Privacy . . . . . . . . . . 1 70 8.3. Program Number Assignment . . . . . . . . . . . . . . . . 1 71 8.4. Other Uses of the RPC Protocol . . . . . . . . . . . . . . 1 72 8.4.1. Batching . . . . . . . . . . . . . . . . . . . . . . . . 1 73 8.4.2. Broadcast Remote Procedure Calls . . . . . . . . . . . . 1 74 9. The RPC Message Protocol . . . . . . . . . . . . . . . . . . 1 75 10. Authentication Protocols . . . . . . . . . . . . . . . . . 1 76 10.1. Null Authentication . . . . . . . . . . . . . . . . . . . 1 77 11. Record Marking Standard . . . . . . . . . . . . . . . . . . 1 78 12. The RPC Language . . . . . . . . . . . . . . . . . . . . . 1 79 12.1. An Example Service Described in the RPC Language . . . . 1 80 12.2. The RPC Language Specification . . . . . . . . . . . . . 1 81 12.3. Syntax Notes . . . . . . . . . . . . . . . . . . . . . . 1 82 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . 1 83 13.1. Numbering Requests to IANA . . . . . . . . . . . . . . . 1 84 13.2. Protecting Past Assignments . . . . . . . . . . . . . . . 1 85 13.3. RPC Number Assignment . . . . . . . . . . . . . . . . . . 1 86 13.3.1. To be assigned by IANA . . . . . . . . . . . . . . . . 1 87 13.3.2. Defined by local administrator . . . . . . . . . . . . 1 88 13.3.3. Transient block . . . . . . . . . . . . . . . . . . . . 1 89 13.3.4. Reserved block . . . . . . . . . . . . . . . . . . . . 1 90 13.3.5. RPC Number Sub-Blocks . . . . . . . . . . . . . . . . . 1 91 13.4. RPC Authentication Flavor Number Assignment . . . . . . . 1 92 13.4.1. Assignment Policy . . . . . . . . . . . . . . . . . . . 1 93 13.4.2. Auth Flavors vs. Pseudo-flavors . . . . . . . . . . . . 1 94 13.5. Authentication Status Number Assignment . . . . . . . . . 1 95 13.5.1. Assignment Policy . . . . . . . . . . . . . . . . . . . 1 96 14. Security Considerations . . . . . . . . . . . . . . . . . . 1 97 15. Appendix A: System Authentication . . . . . . . . . . . . . 1 98 16. Appendix B: Requesting RPC-related numbers from IANA . . . 1 99 17. Appendix C: Current number assignments . . . . . . . . . . 1 100 18. Normative References . . . . . . . . . . . . . . . . . . . 1 101 19. Informative References . . . . . . . . . . . . . . . . . . 1 102 20. Author's Address . . . . . . . . . . . . . . . . . . . . . 1 104 1. Introduction 106 This document specifies version two of the message protocol used in 107 ONC Remote Procedure Call (RPC). The message protocol is specified 108 with the eXternal Data Representation (XDR) language [RFC4506]. This 109 document assumes that the reader is familiar with XDR. It does not 110 attempt to justify remote procedure calls systems or describe their 111 use. The paper by Birrell and Nelson [XRPC] is recommended as an 112 excellent background for the remote procedure call concept. 114 2. Changes since RFC 1831 116 This document obsoletes RFC 1831 as the authoritative document 117 describing RPC, without introducing any over-the-wire protocol 118 changes. The main changes from RFC 1831 are: 120 o Addition of an Appendix which describes how an implementor can 121 request new RPC program numbers, authentication flavor numbers 122 and authentication status numbers from IANA, rather than from 123 Sun Microsystems 125 o Addition of an "IANA Considerations" section which describes 126 past number assignment policy and how IANA is intended to assign 127 them in the future 129 o Clarification of the RPC Language Specification to match current 130 usage 132 o Enhancement of the "Security Considerations" section to reflect 133 experience with strong security flavors 135 o Specification of new authentication errors that are in common 136 use in modern RPC implementations 138 o Updates for the latest IETF intellectual property statements 140 3. Terminology 142 This document discusses clients, calls, servers, replies, services, 143 programs, procedures, and versions. Each remote procedure call has 144 two sides: an active client side that makes the call to a server, 145 which sends back a reply. A network service is a collection of one 146 or more remote programs. A remote program implements one or more 147 remote procedures; the procedures, their parameters, and results are 148 documented in the specific program's protocol specification. A 149 server may support more than one version of a remote program in order 150 to be compatible with changing protocols. 152 For example, a network file service may be composed of two programs. 153 One program may deal with high-level applications such as file system 154 access control and locking. The other may deal with low-level file 155 input and output and have procedures like "read" and "write". A 156 client of the network file service would call the procedures 157 associated with the two programs of the service on behalf of the 158 client. 160 The terms client and server only apply to a particular transaction; a 161 particular hardware entity (host) or software entity (process or 162 program) could operate in both roles at different times. For 163 example, a program that supplies remote execution service could also 164 be a client of a network file service. 166 4. The RPC Model 168 The ONC RPC protocol is based on the remote procedure call model, 169 which is similar to the local procedure call model. In the local 170 case, the caller places arguments to a procedure in some well- 171 specified location (such as a register window). It then transfers 172 control to the procedure, and eventually regains control. At that 173 point, the results of the procedure are extracted from the well- 174 specified location, and the caller continues execution. 176 The remote procedure call model is similar. One thread of control 177 logically winds through two processes: the caller's process, and a 178 server's process. The caller process first sends a call message to 179 the server process and waits (blocks) for a reply message. The call 180 message includes the procedure's parameters, and the reply message 181 includes the procedure's results. Once the reply message is 182 received, the results of the procedure are extracted, and caller's 183 execution is resumed. 185 On the server side, a process is dormant awaiting the arrival of a 186 call message. When one arrives, the server process extracts the 187 procedure's parameters, computes the results, sends a reply message, 188 and then awaits the next call message. 190 In this model, only one of the two processes is active at any given 191 time. However, this model is only given as an example. The ONC RPC 192 protocol makes no restrictions on the concurrency model implemented, 193 and others are possible. For example, an implementation may choose 194 to have RPC calls be asynchronous, so that the client may do useful 195 work while waiting for the reply from the server. Another 196 possibility is to have the server create a separate task to process 197 an incoming call, so that the original server can be free to receive 198 other requests. 200 There are a few important ways in which remote procedure calls differ 201 from local procedure calls: 203 o Error handling: failures of the remote server or network must be 204 handled when using remote procedure calls. 206 o Global variables and side-effects: since the server does not 207 have access to the client's address space, hidden arguments 208 cannot be passed as global variables or returned as side 209 effects. 211 o Performance: remote procedures usually operate one or more 212 orders of magnitude slower than local procedure calls. 214 o Authentication: since remote procedure calls can be transported 215 over unsecured networks, authentication may be necessary. 216 Authentication prevents one entity from masquerading as some 217 other entity. 219 The conclusion is that even though there are tools to automatically 220 generate client and server libraries for a given service, protocols 221 must still be designed carefully. 223 5. Transports and Semantics 225 The RPC protocol can be implemented on several different transport 226 protocols. The scope of the definition of the RPC protocol excludes 227 how a message is passed from one process to another, and includes 228 only the specification and interpretation of messages. However, the 229 application may wish to obtain information about (and perhaps control 230 over) the transport layer through an interface not specified in this 231 document. For example, the transport protocol may impose a 232 restriction on the maximum size of RPC messages, or it may be 233 stream-oriented like TCP [RFC793] with no size limit. The client and 234 server must agree on their transport protocol choices. 236 It is important to point out that RPC does not try to implement any 237 kind of reliability and that the application may need to be aware of 238 the type of transport protocol underneath RPC. If it knows it is 239 running on top of a reliable transport such as TCP, then most of the 240 work is already done for it. On the other hand, if it is running on 241 top of an unreliable transport such as UDP [RFC768], it must 242 implement its own time-out, retransmission, and duplicate detection 243 policies as the RPC protocol does not provide these services. 245 Because of transport independence, the RPC protocol does not attach 246 specific semantics to the remote procedures or their execution 247 requirements. Semantics can be inferred from (but should be 248 explicitly specified by) the underlying transport protocol. For 249 example, consider RPC running on top of an unreliable transport such 250 as UDP. If an application retransmits RPC call messages after time- 251 outs, and does not receive a reply, it cannot infer anything about 252 the number of times the procedure was executed. If it does receive a 253 reply, then it can infer that the procedure was executed at least 254 once. 256 A server may wish to remember previously granted requests from a 257 client and not regrant them in order to insure some degree of 258 execute-at-most-once semantics. A server can do this by taking 259 advantage of the transaction ID that is packaged with every RPC 260 message. The main use of this transaction ID is by the client RPC 261 entity in matching replies to calls. However, a client application 262 may choose to reuse its previous transaction ID when retransmitting a 263 call. The server may choose to remember this ID after executing a 264 call and not execute calls with the same ID in order to achieve some 265 degree of execute-at-most-once semantics. The server is not allowed 266 to examine this ID in any other way except as a test for equality. 268 On the other hand, if using a "reliable" transport such as TCP, the 269 application can infer from a reply message that the procedure was 270 executed exactly once, but if it receives no reply message, it cannot 271 assume that the remote procedure was not executed. Note that even if 272 a connection-oriented protocol like TCP is used, an application still 273 needs time-outs and reconnection to handle server crashes. 275 There are other possibilities for transports besides datagram- or 276 connection-oriented protocols. For example, a request-reply protocol 277 such as [VMTP] is perhaps a natural transport for RPC. ONC RPC 278 currently uses both TCP and UDP transport protocols. Section 10 279 (Record Marking Standard) describes the mechanism employed by ONC RPC 280 to utilize a connection-oriented, stream-oriented transport such as 281 TCP. The mechanism by which future transports having different 282 structural characteristics should be used to transfer ONC RPC 283 messages should be specified by means of a standards-track RFC, once 284 such additional transports are defined. 286 6. Binding and Rendezvous Independence 288 The act of binding a particular client to a particular service and 289 transport parameters is NOT part of this RPC protocol specification. 290 This important and necessary function is left up to some higher-level 291 software. 293 Implementors could think of the RPC protocol as the jump-subroutine 294 instruction ("JSR") of a network; the loader (binder) makes JSR 295 useful, and the loader itself uses JSR to accomplish its task. 297 Likewise, the binding software makes RPC useful, possibly using RPC 298 to accomplish this task. 300 7. Authentication 302 The RPC protocol provides the fields necessary for a client to 303 identify itself to a service, and vice-versa, in each call and reply 304 message. Security and access control mechanisms can be built on top 305 of this message authentication. Several different authentication 306 protocols can be supported. A field in the RPC header indicates 307 which protocol is being used. More information on specific 308 authentication protocols is in section 8.2: "Authentication, 309 Integrity and Privacy". 311 8. RPC Protocol Requirements 313 The RPC protocol must provide for the following: 315 o Unique specification of a procedure to be called. 317 o Provisions for matching response messages to request messages. 319 o Provisions for authenticating the caller to service and vice- 320 versa. 322 Besides these requirements, features that detect the following are 323 worth supporting because of protocol roll-over errors, implementation 324 bugs, user error, and network administration: 326 o RPC protocol mismatches. 328 o Remote program protocol version mismatches. 330 o Protocol errors (such as misspecification of a procedure's 331 parameters). 333 o Reasons why remote authentication failed. 335 o Any other reasons why the desired procedure was not called. 337 8.1. RPC Programs and Procedures 339 The RPC call message has three unsigned integer fields -- remote 340 program number, remote program version number, and remote procedure 341 number -- which uniquely identify the procedure to be called. 342 Program numbers are administered by a central authority (IANA). Once 343 implementors have a program number, they can implement their remote 344 program; the first implementation would most likely have the version 345 number 1 but MUST NOT be the number zero. Because most new protocols 346 evolve, a version field of the call message identifies which version 347 of the protocol the caller is using. Version numbers enable support 348 of both old and new protocols through the same server process. 350 The procedure number identifies the procedure to be called. These 351 numbers are documented in the specific program's protocol 352 specification. For example, a file service's protocol specification 353 may state that its procedure number 5 is "read" and procedure number 354 12 is "write". 356 Just as remote program protocols may change over several versions, 357 the actual RPC message protocol could also change. Therefore, the 358 call message also has in it the RPC version number, which is always 359 equal to two for the version of RPC described here. 361 The reply message to a request message has enough information to 362 distinguish the following error conditions: 364 o The remote implementation of RPC does not support protocol 365 version 2. The lowest and highest supported RPC version numbers 366 are returned. 368 o The remote program is not available on the remote system. 370 o The remote program does not support the requested version 371 number. The lowest and highest supported remote program version 372 numbers are returned. 374 o The requested procedure number does not exist. (This is usually 375 a client side protocol or programming error.) 377 o The parameters to the remote procedure appear to be garbage from 378 the server's point of view. (Again, this is usually caused by a 379 disagreement about the protocol between client and service.) 381 8.2. Authentication, Integrity and Privacy 383 Provisions for authentication of caller to service and vice-versa are 384 provided as a part of the RPC protocol. The call message has two 385 authentication fields, the credential and verifier. The reply 386 message has one authentication field, the response verifier. The RPC 387 protocol specification defines all three fields to be the following 388 opaque type (in the eXternal Data Representation (XDR) language 389 [RFC4506]): 391 enum auth_flavor { 392 AUTH_NONE = 0, 393 AUTH_SYS = 1, 394 AUTH_SHORT = 2, 395 AUTH_DH = 3, 396 RPCSEC_GSS = 6 397 /* and more to be defined */ 398 }; 400 struct opaque_auth { 401 auth_flavor flavor; 402 opaque body<400>; 403 }; 405 In other words, any "opaque_auth" structure is an "auth_flavor" 406 enumeration followed by up to 400 bytes which are opaque to 407 (uninterpreted by) the RPC protocol implementation. 409 The interpretation and semantics of the data contained within the 410 authentication fields is specified by individual, independent 411 authentication protocol specifications. 413 If authentication parameters were rejected, the reply message 414 contains information stating why they were rejected. 416 As demonstrated by RPCSEC_GSS, it is possible for an "auth_flavor" 417 to also support integrity and privacy. 419 8.3. Program Number Assignment 421 Program numbers are given out in groups according to the following 422 chart: 424 0x00000000 Reserved 425 0x00000001 - 0x1fffffff To be assigned by IANA 426 0x20000000 - 0x3fffffff Defined by local administrator 427 (some blocks assigned here) 428 0x40000000 - 0x5fffffff Transient 429 0x60000000 - 0x7effffff Reserved 430 0x7f000000 - 0x7fffffff Assignment outstanding 431 0x80000000 - 0xffffffff Reserved 433 The first group is a range of numbers administered by IANA and should 434 be identical for all sites. The second range is for applications 435 peculiar to a particular site. This range is intended primarily for 436 debugging new programs. When a site develops an application that 437 might be of general interest, that application should be given an 438 assigned number in the first range. Application developers may apply 439 for blocks of RPC program numbers in the first range by methods 440 described in Appendix B. The third group is for applications that 441 generate program numbers dynamically. The final groups are reserved 442 for future use, and should not be used. 444 8.4. Other Uses of the RPC Protocol 446 The intended use of this protocol is for calling remote procedures. 447 Normally, each call message is matched with a reply message. 448 However, the protocol itself is a message-passing protocol with which 449 other (non-procedure call) protocols can be implemented. 451 8.4.1. Batching 453 Batching is useful when a client wishes to send an arbitrarily large 454 sequence of call messages to a server. Batching typically uses 455 reliable byte stream protocols (like TCP) for its transport. In the 456 case of batching, the client never waits for a reply from the server, 457 and the server does not send replies to batch calls. A sequence of 458 batch calls is usually terminated by a legitimate remote procedure 459 call operation in order to flush the pipeline and get positive 460 acknowledgement. 462 8.4.2. Broadcast Remote Procedure Calls 464 In broadcast protocols, the client sends a broadcast call to the 465 network and waits for numerous replies. This requires the use of 466 packet-based protocols (like UDP) as its transport protocol. Servers 467 that support broadcast protocols usually respond only when the call 468 is successfully processed and are silent in the face of errors, but 469 this varies with the application. 471 The principles of broadcast RPC also apply to multicasting - an RPC 472 request can be sent to a multicast address. 474 9. The RPC Message Protocol 476 This section defines the RPC message protocol in the XDR data 477 description language [RFC4506]. 479 enum msg_type { 480 CALL = 0, 481 REPLY = 1 482 }; 484 A reply to a call message can take on two forms: The message was 485 either accepted or rejected. 487 enum reply_stat { 488 MSG_ACCEPTED = 0, 489 MSG_DENIED = 1 490 }; 492 Given that a call message was accepted, the following is the status 493 of an attempt to call a remote procedure. 495 enum accept_stat { 496 SUCCESS = 0, /* RPC executed successfully */ 497 PROG_UNAVAIL = 1, /* remote hasn't exported program */ 498 PROG_MISMATCH = 2, /* remote can't support version # */ 499 PROC_UNAVAIL = 3, /* program can't support procedure */ 500 GARBAGE_ARGS = 4, /* procedure can't decode params */ 501 SYSTEM_ERR = 5 /* e.g. memory allocation failure */ 502 }; 504 Reasons why a call message was rejected: 506 enum reject_stat { 507 RPC_MISMATCH = 0, /* RPC version number != 2 */ 508 AUTH_ERROR = 1 /* remote can't authenticate caller */ 509 }; 511 Why authentication failed: 513 enum auth_stat { 514 AUTH_OK = 0, /* success */ 515 /* 516 * failed at remote end 517 */ 518 AUTH_BADCRED = 1, /* bad credential (seal broken) */ 519 AUTH_REJECTEDCRED = 2, /* client must begin new session */ 520 AUTH_BADVERF = 3, /* bad verifier (seal broken) */ 521 AUTH_REJECTEDVERF = 4, /* verifier expired or replayed */ 522 AUTH_TOOWEAK = 5, /* rejected for security reasons */ 523 /* 524 * failed locally 525 */ 526 AUTH_INVALIDRESP = 6, /* bogus response verifier */ 527 AUTH_FAILED = 7, /* reason unknown */ 528 /* 529 * AUTH_KERB errors; deprecated. See [RFC2695] 530 */ 531 AUTH_KERB_GENERIC = 8, /* kerberos generic error */ 532 AUTH_TIMEEXPIRE = 9, /* time of credential expired */ 533 AUTH_TKT_FILE = 10, /* problem with ticket file */ 534 AUTH_DECODE = 11, /* can't decode authenticator */ 535 AUTH_NET_ADDR = 12, /* wrong net address in ticket */ 536 /* 537 * RPCSEC_GSS GSS related errors 538 */ 539 RPCSEC_GSS_CREDPROBLEM = 13, /* no credentials for user */ 540 RPCSEC_GSS_CTXPROBLEM = 14 /* problem with context */ 541 }; 543 As new authentication mechanisms are added, there may be a need for 544 more status codes to support them. IANA will hand out new auth_stat 545 numbers on a simple first-come, first-served basis as defined in the 546 "IANA Considerations" and Appendix B. 548 The RPC message: 550 All messages start with a transaction identifier, xid, followed by a 551 two-armed discriminated union. The union's discriminant is a 552 msg_type which switches to one of the two types of the message. The 553 xid of a REPLY message always matches that of the initiating CALL 554 message. NB: The xid field is only used for clients matching reply 555 messages with call messages or for servers detecting retransmissions; 556 the service side cannot treat this id as any type of sequence number. 558 struct rpc_msg { 559 unsigned int xid; 560 union switch (msg_type mtype) { 561 case CALL: 562 call_body cbody; 563 case REPLY: 564 reply_body rbody; 565 } body; 566 }; 568 Body of an RPC call: 570 In version 2 of the RPC protocol specification, rpcvers MUST be equal 571 to 2. The fields prog, vers, and proc specify the remote program, 572 its version number, and the procedure within the remote program to be 573 called. After these fields are two authentication parameters: cred 574 (authentication credential) and verf (authentication verifier). The 575 two authentication parameters are followed by the parameters to the 576 remote procedure, which are specified by the specific program 577 protocol. 579 The purpose of the authentication verifier is to validate the 580 authentication credential. Note that these two items are 581 historically separate, but are always used together as one logical 582 entity. 584 struct call_body { 585 unsigned int rpcvers; /* must be equal to two (2) */ 586 unsigned int prog; 587 unsigned int vers; 588 unsigned int proc; 589 opaque_auth cred; 590 opaque_auth verf; 591 /* procedure specific parameters start here */ 592 }; 594 Body of a reply to an RPC call: 596 union reply_body switch (reply_stat stat) { 597 case MSG_ACCEPTED: 598 accepted_reply areply; 599 case MSG_DENIED: 600 rejected_reply rreply; 601 } reply; 603 Reply to an RPC call that was accepted by the server: 605 There could be an error even though the call was accepted. The first 606 field is an authentication verifier that the server generates in 607 order to validate itself to the client. It is followed by a union 608 whose discriminant is an enum accept_stat. The SUCCESS arm of the 609 union is protocol specific. The PROG_UNAVAIL, PROC_UNAVAIL, 610 GARBAGE_ARGS, and SYSTEM_ERR arms of the union are void. The 611 PROG_MISMATCH arm specifies the lowest and highest version numbers of 612 the remote program supported by the server. 614 struct accepted_reply { 615 opaque_auth verf; 616 union switch (accept_stat stat) { 617 case SUCCESS: 618 opaque results[0]; 619 /* 620 * procedure-specific results start here 621 */ 622 case PROG_MISMATCH: 623 struct { 624 unsigned int low; 625 unsigned int high; 626 } mismatch_info; 627 default: 628 /* 629 * Void. Cases include PROG_UNAVAIL, PROC_UNAVAIL, 630 * GARBAGE_ARGS, and SYSTEM_ERR. 631 */ 632 void; 633 } reply_data; 634 }; 636 Reply to an RPC call that was rejected by the server: 638 The call can be rejected for two reasons: either the server is not 639 running a compatible version of the RPC protocol (RPC_MISMATCH), or 640 the server rejects the identity of the caller (AUTH_ERROR). In case 641 of an RPC version mismatch, the server returns the lowest and highest 642 supported RPC version numbers. In case of invalid authentication, 643 failure status is returned. 645 union rejected_reply switch (reject_stat stat) { 646 case RPC_MISMATCH: 647 struct { 648 unsigned int low; 649 unsigned int high; 650 } mismatch_info; 651 case AUTH_ERROR: 652 auth_stat stat; 653 }; 655 10. Authentication Protocols 657 As previously stated, authentication parameters are opaque, but 658 open-ended to the rest of the RPC protocol. This section defines two 659 standard "flavors" of authentication. Implementors are free to 660 invent new authentication types, with the same rules of flavor number 661 assignment as there is for program number assignment. The "flavor" 662 of a credential or verifier refers to the value of the "flavor" field 663 in the opaque_auth structure. Flavor numbers, like RPC program 664 numbers, are also administered centrally, and developers may assign 665 new flavor numbers by methods described in Appendix B. Credentials 666 and verifiers are represented as variable length opaque data (the 667 "body" field in the opaque_auth structure). 669 In this document, two flavors of authentication are described. Of 670 these, Null authentication (described in the next subsection) is 671 mandatory - it MUST be available in all implementations. System 672 authentication (AUTH_SYS) is described in Appendix A. Implementors 673 MAY include AUTH_SYS in their implementations to support existing 674 applications. See "Security Considerations" for information about 675 other, more secure, authentication flavors. 677 10.1. Null Authentication 679 Often calls must be made where the client does not care about its 680 identity or the server does not care who the client is. In this 681 case, the flavor of the RPC message's credential, verifier, and reply 682 verifier is "AUTH_NONE". Opaque data associated with "AUTH_NONE" is 683 undefined. It is recommended that the length of the opaque data be 684 zero. 686 11. Record Marking Standard 688 When RPC messages are passed on top of a byte stream transport 689 protocol (like TCP), it is necessary to delimit one message from 690 another in order to detect and possibly recover from protocol errors. 691 This is called record marking (RM). One RPC message fits into one RM 692 record. 694 A record is composed of one or more record fragments. A record 695 fragment is a four-byte header followed by 0 to (2**31) - 1 bytes of 696 fragment data. The bytes encode an unsigned binary number; as with 697 XDR integers, the byte order is from highest to lowest. The number 698 encodes two values -- a boolean which indicates whether the fragment 699 is the last fragment of the record (bit value 1 implies the fragment 700 is the last fragment) and a 31-bit unsigned binary value which is the 701 length in bytes of the fragment's data. The boolean value is the 702 highest-order bit of the header; the length is the 31 low-order bits. 703 (Note that this record specification is NOT in XDR standard form!) 705 12. The RPC Language 707 Just as there was a need to describe the XDR data-types in a formal 708 language, there is also need to describe the procedures that operate 709 on these XDR data-types in a formal language as well. The RPC 710 Language is an extension to the XDR language, with the addition of 711 "program", "procedure", and "version" declarations. The keywords 712 "program" and "version" are reserved in the RPC Language, and 713 implementations of XDR compilers MAY reserve these keywords even when 714 provided pure XDR, non-RPC, descriptions. The following example is 715 used to describe the essence of the language. 717 12.1. An Example Service Described in the RPC Language 719 Here is an example of the specification of a simple ping program. 721 program PING_PROG { 722 /* 723 * Latest and greatest version 724 */ 726 version PING_VERS_PINGBACK { 727 void 728 PINGPROC_NULL(void) = 0; 729 /* 730 * Ping the client, return the round-trip time 731 * (in microseconds). Returns -1 if the operation 732 * timed out. 733 */ 734 int 735 PINGPROC_PINGBACK(void) = 1; 736 } = 2; 738 /* 739 * Original version 740 */ 741 version PING_VERS_ORIG { 742 void 743 PINGPROC_NULL(void) = 0; 744 } = 1; 745 } = 1; 747 const PING_VERS = 2; /* latest version */ 749 The first version described is PING_VERS_PINGBACK with two 750 procedures, PINGPROC_NULL and PINGPROC_PINGBACK. PINGPROC_NULL takes 751 no arguments and returns no results, but it is useful for computing 752 round-trip times from the client to the server and back again. By 753 convention, procedure 0 of any RPC protocol should have the same 754 semantics, and never require any kind of authentication. The second 755 procedure is used for the client to have the server do a reverse ping 756 operation back to the client, and it returns the amount of time (in 757 microseconds) that the operation used. The next version, 758 PING_VERS_ORIG, is the original version of the protocol and it does 759 not contain PINGPROC_PINGBACK procedure. It is useful for 760 compatibility with old client programs, and as this program matures 761 it may be dropped from the protocol entirely. 763 12.2. The RPC Language Specification 765 The RPC language is identical to the XDR language defined in RFC 766 4506, except for the added definition of a "program-def" described 767 below. 769 program-def: 770 "program" identifier "{" 771 version-def 772 version-def * 773 "}" "=" constant ";" 775 version-def: 776 "version" identifier "{" 777 procedure-def 778 procedure-def * 779 "}" "=" constant ";" 781 procedure-def: 782 proc-return identifier "(" proc-firstarg 783 ("," type-specifier )* ")" "=" constant ";" 785 proc-return: "void" | type-specifier 787 proc-firstarg: "void" | type-specifier 789 12.3. Syntax Notes 791 o The following keywords are added and cannot be used as 792 identifiers: "program" and "version"; 794 o A version name cannot occur more than once within the scope of a 795 program definition. Nor can a version number occur more than 796 once within the scope of a program definition. 798 o A procedure name cannot occur more than once within the scope of 799 a version definition. Nor can a procedure number occur more than 800 once within the scope of version definition. 802 o Program identifiers are in the same name space as constant and 803 type identifiers. 805 o Only unsigned constants can be assigned to programs, versions 806 and procedures. 808 o Current RPC language compilers do not generally support more 809 than one type-specifier in procedure argument lists; the usual 810 practice is to wrap arguments into a structure. 812 13. IANA Considerations 814 The assignment of RPC program numbers, authentication flavor numbers 815 and authentication status numbers has in the past been performed by 816 Sun Microsystems, Inc (Sun). This is inappropriate for an IETF 817 standards-track protocol, as such work is done well by the Internet 818 Assigned Numbers Authority (IANA). This document proposes the 819 transfer of authority over RPC program numbers, authentication flavor 820 numbers and authentication status numbers described here from Sun 821 Microsystems, Inc. to IANA and proposes how IANA will maintain and 822 assign these numbers. Users of RPC protocols will benefit by having 823 an independent body responsible for these number assignments. 825 13.1. Numbering Requests to IANA 827 Appendix B of this document describes the information to be sent to 828 IANA to request one or more RPC numbers and the rules that apply. 829 IANA should store the request for documentary purposes, and put the 830 following information into the public registry: 832 o The short description of purpose and use 834 o The program number(s) assigned 836 o The short identifier string(s) 838 13.2. Protecting Past Assignments 840 Sun has made assignments in both number spaces since the original 841 deployment of RPC. The assignments made by Sun Microsystems are 842 still valid, and will be preserved. Sun will communicate all current 843 assignments in both number spaces to IANA before final handoff of 844 number assignment is done. Current program and auth number 845 assignments are provided in Appendix C. Current authentication 846 status numbers are listed in Section 9 of this document in the "enum 847 auth_stat" definition. 849 13.3. RPC Number Assignment 851 Future IANA practice should deal with the following partitioning of 852 the 32-bit number space as listed in Section 8.3. Detailed 853 information for the administration of the partitioned blocks in 854 Section 8.3. is given below. 856 13.3.1. To be assigned by IANA 858 The first block will be administered by IANA, with previous 859 assignments by Sun protected. Previous assignments were restricted 860 to the range decimal 100000-399999 (0x000186a0 to 0x00061a7f), 861 therefore IANA should begin assignments at decimal 400000. 862 Individual numbers should be grated on a first-come, first-served 863 basis, and blocks should be granted under rules related to the size 864 of the block. 866 13.3.2. Defined by local administrator 868 The "Defined by local administrator" block is available for any local 869 administrative domain to use, in a similar manner to IP address 870 ranges reserved for private use. The expected use would be through 871 the establishment of a local domain "authority" for assigning numbers 872 from this range. This authority would establish any policies or 873 procedures to be used within that local domain for use or assignment 874 of RPC numbers from the range. The local domain should be 875 sufficiently isolated that it would be unlikely that RPC applications 876 developed by other local domains could communicate with the domain. 877 This could result in RPC number contention, which would cause one of 878 the applications to fail. In the absence of a local administrator, 879 this block can be utilized in a "Private Use" manner per [RFC5226]. 881 13.3.3. Transient block 883 The "Transient" block can be used by any RPC application on a "as 884 available" basis. This range is intended for services that can 885 communicate a dynamically selected RPC program number to clients of 886 the service. Any mechanism can be used to communicate the number. 887 Examples include shared memory when the client and server are located 888 on the same system, or a network message (either RPC or otherwise) 889 that disseminates the selected number. 891 The transient block is not administered. An RPC service uses this 892 range by selecting a number in the transient range and attempting to 893 register that number with the local system's RPC bindery (see the 894 RPCBPROC_SET or PMAPPROC_SET procedures in "Binding Protocols for ONC 895 RPC", [RFC1833]). If successful, no other RPC service was using that 896 number and the RPC Bindery has assigned that number to the requesting 897 RPC application. The registration is valid until the RPC Bindery 898 terminates, which normally would only happen if the system reboots 899 causing all applications, including the RPC service using the 900 transient number, to terminate. If the transient number registration 901 fails, another RPC application is using the number and the requestor 902 must select another number and try again. To avoid conflicts, the 903 recommended method is to select a number randomly from the transient 904 range. 906 13.3.4. Reserved block 908 The "Reserved" blocks are available for future use. RPC applications 909 must not use numbers in these ranges unless their use is allowed by 910 future action by the IESG. 912 13.3.5. RPC Number Sub-Blocks 914 RPC numbers are usually assigned for specific RPC services. Some 915 applications, however, require multiple RPC numbers for a service. 916 The most common example is an RPC service that needs to have multiple 917 instances of the service active simultaneously at a specific site. 918 RPC does not have an "instance identifier" in the protocol, so either 919 a mechanism must be implemented to multiplex RPC requests amongst 920 various instances of the service, or unique RPC numbers must be used 921 by each instance. 923 In these cases, the RPC protocol used with the various numbers may be 924 different or the same. The numbers may be assigned dynamically by 925 the application, or as part of a site-specific administrative 926 decision. If possible, RPC services that dynamically assign RPC 927 numbers should use the "Transient" RPC number block defined in 928 section 2. If not possible, RPC number sub-blocks may be requested. 930 Assignment of RPC Number Sub-Blocks is controlled by the size of the 931 sub-block being requested. "Specification Required" and "IESG 932 Approval" are used as defined by [RFC5226] Section 4.1. 934 Size of sub-block Assignment Method Authority 935 ----------------- ----------------- --------- 936 Up to 100 numbers First Come First Served IANA 937 Up to 1000 numbers Specification Required IANA 938 More than 1000 numbers IESG Approval required IESG 940 Note: sub-blocks can be any size. The limits given above are 941 maximums and smaller size sub-blocks are allowed. 943 Sub-blocks sized up to 100 numbers may be assigned by IANA on a First 944 Come First Served basis. The RPC Service Description included in the 945 range must include an indication of how the sub-block is managed. At 946 a minimum, the statement should indicate whether the sub-block is 947 used with a single RPC protocol or multiple RPC protocols, and 948 whether the numbers are dynamically assigned or statically (through 949 administrative action) assigned. 951 Sub-blocks of up to 1000 numbers must be documented in detail. The 952 documentation must describe the RPC protocol or protocols that are to 953 be used in the range. It must also describe how the numbers within 954 the sub-block are to be assigned or used. 956 Sub-blocks sized over 1000 numbers must be documented as described 957 above, and the assignment must be approved by the IESG. It is 958 expected that this will be rare. 960 In order to avoid multiple requests of large blocks of numbers the 961 following rule is proposed. 963 Requests up to and including 100 RPC numbers are handled via the 964 First Come First Served assignment method. This 100 number 965 threshhold applies to the total number of RPC numbers assigned to an 966 individual or entity. For example, if an individual or entity first 967 requests say 70 numbers, and then later requests 40 numbers, then the 968 request for the 40 numbers will be assigned via the Specification 969 Required method. As long as the total number of numbers assigned 970 does not exceed 1000, IANA is free to waive the Specification 971 Required assignment for incremental requests of less than 100 972 numbers. 974 If an individual or entity has under 1000 numbers and later requests 975 an additional set of numbers such that the individual or entity would 976 be granted over 1000 numbers, then the additional request will 977 require IESG Approval. 979 13.4. RPC Authentication Flavor Number Assignment 981 The second number space is the authentication mechanism identifier, 982 or "flavor", number. This number is used to distinguish between 983 various authentication mechanisms which can be optionally used with 984 an RPC message. An authentication identifier is used in the "flavor" 985 field of the "opaque_auth" structure. 987 13.4.1. Assignment Policy 989 Appendix B of this document describes the information to be sent to 990 IANA to request one or more RPC auth numbers and the rules that 991 apply. IANA should store the request for documentary purposes, and 992 put the following information into the public registry: 994 o The short identifier string(s) 996 o The auth number(s) assigned 998 o The short description of purpose and use 1000 13.4.2. Auth Flavors vs. Pseudo-flavors 1002 Recent progress in RPC security has moved away from new auth flavors 1003 as used by AUTH_DH [DH], and focused on using the existing RPCSEC_GSS 1004 [RFC2203] flavor and inventing novel GSS-API mechanisms which can be 1005 used with it. Even though RPCSEC_GSS is an assigned authentication 1006 flavor, use of a new RPCSEC_GSS mechanism with NFS ([RFC1094] 1007 [RFC1813] and [RFC3530]) will require the registration of 'pseudo- 1008 flavors' which are used to negotiate security mechanisms in an 1009 unambiguous way, as defined by [RFC2623]. Existing pseudo-flavors 1010 have been granted in the decimal range 390000-390255. New pseudo- 1011 flavor requests should be granted by IANA within this block on a 1012 First Come First Served basis. 1014 For non-pseudo-flavor requests, IANA should begin granting RPC 1015 authentication flavor numbers at 400000 on a First Come First Served 1016 basis to avoid conflicts with currently granted numbers. 1018 For authentication flavors or RPCSEC_GSS mechanisms to be used on the 1019 Internet, it is strongly advised that an informational or standards- 1020 track RFC be published describing the authentication mechanism 1021 behaviour and parameters. 1023 13.5. Authentication Status Number Assignment 1025 The final number space is the authentication status or "auth_stat" 1026 values which describe the nature of a problem found during an attempt 1027 to authenicate or validate authentication. The complete initial list 1028 of these values is found in Section 9 of this document, in the 1029 "auth_stat" enum listing. It is expected that it will be rare to add 1030 values, but that a small number of new values may be added from time 1031 to time as new authentication flavors introduce new possibilities. 1032 Numbers should be granted on a First Come First Served basis to avoid 1033 conflicts with currently granted numbers. 1035 13.5.1. Assignment Policy 1037 Appendix B of this document describes the information to be sent to 1038 IANA to request one or more auth_stat values and the rules that 1039 apply. IANA should store the request for documentary purposes, and 1040 put the following information into the public registry: 1042 o The short identifier string(s) 1044 o The auth_stat number(s) assigned 1046 o The short description of purpose and use 1048 14. Security Considerations 1050 AUTH_SYS as described in Appendix A is known to be insecure due to 1051 the lack of a verifier to permit the credential to be validated. 1052 AUTH_SYS SHOULD NOT be used for services which permit clients to 1053 modify data. AUTH_SYS MUST NOT be specified as RECOMMENDED or 1054 REQUIRED for any standards-track RPC service. 1056 AUTH_DH as mentioned in sections 8.2 and 13.4.2 is considered 1057 obsolete and insecure; see [RFC2695]. AUTH_SYS SHOULD NOT be used 1058 for services which permit clients to modify data. AUTH_DH MUST NOT 1059 be specified as RECOMMENDED or REQUIRED for any standards-track RPC 1060 service. 1062 [RFC2203] defines a new security flavor, RPCSEC_GSS, which permits 1063 GSS-API [RFC2743] mechanisms to be used for securing RPC. All non- 1064 trivial RPC programs developed in the future should implement 1065 RPCSEC_GSS-based security appropriately. [RFC2623] describes how 1066 this was done for a widely deployed RPC program. 1068 Standards-track RPC services MUST mandate support for RPCSEC_GSS, and 1069 MUST mandate support for an authentication pseudo-flavor with 1070 appropriate levels of security, depending on the need for simple 1071 authentication, integrity a.k.a. non-repudiation, or data privacy. 1073 15. Appendix A: System Authentication 1075 The client may wish to identify itself, for example, as it is 1076 identified on a UNIX(tm) system. The flavor of the client credential 1077 is "AUTH_SYS". The opaque data constituting the credential encodes 1078 the following structure: 1080 struct authsys_parms { 1081 unsigned int stamp; 1082 string machinename<255>; 1083 unsigned int uid; 1084 unsigned int gid; 1085 unsigned int gids<16>; 1086 }; 1088 The "stamp" is an arbitrary ID which the caller machine may generate. 1089 The "machinename" is the name of the caller's machine (like 1090 "krypton"). The "uid" is the caller's effective user ID. The "gid" 1091 is the caller's effective group ID. The "gids" is a counted array of 1092 groups which contain the caller as a member. The verifier 1093 accompanying the credential should have "AUTH_NONE" flavor value 1094 (defined above). Note this credential is only unique within a 1095 particular domain of machine names, uids, and gids. 1097 The flavor value of the verifier received in the reply message from 1098 the server may be "AUTH_NONE" or "AUTH_SHORT". In the case of 1099 "AUTH_SHORT", the bytes of the reply verifier's string encode an 1100 opaque structure. This new opaque structure may now be passed to the 1101 server instead of the original "AUTH_SYS" flavor credential. The 1102 server may keep a cache which maps shorthand opaque structures 1103 (passed back by way of an "AUTH_SHORT" style reply verifier) to the 1104 original credentials of the caller. The caller can save network 1105 bandwidth and server cpu cycles by using the shorthand credential. 1107 The server may flush the shorthand opaque structure at any time. If 1108 this happens, the remote procedure call message will be rejected due 1109 to an authentication error. The reason for the failure will be 1110 "AUTH_REJECTEDCRED". At this point, the client may wish to try the 1111 original "AUTH_SYS" style of credential. 1113 It should be noted that use of this flavor of authentication does not 1114 guarantee any security for the users or providers of a service, in 1115 itself. The authentication provided by this scheme can be considered 1116 legitimate only when applications using this scheme and the network 1117 can be secured externally, and privileged transport addresses are 1118 used for the communicating end-points (an example of this is the use 1119 of privileged TCP/UDP ports in Unix systems - note that not all 1120 systems enforce privileged transport address mechanisms). 1122 16. Appendix B: Requesting RPC-related numbers from IANA 1124 RPC program numbers, authentication flavor numbers and authentication 1125 status numbers which must be unique across all networks are assigned 1126 by the Internet Assigned Number Authority. To apply for a single 1127 number or a block of numbers, electronic mail must be sent to IANA 1128 with the following information: 1130 o The type of number(s) (program number or authentication flavor 1131 number or authentication status number) sought 1133 o How many numbers are sought 1135 o The name of person or company which will use the number 1137 o An "identifier string" which associates the number with a 1138 service 1140 o Email address of the contact person for the service which will 1141 be using the number. 1143 o A short description of the purpose and use of the number 1145 o If an authentication flavor number is sought, and the number 1146 will be a 'pseudo-flavor' intended for use with RPCSEC_GSS and 1147 NFS, mappings analogous to those in Section 4.2 of [RFC2623] are 1148 required. 1150 Specific numbers cannot be requested. Numbers are assigned on a 1151 First Come First Served basis. 1153 For all RPC authentication flavor and authentication status numbers 1154 to be used on the Internet, it is strongly advised that an 1155 informational or standards-track RFC be published describing the 1156 authentication mechanism behaviour and parameters. 1158 17. Appendix C: Current number assignments 1160 # 1161 # Sun-assigned RPC numbers 1162 # 1163 # Description/Owner RPC Program Number Short Name 1164 # ----------------------------------------------------------------- 1165 portmapper 100000 pmapprog portmap rpcbind 1166 remote stats 100001 rstatprog 1167 remote users 100002 rusersprog 1168 nfs 100003 nfs 1169 yellow pages (NIS) 100004 ypprog ypserv 1170 mount demon 100005 mountprog 1171 remote dbx 100006 dbxprog 1172 yp binder (NIS) 100007 ypbindprog ypbind 1173 shutdown msg 100008 wall 1174 yppasswd server 100009 yppasswdprog yppasswdd 1175 ether stats 100010 etherstatprog 1176 disk quotas 100011 rquota 1177 spray packets 100012 spray 1178 3270 mapper 100013 ibm3270prog 1179 RJE mapper 100014 ibmrjeprog 1180 selection service 100015 selnsvcprog 1181 remote database access 100016 rdatabaseprog 1182 remote execution 100017 rexec 1183 Alice Office Automation 100018 aliceprog 1184 scheduling service 100019 schedprog 1185 local lock manager 100020 lockprog llockmgr 1186 network lock manager 100021 netlockprog nlockmgr 1187 x.25 inr protocol 100022 x25prog 1188 status monitor 1 100023 statmon1 1189 status monitor 2 100024 statmon2 1190 selection library 100025 selnlibprog 1191 boot parameters service 100026 bootparam 1192 mazewars game 100027 mazeprog 1193 yp update (NIS) 100028 ypupdateprog ypupdate 1194 key server 100029 keyserveprog 1195 secure login 100030 securecmdprog 1196 nfs net forwarder init 100031 netfwdiprog 1197 nfs net forwarder trans 100032 netfwdtprog 1198 sunlink MAP 100033 sunlinkmap 1199 network monitor 100034 netmonprog 1200 lightweight database 100035 dbaseprog 1201 password authorization 100036 pwdauthprog 1202 translucent file svc 100037 tfsprog 1203 nse server 100038 nseprog 1204 nse activate daemon 100039 nse_activate_prog 1205 sunview help 100040 sunview_help_prog 1206 pnp install 100041 pnp_prog 1207 ip addr allocator 100042 ipaddr_alloc_prog 1208 show filehandle 100043 filehandle 1209 MVS NFS mount 100044 mvsnfsprog 1210 remote user file operations 100045 rem_fileop_user_prog 1211 batched ypupdate 100046 batch_ypupdateprog 1212 network execution mgr 100047 nem_prog 1213 raytrace/mandelbrot remote daemon 100048 raytrace_rd_prog 1214 raytrace/mandelbrot local daemon 100049 raytrace_ld_prog 1215 remote group file operations 100050 rem_fileop_group_prog 1216 remote system file operations 100051 rem_fileop_system_prog 1217 remote system role operations 100052 rem_system_role_prog 1218 gpd lego fb simulator 100053 [unknown] 1219 gpd simulator interface 100054 [unknown] 1220 ioadmd 100055 ioadmd 1221 filemerge 100056 filemerge_prog 1222 Name Binding Program 100057 namebind_prog 1223 sunlink NJE 100058 njeprog 1224 MVSNFS get attribute service 100059 mvsattrprog 1225 SunAccess/SunLink resource manager 100060 rmgrprog 1226 UID allocation service 100061 uidallocprog 1227 license broker 100062 lbserverprog 1228 NETlicense client binder 100063 lbbinderprog 1229 GID allocation service 100064 gidallocprog 1230 SunIsam 100065 sunisamprog 1231 Remote Debug Server 100066 rdbsrvprog 1232 Network Directory Daemon 100067 [unknown] 1233 Network Calendar Program 100068 cmsd cm 1234 ypxfrd 100069 ypxfrd 1235 rpc.timed 100070 timedprog 1236 bugtraqd 100071 bugtraqd 1237 100072 [unknown] 1238 Connectathon Billboard - NFS 100073 [unknown] 1239 Connectathon Billboard - X 100074 [unknown] 1240 Sun tool for scheduling rooms 100075 schedroom 1241 Authentication Negotiation 100076 authnegotiate_prog 1242 Database manipulation 100077 attribute_prog 1243 Kerberos authentication daemon 100078 kerbprog 1244 Internal testing product (no name) 100079 [unknown] 1245 Sun Consulting Special 100080 autodump_prog 1246 Event protocol 100081 event_svc 1247 bugtraq_qd 100082 bugtraq_qd 1248 ToolTalk and Link Service Project 100083 database service 1249 Consulting Services 100084 [unknown] 1250 Consulting Services 100085 [unknown] 1251 Consulting Services 100086 [unknown] 1252 Jupiter Administration 100087 adm_agent admind 1253 100088 [unknown] 1254 100089 [unknown] 1255 Dual Disk support 100090 libdsd/dsd 1256 DocViewer 1.1 100091 [unknown] 1257 ToolTalk 100092 remote_activation_svc 1258 Consulting Services 100093 host_checking 1259 SNA peer-to-peer 100094 [unknown] 1260 Roger Riggs 100095 searchit 1261 Robert Allen 100096 mesgtool 1262 SNA 100097 [unknown] 1263 SISU 100098 networked version of CS5 1264 NFS Automount File System 100099 autofs 1265 100100 msgboard 1266 event dispatching agent [eventd] 100101 netmgt_eventd_prog 1267 statistics/event logger [netlogd] 100102 netmgt_netlogd_prog 1268 topology display manager [topology]100103 netmgt_topology_prog 1269 syncstat agent [syncstatd] 100104 netmgt_syncstatd_prog 1270 ip packet stats agent [ippktd] 100105 netmgt_ippktd_prog 1271 netmgt config agent [configd] 100106 netmgt_configd_prog 1272 restat agent [restatd] 100107 netmgt_restatd_prog 1273 lpq agent [lprstatd] 100108 netmgt_lprstatd_prog 1274 netmgt activity agent [mgtlogd] 100109 netmgt_mgtlogd_prog 1275 proxy DECnet NCP agent [proxydni] 100110 netmgt_proxydni_prog 1276 topology mapper agent [mapperd] 100111 netmgt_mapperd_prog 1277 netstat agent [netstatd] 100112 netmgt_netstatd_prog 1278 sample netmgt agent [sampled] 100113 netmgt_sampled_prog 1279 X.25 statistics agent [vcstatd] 100114 netmgt_vcstatd_prog 1280 Frame Relay 100128 [unknown] 1281 PPP agent 100129 [unknown] 1282 localhad 100130 rpc.localhad 1283 layers2 100131 na.layers2 1284 token ring agent 100132 na.tr 1285 related to lockd and statd 100133 nsm_addr 1286 Kerberos project 100134 kwarn 1287 ertherif2 100135 na.etherif2 1288 hostmem2 100136 na.hostmem2 1289 iostat2 100137 na.iostat2 1290 snmpv2 100138 na.snmpv2 1291 Cooperative Console 100139 cc_sender 1292 na.cpustat 100140 na.cpustat 1293 Sun Cluster SC3.0 100141 rgmd_receptionist 1294 100142 fed 1296 Network Storage 100143 rdc 1297 Sun Cluster products 100144 nafo 1298 SunCluster 3.0 100145 scadmd 1299 ASN.1 100146 amiserv 1300 100147 amiaux # BER and DER 1301 encode and decode 1302 Delegate Management Server 100148 dm 1303 100149 rkstat 1304 100150 ocfserv 1305 100151 sccheckd 1306 100152 autoclientd 1307 100153 sunvts 1308 100154 ssmond 1309 100155 smserverd 1310 100156 test1 1311 100157 test2 1312 100158 test3 1313 100159 test4 1314 100160 test5 1315 100161 test6 1316 100162 test7 1317 100163 test8 1318 100164 test9 1319 100165 test10 1320 100166 nfsmapid 1321 100167 SUN_WBEM_C_CIMON_HANDLE 1322 100168 sacmmd 1323 100169 fmd_adm 1324 100170 fmd_api 1325 100171 [unknown] 1326 100172 idmapd 1327 [available] 100173 - 100174 1328 snmptrap 100175 na.snmptrap 1329 [available] 100176-100199 1331 [available] 100200 1332 MVS/NFS Memory usage stats server 100201 [unknown] 1333 Netapp 100202-100207 1334 [available] 100208-100210 1335 8.0 SunLink SNA RJE 100211 [unknown] 1336 8.0 SunLink SNA RJE 100212 [unknown] 1337 100213 ShowMe 1338 100214 [unknown] 1339 100215 [unknown] 1340 AUTH_RSA Key service 100216 keyrsa 1341 SunSelect PC license service 100217 [unknown] 1342 WWCS (Corporate) 100218 sunsolve 1343 100219 cstatd 1345 X/Open Federated Naming 100220 xfn_server_prog 1346 Kodak Color Management System 100221 kcs_network_io kcs 1347 HA-DBMS 100222 ha_dbms_serv 1348 100223-100225 [unknown] 1349 100226 hafaultd 1350 NFS ACL Service 100227 nfs_acl 1351 distributed lock manager 100228 dlmd 1352 100229 metad 1353 100230 metamhd 1354 100231 nfsauth 1355 100232 sadmind 1356 100233 ufsd 1357 100234 grpservd 1358 100235 cachefsd 1359 100236 msmprog Media_Server 1360 100237 ihnamed 1361 100238 ihnetd 1362 100239 ihsecured 1363 100240 ihclassmgrd 1364 100241 ihrepositoryd 1365 100242 metamedd rpc.metamedd 1366 100243 contentmanager cm 1367 100244 symon 1368 100245 pld genesil 1369 100246 ctid 1370 cluster_transport_interface 1371 100247 ccd 1372 cluster_configuration_db 1373 100248 pmfd 1374 100249 dmi2_client 1375 100250 mfs_admin 1376 100251 ndshared_unlink 1377 100252 ndshared_touch 1378 100253 ndshared_slink 1379 100254 cbs control_board_server 1380 100255 skiserv 1381 100256 nfsxa nfsxattr 1382 100257 ndshared_disable 1383 100258 ndshared_enable 1384 100259 sms_account_admin 1385 100260 sms_modem_admin 1386 100261 sms_r_login 1387 100262 sms_r_subaccount_mgt 1388 100263 sms_service_admin 1389 100264 session_admin 1390 100265 canci_ancs_program 1391 100266 canci_sms_program 1392 100267 msmp 1393 100268 halck 1394 100269 halogmsg 1395 100270 nfs_id_map 1396 100271 ncall 1397 100272 hmip 1398 100273 repl_mig 1399 100274 repl_mig_cb 1400 NIS+ 100300 nisplus 1401 NIS+ 100301 nis_cachemgr 1402 NIS+ call back protocol 100302 [unknown] 1403 NIS+ Password Update Daemon 100303 nispasswdd 1404 FNS context update in NIS 100304 fnsypd 1405 100305 [unknown] 1406 100306 [unknown] 1407 100307 [unknown] 1408 100308 [unknown] 1409 100309 [unknown] 1410 [available] 100310 - 100398 1411 nfscksum 100399 nfscksum 1412 network utilization agent 100400 netmgt_netu_prog 1413 network rpc ping agent 100401 netmgt_rping_prog 1414 100402 na.shell 1415 picsprint 100403 na.picslp 1416 100404 traps 1417 100405 - 100409 [unknown] 1418 100410 jdsagent 1419 100411 na.haconfig 1420 100412 na.halhost 1421 100413 na.hadtsrvc 1422 100414 na.hamdstat 1423 100415 na.neoadmin 1424 100416 ex1048prog 1425 100417 rdmaconfig 1426 IETF NFSv4 Working Group - FedFS 100418 - 100421 1427 100422 mdcommd 1428 100423 kiprop krb5_iprop 1429 100424 stsf 1430 [available] 100425 - 100499 1431 Sun Microsystems 100500 - 100531 [unknown] 1432 100532 ucmmstate 1433 100533 scrcmd 1434 [available] 100534 - 100999 1435 nse link daemon 101002 nselinktool 1436 nse link application 101003 nselinkapp 1437 [available] 101004 - 101900 1438 101901 [unknown] 1439 [available] 101902 - 101999 1440 AssetLite 102000 [unknown] 1441 PagerTool 102001 [unknown] 1442 Discover 102002 [unknown] 1443 [available] 102003 - 105000 1444 ShowMe 105001 sharedapp 1445 Registry 105002 REGISTRY_PROG 1446 Print-server 105003 print-server 1447 Proto-server 105004 proto-server 1448 Notification-server 105005 notification-server 1449 Transfer-agent-server 105006 transfer-agent-server 1450 [available] 105007 - 110000 1451 110001 tsolrpcb 1452 110002 tsolpeerinfo 1453 110003 tsolboot 1454 120001 cmip na.cmip 1455 120002 na.osidiscover 1456 120003 cmiptrap 1457 [available] 120004 - 120099 1458 120100 eserver 1459 120101 repserver 1460 120102 swserver 1461 120103 dmd 1462 120104 ca 1463 [available] 120105 - 120125 1464 120126 nf_fddi 1465 120127 nf_fddismt7_2 1466 [available] 120128 - 150000 1467 pc passwd authorization 150001 pcnfsdprog 1468 TOPS name mapping 150002 [unknown] 1469 TOPS external attribute storage 150003 [unknown] 1470 TOPS hierarchical file system 150004 [unknown] 1471 TOPS NFS transparency extensions 150005 [unknown] 1472 PC NFS License 150006 pcnfslicense 1473 RDA 150007 rdaprog 1474 WabiServer 150008 wsprog 1475 WabiServer 150009 wsrlprog 1476 [available] 150010 - 160000 1477 160001 nihon-cm 1478 160002 nihon-ce 1479 [available] 160003 - 170099 1480 170100 domf_daemon0 1481 170101 domf_daemon1 1482 170102 domf_daemon2 1483 170103 domf_daemon3 1484 170104 domf_daemon4 1485 170105 domf_daemon5 1486 [available] 170106 - 179999 1487 180000 cecprog 1488 180001 cecsysprog 1489 180002 cec2cecprog 1490 180003 cesprog 1491 180004 ces2cesprog 1492 180005 cet2cetprog 1493 180006 cet2cetdoneprog 1494 180007 cetcomprog 1495 180008 cetsysprog 1496 180009 cghapresenceprog 1497 180010 cgdmsyncprog 1498 180011 cgdmcnscliprog 1499 180012 cgdmcrcscliprog 1500 180013 cgdmcrcssvcproG 1501 180014 chmprog 1502 180015 chmsysprog 1503 180016 crcsapiprog 1504 180017 ckptmprog 1505 180018 crimcomponentprog 1506 180019 crimqueryprog 1507 180020 crimsecondaryprog 1508 180021 crimservicesprog 1509 180022 crimsyscomponentprog 1510 180023 crimsysservicesprog 1511 180024 csmagtapiprog 1512 180025 csmagtcallbackprog 1513 180026 csmreplicaprog 1514 180027 csmsrvprog 1515 180028 cssccltprog 1516 180029 csscsvrprog 1517 180030 csscopresultprog 1518 [available] 180031 - 199999 1519 200000 pyramid_nfs 1520 200001 pyramid_reserved 1521 200002 cadds_image 1522 200003 stellar_name_prog 1523 200004 [unknown] 1524 200005 [unknown] 1525 200006 pacl 1526 200007 lookupids 1527 200008 ax_statd_prog 1528 200009 ax_statd2_prog 1529 200010 edm 1530 200011 dtedirwd 1531 200012 [unknown] 1532 200013 [unknown] 1533 200014 [unknown] 1534 200015 [unknown] 1535 200016 easerpcd 1536 200017 rlxnfs 1537 200018 sascuiddprog 1538 200019 knfsd 1539 200020 ftnfsd ftnfsd_program 1540 200021 ftsyncd ftsyncd_program 1541 200022 ftstatd ftstatd_program 1542 200023 exportmap 1543 200024 nfs_metadata 1544 [available] 200025 - 200200 1545 200201 ecoad 1546 200202 eamon 1547 200203 ecolic 1548 200204 cs_printstatus_svr 1549 200205 ecodisc 1550 [available] 200206 - 300000 1551 300001 adt_rflockprog 1552 300002 columbine1 1553 300003 system33_prog 1554 300004 frame_prog1 1555 300005 uimxprog 1556 300006 rvd 1557 300007 entombing daemon 1558 300008 account mgmt system 1559 300009 frame_prog2 1560 300010 beeper access 1561 300011 dptuprog 1562 300012 mx-bcp 1563 300013 instrument-file-access 1564 300014 file-system-statistics 1565 300015 unify-database-server 1566 300016 tmd_msg 1567 300017 [unknown] 1568 300018 [unknown] 1569 300019 automounter access 1570 300020 lock server 1571 300021 [unknown] 1572 300022 office-automation-1 1573 300023 office-automation-2 1574 300024 office-automation-3 1575 300025 office-automation-4 1576 300026 office-automation-5 1577 300027 office-automation-6 1578 300028 office-automation-7 1579 300029 local-data-manager 1580 300030 chide 1581 300031 csi_program 1582 300032 [unknown] 1583 300033 online-help 1584 300034 case-tool 1585 300035 delta 1586 300036 rgi 1587 300037 instrument-config-server 1588 300038 [unknown] 1589 300039 [unknown] 1590 300040 dtia-rpc-server 1591 300041 cms 1592 300042 viewer 1593 300043 aqm 1594 300044 exclaim 1595 300045 masterplan 1596 300046 fig_tool 1597 300047 [unknown] 1598 300048 [unknown] 1599 300049 [unknown] 1600 300050 remote-lock-manager 1601 300051 [unknown] 1602 300052 gdebug 1603 300053 ldebug 1604 300054 rscanner 1605 300055 [unknown] 1606 300056 [unknown] 1607 300057 [unknown] 1608 300058 [unknown] 1609 300059 [unknown] 1610 300060 [unknown] 1611 300061 [unknown] 1612 300062 [unknown] 1613 300063 [unknown] 1614 300064 [unknown] 1615 300065 [unknown] 1616 300066 nSERVER 1617 300067 [unknown] 1618 300068 [unknown] 1619 300069 [unknown] 1620 300070 [unknown] 1621 300071 BioStation 1622 300072 [unknown] 1623 300073 NetProb 1624 300074 Logging 1625 300075 Logging 1626 300076 [unknown] 1627 300077 [unknown] 1628 300078 [unknown] 1629 300079 [unknown] 1630 300080 [unknown] 1631 300081 [unknown] 1632 300082 sw_twin 1633 300083 remote_get_login 1634 300084 odcprog 1635 300085 [unknown] 1636 300086 [unknown] 1637 300087 [unknown] 1638 300088 [unknown] 1639 300089 [unknown] 1640 300090 [unknown] 1641 300091 smartdoc 1642 300092 superping 1643 300093 distributed-chembench 1644 300094 uacman/alfil-uacman 1645 300095 ait_rcagent_prog 1646 300096 ait_rcagent_appl_prog 1647 300097 smart 1648 300098 ecoprog 1649 300099 leonardo 1650 300100 [unknown] 1651 300101 [unknown] 1652 300102 [unknown] 1653 300103 [unknown] 1654 300104 [unknown] 1655 300105 [unknown] 1656 300106 [unknown] 1657 300107 [unknown] 1658 300108 wingz 1659 300109 teidan 1660 300110 [unknown] 1661 300111 [unknown] 1662 300112 [unknown] 1663 300113 [unknown] 1664 300114 [unknown] 1665 300115 [unknown] 1666 300116 cadc_fhlockprog 1667 300117 highscan 1668 300118 [unknown] 1669 300119 [unknown] 1670 300120 [unknown] 1671 300121 opennavigator 1672 300122 aarpcxfer 1673 300123 [unknown] 1674 300124 [unknown] 1675 300125 [unknown] 1676 300126 groggs 1677 300127 licsrv 1678 300128 issdemon 1679 300129 [unknown] 1680 300130 maximize 1681 300131 cgm_server 1682 300132 [unknown] 1683 300133 agent_rpc 1684 300134 docmaker 1685 300135 docmaker 1686 300136 [unknown] 1687 300137 [unknown] 1688 300138 [unknown] 1689 300139 iesx 1690 300140 [unknown] 1691 300141 [unknown] 1692 300142 [unknown] 1693 300143 [unknown] 1694 300144 smart-mbs 1695 300145 [unknown] 1696 300146 [unknown] 1697 300147 docimage 1698 300148 [unknown] 1699 300149 dmc-interface 1700 300150 [unknown] 1701 300151 jss 1702 300152 [unknown] 1703 300153 arimage 1704 300154 xdb-workbench 1705 300155 frontdesk 1706 300156 dmc 1707 300157 expressight-6000 1708 300158 graph service program 1709 300159 [unknown] 1710 300160 [unknown] 1711 300161 [unknown] 1712 300162 [unknown] 1713 300163 [unknown] 1714 300164 [unknown] 1715 300165 [unknown] 1716 300166 [unknown] 1717 300167 [unknown] 1718 300168 [unknown] 1719 300169 [unknown] 1720 300170 [unknown] 1721 300171 [unknown] 1722 300172 [unknown] 1723 300173 [unknown] 1724 300174 [unknown] 1725 300175 [unknown] 1726 300176 rlpr 1727 300177 nx_hostdprog 1728 300178 netuser-x 1729 300179 rmntprog 1730 300180 [unknown] 1731 300181 mipe 1732 300182 [unknown] 1733 300183 collectorprog 1734 300184 uslookup_PROG 1735 300185 viewstation 1736 300186 iate 1737 300187 [unknown] 1738 300188 [unknown] 1739 300189 [unknown] 1740 300190 imsvtprog 1741 300191 [unknown] 1742 300192 [unknown] 1743 300193 [unknown] 1744 300194 pmdb 1745 300195 pmda 1746 300196 [unknown] 1747 300197 [unknown] 1748 300198 trend_idbd 1749 300199 rres 1750 300200 sd.masterd 1751 300201 sd.executiond 1752 300202 sd.listend 1753 300203 sd.reserve1 1754 300204 sd.reserve2 1755 300205 msbd 1756 300206 stagedprog 1757 300207 mountprog 1758 300208 watchdprog 1759 300209 pms 1760 300210 [unknown] 1761 300211 session_server_program 1762 300212 session_program 1763 300213 debug_serverprog 1764 300214 [unknown] 1765 300215 [unknown] 1766 300216 paceprog 1767 300217 [unknown] 1768 300218 mbus 1769 300219 aframes2ps 1770 300220 npartprog 1771 300221 cm1server 1772 300222 cm1bridge 1773 300223 sailfrogfaxprog 1774 300224 sailfrogphoneprog 1775 300225 sailfrogvmailprog 1776 300226 wserviceprog arcstorm 1777 300227 hld 1778 300228 alive 1779 300229 radsp 1780 300230 radavx 1781 300231 radview 1782 300232 rsys_prog 1783 300233 rsys_prog 1784 300234 fm_rpc_prog 1785 300235 aries 1786 300236 uapman 1787 300237 ddman 1788 300238 top 1789 300239 [unknown] 1790 300240 trendlink 1791 300241 licenseprog 1792 300242 statuslicenseprog 1793 300243 oema_rmpf_svc 1794 300244 oema_smpf_svc 1795 300245 oema_rmsg_svc 1796 300246 grapes-sd 1797 300247 ds_master 1798 300248 ds_transfer 1799 300249 ds_logger 1800 300250 ds_query 1801 300251 [unknown] 1802 300252 [unknown] 1803 300253 nsd_prog 1804 300254 browser 1805 300255 epoch 1806 300256 floorplanner 1807 300257 reach 1808 300258 tactic 1809 300259 cachescientific1 1810 300260 cachescientific2 1811 300261 desksrc_prog 1812 300262 photo3d1 1813 300263 photo3d2 1814 300264 [unknown] 1815 300265 soundmgr 1816 300266 s6k 1817 300267 aims_referenced_ 1818 text_processor 1819 300268 xess 1820 300269 ds_queue 1821 300270 [unknown] 1822 300271 orionscanplus 1823 300272 openlink-xx 1824 300273 kbmsprog 1825 300274 [unknown] 1826 300275 futuresource 1827 300276 the_xprt 1828 300277 cmg_srvprog 1829 300278 [unknown] 1830 300279 [unknown] 1831 300280 front 1832 300281 [unknown] 1833 300282 [unknown] 1834 300283 [unknown] 1835 300284 conmanprog 1836 300285 jincv2 1837 300286 isls 1838 300287 systemstatprog 1839 300288 fxpsprog 1840 300289 callpath 1841 300290 axess 1842 300291 armor_rpcd 1843 300292 armor_dictionary_rpcd 1844 300293 armor_miscd 1845 300294 filetransfer_prog 1846 300295 bl_swda 1847 300296 bl_hwda 1848 300297 [unknown] 1849 300298 [unknown] 1850 300299 [unknown] 1851 300300 filemon 1852 300301 acunetprog 1853 300302 rbuild 1854 300303 assistprog 1855 300304 tog 1856 300305 [unknown] 1857 300306 sns7000 1858 300307 igprog 1859 300308 tgprog 1860 300309 plc 1861 300310 pxman pxlsprog 1862 300311 hde_server hdeserver 1863 300312 tsslicenseprog 1864 300313 rpc.explorerd 1865 300314 chrd 1866 300315 tbisam 1867 300316 tbis 1868 300317 adsprog 1869 300318 sponsorprog 1870 300319 querycmprog 1871 300320 [unknown] 1872 300321 [unknown] 1873 300322 mobil1 1874 300323 sld 1875 service_locator_daemon 1876 300324 linkprog 1877 300325 codexdaemonprog 1878 300326 drprog 1879 300327 ressys_commands 1880 300328 stamp 1881 300329 matlab 1882 300330 sched1d 1883 300331 upcprog 1884 300332 xferbkch 1885 300333 xfer 1886 300334 qbthd 1887 300335 qbabort 1888 300336 lsd 1889 300337 geomgrd 1890 300338 generic_fts 1891 300339 ft_ack 1892 300340 lymb 1893 300341 vantage 1894 300342 cltstd clooptstdprog 1895 300343 clui clui_prog 1896 300344 testerd tstdprog 1897 300345 extsim 1898 300346 cmd_dispatch maxm_ems 1899 300347 callpath_receive_program 1900 300348 x3270prog 1901 300349 sbc_lag 1902 300350 sbc_frsa 1903 300351 sbc_frs 1904 300352 atommgr 1905 300353 geostrat 1906 300354 dbvialu6.2 1907 300355 [unknown] 1908 300356 fxncprog 1909 300357 infopolic 1910 300358 [unknown] 1911 300359 aagns 1912 300360 aagms 1913 300361 [unknown] 1914 300362 clariion_mgr 1915 300363 setcimrpc 1916 300364 virtual_protocol_adapter 1917 300365 unibart 1918 300366 uniarch 1919 300367 unifile 1920 300368 unisrex 1921 300369 uniscmd 1922 300370 rsc 1923 300371 set 1924 300372 desaf-ws/key 1925 300373 reeldb 1926 300374 nl 1927 300375 rmd 1928 300376 agcd 1929 300377 rsynd 1930 300378 rcnlib 1931 300379 rcnlib_attach 1932 300380 evergreen_mgmt_agent 1933 300381 fx104prog 1934 300382 rui 1935 remote_user_interface 1936 300383 ovomd 1937 300384 [unknown] 1938 300385 [unknown] 1939 300386 system_server 1940 300387 pipecs cs_pipeprog 1941 ppktrpc 1942 300388 uv-net univision 1943 300389 auexe 1944 300390 audip 1945 300391 mqi 1946 300392 eva 1947 300393 eeei_reserved_1 1948 300394 eeei_reserved_2 1949 300395 eeei_reserved_3 1950 300396 eeei_reserved_4 1951 300397 eeei_reserved_5 1952 300398 eeei_reserved_6 1953 300399 eeei_reserved_7 1954 300400 eeei_reserved_8 1955 300401 cprlm 1956 300402 wg_idms_manager 1957 300403 timequota 1958 300404 spiff 1959 300405-300414 ov_oem_svc 1960 300415 ov_msg_ctlg_svc 1961 300416 ov_advt_reg_svc 1962 300417-300424 showkron 1963 300425 daatd 1964 300426 swiftnet 1965 300427 ovomdel 1966 300428 ovomreq 1967 300429 msg_dispatcher 1968 300430 pcshare server 1969 300431 rcvs 1970 300432 fdfserver 1971 300433 bssd 1972 300434 drdd 1973 300435 mif_gutsprog 1974 300436 mif_guiprog 1975 300437 twolfd 1976 300438 twscd 1977 300439 nwsbumv 1978 300440 dgux_mgr 1979 300441 pfxd 1980 300442 tds 1981 300443 ovomadmind 1982 300444 ovomgate 1983 300445 omadmind 1984 300446 nps 1985 300447 npd 1986 300448 tsa 1987 300449 cdaimc 1988 300450-300452 1989 300453 ckt_implementation 1990 300454 mda-tactical 1991 300455-300458 1992 300459 atrrun 1993 300460 RoadRunner 1994 300461 nas 1995 300462 undelete 1996 300463 ovacadd 1997 300464 tbdesmai 1998 300465 arguslm 1999 300466 dmd 2000 300467 drd 2001 300468 fm_help 2002 300469 ftransrpc_prog 2003 300470 finrisk 2004 300471 dg_pc_idisched 2005 300472 dg_pc_idiserv 2006 300473 apd 2007 300474 ap_sspd 2008 300475 callpatheventrecorder 2009 300476 flc 2010 300477 dg_osm 2011 300478 dspnamed 2012 300479 iqddsrv 2013 300480 iqjobsrv 2014 300481 tacosxx 2015 300482 wheeldbmg 2016 300483 cnxmgr_nm_prog 2017 300484 cnxmgr_cfg_prog 2018 300485 3dsmapper 2019 300486 ids 2020 300487 imagine_rpc_svc 2021 300488 lfn 2022 300489 salesnet 2023 300490 defaxo 2024 300491 dbqtsd 2025 300492 kms 2026 300493 rpc.iced 2027 300494 calc2s 2028 300495 ptouidprog 2029 300496 docsls 2030 300497 new 2031 300498 collagebdg 2032 300499 ars_server 2033 300500 ars_client 2034 300501 vr_catalog 2035 300502 vr_tdb 2036 300503 ama 2037 300504 evama 2038 300505 conama 2039 300506 service_process 2040 300507 reuse_proxy 2041 300508 mars_ctrl 2042 300509 mars_db 2043 300510 mars_com 2044 300511 mars_admch 2045 300512 tbpipcip 2046 300513 top_acs_svc 2047 300514 inout_svc 2048 300515 csoft_wp 2049 300516 mcfs 2050 300517 eventprog 2051 300518 dg_pc_idimsg 2052 300519 dg_pc_idiaux 2053 300520 atsr_gc 2054 300521 alarm alarm_prog 2055 300522 fts_prog 2056 300523 dcs_prog 2057 300524 ihb_prog 2058 300525 [unknown] 2059 300526 [unknown] 2060 300527 clu_info_prog 2061 300528 rmfm 2062 300529 c2sdocd 2063 300530 interahelp 2064 300531 callpathasyncmsghandler 2065 300532 optix_arc 2066 300533 optix_ts 2067 300534 optix_wf 2068 300535 maxopenc 2069 300536 cev cev_server 2070 300537 sitewideprog 2071 300538 drs 2072 300539 drsdm 2073 300540 dasgate 2074 300541 dcdbd 2075 300542 dcpsd 2076 300543 supportlink_prog 2077 300544 broker 2078 300545 listner 2079 300546 multiaccess 2080 300547 spai_interface 2081 300548 spai_adaption 2082 300549 chimera_ci 2083 chimera_clientinterface 2084 300550 chimera_pi 2085 chimera_processinvoker 2086 300551 teamware_fl 2087 teamware_foundationlevel 2088 300552 teamware_sl 2089 teamware_systemlevel 2090 300553 teamware_ui 2091 teamware_userinterface 2092 300554 lprm 2093 300555 mpsprog 2094 Mensuration_Proxy_Server 2095 300556 mo_symdis 2096 300557 retsideprog 2097 300558 slp 2098 300559 slm-api 2099 300560 im_rpc teamconference 2100 300561 license_prog license 2101 300562 stuple stuple_prog 2102 300563 upasswd_prog 2103 300564 gentranmentorsecurity 2104 300565 gentranmentorprovider 2105 300566 latituded 2106 latitude_license_server 2107 300567 gentranmentorreq1 2108 300568 gentranmentorreq2 2109 300569 gentranmentorreq3 2110 300570 rj_server 2111 300571 gws-rdb 2112 300572 gws-mpmd 2113 300573 gws-spmd 2114 300574 vwcalcd 2115 300575 vworad 2116 300576 vwsybd 2117 300577 vwave 2118 300578 online_assistant 2119 300579 internet_assistant 2120 300580 spawnd 2121 300581 procmgrg 2122 300582 cfgdbd 2123 300583 logutild 2124 300584 ibis 2125 300585 ibisaux 2126 300586 aapi 2127 300587 rstrt 2128 300588 hbeat 2129 300589 pcspu 2130 300590 empress 2131 300591 sched_server 2132 LiveScheduler 2133 300592 path_server 2134 LiveScheduler 2135 300593 c2sdmd 2136 300594 c2scf 2137 300595 btsas 2138 300596 sdtas 2139 300597 appie 2140 300598 dmi 2141 300599 pscd 2142 panther software corp daemon 2143 300600 sisd 2144 300601 cpwebserver 2145 300602 wwcommo 2146 300603 mx-mie 2147 300604 mx-mie-debug 2148 300605 idmn 2149 300606 ssrv 2150 300607 vpnserver 2151 300608 samserver 2152 300609 sams_server 2153 300610 chrysalis 2154 300611 ddm 2155 300612 ddm-is 2156 300613 mx-bcp-debug 2157 300614 upmrd 2158 300615 upmdsd 2159 300616 res 2160 300617 colortron 2161 300618 zrs 2162 300619 afpsrv 2163 300620 apxft 2164 300621 nrp 2165 300622 hpid 2166 300623 mailwatch 2167 300624 fos bc_fcrb_receiver 2168 300625 cs_sysadmin_svr 2169 300626 cs_controller_svr 2170 300627 nokia_nms_eai 2171 300628 dbg 2172 300629 remex 2173 300630 cs_bind 2174 300631 idm 2175 300632 prpasswd 2176 300633 iw-pw 2177 300634 starrb 2178 300635 Impress_Server 2179 300636 colorstar 2180 300637 gwugui 2181 300638 gwsgui 2182 300639 dai_command_proxy 2183 300640 dai_alarm_server 2184 300641 dai_fui_proxy 2185 300642 spai_command_proxy 2186 300643 spai_alarm_server 2187 300644 iris 2188 300645 hcxttp 2189 300646 updatedb rsched 2190 300647 urnd urn 2191 300648 iqwpsrv 2192 300649 dskutild 2193 300650 online 2194 300651 nlserv 2195 300652 acsm 2196 300653 dg_clar_sormsg 2197 300654 wwpollerrpc 2198 300655 wwmodelrpc 2199 300656 nsprofd 2200 300657 nsdistd 2201 300658 recollect 2202 300659 lssexecd lss_res 2203 300660 lssagend lss_rea 2204 300661 cdinfo 2205 300662 sninsr_addon 2206 300663 mm-sap 2207 300664 ks 2208 300665 psched 2209 300666 tekdvfs 2210 300667 storxll 2211 300668 nisse 2212 300669 lbadvise 2213 300670 atcinstaller 2214 300671 atntstarter 2215 300672 NetML 2216 300673 tdmesmge 2217 300674 tdmesmgd 2218 300675 tdmesmgt 2219 300676 olm 2220 300677 mediamanagement 2221 300678 rdbprog fieldowsrv 2222 300679 rpwdprog rpwd 2223 300680 sapi-trace 2224 300681 sapi-master-daemon 2225 300682 omdcuprog om-dcu 2226 300683 wwprocmon 2227 300684 tndidprog 2228 300685 rkey_setsecretprog 2229 300686 asdu_server_prog 2230 300687 pwrcntrl 2231 300688 siunixd 2232 300689 wmapi 2233 300690 cross_reference_ole 2234 300691 rtc 2235 300692 disp 2236 300693 sql_compilation_agent 2237 300694 tnsysprog 2238 300695 ius-sapimd 2239 300696 apteam-dx 2240 300697 rmsrpc 2241 300698 seismic_system 2242 300699 remote 2243 300700 tt1_ts_event nokia_nms 2244 300701 fxrs 2245 300702 onlicense 2246 300703 vxkey 2247 300704 dinis 2248 300705 sched2d schedule-2 2249 300706 sched3d schedule-3 2250 300707 sched4d schedule-4 2251 300708 sched5d schedule-5 2252 300709 sched6d schedule-6 2253 300710 sched7d schedule-7 2254 300711 sched8d schedule-8 2255 300712 sched9d schedule-9 2256 300713 adtsqry 2257 300714 adserv 2258 300715 adrepserv 2259 300716 [unknown] 2260 300717 caad 2261 300718 caaui 2262 300719 cescda 2263 300720 vcapiadmin 2264 300721 vcapi20 2265 300722 tcfs 2266 300723 csed 2267 300724 nothand 2268 300725 hacb 2269 300726 nfauth 2270 300727 imlm 2271 300728 bestcomm 2272 300729 lprpasswd 2273 300730 rprpasswd 2274 300731 proplistd 2275 300732 mikomomc 2276 300733 arepa-cas 2277 300734 [unknown] 2278 300735 [unknown] 2279 300736 ando_ts 2280 300737 intermezzo 2281 300738 ftel-sdh-request 2282 300739 ftel-sdh-response 2283 300740 [unknown] 2284 300741 [unknown] 2285 300742 [unknown] 2286 300743 [unknown] 2287 300744 [unknown] 2288 300745 vrc_abb 2289 300746 vrc_comau 2290 300747 vrc_fanuc 2291 300748 vrc_kuka 2292 300749 vrc_reis 2293 300750 hp_sv6d 2294 300751 correntmgr01 2295 300752 correntike 2296 300753 [unknown] 2297 300754 [unknown] 2298 300755 intransa_location 2299 300756 intransa_management 2300 300757 intransa_federation 2301 300758 portprot 2302 300759 ipmiprot 2303 300760 aceapi 2304 300761 f6000pss 2305 300762 vsmapi_program 2306 300763 ubertuple 2307 300764 ctconcrpcif 2308 300765 mfuadmin 2309 300766 aiols 2310 300767 dsmrootd 2311 300768 htdl 2312 300769 caba 2313 300770 vrc_cosimir 2314 300771 cmhelmd 2315 300772 polynsm 2316 300773 [unknown] 2317 300774 [unknown] 2318 300775 [unknown] 2319 300776 [unknown] 2320 300777 [unknown] 2321 300778 [unknown] 2322 300779 [unknown] 2323 300780 [unknown] 2324 300781 dsmrecalld 2325 300782 [unknown] 2326 300783 [unknown] 2327 300784 twrgcontrol 2328 300785 twrled 2329 300786 twrcfgdb 2330 BMC software 300787-300886 2331 [available] 300887 - 300999 2332 Sun Microsystems 301000-302000 [ 2000 numbers ] 2333 [available] 302001-349999 2334 American Airlines 350000 - 350999 2335 Acucobol Inc. 351000 - 351099 2336 The Bristol Group 351100 - 351249 2337 Amteva Technologies 351250 - 351349 2338 351350 wfmMgmtApp 2339 351351 wfmMgmtDataSrv 2340 351352 wfmMgmtFut1 2341 351353 wfmMgmtFut1 2342 351354 wfmAPM 2343 351355 wfmIAMgr 2344 351356 wfmECMgr 2345 351357 wfmLookOut 2346 351358 wfmAgentFut1 2347 351359 wfmAgentFut2 2348 [available] 351360 - 351406 2349 Sterling Software ITD 351407 csed 2350 351360 sched10d 2351 351361 sched11d 2352 351362 sched12d 2353 351363 sched13d 2354 351364 sched14d 2355 351365 sched15d 2356 351366 sched16d 2357 351367 sched17d 2358 351368 sched18d 2359 351369 sched19d 2360 351370 sched20d 2361 351371 sched21d 2362 351372 sched22d 2363 351373 sched23d 2364 351374 sched24d 2365 351375 sched25d 2366 351376 sched26d 2367 351377 sched27d 2368 351378 sched28d 2369 351379 sched29d 2370 351380 sched30d 2371 351381 sched31d 2372 351382 sched32d 2373 351383 sched33d 2374 351384 sched34d 2375 351385 sched35d 2376 351386 sched36d 2377 351387 sched37d 2378 351388 sched38d 2379 351389 sched39d 2380 351390 consoleserver 2381 351391 scheduleserver 2382 351392 RDELIVER 2383 351393 REVENTPROG 2384 351394 RSENDEVENTPROG 2385 351395 snapp 2386 351396 snapad 2387 351397 sdsoodb 2388 351398 sdsmain 2389 351399 sdssrv 2390 351400 sdsclnt 2391 351401 sdsreg 2392 351402 fsbatch 2393 351403 fsmonitor 2394 351404 fsdisp 2395 351405 fssession 2396 351406 fslog 2397 351407 svdpappserv 2398 351408 gns 2399 351409 [unkonwn] 2400 351410 [unkonwn] 2401 351411 [unkonwn] 2402 351412 axi 2403 351413 rpcxfr 2404 351414 slm 2405 351415 smbpasswdd 2406 351416 tbdbserv 2407 351417 tbprojserv 2408 351418 genericserver 2409 351419 dynarc_ds 2410 351420 dnscmdr 2411 351421 ipcmdr 2412 351422 faild 2413 351423 failmon 2414 351424 faildebug 2415 351425 [unknown] 2416 351426 [unknown] 2417 351427 siemens_srs 2418 351428 bsproxy 2419 351429 ifsrpc 2420 351430 CesPvcSm 2421 351431 FrPvcSm 2422 351432 AtmPvcSm 2423 351433 radius 2424 351434 auditor 2425 351435 sft 2426 351436 voicemail 2427 351437 kis 2428 351438 SOFTSERV_NOTIFY 2429 351439 dynarpc 2430 351440 hc 2431 351441 iopas 2432 351442 iopcs 2433 351443 iopss 2434 351444 spcnfs 2435 351445 spcvss 2436 351446 matilda_sms 2437 351447 matilda_brs 2438 351448 matilda_dbs 2439 351449 matilda_sps 2440 351450 matilda_svs 2441 351451 matilda_sds 2442 351452 matilda_vvs 2443 351453 matilda_stats 2444 351454 xtrade 2445 351455 mapsvr 2446 351456 hp_graphicsd 2447 351457 berkeley_db 2448 berkeley_db_svc 2450 351458 io_server 2451 351459 rpc.niod 2452 351460 rpc.kill 2453 351461 hmdisproxy 2454 351462 smdisproxy 2455 351463 avatard 2456 351464 namu 2457 351465 BMCSess 2458 351466 FENS_Sport 2459 351467 EM_CONFIG 2460 351468 EM_CONFIG_RESP 2461 351469 lodge_proof 2462 351470 ARCserveIT-Queue 2463 351471 ARCserveIT-Device 2464 351472 ARCserveIT-Discover 2465 351473 ARCserveIT-Alert 2466 351474 ARCserveIT-Database 2467 351475 scand1 2468 351476 scand2 2469 351477 scand3 2470 351478 scand4 2471 351479 scand5 2472 351480 dscv 2473 351481 cb_svc 2474 351482 [unknown] 2475 351483 iprobe 2476 351484 omniconf 2477 351485 isan 2478 BG Partners 351486 - 351500 2479 351501 mond 2480 351502 iqlremote 2481 351503 iqlalarm 2482 [available] 351504 - 351599 2483 Orion Multisystems 351600-351855 2484 [available] 351856 - 351899 2485 NSP lab 351900 - 351999 2486 [available] 351999 - 352232 2487 352233 asautostart 2488 352234 asmediad1 2489 352235 asmediad2 2490 352236 asmediad3 2491 352237 asmediad4 2492 352238 asmediad5 2493 352239 asmediad6 2494 352240 asmediad7 2495 352241 asmediad8 2496 352242 asmediad9 2497 352243 asmediad10 2498 352244 asmediad11 2499 352245 asmediad12 2500 352246 asmediad13 2501 352247 asmediad14 2502 352248 asmediad15 2503 352249 asmediad16 2504 352250 waruser 2505 352251 warlogd 2506 352252 warsvrmgr 2507 352253 warvfsysd 2508 352254 warftpd 2509 352255 warnfsd 2510 352256 bofproxyc0 2511 352257 bofproxys0 2512 352258 bofproxyc1 2513 352259 bofproxys1 2514 352260 bofproxyc2 2515 352261 bofproxys2 2516 352262 bofproxyc3 2517 352263 bofproxys3 2518 352264 bofproxyc4 2519 352265 bofproxys4 2520 352266 bofproxyc5 2521 352267 bofproxys5 2522 352268 bofproxyc6 2523 352269 bofproxys6 2524 352270 bofproxyc7 2525 352271 bofproxys7 2526 352272 bofproxyc8 2527 352273 bofproxys8 2528 352274 bofproxyc9 2529 352275 bofproxys9 2530 352276 bofproxyca 2531 352277 bofproxysa 2532 352278 bofproxycb 2533 352279 bofproxysb 2534 352280 bofproxycc 2535 352281 bofproxysc 2536 352282 bofproxycd 2537 352283 bofproxysd 2538 352284 bofproxyce 2539 352285 bofproxyse 2540 352286 bofproxycf 2541 352287 bofproxysf 2542 352288 bofproxypo0 2543 352289 bofproxypo1 2544 352290 bofproxypo2 2545 352291 bofproxypo3 2546 352292 bofproxypo4 2547 [available] 352293-370000 2548 370001 [unknown] 2549 370002 [unknown] 2550 370003 [unknown] 2551 370004 [unknown] 2552 370005 [unknown] 2553 370006 [unknown] 2554 370007 [unknown] 2555 370008 [unknown] 2556 370009 [unknown] 2557 370010 [unknown] 2558 370011 [unknown] 2559 370012 [unknown] 2560 370013 [unknown] 2561 370014 [unknown] 2562 370015 [unknown] 2563 370016 [unknown] 2564 370017 [unknown] 2565 370018 [unknown] 2566 370019 [unknown] 2567 370020 [unknown] 2568 370021 [unknown] 2569 370022 [unknown] 2570 370023 [unknown] 2571 370024 [unknown] 2572 370025 [unknown] 2573 370026 [unknown] 2574 370027 [unknown] 2575 [available] 370028 - 379999 2576 380000 opensna 2577 380001 probenet 2578 380002 [unknown] 2579 380003 license 2580 380004 na.3com-remote 2581 380005 na.ntp 2582 380006 probeutil 2583 380007 na.vlb 2584 380008 cds_mhs_agent 2585 380009 cds_x500_agent 2586 380010 cds_mailhub_agent 2587 380011 codex_6500_proxy 2588 380012 codex_6500_trapd 2589 380013 na.nm212 2590 380014 cds_mta_metrics_agent 2591 380015 [unkonwn] 2592 380016 na.caple 2593 380017 codexcapletrap 2595 Swiss Re 380018-380028 2596 380029 ncstat 2597 380030 ncnfsstat 2598 380031 ftams 2599 380032 na.isotp 2600 380033 na.rfc1006 2601 [available] 380034 - 389999 2602 Epoch Systems 390000 - 390049 2603 Quickturn Systems 390050 - 390065 2604 Team One Systems 390066 - 390075 2605 General Electric CRD 390076 - 390085 2606 TSIG NFS subcommittee 390086 - 390089 2607 SoftLab ab 390090 - 390099 2608 Legato Network Services 390100 - 390115 2609 390116 cdsmonitor 2610 390117 cdslock 2611 390118 cdslicense 2612 390119 shm 2613 390120 rws 2614 390121 cdc 2615 Data General 390122 - 390141 2616 Perfect Byte 390142 - 390171 2617 JTS Computer Systems 390172 - 390181 2618 Parametric Technology 390182 - 390191 2619 Voxem 390192 - 390199 2620 Effix Systems 390200 - 390299 2621 Motorola 390300 - 390309 2622 Mobile Data Intl. 390310 - 390325 2623 Physikalisches Institut 390326 - 390330 2624 Ergon Informatik AG 390331 - 390340 2625 Analog Devices Inc. 390341 - 390348 2626 Interphase Corporation 390349 - 390358 2627 NeWsware 390359 - 390374 2628 Qualix Group 390375 - 390379 2629 Xerox Imaging Systems 390380 - 390389 2630 Noble Net 390390 - 390399 2631 Legato Network Services 390400 - 390499 2632 Client Server Tech. 390500 - 390511 2633 Atria 390512 - 390517 2634 GE NMR Instruments 390518 - 390525 2635 Harris Corp. 390526 - 390530 2636 Unisys 390531 - 390562 2637 Aggregate Computing 390563 - 390572 2638 Interactive Data 390573 - 390580 2639 OKG AB 390581 - 390589 2640 K2 Software 390591 - 390594 2641 Collier Jackson 390595 - 390599 2642 Remedy Corporation 390600 - 390699 2643 Mentor Graphics 390700 - 390799 2644 AT&T Bell Labs (Lucent) 390800 - 390899 2645 Xerox 390900 - 390999 2646 Silicon Graphics 391000 - 391063 2647 Data General 391064 - 391095 2648 Computer Support Corp. 391096 - 391099 2649 Quorum Software Systems 391100 - 391199 2650 InterLinear Technology 391200 - 391209 2651 Highland Software 391210 - 391229 2652 Boeing Comp. Svcs. 391230 - 391249 2653 IBM Sweden 391250 - 391259 2654 Signature Authority Svc 391260 - 391271 2655 ZUMTOBEL Licht GmbH 391272 - 391283 2656 NOAA/ERL 391284 - 391299 2657 NCR Corp. 391300 - 391399 2658 FTP Software 391400 - 391409 2659 Cadre Technologies 391410 - 391433 2660 Visionware Ltd (UK) 391434 - 391439 2661 IBR-Partner AG 391440 - 391449 2662 CAP Programator AB 391450 - 391459 2663 Reichle+De-Massari AG 391460 - 391474 2664 Swiss Bank Corp (London) 391475 - 391484 2665 Unisys Enterprise Svr 391485 - 391489 2666 Intel - Test Dev. Tech. 391490 - 391499 2667 Ampex 391500 - 391755 2668 391756 naas-spare 2669 391757 naas-admin 2670 391758 isps 2671 391759 isps-admin 2672 391760 mars 2673 391761 mars-admin 2674 391762 attcis_spare0 2675 391763 attcis_spare1 2676 391764 mail-server 2677 391765 mail-server-spare 2678 391766 attcis_spare2 2679 391767 attcis_spare3 2680 391768 attcis_spare4 2681 391769 attcis_spare5 2682 391770 attcis_spare6 2683 391771 attcis_spare7 2684 Integrated Systems,Inc. 391772 - 391779 2685 Parametric Tech., Inc. 391780 - 391789 2686 Ericsson Telecom AB 391790 - 391799 2687 SLAC 391800 - 391849 2688 391850 qhrdata 2689 391851 qhrbackup 2690 391852 minutedata 2691 391853 prefecture 2692 391854 supc 2693 391855 suadmincrw 2694 391856 suadminotas 2695 391857 sumessage 2696 391858 sublock 2697 391859 sumotd 2698 staffware dev. (uk) 391860 - 391869 2699 Staffware Dev. (UK) 391870 - 391879 2700 391880 namesrvr 2701 391881 disksrvr 2702 391882 tapesrvr 2703 391883 migsrvr 2704 391884 pdmsrvr 2705 391885 pvrsrvr 2706 391886 repacksrvr 2707 391887 [unknown] 2708 Convex Computer Corp. 391888 - 391951 2709 391952 lookoutsrv 2710 391953 lookoutagnt 2711 391954 lookoutprxy 2712 391955 lookoutsnmp 2713 391956 lookoutrmon 2714 391957 lookoutfut1 2715 391958 lookoutfut2 2716 windward 391959 - 391967 2717 391968 sra_legato 2718 391969 sra_legato_imgsvr 2719 391970 sra_legato_0 2720 391971 sra_legato_1 2721 391972 sra_legato_2 2722 391973 sra_legato_3 2723 391974 sra_legato_4 2724 391975 sra_legato_5 2725 391976 sra_legato_6 2726 391977 sra_legato_7 2727 391978 sra_legato_8 2728 391979 sra_legato_9 2729 Brooktree Corp. 391980 - 391989 2730 Cadence Design Systems 391990 - 391999 2731 J. Frank & Associates 392000 - 392999 2732 Cooperative Solutions 393000 - 393999 2733 Xerox Corp. 394000 - 395023 2734 395024 odbc_sqlretriever 2735 3M 395025 - 395091 2736 Digital Zone Intl. 395092 - 395099 2737 Software Professionals 395100 - 395159 2738 Del Mar Solutions 395160 - 395164 2739 395165 ife-es 2740 395166 ife-resmgr 2741 395167 ife-aes 2742 395168 ife-bite 2743 395169 ife-loader 2744 395170 ife-satcom 2745 395171 ife-seat 2746 395172 ife-dbmgr 2747 395173 ife-testmgr 2748 395174 atrium_server 2749 395175 ase_director 2750 395176 ase_agent 2751 395177 ase_hsm 2752 395178 ase_mgr 2753 395179 ase_sim 2754 Hewlett-Packard 395180 - 395194 2755 XES, Inc. 395195 - 395199 2756 Unitech Products 395200 - 395249 2757 TransSys 395250 - 395505 2758 Unisys Govt Systems 395506 - 395519 2759 Bellcore 395520 - 395529 2760 IBM 395530 - 395561 2761 AT&T Network Services 395562 - 395571 2762 Data General 395572 - 395577 2763 Swiss Bank Corp 395578 - 395597 2764 Swiss Bank Corp 395598 - 395637 2765 Novell 395638 - 395643 2766 Computer Associates 395644 - 395650 2767 Omneon Video Networks 395651 - 395656 2768 [available] 395657 - 395908 2769 UK Post Office 395909 - 395924 2770 AEROSPATIALE 395925 - 395944 2771 Result d.o.o. 395945 - 395964 2772 DataTools, Inc. 395965 - 395980 2773 CADIS, Inc. 395981 - 395990 2774 Cummings Group, Inc. 395991 - 395994 2775 Cadre Technologies 395995 - 395999 2776 American Airlines 396000 - 396999 2777 Ericsson Telecom TM Div 397000 - 398023 2778 IBM 398024 - 398028 2779 Toshiba OME Works 398029 - 398033 2780 TUSC Computer Systems 398034 - 398289 2781 AT&T 398290 - 398320 2782 Ontario Hydro 398321 - 398346 2783 Micrion Corporation 398347 - 398364 2784 [available] 398365 - 398591 2785 Pegasystems, Inc. 398592 - 399616 2786 Spectra Securities Soft 399617 - 399850 2787 QualCom 399851 - 399866 2788 [available] 399867 - 399884 2789 Altris Software Ltd. 399885 - 399899 2790 ISO/IEC WG11 399900 - 399919 2791 Parametric Technology 399920 - 399949 2792 Dolby Laboratories 399950 - 399981 2793 [available] 399982 - 399991 2794 Xerox PARC 399992 - 399999 2795 # 2796 Next Inc. 200100000 - 200199999 2797 Netwise (RPCtool) 200200000 2798 Concurrent Computer Corp 200200001 - 200200007 2799 AIM Technology 200300000 - 200399999 2800 TGV 200400000 - 200499999 2801 # 2802 # Sun-assigned authentication flavor numbers 2803 # 2804 AUTH_NONE 0 /* no authentication, see RFC 1831 */ 2805 /* a.k.a. AUTH_NULL */ 2806 AUTH_SYS 1 /* unix style (uid+gids), RFC 1831 */ 2807 /* a.k.a. AUTH_UNIX */ 2808 AUTH_SHORT 2 /* short hand unix style, RFC 1831 */ 2809 AUTH_DH 3 /* des style (encrypted timestamp) */ 2810 /* a.k.a. AUTH_DES, see RFC 2695 */ 2811 AUTH_KERB 4 /* kerberos auth, see RFC 2695 */ 2812 AUTH_RSA 5 /* RSA authentication */ 2813 RPCSEC_GSS 6 /* GSS-based RPC security for auth, 2814 integrity and privacy, RPC 5403 */ 2816 AUTH_NW 30001 NETWARE 2817 AUTH_SEC 200000 TSIG NFS subcommittee 2818 AUTH_ESV 200004 SVr4 ES 2820 AUTH_NQNFS 300000 Univ. of Guelph - Not Quite NFS 2821 AUTH_GSSAPI 300001 OpenVision 2822 AUTH_ILU_UGEN 300002 Xerox 2823 - ILU Unsecured Generic Identity 2824 # 2825 # Small blocks are assigned out of the 39xxxx series of numbers 2826 # 2827 AUTH_SPNEGO 390000 2828 390000 - 390255 NFS 'pseudo' flavors for RPCSEC_GSS 2829 390003 - kerberos_v5 authentication, RFC 2623 2830 390004 - kerberos_v5 with data integrity, RFC 2623 2831 390005 - kerberos_v5 with data privacy, RFC 2623 2833 200000000 reserved 2834 200100000 NeXT Inc. 2836 18. Normative References 2838 [RFC4506] 2839 Eisler, M., "XDR: External Data Representation Standard", RFC 4506, 2840 May 2006 2842 [RFC2203] 2843 Eisler, M., Chiu, A., Ling, L., "RPCSEC_GSS Protocol Specification", 2844 RFC 2203, September 1997 2846 19. Informative References 2848 [XRPC] 2849 Birrell, A. D. & Nelson, B. J., "Implementing Remote Procedure 2850 Calls", XEROX CSL-83-7, October 1983. 2852 [VMTP] 2853 Cheriton, D., "VMTP: Versatile Message Transaction Protocol", 2854 Preliminary Version 0.3, Stanford University, January 1987. 2856 [DH] 2857 Diffie & Hellman, "New Directions in Cryptography", IEEE Transactions 2858 on Information Theory IT-22, November 1976. 2860 [RFC768] 2861 Postel, J., "User Datagram Protocol", STD 6, RFC 768, USC/Information 2862 Sciences Institute, August 1980. 2864 [RFC793] 2865 Postel, J., "Transmission Control Protocol - DARPA Internet Program 2866 Protocol Specification", STD 7, RFC 793, USC/Information Sciences 2867 Institute, September 1981. 2869 [RFC1094] 2870 Sun Microsystems, Inc., "NFS: Network File System Protocol 2871 Specification", RFC 1094, March 1989. 2873 [RFC1813] 2874 Callaghan, B., Pawlowski, B., Staubach, P., "NFS Version 3 Protocol 2875 Specification", RFC 1813, June 1995. 2877 [RFC1831] 2878 R. Srinivasan, "RPC: Remote Procedure Call Protocol Specification 2879 Version 2", RFC 1831, August 1995. 2881 [RFC1833] 2882 R. Srinivasan, "Binding Protocols for ONC RPC Version 2", RFC 1833, 2883 August 1995. 2885 [RFC2119] 2886 Bradner, S., "Key words for use in RFCs to Indicate Requirement 2887 Levels", RFC 2119, March 1997 2889 [RFC2623] 2890 Eisler, M., "NFS Version 2 and Version 3 Security Issues and the NFS 2891 Protocol's Use of RPCSEC_GSS and Kerberos V5", RFC 2623, June 1999. 2893 [RFC2695] 2894 Chiu, A., "Authentication Mechanisms for ONC RPC", RFC 2695, 2895 September 1999. 2897 [RFC2743] 2898 Linn. J., "Generic Security Service Application Program Interface 2899 Version 2, Update 1", RFC 2743, January 2000. 2901 [RFC3530] 2902 Shepler, S., Callaghan, B., Robinson, D., Thurlow, R., Beame, C., 2903 Eisler, M., Noveck, D., "Network File System (NFS) version 4 2904 Protocol", RFC 3530, April 2003. 2906 [RFC5226] 2907 Narten, T. and Alvestrand, H., "Guidelines for Writing an IANA 2908 Considerations Section in RFCs", RFC 5226, May 2008. 2910 20. Author's Address 2912 Address comments related to this memorandum to: 2914 nfsv4@ietf.org 2916 Robert Thurlow 2917 Sun Microsystems, Inc. 2918 500 Eldorado Boulevard, UBRM05-171 2919 Broomfield, CO 80021 2921 Phone: 877-718-3419 2922 E-mail: robert.thurlow@sun.com