
From internet-drafts@ietf.org  Fri Feb  1 09:56:31 2013
Return-Path: <internet-drafts@ietf.org>
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 3047321E80DA; Fri,  1 Feb 2013 09:56:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.527
X-Spam-Level: 
X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 e9RUkIv7j987; Fri,  1 Feb 2013 09:56:30 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A410021E8084; Fri,  1 Feb 2013 09:56:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.37
Message-ID: <20130201175630.27023.2656.idtracker@ietfa.amsl.com>
Date: Fri, 01 Feb 2013 09:56:30 -0800
Cc: sip-overload@ietf.org
Subject: [sip-overload] I-D Action: draft-ietf-soc-overload-control-12.txt
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, 01 Feb 2013 17:56:31 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the SIP Overload Control Working Group of the=
 IETF.

	Title           : Session Initiation Protocol (SIP) Overload Control
	Author(s)       : Vijay K. Gurbani
                          Volker Hilt
                          Henning Schulzrinne
	Filename        : draft-ietf-soc-overload-control-12.txt
	Pages           : 35
	Date            : 2013-02-01

Abstract:
   Overload occurs in Session Initiation Protocol (SIP) networks when
   SIP servers have insufficient resources to handle all SIP messages
   they receive.  Even though the SIP protocol provides a limited
   overload control mechanism through its 503 (Service Unavailable)
   response code, SIP servers are still vulnerable to overload.  This
   document defines the behaviour of SIP servers involved in overload
   control, and in addition, it specifies a loss-based overload scheme
   for SIP.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-soc-overload-control

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-soc-overload-control-12

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-soc-overload-control-12


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From vkg@bell-labs.com  Fri Feb  1 10:05:09 2013
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 3FE4521E8041 for <sip-overload@ietfa.amsl.com>; Fri,  1 Feb 2013 10:05:09 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oDjtjtXrfQzH for <sip-overload@ietfa.amsl.com>; Fri,  1 Feb 2013 10:05:08 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 89A8821E808F for <sip-overload@ietf.org>; Fri,  1 Feb 2013 10:05:07 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id r11I56SG024655 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <sip-overload@ietf.org>; Fri, 1 Feb 2013 12:05:07 -0600 (CST)
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 r11I56xA010035 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <sip-overload@ietf.org>; Fri, 1 Feb 2013 12:05:06 -0600
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 r11I56Db007531 for <sip-overload@ietf.org>; Fri, 1 Feb 2013 12:05:06 -0600 (CST)
Message-ID: <510C03D1.9060105@bell-labs.com>
Date: Fri, 01 Feb 2013 12:05:05 -0600
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/20130110 Thunderbird/17.0.2
MIME-Version: 1.0
To: "sip-overload@ietf.org" <sip-overload@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Subject: [sip-overload] 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, 01 Feb 2013 18:05:09 -0000

All: I have released version -12 of draft-ietf-soc-overload-control [1].

The only change from -11 is the reflection of list discussions on the
text around local policy and the normative strength around it; please
see [2] for a summary on the eventual settlement of this discussion.

-12 includes the text agreed to on the list.

[1] http://tools.ietf.org/html/draft-ietf-soc-overload-control-12
[1] http://www.ietf.org/mail-archive/web/sip-overload/current/msg00903.html

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/

From internet-drafts@ietf.org  Fri Feb  1 11:17:50 2013
Return-Path: <internet-drafts@ietf.org>
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 797F821F8D41; Fri,  1 Feb 2013 11:17:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.526
X-Spam-Level: 
X-Spam-Status: No, score=-102.526 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Ru0lybZhoc1o; Fri,  1 Feb 2013 11:17:50 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06EAB21F8D46; Fri,  1 Feb 2013 11:17:50 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.37
Message-ID: <20130201191750.25394.67669.idtracker@ietfa.amsl.com>
Date: Fri, 01 Feb 2013 11:17:50 -0800
Cc: sip-overload@ietf.org
Subject: [sip-overload] I-D Action: draft-ietf-soc-load-control-event-package-07.txt
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, 01 Feb 2013 19:17:50 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the SIP Overload Control Working Group of the=
 IETF.

	Title           : A Session Initiation Protocol (SIP) Load Control Event P=
ackage
	Author(s)       : Charles Shen
                          Henning Schulzrinne
                          Arata Koike
	Filename        : draft-ietf-soc-load-control-event-package-07.txt
	Pages           : 40
	Date            : 2013-02-01

Abstract:
   We define a load control event package for the Session Initiation
   Protocol (SIP).  It allows SIP entities to distribute load filtering
   policies to other SIP entities in the network.  The load filtering
   policies contain rules to throttle calls based on their source or
   destination domain, telephone number prefix or for a specific user.
   The mechanism helps to prevent signaling overload and complements
   feedback-based SIP overload control efforts.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-soc-load-control-event-package

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-soc-load-control-event-package-07

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-soc-load-control-event-packag=
e-07


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From charles.newyork@gmail.com  Fri Feb  1 11:27:59 2013
Return-Path: <charles.newyork@gmail.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 3585021E804C for <sip-overload@ietfa.amsl.com>; Fri,  1 Feb 2013 11:27:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 ktVUEDH9psh2 for <sip-overload@ietfa.amsl.com>; Fri,  1 Feb 2013 11:27:58 -0800 (PST)
Received: from mail-oa0-f41.google.com (mail-oa0-f41.google.com [209.85.219.41]) by ietfa.amsl.com (Postfix) with ESMTP id 4AC8321E804A for <sip-overload@ietf.org>; Fri,  1 Feb 2013 11:27:58 -0800 (PST)
Received: by mail-oa0-f41.google.com with SMTP id i10so4597684oag.28 for <sip-overload@ietf.org>; Fri, 01 Feb 2013 11:27:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:from:date:x-google-sender-auth :message-id:subject:to:content-type; bh=qAQG8Z0cGOo+KRwqGgxRUIRzXamE2L24BOccwV1u0AU=; b=m0tUyvhU9RJJDnuKQZEDodIl+wQ8woiHsUflsD0KWTzDIytREMb9ksVp5tFgkz3+ZD yBx15cP9OCIVH3+FvpAidcs0o/48XnTb8r0De9jVof+2WJHp4BEBxATgZm/JYjNbWhEj QWk7nU3hGr6F6HaFZKstD0ZtCO7hzjBVcZyAxi1Kllz43UbWogsYmR2UxbBpUOGyyy0C fgcs+lvO6ZyYebv5t5PnPrihPJ8ufVaNTq7Vudtc7NkOY+B1lWeNT2FfhQL0EaLKAkO9 u2V1B8Vtq8SIEoMTMlHc6jaewAaeB0aZCE7pKkrjqnPCK6LiWPwQrTpVbwxxVH8Jpr89 1Vog==
X-Received: by 10.182.123.78 with SMTP id ly14mr9667101obb.58.1359746877630; Fri, 01 Feb 2013 11:27:57 -0800 (PST)
MIME-Version: 1.0
Sender: charles.newyork@gmail.com
Received: by 10.182.151.82 with HTTP; Fri, 1 Feb 2013 11:27:37 -0800 (PST)
From: Charles Shen <charles@cs.columbia.edu>
Date: Fri, 1 Feb 2013 14:27:37 -0500
X-Google-Sender-Auth: HrvozIPSGFKYLkFWTSEV90M4bYI
Message-ID: <CAPSQ9ZVxSAi5_FMQfa3PzyO_1BHr6BVg6wCSQnF9JgvagPjYqw@mail.gmail.com>
To: sip-overload@ietf.org
Content-Type: text/plain; charset=UTF-8
Subject: [sip-overload] draft-ietf-soc-load-control-event-package-07
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, 01 Feb 2013 19:27:59 -0000

