Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

INFORMATIONAL

Authors:

E. Grossman, Ed.
T. Mizrahi
A. Hacker

Stream:

IETF

Source:

detnet (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9055

Discuss this RFC: Send questions or comments to the mailing listdetnet@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 9055

Abstract

A DetNet (deterministic network) provides specific performanceguarantees to its data flows, such as extremely low data loss ratesand bounded latency (including bounded latency variation, i.e.,"jitter"). As a result, securing a DetNet requires that in additionto the best practice security measures taken for any mission-criticalnetwork, additional security measures may be needed to secure theintended operation of these novel service properties.

This document addresses DetNet-specific security considerations fromthe perspectives of both the DetNet system-level designer andcomponent designer. System considerations include a taxonomy ofrelevant threats and attacks, and associations of threats versus usecases and service properties. Component-level considerations includeingress filtering and packet arrival-time violation detection.

This document also addresses security considerations specific to theIP and MPLS data plane technologies, thereby complementing theSecurity Considerations sections of those documents.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.