Upon further reflection, I have a conceptual question related to A.2 UC2.
It is referring to the 'type' leaf of an interface.
When the entire interface is auto-created by the system, then the whole
interface is in the system DS.
But how about the case where an interface is created by a client/user, without
a 'type', and the server fills in the value of the 'type' leaf as described in
the interfaces YANG model:
When an interface entry is created, a server MAY
initialize the type leaf with a valid value, e.g., if it
is possible to derive the type from the name of the
interface.
Is the 'type' leaf in that case considered immutable?
In that case, doesn't that leaf, and the interface itself (at least the list
key), need to be in the system DS?
Jason
> -----Original Message-----
> From: Jason Sterne (Nokia) <[email protected]>
> Sent: Monday, January 12, 2026 9:07 PM
> To: [email protected]; [email protected]
> Subject: [netmod] Re: I-D Action: draft-ietf-netmod-immutable-flag-07.txt
>
> Hi all,
>
> Sorry I've been so slow in getting back to this immutable-flag draft. I've
> finally taken a look at the latest draft (v0.7).
>
> Overall I'm happy with it. My previous comments have been discussed and
> resolved.
>
> Minor comment on A.3 UC3: I think Rob mentioned this previously, but
> perhaps we should say that a hard coded admin account isn't recommended
> but just used here for illustration purposes.
>
> In B.4. change this:
> expect for the "description"
> to this:
> except for the "description"
>
> Jason
>
> > -----Original Message-----
> > From: [email protected] <[email protected]>
> > Sent: Monday, January 12, 2026 3:30 AM
> > To: [email protected]
> > Cc: [email protected]
> > Subject: [netmod] I-D Action: draft-ietf-netmod-immutable-flag-07.txt
> >
> >
> > CAUTION: This is an external email. Please be very careful when clicking
> > links or opening attachments. See the URL nok.it/ext for additional
> > information.
> >
> >
> >
> > Internet-Draft draft-ietf-netmod-immutable-flag-07.txt is now available. It
> is
> > a work item of the Network Modeling (NETMOD) WG of the IETF.
> >
> > Title: YANG Metadata Annotation for Immutable Flag
> > Authors: Qiufang Ma
> > Qin Wu
> > Balazs Lengyel
> > Hongwei Li
> > Name: draft-ietf-netmod-immutable-flag-07.txt
> > Pages: 28
> > Dates: 2026-01-12
> >
> > Abstract:
> >
> > This document defines a way to formally document an existing
> > behavior, implemented by servers in production, on the immutability
> > of some system-provided nodes, using a YANG metadata annotation
> > called "immutable" to flag which nodes are immutable.
> >
> > Clients may use "immutable" annotations provided by the server, to
> > know beforehand why certain otherwise valid configuration requests
> > will cause the server to return an error.
> >
> > The immutable flag is descriptive, documenting an existing behavior,
> > not proscriptive, dictating server behaviors.
> >
> > This document updates RFC 8040 and RFC 8526.
> >
> > The IETF datatracker status page for this Internet-Draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-netmod-immutable-flag/
> >
> > There is also an HTML version available at:
> > https://www.ietf.org/archive/id/draft-ietf-netmod-immutable-flag-07.html
> >
> > A diff from the previous version is available at:
> > https://author-tools.ietf.org/iddiff?url2=draft-ietf-netmod-immutable-flag-
> 07
> >
> > Internet-Drafts are also available by rsync at:
> > rsync.ietf.org::internet-drafts
> >
> >
> > _______________________________________________
> > netmod mailing list -- [email protected]
> > To unsubscribe send an email to [email protected]
>
> _______________________________________________
> netmod mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
_______________________________________________
netmod mailing list -- [email protected]
To unsubscribe send an email to [email protected]
