Configuration options are available for global and local policy parameters.
List of Global Configuration Options
Required for PoC
Option Value for PoC
Version number of the SCMS
RA, PCA, EE
The Global Certificate Chain File (GCCF) version
This identifier is used to determine if the EE's version of the LCCF is up-to-date. The identifier for the LCCF is mirrored from the GCCF identifier by the RA and included in the LCCF file name. If the GCCF and related LCCF identifier in the LCCF file name indicate that a newer LCCF version is available, the RA will download the updated LCCF to the EE.
Additional information on the GCCF File can be found in: Global Certificate Chain File.
Maximum time to maintain trust past next CRL date
How long an EE can continue to operate without a CRL update past a next CRL date before deciding that messages are not trustworthy and rejecting all of them (and turning on an appropriate driver warning indicator).
This is not expected to be implemented in the EEs for PoC, but should be included in the global file for PoC. There must be some point at which this transition occurs, or CRLs are greatly weakened; and it makes sense for the tolerance to change as CRL distribution technology improves.
The length of the certificate's i-period in minutes
Currently the i-value is defined as one week (or 10080 minutes) but this might change with more connectivity.
Minimum certificates per i-period
The minimum number of certificates an EE receives per i-value (currently i-value = week). This number is also the j-value. Currently that is 20 per week and this might change over time.
No maximum number capabilities. Note that CRL plan means that this can be set no higher than 255.
Certificate validity model
Pseudonym certificates are either "concurrently" or "non-concurrently" valid.
This setting means that the 20 certs per week are all concurrently valid during that week, also affects CRL.
RA, PCA, EE
Maximum time with which to provision OBEs with pseudonym certificates
How many years worth of pseudo certs should be provided during the initial provisioning, and then maintained by top-off. For PoC, it is currently 3 years.
Affects ability to make major changes in the overall system; also affects size of CRL.
Maximum Individual Certificate Request Age
Controls maximum amount of time an Individual Certificate Request can stay in the aggregator waiting to be shuffled.
NOTE: this is only for certificate requests (not for top-offs) - minimum number or timing minimum, whichever comes first. In deployment, this will be an infinite number. Use of this option in deployment, if allowed, will require permission from the SCMS Manager.
Specifies the minimum number of Individual Certificate Requests to accumulate before shuffling and sending to PCA.
This is being considered as the minimum number for full privacy mode. Global sets acceptable option value limits. Local sets option value within Global limits.
The length in bytes of the "hash of request"
The length in bytes of the "hash of request" that PCA and RA use to identify individual requests.
Full hash for PoC
RA, PCA, LA
Maximum time interval between requesting GPF and GCCF updates
SCMS Components need to know when the contents of the Global Policy File (GPF) or Global Certificate Chain File (GCCF) change.
Under current procedures, SCMS Components need to request the GPF and GCCF.
RA, PCA, RSE
Validity period of RSE application certificates
1 week + rse_application_cert_overlap
The value of this parameter shall be the total validity period, including the overlap interval. The initial PoC value should be 169 hours (1 week + 1 hour of overlap)
RA, PCA, RSE
Overlap period of RSE application certificates
List of local configuration options
|Identifier||Affected Component||Configuration Option||Description||Required for PoC||Option Value for PoC||Comment|
|RA||Shuffle Threshold||Controls how many Individual Certificate Requests to accumulate before shuffling and sending to PCA.||Y||1000||This is being considered as the minimum number for full privacy mode; Global sets acceptable option value limits; Local sets option value within Global limits.|
|RA, LA, EE||The actual number of certificates per i-value. certs_per_i_value must be equal or larger than min_certs_per_i_value.||This is the actual number of certificates an EE receives. For POC, this is an RA setting (i.e., the setting is per RA, or possibly sub-RA, not necessarily per EE).||Y||20/40||Current plan is to use 20 as the main PoC value, but to test that 40 would also work. Note that CRL plan means that this can be set no higher than 255. All affected components and/or EEs do not necessarily need to be notified separately from the results of cert update requests.|
|RA||Addresses of LA1||Used to communicate with Linkage Authority 1.||Y||Local configuration to be approved by SCMS Manager?|
|RA||Addresses of LA2||Used to communicate with Linkage Authority 2.||Y||Local configuration to be approved by SCMS Manager?|
|RA||Address of PCA||Used to communicate with the Pseudonym Certificate Authority.||Y||Local configuration to be approved by SCMS Manager?|
|RA||TLS Certificate for RA||X.509 certificate used for transport layer security.||Y||Local configuration|
|PCA, LA||Shared symmetric key between LA and PCA||Maximum time between changes to pre-linkage value encryption/decryption key.||Y||Local configuration to be approved by SCMS Manager?|
|PCA||TLS Certificate for PCA||X.509 certificate used for transport layer security.||Y||Local configuration|
|LA||TLS Certificate for LA||X.509 certificate used for transport layer security.||Y||Local configuration|
Time Limited Configuration Options
It is valuable to define a time validity for options. This capability is very useful when the value of a configuration option changes. For instance, if i_period changes from one week to one day on January 1st, 2030, it is necessary to inform all EEs ahead of time about the change.
This is done by including a time validity for each configuration option. Each configuration option entry can take the following time validity options:
- N/A: there is no timely limitation for this configuration parameter
- Sequence of configuration option value and time validity - There is a sequence of the following per configuration option entry
- The configuration option value
- Start time: The start-time when the configuration option value starts being valid. This is 'N/A' if the start-time was in the past. The current/first entry is always 'N/A.'
- End time: The end-time until the configuration option value ends being valid. This is 'N/A' if there is no defined end-time. The last entry is always 'N/A' (open ended).
The following example provides two time dependent options for the parameter la_identifier_size:
Here the text in  is one option, and there are two options. The first option indicates a byte size of 2 bytes for la_identifier_size, valid until 12/31/2015 without any start date. The second option indicates a byte size of 4 bytes for la_identifier_size, valid from 1/1/2016 without any end date.
PoC will test the format and delivery of this extended policy configuration, but each identifier entry will have a single open-ended time span.
- Uniqueness of global policy file: Each global policy file shall be unique in the sense that it supersedes a previous global policy file, and there is exactly one valid technical global policy file
- Completeness of configuration option entry: Each configuration option entry shall be complete in the sense that it provides a configuration option value for any time in the future. This implies that the first time entry and the last time entry are always open ended ('N/A').
- Uniqueness of configuration option entry: Each configuration option entry shall be unique and unambiguous, and at no point in time shall there be two valid entries
- Minimum options: Each configuration option entry shall be minimal, and two subsequent time periods shall not use the same option value.