RFC 8123

Requirements for Marking SIP Messages to be Logged, March 2017

Canonical URL:
https://www.rfc-editor.org/rfc/rfc8123.txt
File formats:
Plain TextPDF
Status:
INFORMATIONAL
Authors:
P. Dawes
C. Arunachalam
Stream:
IETF
Source:
insipid (art)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC8123

Discuss this RFC: Send questions or comments to insipid@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF


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.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader