File: rfc3116.txt

package info (click to toggle)
doc-rfc 20181229-2
  • links: PTS, VCS
  • area: non-free
  • in suites: buster
  • size: 570,944 kB
  • sloc: xml: 285,646; sh: 107; python: 90; perl: 42; makefile: 14
file content (7115 lines) | stat: -rw-r--r-- 294,857 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
3897
3898
3899
3900
3901
3902
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
3921
3922
3923
3924
3925
3926
3927
3928
3929
3930
3931
3932
3933
3934
3935
3936
3937
3938
3939
3940
3941
3942
3943
3944
3945
3946
3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3965
3966
3967
3968
3969
3970
3971
3972
3973
3974
3975
3976
3977
3978
3979
3980
3981
3982
3983
3984
3985
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
4000
4001
4002
4003
4004
4005
4006
4007
4008
4009
4010
4011
4012
4013
4014
4015
4016
4017
4018
4019
4020
4021
4022
4023
4024
4025
4026
4027
4028
4029
4030
4031
4032
4033
4034
4035
4036
4037
4038
4039
4040
4041
4042
4043
4044
4045
4046
4047
4048
4049
4050
4051
4052
4053
4054
4055
4056
4057
4058
4059
4060
4061
4062
4063
4064
4065
4066
4067
4068
4069
4070
4071
4072
4073
4074
4075
4076
4077
4078
4079
4080
4081
4082
4083
4084
4085
4086
4087
4088
4089
4090
4091
4092
4093
4094
4095
4096
4097
4098
4099
4100
4101
4102
4103
4104
4105
4106
4107
4108
4109
4110
4111
4112
4113
4114
4115
4116
4117
4118
4119
4120
4121
4122
4123
4124
4125
4126
4127
4128
4129
4130
4131
4132
4133
4134
4135
4136
4137
4138
4139
4140
4141
4142
4143
4144
4145
4146
4147
4148
4149
4150
4151
4152
4153
4154
4155
4156
4157
4158
4159
4160
4161
4162
4163
4164
4165
4166
4167
4168
4169
4170
4171
4172
4173
4174
4175
4176
4177
4178
4179
4180
4181
4182
4183
4184
4185
4186
4187
4188
4189
4190
4191
4192
4193
4194
4195
4196
4197
4198
4199
4200
4201
4202
4203
4204
4205
4206
4207
4208
4209
4210
4211
4212
4213
4214
4215
4216
4217
4218
4219
4220
4221
4222
4223
4224
4225
4226
4227
4228
4229
4230
4231
4232
4233
4234
4235
4236
4237
4238
4239
4240
4241
4242
4243
4244
4245
4246
4247
4248
4249
4250
4251
4252
4253
4254
4255
4256
4257
4258
4259
4260
4261
4262
4263
4264
4265
4266
4267
4268
4269
4270
4271
4272
4273
4274
4275
4276
4277
4278
4279
4280
4281
4282
4283
4284
4285
4286
4287
4288
4289
4290
4291
4292
4293
4294
4295
4296
4297
4298
4299
4300
4301
4302
4303
4304
4305
4306
4307
4308
4309
4310
4311
4312
4313
4314
4315
4316
4317
4318
4319
4320
4321
4322
4323
4324
4325
4326
4327
4328
4329
4330
4331
4332
4333
4334
4335
4336
4337
4338
4339
4340
4341
4342
4343
4344
4345
4346
4347
4348
4349
4350
4351
4352
4353
4354
4355
4356
4357
4358
4359
4360
4361
4362
4363
4364
4365
4366
4367
4368
4369
4370
4371
4372
4373
4374
4375
4376
4377
4378
4379
4380
4381
4382
4383
4384
4385
4386
4387
4388
4389
4390
4391
4392
4393
4394
4395
4396
4397
4398
4399
4400
4401
4402
4403
4404
4405
4406
4407
4408
4409
4410
4411
4412
4413
4414
4415
4416
4417
4418
4419
4420
4421
4422
4423
4424
4425
4426
4427
4428
4429
4430
4431
4432
4433
4434
4435
4436
4437
4438
4439
4440
4441
4442
4443
4444
4445
4446
4447
4448
4449
4450
4451
4452
4453
4454
4455
4456
4457
4458
4459
4460
4461
4462
4463
4464
4465
4466
4467
4468
4469
4470
4471
4472
4473
4474
4475
4476
4477
4478
4479
4480
4481
4482
4483
4484
4485
4486
4487
4488
4489
4490
4491
4492
4493
4494
4495
4496
4497
4498
4499
4500
4501
4502
4503
4504
4505
4506
4507
4508
4509
4510
4511
4512
4513
4514
4515
4516
4517
4518
4519
4520
4521
4522
4523
4524
4525
4526
4527
4528
4529
4530
4531
4532
4533
4534
4535
4536
4537
4538
4539
4540
4541
4542
4543
4544
4545
4546
4547
4548
4549
4550
4551
4552
4553
4554
4555
4556
4557
4558
4559
4560
4561
4562
4563
4564
4565
4566
4567
4568
4569
4570
4571
4572
4573
4574
4575
4576
4577
4578
4579
4580
4581
4582
4583
4584
4585
4586
4587
4588
4589
4590
4591
4592
4593
4594
4595
4596
4597
4598
4599
4600
4601
4602
4603
4604
4605
4606
4607
4608
4609
4610
4611
4612
4613
4614
4615
4616
4617
4618
4619
4620
4621
4622
4623
4624
4625
4626
4627
4628
4629
4630
4631
4632
4633
4634
4635
4636
4637
4638
4639
4640
4641
4642
4643
4644
4645
4646
4647
4648
4649
4650
4651
4652
4653
4654
4655
4656
4657
4658
4659
4660
4661
4662
4663
4664
4665
4666
4667
4668
4669
4670
4671
4672
4673
4674
4675
4676
4677
4678
4679
4680
4681
4682
4683
4684
4685
4686
4687
4688
4689
4690
4691
4692
4693
4694
4695
4696
4697
4698
4699
4700
4701
4702
4703
4704
4705
4706
4707
4708
4709
4710
4711
4712
4713
4714
4715
4716
4717
4718
4719
4720
4721
4722
4723
4724
4725
4726
4727
4728
4729
4730
4731
4732
4733
4734
4735
4736
4737
4738
4739
4740
4741
4742
4743
4744
4745
4746
4747
4748
4749
4750
4751
4752
4753
4754
4755
4756
4757
4758
4759
4760
4761
4762
4763
4764
4765
4766
4767
4768
4769
4770
4771
4772
4773
4774
4775
4776
4777
4778
4779
4780
4781
4782
4783
4784
4785
4786
4787
4788
4789
4790
4791
4792
4793
4794
4795
4796
4797
4798
4799
4800
4801
4802
4803
4804
4805
4806
4807
4808
4809
4810
4811
4812
4813
4814
4815
4816
4817
4818
4819
4820
4821
4822
4823
4824
4825
4826
4827
4828
4829
4830
4831
4832
4833
4834
4835
4836
4837
4838
4839
4840
4841
4842
4843
4844
4845
4846
4847
4848
4849
4850
4851
4852
4853
4854
4855
4856
4857
4858
4859
4860
4861
4862
4863
4864
4865
4866
4867
4868
4869
4870
4871
4872
4873
4874
4875
4876
4877
4878
4879
4880
4881
4882
4883
4884
4885
4886
4887
4888
4889
4890
4891
4892
4893
4894
4895
4896
4897
4898
4899
4900
4901
4902
4903
4904
4905
4906
4907
4908
4909
4910
4911
4912
4913
4914
4915
4916
4917
4918
4919
4920
4921
4922
4923
4924
4925
4926
4927
4928
4929
4930
4931
4932
4933
4934
4935
4936
4937
4938
4939
4940
4941
4942
4943
4944
4945
4946
4947
4948
4949
4950
4951
4952
4953
4954
4955
4956
4957
4958
4959
4960
4961
4962
4963
4964
4965
4966
4967
4968
4969
4970
4971
4972
4973
4974
4975
4976
4977
4978
4979
4980
4981
4982
4983
4984
4985
4986
4987
4988
4989
4990
4991
4992
4993
4994
4995
4996
4997
4998
4999
5000
5001
5002
5003
5004
5005
5006
5007
5008
5009
5010
5011
5012
5013
5014
5015
5016
5017
5018
5019
5020
5021
5022
5023
5024
5025
5026
5027
5028
5029
5030
5031
5032
5033
5034
5035
5036
5037
5038
5039
5040
5041
5042
5043
5044
5045
5046
5047
5048
5049
5050
5051
5052
5053
5054
5055
5056
5057
5058
5059
5060
5061
5062
5063
5064
5065
5066
5067
5068
5069
5070
5071
5072
5073
5074
5075
5076
5077
5078
5079
5080
5081
5082
5083
5084
5085
5086
5087
5088
5089
5090
5091
5092
5093
5094
5095
5096
5097
5098
5099
5100
5101
5102
5103
5104
5105
5106
5107
5108
5109
5110
5111
5112
5113
5114
5115
5116
5117
5118
5119
5120
5121
5122
5123
5124
5125
5126
5127
5128
5129
5130
5131
5132
5133
5134
5135
5136
5137
5138
5139
5140
5141
5142
5143
5144
5145
5146
5147
5148
5149
5150
5151
5152
5153
5154
5155
5156
5157
5158
5159
5160
5161
5162
5163
5164
5165
5166
5167
5168
5169
5170
5171
5172
5173
5174
5175
5176
5177
5178
5179
5180
5181
5182
5183
5184
5185
5186
5187
5188
5189
5190
5191
5192
5193
5194
5195
5196
5197
5198
5199
5200
5201
5202
5203
5204
5205
5206
5207
5208
5209
5210
5211
5212
5213
5214
5215
5216
5217
5218
5219
5220
5221
5222
5223
5224
5225
5226
5227
5228
5229
5230
5231
5232
5233
5234
5235
5236
5237
5238
5239
5240
5241
5242
5243
5244
5245
5246
5247
5248
5249
5250
5251
5252
5253
5254
5255
5256
5257
5258
5259
5260
5261
5262
5263
5264
5265
5266
5267
5268
5269
5270
5271
5272
5273
5274
5275
5276
5277
5278
5279
5280
5281
5282
5283
5284
5285
5286
5287
5288
5289
5290
5291
5292
5293
5294
5295
5296
5297
5298
5299
5300
5301
5302
5303
5304
5305
5306
5307
5308
5309
5310
5311
5312
5313
5314
5315
5316
5317
5318
5319
5320
5321
5322
5323
5324
5325
5326
5327
5328
5329
5330
5331
5332
5333
5334
5335
5336
5337
5338
5339
5340
5341
5342
5343
5344
5345
5346
5347
5348
5349
5350
5351
5352
5353
5354
5355
5356
5357
5358
5359
5360
5361
5362
5363
5364
5365
5366
5367
5368
5369
5370
5371
5372
5373
5374
5375
5376
5377
5378
5379
5380
5381
5382
5383
5384
5385
5386
5387
5388
5389
5390
5391
5392
5393
5394
5395
5396
5397
5398
5399
5400
5401
5402
5403
5404
5405
5406
5407
5408
5409
5410
5411
5412
5413
5414
5415
5416
5417
5418
5419
5420
5421
5422
5423
5424
5425
5426
5427
5428
5429
5430
5431
5432
5433
5434
5435
5436
5437
5438
5439
5440
5441
5442
5443
5444
5445
5446
5447
5448
5449
5450
5451
5452
5453
5454
5455
5456
5457
5458
5459
5460
5461
5462
5463
5464
5465
5466
5467
5468
5469
5470
5471
5472
5473
5474
5475
5476
5477
5478
5479
5480
5481
5482
5483
5484
5485
5486
5487
5488
5489
5490
5491
5492
5493
5494
5495
5496
5497
5498
5499
5500
5501
5502
5503
5504
5505
5506
5507
5508
5509
5510
5511
5512
5513
5514
5515
5516
5517
5518
5519
5520
5521
5522
5523
5524
5525
5526
5527
5528
5529
5530
5531
5532
5533
5534
5535
5536
5537
5538
5539
5540
5541
5542
5543
5544
5545
5546
5547
5548
5549
5550
5551
5552
5553
5554
5555
5556
5557
5558
5559
5560
5561
5562
5563
5564
5565
5566
5567
5568
5569
5570
5571
5572
5573
5574
5575
5576
5577
5578
5579
5580
5581
5582
5583
5584
5585
5586
5587
5588
5589
5590
5591
5592
5593
5594
5595
5596
5597
5598
5599
5600
5601
5602
5603
5604
5605
5606
5607
5608
5609
5610
5611
5612
5613
5614
5615
5616
5617
5618
5619
5620
5621
5622
5623
5624
5625
5626
5627
5628
5629
5630
5631
5632
5633
5634
5635
5636
5637
5638
5639
5640
5641
5642
5643
5644
5645
5646
5647
5648
5649
5650
5651
5652
5653
5654
5655
5656
5657
5658
5659
5660
5661
5662
5663
5664
5665
5666
5667
5668
5669
5670
5671
5672
5673
5674
5675
5676
5677
5678
5679
5680
5681
5682
5683
5684
5685
5686
5687
5688
5689
5690
5691
5692
5693
5694
5695
5696
5697
5698
5699
5700
5701
5702
5703
5704
5705
5706
5707
5708
5709
5710
5711
5712
5713
5714
5715
5716
5717
5718
5719
5720
5721
5722
5723
5724
5725
5726
5727
5728
5729
5730
5731
5732
5733
5734
5735
5736
5737
5738
5739
5740
5741
5742
5743
5744
5745
5746
5747
5748
5749
5750
5751
5752
5753
5754
5755
5756
5757
5758
5759
5760
5761
5762
5763
5764
5765
5766
5767
5768
5769
5770
5771
5772
5773
5774
5775
5776
5777
5778
5779
5780
5781
5782
5783
5784
5785
5786
5787
5788
5789
5790
5791
5792
5793
5794
5795
5796
5797
5798
5799
5800
5801
5802
5803
5804
5805
5806
5807
5808
5809
5810
5811
5812
5813
5814
5815
5816
5817
5818
5819
5820
5821
5822
5823
5824
5825
5826
5827
5828
5829
5830
5831
5832
5833
5834
5835
5836
5837
5838
5839
5840
5841
5842
5843
5844
5845
5846
5847
5848
5849
5850
5851
5852
5853
5854
5855
5856
5857
5858
5859
5860
5861
5862
5863
5864
5865
5866
5867
5868
5869
5870
5871
5872
5873
5874
5875
5876
5877
5878
5879
5880
5881
5882
5883
5884
5885
5886
5887
5888
5889
5890
5891
5892
5893
5894
5895
5896
5897
5898
5899
5900
5901
5902
5903
5904
5905
5906
5907
5908
5909
5910
5911
5912
5913
5914
5915
5916
5917
5918
5919
5920
5921
5922
5923
5924
5925
5926
5927
5928
5929
5930
5931
5932
5933
5934
5935
5936
5937
5938
5939
5940
5941
5942
5943
5944
5945
5946
5947
5948
5949
5950
5951
5952
5953
5954
5955
5956
5957
5958
5959
5960
5961
5962
5963
5964
5965
5966
5967
5968
5969
5970
5971
5972
5973
5974
5975
5976
5977
5978
5979
5980
5981
5982
5983
5984
5985
5986
5987
5988
5989
5990
5991
5992
5993
5994
5995
5996
5997
5998
5999
6000
6001
6002
6003
6004
6005
6006
6007
6008
6009
6010
6011
6012
6013
6014
6015
6016
6017
6018
6019
6020
6021
6022
6023
6024
6025
6026
6027
6028
6029
6030
6031
6032
6033
6034
6035
6036
6037
6038
6039
6040
6041
6042
6043
6044
6045
6046
6047
6048
6049
6050
6051
6052
6053
6054
6055
6056
6057
6058
6059
6060
6061
6062
6063
6064
6065
6066
6067
6068
6069
6070
6071
6072
6073
6074
6075
6076
6077
6078
6079
6080
6081
6082
6083
6084
6085
6086
6087
6088
6089
6090
6091
6092
6093
6094
6095
6096
6097
6098
6099
6100
6101
6102
6103
6104
6105
6106
6107
6108
6109
6110
6111
6112
6113
6114
6115
6116
6117
6118
6119
6120
6121
6122
6123
6124
6125
6126
6127
6128
6129
6130
6131
6132
6133
6134
6135
6136
6137
6138
6139
6140
6141
6142
6143
6144
6145
6146
6147
6148
6149
6150
6151
6152
6153
6154
6155
6156
6157
6158
6159
6160
6161
6162
6163
6164
6165
6166
6167
6168
6169
6170
6171
6172
6173
6174
6175
6176
6177
6178
6179
6180
6181
6182
6183
6184
6185
6186
6187
6188
6189
6190
6191
6192
6193
6194
6195
6196
6197
6198
6199
6200
6201
6202
6203
6204
6205
6206
6207
6208
6209
6210
6211
6212
6213
6214
6215
6216
6217
6218
6219
6220
6221
6222
6223
6224
6225
6226
6227
6228
6229
6230
6231
6232
6233
6234
6235
6236
6237
6238
6239
6240
6241
6242
6243
6244
6245
6246
6247
6248
6249
6250
6251
6252
6253
6254
6255
6256
6257
6258
6259
6260
6261
6262
6263
6264
6265
6266
6267
6268
6269
6270
6271
6272
6273
6274
6275
6276
6277
6278
6279
6280
6281
6282
6283
6284
6285
6286
6287
6288
6289
6290
6291
6292
6293
6294
6295
6296
6297
6298
6299
6300
6301
6302
6303
6304
6305
6306
6307
6308
6309
6310
6311
6312
6313
6314
6315
6316
6317
6318
6319
6320
6321
6322
6323
6324
6325
6326
6327
6328
6329
6330
6331
6332
6333
6334
6335
6336
6337
6338
6339
6340
6341
6342
6343
6344
6345
6346
6347
6348
6349
6350
6351
6352
6353
6354
6355
6356
6357
6358
6359
6360
6361
6362
6363
6364
6365
6366
6367
6368
6369
6370
6371
6372
6373
6374
6375
6376
6377
6378
6379
6380
6381
6382
6383
6384
6385
6386
6387
6388
6389
6390
6391
6392
6393
6394
6395
6396
6397
6398
6399
6400
6401
6402
6403
6404
6405
6406
6407
6408
6409
6410
6411
6412
6413
6414
6415
6416
6417
6418
6419
6420
6421
6422
6423
6424
6425
6426
6427
6428
6429
6430
6431
6432
6433
6434
6435
6436
6437
6438
6439
6440
6441
6442
6443
6444
6445
6446
6447
6448
6449
6450
6451
6452
6453
6454
6455
6456
6457
6458
6459
6460
6461
6462
6463
6464
6465
6466
6467
6468
6469
6470
6471
6472
6473
6474
6475
6476
6477
6478
6479
6480
6481
6482
6483
6484
6485
6486
6487
6488
6489
6490
6491
6492
6493
6494
6495
6496
6497
6498
6499
6500
6501
6502
6503
6504
6505
6506
6507
6508
6509
6510
6511
6512
6513
6514
6515
6516
6517
6518
6519
6520
6521
6522
6523
6524
6525
6526
6527
6528
6529
6530
6531
6532
6533
6534
6535
6536
6537
6538
6539
6540
6541
6542
6543
6544
6545
6546
6547
6548
6549
6550
6551
6552
6553
6554
6555
6556
6557
6558
6559
6560
6561
6562
6563
6564
6565
6566
6567
6568
6569
6570
6571
6572
6573
6574
6575
6576
6577
6578
6579
6580
6581
6582
6583
6584
6585
6586
6587
6588
6589
6590
6591
6592
6593
6594
6595
6596
6597
6598
6599
6600
6601
6602
6603
6604
6605
6606
6607
6608
6609
6610
6611
6612
6613
6614
6615
6616
6617
6618
6619
6620
6621
6622
6623
6624
6625
6626
6627
6628
6629
6630
6631
6632
6633
6634
6635
6636
6637
6638
6639
6640
6641
6642
6643
6644
6645
6646
6647
6648
6649
6650
6651
6652
6653
6654
6655
6656
6657
6658
6659
6660
6661
6662
6663
6664
6665
6666
6667
6668
6669
6670
6671
6672
6673
6674
6675
6676
6677
6678
6679
6680
6681
6682
6683
6684
6685
6686
6687
6688
6689
6690
6691
6692
6693
6694
6695
6696
6697
6698
6699
6700
6701
6702
6703
6704
6705
6706
6707
6708
6709
6710
6711
6712
6713
6714
6715
6716
6717
6718
6719
6720
6721
6722
6723
6724
6725
6726
6727
6728
6729
6730
6731
6732
6733
6734
6735
6736
6737
6738
6739
6740
6741
6742
6743
6744
6745
6746
6747
6748
6749
6750
6751
6752
6753
6754
6755
6756
6757
6758
6759
6760
6761
6762
6763
6764
6765
6766
6767
6768
6769
6770
6771
6772
6773
6774
6775
6776
6777
6778
6779
6780
6781
6782
6783
6784
6785
6786
6787
6788
6789
6790
6791
6792
6793
6794
6795
6796
6797
6798
6799
6800
6801
6802
6803
6804
6805
6806
6807
6808
6809
6810
6811
6812
6813
6814
6815
6816
6817
6818
6819
6820
6821
6822
6823
6824
6825
6826
6827
6828
6829
6830
6831
6832
6833
6834
6835
6836
6837
6838
6839
6840
6841
6842
6843
6844
6845
6846
6847
6848
6849
6850
6851
6852
6853
6854
6855
6856
6857
6858
6859
6860
6861
6862
6863
6864
6865
6866
6867
6868
6869
6870
6871
6872
6873
6874
6875
6876
6877
6878
6879
6880
6881
6882
6883
6884
6885
6886
6887
6888
6889
6890
6891
6892
6893
6894
6895
6896
6897
6898
6899
6900
6901
6902
6903
6904
6905
6906
6907
6908
6909
6910
6911
6912
6913
6914
6915
6916
6917
6918
6919
6920
6921
6922
6923
6924
6925
6926
6927
6928
6929
6930
6931
6932
6933
6934
6935
6936
6937
6938
6939
6940
6941
6942
6943
6944
6945
6946
6947
6948
6949
6950
6951
6952
6953
6954
6955
6956
6957
6958
6959
6960
6961
6962
6963
6964
6965
6966
6967
6968
6969
6970
6971
6972
6973
6974
6975
6976
6977
6978
6979
6980
6981
6982
6983
6984
6985
6986
6987
6988
6989
6990
6991
6992
6993
6994
6995
6996
6997
6998
6999
7000
7001
7002
7003
7004
7005
7006
7007
7008
7009
7010
7011
7012
7013
7014
7015
7016
7017
7018
7019
7020
7021
7022
7023
7024
7025
7026
7027
7028
7029
7030
7031
7032
7033
7034
7035
7036
7037
7038
7039
7040
7041
7042
7043
7044
7045
7046
7047
7048
7049
7050
7051
7052
7053
7054
7055
7056
7057
7058
7059
7060
7061
7062
7063
7064
7065
7066
7067
7068
7069
7070
7071
7072
7073
7074
7075
7076
7077
7078
7079
7080
7081
7082
7083
7084
7085
7086
7087
7088
7089
7090
7091
7092
7093
7094
7095
7096
7097
7098
7099
7100
7101
7102
7103
7104
7105
7106
7107
7108
7109
7110
7111
7112
7113
7114
7115






Network Working Group                                            J. Dunn
Request for Comments: 3116                                     C. Martin
Category: Informational                                        ANC, Inc.
                                                               June 2001


                    Methodology for ATM Benchmarking

Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2001).  All Rights Reserved.

Abstract

   This document discusses and defines a number of tests that may be
   used to describe the performance characteristics of ATM (Asynchronous
   Transfer Mode) based switching devices.  In addition to defining the
   tests this document also describes specific formats for reporting the
   results of the tests.

   This memo is a product of the Benchmarking Methodology Working Group
   (BMWG) of the Internet Engineering Task Force (IETF).

