RFC 9550: Deterministic Networking (DetNet): Packet Ordering Function
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9550
- Published
- March 2024
- Authors
- B. Varga; J. Farkas; S. Kehrer; T. Heer
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 11
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9551Framework of Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet)Current
March 2024
- RFC 9552Distribution of Link-State and Traffic Engineering Information Using BGPCurrent
December 2023
- RFC 9546Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet) with the MPLS Data PlaneCurrent
February 2024
- RFC 9545Path Segment Identifier in MPLS-Based Segment Routing NetworksCurrent
February 2024
- RFC 9543A Framework for Network Slices in Networks Built from IETF TechnologiesCurrent
March 2024
- RFC 9541Flush Mechanism for Customer MAC Addresses Based on Service Instance Identifier (I-SID) in Provider Backbone Bridging EVPN (PBB-EVPN)Current
March 2024
- RFC 9566Deterministic Networking (DetNet) Packet Replication, Elimination, and Ordering Functions (PREOF) via MPLS over UDP/IPCurrent
April 2024
- RFC 9568Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6Current
April 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?