RE: [Sip] Open Issue #58: Rejected mid-call SDP in 2xx

Jonathan Rosenberg <jdrosen@dynamicsoft.com> Fri, 07 September 2001 21:10 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 RAA28514 for <sip-archive@odin.ietf.org>; Fri, 7 Sep 2001 17:10:09 -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 QAA28092; Fri, 7 Sep 2001 16:56:33 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA28063 for <sip@optimus.ietf.org>; Fri, 7 Sep 2001 16:56:31 -0400 (EDT)
Received: from mail1.dynamicsoft.com ([63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28175 for <sip@ietf.org>; Fri, 7 Sep 2001 16:55:03 -0400 (EDT)
Received: from DYN-EXCH-001.dynamicsoft.com (dyn-exch-001 [63.113.44.7]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id f87Kt2Cj001707; Fri, 7 Sep 2001 16:55:02 -0400 (EDT)
Received: by DYN-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19) id <R9F8YXYR>; Fri, 7 Sep 2001 16:55:55 -0400
Message-ID: <B65B4F8437968F488A01A940B21982BF020D6805@DYN-EXCH-001.dynamicsoft.com>
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
To: "'brett@broadsoft.com'" <brett@broadsoft.com>, Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Cc: sip@ietf.org
Subject: RE: [Sip] Open Issue #58: Rejected mid-call SDP in 2xx
Date: Fri, 07 Sep 2001 16:55:47 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
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


 

> -----Original Message-----
> From: Brett Tate [mailto:brett@broadsoft.com]
> Sent: Friday, September 07, 2001 4:10 PM
> To: 'Jonathan Rosenberg'
> Cc: sip@ietf.org
> Subject: RE: [Sip] Open Issue #58: Rejected mid-call SDP in 2xx
> 
> 
> Sounds fine with me.  However I guess that the 
> "MUST" will have implications for devices that 
> can't or don't distinguish between INVITE and 
> re-INVITE after having underwent a restart.

I had forgotten about this case. Good observation.

> I guess that these UA's would have to persist 
> parts of the SDP if they wish to allow a 
> re-INVITE without SDP to re-establish a call
> (which I don't recommend).

I agree that thats ugly.

I suppose that we could say that its a MUST to use the existing SDP if you
know it. A UA that sends a re-INVITE w/o SDP MUST be prepared for SDP that
may be different for the reason you describe. Hopefully its something
acceptable. If its not, BYE the call. I don't think we can reasonably do
better. We're already talking about the case where the UA has failed and
recovered.

Sound OK?

-Jonathan R.



---
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

_______________________________________________
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