Ali,
AUI-S and AUI-L are not PMDs in SFF-8024. They are Host Electrical Interface IDs. At present, they are seen as two configurations of one implementation. Please see IEEE 802.3ck, where they are defined as such.
How do you see mapping “classes of AUIs” to Host Electrical Interface IDs?
Jeff
From: Ali Ghiasi <aghiasi@xxxxxxxxx>
Sent: Monday, September 26, 2022 10:15 AM
To: STDS-802-3-B400G@xxxxxxxxxxxxxxxxx
Subject: Re: [802.3_B400G] Oct 2022 Series Webpage Update
[External Email. Be cautious of content]
Hello Jeff,
AUI-S and AUI-L is are two settings for the same retime interface (4/5 taps FFE with RX CTLE+4DFE taps), assuming we will introduce some level of adaptive transmitter via CMIS-LT/CL136 you could have 1000’s of valid TX settings.
It is unfortunate that in SFF-8024 AUI-S/L are defined as if they were different PMDs, they are just two settings for one PMD!
AUI-I, II, III, and IV all are in my opinion within the scope of the 802.3df.
To unsubscribe from the STDS-802-3-B400G list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-B400G&A=1
I thought we already agreed to leverage IEEE 802.3ck. I was simply pointing out that we have for instance 100GAUI-1-S and 100GAUI-1-L from IEEE 802.3ck, which I understand we will similarly develop 800GAUI-8-S and 800GAUI-8-L.
Juniper Business Use Only
[External Email. Be cautious of content]
At this point for 200g lanes - no decisions have been made. Perhaps there is progress elsewhere but that does not apply within our project.
As always we are a contribution driven organization.
John
When we finish the first draft we will send it to you.
We already have AUI-S and AUI-L for two ranges essentially of loss, not just one. Regardless, we do have more kinds of implementations needing support from the standard.
Non-Juniper
[External Email. Be cautious of content]
Dear IEEE 802.3df Participants,
I trust everyone rushed to review next week's material as soon as John announced its availability, and discovered the excellent exposition by Mr. Lusted. For those with limited time and trying to decide which presentation to read, may I
kindly call your attention to:
As always, Kent is gently steering us towards wisdom, which for some of us who prefer the more direct approach, is a bit too old school.
What's clear is that a single large loss AUI C2M is no longer sufficient and we should write multiple specifications to adequately meet the need of mushrooming applications, specifically:
-
Traditional large loss for LR backplane, CR passive DAC, and VSR front pluggable
-
New XSR for NPO, twinax-over-PCB, active copper, and XSR front pluggable
Obviously the exact loss is TBD, however a good start for the XSR value are the shorter reach examples in last year's presentation by Sam and Nathan.
In off-line discussions, there has been a lot of interest in XSR's potential to save power, which we will direct into a proposal for the next meeting. For those that would like to join us in contributing or reviewing, please send me an
email so that we can put you on copy as we iterate a draft.
All,
The webpage for the Oct 2022 Series has been updated with all presentation material for next week - https://www.ieee802.org/3/df/public/22_10/index.html.
The proposed PAR modification to IEEE P802.3df and the proposed IEEE P02.3dj PAR have been uploaded.
I wish to highlight the proposed PAR modification to IEEE P802.3df- https://www.ieee802.org/3/df/public/22_10/22_0927/PAR_P802p3df_Proposed_220927.pdf.
As previously noted, I was working with Mr. Law on getting the PARs entered into the MyProject system. An issue has arisen that has not currently been resolved –
For the proposed PAR modification to P802.3df, the date for Item 4.2 could not be entered as presented to the Task
Force. The date proposed to the Task Force was Nov. 2023, however, the MyProject system will not permit entry of a date earlier than Jan 2024. Mr. Law has contacted IEEE SA Solutions Support regarding this issue. At this time the date of Jan 2024 has been
entered for Item 4.2 with the following noted entered for 8.1 –
Item 4.2: The earliest date that Myproject would allow to be entered is Jan 2024. This prevented the entry of the desired date of Nov 2023. (A bug report has been submitted to IEEE SA Solutions
Support. This item of the PAR will be updated to the desired date of Nov 2023 and this note deleted immediately upon a solution being provided.)
For the consideration of the Task Force - the motion to adopt this proposed PAR will be modified to allow modification
of the PAR in accordance with the note above.
Regards,
John D’Ambrosia
Chair, IEEE P802.3df Task Force
To unsubscribe from the STDS-802-3-B400G list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-B400G&A=1
To unsubscribe from the STDS-802-3-B400G list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-B400G&A=1
To unsubscribe from the STDS-802-3-B400G list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-B400G&A=1
To unsubscribe from the STDS-802-3-B400G list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-B400G&A=1
To unsubscribe from the STDS-802-3-B400G list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-B400G&A=1
To unsubscribe from the STDS-802-3-B400G list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-B400G&A=1
To unsubscribe from the STDS-802-3-B400G list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-B400G&A=1
|