Marking SIP Messages to be Logged
draft-ietf-insipid-logme-marking-02

The information below is for an old version of the document
Document Type Expired Internet-Draft (insipid WG)
Last updated 2015-08-31 (latest revision 2015-02-27)
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd Gonzalo Salgueiro
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Gonzalo Salgueiro" <gsalguei@cisco.com>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-insipid-logme-marking-02.txt

Abstract

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.

Authors

Peter Dawes (peter.dawes@vodafone.com)

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