RE: [Sip] Questions about the SIP Replaces Header draft.

"Sriram Parameswar" <sriramp@nortelnetworks.com> Thu, 06 September 2001 20:14 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 QAA07704 for <sip-archive@odin.ietf.org>; Thu, 6 Sep 2001 16:14:36 -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 PAA03117; Thu, 6 Sep 2001 15:52:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA03090 for <sip@ns.ietf.org>; Thu, 6 Sep 2001 15:52:55 -0400 (EDT)
Received: from zrc2s03g.us.nortel.com (zrc2s03g.nortelnetworks.com [47.103.122.66]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06997 for <sip@ietf.org>; Thu, 6 Sep 2001 15:51:22 -0400 (EDT)
Received: from smtprch1.nortel.com (erchg0j.us.nortel.com [47.113.64.103]) by zrc2s03g.us.nortel.com (8.9.3+Sun/8.9.1) with ESMTP id OAA25626 for <sip@ietf.org>; Thu, 6 Sep 2001 14:51:41 -0500 (CDT)
Received: from zrchb200.us.nortel.com by smtprch1.nortel.com; Thu, 6 Sep 2001 14:49:47 -0500
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2653.19) id <SK3L2CZ6>; Thu, 6 Sep 2001 14:49:46 -0500
Message-ID: <9A9367D1556AD21182C40000F80930AB04411D98@crchy28b.us.nortel.com>
From: Sriram Parameswar <sriramp@nortelnetworks.com>
To: "'Padhye, Chinmay'" <c_padhye@trillium.com>, "'sip@ietf.org'" <sip@ietf.org>
Subject: RE: [Sip] Questions about the SIP Replaces Header draft.
Date: Thu, 06 Sep 2001 14:49:41 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1370D.11A60500"
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

Partial answer in-line prefaced by [Sriram]. Hope it helps.

Sriram

__________________________________________
Sriram Parameswar              Phone: 972-685-8540
Interactive Multimedia Server (IMS) Fax: 972-685-3563
Nortel Networks, Richardson USA  Email: sriramp@nortelnetworks.com


-----Original Message-----
From: Padhye, Chinmay [mailto:c_padhye@trillium.com]
Sent: Wednesday, September 05, 2001 3:25 PM
To: 'sip@ietf.org'
Subject: [Sip] Questions about the SIP Replaces Header draft.


Hello,

	I have a few questions and comments regarding the SIP Replaces
Header draft -
http://www.softarmor.com/sipwg/drafts/draft-biggs-sip-replaces-01.txt.

1)	In section 3 the draft states -
	"The to-tag and from-tag parameters MUST be included in the Replaces
header, as they are required for unique call-leg matching."

	In section 4 the draft states -
	"If the Replaces header matches more than one call-leg, the user
agent MAY use the Referred-By header if present to attempt to match the call
with an appropriate call-leg, but should otherwise ignore the header."

	The REFER draft says that the Referred-By header is mandatory
(section 3.2 of REFER 01 draft). Hence the words "if present" in the above
statement must be removed. 

[Sriram] The Refer draft says its mandatory in a REFER. The Replaces draft
         is talking about INVITEs. The Replaces header is sent only in an
         INVITE. The Refer draft goes on the say that the Referred-by may
         be carried in other SIP Requests like INVITEs so no changes are
         required.

	I also have a question regarding this -
	
	a)	When will a Replaces header match more than one call-leg.
The statements in the section 3 and 4 seem to contradict each other.

2)	In section 4 of the draft it says - 
	
	"If the Replaces header matches an unestablished call leg, that it,
the INVITE request for the call has not received or been sent a final
response, the Replaces header MUST be ignored."

	The "it" is a typo and should be "is".

	My question is - 
	How will a Replaces header match an unestablished call leg when a
response has not been received for an INVITE?



3)	I think the figures shown with the examples do not conform to the
latest REFER draft. None of the figures show NOTIFY being used. 

[Sriram]  Correct! A new version needs to be done. Also need the 202 for 
          the Refer.

4)	The reference to the cc draft - reference [4], is to the old draft.

Regards,

Chinmay

_______________________________________________
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