The
Rate Ad Hoc (hence known as RAH) met and agreed to discuss concerns and
then plan how to continue. The following people expressed the following
concerns.
Necdet Uzun: No packet
loss on ring; not preclude STB; not complicate MAC design; high priority
should be shaped to CBR; jitter can be worsened by control packets; ring
not owned/operated by one entity, can trust all MACs, but not all clients
John Lemon:STB
(or small second buffer of DTB) doesn't compromise DTB on same ring, such
as effecting jitter sensitive traffic; reservation per link, different
allowed; reserved traffic jitter bounded by N MTU; topology negotiated
secondary buffer size determining ramp up of low pri traffic; loss <
jitter < utilization; not constrained by 802 bridging, just support
superset of 802 bridging – dumb client sends all BE traffic
Harry Peng: STB design
is not precluded; must interop, but maybe at slightly reduced performance;
separation of access jitter and transit jitter; constrained by 802 bridging
compliance, make sure we don't break it
Luis Rovira: concerned
about complexity; wants simulation/calculation proof/certainty
Stein Gjessing: how
do we specify what values are advertised and how do we specify node's behavior
to comply
Italo Busi: negotiate
for priorities for loss, jitter, utilization
Yiming Yao: allow
customer to choose between loss, jitter, and utilization
Anoop: should not
preclude VDQ; should allow algorithm other than ramp up/down
Other attendees:
Tricia Hill, Vitorio Mascolo, Yongdong Zhao, Rhett Brikovskis, Li Mo, Peter
Jones.
Going forward:
-
General interest messages sent to reflector
with titles starting with RAH
-
Ad hoc bridge + face to face (9:00 am
PT, Tuesdays, starting 3/19), Necdet sets bridge
-
Define priority, reservation, reclamation,
classes of service, etc and give usage
-
Propose how to meet all of above requirements
-
Document
-
Define scenarios to evaluate against
-
Simulate against simulation reference
model