The Common Log Format (CLF) for the Session Initiation Protocol (SIP): Framework and Data Model
draft-ietf-sipclf-problem-statement-10

The information below is for an old version of the document
Document Type Active Internet-Draft (sipclf WG)
Last updated 2012-02-13 (latest revision 2012-02-06)
Replaces draft-gurbani-sipclf-problem-statement
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Doc Shepherd Follow-up Underway
Document shepherd Peter Musgrave
Shepherd write-up Show (last changed 2011-07-14)
IESG IESG state IESG Evaluation::AD Followup
Consensus Boilerplate Unknown
Telechat date
Needs a YES.
Responsible AD Robert Sparks
IESG note Peter Musgrave (musgravepj@gmail.com) is the document shepherd.
Send notices to sipclf-chairs@tools.ietf.org, draft-ietf-sipclf-problem-statement@tools.ietf.org
SIPCLF                                                   V. Gurbani, Ed.
Internet-Draft                         Bell Laboratories, Alcatel-Lucent
Intended status: Standards Track                          E. Burger, Ed.
Expires: August 9, 2012                            Georgetown University
                                                               T. Anjali
                                        Illinois Institute of Technology
                                                             H. Abdelnur
                                                               O. Festor
                                                                   INRIA
                                                        February 6, 2012

 The Common Log Format (CLF) for the Session Initiation Protocol (SIP):
                        Framework and Data Model
                 draft-ietf-sipclf-problem-statement-10

Abstract

   Well-known web servers such as Apache and web proxies like Squid
   support event logging using a common log format.  The logs produced
   using these de-facto standard formats are invaluable to system
   administrators for trouble-shooting a server and tool writers to
   craft tools that mine the log files and produce reports and trends.
   Furthermore, these log files can also be used to train anomaly
   detection systems and feed events into a security event management
   system.  The Session Initiation Protocol (SIP) does not have a common
   log format, and as a result, each server supports a distinct log
   format that makes it unnecessarily complex to produce tools to do
   trend analysis and security detection.  We propose a common log file
   format for SIP servers that can be used uniformly by user agents,
   proxies, registrars, redirect servers as well as back-to-back user
   agents.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Gurbani, et al.          Expires August 9, 2012                 [Page 1]
Internet-Draft                   SIP CLF                   February 2012

   This Internet-Draft will expire on August 9, 2012.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Gurbani, et al.          Expires August 9, 2012                 [Page 2]
Internet-Draft                   SIP CLF                   February 2012

Table of Contents

   1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Problem statement  . . . . . . . . . . . . . . . . . . . . . .  5
   4.  What SIP CLF is and what it is not . . . . . . . . . . . . . .  5
   5.  Alternative approaches to SIP CLF  . . . . . . . . . . . . . .  6
     5.1.  SIP CLF and CDRs . . . . . . . . . . . . . . . . . . . . .  6
     5.2.  SIP CLF and Wireshark packet capture . . . . . . . . . . .  7
   6.  Motivation and use cases . . . . . . . . . . . . . . . . . . .  8
   7.  Challenges in establishing a SIP CLF . . . . . . . . . . . . .  9
   8.  Data model . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     8.1.  SIP CLF mandatory fields . . . . . . . . . . . . . . . . . 11
     8.2.  Mandatory fields and SIP entities  . . . . . . . . . . . . 13
   9.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
     9.1.  UAC registration . . . . . . . . . . . . . . . . . . . . . 15
     9.2.  Direct call between Alice and Bob  . . . . . . . . . . . . 16
     9.3.  Single downstream branch call  . . . . . . . . . . . . . . 18
     9.4.  Forked call  . . . . . . . . . . . . . . . . . . . . . . . 23
Show full document text