[Sip] Re: draft-fwmiller-ping-00 comments
"Frank W. Miller" <fwmiller@cornfed.com> Wed, 22 February 2006 02:02 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FBjLE-0001kv-Os; Tue, 21 Feb 2006 21:02:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FBjLE-0001ko-2N for sip@ietf.org; Tue, 21 Feb 2006 21:02:56 -0500
Received: from celine.siteprotect.com ([64.41.122.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBjLB-0007MQ-Pm for sip@ietf.org; Tue, 21 Feb 2006 21:02:56 -0500
Received: from [192.168.1.4] (pool-141-157-104-69.balt.east.verizon.net [141.157.104.69]) by celine.siteprotect.com (8.11.6/8.11.6) with ESMTP id k1M22YZ32021; Tue, 21 Feb 2006 20:02:35 -0600
From: "Frank W. Miller" <fwmiller@cornfed.com>
To: Rayees Khan <rayees.khan@flextronicssoftware.com>
In-Reply-To: <OFE39A2AC7.4F2974F5-ON6525711C.003317B9-6525711C.003317CA@flextronicssoftware.com>
References: <OFE39A2AC7.4F2974F5-ON6525711C.003317B9-6525711C.003317CA@flextronicssoftware.com>
Content-Type: text/plain
Organization: Cornfed Systems, LLC
Date: Tue, 21 Feb 2006 21:02:32 -0500
Message-Id: <1140573752.2638.2.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.2 (2.2.2-5)
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: sip@ietf.org
Subject: [Sip] Re: draft-fwmiller-ping-00 comments
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: fwmiller@cornfed.com
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
On Tue, 2006-02-21 at 14:48 +0530, Rayees Khan wrote: > Section 2 of the draft mentions that signaling path of the PING method > is established as a result of a call setup. Now what I understand is > that main purpose the method is to keep the signaling path alive or to > check the validity of the signaling path. This means that it would > mostly be sent outside the context of a session. In such context I > guess it has to follow path of a dialog establishing request. > Did some cleanup of wording here to make it more general. > Section 2.1 lists the headers that are expected in the PING method. > Well, I have come across devices using Require and Proxy-Require > header in PING messages. > I saw your other email. I'd still like to hear some other opinions before I add this. > Section 2.2 mentions the responses that are expected for a PING > request. I was wondering that it is very well possible that if a > server receives a PING request which is addressed to something that > Server does not know about it is most likely to send a 404 response. > > Changed the text to allow for any response other than a 1xx or 3xx to be interpreted as a 200 OK New version on the website: http://www.cornfed.com/ping.html and http://www.cornfed.com/ping.txt 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] draft-fwmiller-ping-00 comments Rayees Khan
- [Sip] RE: draft-fwmiller-ping-00 comments fwmiller
- [Sip] RE: draft-fwmiller-ping-00 comments Rayees Khan
- [Sip] Re: draft-fwmiller-ping-00 comments Frank W. Miller
- [Sip] Certification cources Priti