Re: [Netconf] mbj's WGLC review of yang-push-17

Qin Wu <bill.wu@huawei.com> Wed, 26 September 2018 08:00 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B6D6130E1A for <netconf@ietfa.amsl.com>; Wed, 26 Sep 2018 01:00:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 Au8bsEfF3aBf for <netconf@ietfa.amsl.com>; Wed, 26 Sep 2018 01:00:36 -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 6148E130DC2 for <netconf@ietf.org>; Wed, 26 Sep 2018 01:00:36 -0700 (PDT)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 5867C65BCF225; Wed, 26 Sep 2018 09:00:31 +0100 (IST)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.399.0; Wed, 26 Sep 2018 09:00:32 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.200]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0399.000; Wed, 26 Sep 2018 16:00:26 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
CC: Kent Watsen <kwatsen@juniper.net>, Netconf <netconf@ietf.org>
Thread-Topic: [Netconf] mbj's WGLC review of yang-push-17
Thread-Index: AQHUNImyZPENQ2zHlkefbN/9krMXIaUA8lEAgAAPiICAAD1IgIAADScAgAC3DFD//9LEgIAAnV4w
Date: Wed, 26 Sep 2018 08:00:26 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9B053848@nkgeml513-mbx.china.huawei.com>
References: <20180920.094520.798604819426315275.mbj@tail-f.com> <644DA50AFA8C314EA9BDDAC83BD38A2E0EB691A5@sjceml521-mbx.china.huawei.com> <20180924.093612.1791958587714330227.mbj@tail-f.com> <A1DF23A4-3D00-43D7-B121-D9F567B2A43F@juniper.net> <020f01d454ae$2e41e4a0$4001a8c0@gateway.2wire.net> <CABCOCHSATfi4Nq3XLGL65Kj4R_gWTFSf6H0v8qD8DE4aYOpDiQ@mail.gmail.com> <674F5961-D956-4BD1-8AD0-44FE68150070@juniper.net> <20180925213145.r72ybqbuv5qy4dct@anna.jacobs.jacobs-university.de> <5ED013C2-0D95-4B09-B0F5-D715DD58BE45@juniper.net> <B8F9A780D330094D99AF023C5877DABA9B052880@nkgeml513-mbx.china.huawei.com> <20180926063205.occ7oo5jxfnblvg5@anna.jacobs.jacobs-university.de>
In-Reply-To: <20180926063205.occ7oo5jxfnblvg5@anna.jacobs.jacobs-university.de>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.33.244]
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/netconf/rdjBfRyLAA_nC9bGT5dACqlqyJ8>
Subject: Re: [Netconf] mbj's WGLC review of yang-push-17
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Sep 2018 08:00:43 -0000

-----邮件原件-----
发件人: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-university.de] 
发送时间: 2018年9月26日 14:32
收件人: Qin Wu
抄送: Kent Watsen; Netconf
主题: Re: [Netconf] mbj's WGLC review of yang-push-17

On Wed, Sep 26, 2018 at 01:25:54AM +0000, Qin Wu wrote:
> 
> To address this, one solution we proposed in draft-ietf-lime-yang-connectionless-oam-18:
> Is to define ietf-lime-time-types which can be reused in other 
> modules. In ietf-lime-time-types, we define define time-unit-type as identity.
> But maybe typedef is even better since both time-unit and value are defined in one.
>

The good old practice was to think about the number range that makes sense and then to use a numeric type with a suitable unit that covers the number range.

I wonder whether you really need a uint32 range of hours in the OAM models. 
	
[Qin]: not necessary for OAM model, but It may be used in some other models that require unint32 range of hours.

Note that a single uint64 of nanoseconds would give you up to
584 years. If oam models do indeed need delay values that range from nanoseconds to hundreds of years, I would rather go with a single
uint64 instead of a combination of an uint32 and a unit identifier.

[Qin]: Not advocating using such combination, just point out such common type are also needed in some other models, that's why a separate ietf-lime-time-types was defined.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>