RE: [Sip] Re-use of Call-ID in the SIP Replaces header

Jonathan Rosenberg <jdrosen@dynamicsoft.com> Wed, 01 August 2001 06:42 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 SMTP id CAA18980 for <sip-archive@odin.ietf.org>; Wed, 1 Aug 2001 02:42:30 -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 CAA09883; Wed, 1 Aug 2001 02:14:44 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA09854 for <sip@ns.ietf.org>; Wed, 1 Aug 2001 02:14:38 -0400 (EDT)
Received: from mail2.dynamicsoft.com (mail2.dynamicsoft.com [216.173.40.52]) by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA15576 for <sip@ietf.org>; Wed, 1 Aug 2001 02:13:36 -0400 (EDT)
Received: from DYN-EXCH-001.dynamicsoft.com (bluebird [216.173.40.50]) by mail2.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id f716E2w3025533; Wed, 1 Aug 2001 02:14:02 -0400 (EDT)
Received: by DYN-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19) id <QAXL28K5>; Wed, 1 Aug 2001 02:14:36 -0400
Message-ID: <B65B4F8437968F488A01A940B21982BF020D6419@DYN-EXCH-001.dynamicsoft.com>
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
To: 'Billy Biggs' <billy@billybiggs.com>, Jonathan Cumming <jrc@dataconnection.com>
Cc: SIP List <sip@ietf.org>
Subject: RE: [Sip] Re-use of Call-ID in the SIP Replaces header
Date: Wed, 01 Aug 2001 02:14:36 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
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: Billy Biggs [mailto:billy@billybiggs.com]
> Sent: Tuesday, July 31, 2001 10:36 AM
> To: Jonathan Cumming
> Cc: SIP List
> Subject: Re: [Sip] Re-use of Call-ID in the SIP Replaces header
> 
> 
> Jonathan Cumming (jrc@dataconnection.com):
> 
> > In section 2.2 of draft-biggs-sip-replaces-01, you specify that "A
> > unique call-id may be given to the replacement call.".  This seems
> > unnecessarily weak and could lead to interoperability problems where
> > an application assumes the re-use of the Call-ID.
> > 
> > If a unique Call-ID is required, as specified in RFC 2543, then why
> > give the end-point the option to re-use the existing Call-ID?
> 
>   When we were first discussing methods of performing attended call
> transfer, there was alot of discussion about using the Call-ID to
> perform the replaces operation, that is, the replacement call (or
> joining call) would be identified by having the same Call-ID as an
> existing call.
> 
>   So, the text should really read "in our replaces model, a unique
> call-id may be given to the replacement call, instead of 
> previous models
> which overloaded the meaning of the call-id".  I wasn't trying to
> dictate behavior either way.

"may" is not strong enough. I think the consensus was to continue to have
call-ids be unique, in which case the replacement call MUST use a new
call-id.

-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://www.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