Re: [netmod] [Technical Errata Reported] RFC7950 (5784)

The text starts with the general case and says "Leading and trailing
zeros are prohibited", which seems to cover 0.50000000 (which must be
represented as 0.5.

/js

On Wed, Jul 17, 2019 at 09:42:38AM +0000, Qin Wu wrote:
> I realized my proposed changes also have some flaw and may need to be tweaked.
> 
> My question is should trailing zeros in “0.50000” be allowed? I didn’t see the original text prohibit this.
> Yes, the original text is correct, but it excludes some exception cases, such as “0.500000000”, if my understanding is correct.
> 发件人: Rob Wilton (rwilton) [mailto:rwilton@cisco.com]
> 发送时间: 2019年7月17日 17:20
> 收件人: Qin Wu <bill.wu@huawei.com>; Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
> 抄送: ibagdona@gmail.com; warren@kumari.net; netmod@ietf.org; RFC Errata System <rfc-editor@rfc-editor.org>
> 主题: RE: [netmod] 答复: [Technical Errata Reported] RFC7950 (5784)
> 
> Hi Qin,
> 
> I also find the current RFC text quite understandable and correct.
> 
> The “and” is required to disallow “.0” and “0.” as valid canonical forms.  I.e. in the canonical form there MUST always be at least one digit (which could be 0) before the decimal point and then must be at least one digit (which could be 0) after the decimal point.  Otherwise, there must be no leading or trailing 0’s.  So, none of  “.0”, “0.”, “00.0”, “0.00” and “00.00” are in the canonical form, and should be represented as “0.0” instead; similarly none of “.1”, “1.”, “01.0”, “1.00” and “01.00” are in the canonical form and should be represented as “1.0” instead.
> 
> Thanks,
> Rob
> 
> 
> From: netmod <netmod-bounces@ietf.org<mailto:netmod-bounces@ietf.org>> On Behalf Of Qin Wu
> Sent: 17 July 2019 09:59
> To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de<mailto:j.schoenwaelder@jacobs-university.de>>
> Cc: ibagdona@gmail.com<mailto:ibagdona@gmail.com>; warren@kumari.net<mailto:warren@kumari.net>; netmod@ietf.org<mailto:netmod@ietf.org>; RFC Errata System <rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>>
> Subject: [netmod] 答复: [Technical Errata Reported] RFC7950 (5784)
> 
> 
> Understand, the problem lies at "and" that is used in " one digit before and after the decimal point ", that is to say it only focus on the case that has two digits, one is before decimal point, the other digit is after decimal such as "5.06", but doesn't cover the case where "one digit before or after the decimal point ", that’s why I think the case 0.500000 is not covered. We should prohibit trailing zeros in “0.5000000”.
> 
> -----邮件原件-----
> 发件人: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-university.de]
> 发送时间: 2019年7月17日 16:46
> 收件人: Qin Wu <bill.wu@huawei.com<mailto:bill.wu@huawei.com>>
> 抄送: RFC Errata System <rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>>; ibagdona@gmail.com<mailto:ibagdona@gmail.com>; netmod@ietf.org<mailto:netmod@ietf.org>; warren@kumari.net<mailto:warren@kumari.net>
> 主题: Re: [netmod] [Technical Errata Reported] RFC7950 (5784)
> 
> 
> 
> The text starts with the general case and says "Leading and trailing zeros are prohibited", which seems to cover 0.50000000. The text then handles the special rule that there needs to be at least one digit before and after the decimal point. I think all is fine.
> 
> 
> 
> /js
> 
> 
> 
> On Wed, Jul 17, 2019 at 08:11:41AM +0000, Qin Wu wrote:
> 
> > What about "0.50000000"? based on original text, is it legal or illegal?
> 
> > It seem original text exclude the case where one digit before or after the decimal point?
> 
> >
> 
> > -Qin
> 
> > -----邮件原件-----
> 
> > 发件人: netmod [mailto:netmod-bounces@ietf.org] 代表 Juergen Schoenwaelder
> 
> > 发送时间: 2019年7月17日 15:50
> 
> > 收件人: RFC Errata System <rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>>
> 
> > 抄送: ibagdona@gmail.com<mailto:ibagdona@gmail.com>; netmod@ietf.org<mailto:netmod@ietf.org>; warren@kumari.net<mailto:warren@kumari.net>
> 
> > 主题: Re: [netmod] [Technical Errata Reported] RFC7950 (5784)
> 
> >
> 
> > I do not see why the original text makes 0.5 or 0.0 illegal.
> 
> >
> 
> > /js
> 
> >
> 
> > On Tue, Jul 16, 2019 at 08:52:52PM -0700, RFC Errata System wrote:
> 
> > > The following errata report has been submitted for RFC7950, "The
> 
> > > YANG
> 
> > > 1.1 Data Modeling Language".
> 
> > >
> 
> > > --------------------------------------
> 
> > > You may review the report below and at:
> 
> > > https://www.rfc-editor.org/errata/eid5784
> 
> > >
> 
> > > --------------------------------------
> 
> > > Type: Technical
> 
> > > Reported by: Qin WU <bill.wu@huawei.com<mailto:bill.wu@huawei.com>>
> 
> > >
> 
> > > Section: 9.3.2
> 
> > >
> 
> > > Original Text
> 
> > > -------------
> 
> > > Leading and trailing zeros are prohibited, subject to the rule that
> 
> > > there MUST be at least one digit before and after the decimal point.
> 
> > > The value zero is represented as "0.0".
> 
> > >
> 
> > >
> 
> > >
> 
> > >
> 
> > > Corrected Text
> 
> > > --------------
> 
> > > Leading zeros before the first digit and trailing zeros after the
> 
> > > last digit are prohibited, subject to the rule that there MUST be at
> 
> > > least one digit before and after the decimal point.  The value zero
> 
> > > is represented as "0.0".
> 
> > >
> 
> > > Notes
> 
> > > -----
> 
> > > Based on the rule in the orginal text, the value such as "0.5","0.0" is illegal. So I think the intention of the original text is to make sure the leading zeros before the first digit and the trailing zero after the last digit are prohibited.
> 
> > >
> 
> > > Instructions:
> 
> > > -------------
> 
> > > This erratum is currently posted as "Reported". If necessary, please
> 
> > > use "Reply All" to discuss whether it should be verified or rejected.
> 
> > > When a decision is reached, the verifying party can log in to change
> 
> > > the status and edit the report, if necessary.
> 
> > >
> 
> > > --------------------------------------
> 
> > > RFC7950 (draft-ietf-netmod-rfc6020bis-14)
> 
> > > --------------------------------------
> 
> > > Title               : The YANG 1.1 Data Modeling Language
> 
> > > Publication Date    : August 2016
> 
> > > Author(s)           : M. Bjorklund, Ed.
> 
> > > Category            : PROPOSED STANDARD
> 
> > > Source              : Network Modeling
> 
> > > Area                : Operations and Management
> 
> > > Stream              : IETF
> 
> > > Verifying Party     : IESG
> 
> > >
> 
> > > _______________________________________________
> 
> > > netmod mailing list
> 
> > > netmod@ietf.org<mailto:netmod@ietf.org>
> 
> > > https://www.ietf.org/mailman/listinfo/netmod
> 
> >
> 
> > --
> 
> > 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/>
> 
> >
> 
> > _______________________________________________
> 
> > netmod mailing list
> 
> > netmod@ietf.org<mailto:netmod@ietf.org>
> 
> > https://www.ietf.org/mailman/listinfo/netmod
> 
> 
> 
> --
> 
> 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/>

-- 
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/>