Re: [Sipping] I-D ACTION:draft-camarillo-sipping-reason-00.txt
Paul Kyzivat <pkyzivat@cisco.com> Tue, 16 April 2002 14:08 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 KAA05392 for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 10:08:48 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id KAA18433 for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 10:08:52 -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 JAA17154; Tue, 16 Apr 2002 09:55:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA17037 for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 09:55:39 -0400 (EDT)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04384; Tue, 16 Apr 2002 09:55:32 -0400 (EDT)
Received: from cannon.cisco.com (localhost [127.0.0.1]) by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g3GDtHSk016496; Tue, 16 Apr 2002 09:55:17 -0400 (EDT)
Received: from cisco.com (dhcp-161-44-241-140.cisco.com [161.44.241.140]) by cannon.cisco.com (Mirapoint) with ESMTP id AAI47380; Tue, 16 Apr 2002 09:58:11 -0400 (EDT)
Message-ID: <3CBC2D2C.411D97E5@cisco.com>
Date: Tue, 16 Apr 2002 09:54:52 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Internet-Drafts@ietf.org
CC: IETF-Announce: <>, ";"@cisco.com, sipping@ietf.org;
Subject: Re: [Sipping] I-D ACTION:draft-camarillo-sipping-reason-00.txt
References: <200204091241.IAA03423@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit
Gonzalo, I have another possible reason for Reason: 7. Identifying purpose of dialog refresh There are multiple reasons for sending a dialog refresh message (e.g. reINVITE). It may be sent simply to update a session timer, or it may be sent to test the signalling path. In these cases the server need not do anything special. But another reason may be that the sender believes there is some problem that might be resolved by changing something at the other endpoint. For instance the sender may be receiving errors attempting to send media to the receiver. A change in media port at the receiving endpoint might fix this problem. However there is currently no way to distinguish this case from a simple refresh. (I numbered this 7 because you have two 5s in your draft.) There is another case I don't see mentioned, but I am not sure where to put it. This is the case of CANCEL or BYE used to drop extra call legs of a forked invite. Would like to indicate the difference between dropping because answered elsewhere and dropping because changed mind or got tired of waiting. This could be important to avoid later callbacks. This is similar to stuff in your Service Creation section, but the name seems wrong. Paul Internet-Drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > Title : Session Initiation Protocol: Requirements on Reason > Information beyond the Status Code > Author(s) : G. Camarillo > Filename : draft-camarillo-sipping-reason-00.txt > Pages : 5 > Date : 08-Apr-02 > > Some applications need to know why a particular SIP message was > issued. This document describes those applications and provides a > set of requirements that a mechanism used to transport this type of > information has to fulfill. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-camarillo-sipping-reason-00.txt > > To remove yourself from the IETF Announcement list, send a message to > ietf-announce-request with the word unsubscribe in the body of the message. > > Internet-Drafts are also available by anonymous FTP. Login with the username > "anonymous" and a password of your e-mail address. After logging in, > type "cd internet-drafts" and then > "get draft-camarillo-sipping-reason-00.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-camarillo-sipping-reason-00.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > Content-Type: text/plain > Content-ID: <20020408122729.I-D@ietf.org> _______________________________________________ Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@cs.columbia.edu for questions on current sip Use sip@ietf.org for new developments of core SIP
- [Sipping] I-D ACTION:draft-camarillo-sipping-reas… Internet-Drafts
- Re: [Sipping] I-D ACTION:draft-camarillo-sipping-… Paul Kyzivat
- Re: [Sipping] I-D ACTION:draft-camarillo-sipping-… Gonzalo Camarillo