Hi all,

I've submitted an updated version of
draft-ietf-soc-load-control-event-package [1].

The only change from prior version is the reflection of list discussions on the
text around local policy and the normative strength around it; please
see [2] for a summary on the eventual settlement of this discussion.

[1] http://www.ietf.org/id/draft-ietf-soc-load-control-event-package-07.txt

[2] http://www.ietf.org/mail-archive/web/sip-overload/current/msg00903.html

Thanks

Charles

From salvatore.loreto@ericsson.com  Tue Feb  5 05:34:18 2013
Return-Path: <salvatore.loreto@ericsson.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 DEB3F21F869E for <sip-overload@ietfa.amsl.com>; Tue,  5 Feb 2013 05:34:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.248
X-Spam-Level: 
X-Spam-Status: No, score=-106.248 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 azDl96KfQjN8 for <sip-overload@ietfa.amsl.com>; Tue,  5 Feb 2013 05:34:18 -0800 (PST)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 91AC121F8635 for <sip-overload@ietf.org>; Tue,  5 Feb 2013 05:34:17 -0800 (PST)
X-AuditID: c1b4fb30-b7f0d6d000007e61-d7-51110a58ade7
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 5D.52.32353.85A01115; Tue,  5 Feb 2013 14:34:16 +0100 (CET)
Received: from mail.lmf.ericsson.se (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.279.1; Tue, 5 Feb 2013 14:34:16 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id BB5032B24; Tue,  5 Feb 2013 15:34:15 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id CBCC754212; Tue,  5 Feb 2013 15:34:13 +0200 (EET)
Received: from ip-193-234-217-88.guest.ericsson.fi (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 847435413D; Tue,  5 Feb 2013 15:34:13 +0200 (EET)
Message-ID: <51110A56.7030402@ericsson.com>
Date: Tue, 5 Feb 2013 15:34:14 +0200
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "sip-overload@ietf.org" <sip-overload@ietf.org>
Content-Type: multipart/alternative; boundary="------------070707000603080105060608"
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrCLMWRmVeSWpSXmKPExsUyM+JvrW4El2Cgwff9Khb7nyZYzNu/h9WB yaP12V5WjyVLfjIFMEVx2aSk5mSWpRbp2yVwZTz+u4q94L9kxdy2HywNjDNEuxg5OSQETCQW b2thgbDFJC7cW8/WxcjFISRwklFiQfM+dpCEkMB6RomFR5khErsYJd7NfcYC4axllJh4r40J wtnGKPH67XomkBZeAW2Jmcevg9ksAioSjev3g+1gEzCTeP5wCzOILSqQLPHxzjVWiHpBiZMz n4DViAgYSxx5vIURxGYWMJD4/HgXWI2wgI3ErafPgE7iAIqHSRycVwJxtprE1XObmCEu1ZLo PdvJNIFRaBaSqbMQOmaBDbWVuDDnOguELS+x/e0cZghbV+LC/yko4gsY2VYxsucmZuakl5tv YgSG/MEtvw12MG66L3aIUZqDRUmcN9z1QoCQQHpiSWp2ampBalF8UWlOavEhRiYOTqkGRqf7 /Dc6Ek4ky51cln307AE9VullwkkLuuYoqETGTJdkcnKJfNn20/ttFNeKC33i61UmBb49ltz2 TFddVv2tm9zSxQ6d03W2a0h8C2gJvzTB+LPXxS+LPnG9fSVlWZ22d+VGFSt2lYq1Eb2stxYZ yoqHPp2j9U/Na3vYzpVL6s/acmes+LZ5uxJLcUaioRZzUXEiAGPPMkdHAgAA
Cc: Volker Hilt <volker.hilt@alcatel-lucent.com>
Subject: [sip-overload] 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: Tue, 05 Feb 2013 13:34:19 -0000

--------------070707000603080105060608
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

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.


--------------070707000603080105060608
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Dear WG partecipants, <br>
    <br>
    <br>
    Volker and I would like to initiate a second 2 weeks WG Last Call on
    <br>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    draft-ietf-soc-overload-control-12<span class="h1"></span>&nbsp;("
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    Session Initiation Protocol (SIP) Overload Control") <br>
    <a class="moz-txt-link-freetext" href="http://tools.ietf.org/id/draft-ietf-soc-overload-control-12.txt">http://tools.ietf.org/id/draft-ietf-soc-overload-control-12.txt</a><br>
    <br>
    The first WGLC that we run (
    <a class="moz-txt-link-freetext" href="http://www.ietf.org/mail-archive/web/sip-overload/current/msg00731.html">http://www.ietf.org/mail-archive/web/sip-overload/current/msg00731.html</a>
    )<br>
    has produced a significant amount of feedback and comments that have
    been discussed and addressed in subsequent versions<br>
    <br>
    Please send your reviews, as well as expression of support regarding
    <br>
    document readiness for IESG (or not) either to the <b
      class="moz-txt-star"><span class="moz-txt-tag">*soc</span><span
        class="moz-txt-tag">*</span></b> mailing list
    (<a class="moz-txt-link-abbreviated" href="mailto:sip-overload@ietf.org">sip-overload@ietf.org</a>), <br>
    or directly to the WG chairs (Murray Kucherawy and myself). <br>
    <br>
    Comments like "I've read the document and it is Ok to publish" or <br>
    "I've read the document and it has the following issues"<br>
    are useful and would be gratefully accepted by chairs. <br>
    <br>
    <br>
    The WG LC will end on Friday, February 19th. <br>
    <br>
    <br>
    Thank you, <br>
    Salvatore as an SoC co-chair. <br>
    <br>
  </body>
</html>

--------------070707000603080105060608--

From salvatore.loreto@ericsson.com  Sun Feb 10 23:34:53 2013
Return-Path: <salvatore.loreto@ericsson.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 736E121F8808 for <sip-overload@ietfa.amsl.com>; Sun, 10 Feb 2013 23:34:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.248
X-Spam-Level: 
X-Spam-Status: No, score=-106.248 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 Y0kiKeeUoFi1 for <sip-overload@ietfa.amsl.com>; Sun, 10 Feb 2013 23:34:51 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 9C74B21F87E1 for <sip-overload@ietf.org>; Sun, 10 Feb 2013 23:34:48 -0800 (PST)
X-AuditID: c1b4fb2d-b7f316d0000028db-3d-51189f1763d8
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id BF.CA.10459.71F98115; Mon, 11 Feb 2013 08:34:47 +0100 (CET)
Received: from mail.lmf.ericsson.se (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.279.1; Mon, 11 Feb 2013 08:34:47 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 189782ACC; Mon, 11 Feb 2013 09:34:47 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id F20305431F; Mon, 11 Feb 2013 09:34:44 +0200 (EET)
Received: from n106.nomadiclab.com (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id A80B553C95; Mon, 11 Feb 2013 09:34:43 +0200 (EET)
Message-ID: <51189F14.6050405@ericsson.com>
Date: Mon, 11 Feb 2013 09:34:44 +0200
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "sip-overload@ietf.org" <sip-overload@ietf.org>
References: <51110A56.7030402@ericsson.com>
In-Reply-To: <51110A56.7030402@ericsson.com>
Content-Type: multipart/alternative; boundary="------------090401020606050900000908"
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrFLMWRmVeSWpSXmKPExsUyM+Jvja74fIlAgyV39S32P02wmLd/D6sD k0frs72sHkuW/GQKYIrisklJzcksSy3St0vgypi0ILdgrVLFl50uDYwXpLoYOTkkBEwkti2c wAxhi0lcuLeerYuRi0NI4CSjxLX3h5khnA2MEqe/LmaHcHYxSizafZ0VpEVIYC2jxJZjFhCJ ZYwSTXcfMYEkeAW0Jc6//soOYrMIqEqc3PwXbAebgJnE84dbwGxRgWSJj3eusULUC0qcnPmE BcQWETCWOPJ4CyOIzSxgIPH58S6wGmEBB4nJj54zQSzWlvgx4zTYHE4BHYl/myYC1XAA1YdJ bGsMgHhHTeLquU3MEOVaEr1nO5kmMIrMQrJtFkLHLLBlthIX5lxngbDlJba/ncMMYetKXPg/ BUV8ASPbKkb23MTMnPRyw02MwPg4uOW37g7GU+dEDjFKc7AoifOGuV4IEBJITyxJzU5NLUgt ii8qzUktPsTIxMEp1cDIuJJB+kkAG9e7JusSx/v5eS+fLSjui1YSf6eSNX9/x4Tj7i2tc9wL Z7v9q/IWMT1YLSPXESewXqHAjr/8UfuzB2zPBIyj5p/c2fWnrK+GK12SOUzGYWL2X5aPk/ee OcnS2u+yLKslbWp16Ydk28j79RHGF1OXvQtUuTZJ/vnp/aeCG3r/ZyuxFGckGmoxFxUnAgBi oJwMXQIAAA==
Cc: Volker Hilt <volker.hilt@alcatel-lucent.com>
Subject: Re: [sip-overload] 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: Mon, 11 Feb 2013 07:34:53 -0000

--------------090401020606050900000908
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

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



--------------090401020606050900000908
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">this is just a reminder for this WG
      Last Call<br>
      <br>
      I haven't seen yet any comment or feedback <br>
      please we really need you spend some time to reading and reviewing
      the draft<br>
      <br>
      thanks a lot<br>
      Salvatore<br>
      <br>
      On 2/5/13 3:34 PM, Salvatore Loreto wrote:<br>
    </div>
    <blockquote cite="mid:51110A56.7030402@ericsson.com" type="cite">
      <meta http-equiv="content-type" content="text/html;
        charset=ISO-8859-1">
      Dear WG partecipants, <br>
      <br>
      <br>
      Volker and I would like to initiate a second 2 weeks WG Last Call
      on <br>
      <meta http-equiv="content-type" content="text/html;
        charset=ISO-8859-1">
      draft-ietf-soc-overload-control-12<span class="h1"></span>&nbsp;("
      <meta http-equiv="content-type" content="text/html;
        charset=ISO-8859-1">
      Session Initiation Protocol (SIP) Overload Control") <br>
      <a moz-do-not-send="true" class="moz-txt-link-freetext"
        href="http://tools.ietf.org/id/draft-ietf-soc-overload-control-12.txt">http://tools.ietf.org/id/draft-ietf-soc-overload-control-12.txt</a><br>
      <br>
      The first WGLC that we run ( <a moz-do-not-send="true"
        class="moz-txt-link-freetext"
href="http://www.ietf.org/mail-archive/web/sip-overload/current/msg00731.html">http://www.ietf.org/mail-archive/web/sip-overload/current/msg00731.html</a>
      )<br>
      has produced a significant amount of feedback and comments that
      have been discussed and addressed in subsequent versions<br>
      <br>
      Please send your reviews, as well as expression of support
      regarding <br>
      document readiness for IESG (or not) either to the <b
        class="moz-txt-star"><span class="moz-txt-tag">*soc</span><span
          class="moz-txt-tag">*</span></b> mailing list (<a
        moz-do-not-send="true" class="moz-txt-link-abbreviated"
        href="mailto:sip-overload@ietf.org">sip-overload@ietf.org</a>),
      <br>
      or directly to the WG chairs (Murray Kucherawy and myself). <br>
      <br>
      Comments like "I've read the document and it is Ok to publish" or
      <br>
      "I've read the document and it has the following issues"<br>
      are useful and would be gratefully accepted by chairs. <br>
      <br>
      <br>
      The WG LC will end on Friday, February 19th. <br>
      <br>
      <br>
      Thank you, <br>
      Salvatore as an SoC co-chair. <br>
      <br>
    </blockquote>
    <br>
    <br>
  </body>
</html>

--------------090401020606050900000908--

From bruno.chatras@orange.com  Mon Feb 11 00:59:23 2013
Return-Path: <bruno.chatras@orange.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 7A7DE21F8652 for <sip-overload@ietfa.amsl.com>; Mon, 11 Feb 2013 00:59:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level: 
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=0.001]
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 uWlo4QbOeEtO for <sip-overload@ietfa.amsl.com>; Mon, 11 Feb 2013 00:59:21 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id A28B621F8651 for <sip-overload@ietf.org>; Mon, 11 Feb 2013 00:59:20 -0800 (PST)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 3637C18C7C4; Mon, 11 Feb 2013 09:59:19 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id D5F0F4C06E; Mon, 11 Feb 2013 09:59:18 +0100 (CET)
Received: from PEXCVZYM12.corporate.adroot.infra.ftgroup ([fe80::81f:1640:4749:5d13]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0318.004; Mon, 11 Feb 2013 09:59:18 +0100
From: <bruno.chatras@orange.com>
To: Salvatore Loreto <salvatore.loreto@ericsson.com>, "sip-overload@ietf.org" <sip-overload@ietf.org>
Thread-Topic: [sip-overload] WG Last Call for draft-ietf-soc-overload-control-12
Thread-Index: AQHOCCpKMCudLkwQDU6Apb8zyPCouJh0Wc8w
Date: Mon, 11 Feb 2013 08:59:17 +0000
Message-ID: <20305_1360573159_5118B2E6_20305_1921_3_88CAD1D4E8773F42858B58CAA28272A0109278@PEXCVZYM12.corporate.adroot.infra.ftgroup>
References: <51110A56.7030402@ericsson.com> <51189F14.6050405@ericsson.com>
In-Reply-To: <51189F14.6050405@ericsson.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.3]
Content-Type: multipart/alternative; boundary="_000_88CAD1D4E8773F42858B58CAA28272A0109278PEXCVZYM12corpora_"
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.10.24.110314
Cc: Volker Hilt <volker.hilt@alcatel-lucent.com>
Subject: Re: [sip-overload] 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: Mon, 11 Feb 2013 08:59:23 -0000

--_000_88CAD1D4E8773F42858B58CAA28272A0109278PEXCVZYM12corpora_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I just have one comment:

Section 5.10.2 says that the response sent by a SIP server to non-participa=
nts clients in case of overload is a 503 without the Retry-After header. I =
did not find any text about the response sent by participating clients when=
 they have to reject a request. I assume they should send a 503 without the=
 Retry-After header as well. I would suggest adding the following sentence =
at the end of 5.10, after "it will need to reject these requests": In such =
cases, the SIP client shall reply to the requests with a 503 response witho=
ut the Retry-After header.

BC


De : sip-overload-bounces@ietf.org [mailto:sip-overload-bounces@ietf.org] D=
e la part de Salvatore Loreto
Envoy=E9 : lundi 11 f=E9vrier 2013 08:35
=C0 : sip-overload@ietf.org
Cc : Volker Hilt
Objet : Re: [sip-overload] WG Last Call for draft-ietf-soc-overload-control=
-12

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) Ove=
rload 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-overl=
oad/current/msg00731.html )
has produced a significant amount of feedback and comments that have been d=
iscussed 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<mailto: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.


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


--_000_88CAD1D4E8773F42858B58CAA28272A0109278PEXCVZYM12corpora_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.h1
	{mso-style-name:h1;}
span.moz-txt-tag
	{mso-style-name:moz-txt-tag;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=3D"white" lang=3D"FR" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">I just hav=
e one comment:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Section 5.=
10.2 says that the response sent by a SIP server to non-participants client=
s in case of overload is a 503 without the Retry-After header.
 I did not find any text about the response sent by participating clients w=
hen they have to reject a request. I assume they should send a 503 without =
the Retry-After header as well. I would suggest adding the following senten=
ce at the end of 5.10, after &#8220;it
 will need to reject these requests&#8221;: In such cases, the SIP client s=
hall reply to the requests with a 503 response without the Retry-After head=
er.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">BC<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">De&nbsp;:</span></b>=
<span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-s=
erif&quot;;color:windowtext"> sip-overload-bounces@ietf.org [mailto:sip-ove=
rload-bounces@ietf.org]
<b>De la part de</b> Salvatore Loreto<br>
<b>Envoy=E9&nbsp;:</b> lundi 11 f=E9vrier 2013 08:35<br>
<b>=C0&nbsp;:</b> sip-overload@ietf.org<br>
<b>Cc&nbsp;:</b> Volker Hilt<br>
<b>Objet&nbsp;:</b> Re: [sip-overload] WG Last Call for draft-ietf-soc-over=
load-control-12<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">this is just a reminder for this WG Last Call<br>
<br>
I haven't seen yet any comment or feedback <br>
please we really need you spend some time to reading and reviewing the draf=
t<br>
<br>
thanks a lot<br>
Salvatore<br>
<br>
On 2/5/13 3:34 PM, Salvatore Loreto wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Dear WG partecipants,=
 <br>
<br>
<br>
Volker and I would like to initiate a second 2 weeks WG Last Call on <br>
draft-ietf-soc-overload-control-12&nbsp;(&quot; Session Initiation Protocol=
 (SIP) Overload Control&quot;)
<br>
<a href=3D"http://tools.ietf.org/id/draft-ietf-soc-overload-control-12.txt"=
>http://tools.ietf.org/id/draft-ietf-soc-overload-control-12.txt</a><br>
<br>
The first WGLC that we run ( <a href=3D"http://www.ietf.org/mail-archive/we=
b/sip-overload/current/msg00731.html">
http://www.ietf.org/mail-archive/web/sip-overload/current/msg00731.html</a>=
 )<br>
has produced a significant amount of feedback and comments that have been d=
iscussed and addressed in subsequent versions<br>
<br>
Please send your reviews, as well as expression of support regarding <br>
document readiness for IESG (or not) either to the <span class=3D"moz-txt-t=
ag"><b>*soc*</b></span> mailing list (<a href=3D"mailto:sip-overload@ietf.o=
rg">sip-overload@ietf.org</a>),
<br>
or directly to the WG chairs (Murray Kucherawy and myself). <br>
<br>
Comments like &quot;I've read the document and it is Ok to publish&quot; or=
 <br>
&quot;I've read the document and it has the following issues&quot;<br>
are useful and would be gratefully accepted by chairs. <br>
<br>
<br>
The WG LC will end on Friday, February 19th. <br>
<br>
<br>
Thank you, <br>
Salvatore as an SoC co-chair. <o:p></o:p></p>
</blockquote>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
</div>
</div>
<PRE>______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.
</PRE></body>
</html>

--_000_88CAD1D4E8773F42858B58CAA28272A0109278PEXCVZYM12corpora_--

From atle.monrad@ericsson.com  Fri Feb 15 13:52:37 2013
Return-Path: <atle.monrad@ericsson.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 2680321E803C for <sip-overload@ietfa.amsl.com>; Fri, 15 Feb 2013 13:52:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.248
X-Spam-Level: 
X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 PhS7sze+bzVT for <sip-overload@ietfa.amsl.com>; Fri, 15 Feb 2013 13:52:36 -0800 (PST)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 0B56721E8047 for <sip-overload@ietf.org>; Fri, 15 Feb 2013 13:52:33 -0800 (PST)
X-AuditID: c1b4fb30-b7f0d6d000007e61-b8-511eae200aad
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 1D.FA.32353.02EAE115; Fri, 15 Feb 2013 22:52:33 +0100 (CET)
Received: from ESESSMB203.ericsson.se ([169.254.3.65]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.02.0318.004; Fri, 15 Feb 2013 22:52:32 +0100
From: Atle Monrad <atle.monrad@ericsson.com>
To: "sip-overload@ietf.org" <sip-overload@ietf.org>
Thread-Topic: [sip-overload] WG Last Call for draft-ietf-soc-overload-control-12
Thread-Index: AQHOCCpNJrfjPBGi6kGoJYBve6LVbZh0flrQgAbQleA=
Date: Fri, 15 Feb 2013 21:52:30 +0000
Message-ID: <7D2F7D7ADBA812449F25F4A69922881C066214@ESESSMB203.ericsson.se>
References: <51110A56.7030402@ericsson.com> <51189F14.6050405@ericsson.com> <E42CCDDA6722744CB241677169E8365602002006@MISOUT7MSGUSR9I.ITServices.sbc.com>
In-Reply-To: <E42CCDDA6722744CB241677169E8365602002006@MISOUT7MSGUSR9I.ITServices.sbc.com>
Accept-Language: nb-NO, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.18]
Content-Type: multipart/alternative; boundary="_000_7D2F7D7ADBA812449F25F4A69922881C066214ESESSMB203ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrDLMWRmVeSWpSXmKPExsUyM+Jvja7iOrlAg67LbBb7nyY4MHosWfKT KYAxissmJTUnsyy1SN8ugSvj16dbjAWPIysa7i9namB85NvFyMkhIWAicWfmBSYIW0ziwr31 bF2MXBxCAocYJdZ9XMEO4SxmlDiy4zkLSBWbgI7EuZ93WEFsEQFjiSOPtzCC2MICgRJr301l g4gHSfS0LGGEsK0kZt1dAFbPIqAqseDQdrA4r4C3xJrnu1ggFsxmlJi3ZiZYEadAlMSWIzuY uxg5OBgFZCXmNvGChJkFxCVuPZkPdamAxJI955khbFGJl4//sULYihIfX+1jBGllFsiXuPkj CmKVoMTJmU9YJjCKzEIyaRZC1SwkVRAlOhILdn9ig7C1JZYtfM0MY5858JgJWXwBI/sqRvbc xMyc9HLzTYzAGDm45bfBDsZN98UOMUpzsCiJ84a7XggQEkhPLEnNTk0tSC2KLyrNSS0+xMjE wSnVwCgg+dJOPv+yfaQS4+G7GnP93RT5Q8+xHHZ/HBO1fU5EZIcm204/zY1iex0keLYy7oo4 7cev90SV58E6Px2f4z9etsV92D7xq1BnVO2pbYH+zTNSLc/wZrgeNN7/31x4hUO16y8piw8v pVV/HdObUniHRdCpdKfZ7j/758bsLpZP+3AhZ4sGpxJLcUaioRZzUXEiAD7e9nFfAgAA
Subject: Re: [sip-overload] 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, 15 Feb 2013 21:52:37 -0000

--_000_7D2F7D7ADBA812449F25F4A69922881C066214ESESSMB203ericsso_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

G'day

The draft is a 3GPP Rel-11 dependency that I support going forward.

I've read through the draft and have no real comments.

However, I find the statement in section 5.10.2 a bit odd

  .... It would be fair to devote the same amount
   of processing at the overloaded server to the combination of
   rejection and processing from a non-participating client as the
   overloaded server would devote to processing requests from a
   participating client.  This is to ensure that SIP clients that do not
   support this specification don't receive an unfair advantage over
   those that do.
Personally I would have used a term like "local policy" for such decisions =
and not the current guidance given in a the current "fair to devote" fashio=
n ...

I'd like to see the draft progressing.

thanks
/atle

________________________________


Atle Monrad
3GPP CT Chairman
Standardization and Regulation,
Group Function Technology and Portfolio Management
Ericsson


From: sip-overload-bounces@ietf.org [mailto:sip-overload-bounces@ietf.org] =
On Behalf Of Salvatore Loreto
Sent: Monday, February 11, 2013 2:35 AM
To: sip-overload@ietf.org
Cc: Volker Hilt
Subject: Re: [sip-overload] WG Last Call for draft-ietf-soc-overload-contro=
l-12

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 draf=
t

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) Ove=
rload 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-overl=
oad/current/msg00731.html )
has produced a significant amount of feedback and comments that have been d=
iscussed 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<mailto: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.


--_000_7D2F7D7ADBA812449F25F4A69922881C066214ESESSMB203ericsso_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v=3D"urn:schemas-micr=
osoft-com:vml" xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=
=3D"urn:schemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.micros=
oft.com/office/2004/12/omml">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"GENERATOR" content=3D"MSHTML 9.00.8112.16457">
<style>@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; COLOR: black;=
 FONT-SIZE: 12pt
}
LI.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; COLOR: black;=
 FONT-SIZE: 12pt
}
DIV.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; COLOR: black;=
 FONT-SIZE: 12pt
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.h1 {
	mso-style-name: h1
}
SPAN.moz-txt-tag {
	mso-style-name: moz-txt-tag
}
SPAN.EmailStyle19 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: perso=
nal-reply
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.WordSection1 {
	page: WordSection1
}
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" bgcolor=3D"white" vlink=3D"purple" link=3D"blue">
<div><font color=3D"#0000ff" size=3D"2" face=3D"Arial"><span class=3D"26200=
0719-15022013">G'day</span></font></div>
<div><font color=3D"#0000ff" size=3D"2" face=3D"Arial"><span class=3D"26200=
0719-15022013"></span></font>&nbsp;</div>
<div><font color=3D"#0000ff" size=3D"2" face=3D"Arial"><span class=3D"26200=
0719-15022013">The draft is a 3GPP Rel-11 dependency that I support going f=
orward.</span></font></div>
<div><font color=3D"#0000ff" size=3D"2" face=3D"Arial"></font>&nbsp;</div>
<div><font color=3D"#0000ff" size=3D"2" face=3D"Arial"><span class=3D"26200=
0719-15022013">I've read through the draft and have no&nbsp;real&nbsp;comme=
nts.</span></font></div>
<div><font color=3D"#0000ff" size=3D"2" face=3D"Arial"><span class=3D"26200=
0719-15022013"></span></font>&nbsp;</div>
<div><font color=3D"#0000ff" size=3D"2" face=3D"Arial"><span class=3D"26200=
0719-15022013">However, I find the statement in section 5.10.2 a bit odd
</span></font></div>
<div><font color=3D"#0000ff" size=3D"2" face=3D"Arial"></font><font color=
=3D"#0000ff" size=3D"2" face=3D"Arial"></font><font color=3D"#0000ff" size=
=3D"2" face=3D"Arial"></font><br>
&nbsp;&nbsp;<span class=3D"262000719-15022013">....</span> It would be fair=
 to devote the same amount<br>
