Mutating Attributes

I think allowing the server to choose a value for an attribute other
than the value sent by the client in a request is going to make
interoperability more challenging.  As currently defined, the client
must be ready for the server to override (mutate) any attribute.  There
may be cases where the client application would prefer the request fail
than have a particular attribute mutated.  

I think by default the server should either accept the all of the
client's requested values, or fail the request entirely.  There can be
specific allowances in the specification for attributes where mutation
is deemed acceptable.  I think this eases the interoperability challenge
for clients by limiting the scope of what is allowed to change.


-Alan Frindell
SafeNet, Inc.
The information contained in this electronic mail transmission 
may be privileged and confidential, and therefore, protected 
from disclosure. If you have received this communication in 
error, please notify us immediately by replying to this 
message and deleting it from your computer without copying 
or disclosing it.