Is it possible to simulate the effect of a WF reservation using the SE style?
-
When an application asked for WF, the RSVP daemon on the receiver host could use local path state to create an equivalent SE reservation that explicitly listed all senders.
-
However, an SE reservation forces the packet classifier in each node to explicitly select each sender in the list, while a WF allows the packet classifier to simply "wild card" the sender address and port. When there is a large list of senders, a WF style reservation can therefore result in considerably less overhead than an equivalent SE style reservation. For this reason, both SE and WF are included in the protocol.
|