Table of Contents

   1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2. Background . . . . . . . . . . . . . . . . . . . . . . . . . .  5
   2.1. Test Device Requirements . . . . . . . . . . . . . . . . . .  5
   2.2. Systems Under Test (SUTs). . . . . . . . . . . . . . . . . .  5
   2.3. Test Result Evaluation . . . . . . . . . . . . . . . . . . .  5
   2.4. Requirements . . . . . . . . . . . . . . . . . . . . . . . .  5
   2.5. Test Configurations for SONET. . . . . . . . . . . . . . . .  6
   2.6. SUT Configuration. . . . . . . . . . . . . . . . . . . . . .  7
   2.7. Frame Formats. . . . . . . . . . . . . . . . . . . . . . . .  8
   2.8. Frame Sizes. . . . . . . . . . . . . . . . . . . . . . . . .  8
   2.9. Verifying Received IP PDU's. . . . . . . . . . . . . . . . .  9
   2.10. Modifiers . . . . . . . . . . . . . . . . . . . . . . . . .  9
   2.10.1. Management IP PDU's . . . . . . . . . . . . . . . . . . .  9
   2.10.2. Routing Update IP PDU's . . . . . . . . . . . . . . . . . 10
   2.11. Filters . . . . . . . . . . . . . . . . . . . . . . . . . . 10
   2.11.1. Filter Addresses. . . . . . . . . . . . . . . . . . . . . 11
   2.12. Protocol Addresses. . . . . . . . . . . . . . . . . . . . . 12



Dunn & Martin                Informational                      [Page 1]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   2.13. Route Set Up. . . . . . . . . . . . . . . . . . . . . . . . 12
   2.14. Bidirectional Traffic . . . . . . . . . . . . . . . . . . . 12
   2.15. Single Stream Path. . . . . . . . . . . . . . . . . . . . . 12
   2.16. Multi-port. . . . . . . . . . . . . . . . . . . . . . . . . 13
   2.17. Multiple Protocols. . . . . . . . . . . . . . . . . . . . . 14
   2.18. Multiple IP PDU Sizes . . . . . . . . . . . . . . . . . . . 14
   2.19. Testing Beyond a Single SUT . . . . . . . . . . . . . . . . 14
   2.20. Maximum IP PDU Rate . . . . . . . . . . . . . . . . . . . . 15
   2.21. Busty Traffic . . . . . . . . . . . . . . . . . . . . . . . 15
   2.22. Trial Description . . . . . . . . . . . . . . . . . . . . . 16
   2.23. Trial Duration. . . . . . . . . . . . . . . . . . . . . . . 16
   2.24. Address Resolution. . . . . . . . . . . . . . . . . . . . . 16
   2.25. Synchronized Payload Bit Pattern. . . . . . . . . . . . . . 16
   2.26. Burst Traffic Descriptors . . . . . . . . . . . . . . . . . 17
   3. Performance Metrics. . . . . . . . . . . . . . . . . . . . . . 17
   3.1. Physical Layer-SONET . . . . . . . . . . . . . . . . . . . . 17
   3.1.1. Pointer Movements. . . . . . . . . . . . . . . . . . . . . 17
   3.1.1.1. Pointer Movement Propagation . . . . . . . . . . . . . . 17
   3.1.1.2. Cell Loss due to Pointer Movement. . . . . . . . . . . . 19
   3.1.1.3. IP Packet Loss due to Pointer Movement . . . . . . . . . 20
   3.1.2. Transport Overhead (TOH) Error Count . . . . . . . . . . . 21
   3.1.2.1. TOH Error Propagation. . . . . . . . . . . . . . . . . . 21
   3.1.2.2. Cell Loss due to TOH Error . . . . . . . . . . . . . . . 22
   3.1.2.3. IP Packet Loss due to TOH Error. . . . . . . . . . . . . 23
   3.1.3. Path Overhead (POH) Error Count. . . . . . . . . . . . . . 24
   3.1.3.1. POH Error Propagation. . . . . . . . . . . . . . . . . . 24
   3.1.3.2. Cell Loss due to POH Error . . . . . . . . . . . . . . . 25
   3.1.3.3. IP Packet Loss due to POH Error. . . . . . . . . . . . . 26
   3.2. ATM Layer. . . . . . . . . . . . . . . . . . . . . . . . . . 27
   3.2.1. Two-Point Cell Delay Variation (CDV) . . . . . . . . . . . 27
   3.2.1.1. Test Setup . . . . . . . . . . . . . . . . . . . . . . . 27
   3.2.1.2. Two-point CDV/Steady Load/One VCC. . . . . . . . . . . . 27
   3.2.1.3. Two-point CDV/Steady Load/Twelve VCCs. . . . . . . . . . 28
   3.2.1.4. Two-point CDV/Steady Load/Maximum VCCs . . . . . . . . . 30
   3.2.1.5. Two-point CDV/Bursty VBR Load/One VCC. . . . . . . . . . 31
   3.2.1.6. Two-point CDV/Bursty VBR Load/Twelve VCCs. . . . . . . . 32
   3.2.1.7. Two-point CDV/Bursty VBR Load/Maximum VCCs . . . . . . . 34
   3.2.1.8. Two-point CDV/Mixed Load/Three VCC's . . . . . . . . . . 35
   3.2.1.9. Two-point CDV/Mixed Load/Twelve VCCs . . . . . . . . . . 36
   3.2.1.10. Two-point CDV/Mixed Load/Maximum VCCs . . . . . . . . . 38
   3.2.2. Cell Error Ratio (CER) . . . . . . . . . . . . . . . . . . 39
   3.2.2.1. Test Setup . . . . . . . . . . . . . . . . . . . . . . . 39
   3.2.2.2. CER/Steady Load/One VCC. . . . . . . . . . . . . . . . . 40
   3.2.2.3. CER/Steady Load/Twelve VCCs. . . . . . . . . . . . . . . 41
   3.2.2.4. CER/Steady Load/Maximum VCCs . . . . . . . . . . . . . . 42
   3.2.2.5. CER/Bursty VBR Load/One VCC. . . . . . . . . . . . . . . 43
   3.2.2.6. CER/Bursty VBR Load/Twelve VCCs. . . . . . . . . . . . . 44
   3.2.2.7. CER/Bursty VBR Load/Maximum VCCs . . . . . . . . . . . . 46



Dunn & Martin                Informational                      [Page 2]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   3.2.3. Cell Loss Ratio (CLR). . . . . . . . . . . . . . . . . . . 47
   3.2.3.1. CLR/Steady Load/One VCC. . . . . . . . . . . . . . . . . 47
   3.2.3.2. CLR/Steady Load/Twelve VCCs. . . . . . . . . . . . . . . 48
   3.2.3.3. CLR/Steady Load/Maximum VCCs . . . . . . . . . . . . . . 49
   3.2.3.4. CLR/Bursty VBR Load/One VCC. . . . . . . . . . . . . . . 51
   3.2.3.5. CLR/Bursty VBR Load/Twelve VCCs. . . . . . . . . . . . . 52
   3.2.3.6. CLR/Bursty VBR Load/Maximum VCCs . . . . . . . . . . . . 53
   3.2.4. Cell Misinsertion Rate (CMR) . . . . . . . . . . . . . . . 54
   3.2.4.1. CMR/Steady Load/One VCC. . . . . . . . . . . . . . . . . 54
   3.2.4.2. CMR/Steady Load/Twelve VCCs. . . . . . . . . . . . . . . 55
   3.2.4.3. CMR/Steady Load/Maximum VCCs . . . . . . . . . . . . . . 57
   3.2.4.4. CMR/Bursty VBR Load/One VCC. . . . . . . . . . . . . . . 58
   3.2.4.5. CMR/Bursty VBR Load/Twelve VCCs. . . . . . . . . . . . . 59
   3.2.4.6. CMR/Bursty VBR Load/Maximum VCCs . . . . . . . . . . . . 60
   3.2.5. CRC Error Ratio (CRC-ER) . . . . . . . . . . . . . . . . . 62
   3.2.5.1. CRC-ER/Steady Load/One VCC . . . . . . . . . . . . . . . 62
   3.2.5.2. CRC-ER/Steady Load/Twelve VCCs . . . . . . . . . . . . . 63
   3.2.5.3. CRC-ER/Steady Load/Maximum VCCs. . . . . . . . . . . . . 64
   3.2.5.4. CRC-ER/Bursty VBR Load/One VCC . . . . . . . . . . . . . 65
   3.2.5.5. CRC-ER/Bursty VBR Load/Twelve VCCs . . . . . . . . . . . 66
   3.2.5.6. CRC-ER/Bursty VBR Load/Maximum VCCs. . . . . . . . . . . 68
   3.2.5.7. CRC-ER/Bursty UBR Load/One VCC . . . . . . . . . . . . . 69
   3.2.5.8. CRC-ER/Bursty UBR Load/Twelve VCCs . . . . . . . . . . . 70
   3.2.5.9. CRC-ER/Bursty UBR Load/Maximum VCCs. . . . . . . . . . . 71
   3.2.5.10. CRC-ER/Bursty Mixed Load/Three VCC. . . . . . . . . . . 73
   3.2.5.11. CRC-ER/Bursty Mixed Load/Twelve VCCs. . . . . . . . . . 74
   3.2.5.12. CRC-ER/Bursty Mixed Load/Maximum VCCs . . . . . . . . . 75
   3.2.6. Cell Transfer Delay (CTD). . . . . . . . . . . . . . . . . 76
   3.2.6.1. Test Setup . . . . . . . . . . . . . . . . . . . . . . . 76
   3.2.6.2. CTD/Steady Load/One VCC. . . . . . . . . . . . . . . . . 77
   3.2.6.3. CTD/Steady Load/Twelve VCCs. . . . . . . . . . . . . . . 78
   3.2.6.4. CTD/Steady Load/Maximum VCCs . . . . . . . . . . . . . . 79
   3.2.6.5. CTD/Bursty VBR Load/One VCC. . . . . . . . . . . . . . . 81
   3.2.6.6. CTD/Bursty VBR Load/Twelve VCCs. . . . . . . . . . . . . 82
   3.2.6.7. CTD/Bursty VBR Load/Maximum VCCs . . . . . . . . . . . . 83
   3.2.6.8. CTD/Bursty UBR Load/One VCC. . . . . . . . . . . . . . . 85
   3.2.6.9. CTD/Bursty UBR Load/Twelve VCCs. . . . . . . . . . . . . 86
   3.2.6.10. CTD/Bursty UBR Load/Maximum VCCs. . . . . . . . . . . . 87
   3.2.6.11. CTD/Mixed Load/Three VCC's. . . . . . . . . . . . . . . 88
   3.2.6.12. CTD/Mixed Load/Twelve VCCs. . . . . . . . . . . . . . . 90
   3.2.6.13. CTD/Mixed Load/Maximum VCCs . . . . . . . . . . . . . . 91
   3.3. ATM Adaptation Layer (AAL) Type 5 (AAL5) . . . . . . . . . . 93
   3.3.1. IP Packet Loss due to AAL5 Re-assembly Errors. . . . . . . 93
   3.3.2. AAL5 Re-assembly Time. . . . . . . . . . . . . . . . . . . 94
   3.3.3. AAL5 CRC Error Ratio . . . . . . . . . . . . . . . . . . . 95
   3.3.3.1. Test Setup . . . . . . . . . . . . . . . . . . . . . . . 95
   3.3.3.2. AAL5-CRC-ER/Steady Load/One VCC. . . . . . . . . . . . . 95
   3.3.3.3. AAL5-CRC-ER/Steady Load/Twelve VCCs. . . . . . . . . . . 96



Dunn & Martin                Informational                      [Page 3]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   3.3.3.4. AAL5-CRC-ER/Steady Load/Maximum VCCs . . . . . . . . . . 97
   3.3.3.5. AAL5-CRC-ER/Bursty VBR Load/One VCC. . . . . . . . . . . 99
   3.3.3.6. AAL5-CRC-ER/Bursty VBR Load/Twelve VCCs. . . . . . . . .100
   3.3.3.7. AAL5-CRC-ER/Bursty VBR Load/Maximum VCCs . . . . . . . .101
   3.3.3.8. AAL5-CRC-ER/Mixed Load/Three VCC's . . . . . . . . . . .102
   3.3.3.9. AAL5-CRC-ER/Mixed Load/Twelve VCCs . . . . . . . . . . .104
   3.3.3.10. AAL5-CRC-ER/Mixed Load/Maximum VCCs . . . . . . . . . .105
   3.4. ATM Service: Signaling . . . . . . . . . . . . . . . . . . .106
   3.4.1. CAC Denial Time and Connection Establishment Time. . . . .106
   3.4.2. Connection Teardown Time . . . . . . . . . . . . . . . . .107
   3.4.3. Crankback Time . . . . . . . . . . . . . . . . . . . . . .108
   3.4.4. Route Update Response Time . . . . . . . . . . . . . . . .109
   3.5. ATM Service: ILMI. . . . . . . . . . . . . . . . . . . . . .110
   3.5.1. MIB Alignment Time . . . . . . . . . . . . . . . . . . . .110
   3.5.2. Address Registration Time. . . . . . . . . . . . . . . . .111
   4. Security Considerations  . . . . . . . . . . . . . . . . . . .112
   5. Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . .112
   6. References . . . . . . . . . . . . . . . . . . . . . . . . . .113
   7. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . .113
   APPENDIX A  . . . . . . . . . . . . . . . . . . . . . . . . . . .114
   APPENDIX B  . . . . . . . . . . . . . . . . . . . . . . . . . . .114
   APPENDIX C  . . . . . . . . . . . . . . . . . . . . . . . . . . .116
   Full Copyright Statement  . . . . . . . . . . . . . . . . . . . .127

1. Introduction

   This document defines a specific set of tests that vendors can use to
   measure and report the performance characteristics of ATM network
   devices.  The results of these tests will provide the user comparable
   data from different vendors with which to evaluate these devices.
   The methods defined in this memo are based on RFC 2544 "Benchmarking
   Methodology for Network Interconnect Devices".

   The document "Terminology for ATM Benchmarking" (RFC 2761), defines
   many of the terms that are used in this document.  The terminology
   document should be consulted before attempting to make use of this
   document.

   The BMWG produces two major classes of documents: Benchmarking
   Terminology documents and Benchmarking Methodology documents.  The
   Terminology documents present the benchmarks and other related terms.
   The Methodology documents define the procedures required to collect
   the benchmarks cited in the corresponding Terminology documents.








Dunn & Martin                Informational                      [Page 4]

RFC 3116            Methodology for ATM Benchmarking           June 2001


2. Background

2.1. Test Device Requirements

   This document is based on the requirement that a test device is
   available.  The test device can either be off the shelf or can be
   easily built with current technologies.  The test device must have a
   transmitting and receiving port for the interface type under test.
   The test device must be configured to transmit test PDUs and to
   analyze received PDUs.  The test device should be able to transmit
   and analyze received data at the same time.

2.2. Systems Under Test (SUTs)

   There are a number of tests described in this document that do not
   apply to each SUT.  Vendors should perform all of the tests that can
   be supported by a specific product type.  It will take some time to
   perform all of the recommended tests under all of the recommended
   conditions.

2.3. Test Result Evaluation

   Performing all of the tests in this document will result in a great
   deal of data.  The applicability of this data to the evaluation of a
   particular SUT will depend on its expected use and the configuration
   of the network in which it will be used.  For example, the time
   required by a switch to provide ILMI services will not be a pertinent
   measurement in a network that does not use the ILMI protocol, such as
   an ATM WAN.  Evaluating data relevant to a particular network
   installation may require considerable experience, which may not be
   readily available.  Finally, test selection and evaluation of test
   results must be done with an understanding of generally accepted
   testing practices regarding repeatability, variance and the
   statistical significance of a small numbers of trials.

2.4. Requirements

   In this document, the words that are used to define the significance
   of each particular requirement are capitalized.  These words are:

   *  "MUST" This word, or the words "REQUIRED" and "SHALL" mean that
      the item is an absolute requirement of the specification.

   *  "SHOULD" This word or the adjective "RECOMMENDED" means that there
      may exist valid reasons in particular circumstances to ignore this
      item, but the full implications should be understood and the case
      carefully weighed before choosing a different course.




Dunn & Martin                Informational                      [Page 5]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   *  "MAY" This word or the adjective "OPTIONAL" means that this item
      is truly optional.  One vendor may choose to include the item
      because a particular marketplace requires it or because it
      enhances the product, for example; another vendor may omit the
      same item.

   An implementation is not compliant if it fails to satisfy one or more
   of the MUST requirements for the protocols it implements.  An
   implementation that satisfies all the MUST and all the SHOULD
   requirements for its protocols is said to be "unconditionally
   compliant"; one that satisfies all the MUST requirements but not all
   the SHOULD requirements for its protocols is said to be
   "conditionally compliant".

2.5. Test Configurations for SONET

   The test device can be connected to the SUT in a variety of
   configurations depending on the test point.  The following
   configurations will be used for the tests described in this document.

   1) Uni-directional connection: The test devices transmit port
      (labeled Tx) is connected to the SUT receive port (labeled Rx).
      The SUTs transmit port is connected to the test device receive
      port (see Figure 1).  In this configuration, the test device can
      verify that all transmitted packets are acknowledged correctly.
      Note that this configuration does not verify internal system
      functions, but verifies one port on the SUT.

            +-------------+               +-------------+
            |           Tx|-------------->|Rx           |
            |    Test   Rx|<--------------|Tx   SUT     |
            |   Device    |               |             |
            +-------------+               +-------------+

                            Figure 1

   2) Bi-directional connection: The test devices first transmit port is
      connected to the SUTs first receive port.  The SUTs first transmit
      port is connected to the test devices first receive port.  The
      test devices second transmit port is connected to the SUTs second
      receive port.  The SUTs second transmit port is connected to the
      test devices second receive port (see Figure 2).  In this
      configuration, the test device can determine if all of the
      transmitted packets were received and forwarded correctly.  Note
      that this configuration does verify internal system functions,
      since it verifies two ports on the SUT.





Dunn & Martin                Informational                      [Page 6]

RFC 3116            Methodology for ATM Benchmarking           June 2001


            +-------------+               +-------------+
            |     Test  Tx|-------------->|Rx           |
            |    Device Rx|<--------------|Tx   SUT     |
            |    Tx   Rx  |               |   Tx   Rx   |
            +-------------+               +-------------+
                  |   ^                        |    ^
                  |   |                        |    |
                  |   +------------------------+    |
                  |                                 |
                  |---------------------------------|

                             Figure 2

   3) Uni-directional passthrough connection: The test devices first
      transmit port is connected to the SUT1 receive port.  The SUT1
      transmit port is connected to the test devices first receive port.
      The test devices second transmit port is connected to the SUT2
      receive port.  The SUT2 transmit port is connected to the test
      devices second receive port (see Figure 3).  In this
      configuration, the test device can determine if all of the packets
      transmitted by SUT1 were correctly acknowledged by SUT2.  Note
      that this configuration does not verify internal system functions,
      but verifies one port on each SUT.

   +-------------+           +-------------+           +-------------+
   |           Tx|---------->|Rx         Tx|---------->|Rx           |
   |     SUT1  Rx|<----------|Tx   Test  Rx|<----------|Tx   SUT2    |
   |             |           |    Device   |           |             |
   +-------------+           +-------------+           +-------------+

                              Figure 3

2.6. SUT Configuration

   The SUT MUST be configured as described in the SUT users guide.
   Specifically, it is expected that all of the supported protocols will
   be configured and enabled.  It is expected that all of the tests will
   be run without changing the configuration or setup of the SUT in any
   way other than that required to do the specific test.  For example,
   it is not acceptable to disable all but one transport protocol when
   testing the throughput of that protocol.  If PNNI or BISUP is used to
   initiate switched virtual connections (SVCs), the SUT configuration
   SHOULD include the normally recommended routing update intervals and
   keep alive frequency.  The specific version of the software and the
   exact SUT configuration, including what functions are disabled and
   used during the tests MUST be included as part of the report of the
   results.




Dunn & Martin                Informational                      [Page 7]

RFC 3116            Methodology for ATM Benchmarking           June 2001


2.7. Frame formats

   The formats of the test IP PDUs to use for TCP/IP and UPC/IP over ATM
   are shown in Appendix C: Test Frame Formats.  Note that these IP PDUs
   are in accordance with RFC 2225.  These exact IP PDU formats SHOULD
   be used in the tests described in this document for this
   protocol/media combination.  These IP PDUs will be used as a template
   for testing other protocol/media combinations.  The specific formats
   that are used to define the test IP PDUs for a particular test series
   MUST be included in the report of the results.

2.8. Frame sizes

   All of the described tests SHOULD be performed using a number of IP
   PDU sizes.  Specifically, the sizes SHOULD include the maximum and
   minimum legitimate sizes for the protocol under test on the media
   under test and enough sizes in between to be able to get a full
   characterization of the SUT performance.  Except where noted, at
   least five IP PDU sizes SHOULD be tested for each test condition.

   Theoretically the minimum size UDP Echo request IP PDU would consist
   of an IP header (minimum length 20 octets), a UDP header (8 octets),
   AAL5 trailer (8 octets) and an LLC/SNAP code point header (8 octets);
   therefore, the minimum size PDU will fit into one ATM cell.  The
   theoretical maximum IP PDU size is determined by the size of the
   length field in the IP header.  In almost all cases the actual
   maximum and minimum sizes are determined by the limitations of the
   media.  In the case of ATM, the maximum IP PDU size SHOULD be the ATM
   MTU size, which is 9180 octets.

   In theory it would be ideal to distribute the IP PDU sizes in a way
   that would evenly distribute the theoretical IP PDU rates.  These
   recommendations incorporate this theory but specify IP PDU sizes,
   which are easy to understand and remember.  In addition, many of the
   same IP PDU sizes are specified on each of the media types to allow
   for easy performance comparisons.

   Note: The inclusion of an unrealistically small IP PDU size on some
   of the media types (i.e., with little or no space for data) is to
   help characterize the per-IP PDU processing overhead of the SUT.

   The IP PDU sizes that will be used are:

   44, 64, 128, 256, 1024, 1518, 2048, 4472, 9180

   The minimum size IP PDU for UDP on ATM is 44 octets, the minimum size
   of 44 is recommended to allow direct comparison to token ring
   performance.  The IP PDU size of 4472 is recommended instead of the



Dunn & Martin                Informational                      [Page 8]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   theoretical FDDI maximum size of 4500 octets in order to permit the
   same type of comparison.  An IP (i.e., not UDP) IP PDU may be used in
   addition if a higher data rate is desired, in which case the minimum
   IP PDU size is 28 octets.

2.9. Verifying received IP PDUs

   The test equipment SHOULD discard any IP PDUs received during a test
   run that are not actual forwarded test IP PDUs.  For example, keep-
   alive and routing update IP PDUs SHOULD NOT be included in the count
   of received IP PDUs.  In any case, the test equipment SHOULD verify
   the length of the received IP PDUs and check that they match the
   expected length.

   Preferably, the test equipment SHOULD include sequence numbers in the
   transmitted IP PDUs and check for these numbers on the received IP
   PDUs.  If this is done, the reported results SHOULD include, in
   addition to the number of IP PDUs dropped, the number of IP PDUs that
   were received out of order, the number of duplicate IP PDUs received
   and the number of gaps in the received IP PDU numbering sequence.
   This functionality is required for some of the described tests.

2.10. Modifiers

   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.

2.10.1. Management IP PDUs

   Most ATM data networks now make use of ILMI, signaling and OAM.  In
   many environments, there can be a number of management stations
   sending queries to the same SUT at the same time.

   Management queries MUST be made in accordance with the applicable
   specification, e.g., ILMI sysUpTime getNext requests will be made in
   accordance with ILMI 4.0.  The response to the query MUST be verified
   by the test equipment.  Note that, for each management protocol in





Dunn & Martin                Informational                      [Page 9]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   use, this requires that the test equipment implement the associated
   protocol state machine.  One example of the specific query IP PDU
   (ICMP) that should be used is shown in Appendix C.

