[rfc-dist] RFC 8655 on Deterministic Networking Architecture

rfc-editor@rfc-editor.org Thu, 24 October 2019 18:00 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BFA51200E6 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 24 Oct 2019 11:00:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8aq-r-IlFUSj for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 24 Oct 2019 11:00:11 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04AB31200E3 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 24 Oct 2019 11:00:11 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 22745F40704; Thu, 24 Oct 2019 11:00:05 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 74698F406F2; Thu, 24 Oct 2019 11:00:03 -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
Message-Id: <20191024180003.74698F406F2@rfc-editor.org>
Date: Thu, 24 Oct 2019 11:00:03 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8655_on_Deterministic_Networking_Archit?= =?utf-8?q?ecture?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, detnet@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8655

        Title:      Deterministic Networking Architecture 
        Author:     N. Finn, 
                    P. Thubert,
                    B. Varga, 
                    J. Farkas
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2019
        Mailbox:    nfinn@nfinnconsulting.com, 
                    pthubert@cisco.com, 
                    balazs.a.varga@ericsson.com,
                    janos.farkas@ericsson.com
        Pages:      38
        Characters: 
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-detnet-architecture-13.txt

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

        DOI:        10.17487/RFC8655

This document provides the overall architecture for Deterministic
Networking (DetNet), which provides a capability to carry specified
unicast or multicast data flows for real-time applications with
extremely low data loss rates and bounded latency within a network
domain.  Techniques used include 1) reserving data-plane resources
for individual (or aggregated) DetNet flows in some or all of the
intermediate nodes along the path of the flow, 2) providing explicit
routes for DetNet flows that do not immediately change with the
network topology, and 3) distributing data from DetNet flow packets
over time and/or space to ensure delivery of each packet's data in
spite of the loss of a path.  DetNet operates at the IP layer and
delivers service over lower-layer technologies such as MPLS and Time-
Sensitive Networking (TSN) as defined by IEEE 802.1.

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org