Requirements for Marking SIP Messages to be Logged
RFC 8123, “Requirements for Marking SIP Messages to be Logged”, is an Informational document published in March 2017 by P. Dawes, C. Arunachalam. The canonical text is published by the RFC Editor.
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 8123 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8122 Connection-Oriented Media Transport over the Transport Layer Security Protocol in the Session Description Protocol
- RFC 8124 The Session Description Protocol WebSocket Connection URI Attribute
- RFC 8121 Mutual Authentication Protocol for HTTP: Cryptographic Algorithms Based on the Key Agreement Mechanism 3
- RFC 8125 Requirements for Password-Authenticated Key Agreement Schemes
- RFC 8120 Mutual Authentication Protocol for HTTP
- RFC 8126 Guidelines for Writing an IANA Considerations Section in RFCs
- RFC 8119 SIP "cause" URI Parameter for Service Number Translation
- RFC 8127 Mobile Access Gateway Configuration Parameters Controlled by the Local Mobility Anchor