Limitations of current Ethernet switch architectures for enhanced flow control and service differentiation

One of the new challenges associated with full‐duplex Ethernet is that of providing for network congestion control. The IEEE 802.3x Standard does not specify the switch architecture for implementing PAUSE flow control or at what point a MAC Control entity actually generates a PAUSE frame. This is an...

Full description

Saved in:
Bibliographic Details
Published inInternational journal of network management Vol. 19; no. 3; pp. 153 - 174
Main Authors Aweya, James, Montuno, Delfin Y., Ouellette, Michel
Format Journal Article
LanguageEnglish
Published Chichester, UK John Wiley & Sons, Ltd 01.05.2009
Subjects
Online AccessGet full text

Cover

Loading…
More Information
Summary:One of the new challenges associated with full‐duplex Ethernet is that of providing for network congestion control. The IEEE 802.3x Standard does not specify the switch architecture for implementing PAUSE flow control or at what point a MAC Control entity actually generates a PAUSE frame. This is an implementation issue that is product specific and as a result many different switch architectures are possible. There are also a number of limitations of the PAUSE flow control mechanism when implemented in Ethernet switches. These issues have not been adequately addressed in the literature. In addition, multimedia traffic such as real‐time voice and streaming video are now being deployed over switched Ethernet networks, thus calling for congestion control with service differentiation for the various classes of traffic. Here we examine current Ethernet switch architectures and show that the PAUSE flow control when implemented in these architectures does not provide service selectivity and differentiation, making it unsuitable for real‐time traffic. Copyright © 2008 John Wiley & Sons, Ltd.
Bibliography:istex:AFAB056B6CDF0A95DD058795BC30A1D2E2CDCACA
ark:/67375/WNG-RCFPQLFG-5
ArticleID:NEM690
ObjectType-Article-2
SourceType-Scholarly Journals-1
ObjectType-Feature-1
content type line 23
ISSN:1055-7148
1099-1190
DOI:10.1002/nem.690