2.10.2. Routing update IP PDUs

   The processing of PNNI updates could have a significant impact on the
   ability of a switch to forward cells and complete calls.  If PNNI is
   configured on the SUT, one routing update MUST be transmitted before
   the first test IP PDU is transmitted during the trial.  The test
   SHOULD verify that the SUT has properly processed the routing update.

   PNNI routing update IP PDUs SHOULD be sent at the rate specified in
   Appendix B.  Appendix C defines one routing update PDU for the TCP/IP
   over ATM example.  The routing updates are designed to change the
   routing on a number of networks that are not involved in the
   forwarding of the test data.  The first IP PDU sets the routing table
   state to "A", the second one changes the state to "B".  The IP PDUs
   MUST be alternated during the trial.  The test SHOULD verify that the
   SUT has properly processed the routing update.

2.11. Filters

   Filters are added to switches to selectively inhibit the forwarding
   of cells that would normally be forwarded.  This is usually done to
   implement security controls on the data that is accepted between one
   area and another.  Different products have different capabilities to
   implement filters.  Filters are applicable only if the SUT supports
   the filtering feature.

   The SUT SHOULD be first configured to add one filter condition and
   the tests performed.  This filter SHOULD permit the forwarding of the
   test data stream.  This filter SHOULD be of the form as described in
   the SUT Users Guide.

   The SUT SHOULD be then reconfigured to implement a total of 25
   filters.  The first 24 of these filters SHOULD be based on 24
   separate ATM NSAP Network Prefix addresses.

   The 24 ATM NSAP Network Prefix 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 over ATM 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.



Dunn & Martin                Informational                     [Page 10]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   The exact filters configuration command lines used SHOULD be included
   with the report of the results.

2.11.1. Filter Addresses

   Two sets of filter addresses are required, one for the single filter
   case and one for the 25 filter case.

   The single filter case should permit traffic from ATM address [Switch
   Network Prefix] 00 00 00 00 00 01 00 to ATM address [Switch Network
   Prefix] 00 00 00 00 00 02 00 and deny all other traffic.  Note that
   the 13 octet Switch Network Prefix MUST be configured before this
   test can be run.

   The 25 filter case should follow the following sequence.

         deny [Switch Network Prefix] 00 00 00 00 00 01 00
              to [Switch Network Prefix] 00 00 00 00 00 03 00
         deny [Switch Network Prefix] 00 00 00 00 00 01 00
              to [Switch Network Prefix] 00 00 00 00 00 04 00
         deny [Switch Network Prefix] 00 00 00 00 00 01 00
              to [Switch Network Prefix] 00 00 00 00 00 05 00
         ...
         deny [Switch Network Prefix] 00 00 00 00 00 01 00
              to [Switch Network Prefix] 00 00 00 00 00 0C 00
         deny [Switch Network Prefix] 00 00 00 00 00 01 00
              to [Switch Network Prefix] 00 00 00 00 00 0D 00
         allow [Switch Network Prefix] 00 00 00 00 00 01 00
              to [Switch Network Prefix] 00 00 00 00 00 02 00
         deny [Switch Network Prefix] 00 00 00 00 00 01 00
              to [Switch Network Prefix] 00 00 00 00 00 0E 00
         deny [Switch Network Prefix] 00 00 00 00 00 01 00
              to [Switch Network Prefix] 00 00 00 00 00 0F 00
          ...
         deny [Switch Network Prefix] 00 00 00 00 00 01 00
              to [Switch Network Prefix] 00 00 00 00 00 18 00
         deny all else

   All previous filter conditions should be cleared from the switch
   before this sequence is entered.  The sequence is selected to test to
   see if the switch sorts the filter conditions or accepts them in the
   order that they were entered.  Both of these procedures will result
   in a greater impact on performance than will some form of hash
   coding.







Dunn & Martin                Informational                     [Page 11]

RFC 3116            Methodology for ATM Benchmarking           June 2001


2.12. Protocol addresses

   It is easier to implement these tests using a single logical stream
   of data, with one source ATM address and one destination ATM address,
   and for some conditions like the filters described above, a practical
   requirement.  Networks in the real world are not limited to single
   streams of data.  The test suite SHOULD be first run with a single
   ATM source and destination address pair.  The tests SHOULD then be
   repeated with using a random destination address.  In the case of
   testing single switches, the addresses SHOULD be random and uniformly
   distributed over a range of 256 seven octet user parts.  In the case
   of testing multiple interconnected switches, the addresses SHOULD be
   random and uniformly distributed over the 256 network prefixes, each
   of which should support 256 seven octet user parts.  The specific
   address ranges to use for ATM are shown in Appendix A.  IP to ATM
   address mapping MUST be accomplished as described in RFC 2225.

2.13. Route Set Up

   It is not reasonable that all of the routing information necessary to
   forward the test stream, especially in the multiple address case,
   will be manually set up.  If PNNI and/or ILMI are running, at the
   start of each trial a routing update MUST be sent to the SUT.  This
   routing update MUST include all of the ATM addresses that will be
   required for the trial.  This routing update will have to be repeated
   at the interval required by PNNI or ILMI.  An example of the format
   and repetition interval of the update IP PDUs is given in Appendix B
   (interval and size) and Appendix C (format).

2.14. Bidirectional traffic

   Bidirectional performance tests SHOULD be run with the same data rate
   being offered from each direction.  The sum of the data rates should
   not exceed the theoretical limit for the media.

2.15. Single stream path

   The full suite of tests SHOULD be run with the appropriate modifiers
   for a single receive and transmit port on the SUT.  If the internal
   design of the SUT has multiple distinct pathways, for example,
   multiple interface cards each with multiple network ports, then all
   possible permutations of pathways SHOULD be tested separately.  If
   multiple interconnected switches are tested, the test MUST specify
   routes, which allow only one path between source and destination ATM
   addresses.






Dunn & Martin                Informational                     [Page 12]

RFC 3116            Methodology for ATM Benchmarking           June 2001


2.16. Multi-port

   Many switch products provide several network ports on the same
   interface module.  Each port on an interface module SHOULD be
   stimulated in an identical manner.  Specifically, half of the ports
   on each module SHOULD be receive ports and half SHOULD be transmit
   ports.  For example if a SUT has two interface module each of which
   has four ports, two ports on each interface module be receive ports
   and two will be transmit ports.  Each receive port MUST be offered
   the same data rate.  The addresses in the input data streams SHOULD
   be set so that an IP PDU will be directed to each of the transmit
   ports in sequence.  That is, all transmit ports will receive an
   identical distribution of IP PDUs from a particular receive port.

   Consider the following 6 port SUT:

               --------------
      ---------| Rx A   Tx X|--------
      ---------| Rx B   Tx Y|--------
      ---------| Rx C   Tx Z|--------
               --------------

   The addressing of the data streams for each of the inputs SHOULD be:

      stream sent to Rx A:
        IP PDU to Tx X, IP PDU to Tx Y, IP PDU to Tx Z
      stream sent to Rx B:
        IP PDU to Tx X, IP PDU to Tx Y, IP PDU to Tx Z
      stream sent to Rx C
        IP PDU to Tx X, IP PDU to Tx Y, IP PDU to Tx Z

   Note: Each stream contains the same sequence of IP destination
   addresses; therefore, each transmit port will receive 3 IP PDUs
   simultaneously.  This procedure ensures that the SUT will have to
   process multiple IP PDUs addressed to the same transmit port
   simultaneously.

   The same configuration MAY be used to perform a bi-directional
   multi-stream test.  In this case all of the ports are considered both
   receive and transmit ports.  Each data stream MUST consist of IP PDUs
   whose addresses correspond to the ATM addresses all of the other
   ports.









Dunn & Martin                Informational                     [Page 13]

RFC 3116            Methodology for ATM Benchmarking           June 2001


2.17. Multiple protocols

   This document does not address the issue of testing the effects of a
   mixed protocol environment other than to suggest that if such tests
   are wanted then PDUs SHOULD be distributed between all of the test
   protocols.  The distribution MAY approximate the conditions on the
   network in which the SUT would be used.

2.18. Multiple IP PDU sizes

   This document does not address the issue of testing the effects of a
   mixed IP PDU size environment other than to suggest that, if such
   tests are required, then IP PDU size SHOULD be evenly distributed
   among all of the PDU sizes listed in this document.  The distribution
   MAY approximate the conditions on the network in which the SUT would
   be used.

2.19. Testing beyond a single SUT

   In the performance testing of a single SUT, the paradigm can be
   described as applying some input to a SUT and monitoring the output.
   The results of which can be used to form a basis of characterization
   of that device under those test conditions.

   This model is useful when the test input and output are homogeneous
   (e.g., 64-byte IP, AAL5 PDUs into the SUT; 64 byte IP, AAL5 PDUs
   out).

   By extending the single SUT test model, reasonable benchmarks
   regarding multiple SUTs or heterogeneous environments may be
   collected.  In this extension, the single SUT is replaced by a system
   of interconnected network SUTs.  This test methodology would support
   the benchmarking of a variety of device/media/service/protocol
   combinations.  For example, a configuration for a LAN-to-WAN-to-LAN
   test might be:

      (1) ATM UNI -> SUT 1 -> BISUP -> SUT 2 -> ATM UNI

   Or an extended LAN configuration might be:

      (2) ATM UNI -> SUT 1 -> PNNI Network -> SUT 2 -> ATM UNI

   In both examples 1 and 2, end-to-end benchmarks of each system could
   be empirically ascertained.  Other behavior may be characterized
   through the use of intermediate devices.  In example 2, the
   configuration may be used to give an indication of the effect of PNNI
   routing on IP throughput.




Dunn & Martin                Informational                     [Page 14]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   Because multiple SUTs are treated as a single system, there are
   limitations to this methodology.  For instance, this methodology may
   yield an aggregate benchmark for a tested system.  That benchmark
   alone, however, may not necessarily reflect asymmetries in behavior
   between the SUTs, latencies introduced by other apparatus (e.g.,
   CSUs/DSUs, switches), etc.

   Further, care must be used when comparing benchmarks of different
   systems by ensuring that the SUTs' features and configuration of the
   tested systems have the appropriate common denominators to allow
   comparison.

2.20. Maximum IP PDU rate

   The maximum IP PDU rates that should be used when testing LAN
   connections SHOULD be the listed theoretical maximum rate for the IP
   PDU size on the media.

   The maximum IP PDU rate that should be used when testing WAN
   connections SHOULD be greater than the listed theoretical maximum
   rate for the IP PDU size on that speed connection.  The higher rate
   for WAN tests is to compensate for the fact that some vendors employ
   various forms of header compression.

   A list of maximum IP PDU rates for LAN connections is included in
   Appendix B.

2.21. Bursty traffic

   It is convenient to measure the SUT performance under steady state
   load; however, this is an unrealistic way to gauge the functioning of
   a SUT.  Actual network traffic normally consists of bursts of IP
   PDUs.

   Some of the tests described below SHOULD be performed with both
   constant bit rate, bursty Unspecified Bit Rate (UBR) Best Effort
   [AF-TM4.1] and Variable Bit Rate Non-real Time (VBR-nrt) Best Effort
   [AF-TM4.1].  The IP PDUs within a burst are transmitted with the
   minimum legitimate inter-IP PDU gap.

   The objective of the test is to determine the minimum interval
   between bursts that the SUT can process with no IP PDU loss.  Tests
   SHOULD be run with burst sizes of 10% of Maximum Burst Size (MBS),
   20% of MBS, 50% of MBS and 100% MBS.  Note that the number of IP PDUs
   in each burst will depend on the PDU size.  For UBR, the MBS refers
   to the associated VBR traffic parameters.





Dunn & Martin                Informational                     [Page 15]

RFC 3116            Methodology for ATM Benchmarking           June 2001


2.22. Trial description

   A particular test consists of multiple trials.  Each trial returns
   one piece of information, for example the loss rate at a particular
   input IP PDU rate.  Each trial consists of five of phases:

   a) If the SUT is a switch supporting PNNI, send the routing update to
      the SUT receive port and wait two seconds to be sure that the
      routing has settled.

   b) Send an ATM ARP PDU to determine the ATM address corresponding to
      the destination IP address.  The formats of the ATM ARP PDU that
      should be used are shown in the Test Frame Formats document and
      MUST be in accordance with RFC 2225.

   c) Stimulate SUT with traffic load.

   d) Wait for two seconds for any residual IP PDUs to be received.

   e) Wait for at least five seconds for the SUT to restabilize.

2.23. Trial duration

   The objective of the tests defined in this document is to accurately
   characterize the behavior of a particular piece of network equipment
   under varying traffic loads.  The choice of test duration must be a
   compromise between this objective and keeping the duration of the
   benchmarking test suite within reasonable bounds.  The SUT SHOULD be
   stimulated for at least 60 seconds.  If this time period results in a
   high variance in the test results, the SUT SHOULD be stimulated for
   at least 300 seconds.

2.24. Address resolution

   The SUT MUST be able to respond to address resolution requests sent
   by another SUT, an ATM ARP server or the test equipment in accordance
   with RFC 2225.

2.25. Synchronized Payload Bit Pattern.

   Some measurements assume that both the transmitter and receiver
   payload information is synchronized.  Synchronization MUST be
   achieved by supplying a known bit pattern to both the transmitter and
   receiver.  This bit pattern MUST be one of the following: PRBS-15,
   PRBS-23, 0xFF00, or 0xAA55.






Dunn & Martin                Informational                     [Page 16]

RFC 3116            Methodology for ATM Benchmarking           June 2001


2.26. Burst Traffic Descriptors.

   Some measurements require busty traffic patterns.  These patterns
   MUST conform to one of the following traffic descriptors:

1) PCR=100% allotted line rate, SCR=50% allotted line rate, and MBS=8192

2) PCR=100% allotted line rate, SCR=50% allotted line rate, and MBS=4096

3) PCR=90% allotted line rate, SCR=50% allotted line rate, and MBS=8192

4) PCR=90% allotted line rate, SCR=50% allotted line rate, and MBS=4096

5) PCR=90% allotted line rate, SCR=45% allotted line rate, and MBS=8192

6) PCR=90% allotted line rate, SCR=45% allotted line rate, and MBS=4096

7) PCR=80% allotted line rate, SCR=40% allotted line rate, and MBS=65536

8) PCR=80% allotted line rate, SCR=40% allotted line rate, and MBS=32768

   The allotted line rate refers to the total available line rate
   divided by the number of VCCs in use.

3. Performance Metrics

3.1. Physical Layer-SONET

3.1.1. Pointer Movements

3.1.1.1. Pointer Movement Propagation.

   Objective: To determine that the SUT does not propagate pointer
   movements as defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the uni-directional
       configuration.

   2)  Send a specific number of IP PDUs at a specific rate through the
       SUT.  Since this test is not a throughput test, the rate should
       not be greater than 90% of line rate.  The cell payload SHOULD
       contain valid IP PDUs.  The IP PDUs MUST be encapsulated in AAL5.







Dunn & Martin                Informational                     [Page 17]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   3)  Count the IP PDUs that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test, else lower the test device
       traffic rate until the counts are the same.

   4)  Inject one forward payload pointer movement.  Verify that the SUT
       does not change the pointer.

   5)  Inject one forward payload pointer movement every 1 second.
       Verify that the SUT does not change the pointer.

   6)  Discontinue the payload pointer movement.

   7)  Inject five forward payload pointer movements every 1 second.
       Verify that the SUT does not change the pointer.

   8)  Discontinue the payload pointer movement.

   9)  Inject one backward payload pointer movement.  Verify that the
       SUT does not change the pointer.

   10) Inject one backward payload pointer movement every 1 second.
       Verify that the SUT does not change the pointer.

   11) Discontinue the payload pointer movement.

   12) Inject five backward payload pointer movements every 1 second.
       Verify that the SUT does not change the pointer.

   13) Discontinue the payload pointer movement.

   Reporting Format:

      The results of the pointer movement propagation test SHOULD be
      reported in a form of a table.  The rows SHOULD be labeled single
      pointer movement, one pointer movement per second, and five
      pointer movements per second.  The columns SHOULD be labeled
      pointer movement and loss of pointer.  The elements of the table
      SHOULD be either True or False, indicating whether the particular
      condition was observed for each test.

      The table MUST also indicate the IP PDU size in octets and traffic
      rate in IP PDUs per second as generated by the test device.








Dunn & Martin                Informational                     [Page 18]

RFC 3116            Methodology for ATM Benchmarking           June 2001


3.1.1.2. Cell Loss due to Pointer Movement.

   Objective: To determine if the SUT will drop cells due to pointer
   movements as defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the uni-directional
       configuration.

   2)  Send a specific number of cells at a specific rate through the
       SUT.  Since this test is not a throughput test, the rate should
       not be greater than 90% of line rate.  The cell payload SHOULD
       contain valid IP PDUs.  The IP PDUs MUST be encapsulated in AAL5.

   3)  Count the cells that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   4)  Inject one forward payload pointer movement.  Verify that the SUT
       does not drop any cells.

   5)  Inject one forward payload pointer movement every 1 second.
       Verify that the SUT does not drop any cells.

   6)  Discontinue the payload pointer movement.

   7)  Inject five forward payload pointer movements every 1 second.
       Verify that the SUT does not drop any cells.

   8)  Discontinue the payload pointer movement.

   9)  Inject one backward payload pointer movement.  Verify that the
       SUT does not drop any cells.

   10) Inject one backward payload pointer movement every 1 second.
       Verify that the SUT does not drop any cells.

   11) Discontinue the payload pointer movement.

   12) Inject five backward payload pointer movements every 1 second.
       Verify that the SUT does not drop any cells.

   13) Discontinue the payload pointer movement.






Dunn & Martin                Informational                     [Page 19]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   Reporting Format:

      The results of the cell loss due to pointer movement test SHOULD
      be reported in a form of a table.  The rows SHOULD be labeled
      single pointer movement, one pointer movement per second, and five
      pointer movements per second.  The columns SHOULD be labeled cell
      loss and number of cells lost.  The elements of column 1 SHOULD be
      either True or False, indicating whether the particular condition
      was observed for each test.  The elements of column 2 SHOULD be
      non-negative integers.

      The table MUST also indicate the traffic rate in IP PDUs per
      second as generated by the test device.

3.1.1.3. IP Packet Loss due to Pointer Movement.

   Objective: To determine if the SUT will drop IP packets due to
   pointer movements as defined in RFC 2761 "Terminology for ATM
   Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the uni-directional
       configuration.

   2)  Send a specific number of IP packets at a specific rate through
       the SUT.  Since this test is not a throughput test, the rate
       should not be greater than 90% of line rate.  The IP PDUs MUST be
       encapsulated in AAL5.

   3)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   4)  Inject one forward payload pointer movement.  Verify that the SUT
       does not drop any packets.

   5)  Inject one forward payload pointer movement every 1 second.
       Verify that the SUT does not drop any packets.

   6)  Discontinue the payload pointer movement.

   7)  Inject five forward payload pointer movements every 1 second.
       Verify that the SUT does not drop any packets.

   8)  Discontinue the payload pointer movement.




Dunn & Martin                Informational                     [Page 20]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   9)  Inject one backward payload pointer movement.  Verify that the
       SUT does not drop any packets.

   10) Inject one backward payload pointer movement every 1 second.
       Verify that the SUT does not drop any packets.

   11) Discontinue the payload pointer movement.

   12) Inject five backward payload pointer movements every 1 second.
       Verify that the SUT does not drop any packets.

   13) Discontinue the payload pointer movement.

   Reporting Format:

      The results of the IP packet loss due to pointer movement test
      SHOULD be reported in a form of a table.  The rows SHOULD be
      labeled single pointer movement, one pointer movement per second,
      and five pointer movements per second.  The columns SHOULD be
      labeled packet loss and number of packets lost.  The elements of
      column 1 SHOULD be either True or False, indicating whether the
      particular condition was observed for each test.  The elements of
      column 2 SHOULD be non-negative integers.

      The table MUST also indicate the packet size in octets and traffic
      rate in packets per second as generated by the test device.

3.1.2. Transport Overhead (TOH) Error Count

3.1.2.1. TOH Error Propagation.

   Objective: To determine that the SUT does not propagate TOH errors as
   defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the uni-directional
       configuration.

   2)  Send a specific number of IP PDUs at a specific rate through the
       SUT.  Since this test is not a throughput test, the rate should
       not be greater than 90% of line rate.  The cell payload SHOULD
       contain valid IP PDUs.  The IP PDUs MUST be encapsulated in AAL5.

   3)  Count the IP PDUs that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test, else lower the test device
       traffic rate until the counts are the same.



Dunn & Martin                Informational                     [Page 21]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   4)  Inject one error in the first bit of the A1 and A2 Frameword.
       Verify that the SUT does not propagate the error.

   5)  Inject one error in the first bit of the A1 and A2 Frameword
       every 1 second.  Verify that the SUT does not propagate the
       error.

   6)  Discontinue the Frameword error.

   7)  Inject one error in the first bit of the A1 and A2 Frameword for
       4 consecutive IP PDUs in every 6 IP PDUs.  Verify that the SUT
       indicates Loss of Frame.

   8)  Discontinue the Frameword error.

   Reporting Format:

      The results of the TOH error propagation test SHOULD be reported
      in a form of a table.  The rows SHOULD be labeled single error,
      one error per second, and four consecutive errors every 6 IP PDUs.
      The columns SHOULD be labeled error propagated and loss of IP PDU.
      The elements of the table SHOULD be either True or False,
      indicating whether the particular condition was observed for each
      test.

      The table MUST also indicate the IP PDU size in octets and traffic
      rate in IP PDUs per second as generated by the test device.

3.1.2.2. c TOH Error.

   Objective: To determine if the SUT will drop cells due TOH Errors as
   defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the uni-directional
       configuration.

   2)  Send a specific number of cells at a specific rate through the
       SUT.  Since this test is not a throughput test, the rate should
       not be greater than 90% of line rate.  The cell payload SHOULD
       contain valid IP PDUs.  The IP PDUs MUST be encapsulated in AAL5.

   3)  Count the cells that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.




Dunn & Martin                Informational                     [Page 22]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   4)  Inject one error in the first bit of the A1 and A2 Frameword.
       Verify that the SUT does not drop any cells.

   5)  Inject one error in the first bit of the A1 and A2 Frameword
       every 1 second.  Verify that the SUT does not drop any cells.

   6)  Discontinue the Frameword error.

   7)  Inject one error in the first bit of the A1 and A2 Frameword for
       4 consecutive IP PDUs in every 6 IP PDUs.  Verify that the SUT
       does drop cells.

   8)  Discontinue the Frameword error.

   Reporting Format:

      The results of the Cell Loss due to TOH errors test SHOULD be
      reported in a form of a table.  The rows SHOULD be labeled single
      error, one error per second, and four consecutive errors every 6
      IP PDUs.  The columns SHOULD be labeled cell loss and number of
      cells lost.  The elements of column 1 SHOULD be either True or
      False, indicating whether the particular condition was observed
      for each test.  The elements of column 2 SHOULD be non-negative
      integers.

      The table MUST also indicate the traffic rate in IP PDUs per
      second as generated by the test device.

3.1.2.3. IP Packet Loss due to TOH Error.

   Objective: To determine if the SUT will drop IP packets due to TOH
   errors as defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the uni-directional
       configuration.

   2)  Send a specific number of IP packets at a specific rate through
       the SUT.  Since this test is not a throughput test, the rate
       should not be greater than 90% of line rate.  The IP PDUs MUST be
       encapsulated in AAL5.

   3)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.




Dunn & Martin                Informational                     [Page 23]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   4)  Inject one error in the first bit of the A1 and A2 Frameword.
       Verify that the SUT does not drop any packets.

   5)  Inject one error in the first bit of the A1 and A2 Frameword
       every 1 second.  Verify that the SUT does not drop any packets.

   6)  Discontinue the Frameword error.

   7)  Inject one error in the first bit of the A1 and A2 Frameword for
       4 consecutive IP PDUs in every 6 IP PDUs.  Verify that the SUT
       does drop packets.

   8)  Discontinue the Frameword error.

   Reporting Format:

      The results of the IP packet loss due to TOH errors test SHOULD be
      reported in a form of a table.  The rows SHOULD be labeled single
      error, one error per second, and four consecutive errors every 6
      IP PDUs.  The columns SHOULD be labeled packet loss and number of
      packets lost.  The elements of column 1 SHOULD be either True or
      False, indicating whether the particular condition was observed
      for each test.  The elements of column 2 SHOULD be non-negative
      integers.

      The table MUST also indicate the packet size in octets and traffic
      rate in packets per second as generated by the test device.

