Re: [netmod] for a future rfc6991bis

[Robert Wilton <[e-mail]>]

On 29/11/2018 16:34, Juergen Schoenwaelder wrote:
> Rob,
>
> I have added this to my list of things to look at. Whether we do this
> or not may also depend on how the final date solution will look like
> and whether people feel it is worth to move this out of rfc6991bis,
> i.e., such a YANG revision-identifer is useful for modules that do
> not want to depend on rfc6991bis.

Thanks.  Sounds sensible to me.

Rob


>
> /js
>
> On Thu, Nov 29, 2018 at 11:03:45AM +0000, Robert Wilton wrote:
>> Hi Juergen,
>>
>> YANG library currently defines the type "revision-identifer".  Is this a
>> typedef that should logically migrate to rfc6991bis?
>>
>> Thanks,
>> Rob
>>
>> On 14/11/2018 08:16, Ladislav Lhotka wrote:
>>> On Wed, 2018-11-14 at 09:10 +0100, Martin Bjorklund wrote:
>>>> Hi,
>>>>
>>>> Alex Campbell <[e-mail]> wrote:
>>>>> Does a percentage really need a single standard type in the first
>>>>> place? How about "units percent;"?
>>>> At this point, after hearing about how different modules have
>>>> differing requirement on this type, I tend to agree.
>>> +1
>>>
>>> Or even "units %;"
>>>
>>> Lada
>>>
>>>> /martin
>>>>
>>>>
>>>>> ________________________________________
>>>>> From: netmod <[e-mail]> on behalf of Acee Lindem (acee)
>>>>> <[e-mail]>
>>>>> Sent: Wednesday, 14 November 2018 5:03 a.m.
>>>>> To: Juergen Schoenwaelder; Balázs Lengyel
>>>>> Cc: NETMOD WG
>>>>> Subject: Re: [netmod] for a future rfc6991bis
>>>>>
>>>>> On 11/13/18, 9:07 AM, "netmod on behalf of Juergen Schoenwaelder"
>>>>> <[e-mail] on behalf of
>>>>> [e-mail]> wrote:
>>>>>
>>>>>       On Tue, Nov 13, 2018 at 01:33:01PM +0000, Balázs Lengyel wrote:
>>>>>       > Hello,
>>>>>       >
>>>>>       > In some cases I want a percentage without fractions. This could be
>>>>>       > defined
>>>>>       > using range, by specifying the numbers 0 | 1 | 2 ... 99 | 100 in the
>>>>>       > range's
>>>>>       > argument.
>>>>>       >
>>>>>       >     typedef percent-short {
>>>>>       >       type percent { range 0 | 1 | 2 ... 99 | 100; } // didn't type
>>>>> out
>>>>>       >       all the 101 integer values :-)
>>>>>       >     }
>>>>>       >
>>>>>
>>>>>       I guess we need to settle on a small number of percentage types that
>>>>>       people find useful and then module authors hopefully find what they
>>>>>       need. I am not sure that listing 101 numbers is a good pattern to use
>>>>>       (although it does achieve what you want). For percentages that have no
>>>>>       fraction, you likely want to derive from a base type that is efficient
>>>>>       to encode for binary encodings such as CBOR.
>>>>>
>>>>> Or simply define a type with a base type of unit8 type and a range of
>>>>> 0-100.
>>>>>
>>>>> Acee
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>       /js
>>>>>
>>>>>       --
>>>>>       Juergen Schoenwaelder           Jacobs University Bremen gGmbH
>>>>>       Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
>>>>>       Fax:   [phone]         <https://www.jacobs-university.de/>
>>>>>
>>>>>       _______________________________________________
>>>>>       netmod mailing list
>>>>>       [e-mail]
>>>>>       https://www.ietf.org/mailman/listinfo/netmod
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> netmod mailing list
>>>>> [e-mail]
>>>>> https://www.ietf.org/mailman/listinfo/netmod
>>>>> _______________________________________________
>>>>> netmod mailing list
>>>>> [e-mail]
>>>>> https://www.ietf.org/mailman/listinfo/netmod
>>>> _______________________________________________
>>>> netmod mailing list
>>>> [e-mail]
>>>> https://www.ietf.org/mailman/listinfo/netmod