Hi,
I'm not sure how many folks are tacking the netmod list, so I wanted
to raise a point here based on a discussion going on there. It looks
like we (authors of the NI and LNE docs) understood the
draft-ietf-netmod-schema-mount defined extension mount-point as
defining a node, similar to a container, in the data tree *but* the
schema-mount authors intended the extension to not define a node and to
just identify that the node containing the extension was where mounted
modules exist. This isn't too big a deal, but it does mean we now need
to put each mount point in its own container. The tree representation
won't materially change, but the yang module will. An example is
provided below.
So the question is does anyone care about this? If not, the
module/document updates are fairly straight forward. If you do care,
now is the time to speak up, preferably by joining the netmod discussion.
Lou
(as contributor)
For example in draft-ietf-rtgwg-ni-model:
OLD
choice root-type {
description
"Well known mount points.";
yangmnt:mount-point "vrf-root" {
description
"Root for L3VPN type models. This will typically
not be an inline type mount point.";
}
yangmnt:mount-point "vsi-root" {
description
"Root for L2VPN type models. This will typically
not be an inline type mount point.";
}
yangmnt:mount-point "vv-root" {
description
"Root models that support both L2VPN type bridging
and L3VPN type routing. This will typically
not be an inline type mount point.";
}
NEW
choice root-type {
description
"Well known mount points.";
container vrf-root {
description
"Container for mount point.";
yangmnt:mount-point "vrf-root" {
description
"Root for L3VPN type models. This will typically
not be an inline type mount point.";
}
}
container vsi-root {
description
"Container for mount point.";
yangmnt:mount-point "vsi-root" {
description
"Root for L2VPN type models. This will typically
not be an inline type mount point.";
}
}
container vv-root {
description
"Container for mount point.";
yangmnt:mount-point "vv-root" {
description
"Root models that support both L2VPN type bridging
and L3VPN type routing. This will typically
not be an inline type mount point.";
}
}
}
_______________________________________________
rtgwg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/rtgwg
