Re: Protocol: control specifications.

[Hallvard B Furuseth <h.b.furuseth@usit.uio.no>]

Jim Sermersheim writes:
> By way of example, I think what Hallvard means is that if a control
> specification says that the control is always critical, then that
> specification should also say what happens when a client misbehaves and
> sends that control with criticality set to FALSE.

And the other way around: Criticality TRUE when required to be FALSE.

> Hallvard, is that what you are saying?

Yes.  Unless [Protocol] itself is updated to say what happens.

Maybe this message got delayed or lost:

  From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
  
  Jim Sermersheim writes:
  >>>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no> 12/10/03 4:36:13 AM
  >>>>
  >>> 4.1.11. Controls 
  >>
  >>> This document does not specify any controls. Controls may be 
  >>> specified in other documents. The specification of a control consists 
  >>> of: 
  >>> (...)
  >>> - whether the control is always non critical, always critical, or 
  >>> optionally critical, 
  >>
  >> A request fails if this condition is violated?
  > 
  > The control specification would define server behavior when these
  > behaviors are violated.
  
  Then you need to add ', and the result if this constraint is violated'
  to the above text.
  
-- 
Hallvard