What is NBP?

The Name Binding Protocol (NBP) is a network protocol that allows entities to bind human-readable names to their network addresses and register these mappings so other entities can locate them. NBP was primarily used in AppleTalk networks to provide a directory service for network resources.

NBP displays user-friendly names to applications while using internal addresses to locate entities on the network. When an entity registers its name and address, NBP validates the uniqueness of that name within the network zone.

NBP Name Structure

An NBP entity name consists of three fields separated by specific delimiters:

• Object − Identifies the specific resource or user. This field is typically set to a user-defined name specified through system configuration panels, such as the owner name in AppleTalk networks.

• Type − Specifies the service type provided by the entity, such as "LaserWriter" for printers or "AFPServer" for file servers. Entities of the same type can locate each other by searching based on the type field alone.

• Zone − Identifies the AppleTalk zone containing the entity. When registering, an asterisk (*) can be used to indicate the current zone. In simple network configurations without zones, this field may be omitted.

Key Features

• Name-to-address translation − Converts human-readable names into network addresses for communication.

• Dynamic and distributed − Operates as a distributed directory service without requiring centralized servers.

• Network packet matching − Nodes respond to NBP queries only if they match the requested entity name.

• Built on DDP − Functions on top of the Datagram Delivery Protocol in the AppleTalk protocol suite.

• Metadata provision − Provides additional information about network entities to client applications.

How NBP Works

When a client needs to locate a network resource, it broadcasts an NBP lookup request containing the desired entity name. All nodes on the network receive this request, but only those matching the specified name pattern respond with their network addresses. This distributed approach eliminates the need for centralized name servers.

Conclusion

NBP provides essential name resolution services in AppleTalk networks by translating human-readable names to network addresses. Its distributed architecture and three-part naming scheme (Object:Type@Zone) enable efficient resource discovery without centralized directory servers.