[rfc-dist] RFC 9550 on Deterministic Networking (DetNet): Packet Ordering Function

rfc-editor@rfc-editor.org Thu, 21 March 2024 03:36 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABE96C14F71E; Wed, 20 Mar 2024 20:36:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.958
X-Spam-Level:
X-Spam-Status: No, score=-3.958 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jDLLd9SKkMCY; Wed, 20 Mar 2024 20:36:27 -0700 (PDT)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32B92C14F706; Wed, 20 Mar 2024 20:36:27 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 19CBF5BEC3F; Wed, 20 Mar 2024 20:36:27 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20240321033627.19CBF5BEC3F@rfcpa.amsl.com>
Date: Wed, 20 Mar 2024 20:36:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/AIEaR63xUsOFiLPAIkubpiNDViI>
Subject: [rfc-dist] RFC 9550 on Deterministic Networking (DetNet): Packet Ordering Function
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2024 03:36:27 -0000

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

        
        RFC 9550

        Title:      Deterministic Networking (DetNet): Packet Ordering 
                    Function 
        Author:     B. Varga, Ed.,
                    J. Farkas,
                    S. Kehrer,
                    T. Heer
        Status:     Informational
        Stream:     IETF
        Date:       March 2024
        Mailbox:    balazs.a.varga@ericsson.com,
                    janos.farkas@ericsson.com,
                    stephan.kehrer@belden.com,
                    tobias.heer@belden.com
        Pages:      11
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-detnet-pof-11.txt

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

        DOI:        10.17487/RFC9550

The replication and elimination functions of the Deterministic
Networking (DetNet) architecture can result in out-of-order packets,
which is not acceptable for some time-sensitive applications. The
Packet Ordering Function (POF) algorithms described in this document
enable restoration of the correct packet order when the replication
and elimination functions are used in DetNet networks.  The POF only
provides ordering within the latency bound of a DetNet flow; it does
not provide any additional reliability.

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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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