3.1.3. Path Overhead (POH) Error Count

3.1.3.1. POH Error Propagation.

   Objective: To determine that the SUT does not propagate POH errors as
   defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the uni-directional
       configuration.

   2)  Send a specific number of IP PDUs at a specific rate through the
       SUT.  Since this test is not a throughput test, the rate should
       not be greater than 90% of line rate.  The cell payload SHOULD
       contain valid IP PDUs.  The IP PDUs MUST be encapsulated in AAL5.







Dunn & Martin                Informational                     [Page 24]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   3)  Count the IP PDUs that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test, else lower the test device
       traffic rate until the counts are the same.

   4)  Inject one error in the B3 (Path BIP8) byte.  Verify that the SUT
       does not propagate the error.

   5)  Inject one error in the B3 byte every 1 second.  Verify that the
       SUT does not propagate the error.

   6)  Discontinue the POH error.

   Reporting Format:

       The results of the POH error propagation test SHOULD be reported
       in a form of a table.  The rows SHOULD be labeled single error
       and one error per second.  The columns SHOULD be labeled error
       propagated and loss of IP PDU.  The elements of the table SHOULD
       be either True or False, indicating whether the particular
       condition was observed for each test.

       The table MUST also indicate the IP PDU size in octets and
       traffic rate in IP PDUs per second as generated by the test
       device.

3.1.3.2. Cell Loss due to POH Error.

   Objective: To determine if the SUT will drop cells due POH Errors as
   defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the uni-directional
       configuration.

   2)  Send a specific number of cells at a specific rate through the
       SUT.  Since this test is not a throughput test, the rate should
       not be greater than 90% of line rate.  The cell payload SHOULD
       contain valid IP PDUs.  The IP PDUs MUST be encapsulated in AAL5.

   3)  Count the cells that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   4)  Inject one error in the B3 (Path BIP8) byte.  Verify that the SUT
       does not drop any cells.



Dunn & Martin                Informational                     [Page 25]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   5)  Inject one error in the B3 byte every 1 second.  Verify that the
       SUT does not drop any cells.

   6)  Discontinue the POH error.

   Reporting Format:

      The results of the Cell Loss due to POH errors test SHOULD be
      reported in a form of a table.  The rows SHOULD be labeled single
      error and one error per second.  The columns SHOULD be labeled
      cell loss and number of cells lost.  The elements of column 1
      SHOULD be either True or False, indicating whether the particular
      condition was observed for each test.  The elements of column 2
      SHOULD be non-negative integers.

      The table MUST also indicate the traffic rate in IP PDUs per
      second as generated by the test device.

3.1.3.3. IP Packet Loss due to POH Error.

   Objective: To determine if the SUT will drop IP packets due to POH
   errors as defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the uni-directional
       configuration.

   2)  Send a specific number of IP packets at a specific rate through
       the SUT.  Since this test is not a throughput test, the rate
       should not be greater than 90% of line rate.  The IP PDUs MUST be
       encapsulated in AAL5.

   3)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   4)  Inject one error in the B3 (Path BIP8) byte.  Verify that the SUT
       does not drop any packets.

   5)  Inject one error in the B3 byte every 1 second.  Verify that the
       SUT does not drop any packets.

   6)  Discontinue the POH error.






Dunn & Martin                Informational                     [Page 26]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   Reporting Format:

      The results of the IP packet loss due to POH errors test SHOULD be
      reported in a form of a table.  The rows SHOULD be labeled single
      error and one error per second.  The columns SHOULD be labeled
      packet loss and number of packets lost.  The elements of column 1
      SHOULD be either True or False, indicating whether the particular
      condition was observed for each test.  The elements of column 2
      SHOULD be non-negative integers.

      The table MUST also indicate the packet size in octets and traffic
      rate in packets per second as generated by the test device.

3.2. ATM Layer

3.2.1. Two-Point Cell Delay Variation (CDV)

3.2.1.1. Test Setup

   The cell delay measurements assume that both the transmitter and
   receiver timestamp information is synchronized.  Synchronization
   SHOULD be achieved by supplying a common clock signal (minimum of 100
   Mhz or 10 ns resolution) to both the transmitter and receiver.  The
   maximum timestamp values MUST be recorded to ensure synchronization
   in the case of counter rollover.  The cell delay measurements SHOULD
   utilize the O.191 cell (ITUT-O.191) encapsulated in a valid IP
   packet.  If the O.191 cell is not available, a test cell encapsulated
   in a valid IP packet MAY be used.  The test cell MUST contain a
   transmit timestamp which can be correlated with a receive timestamp.
   A description of the test cell MUST be included in the test results.
   The description MUST include the timestamp length (in bits), counter
   rollover value, and the timestamp accuracy (in ns).

3.2.1.2. Two-point CDV/Steady Load/One VCC

   Objective: To determine the SUT variation in cell transfer delay with
   one VCC as defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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,
       VBR, or UBR connection.  The VPI/VCI MUST not be one of the
       reserved ATM signaling channels (e.g., [0,5], [0,16]).




Dunn & Martin                Informational                     [Page 27]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   3)  Send a specific number of IP packets containing timestamps at a
       specific constant rate through the SUT via the defined test VCC.
       Since this test is not a throughput test, the rate should not be
       greater than 90% of line rate.  The IP PDUs MUST be encapsulated
       in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device.

   Reporting Format:

      The results of the Two-point CDV/Steady Load/One VCC test SHOULD
      be reported in a form of text, graph, and histogram.

      The text results SHOULD display the numerical values of the CDV.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, maximum
      and minimum CDV during the test in us, and peak-to-peak CDV in us.

      The graph results SHOULD display the cell delay values.  The x-
      coordinate SHOULD be the test run time in either seconds, minutes
      or days depending on the total length of the test.  The x-
      coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the cell delay in us.  The integration time per point MUST be
      indicated.

      The histogram results SHOULD display the peak-to-peak cell delay.
      The x-coordinate SHOULD be the cell delay in us with at least 256
      bins.  The y-coordinate SHOULD be the number of cells observed in
      each bin.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      bearer class of the created VCC MUST also be indicated.

3.2.1.3. Two-point CDV/Steady Load/Twelve VCCs

   Objective: To determine the SUT variation in cell transfer delay with
   twelve VCCs as defined in RFC 2761 "Terminology for ATM
   Benchmarking".




Dunn & Martin                Informational                     [Page 28]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing timestamps at a
       specific constant rate through the SUT via the defined test VCCs.
       All of the VPI/VCI pairs will generate traffic at the same
       traffic rate.  Since this test is not a throughput test, the rate
       should not be greater than 90% of line rate.  The IP PDUs MUST be
       encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device for all VCCs.

   Reporting Format:

      The results of the Two-point CDV/Steady Load/Twelve VCCs test
      SHOULD be reported in a form of text, graph, and histograms.

      The text results SHOULD display the numerical values of the CDV.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI values, total number of cells transmitted and received on
      each VCC during the test in positive integers, maximum and minimum
      CDV on each VCC during the test in us, and peak-to-peak CDV on
      each VCC in us.

      The graph results SHOULD display the cell delay values.  The x-
      coordinate SHOULD be the test run time in either seconds, minutes
      or days depending on the total length of the test.  The x-
      coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the cell delay for each VCC in ms.  There SHOULD be 12 curves
      on the graph, one curves indicated and labeled for each VCC.  The
      integration time per point MUST be indicated.







Dunn & Martin                Informational                     [Page 29]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      The histograms SHOULD display the peak-to-peak cell delay.  There
      will be one histogram for each VCC.  The x-coordinate SHOULD be
      the cell delay in us with at least 256 bins.  The y-coordinate
      SHOULD be the number of cells observed in each bin.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      bearer class of the created VCC MUST also be indicated.

3.2.1.4. Two-point CDV/Steady Load/Maximum VCCs

   Objective: To determine the SUT variation in cell transfer delay with
   the maximum number VCCs supported on the SUT as defined in RFC 2761
   "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing timestamps at a
       specific constant rate through the SUT via the defined test VCCs.
       All of the VPI/VCI pairs will generate traffic at the same
       traffic rate.  Since this test is not a throughput test, the rate
       should not be greater than 90% of line rate.  The IP PDUs MUST be
       encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device for all VCCs.

   Reporting Format:

      The results of the Two-point CDV/Steady Load/Maximum VCCs test
      SHOULD be reported in a form of text, graphs, and histograms.




Dunn & Martin                Informational                     [Page 30]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      The text results SHOULD display the numerical values of the CDV.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI values, total number of cells transmitted and received on
      each VCC during the test in positive integers, maximum and minimum
      CDV on each VCC during the test in us, and peak-to-peak CDV on
      each VCC in us.

      The graph results SHOULD display the cell delay values.  There
      will be (Max number of VCCs/10) graphs, with 10 VCCs indicated on
      each graph.  The x-coordinate SHOULD be the test run time in
      either seconds, minutes or days depending on the total length of
      the test.  The x-coordinate time SHOULD be configurable.  The y-
      coordinate SHOULD be the cell delay for each VCC in us.  There
      SHOULD be no more than 10 curves on each graph, one curve
      indicated and labeled for each VCC.  The integration time per
      point MUST be indicated.

      The histograms SHOULD display the peak-to-peak cell delay.  There
      will be one histogram for each VCC.  The x-coordinate SHOULD be
      the cell delay in us with at least 256 bins.  The y-coordinate
      SHOULD be the number of cells observed in each bin.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      bearer class of the created VCC MUST also be indicated.

3.2.1.5. Two-point CDV/Bursty VBR Load/One VCC

   Objective: To determine the SUT variation in cell transfer delay with
   one VCC as defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing timestamps at a
       specific VBR through the SUT via the defined test VCC.  Since
       this test is not a throughput test, the rate should not be
       greater than 90% of line rate.  The IP PDUs MUST be encapsulated
       in AAL5.




Dunn & Martin                Informational                     [Page 31]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device.

   Reporting Format:

      The results of the Two-point CDV/Bursty VBR Load/One VCC test
      SHOULD be reported in a form of text, graph, and histogram.

      The text results SHOULD display the numerical values of the CDV.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, maximum
      and minimum CDV during the test in us, and peak-to-peak CDV in us.

      The graph results SHOULD display the cell delay values.  The x-
      coordinate SHOULD be the test run time in either seconds, minutes
      or days depending on the total length of the test.  The x-
      coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the cell delay in us.  The integration time per point MUST be
      indicated.

      The histogram results SHOULD display the peak-to-peak cell delay.
      The x-coordinate SHOULD be the cell delay in us with at least 256
      bins.  The y-coordinate SHOULD be the number of cells observed in
      each bin.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.1.6. Two-point CDV/Bursty VBR Load/Twelve VCCs

   Objective: To determine the SUT variation in cell transfer delay with
   twelve VCCs as defined in RFC 2761 "Terminology for ATM
   Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.




Dunn & Martin                Informational                     [Page 32]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   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]).

   3)  Send a specific number of IP packets containing timestamps at a
       specific VBR through the SUT via the defined test VCCs.  All of
       the VPI/VCI pairs will generate traffic at the same traffic rate.
       Since this test is not a throughput test, the rate should not be
       greater than 90% of line rate.  The IP PDUs MUST be encapsulated
       in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device for all VCCs.

   Reporting Format:

      The results of the Two-point CDV/Bursty VBR Load/Twelve VCCs test
      SHOULD be reported in a form of text, graph, and histograms.

      The text results SHOULD display the numerical values of the CDV.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI values, total number of cells transmitted and received on
      each VCC during the test in positive integers, maximum and minimum
      CDV on each VCC during the test in us, and peak-to-peak CDV on
      each VCC in us.

      The graph results SHOULD display the cell delay values.  The x-
      coordinate SHOULD be the test run time in either seconds, minutes
      or days depending on the total length of the test.  The x-
      coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the cell delay for each VCC in ms.  There SHOULD be 12 curves
      on the graph, one curves indicated and labeled for each VCC.  The
      integration time per point MUST be indicated.

      The histograms SHOULD display the peak-to-peak cell delay.  There
      will be one histogram for each VCC.  The x-coordinate SHOULD be
      the cell delay in us with at least 256 bins.  The y-coordinate
      SHOULD be the number of cells observed in each bin.







Dunn & Martin                Informational                     [Page 33]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.1.7. Two-point CDV/Bursty VBR Load/Maximum VCCs

   Objective: To determine the SUT variation in cell transfer delay with
   the maximum number VCCs supported on the SUT as defined in RFC 2761
   "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing timestamps at a
       specific VBR through the SUT via the defined test VCCs.  All of
       the VPI/VCI pairs will generate traffic at the same traffic rate.
       Since this test is not a throughput test, the rate should not be
       greater than 90% of line rate.  The IP PDUs MUST be encapsulated
       in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device for all VCCs.

   Reporting Format:

      The results of the Two-point CDV/Bursty VBR Load/Maximum VCCs test
      SHOULD be reported in a form of text, graphs, and histograms.

      The text results SHOULD display the numerical values of the CDV.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI values, total number of cells transmitted and received on




Dunn & Martin                Informational                     [Page 34]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      each VCC during the test in positive integers, maximum and minimum
      CDV on each VCC during the test in us, and peak-to-peak CDV on
      each VCC in us.

      The graph results SHOULD display the cell delay values.  There
      will be (Max number of VCCs/10) graphs, with 10 VCCs indicated on
      each graph.  The x-coordinate SHOULD be the test run time in
      either seconds, minutes or days depending on the total length of
      the test.  The x-coordinate time SHOULD be configurable.  The y-
      coordinate SHOULD be the cell delay for each VCC in us.  There
      SHOULD be no more than 10 curves on each graph, one curve
      indicated and labeled for each VCC.  The integration time per
      point MUST be indicated.

      The histograms SHOULD display the peak-to-peak cell delay.  There
      will be one histogram for each VCC.  The x-coordinate SHOULD be
      the cell delay in us with at least 256 bins.  The y-coordinate
      SHOULD be the number of cells observed in each bin.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.1.8. Two-point CDV/Mixed Load/Three VCC's

   Objective: To determine the SUT variation in cell transfer delay with
   three VCC's as defined in RFC 2761 "Terminology for ATM
   Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing timestamps
       through the SUT via the defined test VCCs.  Each generated VCC
       stream MUST match the corresponding VCC Bearer class.  All of the
       VPI/VCI pairs will generate traffic at the same traffic rate.





Dunn & Martin                Informational                     [Page 35]

RFC 3116            Methodology for ATM Benchmarking           June 2001


       Since this test is not a throughput test, the rate should not be
       greater than 90% of line rate.  The IP PDUs MUST be encapsulated
       in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device for all VCC's.

   Reporting Format:

      The results of the Two-point CDV/Mixed Load/Three VCC test SHOULD
      be reported in a form of text, graph, and histogram.

      The text results SHOULD display the numerical values of the CDV.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, maximum
      and minimum CDV during the test in us, and peak-to-peak CDV in us.

      The graph results SHOULD display the cell delay values.  The x-
      coordinate SHOULD be the test run time in either seconds, minutes
      or days depending on the total length of the test.  The x-
      coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the cell delay in us.  The integration time per point MUST be
      indicated.

      The histogram results SHOULD display the peak-to-peak cell delay.
      The x-coordinate SHOULD be the cell delay in us with at least 256
      bins.  The y-coordinate SHOULD be the number of cells observed in
      each bin.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.1.9. Two-point CDV/Mixed Load/Twelve VCCs

   Objective: To determine the SUT variation in cell transfer delay with
   twelve VCCs as defined in RFC 2761 "Terminology for ATM
   Benchmarking".





Dunn & Martin                Informational                     [Page 36]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing timestamps
       through the SUT via the defined test VCCs.  Each generated VCC
       stream MUST match the corresponding VCC Bearer class.  All of the
       VPI/VCI pairs will generate traffic at the same traffic rate.
       Since this test is not a throughput test, the rate should not be
       greater than 90% of line rate.  The IP PDUs MUST be encapsulated
       in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device for all VCCs.

   Reporting Format:

      The results of the Two-point CDV/Mixed Load/Twelve VCCs test
      SHOULD be reported in a form of text, graph, and histograms.

      The text results SHOULD display the numerical values of the CDV.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI values, total number of cells transmitted and received on
      each VCC during the test in positive integers, maximum and minimum
      CDV on each VCC during the test in us, and peak-to-peak CDV on
      each VCC in us.

      The graph results SHOULD display the cell delay values.  The x-
      coordinate SHOULD be the test run time in either seconds, minutes
      or days depending on the total length of the test.  The x-
      coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the cell delay for each VCC in ms.  There SHOULD be 12 curves
      on the graph, one curves indicated and labeled for each VCC.  The
      integration time per point MUST be indicated.





Dunn & Martin                Informational                     [Page 37]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      The histograms SHOULD display the peak-to-peak cell delay.  There
      will be one histogram for each VCC.  The x-coordinate SHOULD be
      the cell delay in us with at least 256 bins.  The y-coordinate
      SHOULD be the number of cells observed in each bin.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.1.10. Two-point CDV/Mixed Load/Maximum VCCs

   Objective: To determine the SUT variation in cell transfer delay with
   the maximum number VCCs supported on the SUT as defined in RFC 2761
   "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing timestamps
       through the SUT via the defined test VCCs.  Each generated VCC
       stream MUST match the corresponding VCC Bearer class.  All of the
       VPI/VCI pairs will generate traffic at the same traffic rate.
       Since this test is not a throughput test, the rate should not be
       greater than 90% of line rate.  The IP PDUs MUST be encapsulated
       in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device for all VCCs.




Dunn & Martin                Informational                     [Page 38]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   Reporting Format:

      The results of the Two-point CDV/Mixed Load/Maximum VCCs test
      SHOULD be reported in a form of text, graphs, and histograms.

      The text results SHOULD display the numerical values of the CDV.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI values, total number of cells transmitted and received on
      each VCC during the test in positive integers, maximum and minimum
      CDV on each VCC during the test in us, and peak-to-peak CDV on
      each VCC in us.

      The graph results SHOULD display the cell delay values.  There
      will be (Max number of VCCs/10) graphs, with 10 VCCs indicated on
      each graph.  The x-coordinate SHOULD be the test run time in
      either seconds, minutes or days depending on the total length of
      the test.  The x-coordinate time SHOULD be configurable.  The y-
      coordinate SHOULD be the cell delay for each VCC in us.  There
      SHOULD be no more than 10 curves on each graph, one curve
      indicated and labeled for each VCC.  The integration time per
      point MUST be indicated.

      The histograms SHOULD display the peak-to-peak cell delay.  There
      will be one histogram for each VCC.  The x-coordinate SHOULD be
      the cell delay in us with at least 256 bins.  The y-coordinate
      SHOULD be the number of cells observed in each bin.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.2. Cell Error Ratio (CER)

3.2.2.1. Test Setup

   The cell error ratio measurements assume that both the transmitter
   and receiver payload information is synchronized.  Synchronization
   MUST be achieved by supplying a known bit pattern to both the
   transmitter and receiver.  If this bit pattern is longer than the
   packet size, the receiver MUST synchronize with the transmitter
   before tests can be run.








Dunn & Martin                Informational                     [Page 39]

RFC 3116            Methodology for ATM Benchmarking           June 2001


3.2.2.2. CER/Steady Load/One VCC

   Objective: To determine the SUT ratio of errored cells on one VCC in
   a transmission in relation to the total cells sent as defined in RFC
   2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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,
       VBR, or UBR connection.  The VPI/VCI MUST not be one of the
       reserved ATM signaling channels (e.g., [0,5], [0,16]).

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a constant rate through the SUT via the
       defined test VCC.  Since this test is not a throughput test, the
       rate should not be greater than 90% of line rate.  The IP PDUs
       MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the number of bit errors at the receiver end of the test
       device.

   Reporting Format:

      The results of the CER/Steady Load/One VCC test SHOULD be reported
      in a form of text and graph.

      The text results SHOULD display the numerical values of the CER.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CER for the entire test.

      The graph results SHOULD display the cell error ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CER.  The integration time per point MUST be indicated.





Dunn & Martin                Informational                     [Page 40]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST be indicated.  The generated bit pattern MUST
      also be indicated.

3.2.2.3. CER/Steady Load/Twelve VCCs

   Objective: To determine the SUT ratio of errored cells on twelve VCCs
   in a transmission in relation to the total cells sent as defined in
   RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a constant rate through the SUT via the
       defined test VCCs.  All of the VPI/VCI pairs will generate
       traffic at the same traffic rate.  Since this test is not a
       throughput test, the rate should not be greater than 90% of line
       rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of bit errors at the receiver end of the test
       device for all VCCs.

   Reporting Format:

      The results of the CER/Steady Load/Twelve VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CER.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CER for the entire test.



Dunn & Martin                Informational                     [Page 41]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      The graph results SHOULD display the cell error ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CER for each VCC.  There should be 12 curves on the graph,
      on curve indicated and labeled for each VCC.  The integration time
      per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST be indicated.  The generated bit pattern MUST
      also be indicated.

3.2.2.4. CER/Steady Load/Maximum VCCs

   Objective: To determine the SUT ratio of errored cells with the
   maximum number VCCs supported on the SUT in a transmission in
   relation to the total cells sent as defined in RFC 2761 "Terminology
   for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a constant rate through the SUT via the
       defined test VCCs.  All of the VPI/VCI pairs will generate
       traffic at the same traffic rate.  Since this test is not a
       throughput test, the rate should not be greater than 90% of line
       rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of bit errors at the receiver end of the test
       device for all VCCs.



Dunn & Martin                Informational                     [Page 42]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   Reporting Format:

      The results of the CER/Steady Load/Maximum VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CER.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CER for the entire test.

      The graph results SHOULD display the cell error ratio values.
      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the CER for each VCC.  There SHOULD be
      no more than 10 curves on each graph, one curve indicated and
      labeled for each VCC.  The integration time per point MUST be
      indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST be indicated.  The generated bit pattern MUST
      also be indicated.

3.2.2.5. CER/Bursty VBR Load/One VCC

   Objective: To determine the SUT ratio of errored cells on one VCC in
   a transmission in relation to the total cells sent as defined in RFC
   2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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.






Dunn & Martin                Informational                     [Page 43]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific VBR rate through the SUT via
       the defined test VCC.  Since this test is not a throughput test,
       the rate should not be greater than 90% of line rate.  The IP
       PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the number of bit errors at the receiver end of the test
       device.

   Reporting Format:

      The results of the CER/Bursty VBR Load/One VCC test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CER.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CER for the entire test.

      The graph results SHOULD display the cell error ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CER.  The integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST be indicated.  The generated bit pattern MUST
      also be indicated.

3.2.2.6. CER/Bursty VBR Load/Twelve VCCs

   Objective: To determine the SUT ratio of errored cells on twelve VCCs
   in a transmission in relation to the total cells sent as defined in
   RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.



Dunn & Martin                Informational                     [Page 44]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   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.

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific VBR rate through the SUT via
       the defined test VCCs.  All of the VPI/VCI pairs will generate
       traffic at the same traffic rate.  Since this test is not a
       throughput test, the rate should not be greater than 90% of line
       rate.  The PCR, SCR, and MBS must be indicated.  The IP PDUs MUST
       be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of bit errors at the receiver end of the test
       device for all VCCs.

   Reporting Format:

      The results of the CER/Bursty VBR Load/Twelve VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CER.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CER for the entire test.

      The graph results SHOULD display the cell error ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CER for each VCC.  There should be 12 curves on the graph,
      on curve indicated and labeled for each VCC.  The integration time
      per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST be indicated.  The generated bit pattern MUST
      also be indicated.



Dunn & Martin                Informational                     [Page 45]

RFC 3116            Methodology for ATM Benchmarking           June 2001


3.2.2.7. CER/Bursty VBR Load/Maximum VCCs

   Objective: To determine the SUT ratio of errored cells with the
   maximum number VCCs supported on the SUT in a transmission in
   relation to the total cells sent as defined in RFC 2761 "Terminology
   for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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.

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific VBR rate through the SUT via
       the defined test VCCs.  All of the VPI/VCI pairs will generate
       traffic at the same traffic rate.  Since this test is not a
       throughput test, the rate should not be greater than 90% of line
       rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of bit errors at the receiver end of the test
       device for all VCCs.

   Reporting Format:

      The results of the CER/Bursty VBR Load/Maximum VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CER.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CER for the entire test.





