[Detnet] Some Comments about the information model

"Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com> Mon, 24 April 2017 13:42 UTC

Return-Path: <gengxuesong@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 8FEB312947D for <detnet@ietfa.amsl.com>; Mon, 24 Apr 2017 06:42:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 20svqgFNRjic for <detnet@ietfa.amsl.com>; Mon, 24 Apr 2017 06:42:08 -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 27F8D12871F for <detnet@ietf.org>; Mon, 24 Apr 2017 06:42:08 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML712-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DLQ82543; Mon, 24 Apr 2017 13:42:04 +0000 (GMT)
Received: from DGGEMA405-HUB.china.huawei.com (10.3.20.46) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 24 Apr 2017 14:42:03 +0100
Received: from DGGEMA501-MBX.china.huawei.com ([169.254.1.85]) by DGGEMA405-HUB.china.huawei.com ([10.3.20.46]) with mapi id 14.03.0301.000; Mon, 24 Apr 2017 21:41:51 +0800
From: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>
To: "detnet@ietf.org" <detnet@ietf.org>, Balázs Varga A <balazs.a.varga@ericsson.com>
CC: "draft-farkas-detnet-flow-information-model@tools.ietf.org" <draft-farkas-detnet-flow-information-model@tools.ietf.org>
Thread-Topic: Some Comments about the information model
Thread-Index: AdK9AHgkJCqeqdxxQI2PTXzNe2FrNA==
Date: Mon, 24 Apr 2017 13:41:50 +0000
Message-ID: <F1C1D5B02EA3FA4A8AF54C86BA4F325CEC1390@DGGEMA501-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.169.123]
Content-Type: multipart/alternative; boundary="_000_F1C1D5B02EA3FA4A8AF54C86BA4F325CEC1390DGGEMA501MBXchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A0B0205.58FE00AD.000B, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.85, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 6e37c76e5936e8b90160a5158b488947
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/0NvKrhX3sFWbmSBgzIK_NkYw-UM>
Subject: [Detnet] Some Comments about the information 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: Mon, 24 Apr 2017 13:42:10 -0000

Hi Bala'zs


I have read "draft-farkas-detnet-flow-information-model-00". Thank you for offering the whole picture of DetNet information model, combining L2 and L3.

Here are some comments and questions after reading the draft:

6.1. Identification and Specification of Flows
"Identification options for TSN flows are specified by [IEEE8021CB], which also includes IP flow identification"

So I find the relative contents in [IEEE8021CB] as follows:
" The IP Stream identification is a passive Stream identification function that operates at the transport layer and Internet Protocol interface layer."

That is to say, the information of this part can only be recognized by the end station or other "DetNet edge node", which contain the transport layer(It is different from the transport layer in draft-finn-detnet-architecture-08. It is the transport layer in IP/TCP I think). However, the intermediate node which will forward the DetNet flow should also have the ability to separate DetNet flows from other flows, and send them to a special queue or make them go through queuing scheduler, in order to limit the delay in this node. So whether you have considered DetNet identification in every intermediate node as described above?


10. Status
"AccumulatedLatency is specified as an integer number of nanoseconds. Latency is measured using the time at which the data frame's message timestamp point passes the reference plane marking the boundary between the network media and PHY. The message timestamp point is specified by IEEE Std 802.1AS [IEEE8021AS] for various media. For a successful Status, the network returns a value less than or equal to the MaxLatency of the UserToNetworkRequirements (Section 9.3)."

If AccumulatedLatency of a particular path is MEASURED, even when it is less than the MaxLatency, it can not been proved that all the flows going through the path will experience latency which is less than their requirements. Because MEASUREMENT is only a special case. Maybe AccumulatedLatency should be defined as a value independent of the Internet conditions, such as a calculated value by the theory or other methods?





Best Regards,

Xuesong