[sip-clf] RFC 6873 on Format for the Session Initiation Protocol (SIP) Common Log Format (CLF)

rfc-editor@rfc-editor.org Thu, 14 February 2013 22:07 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 327B921F845A; Thu, 14 Feb 2013 14:07:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.041
X-Spam-Level:
X-Spam-Status: No, score=-102.041 tagged_above=-999 required=5 tests=[AWL=-0.041, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UCWmpcMFkB99; Thu, 14 Feb 2013 14:06:59 -0800 (PST)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id BD04F21F8910; Thu, 14 Feb 2013 14:06:59 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 977C7B1E00D; Thu, 14 Feb 2013 14:06:30 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130214220630.977C7B1E00D@rfc-editor.org>
Date: Thu, 14 Feb 2013 14:06:30 -0800 (PST)
Cc: sip-clf@ietf.org, rfc-editor@rfc-editor.org
Subject: [sip-clf] RFC 6873 on Format for the Session Initiation Protocol (SIP) Common Log Format (CLF)
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:07:00 -0000

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

        
        RFC 6873

        Title:      Format for the Session Initiation 
                    Protocol (SIP) Common Log Format (CLF) 
        Author:     G. Salgueiro,
                    V. Gurbani,
                    A. B. Roach
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2013
        Mailbox:    gsalguei@cisco.com, 
                    vkg@bell-labs.com, 
                    adam@nostrum.com
        Pages:      28
        Characters: 63449
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sipclf-format-11.txt

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

The SIPCLF working group has defined a Common Log Format (CLF)
framework for Session Initiation Protocol (SIP) servers.  This CLF
mimics the successful event logging format found in well-known web
servers like Apache and web proxies like Squid.  This document
proposes an indexed text encoding format for the SIP CLF that retains
the key advantages of a text-based format while significantly
increasing processing performance over a purely text-based
implementation.  This file format adheres to the SIP CLF information
model and provides an effective encoding scheme for all mandatory and
optional fields that appear in a SIP CLF record.  

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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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