Dunn & Martin                Informational                     [Page 46]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      The graph results SHOULD display the cell error ratio values.
      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the CER for each VCC.  There SHOULD be
      no more than 10 curves on each graph, one curve indicated and
      labeled for each VCC.  The integration time per point MUST be
      indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST be indicated.  The generated bit pattern MUST
      also be indicated.

3.2.3. Cell Loss Ratio (CLR)

3.2.3.1. CLR/Steady Load/One VCC

   Objective: To determine the SUT ratio of lost cells on one VCC in a
   transmission in relation to the total cells sent as defined in RFC
   2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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,
       VBR, or UBR connection.  The VPI/VCI MUST not be one of the
       reserved ATM signaling channels (e.g., [0,5], [0,16]).

   3)  Send a specific number of IP packets at a specific constant rate
       through the SUT via the defined test VCC.  Since this test is not
       a throughput test, the rate should not be greater than 90% of
       line rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the number of cells transmitted and received on the test
       device.




Dunn & Martin                Informational                     [Page 47]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   Reporting Format:

      The results of the CLR/Steady Load/One VCC test SHOULD be reported
      in a form of text and graph.

      The text results SHOULD display the numerical values of the CLR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CLR for the entire test.

      The graph results SHOULD display the Cell Loss ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CLR.  The integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.3.2. CLR/Steady Load/Twelve VCCs

   Objective: To determine the SUT ratio of lost cells on twelve VCCs in
   a transmission in relation to the total cells sent as defined in RFC
   2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets at a specific constant rate
       through the SUT via the defined test VCCs.  All of the VPI/VCI
       pairs will generate traffic at the same traffic rate.  Since this
       test is not a throughput test, the rate should not be greater
       than 90% of line rate.  The IP PDUs MUST be encapsulated in AAL5.







Dunn & Martin                Informational                     [Page 48]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of cells transmitted and received per VCC on
       the test device.

   Reporting Format:

      The results of the CLR/Steady Load/Twelve VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CLR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CLR for the entire test.

      The graph results SHOULD display the Cell Loss ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CLR for each VCC.  There should be 12 curves on the graph,
      on curve indicated and labeled for each VCC.  The integration time
      per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.3.3. CLR/Steady Load/Maximum VCCs

   Objective: To determine the SUT ratio of lost cells with the maximum
   number VCCs supported on the SUT in a transmission in relation to the
   total cells sent as defined in RFC 2761 "Terminology for ATM
   Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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



Dunn & Martin                Informational                     [Page 49]

RFC 3116            Methodology for ATM Benchmarking           June 2001


       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]).

   3)  Send a specific number of IP packets at a specific constant rate
       through the SUT via the defined test VCCs.  All of the VPI/VCI
       pairs will generate traffic at the same traffic rate.  Since this
       test is not a throughput test, the rate should not be greater
       than 90% of line rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of cells transmitted and received per VCC on
       the test device.

   Reporting Format:

      The results of the CLR/Steady Load/Maximum VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CLR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CLR for the entire test.

      The graph results SHOULD display the Cell Loss ratio values.
      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the CLR for each VCC.  There SHOULD be
      no more than 10 curves on each graph, one curve indicated and
      labeled for each VCC.  The integration time per point MUST be
      indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.







Dunn & Martin                Informational                     [Page 50]

RFC 3116            Methodology for ATM Benchmarking           June 2001


3.2.3.4. CLR/Bursty VBR Load/One VCC

   Objective: To determine the SUT ratio of lost cells on one VCC in a
   transmission in relation to the total cells sent as defined in RFC
   2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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.

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific rate through the SUT via the
       defined test VCC.  Since this test is not a throughput test, the
       rate should not be greater than 90% of line rate.  The IP PDUs
       MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the number of cells transmitted and received on the test
       device.

   Reporting Format:

      The results of the CLR/Bursty VBR Load/One VCC test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CLR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CLR for the entire test.

      The graph results SHOULD display the Cell Loss ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CLR.  The integration time per point MUST be indicated.



Dunn & Martin                Informational                     [Page 51]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.3.5. CLR/Bursty VBR Load/Twelve VCCs

   Objective: To determine the SUT ratio of lost cells on twelve VCCs in
   a transmission in relation to the total cells sent as defined in RFC
   2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   2)  Configure the SUT and test device with twelve VCCs, using 1 VPI
       and 12 VCIs.  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.

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific rate through the SUT via the
       defined test VCCs.  All of the VPI/VCI pairs will generate
       traffic at the same traffic rate.  Since this test is not a
       throughput test, the rate should not be greater than 90% of line
       rate.  The PCR, SCR, and MBS must be indicated.  The IP PDUs MUST
       be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of cells transmitted and received per VCC on
       the test device.

   Reporting Format:

      The results of the CLR/Bursty VBR Load/Twelve VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CLR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on



Dunn & Martin                Informational                     [Page 52]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      the given VPI/VCI during the test in positive integers, and the
      CLR for the entire test.

      The graph results SHOULD display the Cell Loss ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CLR for each VCC.  There should be 12 curves on the graph,
      on curve indicated and labeled for each VCC.  The integration time
      per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.3.6. CLR/Bursty VBR Load/Maximum VCCs

   Objective: To determine the SUT ratio of lost cells with the maximum
   number VCCs supported on the SUT in a transmission in relation to the
   total cells sent as defined in RFC 2761 "Terminology for ATM
   Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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.

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific rate through the SUT via the
       defined test VCCs.  All of the VPI/VCI pairs will generate
       traffic at the same traffic rate.  Since this test is not a
       throughput test, the rate should not be greater than 90% of line
       rate.  The IP PDUs MUST be encapsulated in AAL5.







Dunn & Martin                Informational                     [Page 53]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of cells transmitted and received per VCC on
       the test device.

   Reporting Format:

      The results of the CLR/Bursty VBR Load/Maximum VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CLR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CLR for the entire test.

      The graph results SHOULD display the Cell Loss ratio values.
      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the CLR for each VCC.  There SHOULD be
      no more than 10 curves on each graph, one curve indicated and
      labeled for each VCC.  The integration time per point MUST be
      indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.4. Cell Misinsertion Rate (CMR)

3.2.4.1. CMR/Steady Load/One VCC

   Objective: To determine the SUT ratio of cell misinsertion on one VCC
   in a transmission in relation to the total cells sent as defined in
   RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.




Dunn & Martin                Informational                     [Page 54]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   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]).

   3)  Send a specific number of IP packets at a specific constant rate
       through the SUT via the defined test VCC.  Since this test is not
       a throughput test, the rate should not be greater than 90% of
       line rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the number of cell misinsertion errors at the receiver end
       of the test device.

   Reporting Format:

      The results of the CMR/Steady Load/One VCC test SHOULD be reported
      in a form of text and graph.

      The text results SHOULD display the numerical values of the CMR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CMR for the entire test.

      The graph results SHOULD display the Cell misinsertion rate
      values.  The x-coordinate SHOULD be the test run time in either
      seconds, minutes or days depending on the total length of the
      test.  The x-coordinate time SHOULD be configurable.  The y-
      coordinate SHOULD be the CMR.  The integration time per point MUST
      be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.4.2. CMR/Steady Load/Twelve VCCs

   Objective: To determine the SUT rate of misinserted cells on twelve
   VCCs in a transmission in relation to the total cells sent as defined
   in RFC 2761 "Terminology for ATM Benchmarking".




Dunn & Martin                Informational                     [Page 55]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets at a specific constant rate
       through the SUT via the defined test VCCs.  All of the VPI/VCI
       pairs will generate traffic at the same traffic rate.  Since this
       test is not a throughput test, the rate should not be greater
       than 90% of line rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of cell misinsertion errors at the receiver end
       of the test device per VCC.

   Reporting Format:

      The results of the CMR/Steady Load/Twelve VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CMR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CMR for the entire test.

      The graph results SHOULD display the Cell misinsertion rate
      values.  The x-coordinate SHOULD be the test run time in either
      seconds, minutes or days depending on the total length of the
      test.  The x-coordinate time SHOULD be configurable.  The y-
      coordinate SHOULD be the CMR for each VCC.  There should be 12
      curves on the graph, on curve indicated and labeled for each VCC.
      The integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.



Dunn & Martin                Informational                     [Page 56]

RFC 3116            Methodology for ATM Benchmarking           June 2001


3.2.4.3. CMR/Steady Load/Maximum VCCs

   Objective: To determine the SUT rate of misinserted cells with the
   maximum number VCCs supported on the SUT in a transmission in
   relation to the total cells sent as defined in RFC 2761 "Terminology
   for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets at a specific constant rate
       through the SUT via the defined test VCCs.  All of the VPI/VCI
       pairs will generate traffic at the same traffic rate.  Since this
       test is not a throughput test, the rate should not be greater
       than 90% of line rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of cell misinsertion errors at the receiver end
       of the test device per VCC.

   Reporting Format:

      The results of the CMR/Steady Load/Maximum VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CMR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CMR for the entire test.

      The graph results SHOULD display the Cell misinsertion rate
      values.  There will be (Max number of VCCs/10) graphs, with 10
      VCCs indicated on each graph.  The x-coordinate SHOULD be the test
      run time in either seconds, minutes or days depending on the total



Dunn & Martin                Informational                     [Page 57]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the CMR for each VCC.  There SHOULD be
      no more than 10 curves on each graph, one curve indicated and
      labeled for each VCC.  The integration time per point MUST be
      indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.4.4. CMR/Bursty VBR Load/One VCC

   Objective: To determine the SUT rate of misinserted cells on one VCC
   in a transmission in relation to the total cells sent as defined in
   RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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.

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific rate through the SUT via the
       defined test VCC.  Since this test is not a throughput test, the
       rate should not be greater than 90% of line rate.  The IP PDUs
       MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the number of cell misinsertion errors at the receiver end
       of the test device.

   Reporting Format:

      The results of the CMR/Bursty VBR Load/One VCC test SHOULD be
      reported in a form of text and graph.



Dunn & Martin                Informational                     [Page 58]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      The text results SHOULD display the numerical values of the CMR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CMR for the entire test.

      The graph results SHOULD display the Cell misinsertion rate
      values.  The x-coordinate SHOULD be the test run time in either
      seconds, minutes or days depending on the total length of the
      test.  The x-coordinate time SHOULD be configurable.  The y-
      coordinate SHOULD be the CMR.  The integration time per point MUST
      be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.4.5. CMR/Bursty VBR Load/Twelve VCCs

   Objective: To determine the SUT rate of misinserted cells on twelve
   VCCs in a transmission in relation to the total cells sent as defined
   in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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.

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific rate through the SUT via the
       defined test VCCs.  All of the VPI/VCI pairs will generate
       traffic at the same traffic rate.  Since this test is not a
       throughput test, the rate should not be greater than 90% of line
       rate.  The PCR, SCR, and MBS must be indicated.  The IP PDUs MUST
       be encapsulated in AAL5.







Dunn & Martin                Informational                     [Page 59]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of cell misinsertion errors at the receiver end
       of the test device per VCC.

   Reporting Format:

      The results of the CMR/Bursty VBR Load/Twelve VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CMR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CMR for the entire test.

      The graph results SHOULD display the Cell misinsertion rate
      values.  The x-coordinate SHOULD be the test run time in either
      seconds, minutes or days depending on the total length of the
      test.  The x-coordinate time SHOULD be configurable.  The y-
      coordinate SHOULD be the CMR for each VCC.  There should be 12
      curves on the graph, on curve indicated and labeled for each VCC.
      The integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.4.6. CMR/Bursty VBR Load/Maximum VCCs

   Objective: To determine the SUT rate of misinserted cells with the
   maximum number VCCs supported on the SUT in a transmission in
   relation to the total cells sent as defined in RFC 2761 "Terminology
   for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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



Dunn & Martin                Informational                     [Page 60]

RFC 3116            Methodology for ATM Benchmarking           June 2001


       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.

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific rate through the SUT via the
       defined test VCCs.  All of the VPI/VCI pairs will generate
       traffic at the same traffic rate.  Since this test is not a
       throughput test, the rate should not be greater than 90% of line
       rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of cell misinsertion errors at the receiver end
       of the test device per VCC.

   Reporting Format:

      The results of the CMR/Bursty VBR Load/Maximum VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CMR.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, and the
      CMR for the entire test.

      The graph results SHOULD display the Cell misinsertion rate
      values.  There will be (Max number of VCCs/10) graphs, with 10
      VCCs indicated on each graph.  The x-coordinate SHOULD be the test
      run time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the CMR for each VCC.  There SHOULD be
      no more than 10 curves on each graph, one curve indicated and
      labeled for each VCC.  The integration time per point MUST be
      indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.




Dunn & Martin                Informational                     [Page 61]

RFC 3116            Methodology for ATM Benchmarking           June 2001


3.2.5. CRC Error Ratio (CRC-ER)

3.2.5.1. CRC-ER/Steady Load/One VCC

   Objective: To determine the SUT ratio of CRC errors on one VCC in a
   transmission in relation to the total cells sent as defined in RFC
   2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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,
       VBR, or UBR connection.  The VPI/VCI MUST not be one of the
       reserved ATM signaling channels (e.g., [0,5], [0,16]).

   3)  Send a specific number of IP packets at a specific constant rate
       through the SUT via the defined test VCC.  Since this test is not
       a throughput test, the rate should not be greater than 90% of
       line rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the number of CRC errored cells received on the test
       device.

   Reporting Format:

      The results of the CRC-ER/Steady Load/One VCC test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CRC-
      ER.  The values given SHOULD include: time period of test in s,
      test VPI/VCI value, total number of cells transmitted and received
      on the given VPI/VCI during the test in positive integers, and the
      CRC-ER for the entire test.

      The graph results SHOULD display the CRC Error ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CRC-ER.  The integration time per point MUST be indicated.




Dunn & Martin                Informational                     [Page 62]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.5.2. CRC-ER/Steady Load/Twelve VCCs

   Objective: To determine the SUT ratio of lost cells on twelve VCCs in
   a transmission in relation to the total cells sent as defined in RFC
   2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets at a specific constant rate
       through the SUT via the defined test VCCs.  All of the VPI/VCI
       pairs will generate traffic at the same traffic rate.  Since this
       test is not a throughput test, the rate should not be greater
       than 90% of line rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of CRC errored cells received per VCC on the
       test device.

   Reporting Format:

      The results of the CRC-ER/Steady Load/Twelve VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CRC-
      ER.  The values given SHOULD include: time period of test in s,
      test VPI/VCI value, total number of cells transmitted and received
      on the given VPI/VCI during the test in positive integers, and the
      CRC-ER for the entire test.





Dunn & Martin                Informational                     [Page 63]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      The graph results SHOULD display the CRC Error ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CRC-ER for each VCC.  There should be 12 curves on the
      graph, on curve indicated and labeled for each VCC.  The
      integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.5.3. CRC-ER/Steady Load/Maximum VCCs

   Objective: To determine the SUT ratio of lost cells with the maximum
   number VCCs supported on the SUT in a transmission in relation to the
   total cells sent as defined in RFC 2761 "Terminology for ATM
   Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets at a specific constant rate
       through the SUT via the defined test VCCs.  All of the VPI/VCI
       pairs will generate traffic at the same traffic rate.  Since this
       test is not a throughput test, the rate should not be greater
       than 90% of line rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of CRC errored cells received per VCC on the
       test device.





Dunn & Martin                Informational                     [Page 64]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   Reporting Format:

      The results of the CRC-ER/Steady Load/Maximum VCCs test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CRC-
      ER.  The values given SHOULD include: time period of test in s,
      test VPI/VCI value, total number of cells transmitted and received
      on the given VPI/VCI during the test in positive integers, and the
      CRC-ER for the entire test.

      The graph results SHOULD display the CRC Error ratio values.
      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the CRC-ER for each VCC.  There SHOULD
      be no more than 10 curves on each graph, one curve indicated and
      labeled for each VCC.  The integration time per point MUST be
      indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.5.4. CRC-ER/Bursty VBR Load/One VCC

   Objective: To determine the SUT ratio of lost cells on one VCC in a
   transmission in relation to the total cells sent as defined in RFC
   2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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.

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific rate through the SUT via the
       defined test VCC.  Since this test is not a throughput test, the



Dunn & Martin                Informational                     [Page 65]

RFC 3116            Methodology for ATM Benchmarking           June 2001


       rate should not be greater than 90% of line rate.  The IP PDUs
       MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the number of CRC errored cells received per VCC on the
       test device.

   Reporting Format:

      The results of the CRC-ER/Bursty VBR Load/One VCC test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CRC-
      ER.  The values given SHOULD include: time period of test in s,
      test VPI/VCI value, total number of cells transmitted and received
      on the given VPI/VCI during the test in positive integers, and the
      CRC-ER for the entire test.

      The graph results SHOULD display the CRC Error ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CRC-ER.  The integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.5.5. CRC-ER/Bursty VBR Load/Twelve VCCs

   Objective: To determine the SUT ratio of lost cells on twelve VCCs in
   a transmission in relation to the total cells sent as defined in RFC
   2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   2)  Configure the SUT and test device with twelve VCCs, using 1 VPI
       and 12 VCIs.  The VCC MUST be configured as either a CBR or VBR
       connection.  The VPI/VCIs MUST not be one of the reserved ATM



Dunn & Martin                Informational                     [Page 66]

RFC 3116            Methodology for ATM Benchmarking           June 2001


       signaling channels (e.g., [0,5], [0,16]).  The PCR, SCR, and MBS
       must be configured using one of the specified traffic
       descriptors.

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific rate through the SUT via the
       defined test VCCs.  All of the VPI/VCI pairs will generate
       traffic at the same traffic rate.  Since this test is not a
       throughput test, the rate should not be greater than 90% of line
       rate.  The PCR, SCR, and MBS must be indicated.  The IP PDUs MUST
       be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of CRC errored cells received per VCC on the
       test device for all VCCs.

   Reporting Format:

      The results of the CRC-ER/Bursty VBR Load/Twelve VCCs test SHOULD
      be reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CRC-
      ER.  The values given SHOULD include: time period of test in s,
      test VPI/VCI value, total number of cells transmitted and received
      on the given VPI/VCI during the test in positive integers, and the
      CRC-ER for the entire test.

      The graph results SHOULD display the CRC Error ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CRC-ER for each VCC.  There should be 12 curves on the
      graph, on curve indicated and labeled for each VCC.  The
      integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.







Dunn & Martin                Informational                     [Page 67]

RFC 3116            Methodology for ATM Benchmarking           June 2001


3.2.5.6. CRC-ER/Bursty VBR Load/Maximum VCCs

   Objective: To determine the SUT ratio of lost cells with the maximum
   number VCCs supported on the SUT in a transmission in relation to the
   total cells sent as defined in RFC 2761 "Terminology for ATM
   Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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.

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific rate through the SUT via the
       defined test VCCs.  All of the VPI/VCI pairs will generate
       traffic at the same traffic rate.  Since this test is not a
       throughput test, the rate should not be greater than 90% of line
       rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of CRC errored cells received per VCC on the
       test device for all VCCs.

   Reporting Format:

      The results of the CRC-ER/Bursty VBR Load/Maximum VCCs test SHOULD
      be reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CRC-
      ER.  The values given SHOULD include: time period of test in s,
      test VPI/VCI value, total number of cells transmitted and received
      on the given VPI/VCI during the test in positive integers, and the
      CRC-ER for the entire test.

      The graph results SHOULD display the CRC Error ratio values.



Dunn & Martin                Informational                     [Page 68]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the CRC-ER for each VCC.  There SHOULD
      be no more than 10 curves on each graph, one curve indicated and
      labeled for each VCC.  The integration time per point MUST be
      indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.5.7. CRC-ER/Bursty UBR Load/One VCC

   Objective: To determine the SUT ratio of lost cells on one VCC in a
   transmission in relation to the total cells sent as defined in RFC
   2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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.

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific rate through the SUT via the
       defined test VCC.  Since this test is not a throughput test, the
       rate should not be greater than 90% of line rate.  The IP PDUs
       MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the number of CRC errored cells received per VCC on the
       test device.





Dunn & Martin                Informational                     [Page 69]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   Reporting Format:

      The results of the CRC-ER/Bursty UBR Load/One VCC test SHOULD be
      reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CRC-
      ER.  The values given SHOULD include: time period of test in s,
      test VPI/VCI value, total number of cells transmitted and received
      on the given VPI/VCI during the test in positive integers, and the
      CRC-ER for the entire test.

      The graph results SHOULD display the CRC Error ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CRC-ER.  The integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.5.8. CRC-ER/Bursty UBR Load/Twelve VCCs

   Objective: To determine the SUT ratio of lost cells on twelve VCCs in
   a transmission in relation to the total cells sent as defined in RFC
   2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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.

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific rate through the SUT via the
       defined test VCCs.  All of the VPI/VCI pairs will generate
       traffic at the same traffic rate.  Since this test is not a
       throughput test, the rate should not be greater than 90% of line
       rate.  The PCR, SCR, and MBS must be indicated.  The IP PDUs MUST
       be encapsulated in AAL5.




Dunn & Martin                Informational                     [Page 70]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of CRC errored cells received per VCC on the
       test device for all VCCs.

   Reporting Format:

      The results of the CRC-ER/Bursty UBR Load/Twelve VCCs test SHOULD
      be reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CRC-
      ER.  The values given SHOULD include: time period of test in s,
      test VPI/VCI value, total number of cells transmitted and received
      on the given VPI/VCI during the test in positive integers, and the
      CRC-ER for the entire test.

      The graph results SHOULD display the CRC Error ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CRC-ER for each VCC.  There should be 12 curves on the
      graph, on curve indicated and labeled for each VCC.  The
      integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.5.9. CRC-ER/Bursty UBR Load/Maximum VCCs

   Objective: To determine the SUT ratio of lost cells with the maximum
   number VCCs supported on the SUT in a transmission in relation to the
   total cells sent as defined in RFC 2761 "Terminology for ATM
   Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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



Dunn & Martin                Informational                     [Page 71]

RFC 3116            Methodology for ATM Benchmarking           June 2001


       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.

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific rate through the SUT via the
       defined test VCCs.  All of the VPI/VCI pairs will generate
       traffic at the same traffic rate.  Since this test is not a
       throughput test, the rate should not be greater than 90% of line
       rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of CRC errored cells received per VCC on the
       test device for all VCCs.

   Reporting Format:

      The results of the CRC-ER/Bursty UBR Load/Maximum VCCs test SHOULD
      be reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CRC-
      ER.  The values given SHOULD include: time period of test in s,
      test VPI/VCI value, total number of cells transmitted and received
      on the given VPI/VCI during the test in positive integers, and the
      CRC-ER for the entire test.

      The graph results SHOULD display the CRC Error ratio values.
      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the CRC-ER for each VCC.  There SHOULD
      be no more than 10 curves on each graph, one curve indicated and
      labeled for each VCC.  The integration time per point MUST be
      indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.





Dunn & Martin                Informational                     [Page 72]

RFC 3116            Methodology for ATM Benchmarking           June 2001


3.2.5.10. CRC-ER/Bursty Mixed Load/Three VCC

   Objective: To determine the SUT ratio of lost cells on three VCC's in
   relation to the total cells sent as defined in RFC 2761 "Terminology
   for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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.

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns through the SUT via the defined test VCCs.
       Each generated VCC stream MUST match the corresponding VCC Bearer
       class.  All of the VPI/VCI pairs will generate traffic at the
       same traffic rate.  Since this test is not a throughput test, the
       rate should not be greater than 90% of line rate.  The IP PDUs
       MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the number of CRC errored cells received per VCC on the
       test device.

   Reporting Format:

      The results of the CRC-ER/Bursty Mixed Load/Three VCC test SHOULD
      be reported in in a form of text and graph.

      The text results SHOULD display the numerical values of the CRC-
      ER.  The values given SHOULD include: time period of test in s,
      test VPI/VCI value, total number of cells transmitted and received
      on the given VPI/VCI during the test in positive integers, and the
      CRC-ER for the entire test.

      The graph results SHOULD display the CRC Error ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The



