Re: [Sipping] Possible Solution to HERFP

Rohan Mahy <rohan@ekabal.com> Sat, 09 July 2005 10:00 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DrC8Y-0005Yd-16; Sat, 09 Jul 2005 06:00:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DrC8W-0005YY-Do for sipping@megatron.ietf.org; Sat, 09 Jul 2005 06:00:40 -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 GAA18739 for <sipping@ietf.org>; Sat, 9 Jul 2005 06:00:37 -0400 (EDT)
Received: from figas.ekabal.com ([204.61.215.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DrCa3-0002fu-NO for sipping@ietf.org; Sat, 09 Jul 2005 06:29:10 -0400
Received: from [131.161.248.83] (open-131-161-248-83.cliq.com [131.161.248.83]) (authenticated) by figas.ekabal.com (8.11.6/8.11.6) with ESMTP id j69A0R115539; Sat, 9 Jul 2005 03:00:27 -0700
In-Reply-To: <001501c58466$1e8db060$6502a8c0@BEMBUSTER>
References: <dbf0b6ae20c7c5636fe0b2660c1dc1c3@ekabal.com> <001501c58466$1e8db060$6502a8c0@BEMBUSTER>
Mime-Version: 1.0 (Apple Message framework v622)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <172b63a380c152e72053e1b390d9afe4@ekabal.com>
Content-Transfer-Encoding: 7bit
From: Rohan Mahy <rohan@ekabal.com>
Subject: Re: [Sipping] Possible Solution to HERFP
Date: Sat, 09 Jul 2005 03:00:30 -0700
To: Jeroen van Bemmel <jbemmel@zonnet.nl>
X-Mailer: Apple Mail (2.622)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit
Cc: Rohan Mahy <rohan@ekabal.com>, '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

On Jul 9, 2005, at 2:10, Jeroen van Bemmel wrote:

> Hi Rohan,
>
> Section 3 picture at the end: what happens if UAS1 sends some 
> provisional response (with a to-tag) before sending the 415?

Why would UAS1 send any provisional response (other than a 100 Trying) 
before figuring out there was an error?  I've never seen an 
implementation do this, and the spec is pretty clear that you 
immediately send these error before you get the the processing stage 
where you would normally send a 18x.

> If the proxy generates a to-tag of its own for the 130, wouldn't the 
> UAC get confused?

are you asking this in general, or only after the UAS sent its own 
to-tag?

thanks,
-rohan

> Jeroen
>
> ----- Original Message ----- From: "Rohan Mahy" <rohan@ekabal.com>
> To: "'sipping' WG" <sipping@ietf.org>
> Cc: "Rohan Mahy" <rohan@ekabal.com>
> Sent: Saturday, July 09, 2005 4:41 AM
> Subject: [Sipping] Possible Solution to HERFP
>
>
>> 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
>>
>> thanks,
>> -rohan
>> (as an individual)
>>
>>
>> _______________________________________________
>> 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


_______________________________________________
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