Re: [Detnet] Traffic description in DetNet flow info model

John Grant <j@ninetiles.com> Thu, 20 April 2017 09:27 UTC

Return-Path: <j@ninetiles.com>
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 D709112EBC1 for <detnet@ietfa.amsl.com>; Thu, 20 Apr 2017 02:27:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5] 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 E1D0GXkAdsxb for <detnet@ietfa.amsl.com>; Thu, 20 Apr 2017 02:27:05 -0700 (PDT)
Received: from know-smtprelay-omc-10.server.virginmedia.net (know-smtprelay-omc-10.server.virginmedia.net [80.0.253.74]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD08912EBBF for <detnet@ietf.org>; Thu, 20 Apr 2017 02:27:03 -0700 (PDT)
Received: from [192.168.4.61] ([82.21.85.55]) by know-smtprelay-10-imp with bizsmtp id AZT01v00W1BdnUJ01ZT1kJ; Thu, 20 Apr 2017 10:27:01 +0100
X-Originating-IP: [82.21.85.55]
X-Authenticated-User: X-Spam: 0
X-Authority: v=2.1 cv=DPhymH5b c=1 sm=1 tr=0 a=JBiNpTwF/IB2dYUHhn0UHw==:117 a=JBiNpTwF/IB2dYUHhn0UHw==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=-O5YPv7yAAAA:8 a=le6d79QuAAAA:8 a=48vgC7mUAAAA:8 a=WmfpMMCmeeax00oqlN0A:9 a=pILNOxqGKmIA:10 a=ns13WE7amoM8ChYu:21 a=_W_S_7VecoQA:10 a=TLqBRRHTddABEfEY9lce:22 a=QbAMNLWdp4a7deKPGBBn:22 a=w1C3t2QeGrPiZgrLijVG:22
From: John Grant <j@ninetiles.com>
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary="Apple-Mail-17--1022854616"
Date: Thu, 20 Apr 2017 10:27:00 +0100
In-Reply-To: <E78F7186ADD5404AB48E27F02660CA07806C9BDC@dggemm508-mbs.china.huawei.com>
To: DetNet WG <detnet@ietf.org>
References: <E78F7186ADD5404AB48E27F02660CA07806C9BDC@dggemm508-mbs.china.huawei.com>
Message-Id: <3B18D368-5822-4007-88F8-A02C875D7BAE@ninetiles.com>
X-Mailer: Apple Mail (2.1085)
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/1J1qP-8pVF2JqVPtqzMh4IQCU-g>
Subject: Re: [Detnet] Traffic description in DetNet flow info model
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 20 Apr 2017 09:27:08 -0000

As pointed out in 4.1.2, for a VBR flow you have to make a reservation for the peak rate, and there isn't any reason to do anything other than use the service that is already defined for CBR. With circuit-switched systems any part of the reservation that wasn't used was wasted, but in packet-based systems it can be used for best-effort traffic, as stated in 4.3.2.

Regarding synchronous flows, the first paragraph of 4.3.2 explains that if the reservations on incoming and outgoing links are time-aligned then the latency, and hence the amount of buffer space required, can be minimised. The details mechanism for achieving that would, I think, be out of scope for an architecture document.

For a description of a system that implements synchronous flows, see clause 5 of ETSI GR NGP 003, available from the "specifications" tab at http://www.etsi.org/technologies-clusters/technologies/next-generation-protocols

John Grant
Nine Tiles, Cambridge, England
+44 1223 862599 and +44 1223 511455
http://www.ninetiles.com

On 20 Apr 2017, at 08:38, zhayiyong wrote:

> Hi All,
>  
> Recently we have some discussion among authors of the two flow info model draft. The DetNet flow info model should provide some common concepts and description of the flow. One part is traffic specification of the flow. Here is something not clear, is DetNet dealing with VBR flows and what attributes are needed? And how to deal with VBR flow, for source guarantee purpose, do we need to define shaping parameters?
>  
> In architecture draft, section 4.1.2, “The traffic characteristics of an App-flow can be CBR (constant bit rate) or VBR (variable bit rate)”. In section 4.3.2, mentions synchronous flow and asynchronous flow, but no details of that.
> In use case draft, for some cases such as industrial and BAS, it can assumes that the traffic is periodic with constant rate. For cases such as Cellular Radio and M2M, there is usually no assumption on the traffic. E.g., CoMP traffic is between two eNBs, it is hard to say the flow is constant rate.
>  
> Cheers,
> Yiyong
> _______________________________________________
> detnet mailing list
> detnet@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet