Binding is the process by which an RPC client establishes a relationship with a server that supports an interface, object, or some other resource the client is interested in. Since clients operate on server-held resources by making RPCs, you can think of binding, specifically, as creating the state required for an RPC to be made. In practice, the work of binding clients to servers normally involves name and endpoint mapping services. Strictly speaking, however, neither of these services is required for binding, since well-known bindings and endpoints can be used (in the form of string bindings). This topic discusses the underlying binding model, apart from the use of name and endpoint services. It forms an essential introduction for the discussion of name and endpoint services that follows in Overview - Using the DCE Name Service.