Re: [sipcore] Why doesn't 4244bis cover Marianne's use-case?

Paul Kyzivat <> Fri, 19 November 2010 18:15 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 775623A6876 for <>; Fri, 19 Nov 2010 10:15:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -110.454
X-Spam-Status: No, score=-110.454 tagged_above=-999 required=5 tests=[AWL=0.145, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id sOr7gFGLcwk0 for <>; Fri, 19 Nov 2010 10:15:46 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 69D1B3A6850 for <>; Fri, 19 Nov 2010 10:15:46 -0800 (PST)
Authentication-Results:; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Au4FAK9N5kxAZnwM/2dsb2JhbACUX44CcaImmz+FSwSEWoYBgw4
X-IronPort-AV: E=Sophos;i="4.59,224,1288569600"; d="scan'208";a="184134376"
Received: from ([]) by with ESMTP; 19 Nov 2010 18:16:36 +0000
Received: from [] ( []) by (8.13.8/8.14.3) with ESMTP id oAJIGaZW008941 for <>; Fri, 19 Nov 2010 18:16:36 GMT
Message-ID: <>
Date: Fri, 19 Nov 2010 13:16:35 -0500
From: Paul Kyzivat <>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
References: <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [sipcore] Why doesn't 4244bis cover Marianne's use-case?
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 19 Nov 2010 18:15:47 -0000

I'm inclined to agree that this draft 
(draft-mohali-sipcore-reason-extension-application, not 
draft-mohali-diversion-history-info) *ought* to be orthogonal to 
4244bis, and "just work" with it.

BUT, in reality I'm not convinced that this is so. The following is from 

    For retargets that are the result of an explicit SIP response, a
    Reason MUST be associated with the hi-targeted-to-uri.  If the SIP
    response does not include a Reason header (see [RFC3326]), the SIP
    Response Code that triggered the retargeting MUST be included as the
    Reason associated with the hi-targeted-to-uri that has been
    retargeted.  If the response contains a Reason header for a protocol
    that is not SIP (e.g., Q.850), it MUST be captured as an additional
    Reason associated with the hi-targeted-to-uri that has been
    retargeted, along with the SIP Response Code.  If the Reason header
    is a SIP reason, then it MUST be used as the Reason associated with
    the hi-targeted-to-uri rather than the SIP response code.

Note that the above is limited to "retargets that are the result of an 
explicit SIP response". But when I look at the call flows in the draft, 
none of the retargets are the result of a sip response. Rather, they are 
spontaneous retargets due to server logic. 4244bis does not cover using 
the Reason header in H-I entries for this purpose.


On 11/19/2010 11:42 AM, Worley, Dale R (Dale) wrote:
> ________________________________________
> From: [] On Behalf Of Hadriel Kaplan []
> It was unfortunate that we ran out of time in sipcore to talk about Marianne's draft, because I think it's a kind of litmus test of rfc4244bis.  Or else I think I must be missing something very basic. (easily the case)
> _______________________________________________
> As others have said in other terms,  draft-mohali-diversion-history-info is orthogonal to 4244bis.  draft-mohali provides additional Reason values that provide more detailed information on why a call was routed as it was.  Those Reason values will be recorded in H-I according to 4244bis.  In a sense, draft-mohali *is* a litmus test of 4244bis, because without H-I, the value of the new Reason values would be dramatically reduced.  But since the two are orthogonal, draft-mohali needs to be specified, but it can be specified separately.
> Dale
> _______________________________________________
> sipcore mailing list