Re: [netmod] use cases was: finish up

[Phil Shafer <phil at juniper.net>]

"Randy Presuhn" writes:
>You're only looking at part of the problem.  The difference is in how
>the value is allocated.  With the "MAY" behaviour, the client needs
>to replicate whatever allocation logic the server should have had, in
>case the server didn't feel like allocating one that day.  With the "MUST"
>behaviour, client implementors don't need to replicate that logic unless
>they have some other compelling reason to.

Consider the following slightly faked-up scenario:  an IDP detection
policy is shared between a set of chassis.  To be shared, the policy
needs a unique number, but some policies (based on the needs of the
policy) are not shared and do not need this number.  The system MAY
create the "number" leaf if the policy needs it, but won't bother
creating it if it does not need it.

I guess this leaf could be made irrelevant by using a "must" statement
that discards it unless the policy needs it.

Thanks,
 Phil