RFC 9055: Deterministic Networking (DetNet) Security Considerations
In plain English — editorial summary, not part of the RFC
A DetNet (deterministic network) provides specific performance guarantees to its data flows, such as extremely low data loss rates and bounded latency (including bounded latency variation, i.e., "jitter"). As a result, securing a DetNet requires that in addition to the best practice security measures taken for any mission-critical network, additional security measures may be needed to secure the intended operation of these novel service properties. This document addresses DetNet-specific security considerations from the perspectives of both the DetNet system-level designer and component designer. System considerations include a taxonomy of relevant threats and attacks, and associations of threats versus use cases and service properties. Component-level considerations include ingress filtering and packet arrival-time violation detection. This document also addresses security considerations specific to the IP and MPLS data plane technologies, thereby complementing the Security Considerations sections of those documents.
Document record
- Document ID
- RFC9055
- Published
- June 2021
- Authors
- E. Grossman; T. Mizrahi; A. Hacker
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 50
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9016Flow and Service Information Model for Deterministic Networking (DetNet)Current
March 2021
- RFC 9145Integrity Protection for the Network Service Header (NSH) and Encryption of Sensitive Context HeadersCurrent
December 2021
- RFC 8964Deterministic Networking (DetNet) Data Plane: MPLSCurrent
January 2021
- RFC 9305Locator/ID Separation Protocol (LISP) Generic Protocol ExtensionCurrent
October 2022
- RFC 9320Deterministic Networking (DetNet) Bounded LatencyCurrent
November 2022
- RFC 9467Relaxed Packet Counter Verification for Babel MAC AuthenticationCurrent
January 2024
- RFC 8578Deterministic Networking Use CasesCurrent
May 2019
- RFC 9546Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet) with the MPLS Data PlaneCurrent
February 2024
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?