Cart
0
Product
Products
(empty)
No products
To be determined
Shipping
$0.00
Total
Product successfully added to your shopping cart
Quantity
Total
There are 0 items in your cart.
There is 1 item in your cart.
Total products
Total shipping
To be determined
Total
Reduced price!
View larger
View larger
IEEE 1802.3
New product
IEEE 1802.3 2001 Edition, October 1, 2001 Conformance Test Methodology for IEEE Standards for Local and Metropolitan Area Networks - Specific Requirements - Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications
More info
Description / Abstract:
Foreword
This standard defies abstract methods for the conformance testing of 802.3 Clause 14 (10BASE-T MAU) implementations in order to satis6 conformance requirements arising from ISO/IEC 8802-31 [IEEE Std 802.3]. Such methods will form the basis for any subsequent development of executable test cases.
Scope
The conformance test suite is intended to detect incorrect implementations of Clause 14 (10BASE-T MAU) of the ISO/IEC 8802-3 standard [IEEE Std 802.3] with the exception of the options that have been added to Clause 14 since the publication of 1996 edition of ISO/IEC 8802-3 [IEEE Std 802.3]. The Clause 14 options excluded from this conformance test suite are support for Auto-Negotiation and full-duplex operation. The test suite should demonstrate conformance to Clause 14 of the ISO/IEC 8802-3 standard [IEEE Std 802.3]. However, the user should be made aware of Section 1.3, paragraph 2, of the IEEE Standards Manual, December 1990 edition (Conformance of Products or Systems to IEEE Standards):
IEEE Standards may contain testing procedures useful in determining whether products or systems are in compliance with the standards. Compliance in itself does not necessarily imply quality or guarantee proper use. Where IEEE Standards are used as the basis of examination andor testing of products or systems by laboratories or other agencies in the process of determining their suitability for their intended use and safe operation, the IEEE assumes no responsibility for the use or interpretation of its standards or the adequacy of the testing or certification.
The test setups and procedure described in this standard are designed to provide the implementor with a methodology for obtaining repeatable results by which conformance can be judged. However, these methodologies are by no means unique. This standard does not preclude the use of alternative methodologies provided that an equivalence between the prescribed methodology and the alternative methodology can be demonstrated.
It is acknowledged that conformance testing may need to be augmented by other testing (i.e., interoperability or development testing). Such testing is beyond the scope of this standard. It is possible, on the other hand, that an implementation may be interoperable with other implementations but not satisfy conformance testing.
Finally the reader should note that no environmental specifications appear in the test suite. A prudent vendor should ensure that the implementation operates as intended throughout the vendor s specified environmental range before claiming conformance.
This standard defies abstract methods for the conformance testing of 802.3 Clause 14 (10BASE-T MAU) implementations in order to satis6 conformance requirements arising from ISO/IEC 8802-31 [IEEE Std 802.3]. Such methods will form the basis for any subsequent development of executable test cases.
Scope
The conformance test suite is intended to detect incorrect implementations of Clause 14 (10BASE-T MAU) of the ISO/IEC 8802-3 standard [IEEE Std 802.3] with the exception of the options that have been added to Clause 14 since the publication of 1996 edition of ISO/IEC 8802-3 [IEEE Std 802.3]. The Clause 14 options excluded from this conformance test suite are support for Auto-Negotiation and full-duplex operation. The test suite should demonstrate conformance to Clause 14 of the ISO/IEC 8802-3 standard [IEEE Std 802.3]. However, the user should be made aware of Section 1.3, paragraph 2, of the IEEE Standards Manual, December 1990 edition (Conformance of Products or Systems to IEEE Standards):
IEEE Standards may contain testing procedures useful in determining whether products or systems are in compliance with the standards. Compliance in itself does not necessarily imply quality or guarantee proper use. Where IEEE Standards are used as the basis of examination andor testing of products or systems by laboratories or other agencies in the process of determining their suitability for their intended use and safe operation, the IEEE assumes no responsibility for the use or interpretation of its standards or the adequacy of the testing or certification.
The test setups and procedure described in this standard are designed to provide the implementor with a methodology for obtaining repeatable results by which conformance can be judged. However, these methodologies are by no means unique. This standard does not preclude the use of alternative methodologies provided that an equivalence between the prescribed methodology and the alternative methodology can be demonstrated.
It is acknowledged that conformance testing may need to be augmented by other testing (i.e., interoperability or development testing). Such testing is beyond the scope of this standard. It is possible, on the other hand, that an implementation may be interoperable with other implementations but not satisfy conformance testing.
Finally the reader should note that no environmental specifications appear in the test suite. A prudent vendor should ensure that the implementation operates as intended throughout the vendor s specified environmental range before claiming conformance.