RE: [RPRWG] Scheduling
All,
I have seen a variety of emails, which share the opinion of the following:
-----Original Message-----
From: owner-stds-802-17@xxxxxxxx [mailto:owner-stds-802-17@xxxxxxxx]On
Behalf Of Sushil Pandhi
Sent: Wednesday, April 04, 2001 2:03 PM
To: William Dai
Cc: stds-802-17@xxxxxxxx
Subject: Re: [RPRWG] Scheduling
I think 3 priorities seem reasonable: 1) 1 for best effort, 2) 1 for
guarnateed but non-SYNCH traffic and 3) 1 for SYNCH traffic and for RPR
Network Control messages.
-Sushil
<<<<< End of message <<<<<
I happend to agree with this conclusion.
But, I would like to strive toward a common
taxonomy (i.e. glossary) for these three classes.
As an editor, I like to have three distinct one-word names.
Terms like "best effort" have the problem that they are hard
to parse when included in sentences. I'll throw out a few
ideas and ask if anyone has any better ideas:
synchronous - A class of provisioned traffic with guaranteed bandwidth and
lowest latency.
asynchronous - A clsss of provisioned traffic with guaranteed bandwidth and
bounded latency.
residual - A class of traffic limited to consumption of unprovisioned or
unused provisioned bandwidth. Note that RPR attempts to divide residual
bandwidth fairly among nodes with queued residual traffic.
These names are not too bad, but I am a bit concerned that the term
asynchronous applied to residual as well. Perhaps the terms should be:
Provisioned synchronous
Provisioned asynchronous
Unprovisioned asynchronous
But, that seems to be a bit too verbose.
Any other ideas non naming?
DVJ