Some Good points on the discussion.
I think I've heard several perceived issues with YANG scalability:
- Validation times for large numbers of replicated instances,
- User input of config data for the replicated instances
- Overall size of aggregated models.
To me in standards the real value of
Hi
I'd suggest that the 802.1 Yangsters group should track this, and a 802.1
Maintenance item should be raised. (those can proceed in parallel). I had
cautioned some 802.1 editors about the drawbacks of putting xpath conditions in
YANG.
Cheers,
Don
-Original Message-
From: ne
+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
Thanks - In DetNet we have an ID in progress we should change from type
inet:ip-address to inet:ip-address-no-zone. I did not know that.
My other thought is since the ipv4-address (with the zone) is of format
"127.1.1.0%AndAUnterminatedString..", shouldn't every use of ipv4-address type
also h
precise it would settle the arguments.
Regards,
Don
From: Andy Bierman
Sent: Thursday, March 18, 2021 1:23 PM
To: Don Fedyk
Cc: tom petch ; Mahesh Jethanandani
; Juergen Schoenwaelder
; netmod@ietf.org
Subject: Re: [netmod] Use of prefixes in YANG models
On Thu, Mar 18, 2021 at 10:07 AM Don
Clarity and consistency would help.
Many of the supporting tool chains are picky about prefixes. IE they must be
the same as in the definition file. I have a case where yanglint wants "local
prefixes or derived-from(-or-self) construct" for an local identity in an xpath
statement. (either reme
I ietf-ip@2018-02-22
i ietf-yang-schema-mount@2019-01-14
I ietf-network-instance@2019-01-21
i ietf-routing-types@2017-12-04
I ietf-pseudowires@2018-10-22
I ietf-l2vpn@2019-05-28
Cheers
Don
From: Rob Wilton (
+1
(Definitely too many numeric types encoded as strings ) Don
[RW]
Ah, Okay. Yes, I agree. I think that there are already too many types that
get encoded as a string in YANG.
My suggestion was to consider for the next version of YANG to potentially
add two new native YANG types:
- Binary fl
Some comments on the draft :
On the content of the draft L3 Section:
Overall the draft assumes quite a bit of knowledge about L3 service
configuration. I don't know where L3 service to interfaces in the IETF
models. I'd guess it is routing to interfaces and IP forwarding based on
routing b