What is NBP?

The Name Binding Protocol (NBP) allows you to bind a name to the internal storage address of the entity and register that mapping so that other entities can follow.

An NBP name was displayed by the applications to the users and used addresses internally to locate entities. When we register the entity's name and address, NBP validates its uniqueness.

Generally, an entity name consists of three fields, which are as follows −

  • The object − Object field is used to identify the user of the system. Because of the applications this value is set to the owner name, where the user specifies with the help of the Sharing Setup control panel.

  • The type − Type field identifies the type of service that the entity provides, consider an example, Mailbox on a server. The same entity type can find one another and identify the partners by looking up addresses based on the type portion of the name alone.

  • The zone − The zone type which is used to identify the zone to which the node belongs. Generally, we will not specify this value; when we register the process, we specify an asterisk (*) symbol for this field. NBP interprets the asterisk to mean the current zone or no zone. In the case of a simple network configuration the node is not divided into zones.


The features of NBP are as follows −

  • The function of Name Binding Protocol is used to translate names to the addresses.

  • NBP is helpful in transferring packets over the network which is used to match network addresses with named entities.

  • If the node is matching then it responds to protocol otherwise it will not.

  • NBP is a dynamic and distributed protocol.

  • It is present on top of the Datagram Delivery Protocol.

  • It offers limited functionality.

  • NBP provides Meta information for clients.