ITS Object --> Device Configuration Manager:
enrollment request
Definitions
enrollment request (Information Flow): A message used to request an enrollment certificate, which may include a device's canonical identifier.
ITS Object (Source Physical Object): The general 'ITS Object' includes core capabilities common to any class of object.
Device Configuration Manager (Destination Physical Object): The 'device configuration manager' (DCM) is a component of the CCMS that is responsible for bootstrapping an end entity and providing secure connection between the end entity and the enrollment 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:
Relationship | Source | Destination | Flow |
---|---|---|---|
Request-Response | Device Configuration Manager | ITS Object | enrollment cert |
Communication Solutions
- (None-Data) - 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 |