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
extern crate alloc;
use cratedelegate;
use crateExtId;
use Builder;
use *;
/// OID for IEEE 1609.2 Base Types module
pub const IEEE1609_DOT2_BASE_TYPES_OID: &Oid = const_new;
// ***************************************************************************
// ** 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 255, i.e., (hex)ff.
pub type Uint8 = u8;
/// 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.
pub type Uint16 = u16;
/// 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.
pub type Uint32 = u32;
/// 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.
pub type Uint64 = u64;
/// This type is used for clarity of definitions.
;
delegate!;
/// This type is used for clarity of definitions.
;
delegate!;
// ***************************************************************************
// ** OCTET STRING Types **
// ***************************************************************************
/// This is a synonym for ASN.1 OCTET STRING, and is used in the
/// definition of other data structures.
;
delegate!;
/// A type containing the truncated hash of another data structure.
///
/// # Hash Calculation
/// The `HashedId3` is calculated by:
/// 1. Computing the hash of the encoded data structure
/// 2. Taking the low-order three bytes of the hash output
/// 3. Using the last three bytes of the 32-byte hash when represented in network byte order
/// 4. Canonicalizing the data structure before hashing if required
///
/// # Hash Algorithm Selection
/// The hash algorithm used for calculating `HashedId3` is context-dependent:
/// - Each structure including a `HashedId3` field specifies how the hash algorithm
/// is determined
/// - See discussion in section 5.3.9 for more details
///
/// # Example
/// Using SHA-256 hash of an empty string:
/// ```text
/// SHA-256("") =
/// e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
///
/// Resulting HashedId3 = 52b855
/// ```
;
delegate!;
/// This type is used for clarity of definitions.
;
delegate!;
/// A type containing the truncated hash of another data structure.
///
/// # Hash Calculation
/// The `HashedId8` is calculated by:
/// 1. Computing the hash of the encoded data structure
/// 2. Taking the low-order eight bytes of the hash output
/// 3. Using the last eight bytes of the hash when represented in network byte order
/// 4. Canonicalizing the data structure before hashing if required
///
/// # Hash Algorithm Selection
/// The hash algorithm used for calculating `HashedId8` is context-dependent:
/// - Each structure including a `HashedId8` field specifies how the hash algorithm
/// is determined
/// - See discussion in section 5.3.9 for more details
///
/// # Example
/// Using SHA-256 hash of an empty string:
/// ```text
/// SHA-256("") =
/// e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
///
/// Resulting HashedId8 = a495991b7852b855
/// ```
;
delegate!;
/// A type containing the truncated hash of another data structure.
///
/// # Hash Calculation
/// The `HashedId10` is calculated by:
/// 1. Computing the hash of the encoded data structure
/// 2. Taking the low-order ten bytes of the hash output
/// 3. Using the last ten bytes of the hash when represented in network byte order
/// 4. Canonicalizing the data structure before hashing if required
///
/// # Hash Algorithm Selection
/// The hash algorithm used for calculating `HashedId10` is context-dependent:
/// - Each structure including a `HashedId10` field specifies how the hash algorithm
/// is determined
/// - See discussion in section 5.3.9 for more details
///
/// # Example
/// Using SHA-256 hash of an empty string:
/// ```text
/// SHA-256("") =
/// e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
///
/// Resulting HashedId10 = 934ca495991b7852b855
/// ```
;
delegate!;
/// A type containing the truncated hash of another data structure.
///
/// # Hash Calculation
/// The `HashedId32` is calculated by:
/// 1. Computing the hash of the encoded data structure
/// 2. Taking the low-order 32 bytes of the hash output
/// 3. Using the last 32 bytes of the hash when represented in network byte order
/// 4. Canonicalizing the data structure before hashing if required
///
/// # Hash Algorithm Selection
/// The hash algorithm used for calculating `HashedId32` is context-dependent:
/// - Each structure including a `HashedId32` field specifies how the hash algorithm
/// is determined
/// - See discussion in section 5.3.9 for more details
///
/// # Example
/// Using SHA-256 hash of an empty string:
/// ```text
/// SHA-256("") =
/// e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
///
/// Resulting HashedId32 =
/// e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
/// ```
;
delegate!;
/// A type containing the truncated hash of another data structure.
///
/// # Hash Calculation
/// The `HashedId48` is calculated by:
/// 1. Computing the hash of the encoded data structure
/// 2. Taking the low-order 48 bytes of the hash output
/// 3. Using the last 48 bytes of the hash when represented in network byte order
/// 4. Canonicalizing the data structure before hashing if required
///
/// # Hash Algorithm Selection
/// The hash algorithm used for calculating `HashedId48` is context-dependent:
/// - Each structure including a `HashedId48` field specifies how the hash algorithm
/// is determined
/// - See discussion in section 5.3.9 for more details
///
/// # Example
/// Using SHA-384 hash of an empty string:
/// ```text
/// SHA-384("") =
/// 38b060a751ac96384cd9327eb1b1e36a21fdb71114be07434c0cc7bf63f6e1da274edebfe76f65fbd51ad2f14898b95b
///
/// Resulting HashedId48 =
/// 38b060a751ac96384cd9327eb1b1e36a21fdb71114be07434c0cc7bf63f6e1da274edebfe76f65fbd51ad2f14898b95b
/// ```
;
delegate!;
// ***************************************************************************
// ** Time Structures **
// ***************************************************************************
/// This type gives the number of (TAI) seconds since 00:00:00 UTC, 1
/// January, 2004.
;
delegate!;
/// This data structure is a 64-bit integer giving an estimate of the
/// number of (TAI) microseconds since 00:00:00 UTC, 1 January, 2004.
;
delegate!;
/// This type 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`.
/// This structure 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 31,556,952 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.
// ***************************************************************************
// ** Location Structures **
// ***************************************************************************
/// Geographic region representation with specified forms.
///
/// 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.
///
/// # Variants
/// - `CircularRegion`: Contains a single instance of the `CircularRegion` structure
/// - `RectangularRegion`: Array of `RectangularRegion` structures containing at least
/// one entry. Interpreted as a series of rectangles, which may overlap or be
/// disjoint. The permitted region is any point within any of the rectangles.
/// - `PolygonalRegion`: Contains a single instance of the `PolygonalRegion` structure
/// - `IdentifiedRegion`: Array of `IdentifiedRegion` structures containing at least
/// one entry. The permitted region is any point within any of the identified regions.
///
/// # Critical Information Fields
/// 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 (per 4.2.2.3.2)
///
/// - For `RectangularRegion`:
/// - Implementation must support at least eight entries
/// - If number of entries is not supported, SPDU must be marked invalid
///
/// - For `IdentifiedRegion`:
/// - Implementation must support at least eight entries
/// - If number of entries is not supported, SPDU must be marked invalid
/// A structure specifying a circle with its center at `center`, radius in meters,
/// and located tangential to the reference ellipsoid.
///
/// The indicated region includes all 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.
///
/// # Note
/// A point containing an elevation component is considered to be within the
/// circular region if its horizontal projection onto the reference ellipsoid
/// lies within the region.
/// Specifies a "rectangle" on the surface of the WGS84 ellipsoid where the sides
/// are given by lines of constant latitude or longitude.
///
/// # Points with Elevation
/// 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.
///
/// # Validity Rules
/// A RectangularRegion is invalid if:
/// - The `north_west` value is south of the `south_east` value
/// - The latitude values in the two points are equal
/// - The longitude values in the two points are equal
///
/// A certificate containing an invalid RectangularRegion is considered invalid.
///
/// # Fields
/// - `north_west`: The north-west corner of the rectangle
/// - `south_east`: The south-east corner of the rectangle
/// This type is used for clarity of definitions.
;
delegate!;
/// Defines a region using a series of distinct geographic points on the surface of
/// the reference ellipsoid.
///
/// The region is specified by:
/// - Connecting points in their order of appearance via geodesics on the reference ellipsoid
/// - Completing the polygon by connecting the final point to the first point
/// - The allowed region is the interior of the polygon and its boundary
///
/// # Points with Elevation
/// A point containing an elevation component is considered within the polygonal
/// region if its horizontal projection onto the reference ellipsoid lies within
/// the region.
///
/// # Validity Rules
/// A valid `PolygonalRegion`:
/// - Must contain at least three points
/// - Must not have intersecting sides (implied lines making up the polygon)
///
/// # Limitations
/// Does not support enclaves/exclaves (may be addressed in future versions of
/// the standard).
///
/// # Critical Information Fields
/// This is a critical information field as defined in 5.2.6:
/// - Implementation must support at least eight `TwoDLocation` entries
/// - If the number of `TwoDLocation` entries is not supported when verifying
/// a signed SPDU, the implementation must indicate that the SPDU is invalid
;
delegate!;
/// Defines a region using a series of distinct geographic points on the surface of
/// the reference ellipsoid.
///
/// The region is specified by:
/// - Connecting points in their order of appearance via geodesics on the reference ellipsoid
/// - Completing the polygon by connecting the final point to the first point
/// - The allowed region is the interior of the polygon and its boundary
///
/// # Points with Elevation
/// A point containing an elevation component is considered within the polygonal
/// region if its horizontal projection onto the reference ellipsoid lies within
/// the region.
///
/// # Validity Rules
/// A valid `PolygonalRegion`:
/// - Must contain at least three points
/// - Must not have intersecting sides (implied lines making up the polygon)
///
/// # Limitations
/// Does not support enclaves/exclaves (may be addressed in future versions of
/// the standard).
///
/// # Critical Information Fields
/// This is a critical information field as defined in 5.2.6:
/// - Implementation must support at least eight `TwoDLocation` entries
/// - If the number of `TwoDLocation` entries is not supported when verifying
/// a signed SPDU, the implementation must indicate that the SPDU is invalid
/// Indicates the region of validity of a certificate using region identifiers.
///
/// A conformant implementation must support at least one of the possible CHOICE values.
/// The Protocol Implementation Conformance Statement (PICS) in Annex A allows an
/// implementation to state which `CountryOnly` values it recognizes.
///
/// # Variants
/// - `CountryOnly`: Indicates only a country (or a geographic entity included in
/// a country list) is given
/// - `CountryAndRegions`: Indicates one or more top-level regions within a country
/// (as defined by the region listing associated with that country) is given
/// - `CountryAndSubregions`: Indicates one or more regions smaller than the
/// top-level regions within a country (as defined by the region listing
/// associated with that country) is given
///
/// # Critical Information Fields
/// 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 SPDU is invalid (per 4.2.2.3.2)
/// - Invalid in this context means its validity cannot be established
/// This type is used for clarity of definitions.
;
delegate!;
/// Integer representation of country or area identifiers as defined by the United
/// Nations Statistics Division (October 2013, see normative references in Clause 0).
///
/// # Implementation Requirements
/// A conformant implementation of `IdentifiedRegion` must:
/// - Recognize at least one value of `UnCountryId` (ability to determine if a
/// 2D location lies inside/outside the identified borders)
/// - May declare recognized `UnCountryId` values in the Protocol Implementation
/// Conformance Statement (PICS) in Annex A
///
/// # Historical Changes
/// Since 2013 and before this standard's publication, three changes to the country
/// code list:
/// - Added "sub-Saharan Africa" region
/// - Removed "developed regions"
/// - Removed "developing regions"
///
/// Conformant implementations may recognize these region identifiers.
///
/// # Verification Behavior
/// When verifying geographic information in a signed SPDU against a certificate:
/// - SDS may indicate SPDU validity even with unrecognized instances if recognized
/// instances completely contain the relevant geographic information
/// - Not considered a "critical information field" (ref: 5.2.6) as unrecognized
/// values are permitted if SPDU validity can be established with recognized values
///
/// # Important Note
/// An unrecognized value in a certificate may still prevent determining the
/// validity of both the certificate and SPDU.
;
delegate!;
/// This type is defined only for backwards compatibility.
;
delegate!;
/// A type representing country and region information with specific implementation requirements.
///
/// # Implementation Requirements
/// - Must support a `regions` field containing at least eight entries
/// - Must be able to determine whether a two-dimensional location lies inside or
/// outside the borders identified by at least:
/// - One value of `UnCountryId`
/// - One region within the country indicated by that recognized `UnCountryId` value
///
/// # Current Version Requirements
/// The only way to satisfy the implementation requirements in this version is to:
/// - Recognize the `UnCountryId` value indicating USA
/// - Recognize at least one of the FIPS state codes for US states
///
/// # Verification Behavior
/// When verifying geographic information in a signed SPDU against a certificate:
/// - The SDS may indicate validity even with unrecognized country/region values
/// - Validity can be determined if recognized values completely contain the relevant
/// geographic information
/// - This is not a "critical information field" (ref: 5.2.6) as unrecognized values
/// are permitted if validity can be established with recognized values
/// - Note: Unrecognized values in a certificate may still prevent determining
/// certificate validity and consequently SPDU validity
///
/// # Fields
/// - `countryOnly`: A `UnCountryId` value identifying the country
/// - `regions`: One or more regions within the country:
/// - For USA: Uses integer version of 2010 FIPS codes from U.S. Census Bureau
/// - For other countries: Region meaning is undefined in current version
///
/// # PICS Conformance
/// The Protocol Implementation Conformance Statement (PICS) in Annex A allows
/// implementations to declare:
/// - Recognized `UnCountryId` values
/// - Recognized region values within each country
/// Implementation requirements and behavior specification for country and subregion handling.
///
/// # Implementation Requirements
/// A conformant implementation:
/// - Must support at least eight entries in the `region_and_subregions` field
/// - Must recognize at least one country value and one region within that country
/// - Currently must specifically recognize:
/// - USA as a `UnCountryId` value
/// - At least one FIPS state code for US states
///
/// The Protocol Implementation Conformance Statement (PICS) in Annex A allows
/// implementations to declare:
/// - Recognized `UnCountryId` values
/// - Recognized region values within each country
///
/// # Verification Behavior
/// When verifying geographic information in a signed SPDU against a certificate:
/// - SDS may indicate SPDU validity even with unrecognized country or
/// `region_and_subregions` values if recognized instances completely contain
/// the relevant geographic information
/// - Not considered a "critical information field" (ref: 5.2.6) as unrecognized
/// values are permitted if SPDU validity can be established with recognized values
///
/// # Important Note
/// An unrecognized value in a certificate may prevent determining the validity
/// of both the certificate and SPDU.
///
/// # Fields
/// - `country`: A `UnCountryId` value identifying the country
/// - `region_and_subregions`: Identifies one or more subregions within the country
/// Represents regions and subregions within an "enclosing country" context.
///
/// # Context
/// Fields are interpreted within the context of an enclosing country:
/// - In `CountryAndSubregions`, the enclosing country is specified by the `country` field
/// - Future uses will specify how the enclosing country is determined
///
/// # USA-Specific Implementation
/// When the enclosing country is the United States of America:
/// - `region`: Identifies state/equivalent entity using 2010 FIPS codes (U.S. Census Bureau)
/// - `subregions`: Identifies county/equivalent entity using 2010 FIPS codes
///
/// For other countries, the meaning is not defined in this version of the standard.
///
/// # Implementation Requirements
/// A conformant implementation must:
/// - Recognize at least one region within an enclosing country
/// - Recognize at least one subregion for the indicated region
/// - For USA specifically:
/// - Recognize at least one FIPS state code
/// - Recognize at least one county code in at least one recognized state
/// - Support at least eight entries in the `subregions` field
///
/// The PICS (Annex A) allows implementations to declare recognized:
/// - `UnCountryId` values
/// - Region values within countries
///
/// # Verification Behavior
/// When verifying geographic information in a signed SPDU against a certificate:
/// - SDS may indicate SPDU validity even with unrecognized subregion values if
/// recognized instances completely contain the relevant geographic information
/// - Not considered a "critical information field" (ref: 5.2.6) as unrecognized
/// values are permitted if SPDU validity can be established with recognized values
///
/// # Important Note
/// An unrecognized value in a certificate may prevent determining the validity
/// of both the certificate and SPDU.
///
/// # Fields
/// - `region`: Identifies a region within a country
/// - `subregions`: Identifies one or more subregions within the region
/// This type is used for clarity of definitions.
;
delegate!;
/// A structure containing an estimate of 3D location, with field-specific details
/// provided in individual field documentation.
///
/// # Compatibility Note
/// The units used in this structure are consistent with SAE J2735 B26 location
/// data structures, though the encoding is incompatible.
/// An INTEGER encoding of latitude estimate with 1/10th microdegree precision,
/// relative to the World Geodetic System (WGS-84) datum as defined in NIMA
/// Technical Report TR8350.2.
///
/// # Value Range
/// - Minimum: -900,000,000
/// - Maximum: 900,000,000
/// - Special Value: 900,000,001 indicates latitude was not available to sender
;
delegate!;
/// An INTEGER encoding of longitude estimate with 1/10th microdegree precision,
/// relative to the World Geodetic System (WGS-84) datum as defined in NIMA
/// Technical Report TR8350.2.
///
/// # Value Range
/// - Minimum: -1,799,999,999
/// - Maximum: 1,800,000,000
/// - Special Value: 1,800,000,001 indicates longitude was not available to sender
;
delegate!;
/// This structure 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.
;
delegate!;
/// 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.
;
delegate!;
/// The known latitudes are from -900,000,000 to +900,000,000 in 0.1
/// microdegree intervals.
;
delegate!;
/// The value 900,000,001 indicates that the latitude was not
/// available to the sender.
;
delegate!;
/// An integer type representing longitude values with named boundary values
/// and constraints.
///
/// # Value Range
/// - Minimum: -1,799,999,999
/// - Maximum: 1,800,000,000
/// - Special Value: 1,800,000,001 (indicates longitude not available to sender)
;
delegate!;
/// Represents a known longitude value in 0.1 microdegree intervals.
///
/// # Value Range
/// - Minimum: -1,799,999,999 (-180 degrees)
/// - Maximum: 1,800,000,000 (180 degrees)
/// - Precision: 0.1 microdegrees
;
delegate!;
/// Represents a longitude value that is explicitly unknown/unavailable.
///
/// This type can only have the value 1,800,000,001, indicating that the longitude
/// was not available to the sender.
;
delegate!;
// ***************************************************************************
// ** Crypto Structures **
// ***************************************************************************
/// Represents a signature for a supported public key algorithm, which may be
/// contained within `SignedData` or `Certificate`.
///
/// # Critical Information Field
/// This is a critical information field as defined in 5.2.5:
/// - An implementation that does not recognize the indicated CHOICE when verifying
/// a signed SPDU shall indicate that the SPDU is invalid (per 4.2.2.3.2)
/// - Invalid in this context means its validity cannot be established
///
/// # Canonicalization
/// This data structure is subject to canonicalization for operations specified
/// in 6.1.2. Canonicalization applies to:
/// - `EcdsaP256Signature` instances
/// - `EcdsaP384Signature` instances
/// Represents an ECDSA signature, generated as specified in 5.3.1.
///
/// # Signature Process
/// - FIPS 186-4: If followed, integer r is represented as an `EccP256CurvePoint`
/// with `x-only` selection
/// - SEC 1: If followed, elliptic curve point R is represented as an `EccP256CurvePoint`
/// with sender's choice of:
/// - `compressed-y-0`
/// - `compressed-y-1`
/// - `uncompressed`
///
/// # Canonicalization
/// This data structure is subject to canonicalization for operations specified in 6.1.2:
/// - When canonicalized, the `EccP256CurvePoint` in `r_sig` must use `x-only` form
///
/// # Technical Details
/// For signatures with:
/// - `x-only` form: x-value in `r_sig` is an integer mod n (group order)
/// - `compressed-y-*` form: x-value in `r_sig` is an integer mod p (field prime)
///
/// Converting `compressed-y-*` to `x-only`: theoretically requires checking if x-value
/// is between n and p, reducing mod n if so. In practice, this check is unnecessary
/// due to Haase's Theorem (probability ≈ 2^(-128) for 256-bit curves).
///
/// # Curve Parameters (hexadecimal)
/// NIST p256:
/// - p = FFFFFFFF00000001000000000000000000000000FFFFFFFFFFFFFFFFFFFFFFFF
/// - n = FFFFFFFF00000000FFFFFFFFFFFFFFFFBCE6FAADA7179E84F3B9CAC2FC632551
///
/// Brainpool p256:
/// - p = A9FB57DBA1EEA9BC3E660A909D838D726E3BF623D52620282013481D1F6E5377
/// - n = A9FB57DBA1EEA9BC3E660A909D838D718C397AA3B561A6F7901E0E82974856A7
/// Represents an ECDSA signature, generated as specified in 5.3.1.
///
/// # Signature Process
/// - FIPS 186-4: If followed, integer r is represented as an `EccP384CurvePoint`
/// with `x-only` selection
/// - SEC 1: If followed, elliptic curve point R is represented as an `EccP384CurvePoint`
/// with sender's choice of:
/// - `compressed-y-0`
/// - `compressed-y-1`
/// - `uncompressed`
///
/// # Canonicalization
/// This data structure is subject to canonicalization for operations specified in 6.1.2:
/// - When canonicalized, the `EccP384CurvePoint` in `r_sig` must use `x-only` form
///
/// # Technical Details
/// For signatures with:
/// - `x-only` form: x-value in `r_sig` is an integer mod n (group order)
/// - `compressed-y-*` form: x-value in `r_sig` is an integer mod p (field prime)
///
/// Converting `compressed-y-*` to `x-only`: theoretically requires checking if x-value
/// is between n and p, reducing mod n if so. In practice, this check is unnecessary
/// due to Haase's Theorem (probability ≈ 2^(-192) for 384-bit curves).
///
/// # Curve Parameters (hexadecimal)
/// ```text
/// p = 8CB91E82A3386D280F5D6F7E50E641DF152F7109ED5456B412B1DA197FB71123\
/// ACD3A729901D1A71874700133107EC53
/// n = 8CB91E82A3386D280F5D6F7E50E641DF152F7109ED5456B31F166E6CAC0425A7\
/// CF3AB6AF6B7FC3103B883202E9046565
/// ```
/// Represents an 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.
/// Specifies a point on an elliptic curve in Weierstrass form defined over a
/// 256-bit prime number.
///
/// # Supported Curves
/// - NIST p256 (FIPS 186-4)
/// - Brainpool p256r1 (RFC 5639)
/// - SM2 curve (GB/T 32918.5-2017)
///
/// # Encoding Details
/// Fields are OCTET STRINGS encoded according to IEEE Std 1363-2000, 5.5.6:
/// - x-coordinate: Always 32 octets, unsigned integer in network byte order
/// - y-coordinate: Encoding depends on point representation:
/// - `XOnly`: y is omitted
/// - `CompressedY0`: y's least significant bit is 0
/// - `CompressedY1`: y's least significant bit is 1
/// - `Uncompressed`: y is explicit 32 octets, unsigned integer in network byte order
///
/// # Canonicalization
/// Subject to canonicalization for operations specified in 6.1.2 when appearing in:
/// - `HeaderInfo`
/// - `ToBeSignedCertificate`
///
/// See respective type definitions for specific canonicalization operations.
/// Inner type of `EccP256CurvePoint` representing an uncompressed point on the NIST P-256 curve.
/// Specifies a point on an elliptic curve in Weierstrass form defined over a
/// 384-bit prime number.
///
/// # Supported Curves
/// Only supports Brainpool p384r1 as defined in RFC 5639.
///
/// # Encoding Details
/// Fields are OCTET STRINGS encoded according to IEEE Std 1363-2000, 5.5.6:
/// - x-coordinate: Always 48 octets, unsigned integer in network byte order
/// - y-coordinate: Encoding depends on point representation:
/// - `XOnly`: y is omitted
/// - `CompressedY0`: y's least significant bit is 0
/// - `CompressedY1`: y's least significant bit is 1
/// - `Uncompressed`: y is explicit 48 octets, unsigned integer in network byte order
///
/// # Canonicalization
/// Subject to canonicalization for operations specified in 6.1.2 when appearing in:
/// - `HeaderInfo`
/// - `ToBeSignedCertificate`
///
/// See respective type definitions for specific canonicalization operations.
/// Inner type of `EccP384CurvePoint` representing an uncompressed point on the Brainpool P-384 curve.
/// Indicates supported symmetric algorithms and their modes of operation.
///
/// # Supported Algorithms
/// - AES-128
/// - SM4
///
/// # Mode of Operation
/// Only supports Counter Mode Encryption With Cipher Block Chaining Message
/// Authentication Code (CCM).
///
/// Full implementation details are specified in section 5.3.8.
/// Identifies supported hash algorithms. See section 5.3.3 for implementation details.
///
/// # Supported Algorithms
/// - SHA-256
/// - SHA-384
/// - SM3
///
/// # Critical Information Field
/// This is a critical information field as defined in 5.2.6:
/// - An implementation that does not recognize the enumerated value when verifying
/// a signed SPDU shall indicate that the SPDU is invalid (per 4.2.2.3.2)
/// - Invalid in this context means its validity cannot be established
/// Used to transfer 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.
///
/// # Fields
/// - `v`: Sender's ephemeral public key (output V from encryption as specified
/// in 5.3.5.1)
/// - `c`: Encrypted symmetric key (output C from encryption as specified in 5.3.5.1).
/// The algorithm is identified by the CHOICE in the following `SymmetricCiphertext`.
/// For ECIES, this algorithm must be AES-128.
/// - `t`: Authentication tag (output tag from encryption as specified in 5.3.5.1)
/// Used to transfer 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.
///
/// # Fields
/// - `v`: Sender's ephemeral public key (output V from encryption as specified
/// in 5.3.5.2)
/// - `c`: Encrypted symmetric key (output C from encryption as specified in 5.3.5.2).
/// The algorithm is identified by the CHOICE in the following `SymmetricCiphertext`.
/// For SM2, this algorithm must be SM4.
/// - `t`: Authentication tag (output tag from encryption as specified in 5.3.5.2)
/// Contains an encryption key, which may be either public or symmetric.
///
/// # Canonicalization
/// Subject to canonicalization for operations specified in 6.1.2 when appearing in:
/// - `HeaderInfo`
/// - `ToBeSignedCertificate`
///
/// Canonicalization applies to the `PublicEncryptionKey`. See respective type
/// definitions for specific canonicalization operations.
/// Specifies a public encryption key and its associated symmetric algorithm used
/// for bulk data encryption when encrypting for that public key.
///
/// # Canonicalization
/// Subject to canonicalization for operations specified in 6.1.2 when appearing in:
/// - `HeaderInfo`
/// - `ToBeSignedCertificate`
///
/// Canonicalization applies to the `BasePublicEncryptionKey`. See respective type
/// definitions for specific canonicalization operations.
/// This structure 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 public key and its associated verification algorithm.
/// Cryptographic mechanisms are defined in section 5.3.
///
/// # Validity Rules
/// An `EccP256CurvePoint` or `EccP384CurvePoint` within this structure is invalid
/// if it indicates the choice `x-only`.
///
/// # Critical Information Field
/// 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 SPDU is invalid (per 4.2.2.3.2)
/// - Invalid in this context means its validity cannot be established
///
/// # Canonicalization
/// Subject to canonicalization for operations specified in 6.1.2:
/// - Applies to both `EccP256CurvePoint` and `EccP384CurvePoint`
/// - Points must be encoded in compressed form (`compressed-y-0` or `compressed-y-1`)
/// Provides key bytes for use with an identified symmetric algorithm.
///
/// # Supported Algorithms
/// - AES-128 in CCM mode
/// - SM4 in CCM mode
///
/// See section 5.3.8 for implementation details.
// ***************************************************************************
// ** PSID / ITS-AID **
// ***************************************************************************
/// Represents permissions for a certificate holder regarding activities in a single
/// application area, identified by a `Psid`.
///
/// # Permission Determination
/// - The SDEE (not SDS) determines if activities are consistent with PSID and
/// ServiceSpecificPermissions
/// - SDS provides PSID and SSP information to SDEE for determination
/// - See section 5.2.4.3.3 for details
///
/// # SDEE Specification Requirements
/// The SDEE specification must:
/// - Specify permitted activities for particular `ServiceSpecificPermissions` values
/// - Either:
/// - Specify permitted activities when `ServiceSpecificPermissions` is omitted, or
/// - State that `ServiceSpecificPermissions` must always be present
///
/// # Consistency Rules
/// ## With Signed SPDU
/// Consistency between SSP and signed SPDU is defined by PSID-specific rules
/// (out of scope for this standard, see 5.1.1)
///
/// ## With Issuing Certificate
/// When `ssp` field is omitted, entry A is consistent with issuing certificate if
/// the certificate contains a `PsidSspRange` P where:
/// - P's `psid` field equals A's `psid` field and either:
/// - P's `sspRange` field indicates "all"
/// - P's `sspRange` field indicates "opaque" and contains an empty OCTET STRING
///
/// See following subclauses for consistency rules with other `ssp` field forms.
/// This type is used for clarity of definitions.
;
delegate!;
/// This type represents the PSID defined in IEEE Std 1609.2.
;
delegate!;
/// This type is used for clarity of definitions.
;
delegate!;
/// Represents 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 either:
/// - PSID-specific octet strings
/// - Bitmap-based
///
/// See Annex C for guidance on choosing SSP forms for application specifiers.
///
/// # Consistency with Issuing Certificate
/// For an `appPermissions` entry A with `opaque` SSP field, A is consistent with
/// the issuing certificate if it contains one of:
///
/// ## Option 1
/// A `SubjectPermissions` field indicating "all" and no `PsidSspRange` field
/// containing A's `psid` field
///
/// ## Option 2
/// A `PsidSspRange` P where:
/// - P's `psid` field equals A's `psid` field and either:
/// - P's `sspRange` field indicates "all"
/// - P's `sspRange` field indicates "opaque" and contains an OCTET STRING
/// identical to A's opaque field
///
/// See following subclauses for consistency rules with other
/// `ServiceSpecificPermissions` types.
/// This structure represents a bitmap representation of a SSP. The
/// mapping of the bits of the bitmap to constraints on the signed SPDU is
/// PSID-specific.
///
/// 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.
;
delegate!;
/// Represents the certificate issuing or requesting permissions of the certificate
/// holder for a particular set of application permissions.
///
/// # Fields
/// - `psid`: Identifies the application area
/// - `ssp_range`: Identifies the SSPs associated with the PSID for which the holder
/// may issue or request certificates. If omitted, the holder may issue or request
/// certificates for any SSP for that PSID.
/// This type is used for clarity of definitions.
;
delegate!;
/// Identifies the SSPs associated with a PSID for which the holder may issue or
/// request certificates.
///
/// # Consistency with Issuing Certificate
/// ## For Opaque SSP Field
/// A `PsidSspRange` A is consistent with the issuing certificate if it contains
/// one of:
///
/// ### Option 1
/// A `SubjectPermissions` field indicating "all" and no `PsidSspRange` field
/// containing A's `psid` field
///
/// ### Option 2
/// A `PsidSspRange` P where:
/// - P's `psid` field equals A's `psid` field and either:
/// - P's `sspRange` field indicates "all"
/// - Both P and A indicate "opaque", and every OCTET STRING in A's opaque
/// matches one in P's opaque
///
/// ## For All SSP Field
/// A `PsidSspRange` A is consistent if the issuing certificate contains either:
///
/// ### Option 1
/// A `SubjectPermissions` field indicating "all" and no `PsidSspRange` field
/// containing A's `psid` field
///
/// ### Option 2
/// A `PsidSspRange` P where:
/// - P's `psid` field equals A's `psid` field
/// - P's `sspRange` field indicates "all"
///
/// See following subclauses for consistency rules with other `SspRange` types.
///
/// # Note
/// While "all" can be indicated either by omitting `SspRange` in the enclosing
/// `PsidSspRange` or explicitly, omission is preferred.
/// A bitmap representation of a SSP. The `sspValue` indicates permissions and 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.
///
/// # Certificate Consistency
/// If a certificate has a `PsidSspRange` value P for which the sspRange field is
/// bitmapSspRange, P is consistent with the issuing certificate if the issuing
/// certificate contains one of:
///
/// ## Option 1
/// A SubjectPermissions field indicating the choice "all" and no PsidSspRange field
/// containing the psid field in P
///
/// ## Option 2
/// A PsidSspRange R where:
/// - The psid field in R equals the psid field in P and 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 corresponding bit in sspBitmask in P is set to 1
/// - The corresponding bit in sspValue in P equals the bit in sspValue in R
///
/// Reference: ETSI TS 103 097
// ***************************************************************************
// ** Certificate Components **
// ***************************************************************************
/// Contains the certificate holder's assurance level, indicating the security of
/// both the platform and storage of secret keys, as well as the confidence in
/// this assessment.
///
/// # Bit Field Encoding
/// ```text
/// Bit number | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
/// -------------- | --- | --- | --- | --- | --- | --- | --- | --- |
/// Interpretation | A | A | A | R | R | R | C | C |
///
/// Where:
/// - A: Assurance level (bits 7-5)
/// - R: Reserved for future use (bits 4-2)
/// - C: Confidence level (bits 1-0)
/// - Bit 0 is least significant
/// ```
///
/// # Interpretation
/// - Higher assurance values indicate more trusted holders (when comparing
/// certificates with the same confidence value)
/// - Specific assurance level definitions and confidence level encoding are
/// outside this standard's scope
///
/// # Historical Note
/// Originally specified in ETSI TS 103 097. Future uses are expected to maintain
/// consistency with future versions of that standard.
;
delegate!;
/// This integer identifies a series of CRLs issued under the authority of a particular CRACA.
;
delegate!;
// *****************************************************************************
// ** Pseudonym Linkage **
// *****************************************************************************
/// This atomic type is used in the definition of other data structures.
;
delegate!;
/// This is a UTF-8 string as defined in IETF RFC 3629. The contents are determined by policy.
;
delegate!;
/// This is the individual linkage value. See 5.1.3 and 7.3 for details of use.
;
delegate!;
/// This is the group linkage value. See 5.1.3 and 7.3 for details of use.
/// This structure contains a LA Identifier for use in the algorithms specified in 5.1.3.4.
;
delegate!;
/// This type is used for clarity of definitions.
;
delegate!;
/// This structure contains a linkage seed value for use in the algorithms specified in 5.1.3.4.
;
delegate!;
// ***************************************************************************
// ** Information Object Classes and Sets **
// ***************************************************************************
// Excluding CERT-EXT-TYPE - other types here are defined in ETSI TS 103 097 extension module
// /**
// * @brief This structure is the Information Object Class used to contain
// * information about a set of certificate extensions that are associated with
// * each other: an AppExtension, a CertIssueExtension, and a
// * CertRequestExtension.
// */
// CERT-EXT-TYPE ::= CLASS {
// &id ExtId,
// &App,
// &Issue,
// &Req
// } WITH SYNTAX {ID &id APP &App ISSUE &Issue REQUEST &Req}
// /**
// * @brief This parameterized type represents a (id, content) pair drawn from
// * the set ExtensionTypes, which is constrained to contain objects defined by
// * the class EXT-TYPE.
// */
// Extension {EXT-TYPE : ExtensionTypes} ::= SEQUENCE {
// id EXT-TYPE.&extId({ExtensionTypes}),
// content EXT-TYPE.&ExtContent({ExtensionTypes}{@.id})
// }
// /**
// * @brief This class defines objects in a form suitable for import into the
// * definition of HeaderInfo.
// */
// EXT-TYPE ::= CLASS {
// &extId ExtId,
// &ExtContent
// } WITH SYNTAX {&ExtContent IDENTIFIED BY &extId}
// /**
// * @brief This type is used as an identifier for instances of ExtContent
// * within an EXT-TYPE.
// */
// ExtId ::= INTEGER(0..255)
//
/// This structure is the Information Object Class used to contain information about a set of certificate extensions that are associated with each other: an AppExtension, a CertIssueExtension, and a CertRequestExtension.