Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
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>  Marek, Your plan sounds reasonable to me. Curtis   From: Marek Hajduczenia <mxhaj79@xxxxxxxxx>  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:
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 |
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature