Re: [netmod] operational knobs

[Phil Shafer <phil at juniper.net>]

Andy Bierman writes:
>   start-dhcp (start-address=192.168.1.10, end-address=192.168.1.100, ...)

This is fine if the customer doesn't care about any of the details
of how dhcp is deployed, or it your RPC contains all the parameters
they need.  But each customer is different; beware of underestimating
the diversity of the marketplace.

IMHO the world's just not that simple.  Eventually, you'll need
access to other config data (interfaces) and datastore-wide constraint
checking.   The good news is that YANG handle do all this.

>I am not
>convinced that the forklift data-model (ala ipfix-psamp.yang)
>has much chance of widespread deployment.

My hope is that I can define simple transformations between IETF
models and JUNOS models.  I think it's unlikely that JUNOS will
adopt the DHCP module directly, but if we can generate data that
is ietf-dhcp.yang with junos augmentations.

Thanks,
 Phil