IETF Logo Mail Archive

Re: [sip-overload] [Fwd: I-D Action:draft-hilt-sipping-overload-07.txt]

"NOEL, ERIC C (ATTLABS)" <en5192@att.com> Tue, 27 October 2009 13:13 UTC

Return-Path: <en5192@att.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC1D43A6859 for <sip-overload@core3.amsl.com>; Tue, 27 Oct 2009 06:13:50 -0700 (PDT)
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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pyqXPaIjWIHU for <sip-overload@core3.amsl.com>; Tue, 27 Oct 2009 06:13:49 -0700 (PDT)
Received: from mail167.messagelabs.com (mail167.messagelabs.com [216.82.253.179]) by core3.amsl.com (Postfix) with ESMTP id A24DA3A6782 for <sip-overload@ietf.org>; Tue, 27 Oct 2009 06:13:49 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: en5192@att.com
X-Msg-Ref: server-7.tower-167.messagelabs.com!1256649242!18922942!1
X-StarScan-Version: 6.1.3; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 19700 invoked from network); 27 Oct 2009 13:14:02 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-7.tower-167.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 27 Oct 2009 13:14:02 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id n9RDE1VE003976 for <sip-overload@ietf.org>; Tue, 27 Oct 2009 09:14:01 -0400
Received: from misout7msgusr7b.ugd.att.com (misout7msgusr7b.ugd.att.com [144.155.43.104]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id n9RDDwt0003963 for <sip-overload@ietf.org>; Tue, 27 Oct 2009 09:13:58 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 27 Oct 2009 09:13:58 -0400
Message-ID: <5DA01D2CA74FAF40ADF71DB4177D345A02684F69@misout7msgusr7b.ugd.att.com>
In-Reply-To: <4AE5BE5C.1050803@alcatel-lucent.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [sip-overload] [Fwd: I-D Action:draft-hilt-sipping-overload-07.txt]
Thread-Index: AcpWT/eM1EJai1QXQ7uuDoCcVni76gAtSwjw
References: <4AE5BE5C.1050803@alcatel-lucent.com>
From: "NOEL, ERIC C (ATTLABS)" <en5192@att.com>
To: Volker Hilt <volkerh@alcatel-lucent.com>, sip-overload@ietf.org
X-Mailman-Approved-At: Tue, 27 Oct 2009 07:23:15 -0700
Subject: Re: [sip-overload] [Fwd: I-D Action:draft-hilt-sipping-overload-07.txt]
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 27 Oct 2009 14:21:55 -0000

Volker,

Based, on our conference call 2 weeks ago, I understand the sip-overload
group immediate role would be to provide comments (over the sip-overload
mailing list) on both    

http://www.ietf.org/internet-drafts/draft-hilt-sipping-overload-07.txt

And 

http://tools.ietf.org/html/draft-shen-sipping-load-control-event-package
-02

And that going forward we would interact through the sip-overload
mailing list. 

Our (sip overload design team) bi-weekly conference calls are in effect
stopped and will only occur on a as needed basis (i.e. presentation form
team member....).

Lastly, I presented a paper titled "Novel Overload Controls for SIP
Networks" (Eric Noel & Carolyn Johnson co-authored) to ITC21
(http://www.i-teletraffic.org/itc21/technical-program/).  For copyright
reasons, I cannot broadcast an e-version of that paper. Eventually it
will be available through IEEE explorer.

Thanks,

Eric
  
  
-----Original Message-----
From: sip-overload-bounces@ietf.org
[mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt
Sent: Monday, October 26, 2009 11:21 AM
To: sip-overload@ietf.org
Subject: [sip-overload] [Fwd: I-D
Action:draft-hilt-sipping-overload-07.txt]

I've submitted a new version of the overload control draft (see below).

Thanks,

Volker


----------------
New Internet-Draft is available from the on-line Internet-Drafts 
directories.

	Title           : Session Initiation Protocol (SIP) Overload
Control
	Author(s)       : V. Hilt, H. Schulzrinne
	Filename        : draft-hilt-sipping-overload-07.txt
	Pages           : 14
	Date            : 2009-10-25

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 an overload control mechanism for SIP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-hilt-sipping-overload-07.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.


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

v2.23.0 | Report a Bug | By Email