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

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

2012/3/12 Vijay K. Gurbani <[e-mail]>:
> Inaki: Thanks for your feedback.  Based on your and Janet's
> conversation, I propose to add the following in Section 2:
>
>  Note that the terms "SIP client" and "SIP server" are used
>  in their generic forms.  Thus, a "SIP client" could refer to
>  the client transaction state machine in a SIP proxy or it
>  could refer to a user agent client.  Similarly, a "SIP server"
>  could be a user agent server or the server transaction state
>  machine in a proxy.  Various permutations of this are also
>  possible, for instance, SIP clients and servers could also be
>  part of back-to-back user agents (B2BUAs) or gateways.
>
>  However, irrespective of the context (i.e., proxy, B2BUA, UAS,
>  UAC), "SIP client" applies to any SIP entity that provides
>  overload control to traffic destined downstream.  Similarly,
>  "SIP server" applies to any SIP entity that is experiencing
>  overload and would like its upstream neighbour to throttle
>  incoming traffic.
>
> Hope that helps.

It's clear now. Thanks a lot.

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