Erik Kline has entered the following ballot position for
draft-ietf-netmod-geo-location-08: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
+1 The floating point format is really non-intuitive. We have used uint64 bit
rates.
Cheers
Don
-Original Message-
From: netmod On Behalf Of Acee Lindem (acee)
Sent: Friday, May 14, 2021 8:27 AM
To: Italo Busi ; 'Juergen Schoenwaelder'
; Reshad Rahman
Cc: 'netmod@ietf.org' ; t...@iet
I concur with Carsten.
There is YANG modeling work currently ongoing in CCAMP where we are
dealing with analog bandwidth (DWDM transport networks), which is
measured in Hz, kHz, MHz, GHz, and THz.
So, the term bandwidth describing a data rate or bit rate has always
been confusing in the DWDM
On 2021-05-13, 1:25 PM, "netmod on behalf of Juergen Schoenwaelder"
wrote:
On Thu, May 13, 2021 at 11:57:26AM -0400, Reshad Rahman wrote:
> Hi,
>
>
>
> Has there been any discussions wrt adding new bandwidth types e.g. the
bandwidth-xxx types in draft-ietf-teas-yan
I'd be all for using some unsigned integer quantity. I think it was a mistake
for using IEEE floating point in the first place. This floating point nonsense
was carried over to Traffic Engineering (TE) from early work done on transport
area on RSVP. For example, https://www.rfc-editor.org/rfc/rf
On 2021-05-13, at 19:25, Juergen Schoenwaelder
wrote:
>
> The description of bandwidth-ieee-float32 says:
>
> The units are octets per second.
The quantity you are looking for is called “bit rate” (IEC 8:13, item
number 13-13).
Its unit is bit/s.
A single 64-bit integer should g
I assume it is best to settle this in teas. Form a programmatic point
of view, you likely want to have a single unit. Even if you go for bps
(bits per second), a uint64 still allows you to express quite big data
rates (I think 16777216 terra bits per second but please check
yourself). From a human
Reshad, Juergen,
Actually, there is some on-going discussion within TEAS because some packet
technology-specific YANG modules are not using the bandwidth-ieee-float32 but
prefers using some uint type:
https://github.com/tsaad-dev/te/issues/116
The ietf-te-packet-types already defines bandwidth
