[sip-clf] RFC 6872 on The Common Log Format (CLF) for the Session Initiation Protocol (SIP): Framework and Information Model

rfc-editor@rfc-editor.org Thu, 14 February 2013 22:06 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: sip-clf@ietfa.amsl.com
Delivered-To: sip-clf@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id ED51321F844E; Thu, 14 Feb 2013 14:06:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.042
X-Spam-Status: No, score=-102.042 tagged_above=-999 required=5 tests=[AWL=-0.042, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id vrHEayoUO1W8; Thu, 14 Feb 2013 14:06:46 -0800 (PST)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 7036021F8ABD; Thu, 14 Feb 2013 14:06:46 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 236CDB1E002; Thu, 14 Feb 2013 14:06:17 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130214220617.236CDB1E002@rfc-editor.org>
Date: Thu, 14 Feb 2013 14:06:17 -0800 (PST)
Cc: sip-clf@ietf.org, rfc-editor@rfc-editor.org
Subject: [sip-clf] RFC 6872 on The Common Log Format (CLF) for the Session Initiation Protocol (SIP): Framework and Information Model
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Feb 2013 22:06:47 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 6872

        Title:      The Common Log Format (CLF) 
                    for the Session Initiation Protocol (SIP): 
                    Framework and Information Model 
        Author:     V. Gurbani, Ed.,
                    E. Burger, Ed.,
                    T. Anjali, 
                    H. Abdelnur,
                    O. Festor
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2013
        Mailbox:    vkg@bell-labs.com, 
        Pages:      39
        Characters: 72134
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sipclf-problem-statement-13.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6872.txt

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 troubleshooting 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.  This document describes a
framework, including requirements and analysis of existing
approaches, and specifies an information model for development of a
SIP common log file format that can be used uniformly by user agents,
proxies, registrars, and redirect servers as well as back-to-back
user agents.

This document is a product of the SIP Common Log Format Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC