RFC 6872: The Common Log Format (CLF) for the Session Initiation Protocol (SIP): Framework and Information Model
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC6872
- Published
- February 2013
- Authors
- V. Gurbani; E. Burger; T. Anjali; H. Abdelnur; O. Festor
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 39
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7937Content Distribution Network Interconnection (CDNI) Logging InterfaceCurrent
August 2016
- RFC 8123Requirements for Marking SIP Messages to be LoggedCurrent
March 2017
- RFC 8497Marking SIP Messages to Be LoggedCurrent
November 2018
- RFC 6873Format for the Session Initiation Protocol (SIP) Common Log Format (CLF)Updated
February 2013
- RFC 6848Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO)Current
January 2013
- RFC 6910Completion of Calls for the Session Initiation Protocol (SIP)Current
April 2013
- RFC 6914SIMPLE Made Simple: An Overview of the IETF Specifications for Instant Messaging and Presence Using the Session Initiation Protocol (SIP)Current
April 2013
- RFC 6915Flow Identity Extension for HTTP-Enabled Location Delivery (HELD)Current
April 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?