&nbsp;&nbsp; of processing at the overloaded server to the combination of<b=
r>
&nbsp;&nbsp; rejection and processing from a non-participating client as th=
e<br>
&nbsp;&nbsp; overloaded server would devote to processing requests from a<b=
r>
&nbsp;&nbsp; participating client.&nbsp; This is to ensure that SIP clients=
 that do not<br>
&nbsp;&nbsp; support this specification don't receive an unfair advantage o=
ver<br>
&nbsp;&nbsp; those that do.<br>
</div>
<div><font color=3D"#0000ff" size=3D"2" face=3D"Arial"><span class=3D"26200=
0719-15022013">Personally I would have used a term like &quot;local policy&=
quot; for such decisions and not the&nbsp;current guidance given in&nbsp;a =
the current &quot;fair to devote&quot; fashion&nbsp;...</span></font></div>
<div><font color=3D"#0000ff" size=3D"2" face=3D"Arial"></font>&nbsp;</div>
<div><font color=3D"#0000ff" size=3D"2" face=3D"Arial"><span class=3D"26200=
0719-15022013">I'd like to see the draft progressing.</span></font></div>
<div><font color=3D"#0000ff" size=3D"2" face=3D"Arial"><span class=3D"26200=
0719-15022013"></span></font>&nbsp;</div>
<div><font color=3D"#0000ff" size=3D"2" face=3D"Arial"><span class=3D"26200=
0719-15022013">thanks</span></font></div>
<div><font color=3D"#0000ff" size=3D"2" face=3D"Arial"><span class=3D"26200=
0719-15022013">/atle</span></font></div>
<font face=3D"Arial">
<p align=3D"left"><font size=3D"2"><b><span lang=3D"no"><font face=3D"Arial=
">________________________________</font></span></b><span lang=3D"no"><font=
 face=3D"Arial">
