Re: [Sip] Update to PING draft

Cullen Jennings <fluffy@cisco.com> Tue, 16 May 2006 05:46 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FfsO8-0000XU-Nl; Tue, 16 May 2006 01:46:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FfsO7-0000XP-FS for sip@ietf.org; Tue, 16 May 2006 01:46:31 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FfsO5-0000PW-4a for sip@ietf.org; Tue, 16 May 2006 01:46:31 -0400
Received: from sj-dkim-6.cisco.com ([171.68.10.81]) by sj-iport-5.cisco.com with ESMTP; 15 May 2006 22:46:29 -0700
X-IronPort-AV: i="4.05,131,1146466800"; d="scan'208"; a="277358201:sNHT35389772"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-6.cisco.com (8.12.11/8.12.11) with ESMTP id k4G5kSKg018651; Mon, 15 May 2006 22:46:28 -0700
Received: from vtg-um-e2k2.sj21ad.cisco.com (vtg-um-e2k2.cisco.com [171.70.93.54]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k4G5kSsF004763; Mon, 15 May 2006 22:46:28 -0700 (PDT)
Received: from [10.43.1.79] ([10.21.154.83]) by vtg-um-e2k2.sj21ad.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 15 May 2006 22:46:28 -0700
In-Reply-To: <1147735185.2507.1.camel@dimension.cornfed.com>
References: <1147735185.2507.1.camel@dimension.cornfed.com>
Mime-Version: 1.0 (Apple Message framework v750)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <A52007C2-01D5-42C2-AD9E-04B8835C5810@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [Sip] Update to PING draft
Date: Tue, 16 May 2006 07:46:32 +0200
To: fwmiller@cornfed.com
X-Mailer: Apple Mail (2.750)
X-OriginalArrivalTime: 16 May 2006 05:46:28.0261 (UTC) FILETIME=[13726550:01C678AC]
DKIM-Signature: a=rsa-sha1; q=dns; l=858; t=1147758388; x=1148622388; c=relaxed/simple; s=sjdkim6001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:Cullen=20Jennings=20<fluffy@cisco.com> |Subject:Re=3A=20[Sip]=20Update=20to=20PING=20draft; X=v=3Dcisco.com=3B=20h=3DVmk4x4SJOy44yOSnLmSLPyW46AU=3D; b=d2cluIA3aPADRaEfSvW/hRSZde+pIW1Iad3Jl1BADIWJ/asFPWZm3y6oqE2EWrpui6tC4PbO GIOaVOk/XtVybNeEpt3rti0fzuSuKZ2R+OSO9DMI32BlYHDqtWd+Yirm;
Authentication-Results: sj-dkim-6.cisco.com; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: sip@ietf.org
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>
Errors-To: sip-bounces@ietf.org

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 draft:
>
> 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