Re: [netmod] use cases was: finish up

[Phil Shafer <phil at juniper.net>]

"Randy Presuhn" writes:
>If it's what other standards would call "conditionally mandatory",
>then a compromise would be to say that the server MUST create it
>when not supplied by the client *if* the conditions that make it
>mandatory (presumably rigorously spelled out in description text)
>are satisfied.  What I can't abide is just leaving it to
>an implementation's whims, which is what the proposed "MAY"
>language would do.

I read "MUST if xxxx" as "MAY", in which case "conditionally
mandatory" means "the implementor must read the description to know
what they are doing", which is unavoidable on the server side.
I do not read "MAY" as the "implementation's whims", since
the implementor must live by the rules in the description.

Thanks,
 Phil