nsis-8----Page:12
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
|
QoS Objects Contents of QoS object should be opaque to the NSLP This is how several of the following subtleties are captured: Two phase (reserve/commit) reservation Reservation range (minumum/desirable QoS) Partial reservations allow for reservation even if some nodes rejected it Accumulation of end-to-end QoS parameters (e.g. delay) Pre-emption of resources for one flow by another Can use protocol features appropriate for resource management functionality (e.g. stateless NTLP operation for per-class resource management); this is left as implementation freedom Problem of having interoperable QoS models needs to be addressed by someone – by who and when? |