RE: draft-ietf-mmusic-sip-session-timer-00.txt
Pat.Calhoun@Eng.Sun.COM (Patrice Calhoun) Thu, 11 February 1999 19:07 UTC
Return-Path: <owner-confctrl>
Received: (from majordom@localhost) by zephyr.isi.edu (8.8.7/8.8.6) id LAA11915 for confctrl-outgoing; Thu, 11 Feb 1999 11:07:05 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id LAA11910 for <confctrl@zephyr.isi.edu>; Thu, 11 Feb 1999 11:07:04 -0800 (PST)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by tnt.isi.edu (8.8.7/8.8.6) with SMTP id LAA07472 for <confctrl@ISI.EDU>; Thu, 11 Feb 1999 11:07:03 -0800 (PST)
Received: from Eng.Sun.COM (engmail4 [129.144.134.6]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id LAA08587; Thu, 11 Feb 1999 11:06:27 -0800
Received: from hsmpka.eng.sun.com (phys-hsmpka.Eng.Sun.COM [129.146.93.37]) by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id LAA27115; Thu, 11 Feb 1999 11:06:25 -0800
Received: from hsmpka.eng.sun.com by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4) id LAA28606; Thu, 11 Feb 1999 11:06:12 -0800
From: Pat.Calhoun@Eng.Sun.COM
Message-Id: <199902111906.LAA28606@hsmpka.eng.sun.com>
Date: Thu, 11 Feb 1999 11:02:08 -0800
To: "Donovan, Steven R. (MCI)" <Steven.R.Donovan@mci.com>, "'iptel@lists.research.bell-labs.com'" <iptel@lists.research.bell-labs.com>, "'confctrl@ISI.EDU'" <confctrl@ISI.EDU>
Reply-To: Pat.Calhoun@Eng.Sun.COM
Subject: RE: draft-ietf-mmusic-sip-session-timer-00.txt
X-Mailer: Sun NetMail 2.2.5
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-confctrl@zephyr.isi.edu
Precedence: bulk
Pardon the perhaps very naive question, but I suppose I am not as versant in SIP as I would like to be. My understanding is that a SIP Client issues an Invite message to a SIP Server, which in turn forwards the request to a target SIP Client (or some GW or some sort). Once the ACK has returned to the originating client, I was under the impression that both SIP Clients send RTP packets directly to each other, bypassing the SIP Server (this is where I am unclear). So if this is true, how will a SIP Server (stateful, or stateless) enforce any session timeouts? A malicious SIP Client can simply keep the session active for as long as it wishes, ignoring any messages from the SIP Server that may tell it to disconnect. This, as far as I can see, could cause some serious problems if one wishes to deploy a service and still maintain some control over the sessions. Again, perhaps I am way off here. Any clarifications would certainly be appreciated. PatC >This time with the draft attached. Sorry for the extra mail. > >Steve > > <<draft-ietf-mmusic-sip-session-timer-00.txt>> > >> -----Original Message----- >> From: Donovan, Steven R. (MCI) >> Sent: Thursday, February 11, 1999 10:17 AM >> To: 'confctrl@ISI.EDU'; 'iptel@lists.research.bell-labs.com' >> Subject: draft-ietf-mmusic-sip-session-timer-00.txt >> >> This message is notification of the following Internet Draft which has >> been submitted to the IETF for posting. >> >> <draft-ietf-mmusic-sip-session-timer-00.txt> >> >> Abstract: >> >> This document proposes an extension to the SIP specification. This >> extension adds a new message header that is used to specify the >> duration of a requested session. >> >> The session timer can be used to limit the total duration of a session >> if, for instance, one of the participants in the session wants to >> limit the cost of the session. It can also be used by stateful SIP >> Proxy Servers to track the status of sessions for which session state >> exists on the servers. Currently a stateful SIP Proxy Server that is >> not handling the media stream(s) for the session has no mechanism to >> definitively determine the state of all sessions for which it has state. >> While the SIP Specification does provide the BYE method for terminating >> the session, there is no mechanism for a SIP Proxy Server to detect the >> end of a session when the BYE message is not sent or is lost due to >> network problems. >> >> The internet draft is attached. >> >> Steve Donovan >> MCIWorldcom
- draft-ietf-mmusic-sip-session-timer-00.txt Donovan, Steven R. (MCI)
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Donovan, Steven R. (MCI)
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Patrice Calhoun
- Re: draft-ietf-mmusic-sip-session-timer-00.txt Jonathan Rosenberg
- RE: draft-ietf-mmusic-sip-session-timer-00.txt John Hearty
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Donovan, Steven R. (MCI)
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Patrice Calhoun
- Re: draft-ietf-mmusic-sip-session-timer-00.txt Douglas Clowes
- Re: draft-ietf-mmusic-sip-session-timer-00.txt Patrice Calhoun
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Francois Menard Distribution List Management Account
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Patrice Calhoun
- Re: draft-ietf-mmusic-sip-session-timer-00.txt Douglas Clowes
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Douglas Clowes
- Re: draft-ietf-mmusic-sip-session-timer-00.txt Jonathan Rosenberg
- Re: draft-ietf-mmusic-sip-session-timer-00.txt Henning Schulzrinne
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Francois Menard Distribution List Management Account
- Re: draft-ietf-mmusic-sip-session-timer-00.txt Jonathan Rosenberg
- Re: draft-ietf-mmusic-sip-session-timer-00.txt Vipin Palawat
- Re: draft-ietf-mmusic-sip-session-timer-00.txt Patrice Calhoun
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Patrice Calhoun
- RE: RE: draft-ietf-mmusic-sip-session-timer-00.txt Francois Menard
- Re: draft-ietf-mmusic-sip-session-timer-00.txt Jonathan Rosenberg
- RE: RE: draft-ietf-mmusic-sip-session-timer-00.txt Sean Olson
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Donovan, Steven R. (MCI)
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Patrice Calhoun
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Dean Willis
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Douglas Clowes
- RE: RE: draft-ietf-mmusic-sip-session-timer-00.txt Donovan, Steven R. (MCI)
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Donovan, Steven R. (MCI)
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Donovan, Steven R. (MCI)
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Patrice Calhoun
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Patrice Calhoun
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Dean Willis
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Patrice Calhoun
- Re: draft-ietf-mmusic-sip-session-timer-00.txt Jonathan Rosenberg
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Douglas Clowes
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Jerome Privat
- Re: draft-ietf-mmusic-sip-session-timer-00.txt Patrice Calhoun
- Re: draft-ietf-mmusic-sip-session-timer-00.txt Jonathan Rosenberg
- Re: draft-ietf-mmusic-sip-session-timer-00.txt John Hearty
- Re: draft-ietf-mmusic-sip-session-timer-00.txt John Hearty
- Re: draft-ietf-mmusic-sip-session-timer-00.txt Lewis McCarthy
- Re: draft-ietf-mmusic-sip-session-timer-00.txt Jonathan Rosenberg
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Dean Willis
- Re: draft-ietf-mmusic-sip-session-timer-00.txt Jonathan Rosenberg
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Dean Willis
- Re: draft-ietf-mmusic-sip-session-timer-00.txt Jonathan Rosenberg
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Aishling
- Re: draft-ietf-mmusic-sip-session-timer-00.txt Henning Schulzrinne
- RE: draft-ietf-mmusic-sip-session-timer-00.txt Dean Willis
- Re: draft-ietf-mmusic-sip-session-timer-00.txt Mark Handley
- Re: draft-ietf-mmusic-sip-session-timer-00.txt Henning Schulzrinne
- clients and servers Scott Petrack