Browse Prior Art Database

Requirements for Marking SIP Messages to be Logged (RFC8123)

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

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

P. Dawes: AUTHOR [+2]

Abstract

Service providers, enterprises, and others who operate networks that use SIP (see [RFC3261]) need the ability to debug problems reported by end users and also to run regression tests if SIP client software/ hardware is upgraded. Such debugging and testing might be confined to a single service provider or network, or they may occur between the administrative domains of different network operators, including domains in different countries that are interconnected through networks belonging to one or more third parties.

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

Internet Engineering Task Force (IETF)                          P. Dawes Request for Comments: 8123                                Vodafone Group Category: Informational                                   C. Arunachalam ISSN: 2070-1721                                            Cisco Systems                                                               March 2017

            Requirements for Marking SIP Messages to be Logged

Abstract

   SIP networks use signaling monitoring tools to debug customer-    reported problems and for regression testing if network or client    software is upgraded.  As networks grow and become interconnected,    including connection via transit networks, it becomes impractical to    predict the path that SIP signaling will take between clients and,    therefore, impractical to monitor SIP signaling end-to-end.

   This document describes the requirements for adding an indicator to    the SIP Protocol Data Unit (PDU) or a SIP message that marks the PDU    as a candidate for logging.  Such a marking will typically be applied    as part of network testing controlled by the network operator and not    used in regular client signaling.  However, such a marking can be    carried end-to-end, including the SIP terminals, even if a session    originates and terminates in different networks.

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/rfc8123.

 Dawes & Arunachalam           Informational                     [Page 1]
 RFC 8123                     Log Me" Marker                   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. ...