[Sip] Questions about the SIP Replaces Header draft.
"Padhye, Chinmay" <c_padhye@trillium.com> Wed, 05 September 2001 20:44 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 QAA21794 for <sip-archive@odin.ietf.org>; Wed, 5 Sep 2001 16:44:12 -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 QAA22785; Wed, 5 Sep 2001 16:25:26 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA22754 for <sip@ns.ietf.org>; Wed, 5 Sep 2001 16:25:23 -0400 (EDT)
Received: from thalia.fm.intel.com (fmfdns02.fm.intel.com [132.233.247.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21400 for <sip@ietf.org>; Wed, 5 Sep 2001 16:23:55 -0400 (EDT)
Received: from fmsmsxvs043.fm.intel.com (fmsmsxv043-1.fm.intel.com [132.233.48.128]) by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4, v 1.42 2001/09/04 16:24:19 root Exp $) with SMTP id UAA19186 for <sip@ietf.org>; Wed, 5 Sep 2001 20:25:21 GMT
Received: from fmsmsx19.fm.intel.com ([132.233.222.210]) by fmsmsxvs043.fm.intel.com (NAVGW 2.5.1.6) with SMTP id M2001090513244129374 ; Wed, 05 Sep 2001 13:24:41 -0700
Received: by fmsmsx19.fm.intel.com with Internet Mail Service (5.5.2653.19) id <SKXCFXGG>; Wed, 5 Sep 2001 13:25:20 -0700
Message-ID: <F1CE15E08172D4119247009027AE9D500E4EB21E@FMSMSX37>
From: "Padhye, Chinmay" <c_padhye@trillium.com>
To: "'sip@ietf.org'" <sip@ietf.org>
Date: Wed, 05 Sep 2001 13:25:19 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Subject: [Sip] Questions about the SIP Replaces Header draft.
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
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. 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. 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
- [Sip] Questions about the SIP Replaces Header dra… Padhye, Chinmay
- RE: [Sip] Questions about the SIP Replaces Header… Sriram Parameswar
- Re: [Sip] Questions about the SIP Replaces Header… Henry Chen
- Re: [Sip] Questions about the SIP Replaces Header… Henry Chen