idnits 2.17.1 draft-ietf-bmwg-atm-method-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 127 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 1993 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** There are 2773 instances of too long lines in the document, the longest one being 3 characters in excess of 72. == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 120: '... the MUST requirements for the...' RFC 2119 keyword, line 121: '...sfies all the MUST and all the ...' RFC 2119 keyword, line 123: '...atisfies all the MUST requirements but...' RFC 2119 keyword, line 124: '... SHOULD requirements for its protoc...' RFC 2119 keyword, line 191: '... The SUT MUST be configured as ...' (1235 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 11 has weird spacing: '... This docum...' == Line 12 has weird spacing: '...visions of S...' == Line 13 has weird spacing: '...cuments of th...' == Line 14 has weird spacing: '...tribute worki...' == Line 18 has weird spacing: '...eted by other...' == (1988 more instances...) == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with one VCC. The VCC SHOULD contain one VPI/VCI. The VCC MUST be configured as either a CBR or VBR connection. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 12 VCIs. The VCC's MUST be configured as a UBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with one VCC. The VCC SHOULD contain one VPI/VCI. The VCC MUST be configured as a UBR connection. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. Each VCC MUST be defined as one of the Bearer classes for a total of (max VCC/3) CBR, (max VCC/3) UBR and (max VCC/3) VBR VCC's. If the maximum number of VCC's is not divisible by 3, the total for each bearer class MUST be within 3 VCC's of each other. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 12 VCIs. The VCC's MUST be configured as either a CBR, VBR, or UBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with three VCC's. Each VCC MUST be defined as a different Bearer class: one CBR, one UBR and one VBR. Each VCC SHOULD contain one VPI/VCI. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with twelve VCC's. Each VCC MUST be defined as one of the Bearer classes for a total of four CBR, four UBR and four VBR VCC's. Each VCC SHOULD contain one VPI/VCI. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with the maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The VCC's MUST be configured as either a CBR, VBR, or UBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: It is useful to characterize the SUTs performance under a number of conditions. Some of these conditions are noted below. The reported results SHOULD include as many of these conditions as the test equipment is able to generate. The suite of tests SHOULD be run first without any modifying conditions, then repeated under each of the modifying conditions separately. To preserve the ability to compare the results of these tests, any IP PDUs that are required to generate the modifying conditions (excluding management queries) will be included in the same data stream as that of the normal test IP PDUs and in place of one of the test IP PDUs. They MUST not be supplied to the SUT on a separate network port. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: The 24 ATM addresses SHOULD not be any that are represented in the test data stream. The last filter SHOULD permit the forwarding of the test data stream. By "first" and "last" we mean to ensure that in the second case, 25 conditions must be checked before the data IP PDUs will match the conditions that permit the forwarding of the IP PDU. Of course, if the SUT reorders the filters or does not use a linear scan of the filter rules the effect of the sequence in which the filters are input is properly lost. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 12 VCIs. The VCC's MUST be configured as either a CBR, VBR, or UBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with one VCC. The VCC SHOULD contain one VPI/VCI. The VCC MUST be configured as either a CBR or VBR connection. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with one VCC. The VCC SHOULD contain one VPI/VCI. The VCC MUST be configured as a UBR connection. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with the maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The VCC MUST be configured as a UBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with twelve VCC's. Each VCC MUST be defined as one of the Bearer classes for a total of four CBR, four UBR and four VBR VCC's. Each VCC SHOULD contain one VPI/VCI. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. Each VCC MUST be defined as one of the Bearer classes for a total of (max VCC/3) CBR, (max VCC/3) UBR and (max VCC/3) VBR VCC's. If the maximum number of VCC's is not divisible by 3, the total for each bearer class MUST be within 3 VCC's of each other. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 12 VCIs. The VCC's MUST be configured as either a CBR, VBR, or UBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with one VCC. The VCC SHOULD contain one VPI/VCI. The VCC MUST be configured as either a CBR or VBR connection. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 12 VCIs. The VCC's MUST be configured as either a CBR or VBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with one VCC. The VCC SHOULD contain one VPI/VCI. The VCC MUST be configured as a UBR connection. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with the maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The VCC's MUST be configured as a UBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. Each VCC MUST be defined as one of the Bearer classes for a total of (max VCC/3) CBR, (max VCC/3) UBR and (max VCC/3) VBR VCC's. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 12 VCIs. The VCC's MUST be configured as either a CBR, VBR, or UBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with one VCC. The VCC SHOULD contain one VPI/VCI. The VCC MUST be configured as either a CBR or VBR connection. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with the maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The VCC MUST be configured as either a CBR or VBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with one VCC. The VCC SHOULD contain one VPI/VCI. The VCC MUST be configured as a UBR connection. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 12 VCIs. The VCC MUST be configured as a UBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with the maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The VCC MUST be configured as a UBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with three VCC's. Each VCC MUST be defined as a different Bearer class; one CBR, one UBR and one VBR. Each VCC SHOULD contain one VPI/VCI. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. Each VCC MUST be defined as one of the Bearer classes for a total of (max VCC/3) CBR, (max VCC/3) UBR and (max VCC/3) VBR VCC's. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with one VCC. The VCC MUST be configured as either a CBR, VBR, or UBR connection. The VCC SHOULD contain one VPI/VCI. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 12 VCIs. The VCC's MUST be configured as either a CBR, VBR, or UBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with one VCC. The VCC SHOULD contain one VPI/VCI. The VCC MUST be configured as either a CBR or VBR connection. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with the maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The VCC's MUST be configured as either a CBR or VBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with one VCC. The VCC SHOULD contain one VPI/VCI. The VCC MUST be configured as a UBR connection. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 12 VCIs. The VCC's MUST be configured as a UBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with three VCC's. Each VCC MUST be defined as a different Bearer class; one CBR, one UBR and one VBR. Each VCC SHOULD contain one VPI/VCI. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. Each VCC MUST be defined as one of the Bearer classes for a total of (max VCC/3) CBR, (max VCC/3) UBR and (max VCC/3) VBR VCC's. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 12 VCIs. The VCC's MUST be configured as either a CBR, VBR, or UBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with one VCC. The VCC SHOULD contain one VPI/VCI. The VCC MUST be configured as either a CBR or VBR connection. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with the maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The VCC MUST be configured as either a CBR or VBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with one VCC. The VCC SHOULD contain one VPI/VCI. The VCC MUST be configured as a UBR connection. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 12 VCIs. The VCC MUST be configured as a UBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with the maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The VCC MUST be configured as a UBR connection. The VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with three VCC's. Each VCC MUST be defined as a different Bearer class; one CBR, one UBR and one VBR. Each VCC SHOULD contain one VPI/VCI. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of the specified traffic descriptors. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 2) Configure the SUT and test device with maximum number of VCCs supported on the SUT. For example, if the maximum number of VCCs supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. Each VCC MUST be defined as one of the Bearer classes for a total of (max VCC/3) CBR, (max VCC/3) UBR and (max VCC/3) VBR VCC's. The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '0' on line 5205 -- Looks like a reference, but probably isn't: '5' on line 5205 -- Looks like a reference, but probably isn't: '16' on line 5205 == Unused Reference: 'IETF-RFC-2544' is defined on line 5308, but no explicit reference was found in the text == Unused Reference: 'IETF-RFC-2225' is defined on line 5311, but no explicit reference was found in the text == Unused Reference: 'IETF-RFC-2761' is defined on line 5314, but no explicit reference was found in the text == Unused Reference: 'AF-TEST-0022' is defined on line 5320, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 2544 ** Downref: Normative reference to an Informational RFC: RFC 2761 -- Possible downref: Non-RFC (?) normative reference: ref. 'AF-TEST-0022' Summary: 10 errors (**), 0 flaws (~~), 60 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group J. H. Dunn 2 INTERNET-DRAFT C. E. Martin 3 Expires: September, 2000 ANC, Inc. 5 March, 2000 6 Methodology for ATM Benchmarking 7 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance with all 12 provisions of Section 10 of RFC2026. Internet-Drafts are working 13 documents of the Internet Engineering Task Force (IETF), its areas, and 14 its working groups. Note that other groups may also distribute working 15 documents as Internet-Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet-Drafts as reference material 20 or to cite them other than as "work in progress." 22 The list of current Internet-Drafts can be accessed at 23 http://www.ietf.org/ietf/1id-abstracts.txt 25 The list of Internet-Draft Shadow Directories can be accessed at 26 http://www.ietf.org/shadow.html. 28 Copyright Notice 30 Copyright (C) The Internet Society (1999). All Rights Reserved. 32 Abstract 34 This document discusses and defines a number of tests that may be used 35 to describe the performance characteristics of ATM based switching 36 devices. In addition to defining the tests this document also describes 37 specific formats for reporting the results of the tests. 39 Appendix A lists the tests and conditions that we believe should be 40 included for specific cases and gives additional information about 41 testing practices. 43 This memo is a product of the Benchmarking Methodology Working Group 44 (BMWG) of the Internet Engineering Task Force (IETF). 46 1. Introduction. 48 This document defines a specific set of tests that vendors can use to 49 measure and report the performance characteristics of ATM network 50 devices. The results of these tests will provide the user comparable 51 data from different vendors with which to evaluate these devices. The 52 methods defined in this memo are based on RFC 2544 "Benchmarking 53 Methodology for Network Interconnect Devices". 55 The document "Terminology for ATM Benchmarking" (RFC 2761), defines many 56 of the terms that are used in this document. The terminology document 57 should be consulted before attempting to make use of this document. 59 The BMWG produces two major classes of documents: Benchmarking 60 Terminology documents and Benchmarking Methodology documents. The 61 Terminology documents present the benchmarks and other related terms. 62 The Methodology documents define the procedures required to collect the 63 benchmarks cited in the corresponding Terminology documents. 65 2. Background 67 2.1. Test Device Requirements 69 This document is based on the requirement that a test device is 70 available. The test device can either be off the shelf or can be easily 71 built with current technologies. The test device must have a 72 transmitting and receiving port for the interface type under test. The 73 test device must be configured to transmit test PDUs and to analyze 74 received PDUs. The test device should be able to transmit and analyze 75 received data at the same time. 77 2.2. Systems Under Test (SUTs) 79 There are a number of tests described in this document that do not apply 80 to each SUT. Vendors should perform all of the tests that can be 81 supported by a specific product type. It will take some time to perform 82 all of the recommended tests under all of the recommended conditions. 83 Appendix A lists some of the tests and conditions that we believe should 84 be included for specific cases. 86 2.3. Test Result Evaluation 88 Performing all of the tests in this document will result in a great deal 89 of data. The applicability of this data to the evaluation of a 90 particular SUT will depend on its expected use and the configuration of 91 the network in which it will be used. For example, the time required by 92 a switch to provide ILMI services will not be a pertinent measurement in 93 a network that does not use the ILMI protocol, such as an ATM WAN. 94 Evaluating data relevant to a particular network installation may 95 require considerable experience, which may not be readily available. 96 Finally, test selection and evaluation of test results must be done with 97 an understanding of generally accepted testing practices regarding 98 repeatability, variance and the statistical significance of a small 99 numbers of trials. 101 2.4. Requirements 103 In this document, the words that are used to define the significance of 104 each particular requirement are capitalized. These words are: 106 * "MUST" This word, or the words "REQUIRED" and "SHALL" mean that the 107 item is an absolute requirement of the specification. 109 * "SHOULD" This word or the adjective "RECOMMENDED" means that there may 110 exist valid reasons in particular circumstances to ignore this item, but 111 the full implications should be understood and the case carefully 112 weighed before choosing a different course. 114 * "MAY" This word or the adjective "OPTIONAL" means that this item is 115 truly optional. One vendor may choose to include the item because a 116 particular marketplace requires it or because it enhances the product, 117 for example; another vendor may omit the same item. 119 An implementation is not compliant if it fails to satisfy one or more of 120 the MUST requirements for the protocols it implements. An 121 implementation that satisfies all the MUST and all the SHOULD 122 requirements for its protocols is said to be "unconditionally 123 compliant"; one that satisfies all the MUST requirements but not all the 124 SHOULD requirements for its protocols is said to be "conditionally 125 compliant". 127 2.5. Test Configurations for SONET 128 The test device can be connected to the SUT in a variety of 129 configurations depending on the test point. The following 130 configurations will be used for the tests described in this document. 132 1) Uni-directional connection: The test devices transmit port (labeled 133 Tx) is connected to the SUT receive port (labeled Rx). The SUTs 134 transmit port is connected to the test device receive port (see Figure 135 1). In this configuration, the test device can verify that all 136 transmitted packets are acknowledged correctly. Note that this 137 configuration does not verify internal system functions, but verifies 138 one port on the SUT. 140 +-------------+ +-------------+ 141 | Tx|-------------->|Rx | 142 | Test Rx|<--------------|Tx SUT | 143 | Device | | | 144 +-------------+ +-------------+ 146 Figure 1 148 2) Bi-directional connection: The test devices first transmit port is 149 connected to the SUTs first receive port. The SUTs first transmit port 150 is connected to the test devices first receive port. The test devices 151 second transmit port is connected to the SUTs second receive port. The 152 SUTs second transmit port is connected to the test devices second 153 receive port (see Figure 2). In this configuration, the test device can 154 determine if all of the transmitted packets were received and forwarded 155 correctly. Note that this configuration does verify internal system 156 functions, since it verifies two ports on the SUT. 158 +-------------+ +-------------+ 159 | Test Tx|-------------->|Rx | 160 | Device Rx|<--------------|Tx SUT | 161 | Tx Rx | | Tx Rx | 162 +-------------+ +-------------+ 163 | ^ | ^ 164 | | | | 165 | +------------------------+ | 166 | | 167 |---------------------------------| 169 Figure 2 171 2) Uni-directional passthrough connection: The test devices first 172 transmit port is connected to the SUT1 receive port. The SUT1 transmit 173 port is connected to the test devices first receive port. The test 174 devices second transmit port is connected to the SUT2 receive port. The 175 SUT2 transmit port is connected to the test devices second receive port 176 (see Figure 3). In this configuration, the test device can determine if 177 all of the packets transmitted by SUT1 were correctly acknowledged by 178 SUT2. Note that this configuration does not verify internal system 179 functions, but verifies one port on each SUT. 181 +-------------+ +-------------+ +-------------+ 182 | Tx|---------->|Rx Tx|---------->|Rx | 183 | SUT1 Rx|<----------|Tx Test Rx|<----------|Tx SUT2 | 184 | | | Device | | | 185 +-------------+ +-------------+ +-------------+ 187 Figure 3 189 2.5. SUT Configuration 191 The SUT MUST be configured as described in the SUT users guide. 192 Specifically, it is expected that all of the supported protocols will be 193 configured and enabled (See Appendix A). It is expected that all of the 194 tests will be run without changing the configuration or setup of the SUT 195 in any way other than that required to do the specific test. For 196 example, it is not acceptable to disable all but one transport protocol 197 when testing the throughput of that protocol. If PNNI or BISUP is used 198 to initiate switched virtual connections (SVCs), the SUT configuration 199 SHOULD include the normally recommended routing update intervals and 200 keep alive frequency. The specific version of the software and the 201 exact SUT configuration, including what functions are disabled and used 202 during the tests MUST be included as part of the report of the results. 204 2.6. Frame formats 206 The formats of the test IP PDUs to use for TCP/IP over ATM are shown in 207 Appendix C: Test Frame Formats. Note that these IP PDUs are in 208 accordance with RFC 2225. These exact IP PDU formats SHOULD be used in 209 the tests described in this document for this protocol/media 210 combination. These IP PDUs will be used as a template for testing other 211 protocol/media combinations. The specific formats that are used to 212 define the test IP PDUs for a particular test series MUST be included in 213 the report of the results. 215 2.7. Frame sizes 217 All of the described tests SHOULD be performed using a number of IP PDU 218 sizes. Specifically, the sizes SHOULD include the maximum and minimum 219 legitimate sizes for the protocol under test on the media under test and 220 enough sizes in between to be able to get a full characterization of the 221 SUT performance. Except where noted, at least five IP PDU sizes SHOULD 222 be tested for each test condition. 224 Theoretically the minimum size UDP Echo request IP PDU would consist of 225 an IP header (minimum length 20 octets), a UDP header (8 octets), AAL5 226 trailer (8 octets) and an LLC/SNAP code point header(8 octets); 227 therefore, the minimum size PDU will fit into one ATM cell. The 228 theoretical maximum IP PDU size is determined by the size of the length 229 field in the IP header. In almost all cases the actual maximum and 230 minimum sizes are determined by the limitations of the media. In the 231 case of ATM, the maximum IP PDU size SHOULD be the ATM MTU size, which 232 is 9180 octets. 234 In theory it would be ideal to distribute the IP PDU sizes in a way that 235 would evenly distribute the theoretical IP PDU rates. These 236 recommendations incorporate this theory but specify IP PDU sizes, which 237 are easy to understand and remember. In addition, many of the same IP 238 PDU sizes are specified on each of the media types to allow for easy 239 performance comparisons. 241 Note: The inclusion of an unrealistically small IP PDU size on some of 242 the media types (i.e. with little or no space for data) is to help 243 characterize the per-IP PDU processing overhead of the SUT. 245 The IP PDU sizes that will be used are: 247 44, 64, 128, 256, 1024, 1518, 2048, 4472, 9180 249 The minimum size IP PDU for UDP on ATM is 44 octets, the minimum size of 250 44 is recommended to allow direct comparison to token ring performance. 251 The IP PDU size of 4472 is recommended instead of the theoretical FDDI 252 maximum size of 4500 octets in order to permit the same type of 253 comparison. An IP (i.e. not UDP) IP PDU may be used in addition if a 254 higher data rate is desired, in which case the minimum IP PDU size is 28 255 octets. 257 2.8. Verifying received IP PDUs 259 The test equipment SHOULD discard any IP PDUs received during a test run 260 that are not actual forwarded test IP PDUs. For example, keep-alive and 261 routing update IP PDUs SHOULD NOT be included in the count of received 262 IP PDUs. In any case, the test equipment SHOULD verify the length of 263 the received IP PDUs and check that they match the expected length. 265 Preferably, the test equipment SHOULD include sequence numbers in the 266 transmitted IP PDUs and check for these numbers on the received IP PDUs. 267 If this is done, the reported results SHOULD include. in addition to the 268 number of IP PDUs dropped, the number of IP PDUs that were received out 269 of order, the number of duplicate IP PDUs received and the number of 270 gaps in the received IP PDU numbering sequence. This functionality is 271 required for some of the described tests. 273 2.9. Modifiers 275 It is useful to characterize the SUTs performance under a number of 276 conditions. Some of these conditions are noted below. The reported 277 results SHOULD include as many of these conditions as the test equipment 278 is able to generate. The suite of tests SHOULD be run first without any 279 modifying conditions, then repeated under each of the modifying 280 conditions separately. To preserve the ability to compare the results 281 of these tests, any IP PDUs that are required to generate the modifying 282 conditions (excluding management queries) will be included in the same 283 data stream as that of the normal test IP PDUs and in place of one of 284 the test IP PDUs. They MUST not be supplied to the SUT on a separate 285 network port. 287 2.9.1. Management IP PDUs 289 Most ATM data networks now make use of ILMI, signaling and OAM. In many 290 environments, there can be a number of management stations sending 291 queries to the same SUT at the same time. 293 Management queries MUST be made in accordance with the applicable 294 specification, e.g., ILMI sysUpTime getNext requests will be made in 295 accordance with ILMI 4.0. The response to the query MUST be verified by 296 the test equipment. Note that, for each management protocol in use, this 297 requires that the test equipment implement the associated protocol state 298 machine. One example of the specific query IP PDU that should be used 299 is shown in Appendix B. 301 2.9.2. Routing update IP PDUs 303 The processing of PNNI updates could have a significant impact on the 304 ability of a switch to forward cells and complete calls. If PNNI is 305 configured on the SUT, one routing update MUST be transmitted before the 306 first test IP PDU is transmitted during the trial. The test SHOULD 307 verify that the SUT has properly processed the routing update. 309 PNNI routing update IP PDUs SHOULD be sent at the rate specified in 310 Appendix B. Appendix C defines two routing update PDUs for the TCP/IP 311 over ATM example. The routing updates are designed to change the 312 routing on a number of networks that are not involved in the forwarding 313 of the test data. The first IP PDU sets the routing table state to "A", 314 the second one changes the state to "B". The IP PDUs MUST be alternated 315 during the trial. The test SHOULD verify that the SUT has properly 316 processed the routing update. 318 2.10. Filters 320 Filters are added to switches to selectively inhibit the forwarding of 321 cells that would normally be forwarded. This is usually done to 322 implement security controls on the data that is accepted between one 323 area and another. Different products have different capabilities to 324 implement filters. 326 The SUT SHOULD be first configured to add one filter condition and the 327 tests performed. This filter SHOULD permit the forwarding of the test 328 data stream. This filter SHOULD be of the form: 330 To be determined. 332 The SUT SHOULD be then reconfigured to implement a total of 25 filters. 333 The first 24 of these filters SHOULD be of the form: 335 To be determined. 337 The 24 ATM addresses SHOULD not be any that are represented in the test 338 data stream. The last filter SHOULD permit the forwarding of the test 339 data stream. By "first" and "last" we mean to ensure that in the second 340 case, 25 conditions must be checked before the data IP PDUs will match 341 the conditions that permit the forwarding of the IP PDU. Of course, if 342 the SUT reorders the filters or does not use a linear scan of the filter 343 rules the effect of the sequence in which the filters are input is 344 properly lost. 346 The exact filters configuration command lines used SHOULD be included 347 with the report of the results. 349 2.10.1. Filter Addresses 351 Two sets of filter addresses are required, one for the single filter 352 case and one for the 25 filter case. 354 The single filter case should permit traffic from ATM address [Switch 355 Network Prefix] 00 00 00 00 00 01 00 to ATM address [Switch Network 356 Prefix] 00 00 00 00 00 02 00 and deny all other traffic. Note that the 357 13 octet Switch Network Prefix MUST be configured before this test can 358 be run. 360 The 25 filter case should follow the following sequence. 362 deny [Switch Network Prefix] 00 00 00 00 00 01 00 363 to [Switch Network Prefix] 00 00 00 00 00 03 00 364 deny [Switch Network Prefix] 00 00 00 00 00 01 00 365 to [Switch Network Prefix] 00 00 00 00 00 04 00 366 deny [Switch Network Prefix] 00 00 00 00 00 01 00 367 to [Switch Network Prefix] 00 00 00 00 00 05 00 368 ... 369 deny [Switch Network Prefix] 00 00 00 00 00 01 00 370 to [Switch Network Prefix] 00 00 00 00 00 0C 00 371 deny [Switch Network Prefix] 00 00 00 00 00 01 00 372 to [Switch Network Prefix] 00 00 00 00 00 0D 00 373 allow [Switch Network Prefix] 00 00 00 00 00 01 00 374 to [Switch Network Prefix] 00 00 00 00 00 02 00 375 deny [Switch Network Prefix] 00 00 00 00 00 01 00 376 to [Switch Network Prefix] 00 00 00 00 00 0E 00 378 deny [Switch Network Prefix] 00 00 00 00 00 01 00 379 to [Switch Network Prefix] 00 00 00 00 00 0F 00 380 ... 381 deny [Switch Network Prefix] 00 00 00 00 00 01 00 382 to [Switch Network Prefix] 00 00 00 00 00 18 00 383 deny all else 385 All previous filter conditions should be cleared from the switch before 386 this sequence is entered. The sequence is selected to test to see if 387 the switch sorts the filter conditions or accepts them in the order that 388 they were entered. Both of these procedures will result in a greater 389 impact on performance than will some form of hash coding. 391 2.11. Protocol addresses 393 It is easier to implement these tests using a single logical stream of 394 data, with one source ATM address and one destination ATM address, and 395 for some conditions like the filters described above, a practical 396 requirement. Networks in the real world are not limited to single 397 streams of data. The test suite SHOULD be first run with a single ATM 398 source and destination address pair. The tests SHOULD then be repeated 399 with using a random destination address. In the case of testing single 400 switches, the addresses SHOULD be random and uniformly distributed over 401 a range of 256 seven octet user parts. In the case of testing multiple 402 interconnected switches, the addresses SHOULD be random and uniformly 403 distributed over the 256 network prefixes, each of which should support 404 256 seven octet user parts. The specific address ranges to use for ATM 405 are shown in Appendix B. IP to ATM address mapping MUST be accomplished 406 as described in RFC 2225. 408 2.12. Route Set Up 410 It is not reasonable that all of the routing information necessary to 411 forward the test stream, especially in the multiple address case, will 412 be manually set up. If PNNI and/or ILMI are running, at the start of 413 each trial a routing update MUST be sent to the SUT. This routing update 414 MUST include all of the ATM addresses that will be required for the 415 trial. This routing update will have to be repeated at the interval 416 required by PNNI or ILMI. An example of the format and repetition 417 interval of the update IP PDUs is given in Appendix B. 419 2.13. Bidirectional traffic 420 Bidirectional performance tests SHOULD be run with the same data rate 421 being offered from each direction. The sum of the data rates should not 422 exceed the theoretical limit for the media. 424 2.14. Single stream path 426 The full suite of tests SHOULD be run with the appropriate modifiers for 427 a single receive and transmit port on the SUT. If the internal design of 428 the SUT has multiple distinct pathways, for example, multiple interface 429 cards each with multiple network ports, then all possible permutations 430 of pathways SHOULD be tested separately. If multiple interconnected 431 switches are tested, the test MUST specify routes, which allow only one 432 path between source and destination ATM addresses. 434 2.15. Multi-port 436 Many switch products provide several network ports on the same interface 437 module. Each port on an interface module SHOULD be stimulated in an 438 identical manner. Specifically, half of the ports on each module SHOULD 439 be receive ports and half SHOULD be transmit ports. For example if a 440 SUT has two interface module each of which has four ports, two ports on 441 each interface module be receive ports and two will be transmit ports. 442 Each receive port MUST be offered the same data rate. The addresses in 443 the input data streams SHOULD be set so that an IP PDU will be directed 444 to each of the transmit ports in sequence. That is, all transmit ports 445 will receive an identical distribution of IP PDUs from a particular 446 receive port. 448 Consider the following 6 port SUT: 450 -------------- 451 ---------| Rx A Tx X|-------- 452 ---------| Rx B Tx Y|-------- 453 ---------| Rx C Tx Z|-------- 454 -------------- 456 The addressing of the data streams for each of the inputs SHOULD be: 458 stream sent to Rx A: 459 IP PDU to Tx X, IP PDU to Tx Y, IP PDU to Tx Z 460 stream sent to Rx B: 462 IP PDU to Tx X, IP PDU to Tx Y, IP PDU to Tx Z 463 stream sent to Rx C 464 IP PDU to Tx X, IP PDU to Tx Y, IP PDU to Tx Z 466 Note: Each stream contains the same sequence of IP destination 467 addresses; therefore, each transmit port will receive 3 IP PDUs 468 simultaneously. This procedure ensures that the SUT will have to process 469 multiple IP PDUs addressed to the same transmit port simultaneously. 471 The same configuration MAY be used to perform a bi-directional multi- 472 stream test. In this case all of the ports are considered both receive 473 and transmit ports. Each data stream MUST consist of IP PDUs whose 474 addresses correspond to the ATM addresses all of the other ports. 476 2.16. Multiple protocols 478 This document does not address the issue of testing the effects of a 479 mixed protocol environment other than to suggest that if such tests are 480 wanted then PDUs SHOULD be distributed between all of the test 481 protocols. The distribution MAY approximate the conditions on the 482 network in which the SUT would be used. 484 2.17. Multiple IP PDU sizes 486 This document does not address the issue of testing the effects of a 487 mixed IP PDU size environment other than to suggest that, if such tests 488 are required, then IP PDU size SHOULD be evenly distributed among all of 489 the PDU sizes listed in this document. The distribution MAY approximate 490 the conditions on the network in which the SUT would be used. 492 2.18. Testing beyond a single SUT 494 In the performance testing of a single SUT, the paradigm can be 495 described as applying some input to a SUT and monitoring the output. The 496 results of which can be used to form a basis of characterization of that 497 device under those test conditions. 499 This model is useful when the test input and output are homogenous 500 (e.g., 64-byte IP, AAL5 PDUs into the SUT; 64 byte IP, AAL5 PDUs out). 502 By extending the single SUT test model, reasonable benchmarks regarding 503 multiple SUTs or heterogeneous environments may be collected. In this 504 extension, the single SUT is replaced by a system of interconnected 505 network SUTs. This test methodology would support the benchmarking of a 506 variety of device/media/service/protocol combinations. For example, a 507 configuration for a LAN-to-WAN-to-LAN test might be: 509 (1) ATM UNI -> SUT 1 -> BISUP -> SUT 2 -> ATM UNI 511 Or an extended LAN configuration might be: 513 (2) ATM UNI -> SUT 1 -> PNNI Network -> SUT 2 -> ATM UNI 515 In both examples 1 and 2, end-to-end benchmarks of each system could be 516 empirically ascertained. Other behavior may be characterized through the 517 use of intermediate devices. In example 2, the configuration may be used 518 to give an indication of the effect of PNNI routing on IP throughput. 520 Because multiple SUTs are treated as a single system, there are 521 limitations to this methodology. For instance, this methodology may 522 yield an aggregate benchmark for a tested system. That benchmark alone, 523 however, may not necessarily reflect asymmetries in behavior between the 524 SUTs, latencies introduced by other apparatus (e.g., CSUs/DSUs, 525 switches), etc. 527 Further, care must be used when comparing benchmarks of different 528 systems by ensuring that the SUTs' features and configuration of the 529 tested systems have the appropriate common denominators to allow 530 comparison. 532 2.19. Maximum IP PDU rate 534 The maximum IP PDU rates that should be used when testing LAN 535 connections SHOULD be the listed theoretical maximum rate for the IP PDU 536 size on the media. 538 The maximum IP PDU rate that should be used when testing WAN connections 539 SHOULD be greater than the listed theoretical maximum rate for the IP 540 PDU size on that speed connection. The higher rate for WAN tests is to 541 compensate for the fact that some vendors employ various forms of header 542 compression. 544 A list of maximum IP PDU rates for LAN connections is included in 545 Appendix B. 547 2.20. Bursty traffic 549 It is convenient to measure the SUT performance under steady state load; 550 however, this is an unrealistic way to gauge the functioning of a SUT. 551 Actual network traffic normally consists of bursts of IP PDUs. 553 Some of the tests described below SHOULD be performed with both constant 554 bit rate, bursty Unspecified Bit Rate (UBR) Best Effort [AF-TM4.0] and 555 Variable Bit Rate Non-real Time (VBR-nrt) Best Effort [AF-TM4.0]. The 556 IP PDUs within a burst are transmitted with the minimum legitimate 557 inter-IP PDU gap. 559 The objective of the test is to determine the minimum interval between 560 bursts that the SUT can process with no IP PDU loss. Tests SHOULD be 561 run with burst sizes of 10% of Maximum Burst Size (MBS), 20% of MBS, 50% 562 of MBS and 100% MBS. Note that the number of IP PDUs in each burst will 563 depend on the PDU size. For UBR, the MBS refers to the associated VBR 564 traffic parameters. 566 2.21. Trial description 568 A particular test consists of multiple trials. Each trial returns one 569 piece of information, for example the loss rate at a particular input IP 570 PDU rate. Each trial consists of five of phases: 572 a) If the SUT is a switch supporting PNNI, send the routing update to 573 the SUT receive port and wait two seconds to be sure that the routing 574 has settled. 576 b) Send an ATM ARP PDU to determine the ATM address corresponding to the 577 destination IP address. The formats of the ATM ARP PDU that should be 578 used are shown in the Test Frame Formats document and MUST be in 579 accordance with RFC 2225. 581 c) Stimulate SUT with traffic load. 583 d) Wait for two seconds for any residual IP PDUs to be received. 585 e) Wait for at least five seconds for the SUT to restabilize. 587 2.22. Trial duration 588 The objective of the tests defined in this document is to accurately 589 characterize the behavior of a particular piece of network equipment 590 under varying traffic loads. The choice of test duration must be a 591 compromise between this objective and keeping the duration of the 592 benchmarking test suite within reasonable bounds. The SUT SHOULD be 593 stimulated for at least 60 seconds. If this time period results in a 594 high variance in the test results, the SUT SHOULD be stimulated for at 595 least 300 seconds. 597 2.23. Address resolution 599 The SUT MUST be able to respond to address resolution requests sent by 600 another SUT, an ATM ARP server or the test equipment in accordance with 601 RFC 2225. 603 2.24. Synchronized Payload Bit Pattern. 605 Some measurements assume that both the transmitter and receiver payload 606 information is synchronized. Synchronization MUST be achieved by 607 supplying a known bit pattern to both the transmitter and receiver. 608 This bit pattern MUST be one of the following: PRBS-15, PRBS-23, 0xFF00, 609 or 0xAA55. 611 2.25. Burst Traffic Descriptors. 613 Some measurements require busty traffic patterns. These patterns MUST 614 conform to one of the following traffic descriptors: 616 1) PCR=100% allotted line rate, SCR=50% allotted line rate, and MBS=8192 618 2) PCR=100% allotted line rate, SCR=50% allotted line rate, and MBS=4096 620 3) PCR=90% allotted line rate, SCR=50% allotted line rate, and MBS=8192 622 4) PCR=90% allotted line rate, SCR=50% allotted line rate, and MBS=4096 624 5) PCR=90% allotted line rate, SCR=45% allotted line rate, and MBS=8192 626 6) PCR=90% allotted line rate, SCR=45% allotted line rate, and MBS=4096 628 7) PCR=80% allotted line rate, SCR=40% allotted line rate, and MBS=65536 629 8) PCR=80% allotted line rate, SCR=40% allotted line rate, and MBS=32768 631 The allotted line rate refers to the total available line rate divided 632 by the number of VCCs in use. 634 3. Performance Metrics 636 3.1. Physical Layer- SONET 638 3.1.1. Pointer Movements 640 3.1.1.1. Pointer Movement Propagation. 642 Objective: To determine that the SUT does not propagate pointer movements 643 as defined in RFC 2761 "Terminology for ATM Benchmarking". 645 Procedure: 647 1) Set up the SUT and test device using the uni-directional 648 configuration. 650 2) Send a specific number of IP PDUs at a specific rate through the SUT. 651 Since this test is not a throughput test, the rate should not be greater 652 than 90% of line rate. The cell payload SHOULD contain valid IP PDUs. 653 The IP PDUs MUST be encapsulated in AAL5. 655 3) Count the IP PDUs that are transmitted by the SUT to verify 656 connectivity and load. If the count on the test device is the same on 657 the SUT, continue the test, else lower the test device traffic rate 658 until the counts are the same. 660 4) Inject one forward payload pointer movement. Verify that the SUT 661 does not change the pointer. 663 5) Inject one forward payload pointer movement every 1 second. Verify 664 that the SUT does not change the pointer. 666 6) Discontinue the payload pointer movement. 668 7) Inject five forward payload pointer movements every 1 second. Verify 669 that the SUT does not change the pointer. 671 8) Discontinue the payload pointer movement. 673 9) Inject one backward payload pointer movement. Verify that the SUT 674 does not change the pointer. 676 10) Inject one backward payload pointer movement every 1 second. Verify 677 that the SUT does not change the pointer. 679 11) Discontinue the payload pointer movement. 681 12) Inject five backward payload pointer movements every 1 second. 682 Verify that the SUT does not change the pointer. 684 13) Discontinue the payload pointer movement. 686 Reporting Format: 688 The results of the pointer movement propagation test SHOULD be reported 689 in a form of a table. The rows SHOULD be labeled single pointer 690 movement, one pointer movement per second, and five pointer movements 691 per second. The columns SHOULD be labeled pointer movement and loss of 692 pointer. The elements of the table SHOULD be either True or False, 693 indicating whether the particular condition was observed for each test. 695 The table MUST also indicate the IP PDU size in octets and traffic rate 696 in IP PDUs per second as generated by the test device. 698 3.1.1.2. Cell Loss due to Pointer Movement. 700 Objective: To determine if the SUT will drop cells due to pointer movements 701 as defined in RFC 2761 "Terminology for ATM Benchmarking". 703 Procedure: 705 1) Set up the SUT and test device using the uni-directional 706 configuration. 708 2) Send a specific number of cells at a specific rate through the SUT. 710 Since this test is not a throughput test, the rate should not be greater 711 than 90% of line rate. The cell payload SHOULD contain valid IP PDUs. 712 The IP PDUs MUST be encapsulated in AAL5. 714 3) Count the cells that are transmitted by the SUT to verify 715 connectivity and load. If the count on the test device is the same on 716 the SUT, continue the test; else lower the test device traffic rate 717 until the counts are the same. 719 4) Inject one forward payload pointer movement. Verify that the SUT 720 does not drop any cells. 722 5) Inject one forward payload pointer movement every 1 second. Verify 723 that the SUT does not drop any cells. 725 6) Discontinue the payload pointer movement. 727 7) Inject five forward payload pointer movements every 1 second. Verify 728 that the SUT does not drop any cells. 730 8) Discontinue the payload pointer movement. 732 9) Inject one backward payload pointer movement. Verify that the SUT 733 does not drop any cells. 735 10) Inject one backward payload pointer movement every 1 second. Verify 736 that the SUT does not drop any cells. 738 11) Discontinue the payload pointer movement. 740 12) Inject five backward payload pointer movements every 1 second. 741 Verify that the SUT does not drop any cells. 743 13) Discontinue the payload pointer movement. 745 Reporting Format: 747 The results of the cell loss due to pointer movement test SHOULD be 748 reported in a form of a table. The rows SHOULD be labeled single pointer 749 movement, one pointer movement per second, and five pointer movements 750 per second. The columns SHOULD be labeled cell loss and number of cells 751 lost. The elements of column 1 SHOULD be either True or False, 752 indicating whether the particular condition was observed for each test. 753 The elements of column 2 SHOULD be non-negative integers. 755 The table MUST also indicate the traffic rate in IP PDUs per second as 756 generated by the test device. 758 3.1.1.3. IP Packet Loss due to Pointer Movement. 760 Objective: To determine if the SUT will drop IP packets due to pointer 761 movements as defined in RFC 2761 "Terminology for ATM Benchmarking". 763 Procedure: 765 1) Set up the SUT and test device using the uni-directional 766 configuration. 768 2) Send a specific number of IP packets at a specific rate through the 769 SUT. Since this test is not a throughput test, the rate should not be 770 greater than 90% of line rate. The IP PDUs MUST be encapsulated in 771 AAL5. 773 3) Count the IP packets that are transmitted by the SUT to verify 774 connectivity and load. If the count on the test device is the same on 775 the SUT, continue the test; else lower the test device traffic rate 776 until the counts are the same. 778 4) Inject one forward payload pointer movement. Verify that the SUT 779 does not drop any packets. 781 5) Inject one forward payload pointer movement every 1 second. Verify 782 that the SUT does not drop any packets. 784 6) Discontinue the payload pointer movement. 786 7) Inject five forward payload pointer movements every 1 second. Verify 787 that the SUT does not drop any packets. 789 8) Discontinue the payload pointer movement. 791 9) Inject one backward payload pointer movement. Verify that the SUT 792 does not drop any packets. 794 10) Inject one backward payload pointer movement every 1 second. Verify 795 that the SUT does not drop any packets. 797 11) Discontinue the payload pointer movement. 799 12) Inject five backward payload pointer movements every 1 second. 800 Verify that the SUT does not drop any packets. 802 13) Discontinue the payload pointer movement. 804 Reporting Format: 806 The results of the IP packet loss due to pointer movement test SHOULD be 807 reported in a form of a table. The rows SHOULD be labeled single pointer 808 movement, one pointer movement per second, and five pointer movements 809 per second. The columns SHOULD be labeled packet loss and number of 810 packets lost. The elements of column 1 SHOULD be either True or False, 811 indicating whether the particular condition was observed for each test. 812 The elements of column 2 SHOULD be non-negative integers. 814 The table MUST also indicate the packet size in octets and traffic rate 815 in packets per second as generated by the test device. 817 3.1.2. Transport Overhead (TOH) Error Count 819 3.1.2.1. TOH Error Propagation. 821 Objective: To determine that the SUT does not propagate TOH errors as 822 defined in RFC 2761 "Terminology for ATM Benchmarking". 824 Procedure: 826 1) Set up the SUT and test device using the uni-directional 827 configuration. 829 2) Send a specific number of IP PDUs at a specific rate through the SUT. 830 Since this test is not a throughput test, the rate should not be greater 831 than 90% of line rate. The cell payload SHOULD contain valid IP PDUs. 832 The IP PDUs MUST be encapsulated in AAL5. 834 3) Count the IP PDUs that are transmitted by the SUT to verify 835 connectivity and load. If the count on the test device is the same on 836 the SUT, continue the test, else lower the test device traffic rate 837 until the counts are the same. 839 4) Inject one error in the first bit of the A1 and A2 Frameword. Verify 840 that the SUT does not propagate the error. 842 5) Inject one error in the first bit of the A1 and A2 Frameword every 1 843 second. Verify that the SUT does not propagate the error. 845 6) Discontinue the Frameword error. 847 7) Inject one error in the first bit of the A1 and A2 Frameword for 4 848 consecutive IP PDUs in every 6 IP PDUs. Verify that the SUT indicates 849 Loss of Frame. 851 8) Discontinue the Frameword error. 853 Reporting Format: 855 The results of the TOH error propagation test SHOULD be reported in a 856 form of a table. The rows SHOULD be labeled single error, one error per 857 second, and four consecutive errors every 6 IP PDUs. The columns SHOULD 858 be labeled error propagated and loss of IP PDU. The elements of the 859 table SHOULD be either True or False, indicating whether the particular 860 condition was observed for each test. 862 The table MUST also indicate the IP PDU size in octets and traffic rate 863 in IP PDUs per second as generated by the test device. 865 3.1.2.2. Cell Loss due to TOH Error. 867 Objective: To determine if the SUT will drop cells due TOH Errors as 868 defined in RFC 2761 "Terminology for ATM Benchmarking". 870 Procedure: 872 1) Set up the SUT and test device using the uni-directional 873 configuration. 875 2) Send a specific number of cells at a specific rate through the SUT. 877 Since this test is not a throughput test, the rate should not be greater 878 than 90% of line rate. The cell payload SHOULD contain valid IP PDUs. 879 The IP PDUs MUST be encapsulated in AAL5. 881 3) Count the cells that are transmitted by the SUT to verify 882 connectivity and load. If the count on the test device is the same on 883 the SUT, continue the test; else lower the test device traffic rate 884 until the counts are the same. 886 4) Inject one error in the first bit of the A1 and A2 Frameword. Verify 887 that the SUT does not drop any cells. 889 5) Inject one error in the first bit of the A1 and A2 Frameword every 1 890 second. Verify that the SUT does not drop any cells. 892 6) Discontinue the Frameword error. 894 7) Inject one error in the first bit of the A1 and A2 Frameword for 4 895 consecutive IP PDUs in every 6 IP PDUs. Verify that the SUT does drop 896 cells. 898 8) Discontinue the Frameword error. 900 Reporting Format: 902 The results of the Cell Loss due to TOH errors test SHOULD be reported 903 in a form of a table. The rows SHOULD be labeled single error, one error 904 per second, and four consecutive errors every 6 IP PDUs. The columns 905 SHOULD be labeled cell loss and number of cells lost. The elements of 906 column 1 SHOULD be either True or False, indicating whether the 907 particular condition was observed for each test. The elements of column 908 2 SHOULD be non-negative integers. 910 The table MUST also indicate the traffic rate in IP PDUs per second as 911 generated by the test device. 913 3.1.2.3. IP Packet Loss due to TOH Error. 915 Objective: To determine if the SUT will drop IP packets due to TOH errors 916 as defined in RFC 2761 "Terminology for ATM Benchmarking". 918 Procedure: 920 1) Set up the SUT and test device using the uni-directional 921 configuration. 923 2) Send a specific number of IP packets at a specific rate through the 924 SUT. Since this test is not a throughput test, the rate should not be 925 greater than 90% of line rate. The IP PDUs MUST be encapsulated in 926 AAL5. 928 3) Count the IP packets that are transmitted by the SUT to verify 929 connectivity and load. If the count on the test device is the same on 930 the SUT, continue the test; else lower the test device traffic rate 931 until the counts are the same. 933 4) Inject one error in the first bit of the A1 and A2 Frameword. Verify 934 that the SUT does not drop any packets. 936 5) Inject one error in the first bit of the A1 and A2 Frameword every 1 937 second. Verify that the SUT does not drop any packets. 939 6) Discontinue the Frameword error. 941 7) Inject one error in the first bit of the A1 and A2 Frameword for 4 942 consecutive IP PDUs in every 6 IP PDUs. Verify that the SUT does drop 943 packets. 945 8) Discontinue the Frameword error. 947 Reporting Format: 949 The results of the IP packet loss due to TOH errors test SHOULD be 950 reported in a form of a table. The rows SHOULD be labeled single error, 951 one error per second, and four consecutive errors every 6 IP PDUs. The 952 columns SHOULD be labeled packet loss and number of packets lost. The 953 elements of column 1 SHOULD be either True or False, indicating whether 954 the particular condition was observed for each test. The elements of 955 column 2 SHOULD be non-negative integers. 957 The table MUST also indicate the packet size in octets and traffic rate 958 in packets per second as generated by the test device. 960 3.1.3. Path Overhead (POH) Error Count 961 3.1.3.1. POH Error Propagation. 963 Objective: To determine that the SUT does not propagate POH errors as 964 defined in RFC 2761 "Terminology for ATM Benchmarking". 966 Procedure: 968 1) Set up the SUT and test device using the uni-directional 969 configuration. 971 2) Send a specific number of IP PDUs at a specific rate through the SUT. 972 Since this test is not a throughput test, the rate should not be greater 973 than 90% of line rate. The cell payload SHOULD contain valid IP PDUs. 974 The IP PDUs MUST be encapsulated in AAL5. 976 3) Count the IP PDUs that are transmitted by the SUT to verify 977 connectivity and load. If the count on the test device is the same on 978 the SUT, continue the test, else lower the test device traffic rate 979 until the counts are the same. 981 4) Inject one error in the B3 (Path BIP8) byte. Verify that the SUT 982 does not propagate the error. 984 5) Inject one error in the B3 byte every 1 second. Verify that the SUT 985 does not propagate the error. 987 6) Discontinue the POH error. 989 Reporting Format: 991 The results of the POH error propagation test SHOULD be reported in a 992 form of a table. The rows SHOULD be labeled single error and one error 993 per second. The columns SHOULD be labeled error propagated and loss of 994 IP PDU. The elements of the table SHOULD be either True or False, 995 indicating whether the particular condition was observed for each test. 997 The table MUST also indicate the IP PDU size in octets and traffic rate 998 in IP PDUs per second as generated by the test device. 1000 3.1.3.2. Cell Loss due to POH Error. 1002 Objective: To determine if the SUT will drop cells due POH Errors as 1003 defined in RFC 2761 "Terminology for ATM Benchmarking". 1005 Procedure: 1007 1) Set up the SUT and test device using the uni-directional 1008 configuration. 1010 2) Send a specific number of cells at a specific rate through the SUT. 1011 Since this test is not a throughput test, the rate should not be greater 1012 than 90% of line rate. The cell payload SHOULD contain valid IP PDUs. 1013 The IP PDUs MUST be encapsulated in AAL5. 1015 3) Count the cells that are transmitted by the SUT to verify 1016 connectivity and load. If the count on the test device is the same on 1017 the SUT, continue the test; else lower the test device traffic rate 1018 until the counts are the same. 1020 4) Inject one error in the B3 (Path BIP8) byte. Verify that the SUT 1021 does not drop any cells. 1023 5) Inject one error in the B3 byte every 1 second. Verify that the SUT 1024 does not drop any cells. 1026 6) Discontinue the POH error. 1028 Reporting Format: 1030 The results of the Cell Loss due to POH errors test SHOULD be reported 1031 in a form of a table. The rows SHOULD be labeled single error and one 1032 error per second. The columns SHOULD be labeled cell loss and number of 1033 cells lost. The elements of column 1 SHOULD be either True or False, 1034 indicating whether the particular condition was observed for each test. 1035 The elements of column 2 SHOULD be non-negative integers. 1037 The table MUST also indicate the traffic rate in IP PDUs per second as 1038 generated by the test device. 1040 3.1.3.3. IP Packet Loss due to POH Error. 1042 Objective: To determine if the SUT will drop IP packets due to POH errors 1043 as defined in RFC 2761 "Terminology for ATM Benchmarking". 1045 Procedure: 1047 1) Set up the SUT and test device using the uni-directional 1048 configuration. 1050 2) Send a specific number of IP packets at a specific rate through the 1051 SUT. Since this test is not a throughput test, the rate should not be 1052 greater than 90% of line rate. The IP PDUs MUST be encapsulated in 1053 AAL5. 1055 3) Count the IP packets that are transmitted by the SUT to verify 1056 connectivity and load. If the count on the test device is the same on 1057 the SUT, continue the test; else lower the test device traffic rate 1058 until the counts are the same. 1060 4) Inject one error in the B3 (Path BIP8) byte. Verify that the SUT 1061 does not drop any packets. 1063 5) Inject one error in the B3 byte every 1 second. Verify that the SUT 1064 does not drop any packets. 1066 6) Discontinue the POH error. 1068 Reporting Format: 1070 The results of the IP packet loss due to POH errors test SHOULD be 1071 reported in a form of a table. The rows SHOULD be labeled single error 1072 and one error per second. The columns SHOULD be labeled packet loss and 1073 number of packets lost. The elements of column 1 SHOULD be either True 1074 or False, indicating whether the particular condition was observed for 1075 each test. The elements of column 2 SHOULD be non-negative integers. 1077 The table MUST also indicate the packet size in octets and traffic rate 1078 in packets per second as generated by the test device. 1080 3.2. ATM Layer 1082 3.2.1. Two-Point Cell Delay Variation (CDV) 1084 3.2.1.1. Test Setup 1086 The cell delay measurements assume that both the transmitter and 1087 receiver timestamp information is synchronized. Synchronization SHOULD 1088 be achieved by supplying a common clock signal (minimum of 100 Mhz or 10 1089 ns resolution) to both the transmitter and receiver. The maximum 1090 timestamp values MUST be recorded to ensure synchronization in the case 1091 of counter rollover. The cell delay measurements SHOULD utilize the 1092 O.191 cell (ITUT-O.191) encapsulated in a valid IP packet. If the O.191 1093 cell is not available, a test cell encapsulated in a valid IP packet MAY 1094 be used. The test cell MUST contain a transmit timestamp which can be 1095 correlated with a receive timestamp. A description of the test cell MUST 1096 be included in the test results. The description MUST include the 1097 timestamp length (in bits), counter rollover value, and the timestamp 1098 accuracy (in ns). 1100 3.2.1.2. Two-point CDV/Steady Load/One VCC 1102 Objective: To determine the SUT variation in cell transfer delay with one 1103 VCC as defined in RFC 2761 "Terminology for ATM Benchmarking". 1105 Procedure: 1107 1) Set up the SUT and test device using the bi-directional 1108 configuration. 1110 2) Configure the SUT and test device with one VCC. The VCC SHOULD 1111 contain one VPI/VCI. The VCC MUST be configured as either a CBR, VBR, or 1112 UBR connection. The VPI/VCI MUST not be one of the reserved ATM 1113 signaling channels (e.g. [0,5], [0,16]). 1115 3) Send a specific number of IP packets containing timestamps at a 1116 specific constant rate through the SUT via the defined test VCC. Since 1117 this test is not a throughput test, the rate should not be greater than 1118 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 1120 4) Count the IP packets that are transmitted by the SUT to verify 1121 connectivity and load. If the count on the test device is the same on 1122 the SUT, continue the test; else lower the test device traffic rate 1123 until the counts are the same. 1125 5) Record the packets timestamps at the transmitter and receiver ends of 1126 the test device. 1128 Reporting Format: 1130 The results of the Two-point CDV/Steady Load/One VCC test SHOULD be 1131 reported in a form of text, graph, and histogram. 1133 The text results SHOULD display the numerical values of the CDV. The 1134 values given SHOULD include: time period of test in s, test VPI/VCI 1135 value, total number of cells transmitted and received on the given 1136 VPI/VCI during the test in positive integers, maximum and minimum CDV 1137 during the test in us, and peak-to-peak CDV in us. 1139 The graph results SHOULD display the cell delay values. The x- 1140 coordinate SHOULD be the test run time in either seconds, minutes or 1141 days depending on the total length of the test. The x-coordinate time 1142 SHOULD be configurable. The y-coordinate SHOULD be the cell delay in 1143 us. The integration time per point MUST be indicated. 1145 The histogram results SHOULD display the peak-to-peak cell delay. The 1146 x- coordinate SHOULD be the cell delay in us with at least 256 bins. 1147 The y- coordinate SHOULD be the number of cells observed in each bin. 1149 The results MUST also indicate the packet size in octets, traffic rate 1150 in packets per second, and bearer class as generated by the test device. 1151 The VCC and VPI/VCI values MUST be indicated. The bearer class of the 1152 created VCC MUST also be indicated. 1154 3.2.1.3. Two-point CDV/Steady Load/Twelve VCCs 1156 Objective: To determine the SUT variation in cell transfer delay with 1157 twelve VCCs as defined in RFC 2761 "Terminology for ATM Benchmarking". 1159 Procedure: 1161 1) Set up the SUT and test device using the bi-directional 1162 configuration. 1164 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 1165 12 VCIs. The VCC's MUST be configured as either a CBR, VBR, or UBR 1166 connection. The VPI/VCIs MUST not be one of the reserved ATM signaling 1167 channels (e.g. [0,5], [0,16]). 1169 3) Send a specific number of IP packets containing timestamps at a 1170 specific constant rate through the SUT via the defined test VCCs. All 1171 of the VPI/VCI pairs will generate traffic at the same traffic rate. 1173 Since this test is not a throughput test, the rate should not be greater 1174 than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 1176 4) Count the IP packets that are transmitted by the SUT on all VCCs to 1177 verify connectivity and load. If the count on the test device is the 1178 same on the SUT, continue the test; else lower the test device traffic 1179 rate until the counts are the same. 1181 5) Record the packets timestamps at the transmitter and receiver ends of 1182 the test device for all VCCs. 1184 Reporting Format: 1186 The results of the Two-point CDV/Steady Load/Twelve VCCs test SHOULD be 1187 reported in a form of text, graph, and histograms. 1189 The text results SHOULD display the numerical values of the CDV. The 1190 values given SHOULD include: time period of test in s, test VPI/VCI 1191 values, total number of cells transmitted and received on each VCC 1192 during the test in positive integers, maximum and minimum CDV on each 1193 VCC during the test in us, and peak-to-peak CDV on each VCC in us. 1195 The graph results SHOULD display the cell delay values. The x- 1196 coordinate SHOULD be the test run time in either seconds, minutes or 1197 days depending on the total length of the test. The x-coordinate time 1198 SHOULD be configurable. The y-coordinate SHOULD be the cell delay for 1199 each VCC in ms. There SHOULD be 12 curves on the graph, one curves 1200 indicated and labeled for each VCC. The integration time per point MUST 1201 be indicated. 1203 The histograms SHOULD display the peak-to-peak cell delay. There will be 1204 one histogram for each VCC. The x-coordinate SHOULD be the cell delay 1205 in us with at least 256 bins. The y-coordinate SHOULD be the number of 1206 cells observed in each bin. 1208 The results MUST also indicate the packet size in octets, traffic rate 1209 in packets per second, and bearer class as generated by the test device. 1210 The VCC and VPI/VCI values MUST be indicated. The bearer class of the 1211 created VCC MUST also be indicated. 1213 3.2.1.4. Two-point CDV/Steady Load/Maximum VCCs 1214 Objective: To determine the SUT variation in cell transfer delay with the 1215 maximum number VCCs supported on the SUT as defined in RFC 2761 1216 "Terminology for ATM Benchmarking". 1218 Procedure: 1220 1) Set up the SUT and test device using the bi-directional 1221 configuration. 1223 2) Configure the SUT and test device with the maximum number of VCCs 1224 supported on the SUT. For example, if the maximum number of VCCs 1225 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The 1226 VCC's MUST be configured as either a CBR, VBR, or UBR connection. The 1227 VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. 1228 [0,5], [0,16]). 1230 3) Send a specific number of IP packets containing timestamps at a 1231 specific constant rate through the SUT via the defined test VCCs. All 1232 of the VPI/VCI pairs will generate traffic at the same traffic rate. 1233 Since this test is not a throughput test, the rate should not be greater 1234 than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 1236 4) Count the IP packets that are transmitted by the SUT on all VCCs to 1237 verify connectivity and load. If the count on the test device is the 1238 same on the SUT, continue the test; else lower the test device traffic 1239 rate until the counts are the same. 1241 5) Record the packets timestamps at the transmitter and receiver ends of 1242 the test device for all VCCs. 1244 Reporting Format: 1246 The results of the Two-point CDV/Steady Load/Maximum VCCs test SHOULD be 1247 reported in a form of text, graphs, and histograms. 1249 The text results SHOULD display the numerical values of the CDV. The 1250 values given SHOULD include: time period of test in s, test VPI/VCI 1251 values, total number of cells transmitted and received on each VCC 1252 during the test in positive integers, maximum and minimum CDV on each 1253 VCC during the test in us, and peak-to-peak CDV on each VCC in us. 1255 The graph results SHOULD display the cell delay values. There will be 1256 (Max number of VCCs/10) graphs, with 10 VCCs indicated on each graph. 1257 The x-coordinate SHOULD be the test run time in either seconds, minutes 1258 or days depending on the total length of the test. The x-coordinate time 1259 SHOULD be configurable. The y-coordinate SHOULD be the cell delay for 1260 each VCC in us. There SHOULD be no more than 10 curves on each graph, 1261 one curve indicated and labeled for each VCC. The integration time per 1262 point MUST be indicated. 1264 The histograms SHOULD display the peak-to-peak cell delay. There will be 1265 one histogram for each VCC. The x-coordinate SHOULD be the cell delay in 1266 us with at least 256 bins. The y-coordinate SHOULD be the number of 1267 cells observed in each bin. 1269 The results MUST also indicate the packet size in octets, traffic rate 1270 in packets per second, and bearer class as generated by the test device. 1271 The VCC and VPI/VCI values MUST be indicated. The bearer class of the 1272 created VCC MUST also be indicated. 1274 3.2.1.5. Two-point CDV/Bursty VBR Load/One VCC 1276 Objective: To determine the SUT variation in cell transfer delay with one 1277 VCC as defined in RFC 2761 "Terminology for ATM Benchmarking". 1279 Procedure: 1281 1) Set up the SUT and test device using the bi-directional 1282 configuration. 1284 2) Configure the SUT and test device with one VCC. The VCC SHOULD 1285 contain one VPI/VCI. The VCC MUST be configured as either a CBR or VBR 1286 connection. The VPI/VCI MUST not be one of the reserved ATM signaling 1287 channels (e.g. [0,5], [0,16]). 1289 3) Send a specific number of IP packets containing timestamps at a 1290 specific VBR through the SUT via the defined test VCC. Since this test 1291 is not a throughput test, the rate should not be greater than 90% of 1292 line rate. The IP PDUs MUST be encapsulated in AAL5. 1294 4) Count the IP packets that are transmitted by the SUT to verify 1295 connectivity and load. If the count on the test device is the same on 1296 the SUT, continue the test; else lower the test device traffic rate 1297 until the counts are the same. 1299 5) Record the packets timestamps at the transmitter and receiver ends of 1300 the test device. 1302 Reporting Format: 1304 The results of the Two-point CDV/Bursty VBR Load/One VCC test SHOULD be 1305 reported in a form of text, graph, and histogram. 1307 The text results SHOULD display the numerical values of the CDV. The 1308 values given SHOULD include: time period of test in s, test VPI/VCI 1309 value, total number of cells transmitted and received on the given 1310 VPI/VCI during the test in positive integers, maximum and minimum CDV 1311 during the test in us, and peak-to-peak CDV in us. 1313 The graph results SHOULD display the cell delay values. The x- 1314 coordinate SHOULD be the test run time in either seconds, minutes or 1315 days depending on the total length of the test. The x-coordinate time 1316 SHOULD be configurable. The y-coordinate SHOULD be the cell delay in 1317 us. The integration time per point MUST be indicated. 1319 The histogram results SHOULD display the peak-to-peak cell delay. The 1320 x- coordinate SHOULD be the cell delay in us with at least 256 bins. 1321 The y- coordinate SHOULD be the number of cells observed in each bin. 1323 The results MUST also indicate the packet size in octets, traffic rate 1324 in packets per second, and bearer class as generated by the test device. 1325 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 1326 be indicated. The bearer class of the created VCC MUST also be 1327 indicated. 1329 3.2.1.6. Two-point CDV/Bursty VBR Load/Twelve VCCs 1331 Objective: To determine the SUT variation in cell transfer delay with 1332 twelve VCCs as defined in RFC 2761 "Terminology for ATM Benchmarking". 1334 Procedure: 1336 1) Set up the SUT and test device using the bi-directional 1337 configuration. 1339 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 1340 12 VCIs. The VCC's MUST be configured as either a CBR or VBR connection. 1342 The VPI/VCIs MUST not be one of the reserved ATM signaling channels 1343 (e.g. [0,5], [0,16]). 1345 3) Send a specific number of IP packets containing timestamps at a 1346 specific VBR through the SUT via the defined test VCCs. All of the 1347 VPI/VCI pairs will generate traffic at the same traffic rate. Since 1348 this test is not a throughput test, the rate should not be greater than 1349 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 1351 4) Count the IP packets that are transmitted by the SUT on all VCCs to 1352 verify connectivity and load. If the count on the test device is the 1353 same on the SUT, continue the test; else lower the test device traffic 1354 rate until the counts are the same. 1356 5) Record the packets timestamps at the transmitter and receiver ends of 1357 the test device for all VCCs. 1359 Reporting Format: 1361 The results of the Two-point CDV/Bursty VBR Load/Twelve VCCs test SHOULD 1362 be reported in a form of text, graph, and histograms. 1364 The text results SHOULD display the numerical values of the CDV. The 1365 values given SHOULD include: time period of test in s, test VPI/VCI 1366 values, total number of cells transmitted and received on each VCC 1367 during the test in positive integers, maximum and minimum CDV on each 1368 VCC during the test in us, and peak-to-peak CDV on each VCC in us. 1370 The graph results SHOULD display the cell delay values. The x- 1371 coordinate SHOULD be the test run time in either seconds, minutes or 1372 days depending on the total length of the test. The x-coordinate time 1373 SHOULD be configurable. The y-coordinate SHOULD be the cell delay for 1374 each VCC in ms. There SHOULD be 12 curves on the graph, one curves 1375 indicated and labeled for each VCC. The integration time per point MUST 1376 be indicated. 1378 The histograms SHOULD display the peak-to-peak cell delay. There will be 1379 one histogram for each VCC. The x-coordinate SHOULD be the cell delay 1380 in us with at least 256 bins. The y-coordinate SHOULD be the number of 1381 cells observed in each bin. 1383 The results MUST also indicate the packet size in octets, traffic rate 1384 in packets per second, and bearer class as generated by the test device. 1385 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 1386 be indicated. The bearer class of the created VCC MUST also be 1387 indicated. 1389 3.2.1.7. Two-point CDV/Bursty VBR Load/Maximum VCCs 1391 Objective: To determine the SUT variation in cell transfer delay with the 1392 maximum number VCCs supported on the SUT as defined in RFC 2761 1393 "Terminology for ATM Benchmarking". 1395 Procedure: 1397 1) Set up the SUT and test device using the bi-directional 1398 configuration. 1400 2) Configure the SUT and test device with the maximum number of VCCs 1401 supported on the SUT. For example, if the maximum number of VCCs 1402 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The 1403 VCC's MUST be configured as either a CBR or VBR connection. The 1404 VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. 1405 [0,5], [0,16]). 1407 3) Send a specific number of IP packets containing timestamps at a 1408 specific VBR through the SUT via the defined test VCCs. All of the 1409 VPI/VCI pairs will generate traffic at the same traffic rate. Since 1410 this test is not a throughput test, the rate should not be greater than 1411 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 1413 4) Count the IP packets that are transmitted by the SUT on all VCCs to 1414 verify connectivity and load. If the count on the test device is the 1415 same on the SUT, continue the test; else lower the test device traffic 1416 rate until the counts are the same. 1418 5) Record the packets timestamps at the transmitter and receiver ends of 1419 the test device for all VCCs. 1421 Reporting Format: 1423 The results of the Two-point CDV/Bursty VBR Load/Maximum VCCs test 1424 SHOULD be reported in a form of text, graphs, and histograms. 1426 The text results SHOULD display the numerical values of the CDV. The 1427 values given SHOULD include: time period of test in s, test VPI/VCI 1428 values, total number of cells transmitted and received on each VCC 1429 during the test in positive integers, maximum and minimum CDV on each 1430 VCC during the test in us, and peak-to-peak CDV on each VCC in us. 1432 The graph results SHOULD display the cell delay values. There will be 1433 (Max number of VCCs/10) graphs, with 10 VCCs indicated on each graph. 1434 The x-coordinate SHOULD be the test run time in either seconds, minutes 1435 or days depending on the total length of the test. The x-coordinate time 1436 SHOULD be configurable. The y-coordinate SHOULD be the cell delay for 1437 each VCC in us. There SHOULD be no more than 10 curves on each graph, 1438 one curve indicated and labeled for each VCC. The integration time per 1439 point MUST be indicated. 1441 The histograms SHOULD display the peak-to-peak cell delay. There will be 1442 one histogram for each VCC. The x-coordinate SHOULD be the cell delay in 1443 us with at least 256 bins. The y-coordinate SHOULD be the number of 1444 cells observed in each bin. 1446 The results MUST also indicate the packet size in octets, traffic rate 1447 in packets per second, and bearer class as generated by the test device. 1448 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 1449 be indicated. The bearer class of the created VCC MUST also be 1450 indicated. 1452 3.2.1.5. Two-point CDV/Bursty UBR Load/One VCC 1454 Objective: To determine the SUT variation in cell transfer delay with one 1455 VCC as defined in RFC 2761 "Terminology for ATM Benchmarking". 1457 Procedure: 1459 1) Set up the SUT and test device using the bi-directional 1460 configuration. 1462 2) Configure the SUT and test device with one VCC. The VCC SHOULD 1463 contain one VPI/VCI. The VCC MUST be configured as a UBR connection. 1464 The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. 1465 [0,5], [0,16]). 1467 3) Send a specific number of IP packets containing timestamps at a 1468 specific UBR through the SUT via the defined test VCC. Since this test 1469 is not a throughput test, the rate should not be greater than 90% of 1470 line rate. The IP PDUs MUST be encapsulated in AAL5. 1472 4) Count the IP packets that are transmitted by the SUT to verify 1473 connectivity and load. If the count on the test device is the same on 1474 the SUT, continue the test; else lower the test device traffic rate 1475 until the counts are the same. 1477 5) Record the packets timestamps at the transmitter and receiver ends of 1478 the test device. 1480 Reporting Format: 1482 The results of the Two-point CDV/Bursty UBR Load/One VCC test SHOULD be 1483 reported in a form of text, graph, and histogram. 1485 The text results SHOULD display the numerical values of the CDV. The 1486 values given SHOULD include: time period of test in s, test VPI/VCI 1487 value, total number of cells transmitted and received on the given 1488 VPI/VCI during the test in positive integers, maximum and minimum CDV 1489 during the test in us, and peak-to-peak CDV in us. 1491 The graph results SHOULD display the cell delay values. The x- 1492 coordinate SHOULD be the test run time in either seconds, minutes or 1493 days depending on the total length of the test. The x-coordinate time 1494 SHOULD be configurable. The y-coordinate SHOULD be the cell delay in 1495 us. The integration time per point MUST be indicated. 1497 The histogram results SHOULD display the peak-to-peak cell delay. The 1498 x- coordinate SHOULD be the cell delay in us with at least 256 bins. 1499 The y- coordinate SHOULD be the number of cells observed in each bin. 1501 The results MUST also indicate the packet size in octets, traffic rate 1502 in packets per second, and bearer class as generated by the test device. 1503 The VCC and VPI/VCI values MUST be indicated. The bearer class of the 1504 created VCC MUST also be indicated. 1506 3.2.1.6. Two-point CDV/Bursty UBR Load/Twelve VCCs 1508 Objective: To determine the SUT variation in cell transfer delay with 1509 twelve VCCs as defined in RFC 2761 "Terminology for ATM Benchmarking". 1511 Procedure: 1513 1) Set up the SUT and test device using the bi-directional 1514 configuration. 1516 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 1517 12 VCIs. The VCC's MUST be configured as a UBR connection. The VPI/VCIs 1518 MUST not be one of the reserved ATM signaling channels (e.g. [0,5], 1519 [0,16]). 1521 3) Send a specific number of IP packets containing timestamps at a 1522 specific UBR through the SUT via the defined test VCCs. All of the 1523 VPI/VCI pairs will generate traffic at the same traffic rate. Since 1524 this test is not a throughput test, the rate should not be greater than 1525 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 1527 4) Count the IP packets that are transmitted by the SUT on all VCCs to 1528 verify connectivity and load. If the count on the test device is the 1529 same on the SUT, continue the test; else lower the test device traffic 1530 rate until the counts are the same. 1532 5) Record the packets timestamps at the transmitter and receiver ends of 1533 the test device for all VCCs. 1535 Reporting Format: 1537 The results of the Two-point CDV/Bursty UBR Load/Twelve VCCs test SHOULD 1538 be reported in a form of text, graph, and histograms. 1540 The text results SHOULD display the numerical values of the CDV. The 1541 values given SHOULD include: time period of test in s, test VPI/VCI 1542 values, total number of cells transmitted and received on each VCC 1543 during the test in positive integers, maximum and minimum CDV on each 1544 VCC during the test in us, and peak-to-peak CDV on each VCC in us. 1546 The graph results SHOULD display the cell delay values. The x- 1547 coordinate SHOULD be the test run time in either seconds, minutes or 1548 days depending on the total length of the test. The x-coordinate time 1549 SHOULD be configurable. The y-coordinate SHOULD be the cell delay for 1550 each VCC in ms. There SHOULD be 12 curves on the graph, one curves 1551 indicated and labeled for each VCC. The integration time per point MUST 1552 be indicated. 1554 The histograms SHOULD display the peak-to-peak cell delay. There will be 1555 one histogram for each VCC. The x-coordinate SHOULD be the cell delay 1556 in us with at least 256 bins. The y-coordinate SHOULD be the number of 1557 cells observed in each bin. 1559 The results MUST also indicate the packet size in octets, traffic rate 1560 in packets per second, and bearer class as generated by the test device. 1561 The VCC and VPI/VCI values MUST be indicated. The bearer class of the 1562 created VCC MUST also be indicated. 1564 3.2.1.7. Two-point CDV/Bursty UBR Load/Maximum VCCs 1566 Objective: To determine the SUT variation in cell transfer delay with the 1567 maximum number VCCs supported on the SUT as defined in RFC 2761 1568 "Terminology for ATM Benchmarking". 1570 Procedure: 1572 1) Set up the SUT and test device using the bi-directional 1573 configuration. 1575 2) Configure the SUT and test device with the maximum number of VCCs 1576 supported on the SUT. For example, if the maximum number of VCCs 1577 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The 1578 VCC MUST be configured as a UBR connection. The VPI/VCIs MUST not be 1579 one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). 1581 3) Send a specific number of IP packets containing timestamps at a 1582 specific UBR through the SUT via the defined test VCCs. All of the 1583 VPI/VCI pairs will generate traffic at the same traffic rate. Since 1584 this test is not a throughput test, the rate should not be greater than 1585 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 1587 4) Count the IP packets that are transmitted by the SUT on all VCCs to 1588 verify connectivity and load. If the count on the test device is the 1589 same on the SUT, continue the test; else lower the test device traffic 1590 rate until the counts are the same. 1592 5) Record the packets timestamps at the transmitter and receiver ends of 1593 the test device for all VCCs. 1595 Reporting Format: 1597 The results of the Two-point CDV/Bursty UBR Load/Maximum VCCs test 1598 SHOULD be reported in a form of text, graphs, and histograms. 1600 The text results SHOULD display the numerical values of the CDV. The 1601 values given SHOULD include: time period of test in s, test VPI/VCI 1602 values, total number of cells transmitted and received on each VCC 1603 during the test in positive integers, maximum and minimum CDV on each 1604 VCC during the test in us, and peak-to-peak CDV on each VCC in us. 1606 The graph results SHOULD display the cell delay values. There will be 1607 (Max number of VCCs/10) graphs, with 10 VCCs indicated on each graph. 1608 The x-coordinate SHOULD be the test run time in either seconds, minutes 1609 or days depending on the total length of the test. The x-coordinate time 1610 SHOULD be configurable. The y-coordinate SHOULD be the cell delay for 1611 each VCC in us. There SHOULD be no more than 10 curves on each graph, 1612 one curve indicated and labeled for each VCC. The integration time per 1613 point MUST be indicated. 1615 The histograms SHOULD display the peak-to-peak cell delay. There will be 1616 one histogram for each VCC. The x-coordinate SHOULD be the cell delay in 1617 us with at least 256 bins. The y-coordinate SHOULD be the number of 1618 cells observed in each bin. 1620 The results MUST also indicate the packet size in octets, traffic rate 1621 in packets per second, and bearer class as generated by the test device. 1622 The VCC and VPI/VCI values MUST be indicated. The bearer class of the 1623 created VCC MUST also be indicated. 1625 3.2.1.8. Two-point CDV/Mixed Load/Three VCC's 1627 Objective: To determine the SUT variation in cell transfer delay with three 1628 VCC's as defined in RFC 2761 "Terminology for ATM Benchmarking". 1630 Procedure: 1632 1) Set up the SUT and test device using the bi-directional 1633 configuration. 1635 2) Configure the SUT and test device with three VCC's. Each VCC MUST be 1636 defined as a different Bearer class: one CBR, one UBR and one VBR. Each 1637 VCC SHOULD contain one VPI/VCI. The VPI/VCI MUST not be one of the 1638 reserved ATM signaling channels (e.g. [0,5], [0,16]). 1640 3) Send a specific number of IP packets containing timestamps through 1641 the SUT via the defined test VCCs. Each generated VCC stream MUST match 1642 the corresponding VCC Bearer class. All of the VPI/VCI pairs will 1643 generate traffic at the same traffic rate. Since this test is not a 1644 throughput test, the rate should not be greater than 90% of line rate. 1645 The IP PDUs MUST be encapsulated in AAL5. 1647 4) Count the IP packets that are transmitted by the SUT to verify 1648 connectivity and load. If the count on the test device is the same on 1649 the SUT, continue the test; else lower the test device traffic rate 1650 until the counts are the same. 1652 5) Record the packets timestamps at the transmitter and receiver ends of 1653 the test device for all VCC's. 1655 Reporting Format: 1657 The results of the Two-point CDV/Mixed Load/Three VCC test SHOULD be 1658 reported in a form of text, graph, and histogram. 1660 The text results SHOULD display the numerical values of the CDV. The 1661 values given SHOULD include: time period of test in s, test VPI/VCI 1662 value, total number of cells transmitted and received on the given 1663 VPI/VCI during the test in positive integers, maximum and minimum CDV 1664 during the test in us, and peak-to-peak CDV in us. 1666 The graph results SHOULD display the cell delay values. The x- 1667 coordinate SHOULD be the test run time in either seconds, minutes or 1668 days depending on the total length of the test. The x-coordinate time 1669 SHOULD be configurable. The y-coordinate SHOULD be the cell delay in 1670 us. The integration time per point MUST be indicated. 1672 The histogram results SHOULD display the peak-to-peak cell delay. The 1673 x- coordinate SHOULD be the cell delay in us with at least 256 bins. 1674 The y- coordinate SHOULD be the number of cells observed in each bin. 1676 The results MUST also indicate the packet size in octets, traffic rate 1677 in packets per second, and bearer class as generated by the test device. 1678 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 1679 be indicated. The bearer class of the created VCC MUST also be 1680 indicated. 1682 3.2.1.9. Two-point CDV/Mixed Load/Twelve VCCs 1684 Objective: To determine the SUT variation in cell transfer delay with 1685 twelve VCCs as defined in RFC 2761 "Terminology for ATM Benchmarking". 1687 Procedure: 1688 1) Set up the SUT and test device using the bi-directional 1689 configuration. 1691 2) Configure the SUT and test device with twelve VCC's. Each VCC MUST 1692 be defined as one of the Bearer classes for a total of four CBR, four 1693 UBR and four VBR VCC's. Each VCC SHOULD contain one VPI/VCI. The 1694 VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. 1695 [0,5], [0,16]). 1697 3) Send a specific number of IP packets containing timestamps through 1698 the SUT via the defined test VCCs. Each generated VCC stream MUST match 1699 the corresponding VCC Bearer class. All of the VPI/VCI pairs will 1700 generate traffic at the same traffic rate. Since this test is not a 1701 throughput test, the rate should not be greater than 90% of line rate. 1702 The IP PDUs MUST be encapsulated in AAL5. 1704 4) Count the IP packets that are transmitted by the SUT on all VCCs to 1705 verify connectivity and load. If the count on the test device is the 1706 same on the SUT, continue the test; else lower the test device traffic 1707 rate until the counts are the same. 1709 5) Record the packets timestamps at the transmitter and receiver ends of 1710 the test device for all VCCs. 1712 Reporting Format: 1714 The results of the Two-point CDV/Mixed Load/Twelve VCCs test SHOULD be 1715 reported in a form of text, graph, and histograms. 1717 The text results SHOULD display the numerical values of the CDV. The 1718 values given SHOULD include: time period of test in s, test VPI/VCI 1719 values, total number of cells transmitted and received on each VCC 1720 during the test in positive integers, maximum and minimum CDV on each 1721 VCC during the test in us, and peak-to-peak CDV on each VCC in us. 1723 The graph results SHOULD display the cell delay values. The x- 1724 coordinate SHOULD be the test run time in either seconds, minutes or 1725 days depending on the total length of the test. The x-coordinate time 1726 SHOULD be configurable. The y-coordinate SHOULD be the cell delay for 1727 each VCC in ms. There SHOULD be 12 curves on the graph, one curves 1728 indicated and labeled for each VCC. The integration time per point MUST 1729 be indicated. 1731 The histograms SHOULD display the peak-to-peak cell delay. There will be 1732 one histogram for each VCC. The x-coordinate SHOULD be the cell delay 1733 in us with at least 256 bins. The y-coordinate SHOULD be the number of 1734 cells observed in each bin. 1736 The results MUST also indicate the packet size in octets, traffic rate 1737 in packets per second, and bearer class as generated by the test device. 1738 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 1739 be indicated. The bearer class of the created VCC MUST also be 1740 indicated. 1742 3.2.1.10. Two-point CDV/Mixed Load/Maximum VCCs 1744 Objective: To determine the SUT variation in cell transfer delay with the 1745 maximum number VCCs supported on the SUT as defined in RFC 2761 1746 "Terminology for ATM Benchmarking". 1748 Procedure: 1750 1) Set up the SUT and test device using the bi-directional 1751 configuration. 1753 2) Configure the SUT and test device with maximum number of VCCs 1754 supported on the SUT. For example, if the maximum number of VCCs 1755 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. Each 1756 VCC MUST be defined as one of the Bearer classes for a total of (max 1757 VCC/3) CBR, (max VCC/3) UBR and (max VCC/3) VBR VCC's. If the maximum 1758 number of VCC's is not divisible by 3, the total for each bearer class 1759 MUST be within 3 VCC's of each other. The VPI/VCI MUST not be one of 1760 the reserved ATM signaling channels (e.g. [0,5], [0,16]). 1762 3) Send a specific number of IP packets containing timestamps through 1763 the SUT via the defined test VCCs. Each generated VCC stream MUST match 1764 the corresponding VCC Bearer class. All of the VPI/VCI pairs will 1765 generate traffic at the same traffic rate. Since this test is not a 1766 throughput test, the rate should not be greater than 90% of line rate. 1767 The IP PDUs MUST be encapsulated in AAL5. 1769 4) Count the IP packets that are transmitted by the SUT on all VCCs to 1770 verify connectivity and load. If the count on the test device is the 1771 same on the SUT, continue the test; else lower the test device traffic 1772 rate until the counts are the same. 1774 5) Record the packets timestamps at the transmitter and receiver ends of 1775 the test device for all VCCs. 1777 Reporting Format: 1779 The results of the Two-point CDV/Mixed Load/Maximum VCCs test SHOULD be 1780 reported in a form of text, graphs, and histograms. 1782 The text results SHOULD display the numerical values of the CDV. The 1783 values given SHOULD include: time period of test in s, test VPI/VCI 1784 values, total number of cells transmitted and received on each VCC 1785 during the test in positive integers, maximum and minimum CDV on each 1786 VCC during the test in us, and peak-to-peak CDV on each VCC in us. 1788 The graph results SHOULD display the cell delay values. There will be 1789 (Max number of VCCs/10) graphs, with 10 VCCs indicated on each graph. 1790 The x-coordinate SHOULD be the test run time in either seconds, minutes 1791 or days depending on the total length of the test. The x-coordinate time 1792 SHOULD be configurable. The y-coordinate SHOULD be the cell delay for 1793 each VCC in us. There SHOULD be no more than 10 curves on each graph, 1794 one curve indicated and labeled for each VCC. The integration time per 1795 point MUST be indicated. 1797 The histograms SHOULD display the peak-to-peak cell delay. There will be 1798 one histogram for each VCC. The x-coordinate SHOULD be the cell delay in 1799 us with at least 256 bins. The y-coordinate SHOULD be the number of 1800 cells observed in each bin. 1802 The results MUST also indicate the packet size in octets, traffic rate 1803 in packets per second, and bearer class as generated by the test device. 1804 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 1805 be indicated. The bearer class of the created VCC MUST also be 1806 indicated. 1808 3.2.2. Cell Error Ratio (CER) 1810 3.2.2.1. Test Setup 1812 The cell error ratio measurements assume that both the transmitter and 1813 receiver payload information is synchronized. Synchronization MUST be 1814 achieved by supplying a known bit pattern to both the transmitter and 1815 receiver. If this bit pattern is longer than the packet size, the 1816 receiver MUST synchronize with the transmitter before tests can be run. 1818 3.2.2.2. CER/Steady Load/One VCC 1820 Objective: To determine the SUT ratio of errored cells on one VCC in a 1821 transmission in relation to the total cells sent as defined in RFC 2761 1822 "Terminology for ATM Benchmarking". 1824 Procedure: 1826 1) Set up the SUT and test device using the bi-directional 1827 configuration. 1829 2) Configure the SUT and test device with one VCC. The VCC SHOULD 1830 contain one VPI/VCI. The VCC MUST be configured as either a CBR, VBR, or 1831 UBR connection. The VPI/VCI MUST not be one of the reserved ATM 1832 signaling channels (e.g. [0,5], [0,16]). 1834 3) Send a specific number of IP packets containing one of the specified 1835 bit patterns at a constant rate through the SUT via the defined test 1836 VCC. Since this test is not a throughput test, the rate should not be 1837 greater than 90% of line rate. The IP PDUs MUST be encapsulated in 1838 AAL5. 1840 4) Count the IP packets that are transmitted by the SUT to verify 1841 connectivity and load. If the count on the test device is the same on 1842 the SUT, continue the test; else lower the test device traffic rate 1843 until the counts are the same. 1845 5) Record the number of bit errors at the receiver end of the test 1846 device. 1848 Reporting Format: 1850 The results of the CER/Steady Load/One VCC test SHOULD be reported in a 1851 form of text and graph. 1853 The text results SHOULD display the numerical values of the CER. The 1854 values given SHOULD include: time period of test in s, test VPI/VCI 1855 value, total number of cells transmitted and received on the given 1856 VPI/VCI during the test in positive integers, and the CER for the entire 1857 test. 1859 The graph results SHOULD display the cell error ratio values. The x- 1860 coordinate SHOULD be the test run time in either seconds, minutes or 1861 days depending on the total length of the test. The x-coordinate time 1862 SHOULD be configurable. The y-coordinate SHOULD be the CER. The 1863 integration time per point MUST be indicated. 1865 The results MUST also indicate the packet size in octets, traffic rate 1866 in packets per second, and bearer class as generated by the test device. 1867 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 1868 be indicated. The bearer class of the created VCC MUST be indicated. 1869 The generated bit pattern MUST also be indicated. 1871 3.2.2.3. CER/Steady Load/Twelve VCCs 1873 Objective: To determine the SUT ratio of errored cells on twelve VCCs in a 1874 transmission in relation to the total cells sent as defined in RFC 2761 1875 "Terminology for ATM Benchmarking". 1877 Procedure: 1879 1) Set up the SUT and test device using the bi-directional 1880 configuration. 1882 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 1883 12 VCIs. The VCC's MUST be configured as either a CBR, VBR, or UBR 1884 connection. The VPI/VCIs MUST not be one of the reserved ATM signaling 1885 channels (e.g. [0,5], [0,16]). 1887 3) Send a specific number of IP packets containing one of the specified 1888 bit patterns at a constant rate through the SUT via the defined test 1889 VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 1890 rate. Since this test is not a throughput test, the rate should not be 1891 greater than 90% of line rate. The IP PDUs MUST be encapsulated in 1892 AAL5. 1894 4) Count the IP packets that are transmitted by the SUT on all VCCs to 1895 verify connectivity and load. If the count on the test device is the 1896 same on the SUT, continue the test; else lower the test device traffic 1897 rate until the counts are the same. 1899 5) Record the number of bit errors at the receiver end of the test 1900 device for all VCCs. 1902 Reporting Format: 1904 The results of the CER/Steady Load/Twelve VCCs test SHOULD be reported 1905 in a form of text and graph. 1907 The text results SHOULD display the numerical values of the CER. The 1908 values given SHOULD include: time period of test in s, test VPI/VCI 1909 value, total number of cells transmitted and received on the given 1910 VPI/VCI during the test in positive integers, and the CER for the entire 1911 test. 1913 The graph results SHOULD display the cell error ratio values. The x- 1914 coordinate SHOULD be the test run time in either seconds, minutes or 1915 days depending on the total length of the test. The x-coordinate time 1916 SHOULD be configurable. The y-coordinate SHOULD be the CER for each 1917 VCC. There should be 12 curves on the graph, on curve indicated and 1918 labeled for each VCC. The integration time per point MUST be indicated. 1920 The results MUST also indicate the packet size in octets, traffic rate 1921 in packets per second, and bearer class as generated by the test device. 1922 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 1923 be indicated. The bearer class of the created VCC MUST be indicated. The 1924 generated bit pattern MUST also be indicated. 1926 3.2.2.4. CER/Steady Load/Maximum VCCs 1928 Objective: To determine the SUT ratio of errored cells with the maximum 1929 number VCCs supported on the SUT in a transmission in relation to the total 1930 cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". 1932 Procedure: 1934 1) Set up the SUT and test device using the bi-directional 1935 configuration. 1937 2) Configure the SUT and test device with the maximum number of VCCs 1938 supported on the SUT. For example, if the maximum number of VCCs 1939 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The 1940 VCC's MUST be configured as either a CBR, VBR, or UBR connection. The 1941 VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. 1942 [0,5], [0,16]). 1944 3) Send a specific number of IP packets containing one of the specified 1945 bit patterns at a constant rate through the SUT via the defined test 1946 VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 1947 rate. Since this test is not a throughput test, the rate should not be 1948 greater than 90% of line rate. The IP PDUs MUST be encapsulated in 1949 AAL5. 1951 4) Count the IP packets that are transmitted by the SUT on all VCCs to 1952 verify connectivity and load. If the count on the test device is the 1953 same on the SUT, continue the test; else lower the test device traffic 1954 rate until the counts are the same. 1956 5) Record the number of bit errors at the receiver end of the test 1957 device for all VCCs. 1959 Reporting Format: 1961 The results of the CER/Steady Load/Maximum VCCs test SHOULD be reported 1962 in a form of text and graph. 1964 The text results SHOULD display the numerical values of the CER. The 1965 values given SHOULD include: time period of test in s, test VPI/VCI 1966 value, total number of cells transmitted and received on the given 1967 VPI/VCI during the test in positive integers, and the CER for the entire 1968 test. 1970 The graph results SHOULD display the cell error ratio values. There will 1971 be (Max number of VCCs/10) graphs, with 10 VCCs indicated on each graph. 1972 The x-coordinate SHOULD be the test run time in either seconds, minutes 1973 or days depending on the total length of the test. The x-coordinate time 1974 SHOULD be configurable. The y-coordinate SHOULD be the CER for each 1975 VCC. There SHOULD be no more than 10 curves on each graph, one curve 1976 indicated and labeled for each VCC. The integration time per point MUST 1977 be indicated. 1979 The results MUST also indicate the packet size in octets, traffic rate 1980 in packets per second, and bearer class as generated by the test device. 1981 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 1982 be indicated. The bearer class of the created VCC MUST be indicated. The 1983 generated bit pattern MUST also be indicated. 1985 3.2.2.5. CER/Bursty VBR Load/One VCC 1987 Objective: To determine the SUT ratio of errored cells on one VCC in a 1988 transmission in relation to the total cells sent as defined in RFC 2761 1989 "Terminology for ATM Benchmarking". 1991 Procedure: 1993 1) Set up the SUT and test device using the bi-directional 1994 configuration. 1996 2) Configure the SUT and test device with one VCC. The VCC SHOULD 1997 contain one VPI/VCI. The VCC MUST be configured as either a CBR or VBR 1998 connection. The VPI/VCI MUST not be one of the reserved ATM signaling 1999 channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be 2000 configured using one of the specified traffic descriptors. 2002 3) Send a specific number of IP packets containing one of the specified 2003 bit patterns at a specific VBR rate through the SUT via the defined test 2004 VCC. Since this test is not a throughput test, the rate should not be 2005 greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 2007 4) Count the IP packets that are transmitted by the SUT to verify 2008 connectivity and load. If the count on the test device is the same on 2009 the SUT, continue the test; else lower the test device traffic rate 2010 until the counts are the same. 2012 5) Record the number of bit errors at the receiver end of the test 2013 device. 2015 Reporting Format: 2017 The results of the CER/Bursty VBR Load/One VCC test SHOULD be reported 2018 in a form of text and graph. 2020 The text results SHOULD display the numerical values of the CER. The 2021 values given SHOULD include: time period of test in s, test VPI/VCI 2022 value, total number of cells transmitted and received on the given 2023 VPI/VCI during the test in positive integers, and the CER for the entire 2024 test. 2026 The graph results SHOULD display the cell error ratio values. The x- 2027 coordinate SHOULD be the test run time in either seconds, minutes or 2028 days depending on the total length of the test. The x-coordinate time 2029 SHOULD be configurable. The y-coordinate SHOULD be the CER. The 2030 integration time per point MUST be indicated. 2032 The results MUST also indicate the packet size in octets, traffic rate 2033 in packets per second, and bearer class as generated by the test device. 2034 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 2035 be indicated. The bearer class of the created VCC MUST be indicated. The 2036 generated bit pattern MUST also be indicated. 2038 3.2.2.6. CER/Bursty VBR Load/Twelve VCCs 2040 Objective: To determine the SUT ratio of errored cells on twelve VCCs in a 2041 transmission in relation to the total cells sent as defined in RFC 2761 2042 "Terminology for ATM Benchmarking". 2044 Procedure: 2046 1) Set up the SUT and test device using the bi-directional 2047 configuration. 2049 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 2050 12 VCIs. The VCC's MUST be configured as either a CBR or VBR connection. 2051 The VPI/VCIs MUST not be one of the reserved ATM signaling channels 2052 (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using 2053 one of the specified traffic descriptors. 2055 3) Send a specific number of IP packets containing one of the specified 2056 bit patterns at a specific VBR rate through the SUT via the defined test 2057 VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 2058 rate. Since this test is not a throughput test, the rate should not be 2059 greater than 90% of line rate. The PCR, SCR, and MBS must be indicated. 2061 The IP PDUs MUST be encapsulated in AAL5. 2063 4) Count the IP packets that are transmitted by the SUT on all VCCs to 2064 verify connectivity and load. If the count on the test device is the 2065 same on the SUT, continue the test; else lower the test device traffic 2066 rate until the counts are the same. 2068 5) Record the number of bit errors at the receiver end of the test 2069 device for all VCCs. 2071 Reporting Format: 2073 The results of the CER/Bursty VBR Load/Twelve VCCs test SHOULD be 2074 reported in a form of text and graph. 2076 The text results SHOULD display the numerical values of the CER. The 2077 values given SHOULD include: time period of test in s, test VPI/VCI 2078 value, total number of cells transmitted and received on the given 2079 VPI/VCI during the test in positive integers, and the CER for the entire 2080 test. 2082 The graph results SHOULD display the cell error ratio values. The x- 2083 coordinate SHOULD be the test run time in either seconds, minutes or 2084 days depending on the total length of the test. The x-coordinate time 2085 SHOULD be configurable. The y-coordinate SHOULD be the CER for each 2086 VCC. There should be 12 curves on the graph, on curve indicated and 2087 labeled for each VCC. The integration time per point MUST be indicated. 2089 The results MUST also indicate the packet size in octets, traffic rate 2090 in packets per second, and bearer class as generated by the test device. 2091 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 2092 be indicated. The bearer class of the created VCC MUST be indicated. The 2093 generated bit pattern MUST also be indicated. 2095 3.2.2.7. CER/Bursty VBR Load/Maximum VCCs 2097 Objective: To determine the SUT ratio of errored cells with the maximum 2098 number VCCs supported on the SUT in a transmission in relation to the total 2099 cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". 2101 Procedure: 2103 1) Set up the SUT and test device using the bi-directional 2104 configuration. 2106 2) Configure the SUT and test device with the maximum number of VCCs 2107 supported on the SUT. For example, if the maximum number of VCCs 2108 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The 2109 VCC's MUST be configured as either a CBR or VBR connection. The 2110 VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. 2111 [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of 2112 the specified traffic descriptors. 2114 3) Send a specific number of IP packets containing one of the specified 2115 bit patterns at a specific VBR rate through the SUT via the defined test 2116 VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 2117 rate. Since this test is not a throughput test, the rate should not be 2118 greater than 90% of line rate. The IP PDUs MUST be encapsulated in 2119 AAL5. 2121 4) Count the IP packets that are transmitted by the SUT on all VCCs to 2122 verify connectivity and load. If the count on the test device is the 2123 same on the SUT, continue the test; else lower the test device traffic 2124 rate until the counts are the same. 2126 5) Record the number of bit errors at the receiver end of the test 2127 device for all VCCs. 2129 Reporting Format: 2131 The results of the CER/Bursty VBR Load/Maximum VCCs test SHOULD be 2132 reported in a form of text and graph. 2134 The text results SHOULD display the numerical values of the CER. The 2135 values given SHOULD include: time period of test in s, test VPI/VCI 2136 value, total number of cells transmitted and received on the given 2137 VPI/VCI during the test in positive integers, and the CER for the entire 2138 test. 2140 The graph results SHOULD display the cell error ratio values. There will 2141 be (Max number of VCCs/10) graphs, with 10 VCCs indicated on each graph. 2142 The x-coordinate SHOULD be the test run time in either seconds, minutes 2143 or days depending on the total length of the test. The x-coordinate time 2144 SHOULD be configurable. The y-coordinate SHOULD be the CER for each 2145 VCC. There SHOULD be no more than 10 curves on each graph, one curve 2146 indicated and labeled for each VCC. The integration time per point MUST 2147 be indicated. 2149 The results MUST also indicate the packet size in octets, traffic rate 2150 in packets per second, and bearer class as generated by the test device. 2151 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 2152 be indicated. The bearer class of the created VCC MUST be indicated. The 2153 generated bit pattern MUST also be indicated. 2155 3.2.2.5. CER/Bursty UBR Load/One VCC 2157 Objective: To determine the SUT ratio of errored cells on one VCC in a 2158 transmission in relation to the total cells sent as defined in RFC 2761 2159 "Terminology for ATM Benchmarking". 2161 Procedure: 2163 1) Set up the SUT and test device using the bi-directional 2164 configuration. 2166 2) Configure the SUT and test device with one VCC. The VCC SHOULD 2167 contain one VPI/VCI. The VCC MUST be configured as a UBR connection. 2168 The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. 2169 [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of 2170 the specified traffic descriptors. 2172 3) Send a specific number of IP packets containing one of the specified 2173 bit patterns at a specific UBR rate through the SUT via the defined test 2174 VCC. Since this test is not a throughput test, the rate should not be 2175 greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 2177 4) Count the IP packets that are transmitted by the SUT to verify 2178 connectivity and load. If the count on the test device is the same on 2179 the SUT, continue the test; else lower the test device traffic rate 2180 until the counts are the same. 2182 5) Record the number of bit errors at the receiver end of the test 2183 device. 2185 Reporting Format: 2187 The results of the CER/Bursty UBR Load/One VCC test SHOULD be reported 2188 in a form of text and graph. 2190 The text results SHOULD display the numerical values of the CER. The 2191 values given SHOULD include: time period of test in s, test VPI/VCI 2192 value, total number of cells transmitted and received on the given 2193 VPI/VCI during the test in positive integers, and the CER for the entire 2194 test. 2196 The graph results SHOULD display the cell error ratio values. The x- 2197 coordinate SHOULD be the test run time in either seconds, minutes or 2198 days depending on the total length of the test. The x-coordinate time 2199 SHOULD be configurable. The y-coordinate SHOULD be the CER. The 2200 integration time per point MUST be indicated. 2202 The results MUST also indicate the packet size in octets, traffic rate 2203 in packets per second, and bearer class as generated by the test device. 2204 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 2205 be indicated. The bearer class of the created VCC MUST be indicated. The 2206 generated bit pattern MUST also be indicated. 2208 3.2.2.6. CER/Bursty UBR Load/Twelve VCCs 2210 Objective: To determine the SUT ratio of errored cells on twelve VCCs in a 2211 transmission in relation to the total cells sent as defined in RFC 2761 2212 "Terminology for ATM Benchmarking". 2214 Procedure: 2216 1) Set up the SUT and test device using the bi-directional 2217 configuration. 2219 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 2220 12 VCIs. The VCC's MUST be configured as a UBR connection. The VPI/VCIs 2221 MUST not be one of the reserved ATM signaling channels (e.g. [0,5], 2222 [0,16]). The PCR, SCR, and MBS must be configured using one of the 2223 specified traffic descriptors. 2225 3) Send a specific number of IP packets containing one of the specified 2226 bit patterns at a specific UBR rate through the SUT via the defined test 2227 VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 2228 rate. Since this test is not a throughput test, the rate should not be 2229 greater than 90% of line rate. The PCR, SCR, and MBS must be indicated. 2230 The IP PDUs MUST be encapsulated in AAL5. 2232 4) Count the IP packets that are transmitted by the SUT on all VCCs to 2233 verify connectivity and load. If the count on the test device is the 2234 same on the SUT, continue the test; else lower the test device traffic 2235 rate until the counts are the same. 2237 5) Record the number of bit errors at the receiver end of the test 2238 device for all VCCs. 2240 Reporting Format: 2242 The results of the CER/Bursty UBR Load/Twelve VCCs test SHOULD be 2243 reported in a form of text and graph. 2245 The text results SHOULD display the numerical values of the CER. The 2246 values given SHOULD include: time period of test in s, test VPI/VCI 2247 value, total number of cells transmitted and received on the given 2248 VPI/VCI during the test in positive integers, and the CER for the entire 2249 test. 2251 The graph results SHOULD display the cell error ratio values. The x- 2252 coordinate SHOULD be the test run time in either seconds, minutes or 2253 days depending on the total length of the test. The x-coordinate time 2254 SHOULD be configurable. The y-coordinate SHOULD be the CER for each 2255 VCC. There should be 12 curves on the graph, on curve indicated and 2256 labeled for each VCC. The integration time per point MUST be indicated. 2258 The results MUST also indicate the packet size in octets, traffic rate 2259 in packets per second, and bearer class as generated by the test device. 2260 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 2261 be indicated. The bearer class of the created VCC MUST be indicated. The 2262 generated bit pattern MUST also be indicated. 2264 3.2.2.7. CER/Bursty UBR Load/Maximum VCCs 2266 Objective: To determine the SUT ratio of errored cells with the maximum 2267 number VCCs supported on the SUT in a transmission in relation to the total 2268 cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". 2270 Procedure: 2272 1) Set up the SUT and test device using the bi-directional 2273 configuration. 2275 2) Configure the SUT and test device with the maximum number of VCCs 2276 supported on the SUT. For example, if the maximum number of VCCs 2277 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The 2278 VCC's MUST be configured as a UBR connection. The VPI/VCIs MUST not be 2279 one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The 2280 PCR, SCR, and MBS must be configured using one of the specified traffic 2281 descriptors. 2283 3) Send a specific number of IP packets containing one of the specified 2284 bit patterns at a specific UBR rate through the SUT via the defined test 2285 VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 2286 rate. Since this test is not a throughput test, the rate should not be 2287 greater than 90% of line rate. The IP PDUs MUST be encapsulated in 2288 AAL5. 2290 4) Count the IP packets that are transmitted by the SUT on all VCCs to 2291 verify connectivity and load. If the count on the test device is the 2292 same on the SUT, continue the test; else lower the test device traffic 2293 rate until the counts are the same. 2295 5) Record the number of bit errors at the receiver end of the test 2296 device for all VCCs. 2298 Reporting Format: 2300 The results of the CER/Bursty UBR Load/Maximum VCCs test SHOULD be 2301 reported in a form of text and graph. 2303 The text results SHOULD display the numerical values of the CER. The 2304 values given SHOULD include: time period of test in s, test VPI/VCI 2305 value, total number of cells transmitted and received on the given 2306 VPI/VCI during the test in positive integers, and the CER for the entire 2307 test. 2309 The graph results SHOULD display the cell error ratio values. There will 2310 be (Max number of VCCs/10) graphs, with 10 VCCs indicated on each graph. 2311 The x-coordinate SHOULD be the test run time in either seconds, minutes 2312 or days depending on the total length of the test. The x-coordinate time 2313 SHOULD be configurable. The y-coordinate SHOULD be the CER for each 2314 VCC. There SHOULD be no more than 10 curves on each graph, one curve 2315 indicated and labeled for each VCC. The integration time per point MUST 2316 be indicated. 2318 The results MUST also indicate the packet size in octets, traffic rate 2319 in packets per second, and bearer class as generated by the test device. 2320 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 2321 be indicated. The bearer class of the created VCC MUST be indicated. The 2322 generated bit pattern MUST also be indicated. 2324 3.2.1.8. CER/Mixed Load/Three VCC's 2326 Objective: To determine the SUT ratio of errored cells with the maximum 2327 number VCCs supported on the SUT in a transmission in relation to the total 2328 cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". 2330 Procedure: 2332 1) Set up the SUT and test device using the bi-directional 2333 configuration. 2335 2) Configure the SUT and test device with three VCC's. Each VCC MUST be 2336 defined as a different Bearer class; one CBR, one UBR and one VBR. Each 2337 VCC SHOULD contain one VPI/VCI. The VPI/VCI MUST not be one of the 2338 reserved ATM signaling channels (e.g. [0,5], [0,16]). 2340 3) Send a specific number of IP packets containing one of the specified 2341 bit patterns through the SUT via the defined test VCCs. Each generated 2342 VCC stream MUST match the corresponding VCC Bearer class. All of the 2343 VPI/VCI pairs will generate traffic at the same traffic rate. Since 2344 this test is not a throughput test, the rate should not be greater than 2345 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 2347 4) Count the IP packets that are transmitted by the SUT to verify 2348 connectivity and load. If the count on the test device is the same on 2349 the SUT, continue the test; else lower the test device traffic rate 2350 until the counts are the same. 2352 5) Record the number of bit errors at the receiver end of the test 2353 device for all VCCs. 2355 Reporting Format: 2357 The results of the CER/Bursty Mixed Load/Three VCCs test SHOULD be 2358 reported in a form of text and graph. 2360 The text results SHOULD display the numerical values of the CER. The 2361 values given SHOULD include: time period of test in s, test VPI/VCI 2362 value, total number of cells transmitted and received on the given 2363 VPI/VCI during the test in positive integers, and the CER for the entire 2364 test. 2366 The graph results SHOULD display the cell error ratio values. The x- 2367 coordinate SHOULD be the test run time in either seconds, minutes or 2368 days depending on the total length of the test. The x-coordinate time 2369 SHOULD be configurable. The y-coordinate SHOULD be the CER for each 2370 VCC. There should be 12 curves on the graph, on curve indicated and 2371 labeled for each VCC. The integration time per point MUST be indicated. 2373 The results MUST also indicate the packet size in octets, traffic rate 2374 in packets per second, and bearer class as generated by the test device. 2375 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 2376 be indicated. The bearer class of the created VCC MUST be indicated. The 2377 generated bit pattern MUST also be indicated. 2379 3.2.1.9. CER/Mixed Load/Twelve VCCs 2381 Objective: To determine the SUT ratio of errored cells with the maximum 2382 number VCCs supported on the SUT in a transmission in relation to the total 2383 cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". 2385 Procedure: 2386 1) Set up the SUT and test device using the bi-directional 2387 configuration. 2389 2) Configure the SUT and test device with twelve VCC's. Each VCC MUST 2390 be defined as one of the Bearer classes for a total of four CBR, four 2391 UBR and four VBR VCC's. Each VCC SHOULD contain one VPI/VCI. The 2392 VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. 2393 [0,5], [0,16]). 2395 3) Send a specific number of IP packets containing one of the specified 2396 bit patterns through the SUT via the defined test VCCs. Each generated 2397 VCC stream MUST match the corresponding VCC Bearer class. All of the 2398 VPI/VCI pairs will generate traffic at the same traffic rate. Since 2399 this test is not a throughput test, the rate should not be greater than 2400 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 2402 4) Count the IP packets that are transmitted by the SUT on all VCCs to 2403 verify connectivity and load. If the count on the test device is the 2404 same on the SUT, continue the test; else lower the test device traffic 2405 rate until the counts are the same. 2407 5) Record the number of bit errors at the receiver end of the test 2408 device for all VCCs. 2410 Reporting Format: 2412 The results of the CER/Bursty Mixed Load/Twelve VCCs test SHOULD be 2413 reported in a form of text and graph. 2415 The text results SHOULD display the numerical values of the CER. The 2416 values given SHOULD include: time period of test in s, test VPI/VCI 2417 value, total number of cells transmitted and received on the given 2418 VPI/VCI during the test in positive integers, and the CER for the entire 2419 test. 2421 The graph results SHOULD display the cell error ratio values. The x- 2422 coordinate SHOULD be the test run time in either seconds, minutes or 2423 days depending on the total length of the test. The x-coordinate time 2424 SHOULD be configurable. The y-coordinate SHOULD be the CER for each 2425 VCC. There should be 12 curves on the graph, on curve indicated and 2426 labeled for each VCC. The integration time per point MUST be indicated. 2428 The results MUST also indicate the packet size in octets, traffic rate 2429 in packets per second, and bearer class as generated by the test device. 2430 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 2431 be indicated. The bearer class of the created VCC MUST be indicated. The 2432 generated bit pattern MUST also be indicated. 2434 3.2.1.10. CER/Mixed Load/Maximum VCCs 2436 Objective: To determine the SUT ratio of errored cells with the maximum 2437 number VCCs supported on the SUT in a transmission in relation to the total 2438 cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". 2440 Procedure: 2442 1) Set up the SUT and test device using the bi-directional 2443 configuration. 2445 2) Configure the SUT and test device with maximum number of VCCs 2446 supported on the SUT. For example, if the maximum number of VCCs 2447 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. Each 2448 VCC MUST be defined as one of the Bearer classes for a total of (max 2449 VCC/3) CBR, (max VCC/3) UBR and (max VCC/3) VBR VCC's. The VPI/VCI MUST 2450 not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). 2452 3) Send a specific number of IP packets containing one of the specified 2453 bit patterns through the SUT via the defined test VCCs. Each generated 2454 VCC stream MUST match the corresponding VCC Bearer class. All of the 2455 VPI/VCI pairs will generate traffic at the same traffic rate. Since 2456 this test is not a throughput test, the rate should not be greater than 2457 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 2459 4) Count the IP packets that are transmitted by the SUT on all VCCs to 2460 verify connectivity and load. If the count on the test device is the 2461 same on the SUT, continue the test; else lower the test device traffic 2462 rate until the counts are the same. 2464 5) Record the number of bit errors at the receiver end of the test 2465 device for all VCCs. 2467 Reporting Format: 2469 The results of the CER/Bursty Mixed Load/Maximum VCCs test SHOULD be 2470 reported in a form of text and graph. 2472 The text results SHOULD display the numerical values of the CER. The 2473 values given SHOULD include: time period of test in s, test VPI/VCI 2474 value, total number of cells transmitted and received on the given 2475 VPI/VCI during the test in positive integers, and the CER for the entire 2476 test. 2478 The graph results SHOULD display the cell error ratio values. There will 2479 be (Max number of VCCs/10) graphs, with 10 VCCs indicated on each graph. 2480 The x-coordinate SHOULD be the test run time in either seconds, minutes 2481 or days depending on the total length of the test. The x-coordinate time 2482 SHOULD be configurable. The y-coordinate SHOULD be the CER for each 2483 VCC. There SHOULD be no more than 10 curves on each graph, one curve 2484 indicated and labeled for each VCC. The integration time per point MUST 2485 be indicated. 2487 The results MUST also indicate the packet size in octets, traffic rate 2488 in packets per second, and bearer class as generated by the test device. 2489 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 2490 be indicated. The bearer class of the created VCC MUST be indicated. The 2491 generated bit pattern MUST also be indicated. 2493 3.2.3. Cell Loss Ratio (CLR) 2495 3.2.3.1. CLR/Steady Load/One VCC 2497 Objective: To determine the SUT ratio of lost cells on one VCC in a 2498 transmission in relation to the total cells sent as defined in RFC 2761 2499 "Terminology for ATM Benchmarking". 2501 Procedure: 2503 1) Set up the SUT and test device using the bi-directional 2504 configuration. 2506 2) Configure the SUT and test device with one VCC. The VCC SHOULD 2507 contain one VPI/VCI. The VCC MUST be configured as either a CBR, VBR, or 2508 UBR connection. The VPI/VCI MUST not be one of the reserved ATM 2509 signaling channels (e.g. [0,5], [0,16]). 2511 3) Send a specific number of IP packets at a specific constant rate 2512 through the SUT via the defined test VCC. Since this test is not a 2513 throughput test, the rate should not be greater than 90% of line rate. 2514 The IP PDUs MUST be encapsulated in AAL5. 2516 4) Count the IP packets that are transmitted by the SUT to verify 2517 connectivity and load. If the count on the test device is the same on 2518 the SUT, continue the test; else lower the test device traffic rate 2519 until the counts are the same. 2521 5) Record the number of cells transmitted and received on the test 2522 device. 2524 Reporting Format: 2526 The results of the CLR/Steady Load/One VCC test SHOULD be reported in a 2527 form of text and graph. 2529 The text results SHOULD display the numerical values of the CLR. The 2530 values given SHOULD include: time period of test in s, test VPI/VCI 2531 value, total number of cells transmitted and received on the given 2532 VPI/VCI during the test in positive integers, and the CLR for the entire 2533 test. 2535 The graph results SHOULD display the Cell Loss ratio values. The x- 2536 coordinate SHOULD be the test run time in either seconds, minutes or 2537 days depending on the total length of the test. The x-coordinate time 2538 SHOULD be configurable. The y-coordinate SHOULD be the CLR. The 2539 integration time per point MUST be indicated. 2541 The results MUST also indicate the packet size in octets, traffic rate 2542 in packets per second, and bearer class as generated by the test device. 2543 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 2544 be indicated. The bearer class of the created VCC MUST also be 2545 indicated. 2547 3.2.3.2. CLR/Steady Load/Twelve VCCs 2549 Objective: To determine the SUT ratio of lost cells on twelve VCCs in a 2550 transmission in relation to the total cells sent as defined in RFC 2761 2551 "Terminology for ATM Benchmarking". 2553 Procedure: 2555 1) Set up the SUT and test device using the bi-directional 2556 configuration. 2558 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 2559 12 VCIs. The VCC's MUST be configured as either a CBR, VBR, or UBR 2560 connection. The VPI/VCIs MUST not be one of the reserved ATM signaling 2561 channels (e.g. [0,5], [0,16]). 2563 3) Send a specific number of IP packets at a specific constant rate 2564 through the SUT via the defined test VCCs. All of the VPI/VCI pairs will 2565 generate traffic at the same traffic rate. Since this test is not a 2566 throughput test, the rate should not be greater than 90% of line rate. 2568 The IP PDUs MUST be encapsulated in AAL5. 2570 4) Count the IP packets that are transmitted by the SUT on all VCCs to 2571 verify connectivity and load. If the count on the test device is the 2572 same on the SUT, continue the test; else lower the test device traffic 2573 rate until the counts are the same. 2575 5) Record the number of cells transmitted and received per VCC on the 2576 test device. 2578 Reporting Format: 2580 The results of the CLR/Steady Load/Twelve VCCs test SHOULD be reported 2581 in a form of text and graph. 2583 The text results SHOULD display the numerical values of the CLR. The 2584 values given SHOULD include: time period of test in s, test VPI/VCI 2585 value, total number of cells transmitted and received on the given 2586 VPI/VCI during the test in positive integers, and the CLR for the entire 2587 test. 2589 The graph results SHOULD display the Cell Loss ratio values. The x- 2590 coordinate SHOULD be the test run time in either seconds, minutes or 2591 days depending on the total length of the test. The x-coordinate time 2592 SHOULD be configurable. The y-coordinate SHOULD be the CLR for each VCC. 2593 There should be 12 curves on the graph, on curve indicated and labeled 2594 for each VCC. The integration time per point MUST be indicated. 2596 The results MUST also indicate the packet size in octets, traffic rate 2597 in packets per second, and bearer class as generated by the test device. 2598 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 2599 be indicated. The bearer class of the created VCC MUST also be 2600 indicated. 2602 3.2.3.3. CLR/Steady Load/Maximum VCCs 2604 Objective: To determine the SUT ratio of lost cells with the maximum number 2605 VCCs supported on the SUT in a transmission in relation to the total cells 2606 sent as defined in RFC 2761 "Terminology for ATM Benchmarking". 2608 Procedure: 2610 1) Set up the SUT and test device using the bi-directional 2611 configuration. 2613 2) Configure the SUT and test device with the maximum number of VCCs 2614 supported on the SUT. For example, if the maximum number of VCCs 2615 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The 2616 VCC's MUST be configured as either a CBR, VBR, or UBR connection. The 2617 VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. 2618 [0,5], [0,16]). 2620 3) Send a specific number of IP packets at a specific constant rate 2621 through the SUT via the defined test VCCs. All of the VPI/VCI pairs will 2622 generate traffic at the same traffic rate. Since this test is not a 2623 throughput test, the rate should not be greater than 90% of line rate. 2624 The IP PDUs MUST be encapsulated in AAL5. 2626 4) Count the IP packets that are transmitted by the SUT on all VCCs to 2627 verify connectivity and load. If the count on the test device is the 2628 same on the SUT, continue the test; else lower the test device traffic 2629 rate until the counts are the same. 2631 5) Record the number of cells transmitted and received per VCC on the 2632 test device. 2634 Reporting Format: 2636 The results of the CLR/Steady Load/Maximum VCCs test SHOULD be reported 2637 in a form of text and graph. 2639 The text results SHOULD display the numerical values of the CLR. The 2640 values given SHOULD include: time period of test in s, test VPI/VCI 2641 value, total number of cells transmitted and received on the given 2642 VPI/VCI during the test in positive integers, and the CLR for the entire 2643 test. 2645 The graph results SHOULD display the Cell Loss ratio values. There will 2646 be (Max number of VCCs/10) graphs, with 10 VCCs indicated on each graph. 2647 The x-coordinate SHOULD be the test run time in either seconds, minutes 2648 or days depending on the total length of the test. The x-coordinate time 2649 SHOULD be configurable. The y-coordinate SHOULD be the CLR for each 2650 VCC. There SHOULD be no more than 10 curves on each graph, one curve 2651 indicated and labeled for each VCC. The integration time per point MUST 2652 be indicated. 2654 The results MUST also indicate the packet size in octets, traffic rate 2655 in packets per second, and bearer class as generated by the test device. 2656 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 2657 be indicated. The bearer class of the created VCC MUST also be 2658 indicated. 2660 3.2.3.4. CLR/Bursty VBR Load/One VCC 2662 Objective: To determine the SUT ratio of lost cells on one VCC in a 2663 transmission in relation to the total cells sent as defined in RFC 2761 2664 "Terminology for ATM Benchmarking". 2666 Procedure: 2668 1) Set up the SUT and test device using the bi-directional 2669 configuration. 2671 2) Configure the SUT and test device with one VCC. The VCC SHOULD 2672 contain one VPI/VCI. The VCC MUST be configured as either a CBR or VBR 2673 connection. The VPI/VCI MUST not be one of the reserved ATM signaling 2674 channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be 2675 configured using one of the specified traffic descriptors. 2677 3) Send a specific number of IP packets containing one of the specified 2678 bit patterns at a specific rate through the SUT via the defined test 2679 VCC. Since this test is not a throughput test, the rate should not be 2680 greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 2682 4) Count the IP packets that are transmitted by the SUT to verify 2683 connectivity and load. If the count on the test device is the same on 2684 the SUT, continue the test; else lower the test device traffic rate 2685 until the counts are the same. 2687 5) Record the number of cells transmitted and received on the test 2688 device. 2690 Reporting Format: 2692 The results of the CLR/Bursty VBR Load/One VCC test SHOULD be reported 2693 in a form of text and graph. 2695 The text results SHOULD display the numerical values of the CLR. The 2696 values given SHOULD include: time period of test in s, test VPI/VCI 2697 value, total number of cells transmitted and received on the given 2698 VPI/VCI during the test in positive integers, and the CLR for the entire 2699 test. 2701 The graph results SHOULD display the Cell Loss ratio values. The x- 2702 coordinate SHOULD be the test run time in either seconds, minutes or 2703 days depending on the total length of the test. The x-coordinate time 2704 SHOULD be configurable. The y-coordinate SHOULD be the CLR. The 2705 integration time per point MUST be indicated. 2707 The results MUST also indicate the packet size in octets, traffic rate 2708 in packets per second, and bearer class as generated by the test device. 2709 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 2710 be indicated. The bearer class of the created VCC MUST also be 2711 indicated. 2713 3.2.3.5. CLR/Bursty VBR Load/Twelve VCCs 2715 Objective: To determine the SUT ratio of lost cells on twelve VCCs in a 2716 transmission in relation to the total cells sent as defined in RFC 2761 2717 "Terminology for ATM Benchmarking". 2719 Procedure: 2721 1) Set up the SUT and test device using the bi-directional 2722 configuration. 2724 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 2725 12 VCIs. The VCC MUST be configured as either a CBR or VBR connection. 2726 The VPI/VCIs MUST not be one of the reserved ATM signaling channels 2727 (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using 2728 one of the specified traffic descriptors. 2730 3) Send a specific number of IP packets containing one of the specified 2731 bit patterns at a specific rate through the SUT via the defined test 2732 VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 2733 rate. Since this test is not a throughput test, the rate should not be 2734 greater than 90% of line rate. The PCR, SCR, and MBS must be indicated. 2736 The IP PDUs MUST be encapsulated in AAL5. 2738 4) Count the IP packets that are transmitted by the SUT on all VCCs to 2739 verify connectivity and load. If the count on the test device is the 2740 same on the SUT, continue the test; else lower the test device traffic 2741 rate until the counts are the same. 2743 5) Record the number of cells transmitted and received per VCC on the 2744 test device. 2746 Reporting Format: 2748 The results of the CLR/Bursty VBR Load/Twelve VCCs test SHOULD be 2749 reported in a form of text and graph. 2751 The text results SHOULD display the numerical values of the CLR. The 2752 values given SHOULD include: time period of test in s, test VPI/VCI 2753 value, total number of cells transmitted and received on the given 2754 VPI/VCI during the test in positive integers, and the CLR for the entire 2755 test. 2757 The graph results SHOULD display the Cell Loss ratio values. The x- 2758 coordinate SHOULD be the test run time in either seconds, minutes or 2759 days depending on the total length of the test. The x-coordinate time 2760 SHOULD be configurable. The y-coordinate SHOULD be the CLR for each 2761 VCC. There should be 12 curves on the graph, on curve indicated and 2762 labeled for each VCC. The integration time per point MUST be indicated. 2764 The results MUST also indicate the packet size in octets, traffic rate 2765 in packets per second, and bearer class as generated by the test device. 2766 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 2767 be indicated. The bearer class of the created VCC MUST also be 2768 indicated. 2770 3.2.3.6. CLR/Bursty VBR Load/Maximum VCCs 2772 Objective: To determine the SUT ratio of lost cells with the maximum number 2773 VCCs supported on the SUT in a transmission in relation to the total cells 2774 sent as defined in RFC 2761 "Terminology for ATM Benchmarking". 2776 Procedure: 2778 1) Set up the SUT and test device using the bi-directional 2779 configuration. 2781 2) Configure the SUT and test device with the maximum number of VCCs 2782 supported on the SUT. For example, if the maximum number of VCCs 2783 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The 2784 VCC MUST be configured as either a CBR or VBR connection. The VPI/VCIs 2785 MUST not be one of the reserved ATM signaling channels (e.g. [0,5], 2786 [0,16]). The PCR, SCR, and MBS must be configured using one of the 2787 specified traffic descriptors. 2789 3) Send a specific number of IP packets containing one of the specified 2790 bit patterns at a specific rate through the SUT via the defined test 2791 VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 2792 rate. Since this test is not a throughput test, the rate should not be 2793 greater than 90% of line rate. The IP PDUs MUST be encapsulated in 2794 AAL5. 2796 4) Count the IP packets that are transmitted by the SUT on all VCCs to 2797 verify connectivity and load. If the count on the test device is the 2798 same on the SUT, continue the test; else lower the test device traffic 2799 rate until the counts are the same. 2801 5) Record the number of cells transmitted and received per VCC on the 2802 test device. 2804 Reporting Format: 2806 The results of the CLR/Bursty VBR Load/Maximum VCCs test SHOULD be 2807 reported in a form of text and graph. 2809 The text results SHOULD display the numerical values of the CLR. The 2810 values given SHOULD include: time period of test in s, test VPI/VCI 2811 value, total number of cells transmitted and received on the given 2812 VPI/VCI during the test in positive integers, and the CLR for the entire 2813 test. 2815 The graph results SHOULD display the Cell Loss ratio values. There will 2816 be (Max number of VCCs/10) graphs, with 10 VCCs indicated on each graph. 2817 The x-coordinate SHOULD be the test run time in either seconds, minutes 2818 or days depending on the total length of the test. The x-coordinate time 2819 SHOULD be configurable. The y-coordinate SHOULD be the CLR for each 2820 VCC. There SHOULD be no more than 10 curves on each graph, one curve 2821 indicated and labeled for each VCC. The integration time per point MUST 2822 be indicated. 2824 The results MUST also indicate the packet size in octets, traffic rate 2825 in packets per second, and bearer class as generated by the test device. 2826 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 2827 be indicated. The bearer class of the created VCC MUST also be 2828 indicated. 2830 3.2.3.4. CLR/Bursty UBR Load/One VCC 2832 Objective: To determine the SUT ratio of lost cells on one VCC in a 2833 transmission in relation to the total cells sent as defined in RFC 2761 2834 "Terminology for ATM Benchmarking". 2836 Procedure: 2838 1) Set up the SUT and test device using the bi-directional 2839 configuration. 2841 2) Configure the SUT and test device with one VCC. The VCC SHOULD 2842 contain one VPI/VCI. The VCC MUST be configured as a UBR connection. The 2843 VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. 2844 [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of 2845 the specified traffic descriptors. 2847 3) Send a specific number of IP packets containing one of the specified 2848 bit patterns at a specific rate through the SUT via the defined test 2849 VCC. Since this test is not a throughput test, the rate should not be 2850 greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 2852 4) Count the IP packets that are transmitted by the SUT to verify 2853 connectivity and load. If the count on the test device is the same on 2854 the SUT, continue the test; else lower the test device traffic rate 2855 until the counts are the same. 2857 5) Record the number of cells transmitted and received on the test 2858 device. 2860 Reporting Format: 2862 The results of the CLR/Bursty UBR Load/One VCC test SHOULD be reported 2863 in a form of text and graph. 2865 The text results SHOULD display the numerical values of the CLR. The 2866 values given SHOULD include: time period of test in s, test VPI/VCI 2867 value, total number of cells transmitted and received on the given 2868 VPI/VCI during the test in positive integers, and the CLR for the entire 2869 test. 2871 The graph results SHOULD display the Cell Loss ratio values. The x- 2872 coordinate SHOULD be the test run time in either seconds, minutes or 2873 days depending on the total length of the test. The x-coordinate time 2874 SHOULD be configurable. The y-coordinate SHOULD be the CLR. The 2875 integration time per point MUST be indicated. 2877 The results MUST also indicate the packet size in octets, traffic rate 2878 in packets per second, and bearer class as generated by the test device. 2879 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 2880 be indicated. The bearer class of the created VCC MUST also be 2881 indicated. 2883 3.2.3.5. CLR/Bursty UBR Load/Twelve VCCs 2885 Objective: To determine the SUT ratio of lost cells on twelve VCCs in a 2886 transmission in relation to the total cells sent as defined in RFC 2761 2887 "Terminology for ATM Benchmarking". 2889 Procedure: 2891 1) Set up the SUT and test device using the bi-directional 2892 configuration. 2894 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 2895 12 VCIs. The VCC MUST be configured as a UBR connection. The VPI/VCIs 2896 MUST not be one of the reserved ATM signaling channels (e.g. [0,5], 2897 [0,16]). The PCR, SCR, and MBS must be configured using one of the 2898 specified traffic descriptors. 2900 3) Send a specific number of IP packets containing one of the specified 2901 bit patterns at a specific rate through the SUT via the defined test 2902 VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 2903 rate. Since this test is not a throughput test, the rate should not be 2904 greater than 90% of line rate. The PCR, SCR, and MBS must be indicated. 2905 The IP PDUs MUST be encapsulated in AAL5. 2907 4) Count the IP packets that are transmitted by the SUT on all VCCs to 2908 verify connectivity and load. If the count on the test device is the 2909 same on the SUT, continue the test; else lower the test device traffic 2910 rate until the counts are the same. 2912 5) Record the number of cells transmitted and received per VCC on the 2913 test device. 2915 Reporting Format: 2917 The results of the CLR/Bursty UBR Load/Twelve VCCs test SHOULD be 2918 reported in a form of text and graph. 2920 The text results SHOULD display the numerical values of the CLR. The 2921 values given SHOULD include: time period of test in s, test VPI/VCI 2922 value, total number of cells transmitted and received on the given 2923 VPI/VCI during the test in positive integers, and the CLR for the entire 2924 test. 2926 The graph results SHOULD display the Cell Loss ratio values. The x- 2927 coordinate SHOULD be the test run time in either seconds, minutes or 2928 days depending on the total length of the test. The x-coordinate time 2929 SHOULD be configurable. The y-coordinate SHOULD be the CLR for each 2930 VCC. There should be 12 curves on the graph, on curve indicated and 2931 labeled for each VCC. The integration time per point MUST be indicated. 2933 The results MUST also indicate the packet size in octets, traffic rate 2934 in packets per second, and bearer class as generated by the test device. 2935 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 2936 be indicated. The bearer class of the created VCC MUST also be 2937 indicated. 2939 3.2.3.6. CLR/Bursty UBR Load/Maximum VCCs 2941 Objective: To determine the SUT ratio of lost cells with the maximum number 2942 VCCs supported on the SUT in a transmission in relation to the total cells 2943 sent as defined in RFC 2761 "Terminology for ATM Benchmarking". 2945 Procedure: 2947 1) Set up the SUT and test device using the bi-directional 2948 configuration. 2950 2) Configure the SUT and test device with the maximum number of VCCs 2951 supported on the SUT. For example, if the maximum number of VCCs 2952 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The 2953 VCC MUST be configured as a UBR connection. The VPI/VCIs MUST not be one 2954 of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, 2955 SCR, and MBS must be configured using one of the specified traffic 2956 descriptors. 2958 3) Send a specific number of IP packets containing one of the specified 2959 bit patterns at a specific rate through the SUT via the defined test 2960 VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 2961 rate. Since this test is not a throughput test, the rate should not be 2962 greater than 90% of line rate. The IP PDUs MUST be encapsulated in 2963 AAL5. 2965 4) Count the IP packets that are transmitted by the SUT on all VCCs to 2966 verify connectivity and load. If the count on the test device is the 2967 same on the SUT, continue the test; else lower the test device traffic 2968 rate until the counts are the same. 2970 5) Record the number of cells transmitted and received per VCC on the 2971 test device. 2973 Reporting Format: 2975 The results of the CLR/Bursty UBR Load/Maximum VCCs test SHOULD be 2976 reported in a form of text and graph. 2978 The text results SHOULD display the numerical values of the CLR. The 2979 values given SHOULD include: time period of test in s, test VPI/VCI 2980 value, total number of cells transmitted and received on the given 2981 VPI/VCI during the test in positive integers, and the CLR for the entire 2982 test. 2984 The graph results SHOULD display the Cell Loss ratio values. There will 2985 be (Max number of VCCs/10) graphs, with 10 VCCs indicated on each graph. 2986 The x-coordinate SHOULD be the test run time in either seconds, minutes 2987 or days depending on the total length of the test. The x-coordinate time 2988 SHOULD be configurable. The y-coordinate SHOULD be the CLR for each 2989 VCC. There SHOULD be no more than 10 curves on each graph, one curve 2990 indicated and labeled for each VCC. The integration time per point MUST 2991 be indicated. 2993 The results MUST also indicate the packet size in octets, traffic rate 2994 in packets per second, and bearer class as generated by the test device. 2995 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 2996 be indicated. The bearer class of the created VCC MUST also be 2997 indicated. 2999 3.2.3.4. CLR/Bursty Mixed Load/Three VCC 3001 Objective: To determine the SUT ratio of lost cells on one VCC in a 3002 transmission in relation to the total cells sent as defined in RFC 2761 3003 "Terminology for ATM Benchmarking". 3005 Procedure: 3007 1) Set up the SUT and test device using the bi-directional 3008 configuration. 3010 2) Configure the SUT and test device with three VCC's. Each VCC MUST be 3011 defined as a different Bearer class; one CBR, one UBR and one VBR. Each 3012 VCC SHOULD contain one VPI/VCI. The VPI/VCI MUST not be one of the 3013 reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and 3014 MBS must be configured using one of the specified traffic descriptors. 3016 3) Send a specific number of IP packets containing one of the specified 3017 bit patterns through the SUT via the defined test VCCs. Each generated 3018 VCC stream MUST match the corresponding VCC Bearer class. All of the 3019 VPI/VCI pairs will generate traffic at the same traffic rate. Since 3020 this test is not a throughput test, the rate should not be greater than 3021 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 3023 4) Count the IP packets that are transmitted by the SUT to verify 3024 connectivity and load. If the count on the test device is the same on 3025 the SUT, continue the test; else lower the test device traffic rate 3026 until the counts are the same. 3028 5) Record the number of cells transmitted and received per VCC on the 3029 test device. 3031 Reporting Format: 3033 The results of the CLR/Bursty Mixed Load/Three VCC test SHOULD be 3034 reported in in a form of text and graph. 3036 The text results SHOULD display the numerical values of the CLR. The 3037 values given SHOULD include: time period of test in s, test VPI/VCI 3038 value, total number of cells transmitted and received on the given 3039 VPI/VCI during the test in positive integers, and the CLR for the entire 3040 test. 3042 The graph results SHOULD display the Cell Loss ratio values. The x- 3043 coordinate SHOULD be the test run time in either seconds, minutes or 3044 days depending on the total length of the test. The x-coordinate time 3045 SHOULD be configurable. The y-coordinate SHOULD be the CLR for each 3046 VCC. There should be 12 curves on the graph, on curve indicated and 3047 labeled for each VCC. The integration time per point MUST be indicated. 3049 The results MUST also indicate the packet size in octets, traffic rate 3050 in packets per second, and bearer class as generated by the test device. 3051 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 3052 be indicated. The bearer class of the created VCC MUST also be 3053 indicated. 3055 3.2.3.5. CLR/Bursty Mixed Load/Twelve VCCs 3057 Objective: To determine the SUT ratio of lost cells on twelve VCCs in a 3058 transmission in relation to the total cells sent as defined in RFC 2761 3059 "Terminology for ATM Benchmarking". 3061 Procedure: 3063 1) Set up the SUT and test device using the bi-directional 3064 configuration. 3066 2) Configure the SUT and test device with twelve VCC's. Each VCC MUST 3067 be defined as one of the Bearer classes for a total of four CBR, four 3068 UBR and four VBR VCC's. Each VCC SHOULD contain one VPI/VCI. The 3069 VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. 3070 [0,5], [0,16]). 3072 3) Send a specific number of IP packets containing one of the specified 3073 bit patterns through the SUT via the defined test VCCs. Each generated 3074 VCC stream MUST match the corresponding VCC Bearer class. All of the 3075 VPI/VCI pairs will generate traffic at the same traffic rate. Since 3076 this test is not a throughput test, the rate should not be greater than 3077 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 3079 4) Count the IP packets that are transmitted by the SUT on all VCCs to 3080 verify connectivity and load. If the count on the test device is the 3081 same on the SUT, continue the test; else lower the test device traffic 3082 rate until the counts are the same. 3084 5) Record the number of cells transmitted and received per VCC on the 3085 test device. 3087 Reporting Format: 3089 The results of the CLR/Bursty Mixed Load/Twelve VCCs test SHOULD be 3090 reported in a form of text and graph. 3092 The text results SHOULD display the numerical values of the CLR. The 3093 values given SHOULD include: time period of test in s, test VPI/VCI 3094 value, total number of cells transmitted and received on the given 3095 VPI/VCI during the test in positive integers, and the CLR for the entire 3096 test. 3098 The graph results SHOULD display the Cell Loss ratio values. The x- 3099 coordinate SHOULD be the test run time in either seconds, minutes or 3100 days depending on the total length of the test. The x-coordinate time 3101 SHOULD be configurable. The y-coordinate SHOULD be the CLR for each 3102 VCC. There should be 12 curves on the graph, on curve indicated and 3103 labeled for each VCC. The integration time per point MUST be indicated. 3105 The results MUST also indicate the packet size in octets, traffic rate 3106 in packets per second, and bearer class as generated by the test device. 3107 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 3108 be indicated. The bearer class of the created VCC MUST also be 3109 indicated. 3111 3.2.3.6. CLR/Bursty Mixed Load/Maximum VCCs 3113 Objective: To determine the SUT ratio of lost cells with the maximum number 3114 VCCs supported on the SUT in a transmission in relation to the total cells 3115 sent as defined in RFC 2761 "Terminology for ATM Benchmarking". 3117 Procedure: 3119 1) Set up the SUT and test device using the bi-directional 3120 configuration. 3122 2) Configure the SUT and test device with maximum number of VCCs 3123 supported on the SUT. For example, if the maximum number of VCCs 3124 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. Each 3125 VCC MUST be defined as one of the Bearer classes for a total of (max 3126 VCC/3) CBR, (max VCC/3) UBR and (max VCC/3) VBR VCC's. The VPI/VCI MUST 3127 not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). 3129 3) Send a specific number of IP packets containing one of the specified 3130 bit patterns through the SUT via the defined test VCCs. Each generated 3131 VCC stream MUST match the corresponding VCC Bearer class. All of the 3132 VPI/VCI pairs will generate traffic at the same traffic rate. Since 3133 this test is not a throughput test, the rate should not be greater than 3134 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 3136 4) Count the IP packets that are transmitted by the SUT on all VCCs to 3137 verify connectivity and load. If the count on the test device is the 3138 same on the SUT, continue the test; else lower the test device traffic 3139 rate until the counts are the same. 3141 5) Record the number of cells transmitted and received per VCC on the 3142 test device. 3144 Reporting Format: 3146 The results of the CLR/Bursty Mixed Load/Maximum VCCs test SHOULD be 3147 reported in a form of text and graph. 3149 The text results SHOULD display the numerical values of the CLR. The 3150 values given SHOULD include: time period of test in s, test VPI/VCI 3151 value, total number of cells transmitted and received on the given 3152 VPI/VCI during the test in positive integers, and the CLR for the entire 3153 test. 3155 The graph results SHOULD display the Cell Loss ratio values. There will 3156 be (Max number of VCCs/10) graphs, with 10 VCCs indicated on each graph. 3158 The x-coordinate SHOULD be the test run time in either seconds, minutes 3159 or days depending on the total length of the test. The x-coordinate time 3160 SHOULD be configurable. The y-coordinate SHOULD be the CLR for each 3161 VCC. There SHOULD be no more than 10 curves on each graph, one curve 3162 indicated and labeled for each VCC. The integration time per point MUST 3163 be indicated. 3165 The results MUST also indicate the packet size in octets, traffic rate 3166 in packets per second, and bearer class as generated by the test device. 3167 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 3168 be indicated. The bearer class of the created VCC MUST also be 3169 indicated. 3171 3.2.4. Cell Misinsertion Rate (CMR) 3173 3.2.4.1. CMR/Steady Load/One VCC 3175 Objective: To determine the SUT ratio of cell misinsertion on one VCC in a 3176 transmission in relation to the total cells sent as defined in RFC 2761 3177 "Terminology for ATM Benchmarking". 3179 Procedure: 3181 1) Set up the SUT and test device using the bi-directional 3182 configuration. 3184 2) Configure the SUT and test device with one VCC. The VCC MUST be 3185 configured as either a CBR, VBR, or UBR connection. The VCC SHOULD 3186 contain one VPI/VCI. The VPI/VCI MUST not be one of the reserved ATM 3187 signaling channels (e.g. [0,5], [0,16]). 3189 3) Send a specific number of IP packets at a specific constant rate 3190 through the SUT via the defined test VCC. Since this test is not a 3191 throughput test, the rate should not be greater than 90% of line rate. 3192 The IP PDUs MUST be encapsulated in AAL5. 3194 4) Count the IP packets that are transmitted by the SUT to verify 3195 connectivity and load. If the count on the test device is the same on 3196 the SUT, continue the test; else lower the test device traffic rate 3197 until the counts are the same. 3199 5) Record the number of cell misinsertion errors at the receiver end of 3200 the test device. 3202 Reporting Format: 3204 The results of the CMR/Steady Load/One VCC test SHOULD be reported in a 3205 form of text and graph. 3207 The text results SHOULD display the numerical values of the CMR. The 3208 values given SHOULD include: time period of test in s, test VPI/VCI 3209 value, total number of cells transmitted and received on the given 3210 VPI/VCI during the test in positive integers, and the CMR for the entire 3211 test. 3213 The graph results SHOULD display the Cell misinsertion rate values. The 3214 x-coordinate SHOULD be the test run time in either seconds, minutes or 3215 days depending on the total length of the test. The x-coordinate time 3216 SHOULD be configurable. The y-coordinate SHOULD be the CMR. The 3217 integration time per point MUST be indicated. 3219 The results MUST also indicate the packet size in octets, traffic rate 3220 in packets per second, and bearer class as generated by the test device. 3221 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 3222 be indicated. The bearer class of the created VCC MUST also be 3223 indicated. 3225 3.2.4.2. CMR/Steady Load/Twelve VCCs 3227 Objective: To determine the SUT rate of misinserted cells on twelve VCCs in 3228 a transmission in relation to the total cells sent as defined in RFC 2761 3229 "Terminology for ATM Benchmarking". 3231 Procedure: 3233 1) Set up the SUT and test device using the bi-directional 3234 configuration. 3236 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 3237 12 VCIs. The VCC's MUST be configured as either a CBR, VBR, or UBR 3238 connection. The VPI/VCIs MUST not be one of the reserved ATM signaling 3239 channels (e.g. [0,5], [0,16]). 3241 3) Send a specific number of IP packets at a specific constant rate 3242 through the SUT via the defined test VCCs. All of the VPI/VCI pairs will 3243 generate traffic at the same traffic rate. Since this test is not a 3244 throughput test, the rate should not be greater than 90% of line rate. 3245 The IP PDUs MUST be encapsulated in AAL5. 3247 4) Count the IP packets that are transmitted by the SUT on all VCCs to 3248 verify connectivity and load. If the count on the test device is the 3249 same on the SUT, continue the test; else lower the test device traffic 3250 rate until the counts are the same. 3252 5) Record the number of cell misinsertion errors at the receiver end of 3253 the test device per VCC. 3255 Reporting Format: 3257 The results of the CMR/Steady Load/Twelve VCCs test SHOULD be reported 3258 in a form of text and graph. 3260 The text results SHOULD display the numerical values of the CMR. The 3261 values given SHOULD include: time period of test in s, test VPI/VCI 3262 value, total number of cells transmitted and received on the given 3263 VPI/VCI during the test in positive integers, and the CMR for the entire 3264 test. 3266 The graph results SHOULD display the Cell misinsertion rate values. The 3267 x-coordinate SHOULD be the test run time in either seconds, minutes or 3268 days depending on the total length of the test. The x-coordinate time 3269 SHOULD be configurable. The y-coordinate SHOULD be the CMR for each VCC. 3270 There should be 12 curves on the graph, on curve indicated and labeled 3271 for each VCC. The integration time per point MUST be indicated. 3273 The results MUST also indicate the packet size in octets, traffic rate 3274 in packets per second, and bearer class as generated by the test device. 3275 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 3276 be indicated. The bearer class of the created VCC MUST also be 3277 indicated. 3279 3.2.4.3. CMR/Steady Load/Maximum VCCs 3281 Objective: To determine the SUT rate of misinserted cells with the maximum 3282 number VCCs supported on the SUT in a transmission in relation to the total 3283 cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". 3285 Procedure: 3287 1) Set up the SUT and test device using the bi-directional 3288 configuration. 3290 2) Configure the SUT and test device with the maximum number of VCCs 3291 supported on the SUT. For example, if the maximum number of VCCs 3292 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The 3293 VCC's MUST be configured as either a CBR, VBR, or UBR connection. The 3294 VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. 3295 [0,5], [0,16]). 3297 3) Send a specific number of IP packets at a specific constant rate 3298 through the SUT via the defined test VCCs. All of the VPI/VCI pairs will 3299 generate traffic at the same traffic rate. Since this test is not a 3300 throughput test, the rate should not be greater than 90% of line rate. 3301 The IP PDUs MUST be encapsulated in AAL5. 3303 4) Count the IP packets that are transmitted by the SUT on all VCCs to 3304 verify connectivity and load. If the count on the test device is the 3305 same on the SUT, continue the test; else lower the test device traffic 3306 rate until the counts are the same. 3308 5) Record the number of cell misinsertion errors at the receiver end of 3309 the test device per VCC. 3311 Reporting Format: 3313 The results of the CMR/Steady Load/Maximum VCCs test SHOULD be reported 3314 in a form of text and graph. 3316 The text results SHOULD display the numerical values of the CMR. The 3317 values given SHOULD include: time period of test in s, test VPI/VCI 3318 value, total number of cells transmitted and received on the given 3319 VPI/VCI during the test in positive integers, and the CMR for the entire 3320 test. 3322 The graph results SHOULD display the Cell misinsertion rate values. 3323 There will be (Max number of VCCs/10) graphs, with 10 VCCs indicated on 3324 each graph. The x-coordinate SHOULD be the test run time in either 3325 seconds, minutes or days depending on the total length of the test. The 3326 x- coordinate time SHOULD be configurable. The y-coordinate SHOULD be 3327 the CMR for each VCC. There SHOULD be no more than 10 curves on each 3328 graph, one curve indicated and labeled for each VCC. The integration 3329 time per point MUST be indicated. 3331 The results MUST also indicate the packet size in octets, traffic rate 3332 in packets per second, and bearer class as generated by the test device. 3333 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 3334 be indicated. The bearer class of the created VCC MUST also be 3335 indicated. 3337 3.2.4.4. CMR/Bursty VBR Load/One VCC 3339 Objective: To determine the SUT rate of misinserted cells on one VCC in a 3340 transmission in relation to the total cells sent as defined in RFC 2761 3341 "Terminology for ATM Benchmarking". 3343 Procedure: 3345 1) Set up the SUT and test device using the bi-directional 3346 configuration. 3348 2) Configure the SUT and test device with one VCC. The VCC SHOULD 3349 contain one VPI/VCI. The VCC MUST be configured as either a CBR or VBR 3350 connection. The VPI/VCI MUST not be one of the reserved ATM signaling 3351 channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be 3352 configured using one of the specified traffic descriptors. 3354 3) Send a specific number of IP packets containing one of the specified 3355 bit patterns at a specific rate through the SUT via the defined test 3356 VCC. Since this test is not a throughput test, the rate should not be 3357 greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 3359 4) Count the IP packets that are transmitted by the SUT to verify 3360 connectivity and load. If the count on the test device is the same on 3361 the SUT, continue the test; else lower the test device traffic rate 3362 until the counts are the same. 3364 5) Record the number of cell misinsertion errors at the receiver end of 3365 the test device. 3367 Reporting Format: 3369 The results of the CMR/Bursty VBR Load/One VCC test SHOULD be reported 3370 in a form of text and graph. 3372 The text results SHOULD display the numerical values of the CMR. The 3373 values given SHOULD include: time period of test in s, test VPI/VCI 3374 value, total number of cells transmitted and received on the given 3375 VPI/VCI during the test in positive integers, and the CMR for the entire 3376 test. 3378 The graph results SHOULD display the Cell misinsertion rate values. The 3379 x-coordinate SHOULD be the test run time in either seconds, minutes or 3380 days depending on the total length of the test. The x-coordinate time 3381 SHOULD be configurable. The y-coordinate SHOULD be the CMR. The 3382 integration time per point MUST be indicated. 3384 The results MUST also indicate the packet size in octets, traffic rate 3385 in packets per second, and bearer class as generated by the test device. 3386 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 3387 be indicated. The bearer class of the created VCC MUST also be 3388 indicated. 3390 3.2.4.5. CMR/Bursty VBR Load/Twelve VCCs 3392 Objective: To determine the SUT rate of misinserted cells on twelve VCCs in 3393 a transmission in relation to the total cells sent as defined in RFC 2761 3394 "Terminology for ATM Benchmarking". 3396 Procedure: 3398 1) Set up the SUT and test device using the bi-directional 3399 configuration. 3401 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 3402 12 VCIs. The VCC's MUST be configured as either a CBR or VBR connection. 3403 The VPI/VCIs MUST not be one of the reserved ATM signaling channels 3404 (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using 3405 one of the specified traffic descriptors. 3407 3) Send a specific number of IP packets containing one of the specified 3408 bit patterns at a specific rate through the SUT via the defined test 3409 VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 3410 rate. Since this test is not a throughput test, the rate should not be 3411 greater than 90% of line rate. The PCR, SCR, and MBS must be indicated. 3412 The IP PDUs MUST be encapsulated in AAL5. 3414 4) Count the IP packets that are transmitted by the SUT on all VCCs to 3415 verify connectivity and load. If the count on the test device is the 3416 same on the SUT, continue the test; else lower the test device traffic 3417 rate until the counts are the same. 3419 5) Record the number of cell misinsertion errors at the receiver end of 3420 the test device per VCC. 3422 Reporting Format: 3424 The results of the CMR/Bursty VBR Load/Twelve VCCs test SHOULD be 3425 reported in a form of text and graph. 3427 The text results SHOULD display the numerical values of the CMR. The 3428 values given SHOULD include: time period of test in s, test VPI/VCI 3429 value, total number of cells transmitted and received on the given 3430 VPI/VCI during the test in positive integers, and the CMR for the entire 3431 test. 3433 The graph results SHOULD display the Cell misinsertion rate values. The 3434 x-coordinate SHOULD be the test run time in either seconds, minutes or 3435 days depending on the total length of the test. The x-coordinate time 3436 SHOULD be configurable. The y-coordinate SHOULD be the CMR for each 3437 VCC. There should be 12 curves on the graph, on curve indicated and 3438 labeled for each VCC. The integration time per point MUST be indicated. 3440 The results MUST also indicate the packet size in octets, traffic rate 3441 in packets per second, and bearer class as generated by the test device. 3442 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 3443 be indicated. The bearer class of the created VCC MUST also be 3444 indicated. 3446 3.2.4.6. CMR/Bursty VBR Load/Maximum VCCs 3448 Objective: To determine the SUT rate of misinserted cells with the maximum 3449 number VCCs supported on the SUT in a transmission in relation to the total 3450 cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". 3452 Procedure: 3454 1) Set up the SUT and test device using the bi-directional 3455 configuration. 3457 2) Configure the SUT and test device with the maximum number of VCCs 3458 supported on the SUT. For example, if the maximum number of VCCs 3459 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The 3460 VCC's MUST be configured as either a CBR or VBR connection. The VPI/VCIs 3461 MUST not be one of the reserved ATM signaling channels (e.g. [0,5], 3462 [0,16]). The PCR, SCR, and MBS must be configured using one of the 3463 specified traffic descriptors. 3465 3) Send a specific number of IP packets containing one of the specified 3466 bit patterns at a specific rate through the SUT via the defined test 3467 VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 3468 rate. Since this test is not a throughput test, the rate should not be 3469 greater than 90% of line rate. The IP PDUs MUST be encapsulated in 3470 AAL5. 3472 4) Count the IP packets that are transmitted by the SUT on all VCCs to 3473 verify connectivity and load. If the count on the test device is the 3474 same on the SUT, continue the test; else lower the test device traffic 3475 rate until the counts are the same. 3477 5) Record the number of cell misinsertion errors at the receiver end of 3478 the test device per VCC. 3480 Reporting Format: 3482 The results of the CMR/Bursty VBR Load/Maximum VCCs test SHOULD be 3483 reported in a form of text and graph. 3485 The text results SHOULD display the numerical values of the CMR. The 3486 values given SHOULD include: time period of test in s, test VPI/VCI 3487 value, total number of cells transmitted and received on the given 3488 VPI/VCI during the test in positive integers, and the CMR for the entire 3489 test. 3491 The graph results SHOULD display the Cell misinsertion rate values. 3492 There will be (Max number of VCCs/10) graphs, with 10 VCCs indicated on 3493 each graph. The x-coordinate SHOULD be the test run time in either 3494 seconds, minutes or days depending on the total length of the test. The 3495 x- coordinate time SHOULD be configurable. The y-coordinate SHOULD be 3496 the CMR for each VCC. There SHOULD be no more than 10 curves on each 3497 graph, one curve indicated and labeled for each VCC. The integration 3498 time per point MUST be indicated. 3500 The results MUST also indicate the packet size in octets, traffic rate 3501 in packets per second, and bearer class as generated by the test device. 3502 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 3503 be indicated. The bearer class of the created VCC MUST also be 3504 indicated. 3506 3.2.4.4. CMR/Bursty UBR Load/One VCC 3508 Objective: To determine the SUT rate of misinserted cells on one VCC in a 3509 transmission in relation to the total cells sent as defined in RFC 2761 3510 "Terminology for ATM Benchmarking". 3512 Procedure: 3514 1) Set up the SUT and test device using the bi-directional 3515 configuration. 3517 2) Configure the SUT and test device with one VCC. The VCC SHOULD 3518 contain one VPI/VCI. The VCC MUST be configured as a UBR connection. The 3519 VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. 3520 [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of 3521 the specified traffic descriptors. 3523 3) Send a specific number of IP packets containing one of the specified 3524 bit patterns at a specific rate through the SUT via the defined test 3525 VCC. Since this test is not a throughput test, the rate should not be 3526 greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 3528 4) Count the IP packets that are transmitted by the SUT to verify 3529 connectivity and load. If the count on the test device is the same on 3530 the SUT, continue the test; else lower the test device traffic rate 3531 until the counts are the same. 3533 5) Record the number of cell misinsertion errors at the receiver end of 3534 the test device. 3536 Reporting Format: 3538 The results of the CMR/Bursty UBR Load/One VCC test SHOULD be reported 3539 in a form of text and graph. 3541 The text results SHOULD display the numerical values of the CMR. The 3542 values given SHOULD include: time period of test in s, test VPI/VCI 3543 value, total number of cells transmitted and received on the given 3544 VPI/VCI during the test in positive integers, and the CMR for the entire 3545 test. 3547 The graph results SHOULD display the Cell misinsertion rate values. The 3548 x-coordinate SHOULD be the test run time in either seconds, minutes or 3549 days depending on the total length of the test. The x-coordinate time 3550 SHOULD be configurable. The y-coordinate SHOULD be the CMR. The 3551 integration time per point MUST be indicated. 3553 The results MUST also indicate the packet size in octets, traffic rate 3554 in packets per second, and bearer class as generated by the test device. 3555 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 3556 be indicated. The bearer class of the created VCC MUST also be 3557 indicated. 3559 3.2.4.5. CMR/Bursty UBR Load/Twelve VCCs 3561 Objective: To determine the SUT rate of misinserted cells on twelve VCCs in 3562 a transmission in relation to the total cells sent as defined in RFC 2761 3563 "Terminology for ATM Benchmarking". 3565 Procedure: 3567 1) Set up the SUT and test device using the bi-directional 3568 configuration. 3570 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 3571 12 VCIs. The VCC's MUST be configured as a UBR connection. The VPI/VCIs 3572 MUST not be one of the reserved ATM signaling channels (e.g. [0,5], 3573 [0,16]). The PCR, SCR, and MBS must be configured using one of the 3574 specified traffic descriptors. 3576 3) Send a specific number of IP packets containing one of the specified 3577 bit patterns at a specific rate through the SUT via the defined test 3578 VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 3579 rate. Since this test is not a throughput test, the rate should not be 3580 greater than 90% of line rate. The PCR, SCR, and MBS must be indicated. 3581 The IP PDUs MUST be encapsulated in AAL5. 3583 4) Count the IP packets that are transmitted by the SUT on all VCCs to 3584 verify connectivity and load. If the count on the test device is the 3585 same on the SUT, continue the test; else lower the test device traffic 3586 rate until the counts are the same. 3588 5) Record the number of cell misinsertion errors at the receiver end of 3589 the test device per VCC. 3591 Reporting Format: 3593 The results of the CMR/Bursty UBR Load/Twelve VCCs test SHOULD be 3594 reported in a form of text and graph. 3596 The text results SHOULD display the numerical values of the CMR. The 3597 values given SHOULD include: time period of test in s, test VPI/VCI 3598 value, total number of cells transmitted and received on the given 3599 VPI/VCI during the test in positive integers, and the CMR for the entire 3600 test. 3602 The graph results SHOULD display the Cell misinsertion rate values. The 3603 x-coordinate SHOULD be the test run time in either seconds, minutes or 3604 days depending on the total length of the test. The x-coordinate time 3605 SHOULD be configurable. The y-coordinate SHOULD be the CMR for each 3606 VCC. There should be 12 curves on the graph, on curve indicated and 3607 labeled for each VCC. The integration time per point MUST be indicated. 3609 The results MUST also indicate the packet size in octets, traffic rate 3610 in packets per second, and bearer class as generated by the test device. 3611 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 3612 be indicated. The bearer class of the created VCC MUST also be 3613 indicated. 3615 3.2.4.6. CMR/Bursty UBR Load/Maximum VCCs 3617 Objective: To determine the SUT rate of misinserted cells with the maximum 3618 number VCCs supported on the SUT in a transmission in relation to the total 3619 cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". 3621 Procedure: 3623 1) Set up the SUT and test device using the bi-directional 3624 configuration. 3626 2) Configure the SUT and test device with the maximum number of VCCs 3627 supported on the SUT. For example, if the maximum number of VCCs 3628 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The 3629 VCC's MUST be configured as a UBR connection. The VPI/VCIs MUST not be 3630 one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The 3631 PCR, SCR, and MBS must be configured using one of the specified traffic 3632 descriptors. 3634 3) Send a specific number of IP packets containing one of the specified 3635 bit patterns at a specific rate through the SUT via the defined test 3636 VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 3637 rate. Since this test is not a throughput test, the rate should not be 3638 greater than 90% of line rate. The IP PDUs MUST be encapsulated in 3639 AAL5. 3641 4) Count the IP packets that are transmitted by the SUT on all VCCs to 3642 verify connectivity and load. If the count on the test device is the 3643 same on the SUT, continue the test; else lower the test device traffic 3644 rate until the counts are the same. 3646 5) Record the number of cell misinsertion errors at the receiver end of 3647 the test device per VCC. 3649 Reporting Format: 3651 The results of the CMR/Bursty UBR Load/Maximum VCCs test SHOULD be 3652 reported in a form of text and graph. 3654 The text results SHOULD display the numerical values of the CMR. The 3655 values given SHOULD include: time period of test in s, test VPI/VCI 3656 value, total number of cells transmitted and received on the given 3657 VPI/VCI during the test in positive integers, and the CMR for the entire 3658 test. 3660 The graph results SHOULD display the Cell misinsertion rate values. 3661 There will be (Max number of VCCs/10) graphs, with 10 VCCs indicated on 3662 each graph. The x-coordinate SHOULD be the test run time in either 3663 seconds, minutes or days depending on the total length of the test. The 3664 x- coordinate time SHOULD be configurable. The y-coordinate SHOULD be 3665 the CMR for each VCC. There SHOULD be no more than 10 curves on each 3666 graph, one curve indicated and labeled for each VCC. The integration 3667 time per point MUST be indicated. 3669 The results MUST also indicate the packet size in octets, traffic rate 3670 in packets per second, and bearer class as generated by the test device. 3671 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 3672 be indicated. The bearer class of the created VCC MUST also be 3673 indicated. 3675 3.2.4.4. CMR/Bursty Mixed Load/Three VCC 3677 Objective: To determine the SUT rate of misinserted cells on one VCC in a 3678 transmission in relation to the total cells sent as defined in RFC 2761 3679 "Terminology for ATM Benchmarking". 3681 Procedure: 3683 1) Set up the SUT and test device using the bi-directional 3684 configuration. 3686 2) Configure the SUT and test device with three VCC's. Each VCC MUST be 3687 defined as a different Bearer class; one CBR, one UBR and one VBR. Each 3688 VCC SHOULD contain one VPI/VCI. The VPI/VCI MUST not be one of the 3689 reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and 3690 MBS must be configured using one of the specified traffic descriptors. 3692 3) Send a specific number of IP packets containing one of the specified 3693 bit patterns through the SUT via the defined test VCCs. Each generated 3694 VCC stream MUST match the corresponding VCC Bearer class. All of the 3695 VPI/VCI pairs will generate traffic at the same traffic rate. Since 3696 this test is not a throughput test, the rate should not be greater than 3697 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 3699 4) Count the IP packets that are transmitted by the SUT to verify 3700 connectivity and load. If the count on the test device is the same on 3701 the SUT, continue the test; else lower the test device traffic rate 3702 until the counts are the same. 3704 5) Record the number of cell misinsertion errors at the receiver end of 3705 the test device. 3707 Reporting Format: 3709 The results of the CMR/Bursty Mixed Load/Three VCC test SHOULD be 3710 reported reported in a form of text and graph. 3712 The text results SHOULD display the numerical values of the CMR. The 3713 values given SHOULD include: time period of test in s, test VPI/VCI 3714 value, total number of cells transmitted and received on the given 3715 VPI/VCI during the test in positive integers, and the CMR for the entire 3716 test. 3718 The graph results SHOULD display the Cell misinsertion rate values. The 3719 x-coordinate SHOULD be the test run time in either seconds, minutes or 3720 days depending on the total length of the test. The x-coordinate time 3721 SHOULD be configurable. The y-coordinate SHOULD be the CMR for each 3722 VCC. There should be 12 curves on the graph, on curve indicated and 3723 labeled for each VCC. The integration time per point MUST be indicated. 3725 The results MUST also indicate the packet size in octets, traffic rate 3726 in packets per second, and bearer class as generated by the test device. 3727 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 3728 be indicated. The bearer class of the created VCC MUST also be 3729 indicated. 3731 3.2.4.5. CMR/Bursty Mixed Load/Twelve VCCs 3733 Objective: To determine the SUT rate of misinserted cells on twelve VCCs in 3734 a transmission in relation to the total cells sent as defined in RFC 2761 3735 "Terminology for ATM Benchmarking". 3737 Procedure: 3739 1) Set up the SUT and test device using the bi-directional 3740 configuration. 3742 2) Configure the SUT and test device with twelve VCC's. Each VCC MUST 3743 be defined as one of the Bearer classes for a total of four CBR, four 3744 UBR and four VBR VCC's. Each VCC SHOULD contain one VPI/VCI. The 3745 VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. 3746 [0,5], [0,16]). 3748 3) Send a specific number of IP packets containing one of the specified 3749 bit patterns through the SUT via the defined test VCCs. Each generated 3750 VCC stream MUST match the corresponding VCC Bearer class. All of the 3751 VPI/VCI pairs will generate traffic at the same traffic rate. Since 3752 this test is not a throughput test, the rate should not be greater than 3753 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 3755 4) Count the IP packets that are transmitted by the SUT on all VCCs to 3756 verify connectivity and load. If the count on the test device is the 3757 same on the SUT, continue the test; else lower the test device traffic 3758 rate until the counts are the same. 3760 5) Record the number of cell misinsertion errors at the receiver end of 3761 the test device per VCC. 3763 Reporting Format: 3765 The results of the CMR/Bursty Mixed Load/Twelve VCCs test SHOULD be 3766 reported in a form of text and graph. 3768 The text results SHOULD display the numerical values of the CMR. The 3769 values given SHOULD include: time period of test in s, test VPI/VCI 3770 value, total number of cells transmitted and received on the given 3771 VPI/VCI during the test in positive integers, and the CMR for the entire 3772 test. 3774 The graph results SHOULD display the Cell misinsertion rate values. The 3775 x-coordinate SHOULD be the test run time in either seconds, minutes or 3776 days depending on the total length of the test. The x-coordinate time 3777 SHOULD be configurable. The y-coordinate SHOULD be the CMR for each 3778 VCC. There should be 12 curves on the graph, on curve indicated and 3779 labeled for each VCC. The integration time per point MUST be indicated. 3781 The results MUST also indicate the packet size in octets, traffic rate 3782 in packets per second, and bearer class as generated by the test device. 3783 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 3784 be indicated. The bearer class of the created VCC MUST also be 3785 indicated. 3787 3.2.4.6. CMR/Bursty Mixed Load/Maximum VCCs 3789 Objective: To determine the SUT rate of misinserted cells with the maximum 3790 number VCCs supported on the SUT in a transmission in relation to the total 3791 cells sent as defined in RFC 2761 "Terminology for ATM Benchmarking". 3793 Procedure: 3795 1) Set up the SUT and test device using the bi-directional 3796 configuration. 3798 2) Configure the SUT and test device with maximum number of VCCs 3799 supported on the SUT. For example, if the maximum number of VCCs 3800 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. Each 3801 VCC MUST be defined as one of the Bearer classes for a total of (max 3802 VCC/3) CBR, (max VCC/3) UBR and (max VCC/3) VBR VCC's. The VPI/VCI MUST 3803 not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). 3805 3) Send a specific number of IP packets containing one of the specified 3806 bit patterns through the SUT via the defined test VCCs. Each generated 3807 VCC stream MUST match the corresponding VCC Bearer class. All of the 3808 VPI/VCI pairs will generate traffic at the same traffic rate. Since 3809 this test is not a throughput test, the rate should not be greater than 3810 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 3812 4) Count the IP packets that are transmitted by the SUT on all VCCs to 3813 verify connectivity and load. If the count on the test device is the 3814 same on the SUT, continue the test; else lower the test device traffic 3815 rate until the counts are the same. 3817 5) Record the number of cell misinsertion errors at the receiver end of 3818 the test device per VCC. 3820 Reporting Format: 3822 The results of the CMR/Bursty Mixed Load/Maximum VCCs test SHOULD be 3823 reported in a form of text and graph. 3825 The text results SHOULD display the numerical values of the CMR. The 3826 values given SHOULD include: time period of test in s, test VPI/VCI 3827 value, total number of cells transmitted and received on the given 3828 VPI/VCI during the test in positive integers, and the CMR for the entire 3829 test. 3831 The graph results SHOULD display the Cell misinsertion rate values. 3832 There will be (Max number of VCCs/10) graphs, with 10 VCCs indicated on 3833 each graph. The x-coordinate SHOULD be the test run time in either 3834 seconds, minutes or days depending on the total length of the test. The 3835 x- coordinate time SHOULD be configurable. The y-coordinate SHOULD be 3836 the CMR for each VCC. There SHOULD be no more than 10 curves on each 3837 graph, one curve indicated and labeled for each VCC. The integration 3838 time per point MUST be indicated. 3840 The results MUST also indicate the packet size in octets, traffic rate 3841 in packets per second, and bearer class as generated by the test device. 3842 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 3843 be indicated. The bearer class of the created VCC MUST also be 3844 indicated. 3846 3.2.5. Cell Rate Margin (CRM) 3848 To Be Determined 3850 3.2.3. CRC Error Ratio (CRC-ER) 3852 3.2.3.1. CRC-ER/Steady Load/One VCC 3854 Objective: To determine the SUT ratio of CRC errors on one VCC in a 3855 transmission in relation to the total cells sent as defined in RFC 2761 3856 "Terminology for ATM Benchmarking". 3858 Procedure: 3860 1) Set up the SUT and test device using the bi-directional 3861 configuration. 3863 2) Configure the SUT and test device with one VCC. The VCC SHOULD 3864 contain one VPI/VCI. The VCC MUST be configured as either a CBR, VBR, or 3865 UBR connection. The VPI/VCI MUST not be one of the reserved ATM 3866 signaling channels (e.g. [0,5], [0,16]). 3868 3) Send a specific number of IP packets at a specific constant rate 3869 through the SUT via the defined test VCC. Since this test is not a 3870 throughput test, the rate should not be greater than 90% of line rate. 3871 The IP PDUs MUST be encapsulated in AAL5. 3873 4) Count the IP packets that are transmitted by the SUT to verify 3874 connectivity and load. If the count on the test device is the same on 3875 the SUT, continue the test; else lower the test device traffic rate 3876 until the counts are the same. 3878 5) Record the number of CRC errored cells received on the test device. 3880 Reporting Format: 3882 The results of the CRC-ER/Steady Load/One VCC test SHOULD be reported in 3883 a form of text and graph. 3885 The text results SHOULD display the numerical values of the CRC-ER. The 3886 values given SHOULD include: time period of test in s, test VPI/VCI 3887 value, total number of cells transmitted and received on the given 3888 VPI/VCI during the test in positive integers, and the CRC-ER for the 3889 entire test. 3891 The graph results SHOULD display the CRC Error ratio values. The x- 3892 coordinate SHOULD be the test run time in either seconds, minutes or 3893 days depending on the total length of the test. The x-coordinate time 3894 SHOULD be configurable. The y-coordinate SHOULD be the CRC-ER. The 3895 integration time per point MUST be indicated. 3897 The results MUST also indicate the packet size in octets, traffic rate 3898 in packets per second, and bearer class as generated by the test device. 3899 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 3900 be indicated. The bearer class of the created VCC MUST also be 3901 indicated. 3903 3.2.3.2. CRC-ER/Steady Load/Twelve VCCs 3905 Objective: To determine the SUT ratio of lost cells on twelve VCCs in a 3906 transmission in relation to the total cells sent as defined in RFC 2761 3907 "Terminology for ATM Benchmarking". 3909 Procedure: 3911 1) Set up the SUT and test device using the bi-directional 3912 configuration. 3914 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 3915 12 VCIs. The VCC's MUST be configured as either a CBR, VBR, or UBR 3916 connection. The VPI/VCIs MUST not be one of the reserved ATM signaling 3917 channels (e.g. [0,5], [0,16]). 3919 3) Send a specific number of IP packets at a specific constant rate 3920 through the SUT via the defined test VCCs. All of the VPI/VCI pairs will 3921 generate traffic at the same traffic rate. Since this test is not a 3922 throughput test, the rate should not be greater than 90% of line rate. 3923 The IP PDUs MUST be encapsulated in AAL5. 3925 4) Count the IP packets that are transmitted by the SUT on all VCCs to 3926 verify connectivity and load. If the count on the test device is the 3927 same on the SUT, continue the test; else lower the test device traffic 3928 rate until the counts are the same. 3930 5) Record the number of CRC errored cells received per VCC on the test 3931 device. 3933 Reporting Format: 3935 The results of the CRC-ER/Steady Load/Twelve VCCs test SHOULD be 3936 reported in a form of text and graph. 3938 The text results SHOULD display the numerical values of the CRC-ER. The 3939 values given SHOULD include: time period of test in s, test VPI/VCI 3940 value, total number of cells transmitted and received on the given 3941 VPI/VCI during the test in positive integers, and the CRC-ER for the 3942 entire test. 3944 The graph results SHOULD display the CRC Error ratio values. The x- 3945 coordinate SHOULD be the test run time in either seconds, minutes or 3946 days depending on the total length of the test. The x-coordinate time 3947 SHOULD be configurable. The y-coordinate SHOULD be the CRC-ER for each 3948 VCC. There should be 12 curves on the graph, on curve indicated and 3949 labeled for each VCC. The integration time per point MUST be indicated. 3951 The results MUST also indicate the packet size in octets, traffic rate 3952 in packets per second, and bearer class as generated by the test device. 3953 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 3954 be indicated. The bearer class of the created VCC MUST also be 3955 indicated. 3957 3.2.3.3. CRC-ER/Steady Load/Maximum VCCs 3959 Objective: To determine the SUT ratio of lost cells with the maximum number 3960 VCCs supported on the SUT in a transmission in relation to the total cells 3961 sent as defined in RFC 2761 "Terminology for ATM Benchmarking". 3963 Procedure: 3965 1) Set up the SUT and test device using the bi-directional 3966 configuration. 3968 2) Configure the SUT and test device with the maximum number of VCCs 3969 supported on the SUT. For example, if the maximum number of VCCs 3970 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The 3971 VCC's MUST be configured as either a CBR, VBR, or UBR connection. The 3972 VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. 3973 [0,5], [0,16]). 3975 3) Send a specific number of IP packets at a specific constant rate 3976 through the SUT via the defined test VCCs. All of the VPI/VCI pairs will 3977 generate traffic at the same traffic rate. Since this test is not a 3978 throughput test, the rate should not be greater than 90% of line rate. 3979 The IP PDUs MUST be encapsulated in AAL5. 3981 4) Count the IP packets that are transmitted by the SUT on all VCCs to 3982 verify connectivity and load. If the count on the test device is the 3983 same on the SUT, continue the test; else lower the test device traffic 3984 rate until the counts are the same. 3986 5) Record the number of CRC errored cells received per VCC on the test 3987 device. 3989 Reporting Format: 3991 The results of the CRC-ER/Steady Load/Maximum VCCs test SHOULD be 3992 reported in a form of text and graph. 3994 The text results SHOULD display the numerical values of the CRC-ER. The 3995 values given SHOULD include: time period of test in s, test VPI/VCI 3996 value, total number of cells transmitted and received on the given 3997 VPI/VCI during the test in positive integers, and the CRC-ER for the 3998 entire test. 4000 The graph results SHOULD display the CRC Error ratio values. There will 4001 be (Max number of VCCs/10) graphs, with 10 VCCs indicated on each graph. 4002 The x-coordinate SHOULD be the test run time in either seconds, minutes 4003 or days depending on the total length of the test. The x-coordinate time 4004 SHOULD be configurable. The y-coordinate SHOULD be the CRC-ER for each 4005 VCC. There SHOULD be no more than 10 curves on each graph, one curve 4006 indicated and labeled for each VCC. The integration time per point MUST 4007 be indicated. 4009 The results MUST also indicate the packet size in octets, traffic rate 4010 in packets per second, and bearer class as generated by the test device. 4011 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 4012 be indicated. The bearer class of the created VCC MUST also be 4013 indicated. 4015 3.2.3.4. CRC-ER/Bursty VBR Load/One VCC 4017 Objective: To determine the SUT ratio of lost cells on one VCC in a 4018 transmission in relation to the total cells sent as defined in RFC 2761 4019 "Terminology for ATM Benchmarking". 4021 Procedure: 4023 1) Set up the SUT and test device using the bi-directional 4024 configuration. 4026 2) Configure the SUT and test device with one VCC. The VCC SHOULD 4027 contain one VPI/VCI. The VCC MUST be configured as either a CBR or VBR 4028 connection. The VPI/VCI MUST not be one of the reserved ATM signaling 4029 channels (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be 4030 configured using one of the specified traffic descriptors. 4032 3) Send a specific number of IP packets containing one of the specified 4033 bit patterns at a specific rate through the SUT via the defined test 4034 VCC. Since this test is not a throughput test, the rate should not be 4035 greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4037 4) Count the IP packets that are transmitted by the SUT to verify 4038 connectivity and load. If the count on the test device is the same on 4039 the SUT, continue the test; else lower the test device traffic rate 4040 until the counts are the same. 4042 5) Record the number of CRC errored cells received per VCC on the test 4043 device. 4045 Reporting Format: 4047 The results of the CRC-ER/Bursty VBR Load/One VCC test SHOULD be 4048 reported in a form of text and graph. 4050 The text results SHOULD display the numerical values of the CRC-ER. The 4051 values given SHOULD include: time period of test in s, test VPI/VCI 4052 value, total number of cells transmitted and received on the given 4053 VPI/VCI during the test in positive integers, and the CRC-ER for the 4054 entire test. 4056 The graph results SHOULD display the CRC Error ratio values. The x- 4057 coordinate SHOULD be the test run time in either seconds, minutes or 4058 days depending on the total length of the test. The x-coordinate time 4059 SHOULD be configurable. The y-coordinate SHOULD be the CRC-ER. The 4060 integration time per point MUST be indicated. 4062 The results MUST also indicate the packet size in octets, traffic rate 4063 in packets per second, and bearer class as generated by the test device. 4064 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 4065 be indicated. The bearer class of the created VCC MUST also be 4066 indicated. 4068 3.2.3.5. CRC-ER/Bursty VBR Load/Twelve VCCs 4070 Objective: To determine the SUT ratio of lost cells on twelve VCCs in a 4071 transmission in relation to the total cells sent as defined in RFC 2761 4072 "Terminology for ATM Benchmarking". 4074 Procedure: 4076 1) Set up the SUT and test device using the bi-directional 4077 configuration. 4079 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 4080 12 VCIs. The VCC MUST be configured as either a CBR or VBR connection. 4081 The VPI/VCIs MUST not be one of the reserved ATM signaling channels 4082 (e.g. [0,5], [0,16]). The PCR, SCR, and MBS must be configured using 4083 one of the specified traffic descriptors. 4085 3) Send a specific number of IP packets containing one of the specified 4086 bit patterns at a specific rate through the SUT via the defined test 4087 VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 4088 rate. Since this test is not a throughput test, the rate should not be 4089 greater than 90% of line rate. The PCR, SCR, and MBS must be indicated. 4090 The IP PDUs MUST be encapsulated in AAL5. 4092 4) Count the IP packets that are transmitted by the SUT on all VCCs to 4093 verify connectivity and load. If the count on the test device is the 4094 same on the SUT, continue the test; else lower the test device traffic 4095 rate until the counts are the same. 4097 5) Record the number of CRC errored cells received per VCC on the test 4098 device for all VCCs. 4100 Reporting Format: 4102 The results of the CRC-ER/Bursty VBR Load/Twelve VCCs test SHOULD be 4103 reported in a form of text and graph. 4105 The text results SHOULD display the numerical values of the CRC-ER. The 4106 values given SHOULD include: time period of test in s, test VPI/VCI 4107 value, total number of cells transmitted and received on the given 4108 VPI/VCI during the test in positive integers, and the CRC-ER for the 4109 entire test. 4111 The graph results SHOULD display the CRC Error ratio values. The x- 4112 coordinate SHOULD be the test run time in either seconds, minutes or 4113 days depending on the total length of the test. The x-coordinate time 4114 SHOULD be configurable. The y-coordinate SHOULD be the CRC-ER for each 4115 VCC. There should be 12 curves on the graph, on curve indicated and 4116 labeled for each VCC. The integration time per point MUST be indicated. 4118 The results MUST also indicate the packet size in octets, traffic rate 4119 in packets per second, and bearer class as generated by the test device. 4120 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 4121 be indicated. The bearer class of the created VCC MUST also be 4122 indicated. 4124 3.2.3.6. CRC-ER/Bursty VBR Load/Maximum VCCs 4126 Objective: To determine the SUT ratio of lost cells with the maximum number 4127 VCCs supported on the SUT in a transmission in relation to the total cells 4128 sent as defined in RFC 2761 "Terminology for ATM Benchmarking". 4130 Procedure: 4132 1) Set up the SUT and test device using the bi-directional 4133 configuration. 4135 2) Configure the SUT and test device with the maximum number of VCCs 4136 supported on the SUT. For example, if the maximum number of VCCs 4137 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The 4138 VCC MUST be configured as either a CBR or VBR connection. The VPI/VCIs 4139 MUST not be one of the reserved ATM signaling channels (e.g. [0,5], 4140 [0,16]). The PCR, SCR, and MBS must be configured using one of the 4141 specified traffic descriptors. 4143 3) Send a specific number of IP packets containing one of the specified 4144 bit patterns at a specific rate through the SUT via the defined test 4145 VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 4146 rate. Since this test is not a throughput test, the rate should not be 4147 greater than 90% of line rate. The IP PDUs MUST be encapsulated in 4148 AAL5. 4150 4) Count the IP packets that are transmitted by the SUT on all VCCs to 4151 verify connectivity and load. If the count on the test device is the 4152 same on the SUT, continue the test; else lower the test device traffic 4153 rate until the counts are the same. 4155 5) Record the number of CRC errored cells received per VCC on the test 4156 device for all VCCs. 4158 Reporting Format: 4160 The results of the CRC-ER/Bursty VBR Load/Maximum VCCs test SHOULD be 4161 reported in a form of text and graph. 4163 The text results SHOULD display the numerical values of the CRC-ER. The 4164 values given SHOULD include: time period of test in s, test VPI/VCI 4165 value, total number of cells transmitted and received on the given 4166 VPI/VCI during the test in positive integers, and the CRC-ER for the 4167 entire test. 4169 The graph results SHOULD display the CRC Error ratio values. There will 4170 be (Max number of VCCs/10) graphs, with 10 VCCs indicated on each graph. 4171 The x-coordinate SHOULD be the test run time in either seconds, minutes 4172 or days depending on the total length of the test. The x-coordinate time 4173 SHOULD be configurable. The y-coordinate SHOULD be the CRC-ER for each 4174 VCC. There SHOULD be no more than 10 curves on each graph, one curve 4175 indicated and labeled for each VCC. The integration time per point MUST 4176 be indicated. 4178 The results MUST also indicate the packet size in octets, traffic rate 4179 in packets per second, and bearer class as generated by the test device. 4180 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 4181 be indicated. The bearer class of the created VCC MUST also be 4182 indicated. 4184 3.2.3.4. CRC-ER/Bursty UBR Load/One VCC 4186 Objective: To determine the SUT ratio of lost cells on one VCC in a 4187 transmission in relation to the total cells sent as defined in RFC 2761 4188 "Terminology for ATM Benchmarking". 4190 Procedure: 4192 1) Set up the SUT and test device using the bi-directional 4193 configuration. 4195 2) Configure the SUT and test device with one VCC. The VCC SHOULD 4196 contain one VPI/VCI. The VCC MUST be configured as a UBR connection. The 4197 VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. 4198 [0,5], [0,16]). The PCR, SCR, and MBS must be configured using one of 4199 the specified traffic descriptors. 4201 3) Send a specific number of IP packets containing one of the specified 4202 bit patterns at a specific rate through the SUT via the defined test 4203 VCC. Since this test is not a throughput test, the rate should not be 4204 greater than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4206 4) Count the IP packets that are transmitted by the SUT to verify 4207 connectivity and load. If the count on the test device is the same on 4208 the SUT, continue the test; else lower the test device traffic rate 4209 until the counts are the same. 4211 5) Record the number of CRC errored cells received per VCC on the test 4212 device. 4214 Reporting Format: 4216 The results of the CRC-ER/Bursty UBR Load/One VCC test SHOULD be 4217 reported in a form of text and graph. 4219 The text results SHOULD display the numerical values of the CRC-ER. The 4220 values given SHOULD include: time period of test in s, test VPI/VCI 4221 value, total number of cells transmitted and received on the given 4222 VPI/VCI during the test in positive integers, and the CRC-ER for the 4223 entire test. 4225 The graph results SHOULD display the CRC Error ratio values. The x- 4226 coordinate SHOULD be the test run time in either seconds, minutes or 4227 days depending on the total length of the test. The x-coordinate time 4228 SHOULD be configurable. The y-coordinate SHOULD be the CRC-ER. The 4229 integration time per point MUST be indicated. 4231 The results MUST also indicate the packet size in octets, traffic rate 4232 in packets per second, and bearer class as generated by the test device. 4233 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 4234 be indicated. The bearer class of the created VCC MUST also be 4235 indicated. 4237 3.2.3.5. CRC-ER/Bursty UBR Load/Twelve VCCs 4239 Objective: To determine the SUT ratio of lost cells on twelve VCCs in a 4240 transmission in relation to the total cells sent as defined in RFC 2761 4241 "Terminology for ATM Benchmarking". 4243 Procedure: 4245 1) Set up the SUT and test device using the bi-directional 4246 configuration. 4248 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 4249 12 VCIs. The VCC MUST be configured as a UBR connection. The VPI/VCIs 4250 MUST not be one of the reserved ATM signaling channels (e.g. [0,5], 4251 [0,16]). The PCR, SCR, and MBS must be configured using one of the 4252 specified traffic descriptors. 4254 3) Send a specific number of IP packets containing one of the specified 4255 bit patterns at a specific rate through the SUT via the defined test 4256 VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 4257 rate. Since this test is not a throughput test, the rate should not be 4258 greater than 90% of line rate. The PCR, SCR, and MBS must be indicated. 4259 The IP PDUs MUST be encapsulated in AAL5. 4261 4) Count the IP packets that are transmitted by the SUT on all VCCs to 4262 verify connectivity and load. If the count on the test device is the 4263 same on the SUT, continue the test; else lower the test device traffic 4264 rate until the counts are the same. 4266 5) Record the number of CRC errored cells received per VCC on the test 4267 device for all VCCs. 4269 Reporting Format: 4271 The results of the CRC-ER/Bursty UBR Load/Twelve VCCs test SHOULD be 4272 reported in a form of text and graph. 4274 The text results SHOULD display the numerical values of the CRC-ER. The 4275 values given SHOULD include: time period of test in s, test VPI/VCI 4276 value, total number of cells transmitted and received on the given 4277 VPI/VCI during the test in positive integers, and the CRC-ER for the 4278 entire test. 4280 The graph results SHOULD display the CRC Error ratio values. The x- 4281 coordinate SHOULD be the test run time in either seconds, minutes or 4282 days depending on the total length of the test. The x-coordinate time 4283 SHOULD be configurable. The y-coordinate SHOULD be the CRC-ER for each 4284 VCC. There should be 12 curves on the graph, on curve indicated and 4285 labeled for each VCC. The integration time per point MUST be indicated. 4287 The results MUST also indicate the packet size in octets, traffic rate 4288 in packets per second, and bearer class as generated by the test device. 4289 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 4290 be indicated. The bearer class of the created VCC MUST also be 4291 indicated. 4293 3.2.3.6. CRC-ER/Bursty UBR Load/Maximum VCCs 4295 Objective: To determine the SUT ratio of lost cells with the maximum number 4296 VCCs supported on the SUT in a transmission in relation to the total cells 4297 sent as defined in RFC 2761 "Terminology for ATM Benchmarking". 4299 Procedure: 4301 1) Set up the SUT and test device using the bi-directional 4302 configuration. 4304 2) Configure the SUT and test device with the maximum number of VCCs 4305 supported on the SUT. For example, if the maximum number of VCCs 4306 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The 4307 VCC MUST be configured as a UBR connection. The VPI/VCIs MUST not be one 4308 of the reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, 4309 SCR, and MBS must be configured using one of the specified traffic 4310 descriptors. 4312 3) Send a specific number of IP packets containing one of the specified 4313 bit patterns at a specific rate through the SUT via the defined test 4314 VCCs. All of the VPI/VCI pairs will generate traffic at the same traffic 4315 rate. Since this test is not a throughput test, the rate should not be 4316 greater than 90% of line rate. The IP PDUs MUST be encapsulated in 4317 AAL5. 4319 4) Count the IP packets that are transmitted by the SUT on all VCCs to 4320 verify connectivity and load. If the count on the test device is the 4321 same on the SUT, continue the test; else lower the test device traffic 4322 rate until the counts are the same. 4324 5) Record the number of CRC errored cells received per VCC on the test 4325 device for all VCCs. 4327 Reporting Format: 4329 The results of the CRC-ER/Bursty UBR Load/Maximum VCCs test SHOULD be 4330 reported in a form of text and graph. 4332 The text results SHOULD display the numerical values of the CRC-ER. The 4333 values given SHOULD include: time period of test in s, test VPI/VCI 4334 value, total number of cells transmitted and received on the given 4335 VPI/VCI during the test in positive integers, and the CRC-ER for the 4336 entire test. 4338 The graph results SHOULD display the CRC Error ratio values. There will 4339 be (Max number of VCCs/10) graphs, with 10 VCCs indicated on each graph. 4340 The x-coordinate SHOULD be the test run time in either seconds, minutes 4341 or days depending on the total length of the test. The x-coordinate time 4342 SHOULD be configurable. The y-coordinate SHOULD be the CRC-ER for each 4343 VCC. There SHOULD be no more than 10 curves on each graph, one curve 4344 indicated and labeled for each VCC. The integration time per point MUST 4345 be indicated. 4347 The results MUST also indicate the packet size in octets, traffic rate 4348 in packets per second, and bearer class as generated by the test device. 4349 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 4350 be indicated. The bearer class of the created VCC MUST also be 4351 indicated. 4353 3.2.3.4. CRC-ER/Bursty Mixed Load/Three VCC 4355 Objective: To determine the SUT ratio of lost cells on one VCC in a 4356 transmission in relation to the total cells sent as defined in RFC 2761 4357 "Terminology for ATM Benchmarking". 4359 Procedure: 4361 1) Set up the SUT and test device using the bi-directional 4362 configuration. 4364 2) Configure the SUT and test device with three VCC's. Each VCC MUST be 4365 defined as a different Bearer class; one CBR, one UBR and one VBR. Each 4366 VCC SHOULD contain one VPI/VCI. The VPI/VCI MUST not be one of the 4367 reserved ATM signaling channels (e.g. [0,5], [0,16]). The PCR, SCR, and 4368 MBS must be configured using one of the specified traffic descriptors. 4370 3) Send a specific number of IP packets containing one of the specified 4371 bit patterns through the SUT via the defined test VCCs. Each generated 4372 VCC stream MUST match the corresponding VCC Bearer class. All of the 4373 VPI/VCI pairs will generate traffic at the same traffic rate. Since 4374 this test is not a throughput test, the rate should not be greater than 4375 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4377 4) Count the IP packets that are transmitted by the SUT to verify 4378 connectivity and load. If the count on the test device is the same on 4379 the SUT, continue the test; else lower the test device traffic rate 4380 until the counts are the same. 4382 5) Record the number of CRC errored cells received per VCC on the test 4383 device. 4385 Reporting Format: 4387 The results of the CRC-ER/Bursty Mixed Load/Three VCC test SHOULD be 4388 reported in in a form of text and graph. 4390 The text results SHOULD display the numerical values of the CRC-ER. The 4391 values given SHOULD include: time period of test in s, test VPI/VCI 4392 value, total number of cells transmitted and received on the given 4393 VPI/VCI during the test in positive integers, and the CRC-ER for the 4394 entire test. 4396 The graph results SHOULD display the CRC Error ratio values. The x- 4397 coordinate SHOULD be the test run time in either seconds, minutes or 4398 days depending on the total length of the test. The x-coordinate time 4399 SHOULD be configurable. The y-coordinate SHOULD be the CRC-ER for each 4400 VCC. There should be 12 curves on the graph, on curve indicated and 4401 labeled for each VCC. The integration time per point MUST be indicated. 4403 The results MUST also indicate the packet size in octets, traffic rate 4404 in packets per second, and bearer class as generated by the test device. 4405 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 4406 be indicated. The bearer class of the created VCC MUST also be 4407 indicated. 4409 3.2.3.5. CRC-ER/Bursty Mixed Load/Twelve VCCs 4411 Objective: To determine the SUT ratio of lost cells on twelve VCCs in a 4412 transmission in relation to the total cells sent as defined in RFC 2761 4413 "Terminology for ATM Benchmarking". 4415 Procedure: 4417 1) Set up the SUT and test device using the bi-directional 4418 configuration. 4420 2) Configure the SUT and test device with twelve VCC's. Each VCC MUST 4421 be defined as one of the Bearer classes for a total of four CBR, four 4422 UBR and four VBR VCC's. Each VCC SHOULD contain one VPI/VCI. The 4423 VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. 4424 [0,5], [0,16]). 4426 3) Send a specific number of IP packets containing one of the specified 4427 bit patterns through the SUT via the defined test VCCs. Each generated 4428 VCC stream MUST match the corresponding VCC Bearer class. All of the 4429 VPI/VCI pairs will generate traffic at the same traffic rate. Since 4430 this test is not a throughput test, the rate should not be greater than 4431 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4433 4) Count the IP packets that are transmitted by the SUT on all VCCs to 4434 verify connectivity and load. If the count on the test device is the 4435 same on the SUT, continue the test; else lower the test device traffic 4436 rate until the counts are the same. 4438 5) Record the number of CRC errored cells received per VCC on the test 4439 device for all VCCs. 4441 Reporting Format: 4443 The results of the CRC-ER/Bursty Mixed Load/Twelve VCCs test SHOULD be 4444 reported in a form of text and graph. 4446 The text results SHOULD display the numerical values of the CRC-ER. The 4447 values given SHOULD include: time period of test in s, test VPI/VCI 4448 value, total number of cells transmitted and received on the given 4449 VPI/VCI during the test in positive integers, and the CRC-ER for the 4450 entire test. 4452 The graph results SHOULD display the CRC Error ratio values. The x- 4453 coordinate SHOULD be the test run time in either seconds, minutes or 4454 days depending on the total length of the test. The x-coordinate time 4455 SHOULD be configurable. The y-coordinate SHOULD be the CRC-ER for each 4456 VCC. There should be 12 curves on the graph, on curve indicated and 4457 labeled for each VCC. The integration time per point MUST be indicated. 4459 The results MUST also indicate the packet size in octets, traffic rate 4460 in packets per second, and bearer class as generated by the test device. 4461 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 4462 be indicated. The bearer class of the created VCC MUST also be 4463 indicated. 4465 3.2.3.6. CRC-ER/Bursty Mixed Load/Maximum VCCs 4467 Objective: To determine the SUT ratio of lost cells with the maximum number 4468 VCCs supported on the SUT in a transmission in relation to the total cells 4469 sent as defined in RFC 2761 "Terminology for ATM Benchmarking". 4471 Procedure: 4473 1) Set up the SUT and test device using the bi-directional 4474 configuration. 4476 2) Configure the SUT and test device with maximum number of VCCs 4477 supported on the SUT. For example, if the maximum number of VCCs 4478 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. Each 4479 VCC MUST be defined as one of the Bearer classes for a total of (max 4480 VCC/3) CBR, (max VCC/3) UBR and (max VCC/3) VBR VCC's. The VPI/VCI MUST 4481 not be one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). 4483 3) Send a specific number of IP packets containing one of the specified 4484 bit patterns through the SUT via the defined test VCCs. Each generated 4485 VCC stream MUST match the corresponding VCC Bearer class. All of the 4486 VPI/VCI pairs will generate traffic at the same traffic rate. Since 4487 this test is not a throughput test, the rate should not be greater than 4488 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4490 4) Count the IP packets that are transmitted by the SUT on all VCCs to 4491 verify connectivity and load. If the count on the test device is the 4492 same on the SUT, continue the test; else lower the test device traffic 4493 rate until the counts are the same. 4495 5) Record the number of CRC errored cells received per VCC on the test 4496 device for all VCCs. 4498 Reporting Format: 4500 The results of the CRC-ER/Bursty Mixed Load/Maximum VCCs test SHOULD be 4501 reported in a form of text and graph. 4503 The text results SHOULD display the numerical values of the CRC-ER. The 4504 values given SHOULD include: time period of test in s, test VPI/VCI 4505 value, total number of cells transmitted and received on the given 4506 VPI/VCI during the test in positive integers, and the CRC-ER for the 4507 entire test. 4509 The graph results SHOULD display the CRC Error ratio values. There will 4510 be (Max number of VCCs/10) graphs, with 10 VCCs indicated on each graph. 4511 The x-coordinate SHOULD be the test run time in either seconds, minutes 4512 or days depending on the total length of the test. The x-coordinate time 4513 SHOULD be configurable. The y-coordinate SHOULD be the CRC-ER for each 4514 VCC. There SHOULD be no more than 10 curves on each graph, one curve 4515 indicated and labeled for each VCC. The integration time per point MUST 4516 be indicated. 4518 The results MUST also indicate the packet size in octets, traffic rate 4519 in packets per second, and bearer class as generated by the test device. 4520 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 4521 be indicated. The bearer class of the created VCC MUST also be 4522 indicated. 4524 3.2.7. Cell Transfer Delay (CTD) 4526 3.2.7.1. Test Setup 4528 The cell transfer delay measurements assume that both the transmitter 4529 and receiver timestamp information is synchronized. Synchronization 4530 SHOULD be achieved by supplying a common clock signal (minimum of 100 4531 Mhz or 10 ns resolution) to both the transmitter and receiver. The 4532 maximum timestamp values MUST be recorded to ensure synchronization in 4533 the case of counter rollover. The cell transfer delay measurements 4534 SHOULD utilize the O.191 cell (ITUT-O.191) encapsulated in a valid IP 4535 packet. If the O.191 cell is not available, a test cell encapsulated in 4536 a valid IP packet MAY be used. The test cell MUST contain a transmit 4537 timestamp which can be correlated with a receive timestamp. A 4538 description of the test cell MUST be included in the test results. The 4539 description MUST include the timestamp length (in bits), counter 4540 rollover value, and the timestamp accuracy (in ns). 4542 3.2.7.2. CTD/Steady Load/One VCC 4544 Objective: To determine the SUT variation in cell transfer delay with one 4545 VCC as defined in RFC 2761 "Terminology for ATM Benchmarking". 4547 Procedure: 4549 1) Set up the SUT and test device using the bi-directional 4550 configuration. 4552 2) Configure the SUT and test device with one VCC. The VCC SHOULD 4553 contain one VPI/VCI. The VCC MUST be configured as either a CBR, VBR, or 4554 UBR connection. The VPI/VCI MUST not be one of the reserved ATM 4555 signaling channels (e.g. [0,5], [0,16]). 4557 3) Send a specific number of IP packets containing timestamps at a 4558 specific constant rate through the SUT via the defined test VCC. Since 4559 this test is not a throughput test, the rate should not be greater than 4560 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4562 4) Count the IP packets that are transmitted by the SUT to verify 4563 connectivity and load. If the count on the test device is the same on 4564 the SUT, continue the test; else lower the test device traffic rate 4565 until the counts are the same. 4567 5) Record the packets timestamps at the transmitter and receiver ends of 4568 the test device. 4570 Reporting Format: 4572 The results of the CTD/Steady Load/One VCC test SHOULD be reported in a 4573 form of text, graph, and histogram. 4575 The text results SHOULD display the numerical values of the CTD. The 4576 values given SHOULD include: time period of test in s, test VPI/VCI 4577 value, total number of cells transmitted and received on the given 4578 VPI/VCI during the test in positive integers, minimum, maximum, and mean 4579 CTD during the test in us. 4581 The graph results SHOULD display the cell transfer delay values. The x- 4582 coordinate SHOULD be the test run time in either seconds, minutes or 4583 days depending on the total length of the test. The x-coordinate time 4584 SHOULD be configurable. The y-coordinate SHOULD be the cell transfer 4585 delay in us. The integration time per point MUST be indicated. 4587 The histogram results SHOULD display the cell transfer delay. The x- 4588 coordinate SHOULD be the cell transfer delay in us with at least 256 4589 bins. The y-coordinate SHOULD be the number of cells observed in each 4590 bin. 4592 The results MUST also indicate the packet size in octets, traffic rate 4593 in packets per second, and bearer class as generated by the test device. 4594 The VCC and VPI/VCI values MUST be indicated. The bearer class of the 4595 created VCC MUST also be indicated. 4597 3.2.7.3. CTD/Steady Load/Twelve VCCs 4599 Objective: To determine the SUT variation in cell transfer delay with 4600 twelve VCCs as defined in RFC 2761 "Terminology for ATM Benchmarking". 4602 Procedure: 4604 1) Set up the SUT and test device using the bi-directional 4605 configuration. 4607 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 4608 12 VCIs. The VCC's MUST be configured as either a CBR, VBR, or UBR 4609 connection. The VPI/VCIs MUST not be one of the reserved ATM signaling 4610 channels (e.g. [0,5], [0,16]). 4612 3) Send a specific number of IP packets containing timestamps at a 4613 specific constant rate through the SUT via the defined test VCCs. All 4614 of the VPI/VCI pairs will generate traffic at the same traffic rate. 4615 Since this test is not a throughput test, the rate should not be greater 4616 than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4618 4) Count the IP packets that are transmitted by the SUT on all VCCs to 4619 verify connectivity and load. If the count on the test device is the 4620 same on the SUT, continue the test; else lower the test device traffic 4621 rate until the counts are the same. 4623 5) Record the packets timestamps at the transmitter and receiver ends of 4624 the test device for all VCCs. 4626 Reporting Format: 4628 The results of the CTD/Steady Load/Twelve VCCs test SHOULD be reported 4629 in a form of text, graph, and histograms. 4631 The text results SHOULD display the numerical values of the CTD. The 4632 values given SHOULD include: time period of test in s, test VPI/VCI 4633 values, total number of cells transmitted and received on each VCC 4634 during the test in positive integers, maximum and minimum CTD on each 4635 VCC during the test in us, and mean CTD on each VCC in us. 4637 The graph results SHOULD display the cell transfer delay values. The x- 4638 coordinate SHOULD be the test run time in either seconds, minutes or 4639 days depending on the total length of the test. The x-coordinate time 4640 SHOULD be configurable. The y-coordinate SHOULD be the cell transfer 4641 delay for each VCC in ms. There SHOULD be 12 curves on the graph, one 4642 curves indicated and labeled for each VCC. The integration time per 4643 point MUST be indicated. 4645 The histograms SHOULD display the cell transfer delay. There will be one 4646 histogram for each VCC. The x-coordinate SHOULD be the cell transfer 4647 delay in us with at least 256 bins. The y-coordinate SHOULD be the 4648 number of cells observed in each bin. 4650 The results MUST also indicate the packet size in octets, traffic rate 4651 in packets per second, and bearer class as generated by the test device. 4652 The VCC and VPI/VCI values MUST be indicated. The bearer class of the 4653 created VCC MUST also be indicated. 4655 3.2.7.4. CTD/Steady Load/Maximum VCCs 4657 Objective: To determine the SUT variation in cell transfer delay with the 4658 maximum number VCCs supported on the SUT as defined in RFC 2761 4659 "Terminology for ATM Benchmarking". 4661 Procedure: 4663 1) Set up the SUT and test device using the bi-directional 4664 configuration. 4666 2) Configure the SUT and test device with the maximum number of VCCs 4667 supported on the SUT. For example, if the maximum number of VCCs 4668 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The 4669 VCC's MUST be configured as either a CBR, VBR, or UBR connection. The 4670 VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. 4671 [0,5], [0,16]). 4673 3) Send a specific number of IP packets containing timestamps at a 4674 specific constant rate through the SUT via the defined test VCCs. All 4675 of the VPI/VCI pairs will generate traffic at the same traffic rate. 4677 Since this test is not a throughput test, the rate should not be greater 4678 than 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4680 4) Count the IP packets that are transmitted by the SUT on all VCCs to 4681 verify connectivity and load. If the count on the test device is the 4682 same on the SUT, continue the test; else lower the test device traffic 4683 rate until the counts are the same. 4685 5) Record the packets timestamps at the transmitter and receiver ends of 4686 the test device for all VCCs. 4688 Reporting Format: 4690 The results of the CTD/Steady Load/Maximum VCCs test SHOULD be reported 4691 in a form of text, graphs, and histograms. 4693 The text results SHOULD display the numerical values of the CTD. The 4694 values given SHOULD include: time period of test in s, test VPI/VCI 4695 values, total number of cells transmitted and received on each VCC 4696 during the test in positive integers, maximum and minimum CTD on each 4697 VCC during the test in us, and mean CTD on each VCC in us. 4699 The graph results SHOULD display the cell transfer delay values. There 4700 will be (Max number of VCCs/10) graphs, with 10 VCCs indicated on each 4701 graph. The x-coordinate SHOULD be the test run time in either seconds, 4702 minutes or days depending on the total length of the test. The x- 4703 coordinate time SHOULD be configurable. The y-coordinate SHOULD be the 4704 cell transfer delay for each VCC in us. There SHOULD be no more than 10 4705 curves on each graph, one curve indicated and labeled for each VCC. The 4706 integration time per point MUST be indicated. 4708 The histograms SHOULD display the cell transfer delay. There will be one 4709 histogram for each VCC. The x-coordinate SHOULD be the cell transfer 4710 delay in us with at least 256 bins. The y-coordinate SHOULD be the 4711 number of cells observed in each bin. 4713 The results MUST also indicate the packet size in octets, traffic rate 4714 in packets per second, and bearer class as generated by the test device. 4715 The VCC and VPI/VCI values MUST be indicated. The bearer class of the 4716 created VCC MUST also be indicated. 4718 3.2.7.5. CTD/Bursty VBR Load/One VCC 4719 Objective: To determine the SUT variation in cell transfer delay with one 4720 VCC as defined in RFC 2761 "Terminology for ATM Benchmarking". 4722 Procedure: 4724 1) Set up the SUT and test device using the bi-directional 4725 configuration. 4727 2) Configure the SUT and test device with one VCC. The VCC SHOULD 4728 contain one VPI/VCI. The VCC MUST be configured as either a CBR or VBR 4729 connection. The VPI/VCI MUST not be one of the reserved ATM signaling 4730 channels (e.g. [0,5], [0,16]). 4732 3) Send a specific number of IP packets containing timestamps at a 4733 specific VBR through the SUT via the defined test VCC. Since this test 4734 is not a throughput test, the rate should not be greater than 90% of 4735 line rate. The IP PDUs MUST be encapsulated in AAL5. 4737 4) Count the IP packets that are transmitted by the SUT to verify 4738 connectivity and load. If the count on the test device is the same on 4739 the SUT, continue the test; else lower the test device traffic rate 4740 until the counts are the same. 4742 5) Record the packets timestamps at the transmitter and receiver ends of 4743 the test device. 4745 Reporting Format: 4747 The results of the CTD/Bursty VBR Load/One VCC test SHOULD be reported 4748 in a form of text, graph, and histogram. 4750 The text results SHOULD display the numerical values of the CTD. The 4751 values given SHOULD include: time period of test in s, test VPI/VCI 4752 value, total number of cells transmitted and received on the given 4753 VPI/VCI during the test in positive integers, minimum, maximum, and mean 4754 CTD during the test in us. 4756 The graph results SHOULD display the cell transfer delay values. The x- 4757 coordinate SHOULD be the test run time in either seconds, minutes or 4758 days depending on the total length of the test. The x-coordinate time 4759 SHOULD be configurable. The y-coordinate SHOULD be the cell transfer 4760 delay in us. The integration time per point MUST be indicated. 4762 The histogram results SHOULD display the cell transfer delay. The x- 4763 coordinate SHOULD be the cell transfer delay in us with at least 256 4764 bins. The y-coordinate SHOULD be the number of cells observed in each 4765 bin. 4767 The results MUST also indicate the packet size in octets, traffic rate 4768 in packets per second, and bearer class as generated by the test device. 4769 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 4770 be indicated. The bearer class of the created VCC MUST also be 4771 indicated. 4773 3.2.7.6. CTD/Bursty VBR Load/Twelve VCCs 4775 Objective: To determine the SUT variation in cell transfer delay with 4776 twelve VCCs as defined in RFC 2761 "Terminology for ATM Benchmarking". 4778 Procedure: 4780 1) Set up the SUT and test device using the bi-directional 4781 configuration. 4783 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 4784 12 VCIs. The VCC's MUST be configured as either a CBR or VBR connection. 4785 The VPI/VCIs MUST not be one of the reserved ATM signaling channels 4786 (e.g. [0,5], [0,16]). 4788 3) Send a specific number of IP packets containing timestamps at a 4789 specific VBR through the SUT via the defined test VCCs. All of the 4790 VPI/VCI pairs will generate traffic at the same traffic rate. Since 4791 this test is not a throughput test, the rate should not be greater than 4792 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4794 4) Count the IP packets that are transmitted by the SUT on all VCCs to 4795 verify connectivity and load. If the count on the test device is the 4796 same on the SUT, continue the test; else lower the test device traffic 4797 rate until the counts are the same. 4799 5) Record the packets timestamps at the transmitter and receiver ends of 4800 the test device for all VCCs. 4802 Reporting Format: 4804 The results of the CTD/Bursty VBR Load/Twelve VCCs test SHOULD be 4805 reported in a form of text, graph, and histograms. 4807 The text results SHOULD display the numerical values of the CTD. The 4808 values given SHOULD include: time period of test in s, test VPI/VCI 4809 values, total number of cells transmitted and received on each VCC 4810 during the test in positive integers, maximum and minimum CTD on each 4811 VCC during the test in us, and mean CTD on each VCC in us. 4813 The graph results SHOULD display the cell transfer delay values. The x- 4814 coordinate SHOULD be the test run time in either seconds, minutes or 4815 days depending on the total length of the test. The x-coordinate time 4816 SHOULD be configurable. The y-coordinate SHOULD be the cell transfer 4817 delay for each VCC in ms. There SHOULD be 12 curves on the graph, one 4818 curves indicated and labeled for each VCC. The integration time per 4819 point MUST be indicated. 4821 The histograms SHOULD display the cell transfer delay. There will be one 4822 histogram for each VCC. The x-coordinate SHOULD be the cell transfer 4823 delay in us with at least 256 bins. The y-coordinate SHOULD be the 4824 number of cells observed in each bin. 4826 The results MUST also indicate the packet size in octets, traffic rate 4827 in packets per second, and bearer class as generated by the test device. 4828 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 4829 be indicated. The bearer class of the created VCC MUST also be 4830 indicated. 4832 3.2.7.7. CTD/Bursty VBR Load/Maximum VCCs 4834 Objective: To determine the SUT variation in cell transfer delay with the 4835 maximum number VCCs supported on the SUT as defined in RFC 2761 4836 "Terminology for ATM Benchmarking". 4838 Procedure: 4840 1) Set up the SUT and test device using the bi-directional 4841 configuration. 4843 2) Configure the SUT and test device with the maximum number of VCCs 4844 supported on the SUT. For example, if the maximum number of VCCs 4845 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The 4846 VCC's MUST be configured as either a CBR or VBR connection. The 4847 VPI/VCIs MUST not be one of the reserved ATM signaling channels (e.g. 4848 [0,5], [0,16]). 4850 3) Send a specific number of IP packets containing timestamps at a 4851 specific VBR through the SUT via the defined test VCCs. All of the 4852 VPI/VCI pairs will generate traffic at the same traffic rate. Since 4853 this test is not a throughput test, the rate should not be greater than 4854 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4856 4) Count the IP packets that are transmitted by the SUT on all VCCs to 4857 verify connectivity and load. If the count on the test device is the 4858 same on the SUT, continue the test; else lower the test device traffic 4859 rate until the counts are the same. 4861 5) Record the packets timestamps at the transmitter and receiver ends of 4862 the test device for all VCCs. 4864 Reporting Format: 4866 The results of the CTD/Bursty VBR Load/Maximum VCCs test SHOULD be 4867 reported in a form of text, graphs, and histograms. 4869 The text results SHOULD display the numerical values of the CTD. The 4870 values given SHOULD include: time period of test in s, test VPI/VCI 4871 values, total number of cells transmitted and received on each VCC 4872 during the test in positive integers, maximum and minimum CTD on each 4873 VCC during the test in us, and mean CTD on each VCC in us. 4875 The graph results SHOULD display the cell transfer delay values. There 4876 will be (Max number of VCCs/10) graphs, with 10 VCCs indicated on each 4877 graph. The x-coordinate SHOULD be the test run time in either seconds, 4878 minutes or days depending on the total length of the test. The x- 4879 coordinate time SHOULD be configurable. The y-coordinate SHOULD be the 4880 cell transfer delay for each VCC in us. There SHOULD be no more than 10 4881 curves on each graph, one curve indicated and labeled for each VCC. The 4882 integration time per point MUST be indicated. 4884 The histograms SHOULD display the cell transfer delay. There will be one 4885 histogram for each VCC. The x-coordinate SHOULD be the cell transfer 4886 delay in us with at least 256 bins. The y-coordinate SHOULD be the 4887 number of cells observed in each bin. 4889 The results MUST also indicate the packet size in octets, traffic rate 4890 in packets per second, and bearer class as generated by the test device. 4891 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 4892 be indicated. The bearer class of the created VCC MUST also be 4893 indicated. 4895 3.2.7.5. CTD/Bursty UBR Load/One VCC 4897 Objective: To determine the SUT variation in cell transfer delay with one 4898 VCC as defined in RFC 2761 "Terminology for ATM Benchmarking". 4900 Procedure: 4902 1) Set up the SUT and test device using the bi-directional 4903 configuration. 4905 2) Configure the SUT and test device with one VCC. The VCC SHOULD 4906 contain one VPI/VCI. The VCC MUST be configured as a UBR connection. 4907 The VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. 4908 [0,5], [0,16]). 4910 3) Send a specific number of IP packets containing timestamps at a 4911 specific UBR through the SUT via the defined test VCC. Since this test 4912 is not a throughput test, the rate should not be greater than 90% of 4913 line rate. The IP PDUs MUST be encapsulated in AAL5. 4915 4) Count the IP packets that are transmitted by the SUT to verify 4916 connectivity and load. If the count on the test device is the same on 4917 the SUT, continue the test; else lower the test device traffic rate 4918 until the counts are the same. 4920 5) Record the packets timestamps at the transmitter and receiver ends of 4921 the test device. 4923 Reporting Format: 4925 The results of the CTD/Bursty UBR Load/One VCC test SHOULD be reported 4926 in a form of text, graph, and histogram. 4928 The text results SHOULD display the numerical values of the CTD. The 4929 values given SHOULD include: time period of test in s, test VPI/VCI 4930 value, total number of cells transmitted and received on the given 4931 VPI/VCI during the test in positive integers, minimum, maximum, and mean 4932 CTD during the test in us. 4934 The graph results SHOULD display the cell transfer delay values. The x- 4935 coordinate SHOULD be the test run time in either seconds, minutes or 4936 days depending on the total length of the test. The x-coordinate time 4937 SHOULD be configurable. The y-coordinate SHOULD be the cell transfer 4938 delay in us. The integration time per point MUST be indicated. 4940 The histogram results SHOULD display the cell transfer delay. The x- 4941 coordinate SHOULD be the cell transfer delay in us with at least 256 4942 bins. The y-coordinate SHOULD be the number of cells observed in each 4943 bin. 4945 The results MUST also indicate the packet size in octets, traffic rate 4946 in packets per second, and bearer class as generated by the test device. 4947 The VCC and VPI/VCI values MUST be indicated. The bearer class of the 4948 created VCC MUST also be indicated. 4950 3.2.7.6. CTD/Bursty UBR Load/Twelve VCCs 4952 Objective: To determine the SUT variation in cell transfer delay with 4953 twelve VCCs as defined in RFC 2761 "Terminology for ATM Benchmarking". 4955 Procedure: 4957 1) Set up the SUT and test device using the bi-directional 4958 configuration. 4960 2) Configure the SUT and test device with twelve VCCs, using 1 VPI and 4961 12 VCIs. The VCC's MUST be configured as a UBR connection. The VPI/VCIs 4962 MUST not be one of the reserved ATM signaling channels (e.g. [0,5], 4963 [0,16]). 4965 3) Send a specific number of IP packets containing timestamps at a 4966 specific UBR through the SUT via the defined test VCCs. All of the 4967 VPI/VCI pairs will generate traffic at the same traffic rate. Since 4968 this test is not a throughput test, the rate should not be greater than 4969 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 4971 4) Count the IP packets that are transmitted by the SUT on all VCCs to 4972 verify connectivity and load. If the count on the test device is the 4973 same on the SUT, continue the test; else lower the test device traffic 4974 rate until the counts are the same. 4976 5) Record the packets timestamps at the transmitter and receiver ends of 4977 the test device for all VCCs. 4979 Reporting Format: 4981 The results of the CTD/Bursty UBR Load/Twelve VCCs test SHOULD be 4982 reported in a form of text, graph, and histograms. 4984 The text results SHOULD display the numerical values of the CTD. The 4985 values given SHOULD include: time period of test in s, test VPI/VCI 4986 values, total number of cells transmitted and received on each VCC 4987 during the test in positive integers, maximum and minimum CTD on each 4988 VCC during the test in us, and mean CTD on each VCC in us. 4990 The graph results SHOULD display the cell transfer delay values. The x- 4991 coordinate SHOULD be the test run time in either seconds, minutes or 4992 days depending on the total length of the test. The x-coordinate time 4993 SHOULD be configurable. The y-coordinate SHOULD be the cell transfer 4994 delay for each VCC in ms. There SHOULD be 12 curves on the graph, one 4995 curves indicated and labeled for each VCC. The integration time per 4996 point MUST be indicated. 4998 The histograms SHOULD display the cell transfer delay. There will be one 4999 histogram for each VCC. The x-coordinate SHOULD be the cell transfer 5000 delay in us with at least 256 bins. The y-coordinate SHOULD be the 5001 number of cells observed in each bin. 5003 The results MUST also indicate the packet size in octets, traffic rate 5004 in packets per second, and bearer class as generated by the test device. 5005 The VCC and VPI/VCI values MUST be indicated. The bearer class of the 5006 created VCC MUST also be indicated. 5008 3.2.7.7. CTD/Bursty UBR Load/Maximum VCCs 5010 Objective: To determine the SUT variation in cell transfer delay with the 5011 maximum number VCCs supported on the SUT as defined in RFC 2761 5012 "Terminology for ATM Benchmarking". 5014 Procedure: 5016 1) Set up the SUT and test device using the bi-directional 5017 configuration. 5019 2) Configure the SUT and test device with the maximum number of VCCs 5020 supported on the SUT. For example, if the maximum number of VCCs 5021 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. The 5022 VCC MUST be configured as a UBR connection. The VPI/VCIs MUST not be 5023 one of the reserved ATM signaling channels (e.g. [0,5], [0,16]). 5025 3) Send a specific number of IP packets containing timestamps at a 5026 specific UBR through the SUT via the defined test VCCs. All of the 5027 VPI/VCI pairs will generate traffic at the same traffic rate. Since 5028 this test is not a throughput test, the rate should not be greater than 5029 90% of line rate. The IP PDUs MUST be encapsulated in AAL5. 5031 4) Count the IP packets that are transmitted by the SUT on all VCCs to 5032 verify connectivity and load. If the count on the test device is the 5033 same on the SUT, continue the test; else lower the test device traffic 5034 rate until the counts are the same. 5036 5) Record the packets timestamps at the transmitter and receiver ends of 5037 the test device for all VCCs. 5039 Reporting Format: 5041 The results of the CTD/Bursty UBR Load/Maximum VCCs test SHOULD be 5042 reported in a form of text, graphs, and histograms. 5044 The text results SHOULD display the numerical values of the CTD. The 5045 values given SHOULD include: time period of test in s, test VPI/VCI 5046 values, total number of cells transmitted and received on each VCC 5047 during the test in positive integers, maximum and minimum CTD on each 5048 VCC during the test in us, and mean CTD on each VCC in us. 5050 The graph results SHOULD display the cell transfer delay values. There 5051 will be (Max number of VCCs/10) graphs, with 10 VCCs indicated on each 5052 graph. The x-coordinate SHOULD be the test run time in either seconds, 5053 minutes or days depending on the total length of the test. The x- 5054 coordinate time SHOULD be configurable. The y-coordinate SHOULD be the 5055 cell transfer delay for each VCC in us. There SHOULD be no more than 10 5056 curves on each graph, one curve indicated and labeled for each VCC. The 5057 integration time per point MUST be indicated. 5059 The histograms SHOULD display the cell transfer delay. There will be one 5060 histogram for each VCC. The x-coordinate SHOULD be the cell transfer 5061 delay in us with at least 256 bins. The y-coordinate SHOULD be the 5062 number of cells observed in each bin. 5064 The results MUST also indicate the packet size in octets, traffic rate 5065 in packets per second, and bearer class as generated by the test device. 5066 The VCC and VPI/VCI values MUST be indicated. The bearer class of the 5067 created VCC MUST also be indicated. 5069 3.2.7.8. CTD/Mixed Load/Three VCC's 5071 Objective: To determine the SUT variation in cell transfer delay with three 5072 VCC's as defined in RFC 2761 "Terminology for ATM Benchmarking". 5074 Procedure: 5076 1) Set up the SUT and test device using the bi-directional 5077 configuration. 5079 2) Configure the SUT and test device with three VCC's. Each VCC MUST be 5080 defined as a different Bearer class: one CBR, one UBR and one VBR. Each 5081 VCC SHOULD contain one VPI/VCI. The VPI/VCI MUST not be one of the 5082 reserved ATM signaling channels (e.g. [0,5], [0,16]). 5084 3) Send a specific number of IP packets containing timestamps through 5085 the SUT via the defined test VCCs. Each generated VCC stream MUST match 5086 the corresponding VCC Bearer class. All of the VPI/VCI pairs will 5087 generate traffic at the same traffic rate. Since this test is not a 5088 throughput test, the rate should not be greater than 90% of line rate. 5089 The IP PDUs MUST be encapsulated in AAL5. 5091 4) Count the IP packets that are transmitted by the SUT to verify 5092 connectivity and load. If the count on the test device is the same on 5093 the SUT, continue the test; else lower the test device traffic rate 5094 until the counts are the same. 5096 5) Record the packets timestamps at the transmitter and receiver ends of 5097 the test device for all VCC's. 5099 Reporting Format: 5101 The results of the CTD/Mixed Load/Three VCC test SHOULD be reported in a 5102 form of text, graph, and histogram. 5104 The text results SHOULD display the numerical values of the CTD. The 5105 values given SHOULD include: time period of test in s, test VPI/VCI 5106 value, total number of cells transmitted and received on the given 5107 VPI/VCI during the test in positive integers, minimum, maximum, and mean 5108 CTD during the test in us. 5110 The graph results SHOULD display the cell transfer delay values. The x- 5111 coordinate SHOULD be the test run time in either seconds, minutes or 5112 days depending on the total length of the test. The x-coordinate time 5113 SHOULD be configurable. The y-coordinate SHOULD be the cell transfer 5114 delay in us. The integration time per point MUST be indicated. 5116 The histogram results SHOULD display the cell transfer delay. The x- 5117 coordinate SHOULD be the cell transfer delay in us with at least 256 5118 bins. The y-coordinate SHOULD be the number of cells observed in each 5119 bin. 5121 The results MUST also indicate the packet size in octets, traffic rate 5122 in packets per second, and bearer class as generated by the test device. 5123 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 5124 be indicated. The bearer class of the created VCC MUST also be 5125 indicated. 5127 3.2.7.9. CTD/Mixed Load/Twelve VCCs 5129 Objective: To determine the SUT variation in cell transfer delay with 5130 twelve VCCs as defined in RFC 2761 "Terminology for ATM Benchmarking". 5132 Procedure: 5133 1) Set up the SUT and test device using the bi-directional 5134 configuration. 5136 2) Configure the SUT and test device with twelve VCC's. Each VCC MUST 5137 be defined as one of the Bearer classes for a total of four CBR, four 5138 UBR and four VBR VCC's. Each VCC SHOULD contain one VPI/VCI. The 5139 VPI/VCI MUST not be one of the reserved ATM signaling channels (e.g. 5140 [0,5], [0,16]). 5142 3) Send a specific number of IP packets containing timestamps through 5143 the SUT via the defined test VCCs. Each generated VCC stream MUST match 5144 the corresponding VCC Bearer class. All of the VPI/VCI pairs will 5145 generate traffic at the same traffic rate. Since this test is not a 5146 throughput test, the rate should not be greater than 90% of line rate. 5147 The IP PDUs MUST be encapsulated in AAL5. 5149 4) Count the IP packets that are transmitted by the SUT on all VCCs to 5150 verify connectivity and load. If the count on the test device is the 5151 same on the SUT, continue the test; else lower the test device traffic 5152 rate until the counts are the same. 5154 5) Record the packets timestamps at the transmitter and receiver ends of 5155 the test device for all VCCs. 5157 Reporting Format: 5159 The results of the CTD/Mixed Load/Twelve VCCs test SHOULD be reported in 5160 a form of text, graph, and histograms. 5162 The text results SHOULD display the numerical values of the CTD. The 5163 values given SHOULD include: time period of test in s, test VPI/VCI 5164 values, total number of cells transmitted and received on each VCC 5165 during the test in positive integers, maximum and minimum CTD on each 5166 VCC during the test in us, and mean CTD on each VCC in us. 5168 The graph results SHOULD display the cell transfer delay values. The x- 5169 coordinate SHOULD be the test run time in either seconds, minutes or 5170 days depending on the total length of the test. The x-coordinate time 5171 SHOULD be configurable. The y-coordinate SHOULD be the cell transfer 5172 delay for each VCC in ms. There SHOULD be 12 curves on the graph, one 5173 curves indicated and labeled for each VCC. The integration time per 5174 point MUST be indicated. 5176 The histograms SHOULD display the cell transfer delay. There will be one 5177 histogram for each VCC. The x-coordinate SHOULD be the cell transfer 5178 delay in us with at least 256 bins. The y-coordinate SHOULD be the 5179 number of cells observed in each bin. 5181 The results MUST also indicate the packet size in octets, traffic rate 5182 in packets per second, and bearer class as generated by the test device. 5183 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 5184 be indicated. The bearer class of the created VCC MUST also be 5185 indicated. 5187 3.2.7.10. CTD/Mixed Load/Maximum VCCs 5189 Objective: To determine the SUT variation in cell transfer delay with the 5190 maximum number VCCs supported on the SUT as defined in RFC 2761 5191 "Terminology for ATM Benchmarking". 5193 Procedure: 5195 1) Set up the SUT and test device using the bi-directional 5196 configuration. 5198 2) Configure the SUT and test device with maximum number of VCCs 5199 supported on the SUT. For example, if the maximum number of VCCs 5200 supported on the SUT is 1024, define 256 VPIs with 4 VCIs per VPI. Each 5201 VCC MUST be defined as one of the Bearer classes for a total of (max 5202 VCC/3) CBR, (max VCC/3) UBR and (max VCC/3) VBR VCC's. If the maximum 5203 number of VCC's is not divisible by 3, the total for each bearer class 5204 MUST be within 3 VCC's of each other. The VPI/VCI MUST not be one of 5205 the reserved ATM signaling channels (e.g. [0,5], [0,16]). 5207 3) Send a specific number of IP packets containing timestamps through 5208 the SUT via the defined test VCCs. Each generated VCC stream MUST match 5209 the corresponding VCC Bearer class. All of the VPI/VCI pairs will 5210 generate traffic at the same traffic rate. Since this test is not a 5211 throughput test, the rate should not be greater than 90% of line rate. 5212 The IP PDUs MUST be encapsulated in AAL5. 5214 4) Count the IP packets that are transmitted by the SUT on all VCCs to 5215 verify connectivity and load. If the count on the test device is the 5216 same on the SUT, continue the test; else lower the test device traffic 5217 rate until the counts are the same. 5219 5) Record the packets timestamps at the transmitter and receiver ends of 5220 the test device for all VCCs. 5222 Reporting Format: 5224 The results of the CTD/Mixed Load/Maximum VCCs test SHOULD be reported 5225 in a form of text, graphs, and histograms. 5227 The text results SHOULD display the numerical values of the CTD. The 5228 values given SHOULD include: time period of test in s, test VPI/VCI 5229 values, total number of cells transmitted and received on each VCC 5230 during the test in positive integers, maximum and minimum CTD on each 5231 VCC during the test in us, and mean CTD on each VCC in us. 5233 The graph results SHOULD display the cell transfer delay values. There 5234 will be (Max number of VCCs/10) graphs, with 10 VCCs indicated on each 5235 graph. The x-coordinate SHOULD be the test run time in either seconds, 5236 minutes or days depending on the total length of the test. The x- 5237 coordinate time SHOULD be configurable. The y-coordinate SHOULD be the 5238 cell transfer delay for each VCC in us. There SHOULD be no more than 10 5239 curves on each graph, one curve indicated and labeled for each VCC. The 5240 integration time per point MUST be indicated. 5242 The histograms SHOULD display the cell transfer delay. There will be one 5243 histogram for each VCC. The x-coordinate SHOULD be the cell transfer 5244 delay in us with at least 256 bins. The y-coordinate SHOULD be the 5245 number of cells observed in each bin. 5247 The results MUST also indicate the packet size in octets, traffic rate 5248 in packets per second, and bearer class as generated by the test device. 5249 The VCC and VPI/VCI values MUST be indicated. The PCR, SCR, and MBS MUST 5250 be indicated. The bearer class of the created VCC MUST also be 5251 indicated. 5253 4. Security Considerations. 5255 As this document is solely for the purpose of providing methodology and 5256 describes neither a protocol nor an implementation, there are no 5257 security considerations associated with this document. 5259 5. Notices 5261 The IETF takes no position regarding the validity or scope of any 5262 intellectual property or other rights that might be claimed to pertain 5263 to the implementation or use of the technology described in this 5264 document or the extent to which any license under such rights might or 5265 might not be available; neither does it represent that it has made any 5266 effort to identify any such rights. Information on the IETFs procedures 5267 with respect to rights in standards-track and standards-related 5268 documentation can be found in BCP-11. Copies of claims of rights made 5269 available for publication and any assurances of licenses to be made 5270 available, or the result of an attempt made to obtain a general license 5271 or permission for the use of such proprietary rights by implementors or 5272 users of this specification can be obtained from the IETF Secretariat. 5274 The IETF invites any interested party to bring to its attention any 5275 copyrights, patents or patent applications, or other proprietary rights 5276 which may cover technology that may be required to practice this 5277 standard. Please address the information to the IETF Executive 5278 Director. 5280 6. Disclaimer 5282 Copyright (C) The Internet Society (1999). All Rights Reserved. 5284 This document and translations of it may be copied and furnished to 5285 others, and derivative works that comment on or otherwise explain it or 5286 assist in its implementation may be prepared, copied, published and 5287 distributed, in whole or in part, without restriction of any kind, 5288 provided that the above copyright notice and this paragraph are included 5289 on all such copies and derivative works. However, this document itself 5290 may not be modified in any way, such as by removing the copyright notice 5291 or references to the Internet Society or other Internet organizations, 5292 except as needed for the purpose of developing Internet standards in 5293 which case the procedures for copyrights defined in the Internet 5294 Standards process must be followed, or as required to translate it into 5295 languages other than English. 5297 The limited permissions granted above are perpetual and will not be 5298 revoked by the Internet Society or its successors or assigns. This 5299 document and the information contained herein is provided on an "AS IS" 5300 basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE 5301 DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED 5302 TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE 5303 ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 5304 PARTICULAR PURPOSE. 5306 7. References 5308 [IETF-RFC-2544] IETF RFC 2544 "Benchmarking Methodology for Network 5309 Interconnect Devices", March, 1999. 5311 [IETF-RFC-2225] IETF RFC 2225 "Classical IP and ARP over ATM", April, 5312 1998. 5314 [IETF-RFC-2761] IETF RFC 2761 "Terminology for ATM Benchmarking" Draft, 5315 2000. 5317 [AF-ILMI4.0] ATM Forum Integrated Local Management Interface Version 5318 4.0, af-ilmi-0065.000, September 1996. 5320 [AF-TEST-0022] Introduction to ATM Forum Test Specifications, af-test- 5321 0022.00, December 1994. 5323 [AF-TM4.0] ATM Forum, Traffic Management Specification Version 4.0, af- 5324 tm- 0056.00, April 1996. 5326 [AF-UNI3.1] ATM Forum, User Network Interface Specification Version 3.1, 5327 September 1994. 5329 [AF-UNI4.0] ATM Forum, User Network Interface Specification Version 4.0, 5330 July 1996. 5332 8. Editor's Addresses 5334 Jeffrey Dunn 5335 Advanced Network Consultants, Inc. 5336 4214 Crest Place, Ellicott City, MD 21043 USA 5337 Phone: +1 (410) 750-1700, E-mail: Jeffrey.Dunn@worldnet.att.net 5339 Cynthia Martin 5340 Advanced Network Consultants, Inc. 5341 4214 Crest Place, Ellicott City, MD 21043 USA 5342 Phone: +1 (410) 750-1700, E-mail: Cynthia.E.Martin@worldnet.att.net