Registration Authority --> Linkage Authority:
linkage value request
Definitions
linkage value request (Information Flow): Request of authorization certificate linkage data, including linkage values and/or linkage seed (for revocation).
Registration Authority (Source Physical Object): The 'Registration Authority' (RA) is a component of the CCMS that is the main point of contact for an end entity, and is responsible for provisioning the end entity with authorization and successor enrollment
Linkage Authority (Destination Physical Object): A linkage authority (LA) is a component of a CCMS that provides inputs to the linkage value calculation process to enable efficient revocation of pseudonym certificates; using two linkage authorities preserves the privacy of an end entity against the authorization certificate authority.
Included In
This Triple is in the following Service Packages:
- None
This triple is associated with the following Functional Objects:
- None
This Triple is described by the following Functional View Data Flows:
- None
This Triple has the following triple relationships:
None |
Communication Solutions
- (None-Data) - Guaranteed Secure Internet (ITS) (32)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
Development needed |
Security
|
|
TransNet
|
|||
Access
Internet Subnet Alternatives |
Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.
Characteristics
Characteristic | Value |
---|---|
Time Context | Recent |
Spatial Context | Regional |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Source |
Authenticable | True |
Encrypt | True |
Interoperability | Description |
---|---|
Regional | Interoperability throughout the geopolitical region is highly desirable, but if implemented differently in different transportation management jurisdictions, significant benefits will still accrue in each jurisdiction. Regardless, this Information Flow Triple should be implemented consistently within a transportation jurisdiction (i.e., the scope of a regional architecture). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Moderate | High | High | |
Basis |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |