Re: [Sipping] Possible Solution to HERFP

"Jeroen van Bemmel" <jbemmel@zonnet.nl> Mon, 18 July 2005 21:21 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dud3M-0003Bc-DY; Mon, 18 Jul 2005 17:21:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dud3K-0003BN-Bl for sipping@megatron.ietf.org; Mon, 18 Jul 2005 17:21:30 -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 RAA29985 for <sipping@ietf.org>; Mon, 18 Jul 2005 17:21:28 -0400 (EDT)
Received: from smtp1.versatel.nl ([62.58.50.88]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DudWn-0005xE-2D for sipping@ietf.org; Mon, 18 Jul 2005 17:51:59 -0400
Received: (qmail 29694 invoked by uid 0); 18 Jul 2005 21:21:11 -0000
Received: from unknown (HELO BEMBUSTER) ([81.59.101.130]) (envelope-sender <jbemmel@zonnet.nl>) by smtp1.versatel.nl (qmail-ldap-1.03) with SMTP for < >; 18 Jul 2005 21:21:11 -0000
Message-ID: <004e01c58bde$9dde0160$6502a8c0@BEMBUSTER>
From: Jeroen van Bemmel <jbemmel@zonnet.nl>
To: Rohan Mahy <rohan@ekabal.com>, 'sipping' WG <sipping@ietf.org>
References: <dbf0b6ae20c7c5636fe0b2660c1dc1c3@ekabal.com>
Subject: Re: [Sipping] Possible Solution to HERFP
Date: Mon, 18 Jul 2005 23:21:09 +0200
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="response"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2527
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 7bit
Cc:
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,

About the HERFP issue. I was not involved in earlier discussions, so I 
apologize if I am repeating something that was already said

What if HERFP was addressed similar to how a proxy handles multiple 401+407 
responses: all repairable errors are collected and returned as one final 
response ( "4xx multiple responses" with the proxy generating a to-tag). The 
UA could then retry as its sees fit. Each error returned in this way should 
include an address to use to contact that specific entity only. The response 
body would probably be a good place for this collection of mayhem

To address the potential long waiting for some ringing endpoints that block 
forwarding of repairable errors, the UAC could simply include an 'Expires' 
header in the original INVITE, and/or maybe a special 'HERFP timeout' value 
to tell the proxy to CANCEL ringing things and return the best final 
response(s) at that point instead.

To address 2xx responses from hiding other alternatives, the proxy could 
append information about the pending repairable errors to the 2xx response 
before forwarding (for this case perhaps some header would be better than in 
the body). That would give the UAC an opportunity to try those other 
options. If some other branches have not returned yet, perhaps the proxy 
could append a header stating that ( i.e. "Proxy-HERFP-Pending: 3" )

Regards,

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