Dunn & Martin                Informational                     [Page 73]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CRC-ER for each VCC.  There should be 12 curves on the
      graph, on curve indicated and labeled for each VCC.  The
      integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.5.11. CRC-ER/Bursty Mixed Load/Twelve VCCs

   Objective: To determine the SUT ratio of lost cells on twelve VCCs in
   a transmission in relation to the total cells sent as defined in RFC
   2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns through the SUT via the defined test VCCs.
       Each generated VCC stream MUST match the corresponding VCC Bearer
       class.  All of the VPI/VCI pairs will generate traffic at the
       same traffic rate.  Since this test is not a throughput test, the
       rate should not be greater than 90% of line rate.  The IP PDUs
       MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of CRC errored cells received per VCC on the
       test device for all VCCs.

   Reporting Format:

      The results of the CRC-ER/Bursty Mixed Load/Twelve VCCs test
      SHOULD be reported in a form of text and graph.



Dunn & Martin                Informational                     [Page 74]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      The text results SHOULD display the numerical values of the CRC-
      ER.  The values given SHOULD include: time period of test in s,
      test VPI/VCI value, total number of cells transmitted and received
      on the given VPI/VCI during the test in positive integers, and the
      CRC-ER for the entire test.

      The graph results SHOULD display the CRC Error ratio values.  The
      x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on  the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the CRC-ER for each VCC.  There should be 12 curves on the
      graph, on curve indicated and labeled for each VCC.  The
      integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.5.12. CRC-ER/Bursty Mixed Load/Maximum VCCs

   Objective: To determine the SUT ratio of lost cells with the maximum
   number VCCs supported on the SUT in a transmission in relation to the
   total cells sent as defined in RFC 2761 "Terminology for ATM
   Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns through the SUT via the defined test VCCs.
       Each generated VCC stream MUST match the corresponding VCC Bearer
       class.  All of the VPI/VCI pairs will generate traffic at the
       same traffic rate.  Since this test is not a throughput test, the
       rate should not be greater than 90% of line rate.  The IP PDUs
       MUST be encapsulated in AAL5.




Dunn & Martin                Informational                     [Page 75]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of CRC errored cells received per VCC on the
       test device for all VCCs.

   Reporting Format:

      The results of the CRC-ER/Bursty Mixed Load/Maximum VCCs test
      SHOULD be reported in a form of text and graph.

      The text results SHOULD display the numerical values of the CRC-
      ER.  The values given SHOULD include: time period of test in s,
      test VPI/VCI value, total number of cells transmitted and received
      on the given VPI/VCI during the test in positive integers, and the
      CRC-ER for the entire test.

      The graph results SHOULD display the CRC Error ratio values.
      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the CRC-ER for each VCC.  There SHOULD
      be no more than 10 curves on each graph, one curve indicated and
      labeled for each VCC.  The integration time per point MUST be
      indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.6. Cell Transfer Delay (CTD)

3.2.6.1. Test Setup

   The cell transfer delay measurements assume that both the transmitter
   and receiver timestamp information is synchronized.  Synchronization
   SHOULD be achieved by supplying a common clock signal (minimum of 100
   Mhz or 10 ns resolution) to both the transmitter and receiver.  The
   maximum timestamp values MUST be recorded to ensure synchronization
   in the case of counter rollover.  The cell transfer delay
   measurements SHOULD utilize the O.191 cell (ITUT-O.191) encapsulated
   in a valid IP packet.  If the O.191 cell is not available, a test
   cell encapsulated in a valid IP packet MAY be used.  The test cell



Dunn & Martin                Informational                     [Page 76]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   MUST contain a transmit timestamp which can be correlated with a
   receive timestamp.  A description of the test cell MUST be included
   in the test results.  The description MUST include the timestamp
   length (in bits), counter rollover value, and the timestamp accuracy
   (in ns).

3.2.6.2. CTD/Steady Load/One VCC

   Objective: To determine the SUT variation in cell transfer delay with
   one VCC as defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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,
       VBR, or UBR connection.  The VPI/VCI MUST not be one of the
       reserved ATM signaling channels (e.g., [0,5], [0,16]).

   3)  Send a specific number of IP packets containing timestamps at a
       specific constant rate through the SUT via the defined test VCC.
       Since this test is not a throughput test, the rate should not be
       greater than 90% of line rate.  The IP PDUs MUST be encapsulated
       in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device.

   Reporting Format:

      The results of the CTD/Steady Load/One VCC test SHOULD be reported
      in a form of text, graph, and histogram.

      The text results SHOULD display the numerical values of the CTD.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, minimum,
      maximum, and mean CTD during the test in us.

      The graph results SHOULD display the cell transfer delay values.
      The x-coordinate SHOULD be the test run time in either seconds,



Dunn & Martin                Informational                     [Page 77]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the cell transfer delay in us.  The integration time per point
      MUST be indicated.

      The histogram results SHOULD display the cell transfer delay.  The
      x-coordinate SHOULD be the cell transfer delay in us with at least
      256 bins.  The y-coordinate SHOULD be the number of cells observed
      in each bin.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      bearer class of the created VCC MUST also be indicated.

3.2.6.3. CTD/Steady Load/Twelve VCCs

   Objective: To determine the SUT variation in cell transfer delay with
   twelve VCCs as defined in RFC 2761 "Terminology for ATM
   Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing timestamps at a
       specific constant rate through the SUT via the defined test VCCs.
       All of the VPI/VCI pairs will generate traffic at the same
       traffic rate.  Since this test is not a throughput test, the rate
       should not be greater than 90% of line rate.  The IP PDUs MUST be
       encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device for all VCCs.






Dunn & Martin                Informational                     [Page 78]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   Reporting Format:

      The results of the CTD/Steady Load/Twelve VCCs test SHOULD be
      reported in a form of text, graph, and histograms.

      The text results SHOULD display the numerical values of the CTD.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI values, total number of cells transmitted and received on
      each VCC during the test in positive integers, maximum and minimum
      CTD on each VCC during the test in us, and mean CTD on each VCC in
      us.

      The graph results SHOULD display the cell transfer delay values.
      The x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the cell transfer delay for each VCC in ms.  There SHOULD be 12
      curves on the graph, one curves indicated and labeled for each
      VCC.  The integration time per point MUST be indicated.

      The histograms SHOULD display the cell transfer delay.  There will
      be one histogram for each VCC.  The x-coordinate SHOULD be the
      cell transfer delay in us with at least 256 bins.  The y-
      coordinate SHOULD be the number of cells observed in each bin.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      bearer class of the created VCC MUST also be indicated.

3.2.6.4. CTD/Steady Load/Maximum VCCs

   Objective: To determine the SUT variation in cell transfer delay with
   the maximum number VCCs supported on the SUT as defined in RFC 2761
   "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).




Dunn & Martin                Informational                     [Page 79]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   3)  Send a specific number of IP packets containing timestamps at a
       specific constant rate through the SUT via the defined test VCCs.
       All of the VPI/VCI pairs will generate traffic at the same
       traffic rate.  Since this test is not a throughput test, the rate
       should not be greater than 90% of line rate.  The IP PDUs MUST be
       encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device for all VCCs.

   Reporting Format:

      The results of the CTD/Steady Load/Maximum VCCs test SHOULD be
      reported in a form of text, graphs, and histograms.

      The text results SHOULD display the numerical values of the CTD.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI values, total number of cells transmitted and received on
      each VCC during the test in positive integers, maximum and minimum
      CTD on each VCC during the test in us, and mean CTD on each VCC in
      us.

      The graph results SHOULD display the cell transfer delay values.
      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the cell transfer delay for each VCC in
      us.  There SHOULD be no more than 10 curves on each graph, one
      curve indicated and labeled for each VCC.  The integration time
      per point MUST be indicated.

      The histograms SHOULD display the cell transfer delay.  There will
      be one histogram for each VCC.  The x-coordinate SHOULD be the
      cell transfer delay in us with at least 256 bins.  The y-
      coordinate SHOULD be the number of cells observed in each bin.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      bearer class of the created VCC MUST also be indicated.





Dunn & Martin                Informational                     [Page 80]

RFC 3116            Methodology for ATM Benchmarking           June 2001


3.2.6.5. CTD/Bursty VBR Load/One VCC

   Objective: To determine the SUT variation in cell transfer delay with
   one VCC as defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing timestamps at a
       specific VBR through the SUT via the defined test VCC.  Since
       this test is not a throughput test, the rate should not be
       greater than 90% of line rate.  The IP PDUs MUST be encapsulated
       in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device.

   Reporting Format:

      The results of the CTD/Bursty VBR Load/One VCC test SHOULD be
      reported in a form of text, graph, and histogram.

      The text results SHOULD display the numerical values of the CTD.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, minimum,
      maximum, and mean CTD during the test in us.

      The graph results SHOULD display the cell transfer delay values.
      The x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the cell transfer delay in us.  The integration time per point
      MUST be indicated.





Dunn & Martin                Informational                     [Page 81]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      The histogram results SHOULD display the cell transfer delay.  The
      x-coordinate SHOULD be the cell transfer delay in us with at least
      256 bins.  The y-coordinate SHOULD be the number of cells observed
      in each bin.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.6.6. CTD/Bursty VBR Load/Twelve VCCs

   Objective: To determine the SUT variation in cell transfer delay with
   twelve VCCs as defined in RFC 2761 "Terminology for ATM
   Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing timestamps at a
       specific VBR through the SUT via the defined test VCCs.  All of
       the VPI/VCI pairs will generate traffic at the same traffic rate.
       Since this test is not a throughput test, the rate should not be
       greater than 90% of line rate.  The IP PDUs MUST be encapsulated
       in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device for all VCCs.

   Reporting Format:

      The results of the CTD/Bursty VBR Load/Twelve VCCs test SHOULD be
      reported in a form of text, graph, and histograms.





Dunn & Martin                Informational                     [Page 82]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      The text results SHOULD display the numerical values of the CTD.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI values, total number of cells transmitted and received on
      each VCC during the test in positive integers, maximum and minimum
      CTD on each VCC during the test in us, and mean CTD on each VCC in
      us.

      The graph results SHOULD display the cell transfer delay values.
      The x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the cell transfer delay for each VCC in ms.  There SHOULD be 12
      curves on the graph, one curves indicated and labeled for each
      VCC.  The integration time per point MUST be indicated.

      The histograms SHOULD display the cell transfer delay.  There will
      be one histogram for each VCC.  The x-coordinate SHOULD be the
      cell transfer delay in us with at least 256 bins.  The y-
      coordinate SHOULD be the number of cells observed in each bin.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.6.7. CTD/Bursty VBR Load/Maximum VCCs

   Objective: To determine the SUT variation in cell transfer delay with
   the maximum number VCCs supported on the SUT as defined in RFC 2761
   "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing timestamps at a
       specific VBR through the SUT via the defined test VCCs.  All of
       the VPI/VCI pairs will generate traffic at the same traffic rate.
       Since this test is not a throughput test, the rate should not be



Dunn & Martin                Informational                     [Page 83]

RFC 3116            Methodology for ATM Benchmarking           June 2001


       greater than 90% of line rate.  The IP PDUs MUST be encapsulated
       in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device for all VCCs.

   Reporting Format:

      The results of the CTD/Bursty VBR Load/Maximum VCCs test SHOULD be
      reported in a form of text, graphs, and histograms.

      The text results SHOULD display the numerical values of the CTD.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI values, total number of cells transmitted and received on
      each VCC during the test in positive integers, maximum and minimum
      CTD on each VCC during the test in us, and mean CTD on each VCC in
      us.

      The graph results SHOULD display the cell transfer delay values.
      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the cell transfer delay for each VCC in
      us.  There SHOULD be no more than 10 curves on each graph, one
      curve indicated and labeled for each VCC.  The integration time
      per point MUST be indicated.

      The histograms SHOULD display the cell transfer delay.  There will
      be one histogram for each VCC.  The x-coordinate SHOULD be the
      cell transfer delay in us with at least 256 bins.  The y-
      coordinate SHOULD be the number of cells observed in each bin.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.








Dunn & Martin                Informational                     [Page 84]

RFC 3116            Methodology for ATM Benchmarking           June 2001


3.2.6.8. CTD/Bursty UBR Load/One VCC

   Objective: To determine the SUT variation in cell transfer delay with
   one VCC as defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing timestamps at a
       specific UBR through the SUT via the defined test VCC.  Since
       this test is not a throughput test, the rate should not be
       greater than 90% of line rate.  The IP PDUs MUST be encapsulated
       in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device.

   Reporting Format:

      The results of the CTD/Bursty UBR Load/One VCC test SHOULD be
      reported in a form of text, graph, and histogram.

      The text results SHOULD display the numerical values of the CTD.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, minimum,
      maximum, and mean CTD during the test in us.

      The graph results SHOULD display the cell transfer delay values.
      The x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the cell transfer delay in us.  The integration time per point
      MUST be indicated.





Dunn & Martin                Informational                     [Page 85]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      The histogram results SHOULD display the cell transfer delay.  The
      x-coordinate SHOULD be the cell transfer delay in us with at least
      256 bins.  The y-coordinate SHOULD be the number of cells observed
      in each bin.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      bearer class of the created VCC MUST also be indicated.

3.2.6.9. CTD/Bursty UBR Load/Twelve VCCs

   Objective: To determine the SUT variation in cell transfer delay with
   twelve VCCs as defined in RFC 2761 "Terminology for ATM
   Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing timestamps at a
       specific UBR through the SUT via the defined test VCCs.  All of
       the VPI/VCI pairs will generate traffic at the same traffic rate.
       Since this test is not a throughput test, the rate should not be
       greater than 90% of line rate.  The IP PDUs MUST be encapsulated
       in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device for all VCCs.

   Reporting Format:

      The results of the CTD/Bursty UBR Load/Twelve VCCs test SHOULD be
      reported in a form of text, graph, and histograms.

      The text results SHOULD display the numerical values of the CTD.
      The values given SHOULD include: time period of test in s, test



Dunn & Martin                Informational                     [Page 86]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      VPI/VCI values, total number of cells transmitted and received on
      each VCC during the test in positive integers, maximum and minimum
      CTD on each VCC during the test in us, and mean CTD on each VCC in
      us.

      The graph results SHOULD display the cell transfer delay values.
      The x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the cell transfer delay for each VCC in ms.  There SHOULD be 12
      curves on the graph, one curves indicated and labeled for each
      VCC.  The integration time per point MUST be indicated.

      The histograms SHOULD display the cell transfer delay.  There will
      be one histogram for each VCC.  The x-coordinate SHOULD be the
      cell transfer delay in us with at least 256 bins.  The y-
      coordinate SHOULD be the number of cells observed in each bin.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      bearer class of the created VCC MUST also be indicated.

3.2.6.10. CTD/Bursty UBR Load/Maximum VCCs

   Objective: To determine the SUT variation in cell transfer delay with
   the maximum number VCCs supported on the SUT as defined in RFC 2761
   "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing timestamps at a
       specific UBR through the SUT via the defined test VCCs.  All of
       the VPI/VCI pairs will generate traffic at the same traffic rate.
       Since this test is not a throughput test, the rate should not be
       greater than 90% of line rate.  The IP PDUs MUST be encapsulated
       in AAL5.




Dunn & Martin                Informational                     [Page 87]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device for all VCCs.

   Reporting Format:

      The results of the CTD/Bursty UBR Load/Maximum VCCs test SHOULD be
      reported in a form of text, graphs, and histograms.

      The text results SHOULD display the numerical values of the CTD.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI values, total number of cells transmitted and received on
      each VCC during the test in positive integers, maximum and minimum
      CTD on each VCC during the test in us, and mean CTD on each VCC in
      us.

      The graph results SHOULD display the cell transfer delay values.
      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the cell transfer delay for each VCC in
      us.  There SHOULD be no more than 10 curves on each graph, one
      curve indicated and labeled for each VCC.  The integration time
      per point MUST be indicated.

      The histograms SHOULD display the cell transfer delay.  There will
      be one histogram for each VCC.  The x-coordinate SHOULD be the
      cell transfer delay in us with at least 256 bins.  The y-
      coordinate SHOULD be the number of cells observed in each bin.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      bearer class of the created VCC MUST also be indicated.

3.2.6.11. CTD/Mixed Load/Three VCC's

   Objective: To determine the SUT variation in cell transfer delay with
   three VCC's as defined in RFC 2761 "Terminology for ATM
   Benchmarking".






Dunn & Martin                Informational                     [Page 88]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing timestamps
       through the SUT via the defined test VCCs.  Each generated VCC
       stream MUST match the corresponding VCC Bearer class.  All of the
       VPI/VCI pairs will generate traffic at the same traffic rate.
       Since this test is not a throughput test, the rate should not be
       greater than 90% of line rate.  The IP PDUs MUST be encapsulated
       in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device for all VCC's.

   Reporting Format:

      The results of the CTD/Mixed Load/Three VCC test SHOULD be
      reported in a form of text, graph, and histogram.

      The text results SHOULD display the numerical values of the CTD.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI value, total number of cells transmitted and received on
      the given VPI/VCI during the test in positive integers, minimum,
      maximum, and mean CTD during the test in us.

      The graph results SHOULD display the cell transfer delay values.
      The x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the cell transfer delay in us.  The integration time per point
      MUST be indicated.







Dunn & Martin                Informational                     [Page 89]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      The histogram results SHOULD display the cell transfer delay.  The
      x-coordinate SHOULD be the cell transfer delay in us with at least
      256 bins.  The y-coordinate SHOULD be the number of cells observed
      in each bin.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.6.12. CTD/Mixed Load/Twelve VCCs

   Objective: To determine the SUT variation in cell transfer delay with
   twelve VCCs as defined in RFC 2761 "Terminology for ATM
   Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing timestamps
       through the SUT via the defined test VCCs.  Each generated VCC
       stream MUST match the corresponding VCC Bearer class.  All of the
       VPI/VCI pairs will generate traffic at the same traffic rate.
       Since this test is not a throughput test, the rate should not be
       greater than 90% of line rate.  The IP PDUs MUST be encapsulated
       in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device for all VCCs.

   Reporting Format:

      The results of the CTD/Mixed Load/Twelve VCCs test SHOULD be
      reported in a form of text, graph, and histograms.



Dunn & Martin                Informational                     [Page 90]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      The text results SHOULD display the numerical values of the CTD.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI values, total number of cells transmitted and received on
      each VCC during the test in positive integers, maximum and minimum
      CTD on each VCC during the test in us, and mean CTD on each VCC in
      us.

      The graph results SHOULD display the cell transfer delay values.
      The x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the cell transfer delay for each VCC in ms.  There SHOULD be 12
      curves on the graph, one curves indicated and labeled for each
      VCC.  The integration time per point MUST be indicated.

      The histograms SHOULD display the cell transfer delay.  There will
      be one histogram for each VCC.  The x-coordinate SHOULD be the
      cell transfer delay in us with at least 256 bins.  The y-
      coordinate SHOULD be the number of cells observed in each bin.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.

3.2.6.13. CTD/Mixed Load/Maximum VCCs

   Objective: To determine the SUT variation in cell transfer delay with
   the maximum number VCCs supported on the SUT as defined in RFC 2761
   "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).





Dunn & Martin                Informational                     [Page 91]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   3)  Send a specific number of IP packets containing timestamps
       through the SUT via the defined test VCCs.  Each generated VCC
       stream MUST match the corresponding VCC Bearer class.  All of the
       VPI/VCI pairs will generate traffic at the same traffic rate.
       Since this test is not a throughput test, the rate should not be
       greater than 90% of line rate.  The IP PDUs MUST be encapsulated
       in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the packets timestamps at the transmitter and receiver
       ends of the test device for all VCCs.

   Reporting Format:

      The results of the CTD/Mixed Load/Maximum VCCs test SHOULD be
      reported in a form of text, graphs, and histograms.

      The text results SHOULD display the numerical values of the CTD.
      The values given SHOULD include: time period of test in s, test
      VPI/VCI values, total number of cells transmitted and received on
      each VCC during the test in positive integers, maximum and minimum
      CTD on each VCC during the test in us, and mean CTD on each VCC in
      us.

      The graph results SHOULD display the cell transfer delay values.
      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the cell transfer delay for each VCC in
      us.  There SHOULD be no more than 10 curves on each graph, one
      curve indicated and labeled for each VCC.  The integration time
      per point MUST be indicated.

      The histograms SHOULD display the cell transfer delay.  There will
      be one histogram for each VCC.  The x-coordinate SHOULD be the
      cell transfer delay in us with at least 256 bins.  The y-
      coordinate SHOULD be the number of cells observed in each bin.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST also be indicated.



Dunn & Martin                Informational                     [Page 92]

RFC 3116            Methodology for ATM Benchmarking           June 2001


3.3. ATM Adaptation Layer (AAL) Type 5 (AAL5)

3.3.1. IP Packet Loss due to AAL5 Re-assembly Errors

   Objective: To determine if the SUT will drop IP packets due AAL5 Re-
   assembly Errors as defined in RFC 2761 "Terminology for ATM
   Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the uni-directional
       configuration.

   2)  Send a specific number of cells at a specific rate through the
       SUT.  Since this test is not a throughput test, the rate should
       not be greater than 90% of line rate.  The cell payload SHOULD
       contain valid IP PDUs.  The IP PDUs MUST be encapsulated in AAL5.

   3)  Count the cells that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   4)  Inject one error in the first bit of the AAL5 payload.  Verify
       that the SUT does not drop any AAL5 PDU's.

   5)  Discontinue the AAL5 payload error.

   6)  Inject one error in the first bit of the AAL5 header for 4
       consecutive IP PDUs in every 6 IP PDUs.  Verify that the SUT does
       drop the AAL5 PDU's.

   7)  Discontinue the AAL5 payload error.

   Reporting Format:

      The results of the AAL5 PDU Loss due to AAL5 PDU errors test
      SHOULD be reported in a form of a table.  The rows SHOULD be
      labeled single error, one error per second, and four consecutive
      errors every 6 IP PDUs.  The columns SHOULD be labeled AAL5 PDU
      loss and number of PDU's lost.  The elements of column 1 SHOULD be
      either True or False, indicating whether the particular condition
      was observed for each test.  The elements of column 2 SHOULD be
      non-negative integers.

      The table MUST also indicate the traffic rate in IP PDUs per
      second as generated by the test device.




Dunn & Martin                Informational                     [Page 93]

RFC 3116            Methodology for ATM Benchmarking           June 2001


3.3.2. AAL5 Reassembly Time.

   Objective: To determine the SUT AAL5 Reassembly Time as defined in
   RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the uni-directional
       configuration.

   2)  Send a specific number of IP packets at a specific rate through
       the SUT.  Since this test is not a throughput test, the rate
       should not be greater than 90% of line rate.  The IP PDUs MUST be
       encapsulated in AAL5.  The AAL5 PDU size is 65535 octets or 1365
       ATM cells.

   3)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   4)  Given an AAL5 reassembly timer of 'x' seconds, where 'x' is the
       actual value of the AAL5 reassembly timer on the SUT, sent
       traffic at 1365 cells per 'x' seconds.  The expected results are
       that no AAL5 PDU's will be dropped.

   5)  Send traffic at 1360 cells per 'x' seconds.  The expected results
       are that all AAL5 PDU's will be dropped.

   Reporting Format:

      The results of the IP packet loss due to AAL5 reassembly timeout
      test SHOULD be reported in a form of a table.  The rows SHOULD be
      labeled 1365 cells per 'x' seconds and 1360 cells per 'x' seconds.
      The columns SHOULD be labeled packet loss and number of packets
      lost.  The elements of column 1 SHOULD be either True or False,
      indicating whether the particular condition was observed for each
      test.  The elements of column 2 SHOULD be non-negative integers.

      The table MUST also indicate the packet size in octets and traffic
      rate in packets per second as generated by the test device,
      including the value of









Dunn & Martin                Informational                     [Page 94]

RFC 3116            Methodology for ATM Benchmarking           June 2001


3.3.3. AAL5 CRC Error Ratio.

3.3.3.1. Test Setup

   The AAL5 CRC error ratio measurements assume that both the
   transmitter and receiver payload information is synchronized.
   Synchronization MUST be achieved by supplying a known bit pattern to
   both the transmitter and receiver.  If this bit pattern is longer
   than the packet size, the receiver MUST synchronize with the
   transmitter before tests can be run.

