Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

RE: [RPRWG] RAH: Minutes of Rate Ad Hoc meeting



All:
going through my notes I would like to address certain terms.
 
Terms for the RAH:
 
objectives: scalable
objectives: meet applications, SLA enabled
objectives: robust, carrier grade?
 
reserve 1: reserved all the way around the ring
reserve 2: reserved on a link
reclaimed BW
non-reclaimed BW
ring access
ingress access
QoS classes: High, medium, and low
QoS classes: A, B, and C
 
 
 
Behavior: packet loss
Behavior: jitter
    access jitter, ring fitter
Behavior: delay
Behavior: utilization
    throughput and goodput
 
Fairness behaviors
    weighted
   
I may have missed some we can capture and discuss during today's call.
   
... Harry
-----Original Message-----
From: John Lemon [mailto:jalemon@xxxxxxxxx]
Sent: Thursday, March 14, 2002 9:28 PM
To: stds-802-17@xxxxxxxx
Subject: [RPRWG] RAH: Minutes of Rate Ad Hoc meeting

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:

  1. General interest messages sent to reflector with titles starting with RAH
  2. Ad hoc bridge + face to face (9:00 am PT, Tuesdays, starting 3/19), Necdet sets bridge
  3. Define priority, reservation, reclamation, classes of service, etc and give usage
  4. Propose how to meet all of above requirements
  5. Document
  6. Define scenarios to evaluate against
  7. Simulate against simulation reference model