IETF Logo Mail Archive

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

"Vijay K. Gurbani" <vkg@bell-labs.com> Mon, 12 March 2012 14:44 UTC

Return-Path: <vkg@bell-labs.com>
X-Original-To: sip-overload@ietfa.amsl.com
Delivered-To: sip-overload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2788121E8035 for <sip-overload@ietfa.amsl.com>; Mon, 12 Mar 2012 07:44:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.487
X-Spam-Level:
X-Spam-Status: No, score=-108.487 tagged_above=-999 required=5 tests=[AWL=1.196, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_OBFU_COULD=0.917, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X-BJk8uYonjX for <sip-overload@ietfa.amsl.com>; Mon, 12 Mar 2012 07:44:24 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id A26CF21E8040 for <sip-overload@ietf.org>; Mon, 12 Mar 2012 07:44:22 -0700 (PDT)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id q2CEiLjA015134 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <sip-overload@ietf.org>; Mon, 12 Mar 2012 09:44:21 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q2CEiLNE006440 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <sip-overload@ietf.org>; Mon, 12 Mar 2012 09:44:21 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q2CEiLnX022877 for <sip-overload@ietf.org>; Mon, 12 Mar 2012 09:44:21 -0500 (CDT)
Message-ID: <4F5E0CD7.2030703@bell-labs.com>
Date: Mon, 12 Mar 2012 09:48:55 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.1) Gecko/20120209 Thunderbird/10.0.1
MIME-Version: 1.0
To: sip-overload@ietf.org
References: <CALiegfnp8fLw02LJGDBgbDziLHtMq0sw=Q+o7SikhTF1WBksPA@mail.gmail.com> <OF1F28F0B4.238DD4A8-ON852579BD.005A9170-852579BD.005AC1F5@csc.com> <CALiegf=mgFnJEW6jE2J-QpXRV-5ss4cVgW0Fx0Np_psJYHD7+A@mail.gmail.com>
In-Reply-To: <CALiegf=mgFnJEW6jE2J-QpXRV-5ss4cVgW0Fx0Np_psJYHD7+A@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Subject: Re: [sip-overload] draft-ietf-soc-overload-control-07 - Too much "MUST"?
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-overload>, <mailto:sip-overload-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-overload>
List-Post: <mailto:sip-overload@ietf.org>
List-Help: <mailto:sip-overload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-overload>, <mailto:sip-overload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Mar 2012 14:44:28 -0000

On 03/11/2012 10:56 AM, Iñaki Baz Castillo wrote:
> Ok, but maybe section 2 should describe a bit what "SIP client" and
> "SIP server" means. A "SIP client" implementing overload control could
> be a SIP proxy or a SIP UAC (B2BUA or whatever), and a "SIP server"
> coould be a SIP proxy or a SIP UAS (B2BUA, gateway...).

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.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

v2.23.0 | Report a Bug | By Email