Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Authors:

V. Gurbani, Ed.
E. Burger, Ed.
T. Anjali
H. Abdelnur
O. Festor

Stream:

IETF

Source:

sipclf (rai)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC6872

Discuss this RFC: Send questions or comments to the mailing listsip-clf@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 6872

Abstract

Well-known web servers such as Apache and web proxies like Squidsupport event logging using a common log format. The logs producedusing these de facto standard formats are invaluable to systemadministrators for troubleshooting a server and tool writers to crafttools that mine the log files and produce reports and trends.Furthermore, these log files can also be used to train anomalydetection systems and feed events into a security event managementsystem. The Session Initiation Protocol (SIP) does not have a commonlog format, and, as a result, each server supports a distinct logformat that makes it unnecessarily complex to produce tools to dotrend analysis and security detection. This document describes aframework, including requirements and analysis of existingapproaches, and specifies an information model for development of aSIP common log file format that can be used uniformly by user agents,proxies, registrars, and redirect servers as well as back-to-backuser agents.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.