Location Parameter for the SIP Reason Header Field
draft-jesske-dispatch-reason-loc-q850-00

Document Type Active Internet-Draft (individual)
Last updated 2017-02-10
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Dispatch                                                       R. Jesske
Internet-Draft                                          Deutsche Telekom
Updates: RFC6442 (if approved)                         February 10, 2017
Intended status: Standards Track
Expires: August 14, 2017

           Location Parameter for the SIP Reason Header Field
              draft-jesske-dispatch-reason-loc-q850-00.txt

Abstract

   The SIP Reason header field is defined for Q.850 cause values.  Some
   services in SIP networks may need to know the 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 http://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 August 14, 2017.

Copyright Notice

   Copyright (c) 2017 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
   (http://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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Jesske                   Expires August 14, 2017                [Page 1]
Internet-Draft             Location Parameter              February 2017

Table of Contents

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

1.  Introduction

   The SIP Reason header field specification [RFC3326] describes a SIP
   header field that is used to indicate that a SIP request or response
   is carrying the reason of release.  The 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 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 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 BYE message containing the location
   of the call release.  The ISDN location is defined in [Q.850].

Jesske                   Expires August 14, 2017                [Page 2]
Internet-Draft             Location Parameter              February 2017
Show full document text