[Detnet] Traffic description in DetNet flow info model

zhayiyong <zhayiyong@huawei.com> Thu, 20 April 2017 07:40 UTC

Return-Path: <zhayiyong@huawei.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 9B74B129474 for <detnet@ietfa.amsl.com>; Thu, 20 Apr 2017 00:40:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level:
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 fO_X3xjJfwnv for <detnet@ietfa.amsl.com>; Thu, 20 Apr 2017 00:40:53 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA39612EB25 for <detnet@ietf.org>; Thu, 20 Apr 2017 00:40:47 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml702-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DLJ80336; Thu, 20 Apr 2017 07:40:45 +0000 (GMT)
Received: from DGGEMM401-HUB.china.huawei.com (10.3.20.209) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 20 Apr 2017 08:39:36 +0100
Received: from DGGEMM508-MBS.china.huawei.com ([169.254.4.204]) by DGGEMM401-HUB.china.huawei.com ([10.3.20.209]) with mapi id 14.03.0301.000; Thu, 20 Apr 2017 15:38:47 +0800
From: zhayiyong <zhayiyong@huawei.com>
To: DetNet WG <detnet@ietf.org>
Thread-Topic: Traffic description in DetNet flow info model
Thread-Index: AdK5qSSYqSHwGD/BTl6GOqTnuhSZHw==
Date: Thu, 20 Apr 2017 07:38:46 +0000
Message-ID: <E78F7186ADD5404AB48E27F02660CA07806C9BDC@dggemm508-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.15.96]
Content-Type: multipart/alternative; boundary="_000_E78F7186ADD5404AB48E27F02660CA07806C9BDCdggemm508mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090202.58F865FE.001A, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.4.204, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: a1a858e89f2df88ed00fe8d723161390
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/9oSRj-xXkxOnRNIYAphoqi2PnvU>
Subject: [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 07:40:56 -0000

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