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
extern crate alloc;
use Debug;
use ;
use *;
use Bytes;
pub
pub use UnsecuredHeader;
pub use ;
pub use ;
pub use ;
use ;
;
;
/// Expresses the time in milliseconds at which the latitude and longitude
/// of the ITS-S were acquired by the GeoAdhoc router. The time is encoded as:
/// TST = TST(TAI) % 2^32
/// where TST(TAI) is the number of elapsed TAI milliseconds since 2004-01-01 00:00:00.000 UTC
;
/// Identifies the type of header immediately following the GeoNetworking Basic Header
/// Lifetime field. Indicates the maximum tolerable time a packet may be buffered until it reaches its destination
/// Bit 0 to Bit 5: LT sub-field Multiplier
/// Bit 6 to Bit 7: LT sub-field Base
;
/// Traffic class that represents Facility-layer requirements on packet transport
/// Identifies the type of header immediately following the GeoNetworking Common Header
/// Identifies the type of the GeoNetworking header
/// Area type used in header subtypes
/// Broadcast type used in header subtypes
/// Subtype of location service
type GeoBroadcast = GeoAnycast;
/// In case of a circular area (GeoNetworking packet sub-type HST = 0), the fields shall be set to the following values:
/// 1) Distance a is set to the radius r.
/// 2) Distance b is set to 0.
/// 3) Angle is set to 0.
/// only for backwards compatibility
pub type Aes128CcmCiphertext<'input> = ;
/// contains an individual `AppExtension`.
///
/// `AppExtensions` specified in this standard are drawn from the ASN.1 Information Object Set
/// `SetCertExtensions`. This set, and its use in the `AppExtension` type, is structured so that each
/// `AppExtension` is associated with a `CertIssueExtension` and a `CertRequestExtension` and all are
/// identified by the same id value.
/// Inner type
/// This field contains an individual `CertIssueExtension`.
///
/// `CertIssueExtensions` specified in this standard are drawn from the ASN.1
/// Information Object Set `SetCertExtensions`. This set, and its use in the
/// `CertIssueExtension` type, is structured so that each `CertIssueExtension`
/// is associated with a `AppExtension` and a `CertRequestExtension` and all are
/// identified by the same id value. In this structure:
/// Inner type
/// This field contains an individual `CertRequestExtension`
///
/// `CertRequestExtensions` specified in this standard are drawn from the
/// ASN.1 Information Object Set `SetCertExtensions`. This set, and its use in
/// the `CertRequestExtension` type, is structured so that each
/// `CertRequestExtension` is associated with a `AppExtension` and a
/// `CertRequestExtension` and all are identified by the same id value. In this
/// structure:
//**************************************************************************
// Certificates and other Security Management
//**************************************************************************
/// A p rofile of the structure [`CertificateBase`] which
/// specifies the valid combinations of fields to transmit implicit and
/// explicit certificates.
///
/// Note: Canonicalization: This data structure is subject to canonicalization
/// for the relevant operations specified in 6.1.2. The canonicalization
/// applies to the `CertificateBase`.
pub type Certificate<'input> = ;
/// Base certificate data
///
/// Note: Canonicalization: This data structure is subject to canonicalization
/// for the relevant operations specified in 6.1.2. The canonicalization
/// applies to the `ToBeSignedCertificate` and to the Signature.
///
/// Note: Whole-certificate hash: If the entirety of a certificate is hashed
/// to calculate a `HashedId3`, `HashedId8`, or `HashedId10`, the algorithm used for
/// this purpose is known as the whole-certificate hash. The method used to
/// determine the whole-certificate hash algorithm is specified in 5.3.9.2.
/// contains information that is used to identify the certificate holder if necessary.
///
/// Note: Critical information fields:
/// - If present, this is a critical information field as defined in 5.2.6.
///
/// An implementation that does not recognize the choice indicated in this
/// field shall reject a signed SPDU as invalid.
/// Indicates whether a certificate is explicit or implicit.
///
/// Note: Critical information fields: If present, this is a critical
/// information field as defined in 5.2.5. An implementation that does not
/// recognize the indicated CHOICE for this type when verifying a signed SPDU
/// shall indicate that the signed SPDU is invalid in the sense of 4.2.2.3.2,
/// that is, it is invalid in the sense that its validity cannot be
/// established.
/// Anonymous SEQUENCE OF member
)] &'input ,
);
/// Inner type with at least one member
)]
pub ,
);
/// Defines the format of an extension block
///
/// Defines the format of an extension block provided by an identified
/// contributor by using the temnplate provided
/// in the class IEEE1609DOT2-HEADERINFO-CONTRIBUTED-EXTENSION constraint
/// to the objects in the set `Ieee1609Dot2HeaderInfoContributedExtensions`.
/// used for clarity of definitions
///
/// At least one member
)] pub ,
);
/// Used to perform a countersignature over an already-signed SPDU
///
/// This is the profile of an `Ieee1609Dot2Data` containing
/// a signedData. The tbsData within content is composed of a payload
/// containing the hash (extDataHash) of the externally generated, pre-signed
/// SPDU over which the countersignature is performed.
pub type Countersignature<'input> = ;
//**************************************************************************
// Encrypted Data
//**************************************************************************
/// Encodes data that has been encrypted to one or more recipients using the recipients public or symmetric keys as specified in 5.3.4
///
/// Note: Critical information fields:
/// - If present, recipients is a critical information field as defined in
/// 5.2.6. An implementation that does not support the number of `RecipientInfo`
/// in recipients when decrypted shall indicate that the encrypted SPDU could
/// not be decrypted due to unsupported critical information fields. A
/// compliant implementation shall support recipients fields containing at
/// least eight entries.
///
/// Note: If the plaintext is raw data, i.e., it has not been output from a
/// previous operation of the SDS, then it is trivial to encapsulate it in an
/// `Ieee1609Dot2Data` of type unsecuredData as noted in 4.2.2.2.2. For example,
/// `03 80 08 01 23 45 67 89 AB CD EF` is the C-OER encoding of `01 23 45 67
/// 89 AB CD EF` encapsulated in an `Ieee1609Dot2Data` of type unsecuredData.
/// The first byte of the encoding 03 is the protocolVersion, the second byte
/// 80 indicates the choice unsecuredData, and the third byte 08 is the length
/// of the raw data `01 23 45 67 89 AB CD EF`.
/// Encrypted data encryption key
///
/// The data encryption key is input to the data encryption key
/// encryption process with no headers, encapsulation, or length indication.
///
/// Critical information fields: If present and applicable to
/// the receiving SDEE, this is a critical information field as defined in
/// 5.2.6. If an implementation receives an encrypted SPDU and determines that
/// one or more `RecipientInfo` fields are relevant to it, and if all of those
/// `RecipientInfos` contain an `EncryptedDataEncryptionKey` such that the
/// implementation does not recognize the indicated CHOICE, the implementation
/// shall indicate that the encrypted SPDU is not decryptable.
/// Indicates which type of permissions may appear in end-entity certificates
///
/// Permissions in end-entity certificates the chain of whose permissions passes through the
/// `PsidGroupPermissions` field containing this value. If app is indicated, the
/// end-entity certificate may contain an appPermissions field. If enroll is
/// indicated, the end-entity certificate may contain a certRequestPermissions
/// field.
;
/// Profile of the `CertificateBase` structure providing all the fields necessary for an explicit certificate, and no others
pub type ExplicitCertificate<'input> = ;
/// contains the hash of some data with a specified hash algorithm
///
/// See 5.3.3 for specification of the permitted hash algorithms.
///
/// Note: Critical information fields: If present, this is a critical
/// information field as defined in 5.2.6. An implementation that does not
/// recognize the indicated CHOICE for this type when verifying a signed SPDU
/// shall indicate that the signed SPDU is invalid in the sense of 4.2.2.3.2,
/// that is, it is invalid in the sense that its validity cannot be established.
/// contains information that is used to establish validity by the criteria of 5.2
///
/// Note: Canonicalization: This data structure is subject to canonicalization
/// for the relevant operations specified in 6.1.2. The canonicalization
/// applies to the `EncryptionKey`. If encryptionKey is present, and indicates
/// the choice public, and contains a `BasePublicEncryptionKey` that is an
/// elliptic curve point (i.e., of type `EccP256CurvePoint` or
/// `EccP384CurvePoint`), then the elliptic curve point is encoded in compressed
/// form, i.e., such that the choice indicated within the Ecc*`CurvePoint` is
/// compressed-y-0 or compressed-y-1.
///
/// The canonicalization does not apply to any fields after the extension
/// marker, including any fields in contributedExtensions.
/// integer used to identify a `HeaderInfo` extension contributing organization
///
/// In this version of this standard two values are defined:
/// - ieee1609OriginatingExtensionId indicating extensions originating with IEEE 1609.
/// - etsiOriginatingExtensionId indicating extensions originating with ETSI TC ITS.
///
/// value between 0 and 255 inclusive
;
/// Uses the parameterized type Extension to define an
/// [`Ieee1609ContributedHeaderInfoExtension`] as an open Extension Content field
/// identified by an extension identifier. The extension identifier value is
/// unique to extensions defined by ETSI and need not be unique among all
/// extension identifier values defined by all contributing organizations.
pub type Ieee1609ContributedHeaderInfoExtension<'input> = ;
/// In this structure:
///
/// Note: Canonicalization: This data structure is subject to canonicalization
/// for the relevant operations specified in 6.1.2 if it is of type signedData.
/// The canonicalization applies to the `SignedData`.
//**************************************************************************
// Secured Data
//**************************************************************************
/// This data type is used to contain the other data types in this clause
///
/// Note: Canonicalization: This data structure is subject to canonicalization
/// for the relevant operations specified in 6.1.2. The canonicalization
/// applies to the `Ieee1609Dot2Content`.
/// integer used to identify an `Ieee1609ContributedHeaderInfoExtension`
pub type Ieee1609HeaderInfoExtensionId = ExtId;
/// profile of the `CertificateBase` structure providing all
/// the fields necessary for an implicit certificate, and no others.
pub type ImplicitCertificate<'input> = ;
/// allows the recipient of a certificate to determine which keying material to use to authenticate the certificate
///
/// If the choice indicated is sha256AndDigest, sha384AndDigest, or sm3AndDigest:
/// - The structure contains the `HashedId8` of the issuing certificate. The
/// `HashedId8` is calculated with the whole-certificate hash algorithm,
/// determined as described in 6.4.3, applied to the COER-encoded certificate,
/// canonicalized as defined in the definition of Certificate.
/// - The hash algorithm to be used to generate the hash of the certificate
/// for verification is SHA-256 (in the case of sha256AndDigest), SM3 (in the
/// case of sm3AndDigest) or SHA-384 (in the case of sha384AndDigest).
/// - The certificate is to be verified with the public key of the
/// indicated issuing certificate.
///
/// If the choice indicated is self:
/// - The structure indicates what hash algorithm is to be used to generate
/// the hash of the certificate for verification.
/// - The certificate is to be verified with the public key indicated by
/// the verifyKeyIndicator field in theToBeSignedCertificate.
///
/// Note: Critical information fields: If present, this is a critical
/// information field as defined in 5.2.5. An implementation that does not
/// recognize the indicated CHOICE for this type when verifying a signed SPDU
/// shall indicate that the signed SPDU is invalid in the sense of 4.2.2.3.2,
/// that is, it is invalid in the sense that its validity cannot be
/// established.
/// Information that is matched against a linkage ID-based CRL
///
/// A linkage ID-based CRL is used to determine whether the
/// containing certificate has been revoked.
/// See 5.1.3.4 and 7.3 for details of use.
/// may be used to request a CRL that the SSME knows to have been issued and has not yet received.
///
/// It is provided for future use and its use is not defined in this version of this standard.
/// Encapsulates an encrypted ciphertext
///
/// Encapsulates an encrypted ciphertext for any
/// symmetric algorithm with 128-bit blocks in CCM mode. The ciphertext is
/// 16 bytes longer than the corresponding plaintext due to the inclusion of
/// the message authentication code (MAC). The plaintext resulting from a
/// correct decryption of the ciphertext is either a COER-encoded
/// `Ieee1609Dot2Data` structure (see 6.3.41), or a 16-byte symmetric key
/// (see 6.3.44).
///
/// The ciphertext is 16 bytes longer than the corresponding plaintext.
/// The plaintext resulting from a correct decryption of the
/// ciphertext is a COER-encoded `Ieee1609Dot2Data` structure.
///
/// Note: In the name of this structure, "One28" indicates that the
/// symmetric cipher block size is 128 bits. It happens to also be the case
/// that the keys used for both AES-128-CCM and SM4-CCM are also 128 bits long.
/// This is, however, not what One28 refers to. Since the cipher is used in
/// counter mode, i.e., as a stream cipher, the fact that that block size is 128
/// bits affects only the size of the MAC and does not affect the size of the
/// raw ciphertext.
/// `AppExtension` used to identify an operating organization
///
/// The associated `CertIssueExtension` and `CertRequestExtension`
/// are both of type `OperatingOrganizationId`.
///
/// To determine consistency between this type and an SPDU, the SDEE
/// specification for that SPDU is required to specify how the SPDU can be
/// used to determine an OBJECT IDENTIFIER (for example, by including the
/// full OBJECT IDENTIFIER in the SPDU, or by including a RELATIVE-OID with
/// clear instructions about how a full OBJECT IDENTIFIER can be obtained from
/// the RELATIVE-OID). The SPDU is then consistent with this type if the
/// OBJECT IDENTIFIER determined from the SPDU is identical to the OBJECT
/// IDENTIFIER contained in this field.
///
/// This `AppExtension` does not have consistency conditions with a
/// corresponding `CertIssueExtension`. It can appear in a certificate issued
/// by any CA.
;
/// Contains the following fields:
/// identifies the functional entity that is intended to consume an SPDU
///
/// Identifies the functional entity that is intended to consume an SPDU,
/// for the case where that functional entity is
/// not an application process, and are instead security support services for an
/// application process. Further details and the intended use of this field are
/// defined in ISO 21177 \[B20\].
///
/// param tlsHandshake: indicates that the Signed SPDU is not to be directly
/// consumed as an application PDU and is to be used to provide information
/// about the holders permissions to a Transport Layer Security (TLS)
/// (IETF 5246 \[B15\], IETF 8446 \[B16\]) handshake process operating to secure
/// communications to an application process. See IETF \[B15\] and ISO 21177
/// \[B20\] for further information.
///
/// param iso21177ExtendedAuth: indicates that the Signed SPDU is not to be
/// directly consumed as an application PDU and is to be used to provide
/// additional information about the holders permissions to the ISO 21177
/// Security Subsystem for an application process. See ISO 21177 \[B20\] for
/// further information.
///
/// param iso21177SessionExtension: indicates that the Signed SPDU is not to
/// be directly consumed as an application PDU and is to be used to extend an
/// existing ISO 21177 secure session. This enables a secure session to
/// persist beyond the lifetime of the certificates used to establish that
/// session.
;
/// Indicates a symmetric key that may be used directly to decrypt a `SymmetricCiphertext`
///
/// It consists of the low-order 8 bytes of the hash of the COER encoding of a
/// `SymmetricEncryptionKey` structure containing the symmetric key in question.
/// The `HashedId8` is calculated with the hash algorithm determined as
/// specified in 5.3.9.3. The symmetric key may be established by any
/// appropriate means agreed by the two parties to the exchange.
pub type PreSharedKeyRecipientInfo<'input> = ;
/// states the permissions that a certificate holder has
///
/// States the permissions that a certificate holder has
/// with respect to issuing and requesting certificates for a particular set
/// of PSIDs. For examples, see D.5.3 and D.5.4.
/// Transfers the data encryption key
///
/// Used to transfer the data encryption key to
/// an individual recipient of an `EncryptedData`. The option pskRecipInfo is
/// selected if the `EncryptedData` was encrypted using the static encryption
/// key approach specified in 5.3.4. The other options are selected if the
/// `EncryptedData` was encrypted using the ephemeral encryption key approach
/// specified in 5.3.4. The meanings of the choices are:
/// See Annex C.7 for guidance on when it may be appropriate to use
/// each of these approaches.
///
/// Note: If the encryption algorithm is SM2, there is no equivalent of the
/// parameter P1 and so no input to the encryption process that uses the hash
/// of the empty string.
///
/// Note: The material input to encryption is the bytes of the encryption key
/// with no headers, encapsulation, or length indication. Contrast this to
/// encryption of data, where the data is encapsulated in an `Ieee1609Dot2Data`.
/// contains any `AppExtensions` that apply to the certificate holder
///
/// As specified in 5.2.4.2.3, each individual
/// `AppExtension` type is associated with consistency conditions, specific to
/// that extension, that govern its consistency with SPDUs signed by the
/// certificate holder and with the `CertIssueExtensions` in the CA certificates
/// in that certificate holders chain. Those consistency conditions are
/// specified for each individual `AppExtension` below.
)] pub ,
);
/// This field contains any `CertIssueExtensions` that apply to the certificate holder
///
/// As specified in 5.2.4.2.3, each individual
/// `CertIssueExtension` type is associated with consistency conditions,
/// specific to that extension, that govern its consistency with
/// `AppExtensions` in certificates issued by the certificate holder and with
/// the `CertIssueExtensions` in the CA certificates in that certificate
/// holders chain. Those consistency conditions are specified for each
/// individual `CertIssueExtension` below.
)] pub ,
);
/// This field contains any `CertRequestExtensions` that apply to the certificate holder
///
/// As specified in 5.2.4.2.3, each individual
/// `CertRequestExtension` type is associated with consistency conditions,
/// specific to that extension, that govern its consistency with
/// `AppExtensions` in certificates issued by the certificate holder and with
/// the `CertRequestExtensions` in the CA certificates in that certificate
/// holders chain. Those consistency conditions are specified for each
/// individual `CertRequestExtension` below.
)] pub ,
);
/// used for clarity of definitions
)] pub ,
);
/// used for clarity of definitions
)] pub ,
);
/// used for clarity of definitions
)] pub ,
);
/// In this structure:
///
/// Note: Canonicalization: This data structure is subject to canonicalization
/// for the relevant operations specified in 6.1.2. The canonicalization
/// applies to the `ToBeSignedData` and the Signature.
/// contains the data payload of a `ToBeSignedData`
///
/// This structure contains at least one of the optional elements, and may
/// contain more than one. See 5.2.4.3.4 for more details.
///
/// The security profile in Annex C allows an implementation of this standard
/// to state which forms of Signed¬Data¬Payload are supported by that
/// implementation, and also how the signer and verifier are intended to obtain
/// the external data for hashing. The specification of an SDEE that uses
/// external data is expected to be explicit and unambiguous about how this
/// data is obtained and how it is formatted prior to processing by the hash
/// function.
///
/// Note: Canonicalization: This data structure is subject to canonicalization
/// for the relevant operations specified in 6.1.2. The canonicalization
/// applies to the `Ieee1609Dot2Data`.
/// allows the recipient of data to determine which keying material to use to authenticate the data
///
/// It also indicates the verification type to be used to generate the hash for verification, as specified in 5.3.1.
///
/// Note: Critical information fields:
/// - If present, this is a critical information field as defined in 5.2.6.
/// An implementation that does not recognize the CHOICE value for this type when verifying a signed SPDU shall indicate that the signed SPDU is invalid.
/// - If present, certificate is a critical information field as defined in 5.2.6.
/// An implementation that does not support the number of certificates in certificate when verifying a signed SPDU shall indicate that the signed SPDU is invalid.
/// A compliant implementation shall support certificate fields containing at least one certificate.
///
/// Note: Canonicalization: This data structure is subject to canonicalization
/// for the relevant operations specified in 6.1.2. The canonicalization
/// applies to every Certificate in the certificate field.
/// Indicates the granted PSIDs and associated SSPs
///
/// Indicates the PSIDs and associated SSPs for which certificate
/// issuance or request permissions are granted by a `PsidGroupPermissions`
/// structure. If this takes the value explicit, the enclosing
/// `PsidGroupPermissions` structure grants certificate issuance or request
/// permissions for the indicated PSIDs and SSP Ranges. If this takes the
/// value all, the enclosing `PsidGroupPermissions` structure grants certificate
/// issuance or request permissions for all PSIDs not indicated by other
/// `PsidGroupPermissions` in the same certIssuePermissions or
/// certRequestPermissions field.
///
/// Note: Critical information fields:
/// - If present, this is a critical information field as defined in 5.2.6.
/// An implementation that does not recognize the indicated CHOICE when
/// verifying a signed SPDU shall indicate that the signed SPDU is
/// invalidin the sense of 4.2.2.3.2, that is, it is invalid in the sense that
/// its validity cannot be established.
/// - If present, explicit is a critical information field as defined in
/// 5.2.6. An implementation that does not support the number of `PsidSspRange`
/// in explicit when verifying a signed SPDU shall indicate that the signed
/// SPDU is invalid in the sense of 4.2.2.3.2, that is, it is invalid in the
/// sense that its validity cannot be established. A conformant implementation
/// shall support explicit fields containing at least eight entries.
/// Contains the following fields:
/// Encapsulates a ciphertext generated with an approved symmetric algorithm
///
/// Note: Critical information fields: If present, this is a critical
/// information field as defined in 5.2.6. An implementation that does not
/// recognize the indicated CHOICE value for this type in an encrypted SPDU
/// shall indicate that the signed SPDU is invalid in the sense of 4.2.2.3.2,
/// that is, it is invalid in the sense that its validity cannot be established.
pub type TestCertificate<'input> = ;
/// The fields in the `ToBeSignedCertificate` structure have the following meaning:
///
/// For both implicit and explicit certificates, when the certificate
/// is hashed to create or recover the public key (in the case of an implicit
/// certificate) or to generate or verify the signature (in the case of an
/// explicit certificate), the hash is Hash (Data input) || Hash (
/// Signer identifier input), where:
/// - Data input is the COER encoding of toBeSigned, canonicalized as described above.
/// - Signer identifier input depends on the verification type,
/// which in turn depends on the choice indicated by issuer. If the choice
/// indicated by issuer is self, the verification type is self-signed and the
/// signer identifier input is the empty string. If the choice indicated by
/// issuer is not self, the verification type is certificate and the signer
/// identifier input is the COER encoding of the canonicalization per 6.4.3 of
/// the certificate indicated by issuer.
///
/// In other words, for implicit certificates, the value H (`CertU`) in SEC 4,
/// section 3, is for purposes of this standard taken to be H [H
/// (canonicalized `ToBeSignedCertificate` from the subordinate certificate) ||
/// H (entirety of issuer Certificate)]. See 5.3.2 for further discussion,
/// including material differences between this standard and SEC 4 regarding
/// how the hash function output is converted from a bit string to an integer.
///
/// Note: Canonicalization: This data structure is subject to canonicalization
/// for the relevant operations specified in 6.1.2. The canonicalization
/// applies to the `PublicEncryptionKey` and to the `VerificationKeyIndicator`.
/// If the `PublicEncryptionKey` contains a `BasePublicEncryptionKey` that is an
/// elliptic curve point (i.e., of type `EccP256CurvePoint` or `EccP384CurvePoint`),
/// then the elliptic curve point is encoded in compressed form, i.e., such
/// that the choice indicated within the Ecc*`CurvePoint` is compressed-y-0 or
/// compressed-y-1.
///
/// Note: Critical information fields:
/// - If present, appPermissions is a critical information field as defined
/// in 5.2.6. If an implementation of verification does not support the number
/// of `PsidSsp` in the appPermissions field of a certificate that signed a
/// signed SPDU, that implementation shall indicate that the signed SPDU is
/// invalid in the sense of 4.2.2.3.2, that is, it is invalid in the sense
/// that its validity cannot be established.. A conformant implementation
/// shall support appPermissions fields containing at least eight entries.
/// It may be the case that an implementation of verification does not support
/// the number of entries in the appPermissions field and the appPermissions
/// field is not relevant to the verification: this will occur, for example,
/// if the certificate in question is a CA certificate and so the
/// certIssuePermissions field is relevant to the verification and the
/// appPermissions field is not. In this case, whether the implementation
/// indicates that the signed SPDU is valid (because it could validate all
/// relevant fields) or invalid (because it could not parse the entire
/// certificate) is implementation-specific.
/// - If present, certIssuePermissions is a critical information field as
/// defined in 5.2.6. If an implementation of verification does not support
/// the number of `PsidGroupPermissions` in the certIssuePermissions field of a
/// CA certificate in the chain of a signed SPDU, the implementation shall
/// indicate that the signed SPDU is invalid in the sense of 4.2.2.3.2, that
/// is, it is invalid in the sense that its validity cannot be established.
/// A conformant implementation shall support certIssuePermissions fields
/// containing at least eight entries.
/// It may be the case that an implementation of verification does not support
/// the number of entries in the certIssuePermissions field and the
/// certIssuePermissions field is not relevant to the verification: this will
/// occur, for example, if the certificate in question is the signing
/// certificate for the SPDU and so the appPermissions field is relevant to
/// the verification and the certIssuePermissions field is not. In this case,
/// whether the implementation indicates that the signed SPDU is valid
/// (because it could validate all relevant fields) or invalid (because it
/// could not parse the entire certificate) is implementation-specific.
/// - If present, certRequestPermissions is a critical information field as
/// defined in 5.2.6. If an implementaiton of verification of a certificate
/// request does not support the number of `PsidGroupPermissions` in
/// certRequestPermissions, the implementation shall indicate that the signed
/// SPDU is invalid in the sense of 4.2.2.3.2, that is, it is invalid in the
/// sense that its validity cannot be established. A conformant implementation
/// shall support certRequestPermissions fields containing at least eight
/// entries.
///
/// It may be the case that an implementation of verification does not support
/// the number of entries in the certRequestPermissions field and the
/// certRequestPermissions field is not relevant to the verification: this will
/// occur, for example, if the certificate in question is the signing
/// certificate for the SPDU and so the appPermissions field is relevant to
/// the verification and the certRequestPermissions field is not. In this
/// case, whether the implementation indicates that the signed SPDU is valid
/// (because it could validate all relevant fields) or invalid (because it
/// could not parse the entire certificate) is implementation-specific.
/// contains the data to be hashed when generating or verifying a signature.
///
/// See 6.3.4 for the specification of the input to the hash.
///
/// Note: Canonicalization: This data structure is subject to canonicalization
/// for the relevant operations specified in 6.1.2. The canonicalization
/// applies to the `SignedDataPayload` if it is of type data, and to the
/// `HeaderInfo`.
/// The contents of this field depend on whether the certificate is an implicit or an explicit certificate
///
/// Note: Critical information fields: If present, this is a critical
/// information field as defined in 5.2.5. An implementation that does not
/// recognize the indicated CHOICE for this type when verifying a signed SPDU
/// shall indicate that the signed SPDU is invalid indicate that the signed
/// SPDU is invalid in the sense of 4.2.2.3.2, that is, it is invalid in the
/// sense that its validity cannot be established.
///
/// Note: Canonicalization: This data structure is subject to canonicalization
/// for the relevant operations specified in 6.1.2. The canonicalization
/// applies to the `PublicVerificationKey` and to the `EccP256CurvePoint`. The
/// `EccP256CurvePoint` is encoded in compressed form, i.e., such that the
/// choice indicated within the `EccP256CurvePoint` is compressed-y-0 or
/// compressed-y-1.
pub const CERT_EXT_ID_OPERATING_ORGANIZATION: ExtId = ExtId;
pub const ETSI_HEADER_INFO_CONTRIBUTOR_ID: HeaderInfoContributorId = HeaderInfoContributorId;
pub const IEEE1609HEADER_INFO_CONTRIBUTOR_ID: HeaderInfoContributorId = HeaderInfoContributorId;
pub const ISO21177EXTENDED_AUTH: PduFunctionalType = PduFunctionalType;
pub const ISO21177SESSION_EXTENSION: PduFunctionalType = PduFunctionalType;
pub const P2PCD8BYTE_LEARNING_REQUEST_ID: Ieee1609HeaderInfoExtensionId = ExtId;
pub const TLS_HANDSHAKE: PduFunctionalType = PduFunctionalType;
/// specifies the bytes of a public encryption key for a particular algorithm
///
/// Supported public key encryption algorithms are defined in 5.3.5.
///
/// Note: Canonicalization: This data structure is subject to canonicalization
/// for the relevant operations specified in 6.1.2 if it appears in a
/// `HeaderInfo` or in a `ToBeSignedCertificate`. See the definitions of `HeaderInfo`
/// and `ToBeSignedCertificate` for a specification of the canonicalization
/// operations.
/// represents a bitmap representation of a SSP
///
/// The mapping of the bits of the bitmap to constraints on the signed SPDU is
/// PSID-specific.
///
/// Note: Consistency with issuing certificate: If a certificate has an
/// appPermissions entry A for which the ssp field is bitmapSsp, A is
/// consistent with the issuing certificate if the certificate contains one
/// of the following:
/// - (OPTION 1) A `SubjectPermissions` field indicating the choice all and no `PsidSspRange` field containing the psid field in A;
/// - (OPTION 2) A `PsidSspRange` P for which the following holds:
/// - The psid field in P is equal to the psid field in A and one of the following is true:
/// - EITHER The sspRange field in P indicates all
/// - OR The sspRange field in P indicates bitmapSspRange and for every bit set to 1 in the sspBitmask in P, the bit in the identical position in the sspValue in A is set equal to the bit in that position in the sspValue in P.
///
/// Note: A `BitmapSsp` B is consistent with a `BitmapSspRange` R if for every
/// bit set to 1 in the sspBitmask in R, the bit in the identical position in
/// B is set equal to the bit in that position in the sspValue in R. For each
/// bit set to 0 in the sspBitmask in R, the corresponding bit in the
/// identical position in B may be freely set to 0 or 1, i.e., if a bit is
/// set to 0 in the sspBitmask in R, the value of corresponding bit in the
/// identical position in B has no bearing on whether B and R are consistent.
)] pub &'input );
/// represents a bitmap representation of a SSP
///
/// The sspValue indicates permissions. The sspBitmask contains an octet string
/// used to permit or constrain sspValue fields in issued certificates. The
/// sspValue and sspBitmask fields shall be of the same length.
///
/// Note: Consistency with issuing certificate: If a certificate has an
/// `PsidSspRange` value P for which the sspRange field is bitmapSspRange,
/// P is consistent with the issuing certificate if the issuing certificate
/// contains one of the following:
/// - (OPTION 1) A `SubjectPermissions` field indicating the choice all and no `PsidSspRange` field containing the psid field in P;
/// - (OPTION 2) A `PsidSspRange` R for which the following holds:
/// - The psid field in R is equal to the psid field in P and one of the following is true:
/// - EITHER The sspRange field in R indicates all
/// - OR The sspRange field in R indicates bitmapSspRange and for every bit set to 1 in the sspBitmask in R:
/// - The bit in the identical position in the sspBitmask in P is set equal to 1, AND
/// - The bit in the identical position in the sspValue in P is set equal to the bit in that position in the sspValue in R.
///
/// Reference ETSI TS 103 097 for more information on bitmask SSPs.
/// specifies a circle
///
/// Specifies a circle with its center at center, its
/// radius given in meters, and located tangential to the reference ellipsoid.
/// The indicated region is all the points on the surface of the reference
/// ellipsoid whose distance to the center point over the reference ellipsoid
/// is less than or equal to the radius. A point which contains an elevation
/// component is considered to be within the circular region if its horizontal
/// projection onto the reference ellipsoid lies within the region.
/// List of countries and regions
///
/// A conformant implementation that supports `CountryAndRegions` shall
/// support a regions field containing at least eight entries.
///
/// A conformant implementation that implements this type shall recognize
/// (in the sense of "be able to determine whether a two dimensional location
/// lies inside or outside the borders identified by") at least one value of
/// `UnCountryId` and at least one value for a region within the country
/// indicated by that recognized `UnCountryId` value. In this version of this
/// standard, the only means to satisfy this is for a conformant
/// implementation to recognize the value of `UnCountryId` indicating USA and
/// at least one of the FIPS state codes for US states. The Protocol
/// Implementation Conformance Statement (PICS) provided in Annex A allows
/// an implementation to state which `UnCountryId` values it recognizes and
/// which region values are recognized within that country.
///
/// If a verifying implementation is required to check that an relevant
/// geographic information in a signed SPDU is consistent with a certificate
/// containing one or more instances of this type, then the SDS is permitted
/// to indicate that the signed SPDU is valid even if some values of country
/// or within regions are unrecognized in the sense defined above, so long
/// as the recognized instances of this type completely contain the relevant
/// geographic information. Informally, if the recognized values in the
/// certificate allow the SDS to determine that the SPDU is valid, then it
/// can make that determination even if there are also unrecognized values
/// in the certificate. This field is therefore not a "critical information
/// field" as defined in 5.2.6, because unrecognized values are permitted so
/// long as the validity of the SPDU can be established with the recognized
/// values. However, as discussed in 5.2.6, the presence of an unrecognized
/// value in a certificate can make it impossible to determine whether the
/// certificate is valid and so whether the SPDU is valid.
/// List of countries and sub-regions
///
/// A conformant implementation that supports `CountryAndSubregions`
/// shall support a regionAndSubregions field containing at least eight
/// entries.
///
/// A conformant implementation that implements this type shall recognize
/// (in the sense of be able to determine whether a two dimensional location
/// lies inside or outside the borders identified by) at least one value of
/// country and at least one value for a region within the country indicated
/// by that recognized country value. In this version of this standard, the
/// only means to satisfy this is for a conformant implementation to recognize
/// the value of `UnCountryId` indicating USA and at least one of the FIPS state
/// codes for US states. The Protocol Implementation Conformance Statement
/// (PICS) provided in Annex A allows an implementation to state which
/// `UnCountryId` values it recognizes and which region values are recognized
/// within that country.
///
/// If a verifying implementation is required to check that an relevant
/// geographic information in a signed SPDU is consistent with a certificate
/// containing one or more instances of this type, then the SDS is permitted
/// to indicate that the signed SPDU is valid even if some values of country
/// or within regionAndSubregions are unrecognized in the sense defined above,
/// so long as the recognized instances of this type completely contain the
/// relevant geographic information. Informally, if the recognized values in
/// the certificate allow the SDS to determine that the SPDU is valid, then
/// it can make that determination even if there are also unrecognized values
/// in the certificate. This field is therefore not a "critical information
/// field" as defined in 5.2.6, because unrecognized values are permitted so
/// long as the validity of the SPDU can be established with the recognized
/// values. However, as discussed in 5.2.6, the presence of an unrecognized
/// value in a certificate can make it impossible to determine whether the
/// only for backwards compatibility
pub type CountryOnly = UnCountryId;
/// This integer identifies a series of CRLs issued under the authority of a particular CRACA
pub type CrlSeries = Uint16;
/// represents the duration of validity of a certificate
///
/// The Uint16 value is the duration, given in the units denoted
/// by the indicated choice. A year is considered to be 31556952 seconds,
/// which is the average number of seconds in a year.
///
/// Note: Years can be mapped more closely to wall-clock days using the hours
/// choice for up to 7 years and the sixtyHours choice for up to 448 years.
/// Inner type
/// specifies a point on an elliptic curve in Weierstrass form defined over a 256-bit prime number
///
/// The curves supported in this standard are NIST p256 as defined in FIPS 186-4, Brainpool p256r1 as
/// defined in RFC 5639, and the SM2 curve as defined in GB/T 32918.5-2017.
/// The fields in this structure are OCTET STRINGS produced with the elliptic
/// curve point encoding and decoding methods defined in subclause 5.5.6 of
/// IEEE Std 1363-2000. The x-coordinate is encoded as an unsigned integer of
/// length 32 octets in network byte order for all values of the CHOICE; the
/// encoding of the y-coordinate y depends on whether the point is x-only,
/// compressed, or uncompressed. If the point is x-only, y is omitted. If the
/// point is compressed, the value of type depends on the least significant
/// bit of y: if the least significant bit of y is 0, type takes the value
/// compressed-y-0, and if the least significant bit of y is 1, type takes the
/// value compressed-y-1. If the point is uncompressed, y is encoded explicitly
/// as an unsigned integer of length 32 octets in network byte order.
///
/// Note: Canonicalization: This data structure is subject to canonicalization
/// for the relevant operations specified in 6.1.2 if it appears in a
/// `HeaderInfo` or in a `ToBeSignedCertificate`. See the definitions of `HeaderInfo`
/// and `ToBeSignedCertificate` for a specification of the canonicalization
/// operations.
/// Inner type
/// specifies a point on an elliptic curve in Weierstrass form defined over a 384-bit prime number
///
/// The only supported
/// such curve in this standard is Brainpool p384r1 as defined in RFC 5639.
/// The fields in this structure are octet strings produced with the elliptic
/// curve point encoding and decoding methods defined in subclause 5.5.6 of
/// IEEE Std 1363-2000. The x-coordinate is encoded as an unsigned integer of
/// length 48 octets in network byte order for all values of the CHOICE; the
/// encoding of the y-coordinate y depends on whether the point is x-only,
/// compressed, or uncompressed. If the point is x-only, y is omitted. If the
/// point is compressed, the value of type depends on the least significant
/// bit of y: if the least significant bit of y is 0, type takes the value
/// compressed-y-0, and if the least significant bit of y is 1, type takes the
/// value compressed-y-1. If the point is uncompressed, y is encoded
/// explicitly as an unsigned integer of length 48 octets in network byte order.
///
/// Note: Canonicalization: This data structure is subject to canonicalization
/// for the relevant operations specified in 6.1.2 if it appears in a
/// `HeaderInfo` or in a `ToBeSignedCertificate`. See the definitions of `HeaderInfo`
/// and `ToBeSignedCertificate` for a specification of the canonicalization
/// operations.
/// represents an ECDSA signature
///
/// The signature is generated as specified in 5.3.1.
/// If the signature process followed the specification of FIPS 186-4
/// and output the integer r, r is represented as an `EccP256CurvePoint`
/// indicating the selection x-only.
///
/// If the signature process followed the specification of SEC 1 and
/// output the elliptic curve point R to allow for fast verification, R is
/// represented as an `EccP256CurvePoint` indicating the choice compressed-y-0,
/// compressed-y-1, or uncompressed at the sender's discretion.
///
/// Note: Canonicalization: This data structure is subject to canonicalization
/// for the relevant operations specified in 6.1.2. When this data structure
/// is canonicalized, the `EccP256CurvePoint` in rSig is represented in the
/// form x-only.
///
/// Note: When the signature is of form x-only, the x-value in rSig is
/// an integer mod n, the order of the group; when the signature is of form
/// compressed-y-\*, the x-value in rSig is an integer mod p, the underlying
/// prime defining the finite field. In principle this means that to convert a
/// signature from form compressed-y-\* to form x-only, the converter checks
/// the x-value to see if it lies between n and p and reduces it mod n if so.
/// In practice this check is unnecessary: Haase's Theorem states that
/// difference between n and p is always less than 2*square-root(p), and so the
/// chance that an integer lies between n and p, for a 256-bit curve, is
/// bounded above by approximately square-root(p)/p or 2^(-128). For the
/// 256-bit curves in this standard, the exact values of n and p in hexadecimal
/// are:
/// - NISTp256:
/// - p = FFFFFFFF00000001000000000000000000000000FFFFFFFFFFFFFFFFFFFFFFFF
/// - n = FFFFFFFF00000000FFFFFFFFFFFFFFFFBCE6FAADA7179E84F3B9CAC2FC632551
/// - Brainpoolp256:
/// - p = A9FB57DBA1EEA9BC3E660A909D838D726E3BF623D52620282013481D1F6E5377
/// - n = A9FB57DBA1EEA9BC3E660A909D838D718C397AA3B561A6F7901E0E82974856A7
/// represents an ECDSA signature
///
/// The signature is generated as specified in 5.3.1.
/// If the signature process followed the specification of FIPS 186-4
/// and output the integer r, r is represented as an `EccP384CurvePoint`
/// indicating the selection x-only.
///
/// If the signature process followed the specification of SEC 1 and
/// output the elliptic curve point R to allow for fast verification, R is
/// represented as an `EccP384CurvePoint` indicating the choice compressed-y-0,
/// compressed-y-1, or uncompressed at the sender's discretion.
///
/// Note: Canonicalization: This data structure is subject to canonicalization
/// for the relevant operations specified in 6.1.2. When this data structure
/// is canonicalized, the `EccP384CurvePoint` in rSig is represented in the
/// form x-only.
///
/// Note: When the signature is of form x-only, the x-value in rSig is
/// an integer mod n, the order of the group; when the signature is of form
/// compressed-y-\*, the x-value in rSig is an integer mod p, the underlying
/// prime defining the finite field. In principle this means that to convert a
/// signature from form compressed-y-* to form x-only, the converter checks the
/// x-value to see if it lies between n and p and reduces it mod n if so. In
/// practice this check is unnecessary: Haase's Theorem states that difference
/// between n and p is always less than 2*square-root(p), and so the chance
/// that an integer lies between n and p, for a 384-bit curve, is bounded
/// above by approximately square-root(p)/p or 2^(-192). For the 384-bit curve
/// in this standard, the exact values of n and p in hexadecimal are:
/// - p = 8CB91E82A3386D280F5D6F7E50E641DF152F7109ED5456B412B1DA197FB71123ACD3A729901D1A71874700133107EC53
/// - n = 8CB91E82A3386D280F5D6F7E50E641DF152F7109ED5456B31F166E6CAC0425A7CF3AB6AF6B7FC3103B883202E9046565
/// Transfers a 16-byte symmetric key encrypted using SM2 encryption as specified in 5.3.3
///
/// The symmetric key is
/// input to the key encryption process with no headers, encapsulation, or
/// length indication. Encryption and decryption are carried out as specified
/// in 5.3.5.2.
/// Transfers a 16-byte symmetric key encrypted using ECIES as specified in IEEE Std 1363a-2004
///
/// The symmetric key is input to the key encryption process with no headers, encapsulation,
/// or length indication. Encryption and decryption are carried out as
/// specified in 5.3.5.1.
/// represents a elliptic curve signature
///
/// Represents a elliptic curve signature where the component r is constrained to be an integer.
/// This structure supports SM2 signatures as specified in 5.3.1.3.
/// contains an estimate of the geodetic altitude above or below the WGS84 ellipsoid
///
/// The 16-bit value is interpreted as an
/// integer number of decimeters representing the height above a minimum
/// height of -409.5 m, with the maximum height being 6143.9 m.
pub type Elevation = Uint16;
/// contains an encryption key, which may be a public or a symmetric key
///
/// Note: Canonicalization: This data structure is subject to canonicalization
/// for the relevant operations specified in 6.1.2 if it appears in a
/// `HeaderInfo` or in a `ToBeSignedCertificate`. The canonicalization applies to
/// the `PublicEncryptionKey`. See the definitions of `HeaderInfo` and
/// `ToBeSignedCertificate` for a specification of the canonicalization
/// operations.
/// used as an identifier for instances of `ExtContent` within an EXT-TYPE
;
/// Parameterized type representing a (id, content) pair
///
/// Represents a (id, content) pair drawn from
/// the set `ExtensionTypes`, which is constrained to contain objects defined by
/// the class EXT-TYPE.
//**************************************************************************
// Location Structures
//**************************************************************************
/// represents a geographic region of a specified form
///
/// A certificate is not valid if any part of the region indicated in its
/// scope field lies outside the region indicated in the scope of its issuer.
///
/// Note: Critical information fields:
/// - If present, this is a critical information field as defined in 5.2.6.
///
/// An implementation that does not recognize the indicated CHOICE when
/// verifying a signed SPDU shall indicate that the signed SPDU is invalid in
/// the sense of 4.2.2.3.2, that is, it is invalid in the sense that its
/// validity cannot be established.
/// - If selected, rectangularRegion is a critical information field as
/// defined in 5.2.6. An implementation that does not support the number of
/// `RectangularRegion` in rectangularRegions when verifying a signed SPDU shall
/// indicate that the signed SPDU is invalid in the sense of 4.2.2.3.2, that
/// is, it is invalid in the sense that its validity cannot be established.
/// A conformant implementation shall support rectangularRegions fields
/// containing at least eight entries.
/// - If selected, identifiedRegion is a critical information field as
/// defined in 5.2.6. An implementation that does not support the number of
/// `IdentifiedRegion` in identifiedRegion shall reject the signed SPDU as
/// invalid in the sense of 4.2.2.3.2, that is, it is invalid in the sense
/// that its validity cannot be established. A conformant implementation shall
/// support identifiedRegion fields containing at least eight entries.
/// This is the group linkage value
///
/// See 5.1.3 and 7.3 for details of
/// use.
/// identifies a hash algorithm
///
/// The value sha256, indicates SHA-256. The value sha384 indicates SHA-384. The
/// value sm3 indicates SM3. See 5.3.3 for more details.
///
/// Note: Critical information fields: This is a critical information field as
/// defined in 5.2.6. An implementation that does not recognize the enumerated
/// value of this type in a signed SPDU when verifying a signed SPDU shall
/// indicate that the signed SPDU is invalid in the sense of 4.2.2.3.2, that
/// is, it is invalid in the sense that its validity cannot be established.
/// contains the truncated hash of another data structure
///
/// The `HashedId10` for a given data structure is calculated by calculating the
/// hash of the encoded data structure and taking the low-order ten bytes of
/// the hash output. The low-order ten bytes are the last ten bytes of the
/// hash when represented in network byte order. If the data structure
/// is subject to canonicalization it is canonicalized before hashing. See
/// Example below.
///
/// The hash algorithm to be used to calculate a `HashedId10` within a
/// structure depends on the context. In this standard, for each structure
/// that includes a `HashedId10` field, the corresponding text indicates how the
/// hash algorithm is determined. See also the discussion in 5.3.9.
/// Example: Consider the SHA-256 hash of the empty string:
/// SHA-256("") = e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
///
/// The `HashedId10` derived from this hash corresponds to the following:
/// `HashedId10` = 934ca495991b7852b855.
)] pub &'input );
/// contains the truncated hash of another data structure
///
/// The `HashedId3` for a given data structure is calculated by calculating the
/// hash of the encoded data structure and taking the low-order three bytes of
/// the hash output. The low-order three bytes are the last three bytes of the
/// 32-byte hash when represented in network byte order. If the data structure
/// is subject to canonicalization it is canonicalized before hashing. See
/// Example below.
///
/// The hash algorithm to be used to calculate a `HashedId3` within a
/// structure depends on the context. In this standard, for each structure
/// that includes a `HashedId3` field, the corresponding text indicates how the
/// hash algorithm is determined. See also the discussion in 5.3.9.
///
/// Example: Consider the SHA-256 hash of the empty string:
/// SHA-256("") = e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
/// The `HashedId3` derived from this hash corresponds to the following:
/// `HashedId3` = 52b855.
)] pub &'input );
/// Truncated hash of another data structure
///
/// The `HashedId32` for a given data structure is calculated by
/// calculating the hash of the encoded data structure and taking the
/// low-order 32 bytes of the hash output. The low-order 32 bytes are the last
/// 32 bytes of the hash when represented in network byte order. If the data
/// structure is subject to canonicalization it is canonicalized before
/// hashing. See Example below.
/// The hash algorithm to be used to calculate a `HashedId32` within a
/// structure depends on the context. In this standard, for each structure
/// that includes a `HashedId32` field, the corresponding text indicates how the
/// hash algorithm is determined. See also the discussion in 5.3.9.
///
/// Example: Consider the SHA-256 hash of the empty string:
/// SHA-256("") = e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
///
/// The `HashedId32` derived from this hash corresponds to the following:
/// `HashedId32` = e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.
)] pub &'input );
/// Truncated hash of another data structure
///
/// The `HashedId48` for a given data structure is calculated by
/// calculating the hash of the encoded data structure and taking the
/// low-order 48 bytes of the hash output. The low-order 48 bytes are the last
/// 48 bytes of the hash when represented in network byte order. If the data
/// structure is subject to canonicalization it is canonicalized before
/// hashing. See Example below.
///
/// The hash algorithm to be used to calculate a `HashedId48` within a
/// structure depends on the context. In this standard, for each structure
/// that includes a `HashedId48` field, the corresponding text indicates how the
/// hash algorithm is determined. See also the discussion in 5.3.9.
///
/// Example: Consider the SHA-384 hash of the empty string:
/// SHA-384("") = 38b060a751ac96384cd9327eb1b1e36a21fdb71114be07434c0cc7bf63f6 e1da274edebfe76f65fbd51ad2f14898b95b
/// The `HashedId48` derived from this hash corresponds to the following:
/// `HashedId48` = 38b060a751ac96384cd9327eb1b1e36a21fdb71114be07434c0cc7bf63f6e
/// 1da274edebfe76f65fbd51ad2f14898b95b.
)] pub &'input );
/// contains the truncated hash of another data structure
///
/// The `HashedId8` for a given data structure is calculated by calculating the
/// hash of the encoded data structure and taking the low-order eight bytes of
/// the hash output. The low-order eight bytes are the last eight bytes of the
/// hash when represented in network byte order. If the data structure
/// is subject to canonicalization it is canonicalized before hashing. See
/// Example below.
///
/// The hash algorithm to be used to calculate a `HashedId8` within a
/// structure depends on the context. In this standard, for each structure
/// that includes a `HashedId8` field, the corresponding text indicates how the
/// hash algorithm is determined. See also the discussion in 5.3.9.
///
/// Example: Consider the SHA-256 hash of the empty string:
/// SHA-256("") = e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
/// The `HashedId8` derived from this hash corresponds to the following:
/// `HashedId8` = a495991b7852b855.
)] pub &'input );
/// UTF-8 string as defined in IETF RFC 3629
///
/// The contents are determined by policy.
;
//**************************************************************************
// Pseudonym Linkage
//**************************************************************************
/// This atomic type is used in the definition of other data structures
pub type IValue = Uint16;
/// indicates the region of validity of a certificate using region identifiers
///
/// A conformant implementation that supports this type shall support at least
/// one of the possible CHOICE values. The Protocol Implementation Conformance
/// Statement (PICS) provided in Annex A allows an implementation to state
/// which `CountryOnly` values it recognizes.
/// The known latitudes are from -900,000,000 to +900,000,000 in 0.1 microdegree intervals
;
/// The known longitudes are from -1,799,999,999 to +1,800,000,000 in 0.1 microdegree intervals
;
/// contains a LA Identifier for use in the algorithms specified in 5.1.3.4
)] pub &'input );
/// Estimate of the latitude with precision 1/10th microdegree
///
/// This type contains an INTEGER encoding an estimate of the latitude
/// with precision 1/10th microdegree relative to the World Geodetic System
/// (WGS)-84 datum as defined in NIMA Technical Report TR8350.2.
/// The integer in the latitude field is no more than 900 000 000 and no less
/// than ?900 000 000, except that the value 900 000 001 is used to indicate
/// the latitude was not available to the sender.
pub type Latitude = NinetyDegreeInt;
/// contains a linkage seed value for use in the algorithms specified in 5.1.3.4
)] pub &'input );
/// This is the individual linkage value
///
/// See 5.1.3 and 7.3 for details of use.
)] pub &'input );
/// Estimate of the longitude with precision 1/10th microdegree
///
/// This type contains an INTEGER encoding an estimate of the longitude
/// with precision 1/10th microdegree relative to the World Geodetic System
/// (WGS)-84 datum as defined in NIMA Technical Report TR8350.2.
/// The integer in the longitude field is no more than 1 800 000 000 and no
/// less than ?1 799 999 999, except that the value 1 800 000 001 is used to
/// indicate that the longitude was not available to the sender.
pub type Longitude = OneEightyDegreeInt;
/// See [`Latitude`]
///
/// The integer in the latitude field is no more than 900,000,000 and
/// no less than -900,000,000, except that the value 900,000,001 is used to
/// indicate the latitude was not available to the sender.
;
/// See [`Longitude`]
///
/// The integer in the longitude field is no more than 1,800,000,000
/// and no less than -1,799,999,999, except that the value 1,800,000,001 is
/// used to indicate that the longitude was not available to the sender.
;
//**************************************************************************
// OCTET STRING Types
//**************************************************************************
/// synonym for ASN.1 OCTET STRING, and is used in the definition of other data structures
)] pub &'input );
/// defines a region using a series of distinct geographic points, defined on the surface of the reference ellipsoid
///
/// The region is specified by connecting the points in the order they appear,
/// with each pair of points connected by the geodesic on the reference
/// ellipsoid. The polygon is completed by connecting the final point to the
/// first point. The allowed region is the interior of the polygon and its
/// boundary.
///
/// A point which contains an elevation component is considered to be
/// within the polygonal region if its horizontal projection onto the
/// reference ellipsoid lies within the region.
/// A valid `PolygonalRegion` contains at least three points. In a valid
/// `PolygonalRegion`, the implied lines that make up the sides of the polygon
/// do not intersect.
///
/// Note: This type does not support enclaves / exclaves. This might be
/// addressed in a future version of this standard.
///
/// Note: Critical information fields: If present, this is a critical
/// information field as defined in 5.2.6. An implementation that does not
/// support the number of `TwoDLocation` in the `PolygonalRegion` when verifying a
/// signed SPDU shall indicate that the signed SPDU is invalid. A compliant
/// implementation shall support `PolygonalRegions` containing at least eight
/// `TwoDLocation` entries.
;
/// represents the PSID defined in IEEE Std 1609.12
;
//**************************************************************************
// PSID / ITS-AID
//**************************************************************************
/// permissions that the certificate holder has
///
/// This structure represents the permissions that the certificate
/// holder has with respect to activities for a single application area,
/// identified by a Psid.
///
/// Note: The determination as to whether the activities are consistent with
/// the permissions indicated by the PSID and `ServiceSpecificPermissions` is
/// made by the SDEE and not by the SDS; the SDS provides the PSID and SSP
/// information to the SDEE to enable the SDEE to make that determination.
/// See 5.2.4.3.3 for more information.
///
/// Note: The SDEE specification is expected to specify what application
/// activities are permitted by particular `ServiceSpecificPermissions` values.
/// The SDEE specification is also expected EITHER to specify application
/// activities that are permitted if the `ServiceSpecificPermissions` is
/// omitted, OR to state that the `ServiceSpecificPermissions` need to always be
/// present.
///
/// Note: Consistency with signed SPDU: As noted in 5.1.1,
/// consistency between the SSP and the signed SPDU is defined by rules
/// specific to the given PSID and is out of scope for this standard.
///
/// Note: Consistency with issuing certificate: If a certificate has an
/// appPermissions entry A for which the ssp field is omitted, A is consistent
/// with the issuing certificate if the issuing certificate contains a
/// `PsidSspRange` P for which the following holds:
/// - The psid field in P is equal to the psid field in A and one of the following is true:
/// - The sspRange field in P indicates all.
/// - The sspRange field in P indicates opaque and one of the entries in opaque is an OCTET STRING of length 0.
///
/// For consistency rules for other forms of the ssp field, see the following subclauses.
/// certificate issuing or requesting permissions of the certificate holder
///
/// This structure represents the certificate issuing or requesting
/// permissions of the certificate holder with respect to one particular set
/// of application permissions.
/// public encryption key and the associated symmetric algorithm
///
/// This structure specifies a public encryption key and the associated
/// symmetric algorithm which is used for bulk data encryption when encrypting
/// for that public key.
///
/// Note: Canonicalization: This data structure is subject to canonicalization
/// for the relevant operations specified in 6.1.2 if it appears in a
/// `HeaderInfo` or in a `ToBeSignedCertificate`. The canonicalization applies to
/// the `BasePublicEncryptionKey`. See the definitions of `HeaderInfo` and
/// `ToBeSignedCertificate` for a specification of the canonicalization
/// operations.
/// represents a public key and states with what algorithm the public key is to be used
///
/// Cryptographic mechanisms are defined in 5.3.
/// An `EccP256CurvePoint` or `EccP384CurvePoint` within a `PublicVerificationKey`
/// structure is invalid if it indicates the choice x-only.
///
/// Note: Critical information fields: If present, this is a critical
/// information field as defined in 5.2.6. An implementation that does not
/// recognize the indicated CHOICE when verifying a signed SPDU shall indicate
/// that the signed SPDU is invalid indicate that the signed SPDU is invalid
/// in the sense of 4.2.2.3.2, that is, it is invalid in the sense that its
/// validity cannot be established.
///
/// Note: Canonicalization: This data structure is subject to canonicalization
/// for the relevant operations specified in 6.1.2. The canonicalization
/// applies to the `EccP256CurvePoint` and the `Ecc384CurvePoint`. Both forms of
/// point are encoded in compressed form, i.e., such that the choice indicated
/// within the Ecc*`CurvePoint` is compressed-y-0 or compressed-y-1.
/// Specifies a rectangle on the surface of the WGS84 ellipsoid
///
/// Specifies a rectangle on the surface of the WGS84 ellipsoid where the
/// sides are given by lines of constant latitude or longitude.
///
/// A point which contains an elevation component is considered to be within the rectangular region
/// if its horizontal projection onto the reference ellipsoid lies within the region.
///
/// A `RectangularRegion` is invalid if the northWest value is south of the southEast value, or if the
/// latitude values in the two points are equal, or if the longitude values in the two points are
/// equal; otherwise it is valid. A certificate that contains an invalid `RectangularRegion` is invalid.
/// Region and sub-regions
///
/// The meanings of the fields in this structure are to be interpreted
/// in the context of a country within which the region is located, referred
/// to as the "enclosing country". If this structure is used in a
/// `CountryAndSubregions` structure, the enclosing country is the one indicated
/// by the country field in the `CountryAndSubregions` structure. If other uses
/// are defined for this structure in future, it is expected that that
/// definition will include a specification of how the enclosing country can
/// be determined.
///
/// If the enclosing country is the United States of America:
/// - The region field identifies the state or statistically equivalent
/// entity using the integer version of the 2010 FIPS codes as provided by the
/// U.S. Census Bureau (see normative references in Clause 0).
/// - The values in the subregions field identify the county or county
/// equivalent entity using the integer version of the 2010 FIPS codes as
/// provided by the U.S. Census Bureau.
///
/// If the enclosing country is a different country from the USA, the meaning
/// of regionAndSubregions is not defined in this version of this standard.
/// A conformant implementation that implements this type shall recognize (in
/// the sense of "be able to determine whether a two-dimensional location lies
/// inside or outside the borders identified by"), for at least one enclosing
/// country, at least one value for a region within that country and at least
/// one subregion for the indicated region. In this version of this standard,
/// the only means to satisfy this is for a conformant implementation to
/// recognize, for the USA, at least one of the FIPS state codes for US
/// states, and at least one of the county codes in at least one of the
/// recognized states. The Protocol Implementation Conformance Statement
/// (PICS) provided in Annex A allows an implementation to state which
/// `UnCountryId` values it recognizes and which region values are recognized
/// within that country.
///
/// If a verifying implementation is required to check that an relevant
/// geographic information in a signed SPDU is consistent with a certificate
/// containing one or more instances of this type, then the SDS is permitted
/// to indicate that the signed SPDU is valid even if some values within
/// subregions are unrecognized in the sense defined above, so long as the
/// recognized instances of this type completely contain the relevant
/// geographic information. Informally, if the recognized values in the
/// certificate allow the SDS to determine that the SPDU is valid, then it
/// can make that determination even if there are also unrecognized values
/// in the certificate. This field is therefore not not a "critical
/// information field" as defined in 5.2.6, because unrecognized values are
/// permitted so long as the validity of the SPDU can be established with the
/// recognized values. However, as discussed in 5.2.6, the presence of an
/// unrecognized value in a certificate can make it impossible to determine
/// whether the certificate is valid and so whether the SPDU is valid.
/// used for clarity of definitions
)] pub ,
);
/// used for clarity of definitions
;
/// used for clarity of definitions
)] pub ,
);
/// used for clarity of definitions
)] pub ,
);
/// used for clarity of definitions
;
/// used for clarity of definitions
)] pub ,
);
/// used for clarity of definitions
)] pub ,
);
/// used for clarity of definitions
;
/// used for clarity of definitions
;
/// used for clarity of definitions
;
/// used for clarity of definitions
;
/// SSPs for a given entry in a `PsidSsp`
///
/// This structure represents the Service Specific Permissions (SSP)
/// relevant to a given entry in a `PsidSsp`. The meaning of the SSP is specific
/// to the associated Psid. SSPs may be PSID-specific octet strings or
/// bitmap-based. See Annex C for further discussion of how application
/// specifiers may choose which SSP form to use.
///
/// Note: Consistency with issuing certificate: If a certificate has an
/// appPermissions entry A for which the ssp field is opaque, A is consistent
/// with the issuing certificate if the issuing certificate contains one of
/// the following:
/// - (OPTION 1) A `SubjectPermissions` field indicating the choice all and no `PsidSspRange` field containing the psid field in A;
/// - (OPTION 2) A `PsidSspRange` P for which the following holds:
/// - The psid field in P is equal to the psid field in A and one of the following is true:
/// - The sspRange field in P indicates all.
/// - The sspRange field in P indicates opaque and one of the entries in the opaque field in P is an OCTET STRING identical to the opaque field in A.
///
/// For consistency rules for other types of `ServiceSpecificPermissions`, see the following subclauses.
//**************************************************************************
// Crypto Structures
//**************************************************************************
/// represents a signature for a supported public key algorithm
///
/// It may be contained within `SignedData` or Certificate.
///
/// Note: Critical information fields: If present, this is a critical
/// information field as defined in 5.2.5. An implementation that does not
/// recognize the indicated CHOICE for this type when verifying a signed SPDU
/// shall indicate that the signed SPDU is invalid in the sense of 4.2.2.3.2,
/// that is, it is invalid in the sense that its validity cannot be
/// established.
///
/// Note: Canonicalization: This data structure is subject to canonicalization
/// for the relevant operations specified in 6.1.2. The canonicalization
/// applies to instances of this data structure of form `EcdsaP256Signature`
/// and `EcdsaP384Signature`.
/// identifies the SSPs associated with a PSID for which the holder may issue or request certificates
///
/// Note: Consistency with issuing certificate: If a certificate has a
/// `PsidSspRange` A for which the ssp field is opaque, A is consistent with
/// the issuing certificate if the issuing certificate contains one of the
/// following:
/// - (OPTION 1) A `SubjectPermissions` field indicating the choice all and no `PsidSspRange` field containing the psid field in A;
/// - (OPTION 2) A `PsidSspRange` P for which the following holds:
/// - The psid field in P is equal to the psid field in A and one of the following is true:
/// - The sspRange field in P indicates all.
/// - The sspRange field in P indicates opaque, and the sspRange field in
/// A indicates opaque, and every OCTET STRING within the opaque in A is a
/// duplicate of an OCTET STRING within the opaque in P.
///
/// If a certificate has a `PsidSspRange` A for which the ssp field is all,
/// A is consistent with the issuing certificate if the issuing certificate
/// contains a `PsidSspRange` P for which the following holds:
/// - (OPTION 1) A `SubjectPermissions` field indicating the choice all and no `PsidSspRange` field containing the psid field in A;
/// - (OPTION 2) A `PsidSspRange` P for which the psid field in P is equal to the psid field in A and the sspRange field in P indicates all.
///
/// For consistency rules for other types of `SspRange`, see the following subclauses.
///
/// Note: The choice "all" may also be indicated by omitting the
/// `SspRange` in the enclosing `PsidSspRange` structure. Omitting the `SspRange` is
/// preferred to explicitly indicating "all".
//**************************************************************************
// Certificate Components
//**************************************************************************
/// certificate holder's assurance level
///
/// This field contains the certificate holder's assurance level, which
/// indicates the security of both the platform and storage of secret keys as
/// well as the confidence in this assessment.
///
/// This field is encoded as defined in Table 1, where "A" denotes bit
/// fields specifying an assurance level, "R" reserved bit fields, and "C" bit
/// fields specifying the confidence.
///
/// Table 1: Bitwise encoding of subject assurance
/// | Bit number | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
/// | -------------- | --- | --- | --- | --- | --- | --- | --- | --- |
/// | Interpretation | A | A | A | R | R | R | C | C |
///
/// In Table 1, bit number 0 denotes the least significant bit. Bit 7
/// to bit 5 denote the device's assurance levels, bit 4 to bit 2 are reserved
/// for future use, and bit 1 and bit 0 denote the confidence.
///
/// The specification of these assurance levels as well as the
/// encoding of the confidence levels is outside the scope of the present
/// standard. It can be assumed that a higher assurance value indicates that
/// the holder is more trusted than the holder of a certificate with lower
/// assurance value and the same confidence value.
///
/// Note: This field was originally specified in ETSI TS 103 097 and
/// future uses of this field are anticipated to be consistent with future
/// versions of that standard.
)] pub &'input );
/// This enumerated value indicates supported symmetric algorithms
///
/// The algorithm identifier identifies both the algorithm itself and a specific
/// mode of operation. The symmetric algorithms supported in this version of
/// this standard are AES-128 and SM4. The only mode of operation supported is
/// Counter Mode Encryption With Cipher Block Chaining Message Authentication
/// Code (CCM). Full details are given in 5.3.8.
/// provides the key bytes for use with an identified symmetric algorithm
///
/// The supported symmetric algorithms are AES-128 and SM4 in CCM mode as
/// specified in 5.3.8.
/// contains an estimate of 3D location
///
/// The details of the structure are given in the definitions of the individual
/// fields below.
///
/// Note: The units used in this data structure are consistent with the
/// location data structures used in SAE J2735 \[B26\], though the encoding is
/// incompatible.
//**************************************************************************
// Time Structures
//**************************************************************************
/// The number of (TAI) seconds since 00:00:00 UTC, 1 January, 2004
pub type Time32 = Uint32;
/// Estimate of the number of (TAI) microseconds since 00:00:00 UTC, 1 January, 2004
pub type Time64 = Uint64;
/// is used to define validity regions for use in certificates
///
/// The latitude and longitude fields contain the latitude and
/// longitude as defined above.
///
/// Note: This data structure is consistent with the location encoding
/// used in SAE J2735, except that values 900 000 001 for latitude (used to
/// indicate that the latitude was not available) and 1 800 000 001 for
/// longitude (used to indicate that the longitude was not available) are not
/// valid.
/// This atomic type is used in the definition of other data structures
///
/// It is for non-negative integers up to 65,535, i.e., (hex)ff ff.
;
//**************************************************************************
// Integer Types
//**************************************************************************
/// This atomic type is used in the definition of other data structures
///
/// It is for non-negative integers up to 7, i.e., (hex)07.
;
/// This atomic type is used in the definition of other data structures
///
/// It is for non-negative integers up to 4,294,967,295, i.e.,
/// (hex)ff ff ff ff.
;
/// This atomic type is used in the definition of other data structures
///
/// It is for non-negative integers up to 18,446,744,073,709,551,615, i.e.,
/// (hex)ff ff ff ff ff ff ff ff.
;
/// This atomic type is used in the definition of other data structures
///
/// It is for non-negative integers up to 255, i.e., (hex)ff.
;
/// A UN country ID
///
/// This type contains the integer representation of the country or
/// area identifier as defined by the United Nations Statistics Division in
/// October 2013 (see normative references in Clause 0).
///
/// A conformant implementation that implements `IdentifiedRegion` shall
/// recognize (in the sense of be able to determine whether a two dimensional
/// location lies inside or outside the borders identified by) at least one
/// value of `UnCountryId`. The Protocol Implementation Conformance Statement
/// (PICS) provided in Annex A allows an implementation to state which
/// `UnCountryId` values it recognizes.
///
/// Since 2013 and before the publication of this version of this standard,
/// three changes have been made to the country code list, to define the
/// region "sub-Saharan Africa" and remove the "developed regions", and
/// "developing regions". A conformant implementation may recognize these
/// region identifiers in the sense defined in the previous paragraph.
/// If a verifying implementation is required to check that relevant
/// geographic information in a signed SPDU is consistent with a certificate
/// containing one or more instances of this type, then the SDS is permitted
/// to indicate that the signed SPDU is valid even if some instances of this
/// type are unrecognized in the sense defined above, so long as the
/// recognized instances of this type completely contain the relevant
/// geographic information. Informally, if the recognized values in the
/// certificate allow the SDS to determine that the SPDU is valid, then it
/// can make that determination even if there are also unrecognized values in
/// the certificate. This field is therefore not a "critical information
/// field" as defined in 5.2.6, because unrecognized values are permitted so
/// long as the validity of the SPDU can be established with the recognized
/// values. However, as discussed in 5.2.6, the presence of an unrecognized
/// value in a certificate can make it impossible to determine whether the
/// certificate and the SPDU are valid.
pub type UnCountryId = Uint16;
/// The value 900,000,001 indicates that the latitude was not available to the sender
;
/// The value 1,800,000,001 indicates that the longitude was not available to the sender
;
/// gives the validity period of a certificate
///
/// The start of the validity period is given by start and the end is given by
/// start + duration.