dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:data_in_motion
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:data_in_motion [2022/01/17 15:55] nick |
dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:data_in_motion [2022/05/27 19:57] (current) nick |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== 2.3.4.2.2 Data-In-Motion ====== | + | ====== 2.3.4.2.2 Data-in-Motion ====== |
| [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:start| Return to State of Data Taxonomy]] | [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:start| Return to State of Data Taxonomy]] | ||
| ===== Overview ===== | ===== Overview ===== | ||
| - | [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:motion | Return to Top]] | + | [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:data_in_motion| Return to Top]] |
| [[dido:public:ra:xapend:xapend.a_glossary:d:data_in_motion]], also referred to as **Data in Transit** or **Data in Flight**, is a [[dido:public:ra:xapend:xapend.a_glossary:d:digital_asset]] transmitted between locations (i.e., between computers or computer components). Data-In-Motion also describes data within [[dido:public:ra:xapend:xapend.a_glossary:r:computermemory]]. | [[dido:public:ra:xapend:xapend.a_glossary:d:data_in_motion]], also referred to as **Data in Transit** or **Data in Flight**, is a [[dido:public:ra:xapend:xapend.a_glossary:d:digital_asset]] transmitted between locations (i.e., between computers or computer components). Data-In-Motion also describes data within [[dido:public:ra:xapend:xapend.a_glossary:r:computermemory]]. | ||
| Line 14: | Line 14: | ||
| * Traversing trusted private networks (i.e. [[dido:public:ra:xapend:xapend.a_glossary:i:intranet]]) or untrusted networks (i.e., [[dido:public:ra:xapend:xapend.a_glossary:i:internet]]). | * Traversing trusted private networks (i.e. [[dido:public:ra:xapend:xapend.a_glossary:i:intranet]]) or untrusted networks (i.e., [[dido:public:ra:xapend:xapend.a_glossary:i:internet]]). | ||
| - | Once the data arrives at its final destination, it is classified as [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:rest | Data-at-Rest]]. | + | Once the data arrives at its final destination, it is classified as [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:data_at_rest| Data-at-Rest]]. |
| - | Because Data-in-Motion is vulnerable to [[dido:public:ra:xapend:xapend.a_glossary:m:mitm]] attacks, it is often [[dido:public:ra:xapend:xapend.a_glossary:e:encryption | Encrypted]] to prevent interception. For example, the [[dido:public:ra:xapend:xapend.a_glossary:i:iscsi| Internet Small Computer System Interface (iSCSI)]] transport layer incorporates [[dido:public:ra:xapend:xapend.a_glossary:i:ipsec]], which can [[dido:public:ra:xapend:xapend.a_glossary:e:encryption | encrypt]] data as it is transferred between two devices to prevent a hacker with a sniffer from seeing the contents of that data. IPSec has been used extensively as a transit encryption protocol for [[dido:public:ra:xapend:xapend.a_glossary:v:vpn]] tunnels because it makes use of [[dido:public:ra:xapend:xapend.a_glossary:c:cryptographic_algorithm | Cryptography Algorithms]] such as Triple DES (3DES) and [[dido:public:ra:xapend:xapend.b_stds:tech:nist:sp_800-34e | Advanced Encryption Standard (AES)]]. Encryption [[dido:public:ra:xapend:xapend.a_glossary:p:platform]] software can also be integrated with existing [[dido:public:ra:xapend:xapend.a_glossary:e:erp]] systems to keep Data-in-Motion secure. | + | Because Data-in-Motion is vulnerable to [[dido:public:ra:xapend:xapend.a_glossary:m:mitm]] attacks, it is often [[dido:public:ra:xapend:xapend.a_glossary:e:encryption | Encrypted]] to prevent interception. For example, the [[dido:public:ra:xapend:xapend.a_glossary:i:iscsi| Internet Small Computer System Interface (iSCSI)]] transport layer incorporates [[dido:public:ra:xapend:xapend.a_glossary:i:ipsec]], which can [[dido:public:ra:xapend:xapend.a_glossary:e:encryption | encrypt]] data as it is transferred between two devices to prevent a [[dido:public:ra:xapend:xapend.a_glossary:h:hacker]] with a sniffer from seeing the contents of that data. IPSec has been used extensively as a transit encryption protocol for [[dido:public:ra:xapend:xapend.a_glossary:v:vpn]] tunnels because it makes use of [[dido:public:ra:xapend:xapend.a_glossary:c:cryptographic_algorithm | Cryptography Algorithms]] such as Triple DES (3DES) and [[dido:public:ra:xapend:xapend.b_stds:tech:nist:sp_800-34e | Advanced Encryption Standard (AES)]]. Encryption [[dido:public:ra:xapend:xapend.a_glossary:p:platform]] software can also be integrated with existing [[dido:public:ra:xapend:xapend.a_glossary:e:erp]] systems to keep Data-in-Motion secure. |
| ===== DIDO Specifics ===== | ===== DIDO Specifics ===== | ||
| - | [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:motion | Return to Top]] | + | [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:data_in_motion| Return to Top]] |
| ==== Overview ==== | ==== Overview ==== | ||
| Line 32: | Line 32: | ||
| </figure> | </figure> | ||
| - | : **Note:** Also see: [[dido:public:ra:1.4_req:2_nonfunc:28_manageability:06_system]] figure on the __Industrial Internet Consortium’s Connectivity Framework__ | + | : **Note:** Also see the figure describing the __Industrial Internet Consortium’s Connectivity Framework__ in [[dido:public:ra:1.4_req:2_nonfunc:28_manageability:06_system]]. |
| ^ IIOT Level(( | ^ IIOT Level(( | ||
| - | The Industrial Internet Consortium **Levels** are similar, but differnt from the [[dido:public:ra:xapend:xapend.a_glossary:o:osi]] **Layers**. However, there is some overlap between the **Levels** and **Layers** especially at the lower rungs. However, it is imprtant to differentiate between the two. Where possible in the discussion of the **Levels**, the corresponding **Layers** are provided. | + | The Industrial Internet Consortium **Levels** are similar, but different from the [[dido:public:ra:xapend:xapend.a_glossary:o:osi]] **Layers**. However, there is some overlap between the **Levels** and **Layers** especially at the lower rungs. However, it is important to differentiate between the two. Where possible in the discussion of the **Levels**, the corresponding **Layers** are provided. |
| )) ^ Description ^ | )) ^ Description ^ | ||
| ^ Distributed Application | <WRAP> | ^ Distributed Application | <WRAP> | ||
| Line 50: | Line 50: | ||
| * Social media | * Social media | ||
| </WRAP>| | </WRAP>| | ||
| - | ^ DIDO Platform | <WRAP>[[dido:public:ra:xapend:xapend.a_glossary:d:dido_platform | DIDO Platforms ]] are not a single software entity such as in an [[dido:public:ra:xapend:xapend.a_glossary:a:application]], but rather a set of components integrated together. In a DIDO, the integration includes Software and [[dido:public:ra:xapend:xapend.a_glossary:h:hardware]] [[ dido:public:ra:xapend:xapend.a_glossary:c:component | Components]] that are more than just the [[dido:public:ra:xapend:xapend.a_glossary:s:software]] and [[dido:public:ra:xapend:xapend.a_glossary:h:hardware]] components integrated as a[[dido:public:ra:xapend:xapend.a_glossary:s:sw_stack]] or [[dido:public:ra:xapend:xapend.a_glossary:s:solution_stack]] residing on a single [[dido:public:ra:xapend:xapend.a_glossary:n:node]] but on a collection of Nodes called a [[dido:public:ra:xapend:xapend.a_glossary:n:node_network]]. | + | ^ DIDO Platform | <WRAP>[[dido:public:ra:xapend:xapend.a_glossary:d:dido_platform | DIDO Platforms ]] are not a single software entity such as in an [[dido:public:ra:xapend:xapend.a_glossary:a:application]], but rather a set of components integrated together. In a DIDO, the integration includes Software and [[dido:public:ra:xapend:xapend.a_glossary:h:hardware]] [[ dido:public:ra:xapend:xapend.a_glossary:c:component | Components]] that are more than just the [[dido:public:ra:xapend:xapend.a_glossary:s:software]] and [[dido:public:ra:xapend:xapend.a_glossary:h:hardware]] components integrated as a [[dido:public:ra:xapend:xapend.a_glossary:s:sw_stack]] or [[dido:public:ra:xapend:xapend.a_glossary:s:solution_stack]] residing on a single [[dido:public:ra:xapend:xapend.a_glossary:n:node]] but on a collection of Nodes called a [[dido:public:ra:xapend:xapend.a_glossary:n:node_network]]. |
| * [[dido:public:ra:xapend:xapend.a_glossary:b:bitcoin]] | * [[dido:public:ra:xapend:xapend.a_glossary:b:bitcoin]] | ||
| Line 64: | Line 64: | ||
| </WRAP>| | </WRAP>| | ||
| ^ Framework | <WRAP> | ^ Framework | <WRAP> | ||
| - | A Framework is [[dido:public:ra:xapend:xapend.a_glossary:s:software]] that is an [[dido:public:ra:xapend:xapend.a_glossary:n:nonfuncreq]] abstraction of [[dido:public:ra:1.4_req:2_nonfunc:20_maintainability:reuseability | Reusable]], generic, tailorable [[dido:public:ra:xapend:xapend.a_glossary:c:component | Components]] by the use of user-written, application-specific [[dido:public:ra:xapend:xapend.a_glossary:p:plug_in]] software. Frameworks provide a standardized mechanism for designing, building and deploying [[dido:public:ra:xapend:xapend.a_glossary:a:application | Applications]]. Framweworks leverage either a [[dido:public:ra:xapend:xapend.a_glossary:s:solutionstack]] or [[dido:public:ra:xapend:xapend.a_glossary:s:solution_stack]]. | + | A Framework is [[dido:public:ra:xapend:xapend.a_glossary:s:software]] that is a [[dido:public:ra:xapend:xapend.a_glossary:n:nonfuncreq]] abstraction of [[dido:public:ra:1.4_req:2_nonfunc:20_maintainability:reuseability | Reusable]], generic, tailorable [[dido:public:ra:xapend:xapend.a_glossary:c:component | Components]] by the use of user-written, application-specific [[dido:public:ra:xapend:xapend.a_glossary:p:plug_in]] software. Frameworks provide a standardized mechanism for designing, building and deploying [[dido:public:ra:xapend:xapend.a_glossary:a:application | Applications]]. Frameworks leverage either a [[dido:public:ra:xapend:xapend.a_glossary:s:solutionstack]] or [[dido:public:ra:xapend:xapend.a_glossary:s:solution_stack]]. |
| - | The lowest level of the Framework covers the highest layer of the [[dido:public:ra:xapend:xapend.a_glossary:o:osi]], the [[dido:public:ra:xapend:xapend.a_glossary:p:applayer]] and includes: | + | The lowest level of the Framework covers the highest layer of the [[dido:public:ra:xapend:xapend.a_glossary:o:osi]], the [[dido:public:ra:xapend:xapend.a_glossary:a:applayer]] and includes: |
| * [[dido:public:ra:xapend:xapend.a_glossary:d:dds]] | * [[dido:public:ra:xapend:xapend.a_glossary:d:dds]] | ||
| Line 79: | Line 79: | ||
| </WRAP>| | </WRAP>| | ||
| ^ Transport | <WRAP> | ^ Transport | <WRAP> | ||
| - | There are two levels to the **Transport Level**. The transport mechanisims for messages and for connectivity: | + | There are two levels to the **Transport Level**: one for message transport mechanisms and one purely for connectivity: |
| - | * The **Message Transport Level** which is analogous to the the [[dido:public:ra:xapend:xapend.a_glossary:o:osi]] [[dido:public:ra:xapend:xapend.a_glossary:p:presentlayer]] and includes the following messaging systems: | + | * The **Message Transport Level** is analogous to the [[dido:public:ra:xapend:xapend.a_glossary:o:osi]] [[dido:public:ra:xapend:xapend.a_glossary:p:presentlayer]] and includes the following messaging systems: |
| * [[dido:public:ra:xapend:xapend.b_stds:tech:omg:dds_rtps | DDSI-RTPS]] | * [[dido:public:ra:xapend:xapend.b_stds:tech:omg:dds_rtps | DDSI-RTPS]] | ||
| * [[dido:public:ra:xapend:xapend.a_glossary:c:coap]] | * [[dido:public:ra:xapend:xapend.a_glossary:c:coap]] | ||
| Line 95: | Line 95: | ||
| * [[dido:public:ra:xapend:xapend.a_glossary:k:kademlia]] | * [[dido:public:ra:xapend:xapend.a_glossary:k:kademlia]] | ||
| - | * The **Connectivity** which is analogous to the [[dido:public:ra:xapend:xapend.a_glossary:o:osi]] [[dido:public:ra:xapend:xapend.a_glossary:s:netlayer]] and includes: | + | * The **Connectivity Level** is analogous to the [[dido:public:ra:xapend:xapend.a_glossary:o:osi]] [[dido:public:ra:xapend:xapend.a_glossary:s:netlayer]] and includes: |
| * [[dido:public:ra:xapend:xapend.a_glossary:t:tcp]] | * [[dido:public:ra:xapend:xapend.a_glossary:t:tcp]] | ||
| * [[dido:public:ra:xapend:xapend.a_glossary:u:udp]] | * [[dido:public:ra:xapend:xapend.a_glossary:u:udp]] | ||
| Line 101: | Line 101: | ||
| </WRAP>| | </WRAP>| | ||
| ^ Network | <WRAP> | ^ Network | <WRAP> | ||
| - | The **Network Level** is analogous to the [[dido:public:ra:xapend:xapend.a_glossary:o:osi]] [[dido:public:ra:xapend:xapend.a_glossary:s:sessionlayer]] providing data routing paths for network communication. Data is transferred in the form of packets via logical network paths in an ordered format controlled by the network layer. Logical connection setup, data forwarding, routing and delivery error reporting are the Network Layer’s primary responsibilities. | + | The **Network Level** is analogous to the [[dido:public:ra:xapend:xapend.a_glossary:o:osi]] [[dido:public:ra:xapend:xapend.a_glossary:s:sessionlayer]] providing data routing paths for network communication. Data is transferred in the form of packets via logical network paths in an ordered format controlled by the network layer. Logical connection setup, data forwarding, routing, and delivery error reporting are the Network Layer’s primary responsibilities. |
| This layer includes: | This layer includes: | ||
| Line 110: | Line 110: | ||
| </WRAP>| | </WRAP>| | ||
| ^ Link | <WRAP> | ^ Link | <WRAP> | ||
| - | The **Link Level** is analgous to the [[dido:public:ra:xapend:xapend.a_glossary:o:osi]] [[dido:public:ra:xapend:xapend.a_glossary:d:datalinklayer]] controling connections between multiple computers. The session layer tracks the dialogs between computers, which are also called sessions. This layer establishes, controls and ends the sessions between local and remote applications. | + | The **Link Level** is analogous to the [[dido:public:ra:xapend:xapend.a_glossary:o:osi]] [[dido:public:ra:xapend:xapend.a_glossary:d:datalinklayer]] controlling connections between multiple computers. The session layer tracks the dialogs between computers, which are also called sessions. This layer establishes, controls and ends the sessions between local and remote applications. |
| </WRAP>| | </WRAP>| | ||
| ^ Physical | <WRAP> | ^ Physical | <WRAP> | ||
| Line 134: | Line 134: | ||
| ==== Discussion ==== | ==== Discussion ==== | ||
| - | An alternate way to view the Stack is to use the [[dido:public:ra:xapend:xapend.a_glossary:t:tcp_concept_model]]. Figure {{ref>tcpconceptModel}} grphically represent the TCP/IP Conceptial Model. | + | An alternate way to view the Stack is to use the [[dido:public:ra:xapend:xapend.a_glossary:t:tcp_concept_model]]. Figure {{ref>tcpconceptModel}} graphically represents the TCP/IP Conceptual Model. |
| <figure tcpconceptModel> | <figure tcpconceptModel> | ||
| Line 141: | Line 141: | ||
| </figure> | </figure> | ||
| - | Most of the **DIDO Platforms** in combination with the **Frameworks** and **Application Layer** provide a [[dido:public:ra:1.4_req:2_nonfunc:20_maintainability:reuseability | Reusable]], general mechanism for [[dido:public:ra:xapend:xapend.a_glossary:d:dapp | Dapps]] to interact with oither DIDO [[dido:public:ra:xapend:xapend.a_glossary:n:node | Nodes]] in a [[dido:public:ra:xapend:xapend.a_glossary:n:node_network]]. However, this combination of **Platforms**, **Frameworks**, and **Applications** create **DIDO [[dido:public:ra:xapend:xapend.a_glossary:s:silo | Silos]]** creating isolation and offering little to no [[dido:public:ra:xapend:xapend.a_glossary:i:interoperability]] between the silos inhibiting [[dido:public:ra:xapend:xapend.a_glossary:i:interoperability]]. | + | Most of the **DIDO Platforms**, in combination with the **Frameworks** and **Application Layer**, provide a [[dido:public:ra:1.4_req:2_nonfunc:20_maintainability:reuseability | Reusable]], general mechanism for [[dido:public:ra:xapend:xapend.a_glossary:d:dapp | Dapps]] to interact with oither DIDO [[dido:public:ra:xapend:xapend.a_glossary:n:node | Nodes]] in a [[dido:public:ra:xapend:xapend.a_glossary:n:node_network]]. However, this combination of **Platforms**, **Frameworks**, and **Applications** create **DIDO [[dido:public:ra:xapend:xapend.a_glossary:s:silo | Silos]]** thereby inhibiting [[dido:public:ra:xapend:xapend.a_glossary:i:interoperability]] between the silos. |
| - | [[dido:public:ra:xapend:xapend.a_glossary:b:bridge | Bridges]] can be built between the Silos. However, the existing DIDO Platforms have no incentive to design or implement **Bridges**, in fact, they have a deinsentive as the purveyor of competitive DIDO Platforms. Many of the DIDO Platform [[dido:public:ra:xapend:xapend.a_glossary:a:api | Application Programming Interfaces (APIs)]] are poorly documented and hide behind a curtain of [[dido:public:ra:xapend:xapend.a_glossary:o:oss]] as standards. | + | [[dido:public:ra:xapend:xapend.a_glossary:b:bridge | Bridges]] can be built between the Silos. However, existing DIDO Platforms have no incentive to design or implement **Bridges**. In fact, as the purveyor of competitive DIDO Platforms, they have a distinct disincentive. Many of the DIDO Platform [[dido:public:ra:xapend:xapend.a_glossary:a:api | Application Programming Interfaces (APIs)]] are also poorly documented and hide behind a curtain of [[dido:public:ra:xapend:xapend.a_glossary:o:oss]] as standards. |
| - | The Interoperability issues between the various platforms silos csan be traced to the lowest level of the DIDO Platform, or depending on the perspective, the upper level of the [[dido:public:ra:xapend:xapend.a_glossary:o:osi]] [[dido:public:ra:xapend:xapend.a_glossary:p:presentlayer]]. For example, the selection of a **Framework**, narrows the Interoperability options to those DIDO Platforms that have selected the same **Framework**. The same can be said of the messaging systems defined in **''Transport->Message Transport Level''**. | + | The Interoperability issues between the various platforms silos can be traced to the lowest level of the DIDO Platform, or depending on the perspective, the upper level of the [[dido:public:ra:xapend:xapend.a_glossary:o:osi]] [[dido:public:ra:xapend:xapend.a_glossary:p:presentlayer]]. For example, the selection of a **Framework** narrows the Interoperability options to those DIDO Platforms that have selected the same **Framework**. The same can be said of the messaging systems defined in **''Transport --> Message Transport Level''**. Messages are at the core of DIDO Platforms. |
| + | |||
| + | <color blue><todo @char #char:2022-03-17>New section - review </todo></color> | ||
| /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
dido/public/ra/1.2_views/3_taxonomic/4_data_tax/02_state_taxonomy/data_in_motion.1642452915.txt.gz · Last modified: 2022/01/17 15:55 by nick
