s procedure discovers peer's IP address and establishes LMP adjacency relationship automatically. Adjacency relationship requires at least one bidi- rectional control channel (multiple can be used simultaneously) between peers. In order to run the control plane through the link and establish an adjacency relationship, a control channel traversing the link is needed. This is generally defined at the control plane level by a set of parameters that are negotiated by LMP during the adjacency discovery. Once set up, the control channel maintenance is done by LMP by periodic Hello messages. 8.3.2.7.2 Link Connectivity Verification A GLSR knows the local address (ID) for data links that connect its ports to the ports of a peer GLSR. In the absence of a suitable mechanism, the GLSR does not know how a peer identifies the same data links and has no a priori information about the state of the data links. Link IDs mapping between peers should be made in order to have a common unam- biguous association between a link and a link ID and in order to understand signaling messages received from a peer where the link ID is that assigned from the peer. Links ID association is performed by the LMP using test message contains two key parameters: sender's local data_link_ID and Verify_ID; the first is the ID that the GLSR assigns to a link, the second is the request done to the GLSR on the other side of the link: verify the link ID correspondence. Verify_ID also contains the GLSR ID. The GLSR on the other side of the link looks at Verify_ID to understand from which adja- cent GLSR the message comes from. The peer answers with TestStatusSuccess that contains peer's local data link ID and the data link ID from the Test message. 8.3.2.7.3 Link Property Correlation This is a process of synchronizing properties of data channels (e.g., supported switching and encoding types, maximum bandwidth that can be reserved, etc.) between peers and aggregation of data channels to form one TE link done by exchange of messages contain- ing the parameter