Marking SIP Messages to Be Logged
RFC 8497, “Marking SIP Messages to Be Logged”, is a Proposed Standard document published in November 2018 by P. Dawes, C. Arunachalam. The canonical text is published by the RFC Editor.
Abstract
SIP networks use signaling monitoring tools to diagnose user-reported problems and to perform regression testing if network or user agent (UA) 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 user agents and therefore impractical to monitor SIP signaling end to end.
This document describes an indicator for the SIP protocol that can be used to mark signaling as being of interest to logging. Such marking will typically be applied as part of network testing controlled by the network operator and is not used in normal user agent signaling. Operators of all networks on the signaling path can agree to carry such marking end to end, including the originating and terminating SIP user agents, even if a session originates and terminates in different networks.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8497 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8496 P-Charge-Info: A Private Header Field Extension to the Session Initiation Protocol
- RFC 8495 Allocation Token Extension for the Extensible Provisioning Protocol
- RFC 8494 Multicast Email over Allied Communications Publication 142
- RFC 8493 The BagIt File Packaging Format
- RFC 8501 Reverse DNS in IPv6 for Internet Service Providers
- RFC 8502 L2L3 VPN Multicast MIB
- RFC 8491 Signaling Maximum SID Depth Using IS-IS
- RFC 8503 BGP/MPLS Layer 3 VPN Multicast Management Information Base