3.3.3.2. AAL5-CRC-ER/Steady Load/One VCC

   Objective: To determine the SUT ratio of AAL5 CRC PDU errors on one
   VCC in a transmission in relation to the total AAL5 PDU's sent as
   defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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,
       VBR, or UBR connection.  The VPI/VCI MUST not be one of the
       reserved ATM signaling channels (e.g., [0,5], [0,16]).

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a constant rate through the SUT via the
       defined test VCC.  Since this test is not a throughput test, the
       rate should not be greater than 90% of line rate.  The IP PDUs
       MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the number of AAL5 CRC errors at the receiver end of the
       test device.

   Reporting Format:

      The results of the AAL5-CRC-ER/Steady Load/One VCC test SHOULD be
      reported in a form of text and graph.






Dunn & Martin                Informational                     [Page 95]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      The text results SHOULD display the numerical values of the AAL5-
      CRC-ER.  The values given SHOULD include: time period of test in
      s, test VPI/VCI value, total number of AAL5 PDU's transmitted and
      received on the given VPI/VCI during the test in positive
      integers, and the AAL5-CRC-ER for the entire test.

      The graph results SHOULD display the AAL5 CRC error ratio values.
      The x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the AAL5-CRC-ER.  The integration time per point MUST be
      indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST be indicated.  The generated bit pattern MUST
      also be indicated.

3.3.3.3. AAL5-CRC-ER/Steady Load/Twelve VCCs

   Objective: To determine the SUT ratio of AAL5 CRC PDU errors on
   twelve VCC's in a transmission in relation to the total AAL5 PDU's
   sent as defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a constant rate through the SUT via the
       defined test VCCs.  All of the VPI/VCI pairs will generate
       traffic at the same traffic rate.

       Since this test is not a throughput test, the rate should not be
       greater than 90% of line rate.  The IP PDUs MUST be encapsulated
       in AAL5.







Dunn & Martin                Informational                     [Page 96]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of AAL5 CRC errors at the receiver end of the
       test device for all VCCs.

   Reporting Format:

      The results of the AAL5-CRC-ER/Steady Load/Twelve VCCs test SHOULD
      be reported in a form of text and graph.

      The text results SHOULD display the numerical values of the AAL5-
      CRC-ER.  The values given SHOULD include: time period of test in
      s, test VPI/VCI value, total number of AAL5 PDU's transmitted and
      received on the given VPI/VCI during the test in positive
      integers, and the AAL5-CRC-ER for the entire test.

      The graph results SHOULD display the AAL5 CRC error ratio values.
      The x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the AAL5-CRC-ER for each VCC.  There should be 12 curves on the
      graph, on curve indicated and labeled for each VCC.  The
      integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST be indicated.  The generated bit pattern MUST
      also be indicated.

3.3.3.4. AAL5-CRC-ER/Steady Load/Maximum VCCs

   Objective: To determine the SUT ratio of AAL5 CRC PDU errors with the
   maximum number VCCs supported on the SUT in a transmission in
   relation to the total AAL5 PDU's sent as defined in RFC 2761
   "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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



Dunn & Martin                Informational                     [Page 97]

RFC 3116            Methodology for ATM Benchmarking           June 2001


       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]).

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a constant rate through the SUT via the
       defined test VCCs.  All of the VPI/VCI pairs will generate
       traffic at the same traffic rate.  Since this test is not a
       throughput test, the rate should not be greater than 90% of line
       rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of AAL5 CRC errors at the receiver end of the
       test device for all VCCs.

   Reporting Format:

      The results of the AAL5-CRC-ER/Steady Load/Maximum VCCs test
      SHOULD be reported in a form of text and graph.

      The text results SHOULD display the numerical values of the AAL5-
      CRC-ER.  The values given SHOULD include: time period of test in
      s, test VPI/VCI value, total number of AAL5 PDU's transmitted and
      received on the given VPI/VCI during the test in positive
      integers, and the AAL5-CRC-ER for the entire test.

      The graph results SHOULD display the AAL5 CRC error ratio values.
      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the AAL5-CRC-ER for each VCC.  There
      SHOULD be no more than 10 curves on each graph, one curve
      indicated and labeled for each VCC.  The integration time per
      point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST be indicated.  The generated bit pattern MUST
      also be indicated.




Dunn & Martin                Informational                     [Page 98]

RFC 3116            Methodology for ATM Benchmarking           June 2001


3.3.3.5. AAL5-CRC-ER/Bursty VBR Load/One VCC

   Objective: To determine the SUT ratio of AAL5 CRC PDU errors on one
   VCC in a transmission in relation to the total AAL5 PDU's sent as
   defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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.

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific VBR rate through the SUT via
       the defined test VCC.  Since this test is not a throughput test,
       the rate should not be greater than 90% of line rate.  The IP
       PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the number of AAL5 CRC errors at the receiver end of the
       test device.

   Reporting Format:

      The results of the AAL5-CRC-ER/Bursty VBR Load/One VCC test SHOULD
      be reported in a form of text and graph.

      The text results SHOULD display the numerical values of the AAL5-
      CRC-ER.  The values given SHOULD include: time period of test in
      s, test VPI/VCI value, total number of AAL5 PDU's transmitted and
      received on the given VPI/VCI during the test in positive
      integers, and the AAL5-CRC-ER for the entire test.

      The graph results SHOULD display the AAL5 CRC error ratio values.
      The x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The





Dunn & Martin                Informational                     [Page 99]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the AAL5-CRC-ER.  The integration time per point MUST be
      indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST be indicated.  The generated bit pattern MUST
      also be indicated.

3.3.3.6. AAL5-CRC-ER/Bursty VBR Load/Twelve VCCs

   Objective: To determine the SUT ratio of AAL5 CRC PDU errors on
   twelve VCC's in a transmission in relation to the total AAL5 PDU's
   sent as defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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.

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific VBR rate through the SUT via
       the defined test VCCs.  All of the VPI/VCI pairs will generate
       traffic at the same traffic rate.  Since this test is not a
       throughput test, the rate should not be greater than 90% of line
       rate.  The PCR, SCR, and MBS must be indicated.  The IP PDUs MUST
       be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of AAL5 CRC errors at the receiver end of the
       test device for all VCCs.







Dunn & Martin                Informational                    [Page 100]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   Reporting Format:

      The results of the AAL5-CRC-ER/Bursty VBR Load/Twelve VCCs test
      SHOULD be reported in a form of text and graph.

      The text results SHOULD display the numerical values of the AAL5-
      CRC-ER.  The values given SHOULD include: time period of test in
      s, test VPI/VCI value, total number of AAL5 PDU's transmitted and
      received on the given VPI/VCI during the test in positive
      integers, and the AAL5-CRC-ER for the entire test.

      The graph results SHOULD display the AAL5 CRC error ratio values.
      The x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the AAL5-CRC-ER for each VCC.  There should be 12 curves on the
      graph, on curve indicated and labeled for each VCC.  The
      integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST be indicated.  The generated bit pattern MUST
      also be indicated.

3.3.3.7. AAL5-CRC-ER/Bursty VBR Load/Maximum VCCs

   Objective: To determine the SUT ratio of AAL5 CRC PDU errors with the
   maximum number VCCs supported on the SUT in a transmission in
   relation to the total AAL5 PDU's sent as defined in RFC 2761
   "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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.





Dunn & Martin                Informational                    [Page 101]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   3)  Send a specific number of IP packets containing one of the
       specified bit patterns at a specific VBR rate through the SUT via
       the defined test VCCs.  All of the VPI/VCI pairs will generate
       traffic at the same traffic rate.  Since this test is not a
       throughput test, the rate should not be greater than 90% of line
       rate.  The IP PDUs MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of AAL5 CRC errors at the receiver end of the
       test device for all VCCs.

   Reporting Format:

      The results of the AAL5-CRC-ER/Bursty VBR Load/Maximum VCCs test
      SHOULD be reported in a form of text and graph.

      The text results SHOULD display the numerical values of the AAL5-
      CRC-ER.  The values given SHOULD include: time period of test in
      s, test VPI/VCI value, total number of AAL5 PDU's transmitted and
      received on the given VPI/VCI during the test in positive
      integers, and the AAL5-CRC-ER for the entire test.

      The graph results SHOULD display the AAL5 CRC error ratio values.
      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the AAL5-CRC-ER for each VCC.  There
      SHOULD be no more than 10 curves on each graph, one curve
      indicated and labeled for each VCC.  The integration time per
      point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST be indicated.  The generated bit pattern MUST
      also be indicated.

3.3.3.8. AAL5-CRC-ER/Mixed Load/Three VCC's

   Objective: To determine the SUT ratio of AAL5 CRC PDU errors on three
   VCC's in a transmission in relation to the total AAL5 PDU's sent as
   defined in RFC 2761 "Terminology for ATM Benchmarking".



Dunn & Martin                Informational                    [Page 102]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns through the SUT via the defined test VCCs.
       Each generated VCC stream MUST match the corresponding VCC Bearer
       class.  All of the VPI/VCI pairs will generate traffic at the
       same traffic rate.  Since this test is not a throughput test, the
       rate should not be greater than 90% of line rate.  The IP PDUs
       MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT to verify
       connectivity and load.  If the count on the test device is the
       same on the SUT, continue the test; else lower the test device
       traffic rate until the counts are the same.

   5)  Record the number of AAL5 CRC errors at the receiver end of the
       test device for all VCCs.

   Reporting Format:

      The results of the AAL5-CRC-ER/Bursty Mixed Load/Three VCCs test
      SHOULD be reported in a form of text and graph.

      The text results SHOULD display the numerical values of the AAL5-
      CRC-ER.  The values given SHOULD include: time period of test in
      s, test VPI/VCI value, total number of AAL5 PDU's transmitted and
      received on the given VPI/VCI during the test in positive
      integers, and the AAL5-CRC-ER for the entire test.

      The graph results SHOULD display the AAL5 CRC error ratio values.
      The x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the AAL5-CRC-ER for each VCC.  There should be 12 curves on the
      graph, on curve indicated and labeled for each VCC.  The
      integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the



Dunn & Martin                Informational                    [Page 103]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST be indicated.  The generated bit pattern MUST
      also be indicated.

3.3.3.9. AAL5-CRC-ER/Mixed Load/Twelve VCCs

   Objective: To determine the SUT ratio of AAL5 CRC PDU errors on
   twelve VCC's in a transmission in relation to the total AAL5 PDU's
   sent as defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns through the SUT via the defined test VCCs.
       Each generated VCC stream MUST match the corresponding VCC Bearer
       class.  All of the VPI/VCI pairs will generate traffic at the
       same traffic rate.  Since this test is not a throughput test, the
       rate should not be greater than 90% of line rate.  The IP PDUs
       MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.

   5)  Record the number of AAL5 CRC errors at the receiver end of the
       test device for all VCCs.

   Reporting Format:

      The results of the AAL5-CRC-ER/Bursty Mixed Load/Twelve VCCs test
      SHOULD be reported in a form of text and graph.

      The text results SHOULD display the numerical values of the AAL5-
      CRC-ER.  The values given SHOULD include: time period of test in
      s, test VPI/VCI value, total number of AAL5 PDU's transmitted and
      received on the given VPI/VCI during the test in positive
      integers, and the AAL5-CRC-ER for the entire test.



Dunn & Martin                Informational                    [Page 104]

RFC 3116            Methodology for ATM Benchmarking           June 2001


      The graph results SHOULD display the AAL5 CRC error ratio values.
      The x-coordinate SHOULD be the test run time in either seconds,
      minutes or days depending on the total length of the test.  The
      x-coordinate time SHOULD be configurable.  The y-coordinate SHOULD
      be the AAL5-CRC-ER for each VCC.  There should be 12 curves on the
      graph, on curve indicated and labeled for each VCC.  The
      integration time per point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST be indicated.  The generated bit pattern MUST
      also be indicated.

3.3.3.10. AAL5-CRC-ER/Mixed Load/Maximum VCCs

   Objective: To determine the SUT ratio of AAL5 CRC PDU errors with the
   maximum number VCCs supported on the SUT in a transmission in
   relation to the total AAL5 PDU's sent as defined in RFC 2761
   "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   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]).

   3)  Send a specific number of IP packets containing one of the
       specified bit patterns through the SUT via the defined test VCCs.
       Each generated VCC stream MUST match the corresponding VCC Bearer
       class.  All of the VPI/VCI pairs will generate traffic at the
       same traffic rate.  Since this test is not a throughput test, the
       rate should not be greater than 90% of line rate.  The IP PDUs
       MUST be encapsulated in AAL5.

   4)  Count the IP packets that are transmitted by the SUT on all VCCs
       to verify connectivity and load.  If the count on the test device
       is the same on the SUT, continue the test; else lower the test
       device traffic rate until the counts are the same.




Dunn & Martin                Informational                    [Page 105]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   5)  Record the number of AAL5 CRC errors at the receiver end of the
       test device for all VCCs.

   Reporting Format:

      The results of the AAL5-CRC-ER/Bursty Mixed Load/Maximum VCCs test
      SHOULD be reported in a form of text and graph.

      The text results SHOULD display the numerical values of the AAL5-
      CRC-ER.  The values given SHOULD include: time period of test in
      s, test VPI/VCI value, total number of AAL5 PDU's transmitted and
      received on the given VPI/VCI during the test in positive
      integers, and the AAL5-CRC-ER for the entire test.

      The graph results SHOULD display the AAL5 CRC error ratio values.
      There will be (Max number of VCCs/10) graphs, with 10 VCCs
      indicated on each graph.  The x-coordinate SHOULD be the test run
      time in either seconds, minutes or days depending on the total
      length of the test.  The x-coordinate time SHOULD be configurable.
      The y-coordinate SHOULD be the AAL5-CRC-ER for each VCC.  There
      SHOULD be no more than 10 curves on each graph, one curve
      indicated and labeled for each VCC.  The integration time per
      point MUST be indicated.

      The results MUST also indicate the packet size in octets, traffic
      rate in packets per second, and bearer class as generated by the
      test device.  The VCC and VPI/VCI values MUST be indicated.  The
      PCR, SCR, and MBS MUST be indicated.  The bearer class of the
      created VCC MUST be indicated.  The generated bit pattern MUST
      also be indicated.

3.4. ATM Service: Signaling

3.4.1. CAC Denial Time and Connection Establishment Time

   Objective: To determine the CAC rejection time and Connection
   Establishment Time on the SUT as defined in RFC 2761 "Terminology for
   ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   2)  Create a UNI signaling setup message, as described in Appendix C,
       specifying a PCR which will not allow CAC to reject the call.





Dunn & Martin                Informational                    [Page 106]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   3)  Send the UNI signaling setup message.  Note the time the setup
       message was sent.  Verify that the SVC has been setup with the
       correct parameters.  Note the time the connect message was
       received

   4)  Create a UNI signaling setup message, as described in Appendix C,
       specifying a PCR which will allow CAC to reject the call.

   5)  Send the UNI signaling setup message.  Note the time the setup
       message was sent.  Verify that the SVC has been rejected with the
       correct cause code.  Note the time the release complete message
       was received.

   6)  Compute the rejection time as the difference between the time the
       release complete message was received and the time setup message
       was send.

   Reporting Format:

      The results of the CAC Denial Time and Connection Establishment
      Time tests SHOULD be reported in a form of a table.  The rows
      SHOULD be labeled call accepted and call rejected.  The columns
      SHOULD be labeled time setup sent, time response received, and
      correct response.  The elements of the columns 1 and 2 SHOULD be
      in seconds.  The elements of column 3 SHOULD be be either True or
      False, indicating whether the particular condition was observed
      for each test.

      The table MUST also indicate the packet size in octets and traffic
      rate in packets per second as generated by the test device.

3.4.2. Connection Teardown Time

   Objective: To determine the Connection Teardown Time on the SUT as
   defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   2)  Create a UNI signaling setup message, as described in Appendix C,
       specifying a PCR which will not allow CAC to reject the call.

   3)  Send the UNI signaling setup message.  Note the time the setup
       message was sent.  Verify that the SVC has been setup with the
       correct parameters.  Note the time the connect message was
       received



Dunn & Martin                Informational                    [Page 107]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   4)  Create a UNI signaling release message, as described in Appendix
       C, specifying a cause code of normal call clearing.

   5)  Send the UNI signaling release message.  Note the time the
       release message was sent.  Verify that the SVC has been
       terminated with the correct cause code.  Note the time the
       release complete message was received.

   6)  Compute the release time as the difference between the time the
       release complete message was received and the time release
       message was send.

   Reporting Format:

      The results of the Connection Teardown Time tests SHOULD be
      reported in a form of a table.  The rows SHOULD be labeled call
      accepted and call released.  The columns SHOULD be labeled time
      message sent, time response received, and correct response.  The
      elements of the columns 1 and 2 SHOULD be in seconds.  The
      elements of column 3 SHOULD be be either True or False, indicating
      whether the particular condition was observed for each test.

      The table MUST also indicate the packet size in octets and traffic
      rate in packets per second as generated by the test device.

3.4.3. Crankback Time

   Objective: To determine the Crankback Time on the SUT as defined in
   RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the uni-directional
       passthrough configuration.

   2)  Create a PNNI signaling setup message, as described in Appendix
       C, specifying a DTL which is not blocked by the far end SUT.

   3)  Send the PNNI signaling setup message.  Note the time the setup
       message was sent.  Verify that the connect message has been
       received by the near-end switch.  Note the time the connect
       message was received

   4)  Create a PNNI signaling setup message, as described in Appendix
       C, specifying a DTL which is blocked by the far end SUT.

   5)  Send the PNNI signaling release message.  Note the time the
       release message was sent.  Note the time the release complete



Dunn & Martin                Informational                    [Page 108]

RFC 3116            Methodology for ATM Benchmarking           June 2001


       message was received.  Note the time the near-end switch sends
       it's own PNNI setup message (referred to as the near-end setup
       message) specifying the non- blocked DTL.

   6)  Compute the crankback time as the difference between the time the
       near-end setup message was received and the time release message
       was send.

   Reporting Format:

      The results of the Crankback Time tests SHOULD be reported in a
      form of a table.  The rows SHOULD be labeled DTL call accepted and
      call released.  The columns SHOULD be labeled time message sent,
      time response received, and correct response.  The elements of the
      columns 1 and 2 SHOULD be in seconds.  The elements of column 3
      SHOULD be be either True or False, indicating whether the
      particular condition was observed for each test.

      The table MUST also indicate the packet size in octets and traffic
      rate in packets per second as generated by the test device.

3.4.4. Route Update Response Time

   Objective: To determine the Route Update Response Time on the SUT as
   defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the uni-directional
       passthrough configuration.

   2)  Create a PNNI PTSE as described in Appendix C, specifying a
       routing topology.  Verify that the routing tables on the far-end
       and near-end switches are empty.

   3)  Send the PTSE message to the far-end switch.  Note the time the
       PTSE message was sent.  Verify that the PTSE message has been
       received by the far-end switch.  Note the time the PTSE message
       was received.

   4)  Create another PNNI PTSE as described in Appendix C, specifying a
       change in the routing topology.  Verify that the routing tables
       on the far-end and near-end switches contain the previous PTSE
       routes.

   5)  Send the PTSE message to the far-end switch.  Note the time the
       PTSE message was sent.  Verify that the PTSE message has been
       received by the far-end switch.  Note the time the PTSE message



Dunn & Martin                Informational                    [Page 109]

RFC 3116            Methodology for ATM Benchmarking           June 2001


       was received.  Note the time the PTSE was sent to the near-end
       switch.  Note the time the PTSE message was received on the
       near-end switch.

   6)  Compute the Route Update Response time as the difference between
       the time the far-end PTSE message was sent and the time far-end
       PTSE message was received by the near-end.

   Reporting Format:

      The results of the Route Update Response Time tests SHOULD be
      reported in a form of a table.  The rows SHOULD be labeled PTSE
      call accepted, far-end PTSE message send, and near-end message
      received.  The columns SHOULD be labeled time message sent, time
      response received, and correct response.  The elements of the
      columns 1 and 2 SHOULD be in seconds.  The elements of column 3
      SHOULD be be either True or False, indicating whether the
      particular condition was observed for each test.

      The table MUST also indicate the packet size in octets and traffic
      rate in packets per second as generated by the test device.

3.5. ATM Service: ILMI

3.5.1. MIB Alignment Time

   Objective: To determine the MIB Alignment Time on the SUT as defined
   in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   2)  Send a Cold Start message to the SUT.  Note the time the message
       was sent to the SUT.  Verify that the Cold Start message has been
       received by the SUT.  Note the time the message was received.

   3)  Send a Get Request message to the SUT.  Note the time the message
       was sent to the SUT.  Verify that the Get Request message has
       been received by the SUT.  Note the time the message was
       received.

   4)  After all MIB elements are exchanged, verify that the final Get
       Request message has been received by the SUT.  Note the time the
       message was send and received by the SUT.





Dunn & Martin                Informational                    [Page 110]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   5)  Compute the MIB Alignment Time as the difference between the time
       the Cold Start message was sent and the time the final Get
       Request was received by the SUT.

   Reporting Format:

      The results of the MIB Alignment Time tests SHOULD be reported in
      a form of a table.  The rows SHOULD be labeled Cold Start Send,
      Cold Start accepted, Final Get Request send, and Final Get Request
      received.  The columns SHOULD be labeled time message sent, time
      response received, and correct response.  The elements of the
      columns 1 and 2 SHOULD be in seconds.  The elements of column 3
      SHOULD be be either True or False, indicating whether the
      particular condition was observed for each test.

      The table MUST also indicate the packet size in octets and traffic
      rate in packets per second as generated by the test device.

3.5.2. Address Registration Time

   Objective: To determine the Address Registration Time on the SUT as
   defined in RFC 2761 "Terminology for ATM Benchmarking".

   Procedure:

   1)  Set up the SUT and test device using the bi-directional
       configuration.

   2)  Send a Set Request message to the SUT.  Note the time the message
       was sent to the SUT.  Verify that the Set Request message has
       been received by the SUT.  Note the time the message was
       received.

   3)  Send a Get Request message to the SUT.  Note the time the message
       was sent to the SUT.  Verify that the Get Request message has
       been received by the SUT.  Note the time the message was
       received.

   4)  After all MIB elements are exchanged, verify that the final Get
       Request message has been received by the SUT.  Note the time the
       message was send and received by the SUT.

   5)  Compute the Address Registration Time as the difference between
       the time the Set Request message was sent and the time the final
       Get Request was received by the SUT.






Dunn & Martin                Informational                    [Page 111]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   Reporting Format:

      The results of the Address Registration Time tests SHOULD be
      reported in a form of a table.  The rows SHOULD be labeled Set
      Request Send, Set Request accepted, Final Get Request send, and
      Final Get Request received.  The columns SHOULD be labeled time
      message sent, time response received, and correct response.  The
      elements of the columns 1 and 2 SHOULD be in seconds.  The
      elements of column 3 SHOULD be be either True or False, indicating
      whether the particular condition was observed for each test.

      The table MUST also indicate the packet size in octets and traffic
      rate in packets per second as generated by the test device.

4. Security Considerations

   As this document is solely for the purpose of providing methodology
   and describes neither a protocol nor an implementation, there are no
   security considerations associated with this document.

5. Notices

   The IETF takes no position regarding the validity or scope of any
   intellectual property or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; neither does it represent that it
   has made any effort to identify any such rights.  Information on the
   IETFs procedures with respect to rights in standards-track and
   standards-related documentation can be found in BCP-11.  Copies of
   claims of rights made available for publication and any assurances of
   licenses to be made available, or the result of an attempt made to
   obtain a general license or permission for the use of such
   proprietary rights by implementors or users of this specification can
   be obtained from the IETF Secretariat.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights which may cover technology that may be required to practice
   this standard.  Please address the information to the IETF Executive
   Director.










Dunn & Martin                Informational                    [Page 112]

RFC 3116            Methodology for ATM Benchmarking           June 2001


