[Detnet] RFC 9016 on Flow and Service Information Model for Deterministic Networking (DetNet)

rfc-editor@rfc-editor.org Wed, 31 March 2021 00:01 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: detnet@ietfa.amsl.com
Delivered-To: detnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D097F3A091F; Tue, 30 Mar 2021 17:01:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 qkCgeClUnlW2; Tue, 30 Mar 2021 17:01:52 -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 0EB833A0931; Tue, 30 Mar 2021 17:01:51 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id DF7BBF407E1; Tue, 30 Mar 2021 17:01:49 -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: <20210331000149.DF7BBF407E1@rfc-editor.org>
Date: Tue, 30 Mar 2021 17:01:49 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/C31i3itMhpF-61FAwNJ6cNGjKMs>
Subject: [Detnet] =?utf-8?q?RFC_9016_on_Flow_and_Service_Information_Mode?= =?utf-8?q?l_for_Deterministic_Networking_=28DetNet=29?=
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: Wed, 31 Mar 2021 00:01:57 -0000

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

        
        RFC 9016

        Title:      Flow and Service Information Model 
                    for Deterministic Networking (DetNet) 
        Author:     B. Varga,
                    J. Farkas,
                    R. Cummings,
                    Y. Jiang,
                    D. Fedyk
        Status:     Informational
        Stream:     IETF
        Date:       March 2021
        Mailbox:    balazs.a.varga@ericsson.com,
                    janos.farkas@ericsson.com,
                    rodney.cummings@ni.com,
                    jiangyuanlong@huawei.com,
                    dfedyk@labn.net
        Pages:      20
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-detnet-flow-information-model-14.txt

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

        DOI:        10.17487/RFC9016

This document describes the flow and service information model for
Deterministic Networking (DetNet). These models are defined for IP
and MPLS DetNet data planes.

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