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

Janet P Gunn <jgunn6@csc.com> Thu, 21 February 2013 22:20 UTC

Return-Path: <jgunn6@csc.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 288B421E8098; Thu, 21 Feb 2013 14:20:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.791
X-Spam-Level:
X-Spam-Status: No, score=-6.791 tagged_above=-999 required=5 tests=[AWL=-0.193, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q1hYqghb4MNw; Thu, 21 Feb 2013 14:20:30 -0800 (PST)
Received: from mail171.messagelabs.com (mail171.messagelabs.com [216.82.253.243]) by ietfa.amsl.com (Postfix) with ESMTP id DB35F21E8093; Thu, 21 Feb 2013 14:20:29 -0800 (PST)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-7.tower-171.messagelabs.com!1361485228!17405266!1
X-Originating-IP: [20.137.2.88]
X-StarScan-Received:
X-StarScan-Version: 6.8.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8379 invoked from network); 21 Feb 2013 22:20:29 -0000
Received: from amer-mta102.csc.com (HELO amer-mta102.csc.com) (20.137.2.88) by server-7.tower-171.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 21 Feb 2013 22:20:29 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta102.csc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r1LMKRnc029819; Thu, 21 Feb 2013 17:20:27 -0500
In-Reply-To: <51189F14.6050405@ericsson.com>
References: <51110A56.7030402@ericsson.com> <51189F14.6050405@ericsson.com>
To: Salvatore Loreto <salvatore.loreto@ericsson.com>
MIME-Version: 1.0
X-KeepSent: 9BD195B0:FEE31A3A-85257B19:007A01D4; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP4 SHF97 March 26, 2012
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF9BD195B0.FEE31A3A-ON85257B19.007A01D4-85257B19.007AB86B@csc.com>
Date: Thu, 21 Feb 2013 17:20:25 -0500
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 02/21/2013 05:15:12 PM, Serialize complete at 02/21/2013 05:15:12 PM
Content-Type: multipart/alternative; boundary="=_alternative 007AB82585257B19_="
Cc: sip-overload-bounces@ietf.org, Volker Hilt <volker.hilt@alcatel-lucent.com>, "sip-overload@ietf.org" <sip-overload@ietf.org>
Subject: [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: Thu, 21 Feb 2013 22:20:31 -0000

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."

Janet




From:   Salvatore Loreto <salvatore.loreto@ericsson.com>
To:     "sip-overload@ietf.org" <sip-overload@ietf.org>
Cc:     Volker Hilt <volker.hilt@alcatel-lucent.com>
Date:   02/11/2013 02:35 AM
Subject:        Re: [sip-overload] WG Last Call for 
draft-ietf-soc-overload-control-12
Sent by:        sip-overload-bounces@ietf.org



this is just a reminder for this WG Last Call

I haven't seen yet any comment or feedback 
please we really need you spend some time to reading and reviewing the 
draft

thanks a lot
Salvatore

On 2/5/13 3:34 PM, Salvatore Loreto wrote:
Dear WG partecipants, 


Volker and I would like to initiate a second 2 weeks WG Last Call on 
draft-ietf-soc-overload-control-12 (" Session Initiation Protocol (SIP) 
Overload Control") 
http://tools.ietf.org/id/draft-ietf-soc-overload-control-12.txt

The first WGLC that we run ( 
http://www.ietf.org/mail-archive/web/sip-overload/current/msg00731.html )
has produced a significant amount of feedback and comments that have been 
discussed and addressed in subsequent versions

Please send your reviews, as well as expression of support regarding 
document readiness for IESG (or not) either to the *soc* mailing list (
sip-overload@ietf.org), 
or directly to the WG chairs (Murray Kucherawy and myself). 

Comments like "I've read the document and it is Ok to publish" or 
"I've read the document and it has the following issues"
are useful and would be gratefully accepted by chairs. 


The WG LC will end on Friday, February 19th. 


Thank you, 
Salvatore as an SoC co-chair. 


_______________________________________________
sip-overload mailing list
sip-overload@ietf.org
https://www.ietf.org/mailman/listinfo/sip-overload