The MPLS WG Archive

[Suresh Katukam <skatukam@cisco.com>]

I think it is useful to have Message IDs for all messages. Even for 
optical/SONET links too.
If you have OF/OB, or IF/IB control channels, it is quite possible that you 
wanted to send
a refresh PATH message and then send a PATH TEAR. If you do not use message 
ids,
it is quite possible that PATH TEAR may come first and then the PATH 
message at the
other end. This would tear down and create the circuit at the other end of 
the link.

In effect, to find out of order messages.

-- Suresh

At 03:48 PM 2/13/2002 -0800, Ping Pan wrote:
>If I recall correctly, at one point, we were worried about the noisy 
>links, where without some sort of ack, RSVP messages may get dropped. In 
>this case, having msgids for teardown and error would be nice. Depending 
>on where you want to apply refresh reduction, you have the option where to 
>apply msgid's. On SONET/optial links, I am not sure it's useful to use 
>msgid for error and teardown messages.
>
>2 cents,
>
>- Ping
>
>
>Sandeep B wrote:
>
>>I have a more basic question.
>>Ping -
>>Why do we need to send PATHTEAR, RESVTEAR, PATHERR, RESVERR with Msgids. 
>>These are all triggered messages and what purpose do they solve when we 
>>send these packets with msgid.
>>-Sandeep
>>
>>_________________________________________________________________
>>Send and receive Hotmail on your mobile device: http://mobile.msn.com
>
>