</font></span><br>
<br>
<br>
</font><span lang=3D"no"><font size=3D"2"><b><font face=3D"Arial">Atle Monr=
ad</font></b><br>
</font><font size=3D"2"><font face=3D"Arial">3GPP CT Chairman<br>
Standardization and Regulation,<br>
Group Function Technology and Portfolio Management</font><font face=3D"Time=
s New Roman">
</font></font></span><br>
<span lang=3D"no"><font size=3D"2" face=3D"Arial">Ericsson</font></span></f=
ont></p>
<br>
<div dir=3D"ltr" lang=3D"en-us" class=3D"OutlookMessageHeader" align=3D"lef=
t">
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Calibri','sans-serif'; =
COLOR: #1f497d; FONT-SIZE: 11pt"><o:p></o:p></span></p>
<span style=3D"FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SI=
ZE: 11pt"><o:p><font color=3D"#0000ff" size=3D"2" face=3D"Arial"></font>&nb=
sp;</o:p></span></div>
<div class=3D"WordSection1">
<div>
<div style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING=
-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1p=
t solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<p class=3D"MsoNormal"><b><span style=3D"FONT-FAMILY: 'Tahoma','sans-serif'=
; COLOR: windowtext; FONT-SIZE: 10pt">From:</span></b><span style=3D"FONT-F=
AMILY: 'Tahoma','sans-serif'; COLOR: windowtext; FONT-SIZE: 10pt"> sip-over=
load-bounces@ietf.org [mailto:sip-overload-bounces@ietf.org]
<b>On Behalf Of </b>Salvatore Loreto<br>
<b>Sent:</b> Monday, February 11, 2013 2:35 AM<br>
<b>To:</b> sip-overload@ietf.org<br>
<b>Cc:</b> Volker Hilt<br>
<b>Subject:</b> Re: [sip-overload] WG Last Call for draft-ietf-soc-overload=
-control-12<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">this is just a reminder for this WG Last Call<br>
<br>
I haven't seen yet any comment or feedback <br>
please we really need you spend some time to reading and reviewing the draf=
t<br>
<br>
thanks a lot<br>
Salvatore<br>
<br>
On 2/5/13 3:34 PM, Salvatore Loreto wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt">
<p style=3D"MARGIN-BOTTOM: 12pt" class=3D"MsoNormal">Dear WG partecipants, =
<br>
<br>
<br>
Volker and I would like to initiate a second 2 weeks WG Last Call on <br>
draft-ietf-soc-overload-control-12&nbsp;(&quot; Session Initiation Protocol=
 (SIP) Overload Control&quot;)
