RFC 1833 (rfc1833) - Page 3 of 14

Binding Protocols for ONC RPC Version 2

RFC 1833        Binding Protocols for ONC RPC Version 2      August 1995


   those addresses publicly available.

   The RPCBIND program also aids in broadcast RPC.  A given RPC program
   will usually have different transport address bindings on different
   machines, so there is no way to directly broadcast to all of these
   programs. The RPCBIND program, however, does have a well-known
   address.  So, to broadcast to a given program, the client actually
   sends its message to the RPCBIND program located at the broadcast
   address. Each instance of the RPCBIND program that picks up the
   broadcast then calls the local service specified by the client.  When
   the RPCBIND program gets the reply from the local service, it sends
   the reply back to the client.

2.1 RPCBIND Protocol Specification (in RPC Language)

/*
 * rpcb_prot.x
 * rpcbind protocol, versions 3 and 4, in RPC Language
 */

/*
 * rpcbind address for TCP/UDP
 */
const RPCB_PORT = 111;

/*
 * A mapping of (program, version, network ID) to address
 *
 * The network identifier  (r_netid):
 * This is a string that represents a local identification for a
 * network. This is defined by a system administrator based on local
 * conventions, and cannot be depended on to have the same value on
 * every system.
 */
struct rpcb {
 unsigned long r_prog;    /* program number */
 unsigned long r_vers;    /* version number */
 string r_netid;        /* network id */
 string r_addr;         /* universal address */
 string r_owner;        /* owner of this service */
};

struct rp__list {
 rpcb rpcb_map;
 struct rp__list *rpcb_next;
};





Srinivasan                  Standards Track