[sip-overload] draft-ietf-soc-overload-control-07 - Too much "MUST"?

[Iñaki Baz Castillo <[e-mail]>]

Hi, as an initial reading of the draft (revision 07) I've found
various cases in which the text says things like:

-------------------------------
4.1.  The oc parameter

   This parameter is inserted by the SIP client and updated by the SIP
   server.

   A SIP client MUST add an "oc" parameter to the topmost Via [...]

   The downstream server MUST add a value to the "oc" parameter in the
   response going upstream.
-------------------------------


Reading that it seems that any SIP client and any SIP server/proxy
should implement this specification. I would suggest a "Terminology"
section in which is stated that this document describes a "SIP client"
as a SIP entity which implements this specification and wants to use
it, and "SIP server" as a SIP proxy or server that implements this
specification and, as well, wants to use it.

There is no "Require/Supported" negotiation mechanism here since
information is just added as Via parameters, so IMHO the document
should relax those "MUST" or clearly explain the scope of them.



-- 
Iñaki Baz Castillo
<[e-mail]>