If the percentage is defined as following, as a author of 
draft-ye-ccamp-mw-topo-yang-02, we will be happy to use it.
But it's better to include in RFC6991bis, as percentage is a generic and widely 
used item.

BR,
Amy
________________________________
发件人: netmod [[email protected]] 代表 Qin Wu [[email protected]]
发送时间: 2018年11月6日 9:25
收件人: Xufeng Liu; [email protected]
抄送: NETMOD WG
主题: Re: [netmod] for a future rfc6991bis


Another case would be :


“

typedef percentage {

      type decimal64 {

         fraction-digits 5;

         range "0..100";

     }

   description "Percentage.";
   }
”
Which is defined ietf-connectionless-oam.yang module.

-Qin
发件人: netmod [mailto:[email protected]] 代表 Xufeng Liu
发送时间: 2018年11月6日 3:49
收件人: [email protected]
抄送: NETMOD WG <[email protected]>
主题: Re: [netmod] for a future rfc6991bis

The draft that asked for the percentage type is: 
https://tools.ietf.org/html/draft-ye-ccamp-mw-topo-yang-02

They currently define:

              leaf availability {
                type decimal64 {
                  fraction-digits 4;
                  range "0..99.9999";
                }
                description "Availability level of the link";
              }

Thanks,
- Xufeng

On Sun, Nov 4, 2018 at 7:07 AM Balázs Lengyel 
<[email protected]<mailto:[email protected]>> wrote:

+1 to percentage.

Balazs
On 2018. 11. 03. 3:44, Xufeng Liu wrote:
Remember that some draft asked for a type of percentage value to the nearest 
hundredth. Wondering if it can be put in.

Thanks,
- Xufeng

On Fri, Nov 2, 2018 at 11:39 AM tom petch 
<[email protected]<mailto:[email protected]>> wrote:
---- Original Message -----
From: "Juergen Schoenwaelder" 
<[email protected]<mailto:[email protected]>>
To: "Kent Watsen" <[email protected]<mailto:[email protected]>>
Cc: <[email protected]<mailto:[email protected]>>
Sent: Tuesday, October 30, 2018 10:14 AM

> On Tue, Oct 30, 2018 at 12:05:17AM +0000, Kent Watsen wrote:
> >
> > >> In addition, it might be good to introduce [inet?] types for RFC
5322
> > >> (Internet Message Format) including perhaps:
> > >>
> > >>   - email-address        (addr-spec, per Section 3.4.1)
> > >>   - named-email-address  (name-addr, per Section 3.4)
> > >>
> > >
> > > Where are these used? Or have these already been used somewhere?
> >
> > I'm unaware of these ever having been used before.  I am working on
a private module for which I want to configure an email address.  After
some searching, I concluded that no such types have been defined, and
thus thought that they might be good candidates for addition.


We could defined a user-name, of the form localpart@domainpart as is
widely used to identify a user in operations but which does not, in my
experience, owe anything to i18n, just a straightforward character set;
yes it would not boil the ocean, but could be useful.  I am surprised
not to find such a definition somewhere in our 40 or so NETCONF I-Ds.

Tom Petch







> >
>
> It would be good to have strong use cases. I fear that defining this
> type won't be easy given that we also have internationalized email
> addresses (RFC 6530 provides an overview) and we might have to create
> a union of RFC 5322 addresses and "SMTPUTF8 (compliant) addresses".
>
> /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/>
>
> _______________________________________________
> netmod mailing list
> [email protected]<mailto:[email protected]>
> https://www.ietf.org/mailman/listinfo/netmod

_______________________________________________
netmod mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/netmod


_______________________________________________

netmod mailing list

[email protected]<mailto:[email protected]>

https://www.ietf.org/mailman/listinfo/netmod<UrlBlockedError.aspx>

--

Balazs Lengyel                       Ericsson Hungary Ltd.

Senior Specialist

Mobile: +36-70-330-7909              email: 
[email protected]<mailto:[email protected]>
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to