231 ;;Quote: we treat information from a telephone clearinghouse as a hint which is verified when we make a call

231 ;;Quote: the telephone clearinghouse maps between finding objects by name, by number, or by subject

232 ;;Quote: dynamic binding of names to addresses allows graceful adaptation to changes

232 ;;Quote: telephone books are decentralized for size reduction and disambiguation of names

232 ;;Quote: the telephone clearinghouse require clients to resolve ambiguities

232 ;;Quote: users initiate directory updates that the telephone company installs

232 ;;Quote: telephone company provides a naming authority to allocate telephone numbers

233 ;;Quote: if someone moves, the old telephone is out-of-service and provides forwarding information

233 ;;Quote: telephone clearinghouse only maintains phone number for your name of yourself; others by still use nicknames

235 ;;Quote: an absolute name means the same thing when given to another client

236 ;;Quote: a hierarchical name allows decentralization and suggests a search path

237 ;;Quote: should be able to join naming universes, e.g., north america merged via area codes

237 ;;Quote: should hierarchical name have a constant or a variable number of levels

238 ;;Quote: a Clearinghouse names consists of localName:domain:organization

238 ;;Quote: every Clearinghouse object has an absolute, distinguished name

238 ;;Quote: a Clearinghouse object may have an alias for its distinguished name; aliases are unique

239 ;;Quote: equal naming domains or organizations does not imply physical adjacency

239 ;;Quote: even though relative naming is simpler, absolute naming has clear advantages

239 ;;Quote: three-level hierarchical names simplify naming while still allowing merges of networks

240 ;;Quote: Clearinghouse uses legal names for people to reduce ambiguities

240 ;;Quote: Clearinghouse aliases used as short names for ease of typing; aliases are unique

240 ;;Quote: even if people have the same legal name in a domain, pick unique names

241 ;;Quote: a Clearinghouse property has a name, a type and a value

241 ;;Quote: a Clearinghouse item is an uninterpreted block of data (a property type)

241 ;;Quote: a Clearinghouse group is a set of names (a property type)

242 ;;Quote: a user profile contains names of mail and file servers instead of addresses; allows relocation of servers

242 ;;Quote: Clearinghouse's set of names allows simultaneous updates

242 ;;Quote: lookupGeneric defines a yellow-pages for Clearinghouse; e.g., find Help Service

243 ;;Quote: Clearinghouse includes wild card matches

243 ;;Quote: add wild cards to match partial names by full names

243 ;;Quote: Clearinghouse clients are machines so all interaction must be automated

243 ;;Quote: Clearinghouse is decentralized and replicated

243 ;;Quote: distributed systems increase efficiency, security, and reliability

243 ;;Quote: Clearinghouse assumes one global database that is decentralized

243 ;;Quote: clients may use any name known anywhere in Clearinghouse

244 ;;Quote: uniform access to Clearinghouse by a stub on each client that knows a server

244 ;;Quote: data (hints) stored by Clearinghouse may be inconsistent or incorrect

244 ;;Quote: Clearinghouse guarantees that information is eventually consistent and correct

244 ;;Quote: the Clearinghouse contains the truth about an entry or will contain it soon

244 ;;Quote: depending on time scale the Clearinghouse holds either truth or hint

245 ;;Quote: use early binding for performance and late binding when early binding becomes invalid

246 ;;Quote: every domain has a domain clearinghouse; contains all mappings for every name in domain

246 ;;Quote: the organization CHServers contains the network addresses for domain clearinghouses

247 ;;Quote: the organization CHServers contains a list of domain clearinghouses for each domain

247 ;;Quote: an organization clearinghouse is in CHServers; it contains names and address for its domain clearinghouses

247 ;;Quote: every Clearinghouse server is an organization clearinghouse for CHServers:CHServers; provides access to every organization clearinghouse

248 ;;Quote: distinguish physical, Clearinghouse servers from logical domain and organizational clearinghouses

248 ;;Quote: Clearinghouse stubs must use broadcast to locate a server that's moved

249 ;;Quote: if a clearinghouse server does not include a domain clearinghouse; it returns the names and addresses of servers that are clearinghouses

249 ;;Quote: Clearinghouse domain servers can keep direct pointers or replicas of other domain clearinghouses

250 ;;Quote: Clearinghouse servers broadcast update requests to their siblings

250 ;;Quote: Clearinghouse authenticates all update requests against requesters credentials

251 ;;Quote: Clearinghouse attaches an access control list to each domain and property

251 ;;Quote: binding mechanism for network-visible objects is needed for large network-based systems; e.g., Clearinghouse

252 ;;Quote: machines may have multiple network addresses but objects may reside on only one machine

252 ;;Quote: check an address by checking the object's unique identifier

252 ;;Quote: under Clearinghouse, address of object is network address plus unique id.