Dear Kent, Andy and Alex, I think Alex statement https://mailarchive.ietf.org/arch/msg/netconf/5Yaiom0B0lDTeSPOvgNfPIEFvBw/, Andy's feedback and guidelines in https://datatracker.ietf.org/doc/html/rfc8407#section-4.4 resp. https://datatracker.ietf.org/doc/html/draft-ietf-netmod-rfc8407bis-15#section-4.4 makes perfectly sense and I don't see why we should do else. As an author, I suggest to add in section 4 of draft-ietf-netmod-rfc8407bis based on the conclusion of this discussion guidelines on reusable YANG groupings.
Best wishes Thomas From: Kent Watsen <[email protected]> Sent: Wednesday, September 18, 2024 3:12 AM To: Andy Bierman <[email protected]> Cc: [email protected]; [email protected] Subject: [netconf] Re: Default statements on udp-client-server groupings Be aware: This is an external email. Hi Andy, The main purpose for YANG defaults is ease of use. If there are less things to configure then the device is easier to use. Without a default port then this parameter becomes mandatory to configure. Alex is trying to maximize lazy binding. That is, as a general statement, unless 100% sure, groupings should never specify the “default” or “mandatory” statements, leaving it to terminal “uses” statements to specify. His comment raises to the level of something that could be an addition to rfc8407bis. Thoughts? Kent
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