<br>
<a href=3D"http://tools.ietf.org/id/draft-ietf-soc-overload-control-12.txt"=
>http://tools.ietf.org/id/draft-ietf-soc-overload-control-12.txt</a><br>
<br>
The first WGLC that we run ( <a href=3D"http://www.ietf.org/mail-archive/we=
b/sip-overload/current/msg00731.html">
http://www.ietf.org/mail-archive/web/sip-overload/current/msg00731.html</a>=
 )<br>
has produced a significant amount of feedback and comments that have been d=
iscussed and addressed in subsequent versions<br>
<br>
Please send your reviews, as well as expression of support regarding <br>
document readiness for IESG (or not) either to the <span class=3D"moz-txt-t=
ag"><b>*soc*</b></span> mailing list (<a href=3D"mailto:sip-overload@ietf.o=
rg">sip-overload@ietf.org</a>),
<br>
or directly to the WG chairs (Murray Kucherawy and myself). <br>
<br>
Comments like &quot;I've read the document and it is Ok to publish&quot; or=
 <br>
&quot;I've read the document and it has the following issues&quot;<br>
are useful and would be gratefully accepted by chairs. <br>
<br>
<br>
The WG LC will end on Friday, February 19th. <br>
<br>
<br>
Thank you, <br>
Salvatore as an SoC co-chair. <o:p></o:p></p>
</blockquote>
<p style=3D"MARGIN-BOTTOM: 12pt" class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_7D2F7D7ADBA812449F25F4A69922881C066214ESESSMB203ericsso_--

