Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
The first option, i.e., update both MAU and PHY attributes to match whatever combination of devices we plan to support. I am still checking to see why we would even care about MAU to begin with (I have conflicting statements being made for now)
Marek
Hi Marek,
Not exactly clear what you are proposing. Is it to update both aMauType and aPhyType tables to bring in all the latest MAU and PHY types? Or is it something else?
Glen
From: Curtis Knittle <C.Knittle@xxxxxxxxxxxxx>
Sent: Thursday, December 15, 2022 3:54 PM
To: STDS-1904-4-TF@xxxxxxxxxxxxxxxxx
Subject: Re: [1904.4 TF] 1904.4 Open action items
Marek,
Your plan sounds reasonable to me.
Curtis
From: Marek Hajduczenia <mxhaj79@xxxxxxxxx>
Sent: Thursday, December 15, 2022 2:39 PM
To: Curtis Knittle <C.Knittle@xxxxxxxxxxxxx>; stds-1904-4-tf@xxxxxxxxxxxxxxxxx
Subject: Re: 1904.4 Open action items
Good morning, colleagues,
On item #45, which I took upon myself as Ryan's substitute, I have been looking at the way aPHY and aMAU are used in IEEE Std 802.3 and I cannot find any clear reason why we would need to even care about MAU value apart from some of legacy management attributes. Neither the MAU nor the AUI interfaces exist (apart, perhaps as notional entities for the purposes of thinking about layering the interface) in our modern PHYs and everything following Fast Ethernet is built around the MAC and PHY separation, with xMII in the middle. I think it might be one of these cases of having to just do it because of legacy reasons, closing the eyes and moving on
if we have consensus on just getting this done, i am happy to update the relevant table(s) via a comment on D1.2
Marek
On 12/14/22 09:07, Curtis Knittle wrote:
Colleagues,
Below you will find the current list of assigned and open action items.
Curtis
Curtis Knittle
VP Wired Technologies – R&D
CableLabs
desk: +1-303-661-3851
mobile: +1-303-589-6869
Stay up to date with CableLabs: Read the blog and follow us on Twitter
#whosaysicant
To unsubscribe from the STDS-1904-4-TF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-1904-4-TF&A=1
To unsubscribe from the STDS-1904-4-TF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-1904-4-TF&A=1
To unsubscribe from the STDS-1904-4-TF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-1904-4-TF&A=1
To unsubscribe from the STDS-1904-4-TF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-1904-4-TF&A=1