1 / 5

ETC/PFC Convergence Discussion

This document discusses the convergence proposals for ETS and PFC, emphasizing the need for simplicity and flexibility in network configurations. Both ETS and PFC were created with consensus among various authors, aiming to avoid unnecessary restrictions on implementation. A recent proposal complicates ETS and PFC by enforcing additional restrictions and predefined mappings between traffic classes and priorities. This raises concerns about limiting product use cases and misconfiguration risks in data centers. The recommendation is to adhere to the original ETS goals of providing flexible and simple solutions.

hinda
Télécharger la présentation

ETC/PFC Convergence Discussion

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ETC/PFC Convergence Discussion Craig W. Carlson, QLogic Manoj Wadekar, QLogic Derek Rhode, QLogic

  2. Background • Both ETS and PFC proposals were submitted with consensus of many authors • Original goal of ETS was to “keep it simple” • ETS specification was to not dictate implementation • At last meeting a proposal was brought in that places additional restrictions on, and complicates ETS and PFC • az-pelissier-convergence-proposal-0708.pdf

  3. The issue… • Goal of ETS has been to define consistent configurability • Priority - Traffic class mapping is internal issue to a product • Has not been defined by 802.1 • Needs more discussion whether it is required • Convergence proposal places restrictions on product use cases • Disallows certain use cases • Has the case been made whether such restrictions are mandatory? • This should be product and deployment decision

  4. The issue (cont)… 4 Convergence proposal pre-defines a mapping between Priorities and Traffic Classes • This violates the original idea behind ETS – Allow flexibility to the implementation • This also prevents an administrator from configuring a system as appropriate to their situation • Data Centers Bridging has discussed assumption of “single-administrative-domain” • Is proposed complexity to potentially reduce misconfiguration warranted? Sep XX, 2007

  5. Conclusion • We believe we should stick with the “Keep it Simple” approach of the original ETS goals • It also appears as though the proposal goes against the spirit of 802.1, allow the implementation, and deployment the flexibility to do what is needed their particular configuration

More Related