From ecnoel@research.att.com  Sun Feb 17 14:49:08 2013
Return-Path: <ecnoel@research.att.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 82C6D21F8849 for <sip-overload@ietfa.amsl.com>; Sun, 17 Feb 2013 14:49:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 8XzHRCx2Fqdu for <sip-overload@ietfa.amsl.com>; Sun, 17 Feb 2013 14:49:07 -0800 (PST)
Received: from mail-pink.research.att.com (mail-pink.research.att.com [192.20.225.111]) by ietfa.amsl.com (Postfix) with ESMTP id 8425621F868B for <sip-overload@ietf.org>; Sun, 17 Feb 2013 14:49:07 -0800 (PST)
Received: from mail-green.research.att.com (unknown [135.207.178.10]) by mail-pink.research.att.com (Postfix) with ESMTP id 19130120994; Sun, 17 Feb 2013 17:51:17 -0500 (EST)
Received: from njfpsrvexg2.research.att.com (njfpsrvexg2.research.att.com [135.207.177.29]) by mail-green.research.att.com (Postfix) with ESMTP id 51AC3E36E0; Sun, 17 Feb 2013 17:42:49 -0500 (EST)
Received: from njfpsrvexg2.research.att.com ([fe80::a158:97ea:81b0:43d9]) by njfpsrvexg2.research.att.com ([fe80::a158:97ea:81b0:43d9%14]) with mapi; Sun, 17 Feb 2013 17:49:06 -0500
From: "NOEL, ERIC  (ERIC C)" <ecnoel@research.att.com>
To: Salvatore Loreto <salvatore.loreto@ericsson.com>, "sip-overload@ietf.org" <sip-overload@ietf.org>
Date: Sun, 17 Feb 2013 17:49:06 -0500
Thread-Topic: [sip-overload] WG Last Call for draft-ietf-soc-overload-control-12
Thread-Index: Ac4IKkvhKhhs5fbWS4qQYC7+V29EsAFMIG6n
Message-ID: <5EBD159DE88147488A3B1590E09001840353173DCBC2@njfpsrvexg2.research.att.com>
References: <51110A56.7030402@ericsson.com>,<51189F14.6050405@ericsson.com>
In-Reply-To: <51189F14.6050405@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Volker Hilt <volker.hilt@alcatel-lucent.com>
Subject: Re: [sip-overload] 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: Sun, 17 Feb 2013 22:49:08 -0000

