Re: [Sip] Update to PING draft

Vikram Agarwal <vikram.agarwal@flextronicssoftware.com> Tue, 16 May 2006 09:08 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FfvXg-0005ck-Kj; Tue, 16 May 2006 05:08:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FfvXf-0005cf-PT for sip@ietf.org; Tue, 16 May 2006 05:08:36 -0400
Received: from [203.187.132.2] (helo=delta.hssblr.co.in) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FfvXS-0001oP-6e for sip@ietf.org; Tue, 16 May 2006 05:08:35 -0400
Received: from espion.blr.hss.hns.com (espion.blr.hss.hns.com [10.203.193.21]) by delta.hssblr.co.in (8.13.6/8.11.6) with ESMTP id k4G96phf012378; Tue, 16 May 2006 14:37:00 +0530
In-Reply-To: <A52007C2-01D5-42C2-AD9E-04B8835C5810@cisco.com>
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [Sip] Update to PING draft
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.1 January 21, 2004
Message-ID: <OF03D46767.33F8F222-ON65257170.002A43C4-65257170.0032104C@flextronicssoftware.com>
From: Vikram Agarwal <vikram.agarwal@flextronicssoftware.com>
Date: Tue, 16 May 2006 14:36:49 +0530
X-MIMETrack: Serialize by Router on Espion/BLR/HSS(Release 6.5.5|November 30, 2005) at 05/16/2006 02:37:05 PM, Serialize complete at 05/16/2006 02:37:05 PM
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 43317e64100dd4d87214c51822b582d1
Cc: sip@ietf.org, fwmiller@cornfed.com
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1807701728=="
Errors-To: sip-bounces@ietf.org

Hi Cullen,

  The same point i had raised some time back when the PING method was 
being introduced (w.r.t NAT keep alive). The response from Jonathan R. i 
got was that PING would be a modified SIP method, where only some 2 - 3 
headers would be parsed (not like OPTIONS method where all the mandatory 
headers would be parsed) to save the parsing time. But, now when i see the 
PING draft, it is the same like OPTIONS. i.e nothing new w.r.t parsing of 
headers in the PING/OPTIONS method. In this case i am not able to get the 
significance of introducing the PING method over OPTIONS?

Please refer to the response below from Jonathan:

"I will further note that a "modified PING message", or any other kind of 
SIP message processing that does not follow SIP semantics as defined in 
RFC 3261, is effectively identical to the multiple-protocol mechanism of 
running STUN and SIP on the same port. You'll need to figure out which 
protocol it is (SIP or modified SIP), and send the request to the right 
code path appropirately."

Regards,
--Vikram.
 



Cullen Jennings <fluffy@cisco.com> 
05/16/2006 11:16 AM


To
fwmiller@cornfed.com
cc
sip@ietf.org
Subject
Re: [Sip] Update to PING draft







Why is this any better than using OPTIONs?


On May 16, 2006, at 1:19 AM, Frank W. Miller wrote:

>
> I've updated the PING draf
>
> draft-fwmiller-ping-03
>
> http://www.cornfed.com/ping.txt
> http://www.cornfed.com/ping.html
>
> There was one paragraph that I overlooked that still referred to no
> retransmissions that has been removed.  The draft definitely calls 
> out a
> standard NIT with standard retransmissions.
>
> I'm also uploading the .txt version to the IETF side tonight.
>
> Thanks,
> FM
>
>
>
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip