IND (Inverse Neighbor Discovery) is defined in RFC 3122. IND allows a node that knows the link-layer address of a directly connected remote node to learn the IPv6 addresses of that node.
The principle of IND is a very simple. A node sends an Inverse Neighbor Discovery Solicitation message to request an IPv6 address corresponding to a link-layer address of the target node while also providing its own link-layer address to the target. The sender must send the following options in the Solicitation message:
These options are optional:
A solicited node sends Inverse Neighbor Discovery Advertisements message in response to IND Solicitation messages to a link-layer address of the target node. The sender node must send the following options in Advertisement message:
The sender of the Solicitation message stores the received information in its Neighbor Cache.
The sender node may send the MTU option in the Advertisement message. The Source/Target Link-Layer Address and MTU options are depicted in Link-Layer Address Determining section.