Salvatore,

I read the document and have a few comments:

- Typos:
      + Section 5.4 page 12, second paragraph "... is larger than the value=
 stored value, ...." --> "... is larger than the stored value, ..."
      + Section 6.2 page 18, 7th paragraph, "20% for 1s." --> "20% for 0.5s=
" or "oc-validity=3D500"  --> "oc-validity=3D1000"

- Questions:
      + Section 4.1 page 6, 4th paragraph, why using SHOULD and not MUST to=
 describe the client behavior upon receiving a response with the oc paramet=
ers filled in. This is in contrast with section 5.5 page 12, first paragrap=
h, where a SIP client MUST honor overload control values it receives from d=
ownstream neighbors.
      + Section 4.4 page 8, 4th paragraph, following a sequence number over=
flow, the server must reset the oc-seq parameter. Do we incur the risk of h=
aving the client ignore all server requests with the new oc-seq until oc-va=
lidity expires? Or does the client need to be able to identify when oc-seq =
was reset?=20
      + Section 7, should there be any mention of draft soc-overload-rate-c=
ontrol?
    =20
Thanks,

Eric
________________________________________
From: sip-overload-bounces@ietf.org [sip-overload-bounces@ietf.org] On Beha=
lf Of Salvatore Loreto [salvatore.loreto@ericsson.com]
Sent: Monday, February 11, 2013 2:34 AM
To: sip-overload@ietf.org
Cc: Volker Hilt
Subject: Re: [sip-overload] WG Last Call for    draft-ietf-soc-overload-con=
trol-12

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 draf=
t

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) Ove=
rload 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-overl=
oad/current/msg00731.html )
has produced a significant amount of feedback and comments that have been d=
iscussed 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<mailto: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.




