A solution for the HERFP caused by forked SIP INVITE requests
draft-jbemmel-sipping-herfp-solution-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jeroen van Bemmel | ||
| Last updated | 2005-09-15 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes a solution to the Heterogeneous Error Response Forking Problem (HERFP), a situation in which a UAC remains unaware of elements that are responding to its INVITE with a 'repairable' error response, because a forking proxy in the signalling path only forwards what it considers the 'best' final response. This issue may cause communication establishment to be delayed or even fail. To address this issue this document proposes a new method [preliminarily called 'FIX'] to be used by a forking proxy that detects a HERFP to notify the UAC of a repairable error.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)