communication protocol
Let an agent handle communication protocols by layer, specification, versions, implementations and security.
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.
written by Claude from model knowledge without web access - no source was read, every claim is a lead to verify
Researched by: Claude
Purpose and description
Let an agent handle communication protocols by layer, specification, versions, implementations and security.
A set of rules and formats governing how data is exchanged between devices, programs or systems, such as TCP/IP, HTTP, USB, Bluetooth, XMPP and OGC web services; specified in technical standards.
What it is for: Interoperable communication between systems.
It can be identify the protocol and version; find the authoritative specification; check security properties; debug interoperability issues.
Distinguishing features
Defines message formats and rules
Layered
Versioned and standardised
Security varies
What it looks like
Not physical; defined in specifications and seen in network traffic.
How it is recognised
Names such as HTTP, TCP, MQTT
RFCs and standards documents
Diplomatic protocol is a different sense
Related models
is a kind of - category
is specified by - bodies
is implemented in - implementation
is confused with - another sense
In practice
Families and kinds
network protocols
application protocols
hardware interface protocols
messaging protocols
geospatial web service protocols
Identifiers
RFC number IETF document number specifications
Standards and regulation
IETF RFCs
IEEE 802 standards
EU Cyber Resilience Act for products
Failure modes and hazards
Using insecure or deprecated protocols
Misreading the specification version
Also called
+29
Where this came from
wikidata · CC0 1.0
Drafted structure
Bundle to layer to finding to question, as the second pass will find it: 4 bundles · 8 layers · 8 findings · 16 questions.
Identity Which protocol.
Specifications define protocols.
Name
Protocol and version.
Name
Protocol identity.
- Which protocol and version is meant? definition
- Which layer does it operate at? definition
Specification
Authoritative document.
Specification
Specification.
- Which document is the authoritative specification? provenance
- Has it been updated or obsoleted? provenance
Security Safety.
Security must be checked.
Properties
Encryption.
Properties
Security properties.
- Does the protocol provide encryption and authentication? definition
- Which versions are deprecated for security reasons? provenance
Vulnerabilities
Advisories.
Vulnerabilities
Vulnerabilities.
- Are there known vulnerabilities in this implementation? provenance
- Which advisory lists them? provenance
Implementation Using it.
Implementations vary.
Libraries
Software.
Libraries
Implementations.
- Which maintained libraries implement it? provenance
- Are they conformant? boundary
Debug
Troubleshooting.
Debug
Troubleshooting.
- How can interoperability problems be diagnosed? action
- Which tools inspect the traffic? provenance
Senses Disambiguation.
Protocol has other senses.
Diplomatic
Etiquette.
Diplomatic
Diplomatic sense.
- Is diplomatic protocol meant? boundary
- Which entry fits? action
Medical
Clinical protocol.
Medical
Medical sense.
- Is a clinical or research protocol meant? boundary
- Which entry fits? action
What the second pass must settle
- Should each protocol be a separate entry?
- How should specifications be linked?
- How should security status be tracked?