Re: [sip-overload] draft minutes IETF83

"Ravindran, Parthasarathi" <pravindran@sonusnet.com> Tue, 24 April 2012 01:24 UTC

Return-Path: <pravindran@sonusnet.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 1B85511E8075 for <sip-overload@ietfa.amsl.com>; Mon, 23 Apr 2012 18:24:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level:
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 gl5mgSLevX5C for <sip-overload@ietfa.amsl.com>; Mon, 23 Apr 2012 18:24:21 -0700 (PDT)
Received: from na3sys010aog108.obsmtp.com (na3sys010aog108.obsmtp.com [74.125.245.84]) by ietfa.amsl.com (Postfix) with ESMTP id 02B3111E8072 for <sip-overload@ietf.org>; Mon, 23 Apr 2012 18:24:20 -0700 (PDT)
Received: from USMA-EX-HUB2.sonusnet.com ([69.147.176.212]) (using TLSv1) by na3sys010aob108.postini.com ([74.125.244.12]) with SMTP ID DSNKT5YAxLFHqKNkJZW4EZFqiQrG/MyQeh9w@postini.com; Mon, 23 Apr 2012 18:24:21 PDT
Received: from INBA-HUB02.sonusnet.com (10.70.51.87) by USMA-EX-HUB2.sonusnet.com (66.203.90.17) with Microsoft SMTP Server (TLS) id 14.2.247.3; Mon, 23 Apr 2012 21:24:20 -0400
Received: from INBA-MAIL01.sonusnet.com ([fe80::8d0f:e4f9:a74f:3daf]) by inba-hub02.sonusnet.com ([fe80::80b9:dc60:caf7:7dfc%11]) with mapi id 14.01.0355.002; Tue, 24 Apr 2012 06:54:09 +0530
From: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>, Volker Hilt <volker.hilt@bell-labs.com>
Thread-Topic: [sip-overload] draft minutes IETF83
Thread-Index: AQHNH/FX2r8tIMu4aU2GEinS/npxC5amC+XAgAIdIQCAAAQIAIAACDUAgAAAUQCAAAv5gIAA7okQ
Date: Tue, 24 Apr 2012 01:24:07 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C0E237E4A@inba-mail01.sonusnet.com>
References: <4F93044A.5020207@ericsson.com> <387F9047F55E8C42850AD6B3A7A03C6C0E228BF8@inba-mail01.sonusnet.com> <4F956FC8.2030503@bell-labs.com> <4F95732A.1000506@bell-labs.com> <4F957A0C.4050606@bell-labs.com> <4F957A50.7040402@bell-labs.com> <4F95845B.2040508@bell-labs.com>
In-Reply-To: <4F95845B.2040508@bell-labs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [121.242.142.186]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "sip-overload@ietf.org" <sip-overload@ietf.org>
Subject: Re: [sip-overload] draft minutes IETF83
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, 24 Apr 2012 01:24:22 -0000

Vijay/Volker,

I'm reading this mail after replied to your initial proposal as this mail is not in my "To me" folder :-)

I have difference of opinion about the content of sub/not in Sec 9 as it is not fully analyzed after deep-dive into "OC" parameters in "via" header based mechanism. My opinion comes from the Session Initiation Protocol (SIP) Resource availability Event package draft (http://tools.ietf.org/html/draft-partha-soc-overload-resource-availability-00).  I personally feel that it is not worthy to discuss about SUB/NOT mechanism's merits/demerits within this draft at this moment. In case you wish to discuss, I'll continue the merit/demerit as part of this mail thread.

Thanks
Partha

>-----Original Message-----
>From: sip-overload-bounces@ietf.org [mailto:sip-overload-
>bounces@ietf.org] On Behalf Of Vijay K. Gurbani
>Sent: Monday, April 23, 2012 10:04 PM
>To: Volker Hilt
>Cc: sip-overload@ietf.org
>Subject: Re: [sip-overload] draft minutes IETF83
>
>On 04/23/2012 10:50 AM, Volker Hilt wrote:
>> This discussion is specific to the mechanism proposed in this draft
>> and it was felt that it is better to keep it there.
>
>Hmmm ... OK.
>
>>> OLD:
>>> 9.1. SIP Mechanism
>>>
>>> A SIP mechanism is needed to convey overload feedback from the
>>> receiving to the sending SIP entity. A number of different
>>> alternatives exist to implement such a mechanism.
>>>
>>> NEW:
>>> 9.1. SIP Mechanism
>>>
>>> A SIP mechanism is needed to convey overload feedback from the
>>> receiving to the sending SIP entity. Different alternatives exist to
>>> implement such a mechanism, and the fundamental design choices
>>> related to each are discussed below. This document uses the SIP
>>> response headers (Section 9.1.1) to achieve overload control; the
>>> design choices related to SIP event package (Section 9.1.2) are
>>> provided for the sake of completeness.
>>>
>> Works fine for me.
>
>Unless someone objects to this, I will update the draft as outlined
>above.
>
>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/
>_______________________________________________
>sip-overload mailing list
>sip-overload@ietf.org
>https://www.ietf.org/mailman/listinfo/sip-overload