network interface controller
Enable an agent to recognise a network interface controller, assess its connectivity and operating state, and determine compatible and authorised configuration, use and maintenance actions.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
recalled by Codex without web access - no source was read
Researched by: Codex
Purpose and description
Enable an agent to recognise a network interface controller, assess its connectivity and operating state, and determine compatible and authorised configuration, use and maintenance actions.
A network interface controller is a hardware component that connects a host system to a network by implementing network-medium access and exchanging network data with the host through a hardware interface and device driver.
It can be Identify the controller and map its physical interfaces to host-visible devices.; Check compatibility among the host attachment, driver, firmware, network medium and intended peer.; Configure supported link modes, queues, frame limits and offloads within an authorised operating policy.; Observe link transitions and traffic counters to investigate connectivity or packet-transfer faults.; Assign supported hardware resources to workloads while checking isolation and ownership.; Plan a supported reset, firmware update or replacement with its connectivity impact recorded..
Distinguishing features
Provides a hardware transmit and receive path between a host and a network, rather than merely naming a software interface.
Exposes a host control or data interface alongside network-facing communication functions; a connector or passive adapter alone does not qualify.
Performs controller functions such as frame handling, buffering or host data transfer; a standalone physical-layer transceiver does not by itself establish this identity.
Acts as a host network attachment, even when it includes switching or programmable processing; a standalone switch or router requires a different primary model.
May be integrated into a motherboard or system-on-chip, so a removable expansion card is not a necessary recognition test.
Scope
+ Controller hardware implemented as an integrated circuit, board component or network adapter
+ Host attachment, device enumeration, driver and firmware dependencies
+ Network ports or radio interfaces, link capabilities and address handling
+ Transmit and receive queues, packet transfer and supported hardware offloads
+ Link state, performance limits, diagnostics, power management and recovery
- The host computer and its complete operating system or network stack
- Network cables, transceivers and antennas as independently managed components
- Switches, routers and access points acting as separate network infrastructure
- Virtual interfaces implemented entirely in software
- End-to-end network services, routing policy and application performance
- Product lines and individual asset histories as separate catalogue entities
Characteristics
- Implementation and integration
- Controller chip, motherboard-integrated controller, system-on-chip block, removable adapter Determines the physical boundary, replacement options and which supporting components are external.
- Host attachment
- Host bus or internal interconnect, supported generation, lane count and negotiated configuration where applicable Determines host compatibility and possible data-transfer bottlenecks.
- Network technology and media
- Supported network families, media, connectors or radio bands, with applicable specification revisions Determines which peers and physical connections can establish a link.
- Network interface count
- Number of physical ports or radio interfaces, distinguished from logical interfaces and host functions Prevents physical connectivity from being inferred from software interface counts.
- Link rate capabilities
- Supported and negotiated bit/s per interface, with direction and operating mode Constrains transfer capacity without equating link rate with application throughput.
- Frame size limits
- Bytes, stating whether the value describes a frame, payload or host MTU Supports compatible configuration and interpretation of size-related drops.
- Address identity
- Permanent and effective link-layer addresses where applicable, including assignment origin Supports interface recognition while accounting for address overrides and randomisation.
- Queue and offload capabilities
- Transmit and receive queue limits; supported checksum, segmentation, steering, timestamping or other accelerations Determines which host workloads and configurations the hardware can support.
- Software compatibility
- Controller revision linked to driver, firmware, operating system and supported feature combinations Separates hardware capability from functionality available in the installed environment.
- Operational state
- Enumeration, administrative enablement, link state, negotiated mode, power state and fault indicators recorded separately Distinguishes a disabled or sleeping controller from a failed device or disconnected link.
- Traffic and error counters
- Packets, bytes, drops and errors over a stated interval, with counter definitions and reset history Supports diagnosis without confusing accumulated history with current faults.
- Power and thermal envelope
- W and °C, qualified by operating mode, measurement location and manufacturer limits Constrains installation, sustained operation and power-saving choices.
Also called
Where this came from
wikidata · CC0 1.0
Drafted structure
Bundle to layer to finding to question, as the second pass will find it: 6 bundles · 11 layers · 19 findings · 29 questions.
Controller boundary Establish what hardware constitutes the controller and how it appears to the host.
A chip, adapter, port and operating-system interface are related but cannot be treated as interchangeable identities.
Hardware composition
Locate controller functions and their supporting physical components.
Controller function boundary
Record which host-transfer, frame-processing and physical-interface functions lie inside the modelled hardware boundary.
- Which components perform host data transfer and network frame handling? definition
- Are the physical-layer device, transceiver, antenna and connector integrated or separately managed? boundary
Host device mapping
Relate physical hardware to enumerated devices and logical interfaces.
Identity and enumeration
Capture evidence connecting controller identity, hardware revision, host functions and network interfaces.
- Which hardware identifiers and manufacturer records establish the controller and revision? provenance
- How do physical ports or radios map to host functions and operating-system interfaces? boundary
Network link Describe compatible network attachments and the conditions for establishing a usable link.
A controller can be recognised by the host yet remain unable to communicate with the attached medium or peer.
Media and protocols
Define the supported network technologies and physical connection requirements.
Attachment compatibility
Record supported network specifications and the components required to realise each attachment.
- Which network specifications, revisions and issuing bodies are explicitly supported by authoritative documentation? provenance
- Which media, transceivers or antennas are required, and what compatibility limits apply? boundary
Link establishment
Separate supported link modes from configured and currently established modes.
Negotiation and link state
Record the evidence and prerequisites for a link, including technology-specific negotiation or association.
- What rate, duplex or radio mode is currently established, and which status evidence supports it? measurement
- Which controller settings and peer conditions must be satisfied to establish or restore the link? action
Host packet path Describe packet movement between host memory and network interfaces.
Host interconnects, queues and acceleration features determine usable capacity and explain faults that link status alone cannot reveal.
Transfer and buffering
Capture host transfer mechanisms, queues and packet-size constraints.
Data path capacity
Record constraints that can limit packet transfer independently of nominal network rate.
- What host interconnect configuration, queue counts and buffer limits are supported and currently active? measurement
- What frame or payload sizes are accepted, and how are oversize frames and exhausted buffers handled? definition
Hardware acceleration
Describe optional packet-processing work performed by the controller.
Offload availability
Distinguish advertised hardware features from features exposed and enabled by the installed software.
- Which offloads, receive-steering functions and timestamping capabilities are documented for this revision? provenance
- Which features can be enabled for the intended workload, and what dependencies or incompatibilities constrain them? action
Control and isolation Describe configuration authority, address handling and separation of controller resources.
Controller settings affect traffic visibility, host access and workload separation, especially when hardware is shared or assigned directly.
Addressing and filtering
Capture interface identities and hardware decisions about accepted or classified traffic.
Effective receive policy
Record effective link-layer addresses and supported receive filters without assuming they provide complete network security.
- Which addresses are permanent, assigned or overridden, and which are effective now? provenance
- Who may change address, multicast, VLAN or promiscuous-mode settings, and what traffic exposure would change? action
Resource assignment
Describe ownership of host functions, queues and any virtualised hardware resources.
Sharing and memory access
Record supported sharing mechanisms and the platform controls required for safe direct hardware access.
- Can the controller expose independently assignable functions or queues, and which resources remain shared? boundary
- What platform isolation and access controls are required before assigning the controller or a function to a workload? action
Health and lifecycle Assess faults, operating limits and supported interventions across controller service life.
A down link, driver failure, power transition and hardware fault require different evidence and recovery actions.
Diagnostic evidence
Relate observable controller state and counters to plausible fault locations.
Fault localisation
Record symptoms and diagnostic evidence while separating controller faults from host, medium and peer faults.
- Which errors, drops, resets or link transitions occurred over the observation interval, and how are their counters defined? measurement
- Which supported diagnostics can distinguish controller, driver, cable or radio, and peer-side problems? action
Service and power transitions
Capture maintenance dependencies, operating limits and the effects of disruptive actions.
Supported recovery
Record evidence for supported power changes, resets, firmware updates and replacement procedures.
- Which power and temperature limits, driver-firmware combinations and recovery procedures are documented for the hardware revision? provenance
- What connectivity, shared-function and remote-management effects must be accounted for before sleep, reset, update or replacement? action
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Check these first
Recalled without web access and unsourced; every item is a lead to verify.
- Controller, adapter, and card are frequently used interchangeably; confirm whether the registry intends the controller chip or the complete hardware interface.
- Measurement ranges are illustrative recall, not researched market statistics; link rate differs from application throughput, and MTU is a configuration parameter.
- Applicable standards depend on the network medium and host interface; wireless capabilities and regulatory limits require product-specific verification.
- Which of these check these first hold for the sense of network interface controller this model covers, and on what evidence? provenance
Kinds and varieties
Recalled without web access and unsourced; every item is a lead to verify.
- Ethernet controller
- Wireless LAN controller
- Integrated motherboard network interface
- Expansion-card network interface
- USB network adapter
- SmartNIC with programmable processing or hardware offload
- Which of these kinds and varieties hold for the sense of network interface controller this model covers, and on what evidence? provenance
Identifiers and schemes
Recalled without web access and unsourced; every item is a lead to verify.
- IEEE EUI-48 / MAC address - 48 bits, commonly displayed as six hexadecimal octets - Commonly identifies an Ethernet or Wi-Fi interface; an assigned hardware address may be overridden or randomized, and one controller can expose multiple interfaces.
- PCI vendor and device identifiers - 16-bit vendor ID and 16-bit device ID - Identify PCI or PCI Express controller implementations for enumeration and driver matching, rather than individual physical units.
- USB vendor and product identifiers - 16-bit VID and 16-bit PID - Identify USB adapter implementations; they are not normally unique serial identifiers.
- Which of these identifiers and schemes hold for the sense of network interface controller this model covers, and on what evidence? provenance
Standards and regulation
Recalled without web access and unsourced; every item is a lead to verify.
- IEEE 802.3, issued by IEEE: Ethernet MAC and physical-layer specifications.
- IEEE 802.11, issued by IEEE: wireless LAN MAC and physical-layer specifications.
- PCI Express specifications, issued by PCI-SIG: host interconnection for applicable controllers.
- USB specifications, issued by the USB Implementers Forum: host interconnection for applicable adapters.
- Which of these standards and regulation hold for the sense of network interface controller this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Connecting desktop and laptop computers to wired or wireless local-area networks.
- Connecting servers to data-centre networks.
- Providing network connectivity for embedded systems and industrial equipment.
- Providing separate network ports for routing, firewalling, or traffic isolation.
- Offloading selected packet-processing operations from the host CPU.
- Which of these real-world use hold for the sense of network interface controller this model covers, and on what evidence? provenance
Typical measurements
Recalled without web access and unsourced; every item is a lead to verify.
- Nominal Ethernet link rate - 1-10 for many desktop and workstation interfaces; 10-400 for many server interfaces - Gbit/s
- Physical port count on Ethernet adapter cards - 1-4 - ports
- Common Ethernet IP maximum transmission unit - 1500 conventionally; approximately 9000 where jumbo frames are supported and configured - bytes
- Which of these typical measurements hold for the sense of network interface controller this model covers, and on what evidence? provenance
Failure modes and hazards
Recalled without web access and unsourced; every item is a lead to verify.
- Cable, connector, transceiver, or radio-link faults can cause link loss, packet errors, or intermittent connectivity.
- Driver or firmware defects can cause crashes, stalled transmit queues, or incorrect packet processing.
- Receive-buffer exhaustion or host-bus bottlenecks can cause packet drops and reduced throughput.
- Overheating, electrostatic discharge, or electrical surges can damage the controller or its ports.
- Vulnerable firmware or inadequately isolated direct memory access can expose the host to security compromise.
- Which of these failure modes and hazards hold for the sense of network interface controller this model covers, and on what evidence? provenance
Regional variation
Recalled without web access and unsourced; every item is a lead to verify.
- Wireless interfaces have country-dependent permitted channels, frequency bands, and transmit-power limits.
- Which of these regional variation hold for the sense of network interface controller this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Recalled without web access and unsourced; every item is a lead to verify.
- Network interface card - Strictly denotes a physical card containing a controller and supporting components; a controller can instead be integrated into a motherboard or chip, although the terms are often used interchangeably.
- Network transceiver - Converts between electrical, optical, or radio signals and a physical link; it does not by itself provide the controller's complete host-facing network interface.
- Network switch - Forwards traffic among network ports, whereas a controller primarily attaches a host to a network.
- Device driver - Is software that operates the controller, rather than the networking hardware itself.
- Virtual network interface - Is a software-visible interface that need not correspond to a dedicated physical controller.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of network interface controller this model covers, and on what evidence? provenance
What the second pass must settle
- Does the registry intend this entry to include wireless network controllers and modem-integrated network adapters, or are those owned by neighbouring entries?
- Where should the boundary fall between a network interface controller and a programmable SmartNIC or data processing unit with independent compute functions?
- Which existing Vercy models already own physical-layer transceivers, network adapters and virtual interfaces, and how should this entry link to them?
- Which authoritative specifications and manufacturer documents should establish technology-specific capabilities, diagnostics and operating limits?
- Should physical dimensions, replaceable components and certification evidence attach to the controller chip, complete adapter or both when those boundaries differ?