[Detnet] RFC 9055 on Deterministic Networking (DetNet) Security Considerations

rfc-editor@rfc-editor.org Fri, 25 June 2021 23:40 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: detnet@ietfa.amsl.com
Delivered-To: detnet@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 732AF3A1203; Fri, 25 Jun 2021 16:40:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 9C4NtYKAqFGh; Fri, 25 Jun 2021 16:40:37 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FE6F3A1204; Fri, 25 Jun 2021 16:40:33 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 38710F40729; Fri, 25 Jun 2021 16:40:23 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, detnet@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210625234023.38710F40729@rfc-editor.org>
Date: Fri, 25 Jun 2021 16:40:23 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/71KuGmp92ddHdN_hveVMWtm_368>
Subject: [Detnet] =?utf-8?q?RFC_9055_on_Deterministic_Networking_=28DetNe?= =?utf-8?q?t=29_Security_Considerations?=
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:detnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet/>
List-Post: <mailto:detnet@ietf.org>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet>, <mailto:detnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jun 2021 23:40:44 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 9055

        Title:      Deterministic Networking (DetNet) 
                    Security Considerations 
        Author:     E. Grossman, Ed.,
                    T. Mizrahi,
                    A. Hacker
        Status:     Informational
        Stream:     IETF
        Date:       June 2021
        Mailbox:    ethan@ieee.org,
        Pages:      50
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-detnet-security-16.txt

        URL:        https://www.rfc-editor.org/info/rfc9055

        DOI:        10.17487/RFC9055

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.

This document is a product of the Deterministic Networking Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC