dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_identity

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_identity [2026/07/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:l:logical_node_identity to dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_identity nick_didodido:99_annexes:annex-b-terms-and-definitions:l:logical_node_identity [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Logical Node Identity ====== ====== Logical Node Identity ======
  
-[[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]+[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]
  
 ===== Discussion ===== ===== Discussion =====
Line 9: Line 9:
 Logical Node Identity supports logical attribution and traceability. It allows reviewers to determine which Logical Node produced information, consumed information, performed a role, participated in a Runtime Plane, or contributed to an interaction. Logical Node Identity supports logical attribution and traceability. It allows reviewers to determine which Logical Node produced information, consumed information, performed a role, participated in a Runtime Plane, or contributed to an interaction.
  
-Logical Node Identity remains distinct from implementation and deployment identifiers. Later implementation profiles use runtime identifiers such as certificates, service accounts, process names, container names, pod names, host names, network addresses, API identities, or DDS participant names to realise, bind, or reference a Logical Node Identity. Those identifiers do not replace the Logical Node Identity.+Logical Node Identity remains distinct from implementation and deployment identifiers. Later implementation profiles use runtime identifiers such as certificates, service accounts, process names, container names, pod names, host names, network addresses, API identities, or DDS participant names to realize, bind, or reference a Logical Node Identity. Those identifiers do not replace the Logical Node Identity.
  
 ===== Definition ===== ===== Definition =====
Line 17: Line 17:
 ===== Source ===== ===== Source =====
  
-Specialisation of Node Identity from Part 1, Section 7.3; generalised from identity material in the original FX Demo Reference Architecture.+Specialization of Node Identity from Part 1, Section 7.3; generalised from identity material in the original FX Demo Reference Architecture.
  
 ===== Note ===== ===== Note =====
  
-Logical Node Identity is not a user identity, organisation identity, container name, pod name, host name, network address, process identifier, repository path, or deployment profile name.+Logical Node Identity is not a user identity, organization identity, container name, pod name, host name, network address, process identifier, repository path, or deployment profile name.
  
 ===== Example ===== ===== Example =====
  
 A logical Config and Policy Sync Node has a stable Logical Node Identity, so command acknowledgements, configuration status, audit entries, and provenance records all identify the same logical participant. A logical Config and Policy Sync Node has a stable Logical Node Identity, so command acknowledgements, configuration status, audit entries, and provenance records all identify the same logical participant.
  • dido/99_annexes/annex-b-terms-and-definitions/l/logical_node_identity.1783793679.txt.gz
  • Last modified: 2026/07/11 11:14
  • by nick_dido