Re: [netmod] use cases was: finish up
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [netmod] use cases was: finish up



Hi -

> From: "Phil Shafer" <phil at juniper.net>
> To: "Randy Presuhn" <randy_presuhn at mindspring.com>
> Cc: <netmod at ietf.org>
> Sent: Friday, October 23, 2009 1:07 PM
> Subject: Re: [netmod] use cases was: finish up 
...
> My concerns are more practical.  MUST forces a modeler to do something
> that might not be required, and the real difference (in terms of
> behaviors) in MUST and MAY is near zero.

As both Andy and I have pointed out, it makes a huge difference
for the client implementation.

>  The client will refetch
> either way (if it cares).

That's not the point, as both Andy and I have pointed out.

>  The server will be driven by the behavior
> required in the "description", not the "s-c" statement.

The problem is what the client is required to do.  If the server
cannot be relied on to supply required s-c values, equivalent,
or potentially more complex logic, which would otherwise not be
needed, must be implemented in clients.

Randy


Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.