4.1 Merging Owner-Version Maps from Different Partners

When an NBNS server has received Owner-Version Map Response messages from its push partners, it merges the maps to determine the partner that has the latest version for an owner, and what the range of versions on the partner are. Below is an example. Suppose that the pull partner with IPv4 address IPa has two push partners: push partner1 with IPv4 address IPb, and push partner 2 with IPv4 address IPc. The pull partner currently knows the owners with the following IPv4 addresses: IPa (itself), IPb (push partner 1), IPc (push partner 2), and IPd (a nonpartner replicated from push partner 1). The owner and maximum version table on the pull partner might look like the following table.

 Owner IPv4 address

 Maximum version number

IPa

1023

IPb

521

IPc

643

IPd

758

The owner and maximum version map from push partner 1 might look like the following table.

 Owner IPv4 address

 Maximum version number

IPa

764

IPb

900

IPc

326

IPd

958

The owner and maximum version map from push partner 2 might look like the following table.

 Owner IPv4 address

 Maximum version number

IPa

679

IPb

745

IPc

1329

IPe

453

The merged table looks like the following. Note that now the pull partner gets to know a new NBNS server (IPe) through push partner 2.

 Owner IPv4 address

 Maximum version number

 Partner with the maximum version number

IPa

1023

self

IPb

900

Partner 1

IPc

1329

Partner 2

IPd

958

Partner 1

IPe

453

Partner 2

After obtaining the merged owner-version the preceding table, the pull partner sends a Name Records Request message to the push partners to actually get the name records. The following table shows the messages to be sent.

 Owner

 Push partner to send message to

 Minimum version in the request

 Maximum version in the request

IPb

Push partner 1

522

900

IPc

Push partner 2

644

1329

IPd

Push partner 1

759

958

IPe

Push partner 2

1

453