NET-004 — Configure Communication Behavior

Go to C.3.4 Virtual Network and Communication Requirements

NET-004 is a non-leaf requirement group governing configuration of communication behavior within a Virtual Network.

Communication behavior may be governed by Communication Characteristics, Communication Protocols, and Quality of Service controls.

A Communication Characteristic describes an aspect of information exchange that may be measured, constrained, configured, or reproduced. Latency is one such characteristic.

A Communication Protocol specifies the rules and conventions governing information exchange between communicating entities.

Internet Quality of Service (Internet QoS) describes the quality of packet delivery provided by an Internet Protocol network using measurable or controlled network communication characteristics.

A Communication Parameter specifies a value, condition, or constraint governing a Communication Characteristic or other configurable aspect of communication.

Communication behavior remains distinct from the Network Topology defined under NET-002. Network Topology establishes communication relationships among participating entities. NET-004 governs characteristics, protocols, and service behavior associated with communication across those relationships.

Conformance is assessed against the individual leaf requirements listed below. NET-004 does not establish a separate conformance obligation.

Requirements

Requirement ID	Requirement Title	Purpose
NET-004a	Configure Communication Latency	Configure the Latency specified for communication through a Virtual Network.
NET-004b	Configure Communication Protocol	Configure the Communication Protocol specified for communication through a Virtual Network.
NET-004c	Configure Internet Quality of Service	Configure the Internet QoS characteristics specified for communication through a Virtual Network.

Contents

Source

, representation and configuration of distance, latency, and communication protocols within Virtual Networks[DTE2] Non-Traditional BAA Submission, Virtual Networks and Communication[DTE9] Distributed Immutable Data Object Reference Architecture (DIDO-RA), distributed communication and Quality of Service concepts

Rationale

Distributed-system behavior may depend upon multiple independently configurable aspects of communication among participating Nodes and other communicating entities.

A Virtual Network therefore requires the ability to represent communication behavior specified for a test independently of the physical communication infrastructure used to realize the network.

The source material explicitly identifies Latency and Communication Protocols as configurable aspects of a Virtual Network. The DIDO Reference Architecture additionally provides Quality of Service concepts relevant to distributed communication.

Latency, Communication Protocol, and Internet QoS are independently configurable and independently verifiable. NET-004 therefore decomposes them into separate leaf requirements rather than combining them into a single normative Statement.

A Communication Characteristic identifies an aspect of communication being described or controlled. A Communication Parameter provides a value, condition, or constraint governing a configurable aspect of communication.

The requirement group remains implementation-neutral. It does not require DDS, a particular network emulator, software-defined networking, middleware, or another specific communication technology.

Applies To

Traceability

ConOps Relationship

This requirement group governs configuration of communication behavior associated with communication through a Virtual Network.

NET-001 establishes the Virtual Network, NET-002 defines its Network Topology, and NET-003 connects participating Nodes through that network.

The subordinate NET-004 requirements independently configure Latency, Communication Protocol, and Internet QoS without prescribing the implementation mechanism used to realize them.

Delivery Phase

TBD

Requirement Status

Draft

Notes for Editors

NET-004 is a non-leaf requirement group and does not contain an independent normative Statement or Verification section.

The explicit child links under Contents remain while the subordinate requirement pages are being created and reviewed. After all child pages exist, you may remove the explicit links because the indexmenu automatically discovers them.

Add subordinate communication-behavior requirements only when the source material or an approved architectural derivation establishes an independently verifiable obligation.

Do not treat Communication Protocol as a subtype of Communication Characteristic. A Communication Protocol specifies rules governing information exchange, while a Communication Characteristic describes an aspect of that exchange.

Do not infer packet loss, jitter, bandwidth limitations, routing behavior, or other specific Communication Characteristics solely from references to Degraded Communication Conditions or contested communication conditions.

NET-004 governs configuration of communication behavior. NET-005 separately governs reproduction of Degraded Communication Conditions.

Do not prescribe DDS, a network emulator, software-defined networking, a cloud networking service, or another particular implementation technology in subordinate requirement Statements unless an authoritative source requires that technology.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.