[netmod] draft-bjorklund-netmod-structural-mount: Namespace issues

[Anton Tkáčik <[e-mail]>]

Hi,

if I understand correctly netmod-structural-mount inlines "mounted" data directly to container / list which is used,

which brings up following issues:


1. It is possible to have identifier conflict between data from model defining mount and mounted data (if mounted schema

contains same model).

e.g.

      module mount-under-mount {

             container mounts {

                   list mount {

                       key name;

                       leaf name;

                              container mounts {

                                    // List of discovered remote mounts

                              }

                              mnt:mount-point data;

                   }

             }?

      }


2. Expanding data directly under container / list may be problematic for clients which do not support netmod-structural-mount.


I believe both can be solved elegantly by requiring mount-point extension to be used inside anydata element, which signifies

to client that this may be any YANG modeled data (and client can omit processing it) and also provides isolation between

data from module defining mount point and mounted data.


E.g:

list mount {

    key name;

    leaf name {...}

    // additional data

    anydata data {

         mnt:mount-point data {

              mnt:mount-yang-library;?

         }

    }

}
AntonTkáčik
Chief Software Architect

Mlynské Nivy 56 / 821 05 Bratislava / Slovakia
[phone] / [e-mail]
reception: [phone] / www.pantheon.sk
[logo]