tsvwg-2----Page:9
1 2 3 4 5 6 7 8 9 10
|
Open issues Do we include this tspec in the ResvTear message and specify that the Aggregator *not* ignore it? Do we need to address the case in which the Err message are sent, but the flow is not reduced in a timely manner? unnecessary if above bullet answer is yes Should the text be opened up to individual flow considerations? to allow endpoints to adjust to the decreased bandwidth allocation (perhaps use a lower bw codec) comments to this affect already |