6432
PROPOSED STANDARD
Carrying Q.850 Codes in Reason Header Fields in SIP (Session Initiation Protocol) Responses
Authors: R. Jesske, L. Liess
Date: November 2011
Working Group: NON WORKING GROUP
Stream: IETF
Abstract
Although the use of the SIP (Session Initiation Protocol) Reason header field in responses is considered in general in RFC 3326, its use is not specified for any particular response code. Nonetheless, existing deployments have been using Reason header fields to carry failure-related Q.850 cause codes in SIP responses to INVITE requests that have been gatewayed to Public Switched Telephone Network (PSTN) systems. This document normatively describes the use of the Reason header field in carrying Q.850 cause codes in SIP responses. [STANDARDS-TRACK]
RFC 6432
PROPOSED STANDARD
Internet Engineering Task Force (IETF) R. Jesske
Request for Comments: 6432 L. Liess
Category: Standards Track Deutsche Telekom
ISSN: 2070-1721 November 2011
<span class="h1">Carrying Q.850 Codes in Reason Header Fields</span>
<span class="h1">in SIP (Session Initiation Protocol) Responses</span>
Abstract
Although the use of the SIP (Session Initiation Protocol) Reason
header field in responses is considered in general in <a href="./rfc3326">RFC 3326</a>, its
use is not specified for any particular response code. Nonetheless,
existing deployments have been using Reason header fields to carry
failure-related Q.850 cause codes in SIP responses to INVITE requests
that have been gatewayed to Public Switched Telephone Network (PSTN)
systems. This document normatively describes the use of the Reason
header field in carrying Q.850 cause codes in SIP responses.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc6432">http://www.rfc-editor.org/info/rfc6432</a>.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Jesske & Liess Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc6432">RFC 6432</a> Reason Header Field November 2011</span>
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
<a href="#section-1">1</a>. Overview ........................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-2">2</a>
<a href="#section-3">3</a>. Applicability ...................................................<a href="#page-3">3</a>
<a href="#section-4">4</a>. Security Considerations .........................................<a href="#page-3">3</a>
<a href="#section-5">5</a>. Acknowledgments .................................................<a href="#page-3">3</a>
<a href="#section-6">6</a>. Normative References ............................................<a href="#page-3">3</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Overview</span>
Although the use of the SIP (Session Initiation Protocol) Reason
header field in responses is considered in general in <a href="./rfc3326">RFC 3326</a>
[<a href="./rfc3326" title=""The Reason Header Field for the Session Initiation Protocol (SIP)"">RFC3326</a>], its use is not specified for any particular response code.
Nonetheless, existing deployments have been using Reason header
fields to carry failure-related Q.850 [<a href="#ref-Q.850" title=""Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part"">Q.850</a>] cause codes in SIP
responses to INVITE requests that have been gatewayed to PSTN
systems. This document normatively describes the use of the Reason
header field in SIP responses to carry Q.850 [<a href="#ref-Q.850" title=""Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part"">Q.850</a>] cause codes.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
This document uses terms from [<a href="./rfc3261" title=""SIP: Session Initiation Protocol"">RFC3261</a>].
<span class="grey">Jesske & Liess Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc6432">RFC 6432</a> Reason Header Field November 2011</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Applicability</span>
This document allows SIP responses to carry Reason header fields as
follows:
Any SIP Response message, with the exception of a 100 (Trying),
MAY contain a Reason header field with a Q.850 [<a href="#ref-Q.850" title=""Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part"">Q.850</a>] cause code.
The Reason header field is not needed in the 100 (Trying)
responses, since they are transmitted hop by hop, not end to end.
SIP responses with Reason header fields carrying values other than
Q.850 [<a href="#ref-Q.850" title=""Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part"">Q.850</a>] cause codes are outside of the scope of this
document.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
This specification allows the presence of the Reason header field
containing Q.850 [<a href="#ref-Q.850" title=""Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part"">Q.850</a>] cause codes in responses. The presence of
the Reason header field in a response does not affect the treatment
of the response. Nevertheless, there could be situations where a
wrong Q.850 [<a href="#ref-Q.850" title=""Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part"">Q.850</a>] cause code could, for example, cause an
announcement system to play the wrong information. To avoid such
situations, it is RECOMMENDED that this header field be protected by
a suitable integrity mechanism. The use of transport- or network-
layer hop-by-hop security mechanisms, such as Transport Layer
Security (TLS) or IPsec with appropriate cipher suites, can satisfy
this requirement.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgments</span>
Thanks to Gonzalo Camarillo and Mary Barnes for the detailed review
of this document.
Thanks to Paul Kyzivat, Mary Barnes, John Elwell, Keith Drage, and
Thomas Belling, who provided helpful comments, feedback, and
suggestions.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Normative References</span>
[<a id="ref-Q.850">Q.850</a>] "Usage of cause and location in the Digital Subscriber
Signalling System No. 1 and the Signalling System No. 7
ISDN User Part", ITU Recommendation Q.850, May 1998.
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
<span class="grey">Jesske & Liess Standards Track [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc6432">RFC 6432</a> Reason Header Field November 2011</span>
[<a id="ref-RFC3261">RFC3261</a>] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", <a href="./rfc3261">RFC 3261</a>,
June 2002.
[<a id="ref-RFC3326">RFC3326</a>] Schulzrinne, H., Oran, D., and G. Camarillo, "The Reason
Header Field for the Session Initiation Protocol (SIP)",
<a href="./rfc3326">RFC 3326</a>, December 2002.
Authors' Addresses
Roland Jesske
Deutsche Telekom
Heinrich-Hertz-Strasse 3-7
Darmstadt 64307
Germany
Phone: +4961515812766
EMail: [email protected]
Laura Liess
Deutsche Telekom
Heinrich-Hertz-Strasse 3-7
Darmstadt 64307
Germany
Phone: +4961515812761
EMail: [email protected]
Jesske & Liess Standards Track [Page 4]
Annotations
Select text to annotate