The MPLS WG Archive

[Ping Pan <pingpan@juniper.net>]

Each RSVP Resv message can be represented via a MESSAGE_ID.

This implies the following:

1. Per RSVP, you can combine multiple filters within a single Resv, in 
which case you need to track the message id for all the filters at both 
sending and receiving nodes. I know, it can be a pain in the ass to 
handle this. :-)

2. To simplify the code, when you send refresh messages, you have the 
option to force one filter per Resv.

Hope this will help!


- Ping

Gopalkrishna Panicker wrote:

> Hello,
> 
> I have a question regarding the use of MESSAGE_ID
> object in a resv message.
> 
> Per my understanding of RFC 2209, a Resv state block
> is created for every {Flowspec, Filterspec(s)}.
>  
> If a session uses FF style and there are 
> multiple senders, a SINGLE resv message carries 
> a {flowspec,filterspec} set for each sender.
> This will result in RSB being created for each such
> set. 
> 
> Now if ROR is used and as only one MESSAGE_ID object 
> is allowed per message, should a separate resv message
> be sent for each distinct reservation ? 
> 
> 
> Cheers,
> 
> Gopal
> 
> 
> __________________________________________________
> Do You Yahoo!?
> LAUNCH - Your Yahoo! Music Experience
> http://launch.yahoo.com
> 
> 
>