I need to design an interface that will run at 1Gbps that someone else will be designing and testing.

If I specify that this interface as requiring to adhere to the 100Base-T standard, is that sufficient?

In other words, do I need to specify line rate vs data rate or what protocol to use or is that already assumed in the standard.
My thinking is that if the vendor complies with the standard, they would have to account for the different protocols that you can run etc.

Thanks!

 

I need to design an interface that will run at 1Gbps that someone else will be designing and testing.

If I specify that this interface as requiring to adhere to the 100Base-T standard, is that sufficient?

In other words, do I need to specify line rate vs data rate or what protocol to use or is that already assumed in the standard.
My thinking is that if the vendor complies with the standard, they would have to account for the different protocols that you can run etc.

Thanks!

That should be enough to provide anyone with the requirements at layer 1 and 2.

 

Did you mean to say 1000Base-T - ?

ak

 

Did you mean to say 1000Base-T - ?

ak

Yes sorry

 

Just to clarify, 100Base-T is 100 Mbps, not 1 Gbps , for a 1 Gbps copper interface, you’d want to specify compliance with 1000BASE-T under IEEE 802.3. If you state 1000BASE-T per IEEE 802.3, that already defines the 1 Gbps line rate, signaling, auto-negotiation, duplex mode, and cabling requirements at the physical layer, so you don’t need to separately specify line vs. data rate. However, keep in mind this only covers the PHY. If your design depends on specific higher-layer protocols, latency limits, VLANs, jumbo frames, or other performance requirements, those should be explicitly called out.

 

Just to clarify, 100Base-T is 100 Mbps, not 1 Gbps , for a 1 Gbps copper interface, you’d want to specify compliance with 1000BASE-T

See post #4

ak