6. References

   [RFC2544]      Bradner, S. and J. McQuaid, "Benchmarking Methodology
                  for Network Interconnect Devices", RFC 2544, March
                  1999.

   [RFC2225]      Laubach, M. and J. Halpern, "Classical IP and ARP over
                  ATM", RFC 2225, April 1998.

   [RFC2761]      Dunn, J. and C. Martin, "Terminology for ATM
                  Benchmarking", RFC 2761, February 2000.

   [AF-ILMI4.0]   ATM Forum Integrated Local Management Interface
                  Version 4.0, af-ilmi-0065.000, September 1996.

   [AF-TEST-0022] Introduction to ATM Forum Test Specifications, af-
                  test-0022.00, December 1994.

   [AF-TM4.1]     ATM Forum, Traffic Management Specification Version
                  4.1, af-tm-0121.00, April 1996.

   [AF-UNI3.1]    ATM Forum, User Network Interface Specification
                  Version 3.1, September 1994.

   [AF-UNI4.0]    ATM Forum, User Network Interface Specification
                  Version 4.0, July 1996.

7. Authors' Addresses

   Jeffrey Dunn
   Advanced Network Consultants, Inc.
   4214 Crest Place
   Ellicott City, MD 21043, USA

   Phone: +1 (410) 750-1700
   EMail: Jeffrey.Dunn@worldnet.att.net


   Cynthia Martin
   Advanced Network Consultants, Inc.
   4214 Crest Place
   Ellicott City, MD 21043, USA

   Phone: +1 (410) 750-1700
   EMail: Cynthia.E.Martin@worldnet.att.net






Dunn & Martin                Informational                    [Page 113]

RFC 3116            Methodology for ATM Benchmarking           June 2001


Appendix A: Ranges

   ATM NSAP Network Prefix.
     39 0000 0000 0000 0000 0000 0000-39 0000 0000 0000 0000 0000 00FF
     39 0000 0000 0000 0000 0001 0000-39 0000 0000 0000 0000 0001 00FF
     39 0000 0000 0000 0001 0000 0000
     39 0000 0000 0000 0002 0020 0000
     39 0000 0000 0300 0002 0030 0000
     39 0000 0000 4000 0002 0060 0000
     39 0000 0006 0060 0002 0030 0000
     39 0000 0006 0050 0002 0030 0000
     39 0000 0009 0300 0002 0030 0000
     39 0000 00A0 0300 0002 0030 0000
     39 0000 0B00 0300 0002 0030 0000
     39 0000 C000 0300 0002 0030 0000

   ATM NSAP End System Identifier.
     1111 1111 1111 00-1111 1111 11FF 00
     2222 2222 2000 00-2222 2222 2222 00
     9999 999A 0000 00-9999 999C 0000 00

Appendix B: Rates

   PNNI Routing Update Size.

   1) 1 PNNI routing entry update on non-aggregated addresses

   2) 2 PNNI routing entry updates on non-aggregated addresses

   3) 5 PNNI routing entry updates on non-aggregated addresses

   4) 1 % of total available bandwidth or 1 Mb/s, whichever is less on
      non- aggregated addresses

   5) 1 % of total available bandwidth or 1 Mb/s, whichever is less on
      of non-aggregated addresses and of aggregated addresses

   6) 1 % of total available bandwidth or 1 Mb/s, whichever is less on
      aggregated addresses

   7) 2 % of total available bandwidth or 2 Mb/s, whichever is less on
      non- aggregated addresses

   8) 2 % of total available bandwidth or 2 Mb/s, whichever is less on
      of non-aggregated addresses and of aggregated addresses

   9) 2 % of total available bandwidth or 2 Mb/s, whichever is less on
      aggregated addresses



Dunn & Martin                Informational                    [Page 114]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   PNNI Routing Update Repetition Interval.

   Repetition Interval begins after initial PNNI routing table
      stabilizes.

   1) 1 update every 1 hour, for 24 hours

   2) 1 update every 30 minutes, for 24 hours

   3) 1 update every 5 minutes, for 1 hour

   4) 1 update every 1 minute, for 15 minutes

   5) 1 update every 30 seconds, for 5 minutes

   6) 1 update every 30 seconds, for 1 minute

   7) 1 update every 1 second, for 30 seconds

   Maximum WAN Connection rates in packets per second (pps):

                    25.6        OC-3c       OC-12c
   IP Packet Size
   octets/cells
       44/2         30188       176603      706412
       64/2         30188       176603      706412
      128/3         20125       117735      470940
      256/6         10062        58867      235468
    1024/22          2744        16054      64216
    1518/32          1886        11037      44148
    2048/43          1404         8214      32856
    4472/94           642         3757      15028
   9180/192           314         1839       7356

   Maximum LAN Connection rates in packets per second (pps):

                    DS-1       DS-3       E1        E3
   IP Packet Size
   octets/cells
       44/2          1811      52133      2340     40000
       64/2          1811      52133      2340     40000
      128/3          1207      34755      1560     26666
      256/6           603      17377       780     13333
    1024/22           164       4739       212      3636
    1518/32           113       3258       146      2500
    2048/43            84       2424       108      1860
    4472/94            38       1109        49       851
    9180/192           18        543        24       416



Dunn & Martin                Informational                    [Page 115]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   Notes: 1.  PDU size in cells is computed based on ceiling( ( PDU size
   in octets + 16) / 48).  This assumes an 8 octet LLC/SNAP header and
   an 8 octet AAL/5 trailer.

   2.  Due to the number of possible configurations, IMA pps rates are
   not listed, but may be derived from the following formula: floor
   (IDCR/cells per packet), where cells per packet is computed as in
   note 1.

   3. The following cell rates were used: DS-1 = 3622 cps (using ATM TC)
   E1 = 4681 cps 25.6 Mb/s = 60377 cps E3 = 80000 cps (using ATM TC)
   DS-3 = 104266 cps (using ATM TC) OC-3c = 353207 cps OC-12c = 1412828
   cps

Appendix C: PDU's

 TCP/IP over ATM Example 1.
    LLC:    DSAP                        0xAA (SNAP-SAP)
                SSAP                       0xAA (SNAP-SAP)
                Control                    0x03 (Unnumbered Information)
    SNAP: OUI                           0x00-00-00 (Ethertype)
                 PID                       0x0800 (Internet Protocol)
    IP:      Version = 4
             Header length = 20
             Type of service = 0
                 000. .... Precedence = Routine(0)
                 ...0 .... Delay = Normal (0)
                 .... 0... Throughput = Normal (0)
                 .... .0.. Reliability = Normal (0)
             Packet length = 40
             Id = 0
             Fragmentation Info = 0x0000
                 .0.. ....  .... .... Don't Fragment Bit = FALSE
                 ..0. ....  .... .... More Fragments Bit = FALSE
                 ...0 0000  0000 0000 Fragment offset = 0
             Time to live = 255
             Protocol = TCP (6)
             Header checksum = F9CF
             Source address = 15.19.209.236
             Destination address = 15.19.209.237
    TCP:     Source port = smtp (25)
             Destination port = smtp (25)
             Sequence number = 1
             Ack number = 0
             Data offset = 20
             Flags = 0x02
                 ..0. .... URGENT Flag = FALSE
                 ...0 .... ACK Flag = FALSE



Dunn & Martin                Informational                    [Page 116]

RFC 3116            Methodology for ATM Benchmarking           June 2001


                 .... 0... PUSH Flag = FALSE
                 .... .0.. RST Flag = FALSE
                 .... ..1. SYN Flag = TRUE
                 .... ...0 FIN Flag = FALSE
             Window = 0
             Checksum = EDAF
             Urgent pointer = 00000000

 TCP/IP over ATM Example 2.
LLC:     DSAP                         0xAA (SNAP-SAP)
             SSAP                        0xAA (SNAP-SAP)
             Control                     0x03 (Unnumbered Information)
    SNAP:  OUI                        0x00-00-00 (Ethertype)
             PID                         0x0800 (Internet Protocol)
    IP:      Version = 4
             Header length = 20
             Type of service = 0
                 000. .... Precedence = Routine(0)
                 ...0 .... Delay = Normal (0)
                 .... 0... Throughput = Normal (0)
                 .... .0.. Reliability = Normal (0)
             Packet length = 40
             Id = 0
             Fragmentation Info = 0x0000
                 .0.. ....  .... .... Don't Fragment Bit = FALSE
                 ..0. ....  .... .... More Fragments Bit = FALSE
                 ...0 0000  0000 0000 Fragment offset = 0
             Time to live = 255
             Protocol = TCP (6)
             Header checksum = F9CF
             Source address = 15.19.209.236
             Destination address = 15.19.209.237
    TCP:     Source port = ftp-data (20)
             Destination port = 2000
             Sequence number = 1
             Ack number = 0
             Data offset = 20
             Flags = 0x02
                 ..0. .... URGENT Flag = FALSE
                 ...0 .... ACK Flag = FALSE
                 .... 0... PUSH Flag = FALSE
                 .... .0.. RST Flag = FALSE
                 .... ..1. SYN Flag = TRUE
                 .... ...0 FIN Flag = FALSE
             Window = 0
             Checksum = E5FD
             Urgent pointer = 00000000




Dunn & Martin                Informational                    [Page 117]

RFC 3116            Methodology for ATM Benchmarking           June 2001


 UDP/IP over ATM Example.
    LLC:    DSAP                        0xAA (SNAP-SAP)
            SSAP                        0xAA (SNAP-SAP)
            Control                     0x03 (Unnumbered Information)
    SNAP:   OUI                         0x00-00-00 (Ethertype)
            PID                         0x0800 (Internet Protocol)
    IP:      Version = 4
             Header length = 20
             Type of service = 0
                 000. .... Precedence = Routine(0)
                 ...0 .... Delay = Normal (0)
                 .... 0... Throughput = Normal (0)
                 .... .0.. Reliability = Normal (0)
             Packet length = 28
             Id = 0
             Fragmentation Info = 0x0000
                 .0.. ....  .... .... Don't Fragment Bit = FALSE
                 ..0. ....  .... .... More Fragments Bit = FALSE
                 ...0 0000  0000 0000 Fragment offset = 0
             Time to live = 255
             Protocol = ICMP (1)
             Header checksum = F9E0
             Source address = 15.19.209.236
             Destination address = 15.19.209.237
    ICMP:    Type = Echo request (8)
             Code = 0
             Checksum = F7FF
             Identifier = 0 (0x0)
             Sequence Number = 0 (0x0)

 RIP Routing Update over ATM.

    -- DATAGRAM HEADER
          offset data (hex)            description
          00     FF FF FF FF FF FF     dest MAC address is broadcast
          06     xx xx xx xx xx xx     source hardware address
          12     08 00                 type

          -- IP HEADER
          14     45                    IP version - 4, header length (4
         byte units) - 5
          15     00                    service field
          16     00 EE                 total length
          18     00 00                 ID
          20     40 00                 flags (3 bits) 4 (do not
         fragment),
                                       fragment offset-0
          22     0A                    TTL



Dunn & Martin                Informational                    [Page 118]

RFC 3116            Methodology for ATM Benchmarking           June 2001


          23     11                    protocol - 17 (UDP)
          24     C4 8D                 header checksum
          26     xx xx xx xx           source IP address
          30     xx xx xx              destination IP address
          33     FF                    host part = FF for broadcast

          -- UDP HEADER
          34     02 08                 source port 208 = RIP
          36     02 08                 destination port 208 = RIP
          38     00 DA                 UDP message length
          40     00 00                 UDP checksum

          -- RIP packet
          42     02                  command = response
          43     01                  version = 1
          44     00 00               0

          -- net 1
          46     00 02               family = IP
          48     00 00               0
          50     xx xx xx            net 1 IP address
          53     00                  net not node
          54     00 00 00 00         0
          58     00 00 00 00         0
          62     00 00 00 07         metric 7

          -- net 2

          66     00 02               family = IP
          68     00 00               0
          70     xx xx xx            net 2 IP address
          73     00                  net not node
          74     00 00 00 00         0
          78     00 00 00 00         0
          82     00 00 00 07         metric 7

          -- net 3
          86     00 02               family = IP
          88     00 00               0
          90     xx xx xx            net 3 IP address
          93     00                  net not node
          94     00 00 00 00         0
          98     00 00 00 00         0
          102    00 00 00 07         metric 7

          -- net 4
          106    00 02               family = IP
          108    00 00               0



Dunn & Martin                Informational                    [Page 119]

RFC 3116            Methodology for ATM Benchmarking           June 2001


          110    xx xx xx            net 4 IP address
          113    00                  net not node
          114    00 00 00 00         0
          118    00 00 00 00         0
          122    00 00 00 07         metric 7

          -- net 5
          126    00 02               family = IP
          128    00 00               0
          130    00                  net 5 IP address
          133    00                  net not node
          134    00 00 00 00         0
          138    00 00 00 00         0
          142    00 00 00 07         metric 7

          -- net 6
          146    00 02               family = IP
          148    00 00               0
          150    xx xx xx            net 6 IP address
          153    00                  net not node
          154    00 00 00 00         0
          158    00 00 00 00         0
          162    00 00 00 07         metric 7

   UNI  3.1 Signaling Setup Message Example.  PCR will not allow CAC to
   reject the call.

    Protocol Discriminator    : Q.93B UNI call control
    Call Reference Length     : 3
    Call Reference Flag       : orig
    Call Reference Value      : 0
    Message Type              : SETUP
    Ext                       : last octet
    Action Indicator          : clear call
    Message Length            : 50
    Information Element ID    : ATM Traffic Descriptor
    Ext                       : last octet
    Coding Standard           : ITU-T standard
    Action Indicator          : clear call
    IE Length                 : 9
    Cell Rate Subfield ID     : forward peak CR(CLP=0+1)
    Forward Peak Cell Rate    : 1
    Cell Rate Subfield ID     : backward peak CR(CLP=0+1)
    Backward Peak Cell Rate   : 1
    Cell Rate Subfield ID     : best effort indicator
    Information Element ID    : Broadband Bearer Capability
    Ext                       : last octet
    Coding Standard           : ITU-T standard



Dunn & Martin                Informational                    [Page 120]

RFC 3116            Methodology for ATM Benchmarking           June 2001


    Action Indicator          : clear call
    IE Length                 : 2
    Ext                       : last octet
    Bearer Class              : BCOB-X
    Ext                       : last octet
    Clipping Susceptibility   : not susceptible to clipping
    User Plane Connection CFG : point-to-point
    Information Element ID    : Called Party Number
    Ext                       : last octet
    Coding Standard           : ITU-T standard
    Action Indicator          : clear call
    IE Length                 : 21
    Ext                       : last octet
    Addressing/Numbering Plan : ISO NSAP addressing
    ISO NSAP Address Octets   : 3900000000000000000000000011111111111100
    Information Element ID    : Quality of Service Parameter
    Ext                       : last octet
    Coding Standard           : ITU-T standard
    Action Indicator          : clear call
    IE Length                 : 2
    QoS Class Forward         : QoS class 0 - unspecified
    QoS Class Backward        : QoS class 0 - unspecified

   UNI 3.1 Signaling Setup Message Reject Example.  PCR  will  allow
   CAC  to reject the call.

    Protocol Discriminator    : Q.93B UNI call control
    Call Reference Length     : 3
    Call Reference Flag       : orig
    Call Reference Value      : 0
    Message Type              : SETUP
    Ext                       : last octet
    Action Indicator          : clear call
    Message Length            : 50
    Information Element ID    : ATM Traffic Descriptor
    Ext                       : last octet
    Coding Standard           : ITU-T standard
    Action Indicator          : clear call
    IE Length                 : 8
    Cell Rate Subfield ID     : forward peak CR(CLP=0+1)
    Forward Peak Cell Rate    : 300000
    Cell Rate Subfield ID     : backward peak CR(CLP=0+1)
    Backward Peak Cell Rate   : 300000
    Information Element ID    : Broadband Bearer Capability
    Ext                       : last octet
    Coding Standard           : ITU-T standard
    Flag                      : not significant
    Action Indicator          : clear call



Dunn & Martin                Informational                    [Page 121]

RFC 3116            Methodology for ATM Benchmarking           June 2001


    IE Length                 : 3
    Ext                       : another octet
    Bearer Class              : BCOB-X
    Ext                       : last octet
    Traffic Type              : constant bit rate
    Timing Requirements       : end-to-end timing required
    Ext                       : last octet
    Clipping Susceptibility   : not susceptible to clipping
    User Plane Connection CFG : point-to-point
    Information Element ID    : Called Party Number
    Ext                       : last octet
    Coding Standard           : ITU-T standard
    Action Indicator          : clear call
    IE Length                 : 21
    Ext                       : last octet
    Addressing/Numbering Plan : ISO NSAP addressing
    ISO NSAP Address Octets   : 3900000000000000000000000011111111111100
    Information Element ID    : Quality of Service Parameter
    Ext                       : last octet
    Coding Standard           : ITU-T standard
    Action Indicator          : clear call
    IE Length                 : 2
    QoS Class Forward         : QoS class 0 - unspecified
    QoS Class Backward        : QoS class 0 - unspecified

   UNI  3.1 Signaling Release Message, specifying a cause code of normal
   call clearing.

    Protocol Discriminator   : Q.93B UNI call control
    Call Reference Length    : 3
    Call Reference Flag      : orig
    Call Reference Value     : 0
    Message Type             : RELEASE
    Ext                      : last octet
    Action Indicator         : clear call
    Message Length           : 6
    Information Element ID   : Cause
    Ext                      : last octet
    Coding Standard          : ITU-T standard
    Action Indicator         : clear call
    IE Length                : 2
    Ext                      : last octet
    Location                 : user
    Ext                      : last octet
    Cause Value              : NE:normal call clearing

   PNNI Signaling Setup Message, specifying a DTL which is not blocked
   by the far end SUT.



Dunn & Martin                Informational                    [Page 122]

RFC 3116            Methodology for ATM Benchmarking           June 2001


    Protocol Discriminator    : PNNI signalling
    Call Reference Length     : 3
    Call Reference Flag       : from
    Message Type              : SETUP
    Ext                       : last octet
    Pass Along Request        : no pass along request
    Action Indicator          : clear call
    Message Length            : 56
    Information Element ID    : ATM Traffic Descriptor
    Ext                       : last octet
    Coding Standard           : ITU-T standardized
    Pass Along Request        : no pass along request
    Action Indicator          : clear call
    IE Length                 : 0
    Information Element ID    : Broadband Bearer Capability
    Ext                       : last octet
    Coding Standard           : ITU-T standardized
    Pass Along Request        : no pass along request
    Action Indicator          : clear call
    IE Length                 : 3
    Ext                       : another octet
    Bearer Class              : BCOB-X
    Ext                       : last octet
    ATM Transfer Capability   : reserved for bwd compatibility
    Ext                       : last octet
    Clipping Susceptibility   : not susceptible to clipping
    User Plane Connection cfg : point-to-point
    Information Element ID    : Called Party Number
    Ext                       : last octet
    Coding Standard           : ITU-T standardized
    Pass Along Request        : no pass along request
    Action Indicator          : clear call
    IE Length                 : 8
    Ext                       : last octet
    Type of Number            : unknown
    Addressing/Numbering Plan : ATM endsystem address
    ATM Endsystem Address Oct : 11111111111101
    Information Element ID    : Designated Transit List
    Ext                       : last octet
    Coding Standard           : ATM Forum specific
    Pass Along Request        : no pass along request
    Action Indicator          : clear call
    IE Length                 : 29
    Current Transit Pointer   : 0
    Logical Node/Port Indicat : Logical Node/Port Indicator
    Logical Node Identifier   : 3900000000000000000000000011111111111100





Dunn & Martin                Informational                    [Page 123]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   PNNI  Signaling Setup Message Reject, specifying a DTL which is
   blocked by the far end SUT.

Protocol Discriminator      : PNNI signalling
    Call Reference Length   : 3
    Call Reference Flag     : from
    Call Reference Value    : 0
    Message Type            : SETUP
    Ext                     : last octet
    Pass Along Request      : no pass along request
    Action Indicator        : clear call
    Message Length          : 56
    Information Element ID  : ATM Traffic Descriptor
    Ext                     : last octet
    Coding Standard         : ITU-T standardized
    Pass Along Request      : no pass along request
    Action Indicator        : clear call
    IE Length               : 0
    Information Element ID  : Broadband Bearer Capability
    Ext                     : last octet
    Coding Standard         : ITU-T standardized
    Pass Along Request      : no pass along request
    Action Indicator        : clear call
    IE Length               : 3
    Bearer Class            : BCOB-X
    Ext                     : last octet
    ATM Transfer Capability : reserved for bwd compatibility
    Ext                     : last octet
    Clipping Susceptibility : not susceptible to clipping
    User Plane Connection cfg : point-to-point
    Information Element ID  : Called Party Number
    Ext                     : last octet
    Coding Standard         : ITU-T standardized
    Pass Along Request      : no pass along request
    Action Indicator        : clear call
    IE Length               : 8
    Ext                     : last octet
    Addressing/Numbering Plan : ATM endsystem address
    ATM Endsystem Address Oct : 11111111111101
    Information Element ID    : Designated Transit List
    Ext                       : last octet
    Coding Standard           : ATM Forum specific
    Pass Along Request        : no pass along request
    Action Indicator          : clear call
    IE Length                 : 29
    Current Transit Pointer   : 0
    Logical Node/Port Indicat : Logical Node/Port Indicator
    Logical Node Identifier   : 3900000000000000000000000011111111111100



Dunn & Martin                Informational                    [Page 124]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   PNNI Far End Request Message.

Header:  Packet Type                    5 (PTSE REQUEST)
             Packet Length             40
             Protocol Version           1
             Newest Version Supported   1
             Oldest Version Supported   0
             Reserved                   0
    IG:      Information Group Type   513 (Requested PTSE Header)
             Information Group Length  32
             Originating Node ID
                   00013900-00000000-00000000-00000011-11111111-1100
             PTSE Request Count     1
             PTSE Identifier        0

   PNNI PTSE, specifying a routing topology.

Header:  Packet Type                    4 (DATABASE SUMMARY)
             Packet Length             76
             Protocol Version           1
             Newest Version Supported   1
             Oldest Version Supported   0
             Reserved                   0
             Initialize (I)Bit          1 (during init. of DB syn
                                           process)
             More (M)Bit                1 (PTSEs to summarize)
             Master (MS)Bit             1 (both nodes)
             Reserved                   0
             Reserved                   0
             DS Sequence Number         0
    IG:      Information Group Type   512 (Nodal PTSE Summaries)
             Information Group Length  60
             Originating Node ID
                 00013900-00000000-00000000-00000011-11111111-1100
             Originating Node's Peer Group 00000000-00000000-00000000-
                                           0001
             Reserved                    0
             PTSE Summary Count          1
             PTSE Type                   0
             Reserved                    0
             PTSE Identifier             0
             PTSE Sequence Number        0
             PTSE Checksum               0
             PTSE Remaining Lifetime     0







Dunn & Martin                Informational                    [Page 125]

RFC 3116            Methodology for ATM Benchmarking           June 2001


   PNNI PTSE Update, specifying a change in the routing topology.

Header:  Packet Type                    2 (PTSP)
             Packet Length             96
             Protocol Version           1
             Newest Version Supported   1
             Oldest Version Supported   0
             Reserved                   0
             Originating Node ID
                 00013900-00000000-00000000-00000011-11111111-1100
             Originating Node's Peer Group 00000000-00000000-00000000-
                                           0001
    IG:      Information Group Type     64 (PTSE)
             Information Group Length   52
             PTSE Type                   0
             Reserved                    0
             PTSE Identifier             0
             PTSE Sequence Number        0
             PTSE Checksum           42252
             PTSE Remaining Lifetime  3600
    IG:       Information Group Type   224 (Internal Reachable ATM
                                            Addresses)
             Information Group Length   32
             VP Capability Flag          1 (VPCs supported)
             Reserved                    0
             Reserved                    0
             Port ID                     0
             Scope of Advertisement     96
             Address Information Length 14
             Address Information Count   1
             Prefix Length              13
             Reachable Address Prefix   39000000-00000000-00000000-01



















Dunn & Martin                Informational                    [Page 126]

RFC 3116            Methodology for ATM Benchmarking           June 2001


Full Copyright Statement

   Copyright (C) The Internet Society (2001).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.



















Dunn & Martin                Informational                    [Page 127]