From jgunn6@csc.com  Thu Feb 21 14:20:31 2013
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

This is a multipart message in MIME format.
--=_alternative 007AB82585257B19_=
Content-Type: text/plain; charset="US-ASCII"

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


--=_alternative 007AB82585257B19_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif">OK, finally getting to this.</font>
<br>
<br><font size=2 face="sans-serif">In section 1, the last paragraph (&quot;this
document defines...&quot;) seems to miss the main point, which is a protocol
for COMMUNICATING overload information.</font>
<br>
<br><font size=2 face="sans-serif">Therefore, I would suggest changing</font>
<br>
<br><font size=2 face="sans-serif">&nbsp;&quot; &nbsp;This document defines
the general behaviour of SIP servers and</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;clients involved in overload
control in Section 5. &nbsp;In addition,</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;Section 6 specifies a loss-based
overload control scheme. &nbsp;SIP</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;clients and servers conformant
to this specification MUST implement</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;the loss-based overload
control scheme. &nbsp;They MAY implement other</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;overload control schemes
as well.&quot;</font>
<br>
<br><font size=2 face="sans-serif">to</font>
<br>
<br><font size=2 face="sans-serif">&quot; &nbsp; This document defines
the protocol for communicating overload</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;information between SIP
servers and clients, so that clients can reduce</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;the volume of traffic sent
to overloaded servers, avoiding congestion</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;collapse, and increasing
usefull throughput. Section 4 describes the</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;Via header parameters used
for this communication. &nbsp;The general</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;behaviour of SIP servers
and clients involved in overload control</font>
<br><font size=2 face="sans-serif">&nbsp; is described in Section 5. &nbsp;In
addition,</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;Section 6 specifies a loss-based
overload control scheme. &nbsp;SIP</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;clients and servers conformant
to this specification MUST implement</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;the loss-based overload
control scheme. &nbsp;They MAY implement other</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;overload control schemes
as well.&quot;</font>
<br>
<br><font size=2 face="sans-serif">Janet<br>
</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From: &nbsp; &nbsp; &nbsp;
&nbsp;</font><font size=1 face="sans-serif">Salvatore Loreto &lt;salvatore.loreto@ericsson.com&gt;</font>
<br><font size=1 color=#5f5f5f face="sans-serif">To: &nbsp; &nbsp; &nbsp;
&nbsp;</font><font size=1 face="sans-serif">&quot;sip-overload@ietf.org&quot;
&lt;sip-overload@ietf.org&gt;</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc: &nbsp; &nbsp; &nbsp;
&nbsp;</font><font size=1 face="sans-serif">Volker Hilt &lt;volker.hilt@alcatel-lucent.com&gt;</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date: &nbsp; &nbsp; &nbsp;
&nbsp;</font><font size=1 face="sans-serif">02/11/2013 02:35 AM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject: &nbsp; &nbsp;
&nbsp; &nbsp;</font><font size=1 face="sans-serif">Re: [sip-overload]
WG Last Call for &nbsp; &nbsp; &nbsp; &nbsp;draft-ietf-soc-overload-control-12</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by: &nbsp; &nbsp;
&nbsp; &nbsp;</font><font size=1 face="sans-serif">sip-overload-bounces@ietf.org</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=3>this is just a reminder for this WG Last Call<br>
<br>
I haven't seen yet any comment or feedback <br>
please we really need you spend some time to reading and reviewing the
draft<br>
<br>
thanks a lot<br>
Salvatore<br>
<br>
On 2/5/13 3:34 PM, Salvatore Loreto wrote:</font>
<br><font size=3>Dear WG partecipants, <br>
<br>
<br>
Volker and I would like to initiate a second 2 weeks WG Last Call on <br>
draft-ietf-soc-overload-control-12 (&quot; Session Initiation Protocol
(SIP) Overload Control&quot;) </font><font size=3 color=blue><u><br>
</u></font><a href="http://tools.ietf.org/id/draft-ietf-soc-overload-control-12.txt"><font size=3 color=blue><u>http://tools.ietf.org/id/draft-ietf-soc-overload-control-12.txt</u></font></a><font size=3><br>
<br>
The first WGLC that we run ( </font><a href="http://www.ietf.org/mail-archive/web/sip-overload/current/msg00731.html"><font size=3 color=blue><u>http://www.ietf.org/mail-archive/web/sip-overload/current/msg00731.html</u></font></a><font size=3>
)<br>
has produced a significant amount of feedback and comments that have been
discussed and addressed in subsequent versions<br>
<br>
Please send your reviews, as well as expression of support regarding <br>
document readiness for IESG (or not) either to the <b>*soc*</b> mailing
list (</font><a href="mailto:sip-overload@ietf.org"><font size=3 color=blue><u>sip-overload@ietf.org</u></font></a><font size=3>),
<br>
or directly to the WG chairs (Murray Kucherawy and myself). <br>
<br>
Comments like &quot;I've read the document and it is Ok to publish&quot;
or <br>
&quot;I've read the document and it has the following issues&quot;<br>
are useful and would be gratefully accepted by chairs. <br>
<br>
<br>
The WG LC will end on Friday, February 19th. <br>
<br>
<br>
Thank you, <br>
Salvatore as an SoC co-chair. <br>
</font>
<br><font size=3><br>
</font><tt><font size=2>_______________________________________________<br>
sip-overload mailing list<br>
sip-overload@ietf.org<br>
</font></tt><a href="https://www.ietf.org/mailman/listinfo/sip-overload"><tt><font size=2>https://www.ietf.org/mailman/listinfo/sip-overload</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
--=_alternative 007AB82585257B19_=--
