Skip to main content

Marking SIP Messages to be Logged

Document Type Replaced Internet-Draft (individual)
Author Peter Dawes
Last updated 2015-01-22 (Latest revision 2014-07-21)
Replaced by draft-ietf-insipid-logme-marking, RFC 8497
Stream (None)
Expired & archived
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)
This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at:


SIP networks use signalling monitoring tools to diagnose user reported problems and for regression testing if network or user agent software is upgraded. As networks grow and become interconnected, including connection via transit networks, it becomes impractical to predict the path that SIP signalling will take between user agents, and therefore impractical to monitor SIP signalling end-to-end. This document describes an indicator for the SIP protocol which can be used to mark signalling as of interest to logging. Such marking will typically be applied as part of network testing controlled by the network operator and not used in regular user agent signalling. However, such marking can be carried end-to-end including the SIP user agents, even if a session originates and terminates in different networks.


Peter Dawes

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)