Re: LMP & neighbor discovery (verify_id)

[Dimitri.Papadimitriou@alcatel.be]

Yangguang,

That's seems more than clear from the definition of the VERIFY_ID
object but Michiel mentioned he wants a node ID as indicated in 
the frame format he provided (for "discovery" purposes):

> +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
> | 1   2   3   4   5   6   7   8   9   10  11  12  13  14  15  16|
> +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
> |CRC|Typ|Dis|       Node Identifier         |  Port Identifier  |
> +---+---+---+-------------------------------+-------------------+ 

If this is not the case (ie the node id is not a node unique
value), then please provide more information on how the node 
id is defined in the above frame this from the definition we 
have received from him:

> Node Identifier
>   The "node identifier" is the IPv4 address that identifies the
>   sending Node_Id. The IPv4 address is encoded in 8 hex characters.

Link Property Correlation message related exchanges are not 
coupled with the above information exchange - this also part
of the global request as far as i understand it - so i don't 
clearly see your point with respect to "discovery" (moreover
nothing precludes the subsequent usage of the Verify ID as 
currently defined when TE Links are build up and wanted to be 
verified).
 
thanks,
- dimitri.

Yangguang Xu wrote:
> 
> Dimitri,
> 
> > In LMP the VERIFY ID object seems to correspond to the
> > Node ID that you require; in fact from its definition:
> >
> > "The VERIFY_ID object contains a node-unique value that is
> > assigned by the generator of the BeginVerifyAck message.
> > This value is used to uniquely identify the Verification
> > process from multiple LMP neighbors and/or parallel Test
> > procedures between the same LMP neighbors."
> >
> > This i-d can be used for the purpose you have mentioned.
> > p54 of the same document gives also you more information
> > on this.
> 
> I thought about this, yet, it doesn't seem to work. Indeed, both Michiel and
> Jonathan pointed me the case that when two NEs have parallel TE links, you need
> different verify IDs.
> 
> Yangguang

-- 
Papadimitriou Dimitri 
E-mail : dimitri.papadimitriou@alcatel.be 
Website: http://www.rc.bel.alcatel.be/~papadimd/index.html
Address: Alcatel - Optical NA, Fr. Wellesplein, 1 
         B-2018 Antwerpen, Belgium
Phone:   Work: +32 3 2408491 - Home: +32 2 3434361