Browse Prior Art Database

SIP "cause" URI Parameter for Service Number Translation (RFC8119)

IP.com Disclosure Number: IPCOM000249673D
Original Publication Date: 2017-Mar-01
Included in the Prior Art Database: 2017-Mar-16
Document File: 24 page(s) / 24K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Mohali: AUTHOR [+2]

Abstract

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.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 11% of the total text.

Internet Engineering Task Force (IETF)                         M. Mohali Request for Comments: 8119                                        Orange Updates: 4458                                                  M. Barnes Category: Informational                      MLB@Realtime Communications ISSN: 2070-1721                                               March 2017

         SIP "cause" URI Parameter for Service Number Translation

Abstract

   RFC 4458 (regarding SIP URIs for applications) defines a "cause" URI    parameter, which may appear in the Request-URI of a SIP request, that    is used to indicate a reason why the request arrived to the User    Agent Server (UAS) receiving the message.  This document updates RFC    4458 by creating a new predefined value for the "cause" URI parameter    to cover service number translation for cases of retargeting due to    specific service action leading to the translation of a called    service access number.  This document also provides guidance, which    was missing in RFC 4458, for using the "cause" URI parameter within    the History-Info header field, since this use is mandatory in some IP    networks' implementations.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   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).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc8119.

Mohali & Barnes               Informational                     [Page 1]
 RFC 8119          Cause for Service Number Translation        March 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...