|
Question : RFC Compliance Checklist
|
|
Hi All, I'm trying to test a device and ensure that it's Compliant to RFC 2878 (BCP). At the minute all I have is the RFC which is proving difficult to actually try and extract requirements which will ensure compliance, or not as the case may be. Does anyone know if a checklist that is available for the RFC, or some general variation of a PICS Proforma for the RFC's?
All info greatly appreciated. Thanks Scott
|
Answer : RFC Compliance Checklist
|
|
I've done some compliance testing on ATM switches (UNI 3.1) and we had to write our own test cases and there's no way I'd publish them without some sort of royalty. But I could be wrong. Call Cisco, ask them.
I looked at the RFC briefly and found a couple of things like . . . Separation of Spanning Tree Domains - If a switch A isn't configure to support Spanning Tree but switch B sends it a config packet, a compliant switch, in this case switch A, needs to respond, not just ignore the config packet. So you write a test cast to trace this condition between two switches and if your device responds to a config packet then it's compliant with respect to section 4.1.4 of RFC 2878.
Section 4.1 said that before bridged LAN Traffic or BPDUs may be communicated, PPP MUST reach the Network-Layer protocol phase, and the Bridging Control Protocol MUST reach the Opened state. You should be able to put your device into debug mode when it's negotiating a PPP link to verify that this happens.
You might start by searching for the word "MUST" in the body of the RFC and writing test cases to prove all "MUST" conditions. That's essentially a compliance test. Anyway, good luck.
Steve
|
|
|
|