Re: [sipcore] Reason as a parameter rather than an escaped header

Paul Kyzivat <> Wed, 24 November 2010 22:35 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 85B1328C1A4 for <>; Wed, 24 Nov 2010 14:35:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -110.213
X-Spam-Status: No, score=-110.213 tagged_above=-999 required=5 tests=[AWL=-0.214, BAYES_00=-2.599, J_CHICKENPOX_51=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 0qpcYWDdfGTj for <>; Wed, 24 Nov 2010 14:35:33 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id DF8A428C129 for <>; Wed, 24 Nov 2010 14:35:32 -0800 (PST)
Authentication-Results:; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAFsi7UxAZnwM/2dsb2JhbACjCXGjEJsuhUcEhFuGBYMP
X-IronPort-AV: E=Sophos;i="4.59,250,1288569600"; d="scan'208";a="185909137"
Received: from ([]) by with ESMTP; 24 Nov 2010 22:36:33 +0000
Received: from [] ([]) by (8.13.8/8.14.3) with ESMTP id oAOMaWtW012387; Wed, 24 Nov 2010 22:36:32 GMT
Message-ID: <>
Date: Wed, 24 Nov 2010 17:36:32 -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
To: Christer Holmberg <>
References: <> <> <>, <> <>
In-Reply-To: <>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "Worley, Dale R (Dale)" <>, "" <>
Subject: Re: [sipcore] Reason as a parameter rather than an escaped header
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: Wed, 24 Nov 2010 22:35:36 -0000

On 11/24/2010 3:27 PM, Christer Holmberg wrote:
> Hi,
>>> I would suggest that the best way forward is that we keep the current
>>> text as is and note that any additional Reason headers that are defined
>>> in the future MUST be interpreted in the same manner.  However, I do NOT
>>> think we should hold up 4244bis until we get full agreement on adding
>>> new Reason header values for applications as I firmly believe it is
>>> orthogonal - it can work based upon the current normative approach and
>>> interpretation of the Reason in the hi-entries.  We can debate till the
>>> end of time (or the end of SIPCORE WG as we did with other broken things
>>> in SIP) that this wasn't the right approach, but it is what it is and I
>>> think it's time to move forward.
>> I agree that 4244bis should not be held up because of the new reason
>> values draft(s?).
>> At this point I would just like some clarity whether the *way* reasons
>> are used in the examples in
>> draft-mohali-sipcore-reason-extension-application-00 - reasons without
>> responses - is thought to be *valid* in the context of 4244bis. If the
>> answer is NO, then I'll shut up, and let Marianne or somebody else from
>> 3gpp complain if they think it should be.
>> If the answer is YES - that usage is considered valid according to
>> 4244bis, then I still want to know why, and perhaps see some additional
>> text to make it clear.
> I think we should ask ourselves: assuming we allowed to do what Marianne is proposing, would anything break?
> Does anyone really care whether a H-I entry was inserted based on a "real" or "virtual" response? Aren't people more interested in the actual reason value?

I don't currently see a problem with permitting this (though I'm 
interested to hear if somebody else sees an issue).

But IMO the current text doesn't suggest to me that this is valid.
So if the desire is for it to be valid it would be good to have some 
text that makes it so.