IETF Logo Mail Archive

Re: [sip-overload] Introduction - "This document defines..." Re: WG Last Call for draft-ietf-soc-overload-control-12

"Vijay K. Gurbani" <vkg@bell-labs.com> Fri, 22 March 2013 15:27 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 A5F0221F86EA for <sip-overload@ietfa.amsl.com>; Fri, 22 Mar 2013 08:27:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 xMZyW7SvUWDs for <sip-overload@ietfa.amsl.com>; Fri, 22 Mar 2013 08:27:53 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 4A80021F86CA for <sip-overload@ietf.org>; Fri, 22 Mar 2013 08:27:52 -0700 (PDT)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id r2MFRijY005039 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 22 Mar 2013 10:27:45 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r2MFRifk026074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 22 Mar 2013 10:27:44 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r2MFRg56001037; Fri, 22 Mar 2013 10:27:42 -0500 (CDT)
Message-ID: <514C7918.4020108@bell-labs.com>
Date: Fri, 22 Mar 2013 10:30:32 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130311 Thunderbird/17.0.4
MIME-Version: 1.0
To: Janet P Gunn <jgunn6@csc.com>
References: <51110A56.7030402@ericsson.com> <51189F14.6050405@ericsson.com> <OF9BD195B0.FEE31A3A-ON85257B19.007A01D4-85257B19.007AB86B@csc.com>
In-Reply-To: <OF9BD195B0.FEE31A3A-ON85257B19.007A01D4-85257B19.007AB86B@csc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: Volker Hilt <volker.hilt@alcatel-lucent.com>, "sip-overload@ietf.org" <sip-overload@ietf.org>
Subject: Re: [sip-overload] Introduction - "This document defines..." Re: WG Last Call for draft-ietf-soc-overload-control-12
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: Fri, 22 Mar 2013 15:27:55 -0000

Janet: Sorry for the delay, circling back to close issues on SOC.

Your suggestion below sounds reasonable.  I will modify the last
paragraph of S1 as you indicate.

On 02/21/2013 04:20 PM, Janet P Gunn wrote:
> OK, finally getting to this.
>
> In section 1, the last paragraph ("this document defines...") seems to
> miss the main point, which is a protocol for COMMUNICATING overload
> information.
>
> Therefore, I would suggest changing
>
>   "  This document defines the general behaviour of SIP servers and
>     clients involved in overload control in Section 5.  In addition,
>     Section 6 specifies a loss-based overload control scheme.  SIP
>     clients and servers conformant to this specification MUST implement
>     the loss-based overload control scheme.  They MAY implement other
>     overload control schemes as well."
>
> to
>
> "   This document defines the protocol for communicating overload
>     information between SIP servers and clients, so that clients can reduce
>     the volume of traffic sent to overloaded servers, avoiding congestion
>     collapse, and increasing usefull throughput. Section 4 describes the
>     Via header parameters used for this communication.  The general
>     behaviour of SIP servers and clients involved in overload control
>    is described in Section 5.  In addition,
>     Section 6 specifies a loss-based overload control scheme.  SIP
>     clients and servers conformant to this specification MUST implement
>     the loss-based overload control scheme.  They MAY implement other
>     overload control schemes as well."

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.8.7 | Report a Bug | By Email