| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Albert, One suggestion for the proposals is to be careful to not over constrain or predetermine a solution in the PAR. For example, Statement 1, Alternative 1 reads okay as long as there is a definition for what DMLT is. That definition doesn’t need to be in the scope, but probably should be in the Need for the Project. In Statement 1, Alternative #2, the wording “to provide minimum latency for the transmission of” is not a bounded statement to help determine if the standards project has completed its work. It would imply that a minimum latency parameter needs to be defined before the project could start which may constrain how the standard is written or the viability of the project. Statements #2 and #3 are starting to presume how the standard needs to be written. Those aspects are typically captured in the Objectives. Your suggestions relative to Need for the Project are pretty good. The only caution would be that while end-to-end latency is important relative to the application space, 802.3 can only focus on point-to-point latency. This project needs to have the ability to control point-to-point latency to be able to control the overall end-to-end latency. Thanks, From: Tretter, Albert [mailto:albert.tretter@xxxxxxxxxxx] Dear Colleagues, attached you will find my proposals on the "scope" and the "need of the project" as an input for the upcoming SG meeting. Proposal for the "scope of the project" Statement 1: Alternative #1 The scope of this project is to specify additions to IEEE Std 802.3 to add support for Distinguished Minimum Latency Traffic in a converged traffic environment on Ethernet based LANs. Statement 1: Alternative #2 The scope of this project is to specify additions to IEEE Std 802.3 to provide minimum latency for the transmission of Distinguished Minimum Latency Traffic in a converged traffic environment on Ethernet based LANs. Statement 1: Alternative #3 The scope of this project is to specify additions to and appropriate modifications to IEEE Std 802.3 to provide minimum latency for the transmission of Distinguished Minimum Latency Traffic in a converged traffic environment on Ethernet based LANs. Statement 1: Alternative #4 The scope of this project is to specify additions to and appropriate modifications to IEEE Std 802.3 to provide minimum latency for the transmission of Distinguished Minimum Latency Traffic in a converged traffic environment on bridged LANs. Statement 1: Alternative #5 The scope of this project is to specify additions to and appropriate modifications to IEEE Std 802.3 to provide minimum latency for the transmission of Distinguished Minimum Latency Traffic in a converged traffic environment on IEEE Stds 802.1/802.3 based Local Area Networks. Additional At the next meeting we should discuss if we need a further statement like: Statement 2: Alternative #1 The necessary additions and modifications to IEEE Std 802.3 are specified while preserving the original MAC. Statement 2: Alternative #2 Adjustments to IEEE 802.3 Media Access Control (MAC) parameters, additions to the MAC client service interface and management attribute definitions are necessary. Statement 3: Alternative #2 Also, specify minimal adjustments to IEEE 802.3 Media Access Control (MAC) parameters, additions to the MAC client service interface and management attribute definitions. Proposals for the "Need for the Standard" Statement 1: Alternative #1 The opportunity to expand the overall Ethernet market, including but not limited to, automotive, industrial automation, transportation (aircraft, railway and heavy trucks) generates the need to support minimum latency for Distinguished Minimum Latency Traffic in a converged traffic environment on Ethernet based LANs. IEEE Std 802.3 currently does not support minimum latency for Distinguished Minimum Latency Traffic through its service layers. Minimum latency for Distinguished Minimum Latency Traffic in a converged traffic environment means the simultaneous support of real-time control traffic with a defined Quality of Service (Minimum Latency)and best-effort traffic on a single Ethernet network (converged network). Statement 1: Alternative #2 Adoption of Ethernet into new market areas, including but not limited to, automotive, industrial automation, transportation (aircraft, railway and heavy trucks) has generated a need for distinguished, reduced-latency, traffic in a converged traffic environment in bridges and end-stations with Ethernet. IEEE Std 802.3 currently does not have support for distinguished, reduced latency, traffic through its service layers. Distinguished, reduced-latency, traffic: Traffic with a defined Quality of Service (Minimum Latency) which is required to implement a real-time control network. Statement 1: Alternative #3 Adoption of Ethernet into new market areas, including but not limited to, automotive, industrial automation, transportation (aircraft, railway and heavy trucks) has generated a need for distinguished, reduced-latency, traffic in a converged traffic environment in bridges and end-stations with Ethernet. IEEE Std 802.3 currently does not have support for distinguished, reduced latency, traffic through its service layers. Distinguished, reduced-latency, traffic: Traffic which provides a defined, deterministic end-to-end latency (Mimum Latency) which is required to implement real-time control networks. Statement 1: Alternative #4 Adoption of Ethernet into new market areas, including but not limited to, automotive, industrial automation, transportation (aircraft, railway and heavy trucks) has generated the need to support the transmission of distinguished, real-time traffic with a deterministic and predictable network delay parallel to the transmission of best-effort traffic with maximum possible network utilization on a single Ethernet network (converged network). IEEE Std 802.3 currently does not have support for distinguished, reduced latency, traffic through its service layers. With best regards, Albert Tretter |