[Sipping-tispan] Reason header in Responses

"Jesske, R" <R.Jesske@t-com.net> Tue, 18 October 2005 09:27 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERnkf-0003y4-8r; Tue, 18 Oct 2005 05:27:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERnka-0003xp-Oy; Tue, 18 Oct 2005 05:27:18 -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 FAA16251; Tue, 18 Oct 2005 05:27:08 -0400 (EDT)
Received: from tcmail33.telekom.de ([217.6.95.240]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERnw4-00070f-S1; Tue, 18 Oct 2005 05:39:10 -0400
Received: from s4de8psaans.mitte.t-com.de by tcmail31.dmz.telekom.de with ESMTP; Tue, 18 Oct 2005 11:24:19 +0200
Received: by S4DE8PSAANS.blf.telekom.de with Internet Mail Service (5.5.2653.19) id <VBY7JPJJ>; Tue, 18 Oct 2005 11:24:18 +0200
Message-Id: <E7666D92C64C2845AEF12636FF94F95202319FF5@S4DE8PSAAGQ.blf.telekom.de>
From: "Jesske, R" <R.Jesske@t-com.net>
To: sipping@ietf.org, sipping-tispan@ietf.org
Date: Tue, 18 Oct 2005 11:24:13 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Cc:
Subject: [Sipping-tispan] Reason header in Responses
X-BeenThere: sipping-tispan@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of requirements for SIP introduced by ETSI TISPAN <sipping-tispan.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping-tispan>, <mailto:sipping-tispan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sipping-tispan>
List-Post: <mailto:sipping-tispan@ietf.org>
List-Help: <mailto:sipping-tispan-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping-tispan>, <mailto:sipping-tispan-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0537687284=="
Sender: sipping-tispan-bounces@ietf.org
Errors-To: sipping-tispan-bounces@ietf.org

Dear all,
Still the use of the Reason header confuses me.
With regard to the discussion of the retargeting draft the inclusion of a 486 in a 302 is discussed as possible.
But on the other side the inclusion of a Q.850 reason header in a response is not allowed.
Could I have some Guidance How I have to understand the following phrase written in RFC 3326 Reason Header:

   Initially, the Reason header field defined here appears to be most
   useful for BYE and CANCEL requests, but it can appear in any request
   within a dialog, in any CANCEL request and in any response whose
   status code explicitly allows the presence of this header field.

   Note that the Reason header field is usually not needed in responses
   because the status code and the reason phrase already provide
   sufficient information.

Does this mean that if I specify the use of SIP Reason in a response (e.G in a IETF RFC, ITU-T or ETSI Specification) it is allowed to use this now or do I need a special IETF draft to allow the use of Q.850 Reasons in responses?

Best Regards

Roland


Deutsche Telekom AG
T-Com Zentrale
Roland Jesske, TE332-2
Section TE33; Signalling, Gateways and Switching Systems 
 64307 Darmstadt, Germany
Phone:  +49 6151 83-5940 
Fax:      +49 6151 83-4577 
email:   r.jesske@t-com.net

_______________________________________________
Sipping-tispan mailing list
Sipping-tispan@ietf.org
https://www1.ietf.org/mailman/listinfo/sipping-tispan