State Management Points of Commonality: The following semantics are needed RESERVE/TEAR/REFRESH (full and summary)/ACK/NACK Open issues: Do we need the following explicitly? PATH (setup path state to allow receiver initiation) For particular resource management models, COMMIT (commit resources previously reserved) MODIFY (modify existing reservation) Is the full/summary distinction more to do with the QoS object? How are the semantics reflected as message types two message types: “manipulate state”, reponse, OR one to one mapping between message types and semantics |