[Detnet] 答复: ????: Question about yang moel

"Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com> Mon, 16 July 2018 19:55 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 95DD6130E34 for <detnet@ietfa.amsl.com>; Mon, 16 Jul 2018 12:55:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 mMoTlTmiOV0Z for <detnet@ietfa.amsl.com>; Mon, 16 Jul 2018 12:55:12 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BE92129C6B for <detnet@ietf.org>; Mon, 16 Jul 2018 12:55:12 -0700 (PDT)
Received: from lhreml709-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 694D2CA88EFA3; Mon, 16 Jul 2018 20:55:07 +0100 (IST)
Received: from DGGEMA405-HUB.china.huawei.com (10.3.20.46) by lhreml709-cah.china.huawei.com (10.201.108.32) with Microsoft SMTP Server (TLS) id 14.3.399.0; Mon, 16 Jul 2018 20:55:09 +0100
Received: from DGGEMA521-MBX.china.huawei.com ([169.254.6.142]) by DGGEMA405-HUB.china.huawei.com ([10.3.20.46]) with mapi id 14.03.0382.000; Tue, 17 Jul 2018 03:55:04 +0800
From: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>
To: Toerless Eckert <tte@cs.fau.de>
CC: "detnet@ietf.org" <detnet@ietf.org>
Thread-Topic: [Detnet] ????: Question about yang moel
Thread-Index: AQHUHS2i3GX0wuIccU6dMvP4W7h8WKSSPd4g
Date: Mon, 16 Jul 2018 19:55:03 +0000
Message-ID: <F1C1D5B02EA3FA4A8AF54C86BA4F325C22D1983D@dggema521-mbx.china.huawei.com>
References: <20180716154750.p727uz5g4gsxlf3i@faui48f.informatik.uni-erlangen.de> <F1C1D5B02EA3FA4A8AF54C86BA4F325C22D197C8@dggema521-mbx.china.huawei.com> <20180716175120.5gsxecwfoaq6ffu3@faui48f.informatik.uni-erlangen.de>
In-Reply-To: <20180716175120.5gsxecwfoaq6ffu3@faui48f.informatik.uni-erlangen.de>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.124.182.192]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/g0imamzynzZrfb8U0kP9VoC9N3c>
Subject: [Detnet] 答复: ????: Question about yang moel
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.27
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, 16 Jul 2018 19:55:15 -0000

Hi Toerless,

I fully agree with you that these parameters should be considered in the DetNet YANG Model, not all of which can be covered by IEEE.
However, I still think we should be careful about the "bounded latency" relevant parameters. Currently, we try to treat them as two parts: 1. Parameters about Queuing mechanism, defined in IEEE Qcw; 2. Parameters about Qos, which is under discussion of data plane draft. And we plan to leave point 1 to IEEE and define point 2 after the data plane work is done.
Also, how to make the IEEE yang model perform well in the DetNet YANG Structure is very important, and may request cooperation between two organizations.


Best Regards
Xuesong

-----邮件原件-----
发件人: Toerless Eckert [mailto:tte@cs.fau.de] 
发送时间: 2018年7月17日 1:51
收件人: Gengxuesong (Geng Xuesong) <gengxuesong@huawei.com>
抄送: detnet@ietf.org
主题: Re: [Detnet] ????: Question about yang moel

If we can inherit somehow "subtrees" specified by IEEE that would be great, but i am not sure if that would suffice, and it may make the IETF yang tree problematic. Of course, we do not want to contradict any reuseable QoS parameters specified by IEEE, i am counting on that.

Effectively, the problem is that if we say "here is a detnet 6 tuple flow", and here are the IEEE specified qos parameters for it", there is no IEEE spec for this behavior on detnet flows, so we may not get away referring to IEEE as being authoritative.

Cheers
    Toerless

On Mon, Jul 16, 2018 at 03:58:42PM +0000, Gengxuesong (Geng Xuesong) wrote:
> Thanks for your question Toerless.
> We intend to include the parameters of bounded latency function and other functions in the YANG Model. However, the situation is, a parallel yang model definition work is being done in IEEE, just as what is showed in page8 and page9 in the slides that are presented today. A lot of parameters that are bounded latency related are supposed to define in IEEE. If there are some solutions/functions which are defined in IETF and not covered by IEEE, the parameters of them are supposed to be included in the yang model draft. And of course, the solution/function should be in the WG work first.
> 
> Best Regards
> Xuesong
> 
> -----????????-----
> ??????: detnet [mailto:detnet-bounces@ietf.org] ???? Toerless Eckert
> ????????: 2018??7??16?? 23:48
> ??????: detnet@ietf.org
> ????: [Detnet] Question about yang moel
> 
> 
> Process question (alas, i am clueless on this):
> 
> Whats the IETF rules on including Yang objects into the model that refer to functionality that is only specified as informational ?
> 
> I am asking because some functionality like the DetNet bounded latency functionality might only be in informational documents.
> I definitely would want to have all this be included as (of course
> optional) parts of the DetNet Yang model, but if there is an issue with this Wrt. IETF process, we should rather know about this earlier than later.
> 
> Thanks
>     Toerless
> 
> _______________________________________________
> detnet mailing list
> detnet@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet
> _______________________________________________
> detnet mailing list
> detnet@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet