Re: [sip-ops] [Sip-implementors] SIP OPTIONS "ping"

"Paul E. Jones" <paulej@packetizer.com> Fri, 13 August 2010 04:09 UTC

Return-Path: <paulej@packetizer.com>
X-Original-To: sip-ops@core3.amsl.com
Delivered-To: sip-ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 602A03A68B1 for <sip-ops@core3.amsl.com>; Thu, 12 Aug 2010 21:09:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.113
X-Spam-Level:
X-Spam-Status: No, score=-1.113 tagged_above=-999 required=5 tests=[AWL=1.485, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 JmDPOBe8e6Sw for <sip-ops@core3.amsl.com>; Thu, 12 Aug 2010 21:09:07 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by core3.amsl.com (Postfix) with ESMTP id C97903A6892 for <sip-ops@ietf.org>; Thu, 12 Aug 2010 21:09:03 -0700 (PDT)
Received: from sydney (rrcs-98-101-146-183.midsouth.biz.rr.com [98.101.146.183]) (authenticated bits=0) by dublin.packetizer.com (8.14.2/8.14.2) with ESMTP id o7D49Vwo016316 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 13 Aug 2010 00:09:36 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1281672577; bh=hjrecyR8xMAjK60wTp2DvfSt4mgBkmb+MxDWTtb6kZ8=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=VVWkXJYulVCbX+N8w0cBWyzE4qmmhLmcgdi3uL1cUhbKUcpULBblpFeifXx1xC8GE oQVgJUGDosmvMnxHq5B7TgkKBUjpwUVHEoPaocdsUe/IoJRTvtNsIDo5Dyh9TSwxWT kcfU2UO7NFQfisuiG0tI6Ip4cSXevfKBlVycBQ5U=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'$@r\\/|>r!`/@'" <sarvpriyagupta@gmail.com>
References: <053401cb39dd$44070ee0$cc152ca0$@packetizer.com> <AANLkTimqTBOZUyRBSQazhATq6aQCiyq7tRVBGdzFKOS7@mail.gmail.com>
In-Reply-To: <AANLkTimqTBOZUyRBSQazhATq6aQCiyq7tRVBGdzFKOS7@mail.gmail.com>
Date: Fri, 13 Aug 2010 00:08:41 -0400
Message-ID: <005601cb3a9d$3a9c0110$afd40330$@packetizer.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0057_01CB3A7B.B38D9560"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJ7YPXf2shkdXst8Oeg2uiqnTvIBAHNWDL+kXAKcxA=
Content-language: en-us
Cc: sip-ops@ietf.org, 'Hadriel Kaplan' <HKaplan@acmepacket.com>, sip-implementors@lists.cs.columbia.edu
Subject: Re: [sip-ops] [Sip-implementors] SIP OPTIONS "ping"
X-BeenThere: sip-ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Operations <sip-ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip-ops>, <mailto:sip-ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-ops>
List-Post: <mailto:sip-ops@ietf.org>
List-Help: <mailto:sip-ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-ops>, <mailto:sip-ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Aug 2010 04:09:15 -0000

The draft does specify the use of 503 to indicate overload.  The 486 was
proposed as a means of indicating that the device is nearing capacity,
versus being totally overloaded.  So, if one sends an OPTIONS message and
the peer device is in great shape, it would return a 200.  If it's nearing
capacity, but still able to accept new requests, it would return a 486.  If
it cannot accept new requests, it would return 503.

 

The value in using the 486 (and this could be any other code folks agreed to
use) is that it gives an SBC warning that overload is eminent.  It's
important to give given that advanced warning before the peer reaches an
overload state.  Having said that, addressing overload is really a separate
problem entirely and is not the primary focus of OPTIONS "ping".  So, I
would not be opposed to removing this part entirely.  For overload control,
there is a WG focused on doing percentage-based overload control.  I view
that as good for stateless SIP entities, but not very useful (in my opinion)
for peered SBCs.  So, we have a separate draft aimed at overload control
called "Session Capacity Estimate" SIP entities that are stateful:

http://tools.ietf.org/html/draft-jones-sip-overload-sce-00

 

Anyway, I don't want to get too off-topic :-)  For OPTIONS, I just want to
get the feel of the group as to whether there is value in trying to do
something.  I take it you think this is worthwhile.

 

I'll remove the paragraph that describes use of 486, since I think use of
Session Capacity Estimate is a far better solution.  OPTIONS is just to
determine if the peer is alive and an SCE value can be returned in an
OPTIONS ping.  Any other changes that would help tighten the language and
reduce interop issues?

 

Paul

 

From: $@r\/|>r!`/@ [mailto:sarvpriyagupta@gmail.com] 
Sent: Thursday, August 12, 2010 3:51 AM
To: Paul E. Jones
Cc: sip-ops@ietf.org; sip-implementors@lists.cs.columbia.edu; Gonzalo
Salgueiro; Hadriel Kaplan
Subject: Re: [Sip-implementors] SIP OPTIONS "ping"

 

Hi,

 

Gud to see your initiative.

 

Instead of using 486 for denoting overload, 503 message can be used. I have
seen this usage to use as overload control mechanism. Entirely in my
opinion, 486 is not apt.

 

 

cheers!!!!
sarvpriya

http://sarvpriyak.blogspot.com/

 

On Thu, Aug 12, 2010 at 10:44 AM, Paul E. Jones <paulej@packetizer.com>;
wrote:

Folks,



Gonzalo and I produced an Internet Draft aiming at trying to bring some
consistency to the way in which SIP user agents implement an OPTIONS "ping"
procedure.  It seems that a very large number of vendors do this, but
unfortunately, there seems to be little consistency.



Initially, we positioned the document as a standards track RFC, since this
essentially builds on RFC 3261.  However, there was some pushback from folks
in the IETF for a variety of reasons, not the least of which is the fact
that there is no working group chartered to do the work.  We don't feel this
one draft warrants the creation of a working group.



So, we've got three options we can consider:

1)      Forge ahead outside of a working group

2)      Change the status of the draft to Informational

3)      Forget about the draft and let every SIP device do it the way they
want, throwing hope of consistency out the window



(Yeah, you can tell I prefer not to go for the third option.)



In any case, I'd like to get feedback from the on the SIP operators and SIP
implementers lists.  Do you think it's worth trying to address this issue?
If so, which option do you think we should pursue?



Note that we're certainly open to feedback on the draft.  I'd prefer it to
have a few more "MUST" statements in the text, rather than "SHOULD".  But,
we need to find that right balance:

http://tools.ietf.org/html/draft-jones-sip-options-ping



Paul



_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors




--