Bandwidth in uint64 or bandwidth-scientific-notation

[italobusi]

The bandwidth profile parameters (cir, eir, cbs, ebs) are defined as uint64

Should they be re-defined using the bandwidth-scientific-notation?

The units for cbs, ebs are Kbytes: should we generalize the bandwidth-scientific-notation with number-scientific-notation?

[tsaad-dev]

Which YANG models are using scientific notation? Why do we need it?

[italobusi]

The bandwidth profile parameters (cir, eir, cbs, ebs) are defined as uint64

Should they be re-defined using the bandwidth-scientific-notation?

The units for cbs, ebs are Kbytes: should we generalize the bandwidth-scientific-notation with number-scientific-notation?

See past discussion in #116 and ietf-ccamp-wg/draft-ietf-ccamp-client-signal-yang#7

The solution (bandwidth-scientific-notation as defined in RFC8776-bis I-D) solves the problem with CIR, EIR and PIR but not for CBS, EBS and PBS attributes ...

[italobusi]

2023-06-23

Agreements:

1. to have a consistent representation of packet bandwidth:

              type uint64;
              units "bits/second";
   

2. remove bandwidth-scientific-notation data type

3. to have a consistent representation of burst size

              type uint64;
              units "bytes";