Re: [8023-CMSG] Problem statement

[David V James <dvj@xxxxxxxxxxxx>]

Title: Problem statement

Hmm,...

 

1) I had thought the primary reason for congestion management was to avoid

the short-term problem of loss of traffic during coincidental peaks in traffic.

 

The term "oversubscription" seems to imply a long-term flow control solution.

I suppose that's OK if the original intent of (1) was misperceived or has changed.

 

DVJ

 

David V. James
3180 South Ct
Palo Alto, CA 94306
Home: +1.650.494.0926
      +1.650.856.9801
Cell: +1.650.954.6906
Fax:  +1.360.242.5508
Base: dvj@alum.mit.edu 

-----Original Message-----
From: owner-stds-802-3-cm@listserv.ieee.org [mailto:owner-stds-802-3-cm@listserv.ieee.org]On Behalf Of Booth, Bradley
Sent: Monday, September 13, 2004 1:59 PM
To: STDS-802-3-CM@listserv.ieee.org
Subject: [8023-CMSG] Problem statement

Greetings,

I wasn't able to attend the CMSG meeting in July, due to being a little busy in 802.3an, but I was looking at the problem statement that I believe was adopted by the SG.  I was a little concerned that the statement only mentioned 802.3 MAC Clients and nothing about the 802.3 MAC itself.  I was wondering if the following problem statement would still be palatable to everyone:

"802.3 MAC Clients need the ability to communicate, via 802.3 MACs, congestion information to avoid oversubscription."

Thoughts?  Feedback?

Thanks,
Brad