[rfc-dist] RFC 8578 on Deterministic Networking Use Cases

rfc-editor@rfc-editor.org Fri, 10 May 2019 19:31 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 8F66C1200C1 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 10 May 2019 12:31:50 -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 YIB1RGoRi6Sv for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 10 May 2019 12:31:49 -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 7AE8912006D for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 10 May 2019 12:31:49 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 69651B80E06; Fri, 10 May 2019 12:31:41 -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 7044FB80E04; Fri, 10 May 2019 12:31:40 -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: <20190510193140.7044FB80E04@rfc-editor.org>
Date: Fri, 10 May 2019 12:31:40 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8578_on_Deterministic_Networking_Use_Ca?= =?utf-8?q?ses?=
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 8578

        Title:      Deterministic Networking Use Cases 
        Author:     E. Grossman, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       May 2019
        Mailbox:    ethan.grossman@dolby.com
        Pages:      97
        Characters: 227904
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-detnet-use-cases-20.txt

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

        DOI:        10.17487/RFC8578

This document presents use cases for diverse industries that have in
common a need for "deterministic flows".  "Deterministic" in this
context means that such flows provide guaranteed bandwidth, bounded
latency, and other properties germane to the transport of
time-sensitive data.  These use cases differ notably in their network
topologies and specific desired behavior, providing as a group broad
industry context for Deterministic Networking (DetNet).  For each use
case, this document will identify the use case, identify
representative solutions used today, and describe potential
improvements that DetNet can enable.

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


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