|
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.
Hallvard, is that what you are saying?
Jim >>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 12/18/03 4:57:40 PM >>> At 12:27 PM 12/18/2003, Jim Sermersheim wrote: >>>> 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. The control specification should detail any particular criticality requirements it has on how controls should be generated but should not detail any criticality requirements on how controls should be processed by the receiver. The latter needs to be covered in protocol. Kurt |