3 ;;Quote: Clearinghouse provides support for system administration of its distributed environment

3+ ;;Quote: a Clearinghouse contains information needed by system administrators of the distributed environment; e.g., users and workstations

3 ;;Quote: Clearinghouse easily adds new networks, adds servers, or merges networks

24 ;;Quote: Clearinghouse command to return all aliases for an object

26 ;;Quote: use lookupGeneric to return names which have a property

26 ;;Quote: in Clearinghouse lookupGeneric, a wild card for a local name returns all names with a property

26 ;;Quote: in Clearinghouse can enumerate all names in a domain

27 ;;Quote: in Clearinghouse, can get the set of properties assigned to a name

28 ;;Quote: use lookupGeneric to find all printers in a domain

32 ;;Quote: Clearinghouse stubs follow a simpler protocol than servers; lots of them, offline frequently, change frequently

32 ;;Quote: domain and organization clearinghouses share information freely; trust is assumed among servers

33 ;;Quote: for Clearinghouse servers, trust is an equivalence relation (commutative and transitive); simplifies access control

35 ;;Quote: Clearinghouse automatically resolves aliases without involving the stub

37 ;;Quote: Clearinghouse uses timestamps to detect subsumed update requests

38 ;;Quote: in Clearinghouse, periodically compare databases in case broadcast fails

38 ;;Quote: simultaneous, conflicting updates indicate an external coordination problem

38 ;;Quote: Clearinghouse discards requests if subsumed or if all siblings are consistent

38 ;;Quote: Clearinghouse updates last a week -- long-down servers re-initialize themselves

39 ;;Quote: Clearinghouse assumes inconsistent requests are due to lost or late requests

41 ;;Quote: Clearinghouse uses an access control list for each operation, domain

43 ;;Quote: Clearinghouse sentry to verify and forward internetwork requests

46 ;;Quote: Clearinghouse property names assigned by a naming authority (for ease of merging)