ISUP Cause Location Parameter for the SIP Reason Header Field
draft-ietf-sipcore-reason-q850-loc-04

Document Type Active Internet-Draft (sipcore WG)
Last updated 2018-08-20
Replaces draft-sipcore-reason-q850-loc
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state In WG Last Call
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Sipcore                                                        R. Jesske
Internet-Draft                                          Deutsche Telekom
Updates: RFC3326 (if approved)                           August 20, 2018
Intended status: Standards Track
Expires: February 21, 2019

     ISUP Cause Location Parameter for the SIP Reason Header Field
               draft-ietf-sipcore-reason-q850-loc-04.txt

Abstract

   The SIP Reason header field is defined for carrying ISDN User Part
   (ISUP) cause values as well as SIP response codes.  Some services in
   SIP networks may need to know the ISUP location where the call was
   released in the PSTN network to correctly interpret the reason of
   release.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on February 21, 2019.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) 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

Jesske                  Expires February 21, 2019               [Page 1]
Internet-Draft       ISUP Release Location Parameter         August 2018

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Rationale . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   4.  Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Example . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   4
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Registration of location Parameter for Reason header
           field . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   10. Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The SIP Reason header field specification [RFC3326] describes a SIP
   header field that is used to indicate that a SIP request is carrying
   the reason of release.  It may be an SIP response or ISUP release
   cause as specified within [Q.850].  [RFC3326] does specify that a
   ISUP [Q.850] cause code can be carried within a SIP response.  The
   [Q.850] location information identifies the part of the ISUP network
   where the call was released.

   This document adds a location value parameter to the reason-extension
   parameter in [RFC3326] so that the [Q.850] location value can be
   interworked from the PSTN.  The interworking from PTSN needs only to
   include the location received by the interworking gateway.

2.  Terminology

   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 [RFC2119].

3.  Rationale

   The primary intent of the parameter defined in this specification is
   for use in IMS (IP Multimedia Subsystem) networks defined by 3GPP but
   also open to be used by any other network.  The purpose of this
   parameter is to transport the location of call release from the
   originating PSTN entity to the SIP entity receiving the response or

Jesske                  Expires February 21, 2019               [Page 2]
Internet-Draft       ISUP Release Location Parameter         August 2018

   BYE message containing the location of the call release.  The ISDN
   location is defined in [Q.850].

4.  Mechanism

   As defined by [RFC3326] a Reason header field MAY appear in any
   request in a dialog, in any CANCEL request and in any response whose
   status code explicitly allows the presence of this header field.  The
Show full document text