The MPLS WG Archive

[David Charlap <David.Charlap@marconi.com>]

Gopalkrishna Panicker wrote:
> 
> Per my understanding of RFC 2209, a Resv state block
> is created for every {Flowspec, Filterspec(s)}.

If your implementation is based on the architecture that RFC 2209, then
you have an RSB for every uniquely received Resv message.  Which is
keyed on session, sender (filterspec) and next-hop address.

Flowspec is not a key, but a value.

> 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.

Correct.

> 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 ?

No.  It just means that the one MESSAGE_ID will refresh multiple RSBs
when it appears in an SRefresh message.

-- David