2.2.8 Update Notification Message

 An NBNS push partner sends an Update Notification Message to advertise its owner-version map to the NBNS pull partner. The Update Notification Message format is shown in the following diagram.


0


1


2


3


4


5


6


7


8


9

1
0


1


2


3


4


5


6


7


8


9

2
0


1


2


3


4


5


6


7


8


9

3
0


1

Common Replication Message Header (16 bytes)

...

...

Reserved

RplOpCode

Number of Owners

Owner Record (variable)

...

Initiator IPv4 Address

Common Replication Message Header (16 bytes):  The Common Replication Message Header as specified in section 2.2.2. Message Type field MUST be set to 3.

Reserved (3 bytes): An unsigned 24-bit integer. It MUST be set to 0 and ignored upon receipt.

RplOpCode (1 byte): An unsigned 8-bit integer.

Value

Meaning

0x04

Update notification without persistent connection. The receiving server MUST NOT propagate the notification to the other NBNS replication partner.

0x05

 Update notification without persistent connection. The receiving server SHOULD propagate the notification to the other NBNS replication partner.

0x08

 Update notification with persistent connection. The receiving server MUST NOT propagate the notification to the other NBNS replication partner.

0x09

 Update notification with persistent connection. The receiving server SHOULD propagate the notification to the other NBNS replication partner.

Other values MUST NOT be sent for this message. If received, the packets are silently discarded.

Number of Owners (4 bytes):  An unsigned 32-bit integer that denotes the number of Owner Records in the Owner Record field.

Owner Record (variable):  The Owner Record field shows the owner NBNS server information, as specified in section 2.2.7.1.

Initiator IPv4 Address (4 bytes):  The Update Notification Message can be propagated from machine to machine. This is the IPv4 address of the NBNS server that generates the original Update Notification Message.