Skip to main content

Requirements for Marking SIP Messages to be Logged

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Peter Dawes
Last updated 2014-07-21 (Latest revision 2014-01-16)
Replaces draft-dawes-dispatch-logme-reqs
Replaced by draft-ietf-insipid-logme-reqs
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-insipid-logme-reqs
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


SIP networks use signalling monitoring tools to diagnose user reported problem 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 signalling will take between clients, and therefore impractical to monitor SIP signalling end-to-end. This draft describes requirements for adding an indicator to 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 client signalling. However, such marking can be carried end-to-end including the SIP terminals, 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.)