Re: [Detnet] Comments on 4 Technical Requirements in Large-Scale Deterministic (draft-liu-detnet-large-scale-requirements)

Peng Liu <liupengyjy@chinamobile.com> Fri, 29 July 2022 14:56 UTC

Return-Path: <liupengyjy@chinamobile.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 B58E1C14F728; Fri, 29 Jul 2022 07:56:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Level:
X-Spam-Status: No, score=-6.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_FACE_BAD=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pj17HuEk8VdA; Fri, 29 Jul 2022 07:56:30 -0700 (PDT)
Received: from cmccmta3.chinamobile.com (cmccmta3.chinamobile.com [221.176.66.81]) by ietfa.amsl.com (Postfix) with ESMTP id 9B8C8C14CF0A; Fri, 29 Jul 2022 07:56:27 -0700 (PDT)
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[172.16.121.95]) by rmmx-syy-dmz-app09-12009 (RichMail) with SMTP id 2ee962e3f511660-bc818; Fri, 29 Jul 2022 22:56:21 +0800 (CST)
X-RM-TRANSID: 2ee962e3f511660-bc818
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from CMCC-LP (unknown[120.244.192.66]) by rmsmtp-syy-appsvrnew08-12033 (RichMail) with SMTP id 2f0162e3f512c7b-986ee; Fri, 29 Jul 2022 22:56:20 +0800 (CST)
X-RM-TRANSID: 2f0162e3f512c7b-986ee
Date: Fri, 29 Jul 2022 23:01:13 +0800
From: Peng Liu <liupengyjy@chinamobile.com>
To: Chengzuopin <czp@h3c.com>
Cc: detnet <detnet@ietf.org>, draft-liu-detnet-large-scale-requirements <draft-liu-detnet-large-scale-requirements@ietf.org>, Zhushiyin <zhushiyin@h3c.com>, "zhou.leih" <zhou.leiH@h3c.com>
References: <c432d1a413ed48019df4e1cdc4becda4@h3c.com>
X-Priority: 3
X-GUID: 8FC93375-3ADD-4469-94A9-24BECDDE5C94
X-Has-Attach: no
X-Mailer: Foxmail 7.2.21.453[cn]
Mime-Version: 1.0
Message-ID: <2022072923011269956460@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart468181832863_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/s2AzPfj2-jFINOWOIZ3sy4p16gY>
Subject: Re: [Detnet] Comments on 4 Technical Requirements in Large-Scale Deterministic (draft-liu-detnet-large-scale-requirements)
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 29 Jul 2022 14:56:31 -0000

Hi Cheng,

Thank you for your comments. Let me try to understand your proposal.

The proposed new section name of "Supports hierarchical deterministic peers" is a little hard to be understood from the my side. According to the proposed text below, I guess you mean to decouple multiple domains as possible based on the gateways at edge or between two domains, which could support flow access control, traffic shaping, traffic mark, deterministic scheduling, and jitter compression. 

So if my understanding is right, the point is to enhance the gateways, which was mentioned in 'section 4.7 Support Queueing Mechanisms Switchover Crossing Multi-domains'. We can discuss more about whether or how to merge your proposal into the existing section. 

BTW, I think more explanation of your text and/or some key words such as 'jitter compression' will help us understand better of it. Thanks.

Regards,
Peng 


liupengyjy@chinamobile.com
 
From: Chengzuopin
Date: 2022-07-29 19:50
To: liupengyjy@chinamobile.com
CC: detnet@ietf.org; draft-liu-detnet-large-scale-requirements@ietf.org; Zhushiyin; Zhoulei
Subject: [Detnet] Comments on 4 Technical Requirements in Large-Scale Deterministic (draft-liu-detnet-large-scale-requirements)
Hi Peng, 
  Suggest “Chapter 4 Technical Requirements in Large-Scale Deterministic” to add new chapter “4.8 Supports hierarchical deterministic peers”. 
 
4.8 Supports hierarchical deterministic peers
Large-scale deterministic network can often cross multiple domains, and one of DetNet network's goals is to provide end-to-end deterministic latency services. The technology and capabilities of each domain are different and the corresponding topology models are either segmented or nested. In this way, it is necessary to reduce the coupling between two domains as much as possible, as long as the network meets a certain range of requirements and end-to-end devices implement the jitter compression, end-to-end deterministic latency services can be supported. For example, the two-end user networks are carried by the operator's intermediate network. As long as the operator's intermediate network ensures its end-to-end latency, bounded jitter and reliability capabilities for deterministic flow,  the operator network can be made as a pipeline for the two-end user network. So gateway equipment deployed on both ends utilizes these mechanisms including flow access control, traffic shaping, traffic mark, deterministic scheduling, and jitter compression to meet the end-to-end deterministic latency service.
 Best,
cheng
-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有新华三集团的保密信息,仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、
或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本
邮件!
This e-mail and its attachments contain confidential information from New H3C, which is 
intended only for the person or entity whose address is listed above. Any use of the 
information contained herein in any way (including, but not limited to, total or partial 
disclosure, reproduction, or dissemination) by persons other than the intended 
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender 
by phone or email immediately and delete it!