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

Document Type Active Internet-Draft (sipcore WG)
Last updated 2019-05-13 (latest revision 2019-03-15)
Replaces draft-sipcore-reason-q850-loc
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Brian Rosen
Shepherd write-up Show (last changed 2018-10-23)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Ben Campbell
Send notices to Brian Rosen <br@brianrosen.net>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state RFC-EDITOR
Sipcore                                                        R. Jesske
Internet-Draft                                          Deutsche Telekom
Updates: 3326 (if approved)                               March 13, 2019
Intended status: Standards Track
Expires: September 14, 2019

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

Abstract

   The SIP Reason header field is defined for carrying ISUP (Integrated
   Services Digital Network User Part) 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.  This document will update
   RFC3326.

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 September 14, 2019.

Copyright Notice

   Copyright (c) 2019 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 September 14, 2019               [Page 1]
Internet-Draft       ISUP Release Location Parameter          March 2019

   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 . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Example . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Registration of location Parameter for Reason header
           field . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   10. Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

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.  The reason of release indicates why a SIP
   Dialog or a PSTN call, in case where the call was interworked to the
   PSTN, was terminated.  This may be a normal termination or a
   termination based on a failure within an entity or other reasons like
   congestion.  The reason may be an SIP response or ISUP release cause
   as specified within [Q.850].  [RFC6432] specifies that a ISUP [Q.850]
   cause code can be carried within a SIP response, but not the Q.850
   location information.  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.  [Q.850]
   describes the definition of cause code values and locations used in
   ISDN and DSS1 environment.  The cause code is used for identifying
   the reason of release of a call and the location identifies where the
   call was released.

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP

Jesske                 Expires September 14, 2019               [Page 2]
Internet-Draft       ISUP Release Location Parameter          March 2019
Show full document text