Re: [Sip] Open Issue #7: CANCEL for non-INVITE

"Henning G. Schulzrinne" <hgs@cs.columbia.edu> Sat, 22 September 2001 01:53 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10702 for <sip-archive@odin.ietf.org>; Fri, 21 Sep 2001 21:53:54 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA00029; Fri, 21 Sep 2001 21:23:12 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA29994 for <sip@optimus.ietf.org>; Fri, 21 Sep 2001 21:23:09 -0400 (EDT)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09420 for <sip@ietf.org>; Fri, 21 Sep 2001 21:23:46 -0400 (EDT)
Received: from cs.columbia.edu (metroliner.cs.columbia.edu [128.59.19.252]) by opus.cs.columbia.edu (8.9.3+Sun/8.9.3) with ESMTP id VAA24382; Fri, 21 Sep 2001 21:22:51 -0400 (EDT)
Message-ID: <3BABE7EB.D66B2641@cs.columbia.edu>
Date: Fri, 21 Sep 2001 21:22:51 -0400
From: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>
Organization: Dept. of Computer Science, Columbia University
X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.19-3cucs i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
CC: Jonathan Rosenberg <jdrosen@dynamicsoft.com>, 'Rohan Mahy' <rohan@cisco.com>, sip@ietf.org
Subject: Re: [Sip] Open Issue #7: CANCEL for non-INVITE
References: <B65B4F8437968F488A01A940B21982BF020D68A8@DYN-EXCH-001.dynamicsoft.com> <3BA8588E.B54D5721@lmf.ericsson.se>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Session Initiation Protocol <sip.ietf.org>
X-BeenThere: sip@ietf.org
Content-Transfer-Encoding: 7bit

Christer Holmberg wrote:
> 
> Hi,
> 
> I agree on this thread. Also, I don't see the problem with this issue,
> EVEN if there would be non-INVITE requests in the future that can be
> cancelled. The UAC and UAS should know what can be cancelled, and what
> can't be, and if the UAC tries to CANCEL something else the UAS simply
> returns 400/405/whatever... We could even add some response code saying
> "The request can't be cancelled"...

I don't understand this paragraph. Unless I'm misunderstanding the whole
discussion, the proposal is that it will be illegal in the future to
send a CANCEL for any non-INVITE request and it will be illegal for any
SIP device to implement CANCEL for non-INVITE. (It's always been legal
for UAS to not implement CANCEL.)


> 
> In fact, I am pretty sure the world would have been a better place
> without the CANCEL in the first place...

Well, nobody has to support it.

> 
> NOTE: That was NOT a proposal to remove CANCEL from SIP, just my
> personal opinion :)
> 

-- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs

_______________________________________________
Sip mailing list  http://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