Re: [Sipping] Possible Solution to HERFP

"Vijay K. Gurbani" <vkg@lucent.com> Mon, 11 July 2005 16:52 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ds1WP-00015A-Tk; Mon, 11 Jul 2005 12:52:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ds1WO-000155-48 for sipping@megatron.ietf.org; Mon, 11 Jul 2005 12:52:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28741 for <sipping@ietf.org>; Mon, 11 Jul 2005 12:52:40 -0400 (EDT)
Received: from ihemail2.lucent.com ([192.11.222.163]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ds1yO-0007vl-5K for sipping@ietf.org; Mon, 11 Jul 2005 13:21:42 -0400
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70]) by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id j6BGqMQs017851; Mon, 11 Jul 2005 11:52:22 -0500 (CDT)
Received: from [135.185.173.147] (il0015vkg1.ih.lucent.com [135.185.173.147]) by ihmail.ih.lucent.com (8.11.7p1+Sun/EMS-1.5 sol2) id j6BGqLI21051; Mon, 11 Jul 2005 11:52:21 -0500 (CDT)
Message-ID: <42D2A3C6.10505@lucent.com>
Date: Mon, 11 Jul 2005 11:52:22 -0500
From: "Vijay K. Gurbani" <vkg@lucent.com>
Organization: Wireless Networks Research and Development
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Rohan Mahy <rohan@ekabal.com>
Subject: Re: [Sipping] Possible Solution to HERFP
References: <dbf0b6ae20c7c5636fe0b2660c1dc1c3@ekabal.com>
In-Reply-To: <dbf0b6ae20c7c5636fe0b2660c1dc1c3@ekabal.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
Cc: 'sipping' WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

Rohan Mahy wrote:
> Hi Folks,
> 
> I just submitted a new individual I-D that describes a possible  
> solution to the Heterogeneous Error Response Forking Protocol.  Until  
> it appears in the archives, you can find it here:
> 
> https://scm.sipfoundry.org/rep/ietf-drafts/rohan/herf-fix/draft-mahy- 
> sipping-herfp-fix-00.txt
> https://scm.sipfoundry.org/rep/ietf-drafts/rohan/herf-fix/draft-mahy- 
> sipping-herfp-fix-00.html

Rohan:

Interesting approach to the problem.  After a quick reading, it
strikes me that a long time ago, we had a SIP mantra that was oft
repeated: "Every transaction completes independent of others."

Did we break this mantra?  In Figure 4, there are two INVITEs
leaving the UAC, the second in response to the 130.  However,
there is only one final response coming back to the UAC (the
200 OK).  Since the draft states that the original INVITE request
is unaffected by the new request, it would seem that the UAC
will wait for another final response to balance out the original
request?

Before proposing any solutions, wanted to make sure that we do
indeed have a dangling INVITE problem...

Thanks,

- vijay
-- 
Vijay K. Gurbani, Ph.D.  vkg@{lucent.com,research.bell-labs.com,acm.org}
Wireless Networks Group/Internet Software and Services
Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440
Naperville, Illinois 60566     Voice: +1 630 224 0216

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP