
From fluffy@cisco.com  Wed Jul  1 12:31:32 2009
Return-Path: <fluffy@cisco.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 73B773A6A66 for <sip-clf@core3.amsl.com>; Wed,  1 Jul 2009 12:31:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.567
X-Spam-Level: 
X-Spam-Status: No, score=-106.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YeJyutarIdVv for <sip-clf@core3.amsl.com>; Wed,  1 Jul 2009 12:31:31 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 6A8243A69BB for <sip-clf@ietf.org>; Wed,  1 Jul 2009 12:31:31 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,327,1243814400"; d="scan'208";a="182251287"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-2.cisco.com with ESMTP; 01 Jul 2009 19:31:53 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n61JVrlk025239;  Wed, 1 Jul 2009 12:31:53 -0700
Received: from [192.168.1.75] (sjc-vpn3-143.cisco.com [10.21.64.143]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id n61JVrjA009722; Wed, 1 Jul 2009 19:31:53 GMT
Message-Id: <0963F0FF-D78E-45FC-B0C0-21AF8E7427F9@cisco.com>
From: Cullen Jennings <fluffy@cisco.com>
To: sip-clf@ietf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 1 Jul 2009 12:31:52 -0700
X-Mailer: Apple Mail (2.935.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=867; t=1246476713; x=1247340713; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20<fluffy@cisco.com> |Subject:=20Chair=20Candidates=20for=20a=20CLF=20WG? |Sender:=20; bh=m+rcKJsUvnJCQFJbNTmL+En2/qnhqf/G1yoV37GSIRU=; b=cTmxPZNewKTgGW2KE3H8wphktZoKm+MYvDyjdL8R4yhEUFEVOtB1ITHpJu VB7c8Nq2yqDKaQBXooDse2E3D0gxpdlbu+PqEUYwoJeDiWSqdJ08yjLwIMvp hKV9R/9me+;
Authentication-Results: sj-dkim-4; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Subject: [sip-clf] Chair Candidates for a CLF WG?
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 01 Jul 2009 19:31:32 -0000

Hi All,

As part of getting a WG set up for this, Robert and I are soliciting  
input on who would be a good chair. If you are willing to chair, or if  
you have input on who would be a good victim^H^H^H^H^H volunteer,  
please send Robert and I some private email.

In an ideal world we would find two chairs, with at least one of  
person who was not one of the usual RAI chairs and expanded our group  
of experienced chairs, and at least one person who had a reasonable  
understanding of IETF process. We understand travel budget are an  
issue these days and we would not expect folks to be able to make it  
to every IETF meeting but they need to be able to make it to some of  
them.

Thanks, Cullen <RAI AD>

PS - We are not keen on a chair who is also the author of the primary  
specification document. That always complicates things.




From rjsparks@nostrum.com  Fri Jul 17 14:13:34 2009
Return-Path: <rjsparks@nostrum.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 438443A68EC for <sip-clf@core3.amsl.com>; Fri, 17 Jul 2009 14:13:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zRbGNmCF2WyQ for <sip-clf@core3.amsl.com>; Fri, 17 Jul 2009 14:13:30 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id B56193A6AE5 for <sip-clf@ietf.org>; Fri, 17 Jul 2009 14:13:26 -0700 (PDT)
Received: from dn3-232.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id n6HLDVaE097908 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <sip-clf@ietf.org>; Fri, 17 Jul 2009 16:13:58 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-Id: <D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
To: sip-clf@ietf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 17 Jul 2009 16:13:58 -0500
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com>
X-Mailer: Apple Mail (2.935.3)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Subject: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 17 Jul 2009 21:13:34 -0000

All -

We are working on forming a CLF working group based on DISPATCH's  
decision.

Below is a proposed charter for this working group. Please review and  
comment
on this list. Depending on the feedback we receive, we will target  
forming this
group shortly after the Stockholm meeting.

We'll also be discussing this in Thursday's opsarea meeting.

Thanks,

RjS


> The SIP Common Log File (CLF) working group is chartered to define
> a standard logging format for systems processing SIP messages.
>
> 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 to produce reports and trends
> and to search for a certain SIP message or messages, a transaction
> or a related set of transactions.  Furthermore, these log records
> can also be used to train anomaly detection systems and feed events
> into a security event management system.
>
> The Session Initiation Protocol does not have a common log
> format. Diverse element provide distinct log formats making
> it complex to produce tools to analyze them.
>
> The CLF working group will produce a format suitable for logging
> from any SIP element. The format will anticipate the need to
> search, merge, and summarize the log records from diverse elements.
> The format will anticipate the need to correlate messages from
> multiple elements related to a given request (that may fork)
> or a given dialog. The format will take SIP's extensibility into
> consideration, providing a way to represent SIP message components
> that are defined in the future.  The format will anticipate being
> used both for off-line analysis and on-line real-time processing
> applications. The working group will consider the need for
> efficient processing in its design of this format.
>
> The working group is not pre-constrained to producing either a
> bit-field oriented or text-oriented format, and may choose to
> provide both. If the group chooses to specify both, it must be
> possible to mechanically translate between the formats without
> loss of information.
>
> Specifying the mechanics of exchanging, transporting, and storing
> SIP Common Log Format records is explicitly out of scope. Specifying
> a real-time transfer mechanism for heuristic analysis is explicitly
> out of scope.
>
> The group will generate:
>
> - A problem statement enunciating the motivation,
>  and use cases for a SIP Common Log Format. This analysis
>  will identify the required minimal information that must
>  appear in any record.
>
> - A specification of the SIP Common Log Format record.
>
> The group will consider providing one or more reference
> implementations for decoding a CLF record.
>
> Goals and Milestones
> ===========================
>
> Nov 09 - Problem statement, motivation, and use cases to IESG  
> (Informational)
> Feb 10 - SIP Common Log Format specification to IESG (PS)
>


From dromasca@avaya.com  Mon Jul 20 07:45:00 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF9523A6C34 for <sip-clf@core3.amsl.com>; Mon, 20 Jul 2009 07:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.367
X-Spam-Level: 
X-Spam-Status: No, score=-2.367 tagged_above=-999 required=5 tests=[AWL=0.232,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n6KwK5eXDbpn for <sip-clf@core3.amsl.com>; Mon, 20 Jul 2009 07:44:57 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id D3B863A6941 for <sip-clf@ietf.org>; Mon, 20 Jul 2009 07:44:56 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.43,234,1246852800"; d="scan'208";a="177421382"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 20 Jul 2009 10:44:56 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 20 Jul 2009 10:44:56 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 20 Jul 2009 16:44:29 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401892AF4@307622ANEX5.global.avaya.com>
In-Reply-To: <D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-clf] draft CLF charter
thread-index: AcoHI4kvZTPCiRUvRl6mSXW2RdOaGACI5ufg
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com> <D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Robert Sparks" <rjsparks@nostrum.com>, <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 20 Jul 2009 14:45:01 -0000

A few comments after the first reading of the charter.=20

- Is it Common Log File as it appears at the first instance, or Common
Log Format?=20
- What does 'efficient processing' mean? More clarity and details here
would be welcome (is it at client, at server, both? Is it efficiency on
storage, on transmission? etc.)
- Would it be useful to include (maybe as part of the problem statement
work, maybe as a separate item) a look at what is already available as
standards for logging events (e.g. syslog is discussing rechartering at
the same IETF meeting - can syslog format be used? pcap? Other? Are
there any initial proposals?)
- if the WG ends by doing both a bit-field oriented and a text-oriented
format will these end being separate deliverables?=20

Dan


> -----Original Message-----
> From: sip-clf-bounces@ietf.org=20
> [mailto:sip-clf-bounces@ietf.org] On Behalf Of Robert Sparks
> Sent: Saturday, July 18, 2009 12:14 AM
> To: sip-clf@ietf.org
> Subject: [sip-clf] draft CLF charter
>=20
> All -
>=20
> We are working on forming a CLF working group based on=20
> DISPATCH's decision.
>=20
> Below is a proposed charter for this working group. Please=20
> review and comment on this list. Depending on the feedback we=20
> receive, we will target forming this group shortly after the=20
> Stockholm meeting.
>=20
> We'll also be discussing this in Thursday's opsarea meeting.
>=20
> Thanks,
>=20
> RjS
>=20
>=20
> > The SIP Common Log File (CLF) working group is chartered to=20
> define a=20
> > standard logging format for systems processing SIP messages.
> >
> > Well-known web servers such as Apache and web proxies like Squid=20
> > support event logging using a common log format.  The logs produced=20
> > using these de-facto standard formats are invaluable to system=20
> > administrators for trouble-shooting a server and tool=20
> writers to craft=20
> > tools that mine the log files to produce reports and trends and to=20
> > search for a certain SIP message or messages, a transaction or a=20
> > related set of transactions.  Furthermore, these log=20
> records can also=20
> > be used to train anomaly detection systems and feed events into a=20
> > security event management system.
> >
> > The Session Initiation Protocol does not have a common log format.=20
> > Diverse element provide distinct log formats making it complex to=20
> > produce tools to analyze them.
> >
> > The CLF working group will produce a format suitable for=20
> logging from=20
> > any SIP element. The format will anticipate the need to=20
> search, merge,=20
> > and summarize the log records from diverse elements.
> > The format will anticipate the need to correlate messages from=20
> > multiple elements related to a given request (that may fork) or a=20
> > given dialog. The format will take SIP's extensibility into=20
> > consideration, providing a way to represent SIP message components=20
> > that are defined in the future.  The format will anticipate=20
> being used=20
> > both for off-line analysis and on-line real-time processing=20
> > applications. The working group will consider the need for=20
> efficient=20
> > processing in its design of this format.
> >
> > The working group is not pre-constrained to producing either a=20
> > bit-field oriented or text-oriented format, and may choose=20
> to provide=20
> > both. If the group chooses to specify both, it must be possible to=20
> > mechanically translate between the formats without loss of=20
> > information.
> >
> > Specifying the mechanics of exchanging, transporting, and=20
> storing SIP=20
> > Common Log Format records is explicitly out of scope. Specifying a=20
> > real-time transfer mechanism for heuristic analysis is=20
> explicitly out=20
> > of scope.
> >
> > The group will generate:
> >
> > - A problem statement enunciating the motivation,  and use=20
> cases for a=20
> > SIP Common Log Format. This analysis  will identify the required=20
> > minimal information that must  appear in any record.
> >
> > - A specification of the SIP Common Log Format record.
> >
> > The group will consider providing one or more reference=20
> > implementations for decoding a CLF record.
> >
> > Goals and Milestones
> > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
> >
> > Nov 09 - Problem statement, motivation, and use cases to IESG
> > (Informational)
> > Feb 10 - SIP Common Log Format specification to IESG (PS)
> >
>=20
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf
>=20

From drage@alcatel-lucent.com  Mon Jul 20 09:23:17 2009
Return-Path: <drage@alcatel-lucent.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5ECAC28C1C8 for <sip-clf@core3.amsl.com>; Mon, 20 Jul 2009 09:23:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.505
X-Spam-Level: 
X-Spam-Status: No, score=-3.505 tagged_above=-999 required=5 tests=[AWL=-1.255, BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ETnOk7nnhHmw for <sip-clf@core3.amsl.com>; Mon, 20 Jul 2009 09:23:10 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by core3.amsl.com (Postfix) with ESMTP id 2A29D28C1B7 for <sip-clf@ietf.org>; Mon, 20 Jul 2009 09:23:09 -0700 (PDT)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n6KGLLAR009823 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 20 Jul 2009 18:21:21 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.47]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Mon, 20 Jul 2009 18:21:21 +0200
From: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
To: Robert Sparks <rjsparks@nostrum.com>, "sip-clf@ietf.org" <sip-clf@ietf.org>
Date: Mon, 20 Jul 2009 18:21:24 +0200
Thread-Topic: [sip-clf] draft CLF charter
Thread-Index: AcoHI4m7QIuNfGrGS8+mXOMoVgHQ/ACMgiNQ
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE20707CECC@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com> <D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com>
In-Reply-To: <D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 20 Jul 2009 16:23:17 -0000

Just to note that previously the input from the other area director was to =
provide separate milestones for taking a draft to WGLC and publication requ=
est to IESG.

> We'll also be discussing this in Thursday's opsarea meeting.
>=20

Can you clarify what you mean by this? All discussion will henceforward be =
in opsarea or just seeking their input to continuing discussion on the disp=
atch mailing list.

regards

Keith

> -----Original Message-----
> From: sip-clf-bounces@ietf.org=20
> [mailto:sip-clf-bounces@ietf.org] On Behalf Of Robert Sparks
> Sent: Friday, July 17, 2009 10:14 PM
> To: sip-clf@ietf.org
> Subject: [sip-clf] draft CLF charter
>=20
> All -
>=20
> We are working on forming a CLF working group based on=20
> DISPATCH's decision.
>=20
> Below is a proposed charter for this working group. Please=20
> review and comment on this list. Depending on the feedback we=20
> receive, we will target forming this group shortly after the=20
> Stockholm meeting.
>=20
> We'll also be discussing this in Thursday's opsarea meeting.
>=20
> Thanks,
>=20
> RjS
>=20
>=20
> > The SIP Common Log File (CLF) working group is chartered to=20
> define a=20
> > standard logging format for systems processing SIP messages.
> >
> > Well-known web servers such as Apache and web proxies like Squid=20
> > support event logging using a common log format.  The logs produced=20
> > using these de-facto standard formats are invaluable to system=20
> > administrators for trouble-shooting a server and tool=20
> writers to craft=20
> > tools that mine the log files to produce reports and trends and to=20
> > search for a certain SIP message or messages, a transaction or a=20
> > related set of transactions.  Furthermore, these log=20
> records can also=20
> > be used to train anomaly detection systems and feed events into a=20
> > security event management system.
> >
> > The Session Initiation Protocol does not have a common log format.=20
> > Diverse element provide distinct log formats making it complex to=20
> > produce tools to analyze them.
> >
> > The CLF working group will produce a format suitable for=20
> logging from=20
> > any SIP element. The format will anticipate the need to=20
> search, merge,=20
> > and summarize the log records from diverse elements.
> > The format will anticipate the need to correlate messages from=20
> > multiple elements related to a given request (that may fork) or a=20
> > given dialog. The format will take SIP's extensibility into=20
> > consideration, providing a way to represent SIP message components=20
> > that are defined in the future.  The format will anticipate=20
> being used=20
> > both for off-line analysis and on-line real-time processing=20
> > applications. The working group will consider the need for=20
> efficient=20
> > processing in its design of this format.
> >
> > The working group is not pre-constrained to producing either a=20
> > bit-field oriented or text-oriented format, and may choose=20
> to provide=20
> > both. If the group chooses to specify both, it must be possible to=20
> > mechanically translate between the formats without loss of=20
> > information.
> >
> > Specifying the mechanics of exchanging, transporting, and=20
> storing SIP=20
> > Common Log Format records is explicitly out of scope. Specifying a=20
> > real-time transfer mechanism for heuristic analysis is=20
> explicitly out=20
> > of scope.
> >
> > The group will generate:
> >
> > - A problem statement enunciating the motivation,  and use=20
> cases for a=20
> > SIP Common Log Format. This analysis  will identify the required=20
> > minimal information that must  appear in any record.
> >
> > - A specification of the SIP Common Log Format record.
> >
> > The group will consider providing one or more reference=20
> > implementations for decoding a CLF record.
> >
> > Goals and Milestones
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
> >
> > Nov 09 - Problem statement, motivation, and use cases to IESG
> > (Informational)
> > Feb 10 - SIP Common Log Format specification to IESG (PS)
> >
>=20
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf
> =

From vkg@alcatel-lucent.com  Tue Jul 21 15:25:30 2009
Return-Path: <vkg@alcatel-lucent.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1486F3A67F9 for <sip-clf@core3.amsl.com>; Tue, 21 Jul 2009 15:25:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.469
X-Spam-Level: 
X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0qbtKLhEOROI for <sip-clf@core3.amsl.com>; Tue, 21 Jul 2009 15:25:29 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id E1A233A6AC0 for <sip-clf@ietf.org>; Tue, 21 Jul 2009 15:25:28 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id n6LMPNI7016703 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Jul 2009 17:25:23 -0500 (CDT)
Received: from [135.185.236.17] (il0015vkg1.ih.lucent.com [135.185.236.17]) by umail.lucent.com (8.13.8/TPES) with ESMTP id n6LMPN7a026015; Tue, 21 Jul 2009 17:25:23 -0500 (CDT)
Message-ID: <4A664053.7070603@alcatel-lucent.com>
Date: Tue, 21 Jul 2009 17:25:23 -0500
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com>	<D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com> <EDC652A26FB23C4EB6384A4584434A0401892AF4@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401892AF4@307622ANEX5.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 21 Jul 2009 22:25:30 -0000

Romascanu, Dan (Dan) wrote:
> A few comments after the first reading of the charter. 

Dan: Thanks for your feedback; more inline.

> - Is it Common Log File as it appears at the first instance, or Common
> Log Format? 

CLF expands to Common Log File, though colloquially you will
see references to "the CLF format", which simply means the
specific fields and their representation.

> - What does 'efficient processing' mean? More clarity and details here
> would be welcome (is it at client, at server, both? 

Efficiency is envisioned here to encompass both the server and the
client.  From the server's perspective, the generation of the
CLF should not cause an unnecessarily burden so as to slow the
normal processing done by the server.

 From the client perspective, the processing of the file should
not take undue time.  Some clients may consume data produced
in CLF format in real time while others may do so in "batch"
mode (i.e., find all the SIP messages corresponding to a
certain dialog.)  To do such batch mode processing, it is
advantageous if the CLF data is so structured as to aid in
skipping records that are not part of the search criteria.

> Is it efficiency on storage, on transmission? etc.)

More than storage costs or transmission overhead, efficiency
is measured in processing time at the clients and servers.

> - Would it be useful to include (maybe as part of the problem statement
> work, maybe as a separate item) a look at what is already available as
> standards for logging events (e.g. syslog is discussing rechartering at
> the same IETF meeting - can syslog format be used? pcap? Other? Are
> there any initial proposals?)

The members of the sip-clf list have experimented with ASCII-,
binary- as well as a hybrid-based approach to producing the CLF.
While pcap is good for capturing network traffic, requiring a SIP
entity to expressly produce CLF in pcap format will be burdening
it to spend CPU cycles in converting the SIP message from its
internal representation to the pcap format -- this may not
be sustainable in a high transaction volume SIP proxy, for
instance.  With respect to syslog, SIP CLF is more than an
event notification message -- it is essentially continuous
spooling of the messages that a SIP entity is processing.
It could well be that the SIP entity, if it detects something amiss
in a message, emits a syslog message; however, SIP CLF itself
was not viewed as an event notification mechanism.  Hence the
charter leaves out of scope mechanisms of exchanging, transporting,
and storing CLF format records.

> - if the WG ends by doing both a bit-field oriented and a text-oriented
> format will these end being separate deliverables? 

Possibly; or they could be different sections in the same
document.  The CLF fields will be the same, just the representation
of them will differ.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
Web:   http://ect.bell-labs.com/who/vkg/

From HKaplan@acmepacket.com  Tue Jul 21 16:47:21 2009
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D7F9E3A6AAF for <sip-clf@core3.amsl.com>; Tue, 21 Jul 2009 16:47:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3hazmnAbM1Hc for <sip-clf@core3.amsl.com>; Tue, 21 Jul 2009 16:47:21 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 0CD993A67FB for <sip-clf@ietf.org>; Tue, 21 Jul 2009 16:47:21 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Tue, 21 Jul 2009 19:47:20 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Tue, 21 Jul 2009 19:47:20 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>, "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Date: Tue, 21 Jul 2009 19:47:19 -0400
Thread-Topic: [sip-clf] draft CLF charter
Thread-Index: AcoKUins/30j881fSJOMwQybw4gOiAACXgjQ
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC3196D06C8EF@mail>
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com> <D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com> <EDC652A26FB23C4EB6384A4584434A0401892AF4@307622ANEX5.global.avaya.com> <4A664053.7070603@alcatel-lucent.com>
In-Reply-To: <4A664053.7070603@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "sip-clf@ietf.org" <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 21 Jul 2009 23:47:21 -0000

> -----Original Message-----
> From: sip-clf-bounces@ietf.org [mailto:sip-clf-bounces@ietf.org] On Behal=
f
> Of Vijay K. Gurbani
> Sent: Tuesday, July 21, 2009 6:25 PM
>=20
> While pcap is good for capturing network traffic, requiring a SIP
> entity to expressly produce CLF in pcap format will be burdening
> it to spend CPU cycles in converting the SIP message from its
> internal representation to the pcap format -- this may not
> be sustainable in a high transaction volume SIP proxy, for
> instance. =20

I disagree with that - or rather, it's not the format conversion from an in=
ternal representation to a PCAP format that would burn CPU.  I wrote an exa=
mple library for (and submitted a draft on) recording CLF in a PCAP format.=
  While the code was kludgy (because I'm not a programmer and I was trying =
to make it a generic library and thus internal-representation agnostic)... =
it could be written better.

But no matter what format we pick, there will be a "conversion" from an int=
ernal representation to a CLF format for most everyone, if not actually eve=
ryone.

-hadriel

From dromasca@avaya.com  Wed Jul 22 01:32:42 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 366343A6825 for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 01:32:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.618
X-Spam-Level: 
X-Spam-Status: No, score=-1.618 tagged_above=-999 required=5 tests=[AWL=-0.149, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id loDDbxx-xwUE for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 01:32:41 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 277DE3A67F1 for <sip-clf@ietf.org>; Wed, 22 Jul 2009 01:32:40 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.43,245,1246852800"; d="scan'208";a="177623866"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 22 Jul 2009 04:30:59 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 22 Jul 2009 04:30:59 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 22 Jul 2009 10:30:02 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401892EB9@307622ANEX5.global.avaya.com>
In-Reply-To: <4A664053.7070603@alcatel-lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-clf] draft CLF charter
thread-index: AcoKUicYrZMTdVWKTpWvPSVpRx++pgAU8ACw
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com>	<D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com> <EDC652A26FB23C4EB6384A4584434A0401892AF4@307622ANEX5.global.avaya.com> <4A664053.7070603@alcatel-lucent.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 22 Jul 2009 08:32:42 -0000

Thanks for the answers. Most clarifications are fine with me, a couple
of observations in line.=20

Dan

=20

> -----Original Message-----
> From: Vijay K. Gurbani [mailto:vkg@alcatel-lucent.com]=20
> Sent: Wednesday, July 22, 2009 1:25 AM
> To: Romascanu, Dan (Dan)
> Cc: Robert Sparks; sip-clf@ietf.org
> Subject: Re: [sip-clf] draft CLF charter
>=20
> Romascanu, Dan (Dan) wrote:

...

>=20
> > Is it efficiency on storage, on transmission? etc.)
>=20
> More than storage costs or transmission overhead, efficiency=20
> is measured in processing time at the clients and servers.

Some clarification in the text of the charter would be welcome.=20

...


>=20
> > - if the WG ends by doing both a bit-field oriented and a=20
> > text-oriented format will these end being separate deliverables?
>=20
> Possibly; or they could be different sections in the same=20
> document.  The CLF fields will be the same, just the=20
> representation of them will differ.
>=20

So, basically we are talking about fields definition (one) and mapping
of the fields to different formats (one or more). Again, clarifying this
in text may help.=20

...

Dan

From dromasca@avaya.com  Wed Jul 22 06:43:02 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1745F3A6768 for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 06:43:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.164
X-Spam-Level: 
X-Spam-Status: No, score=-2.164 tagged_above=-999 required=5 tests=[AWL=0.435,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oA-QU3XgMTnr for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 06:43:00 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id E28C23A68E1 for <sip-clf@ietf.org>; Wed, 22 Jul 2009 06:42:59 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.43,247,1246852800"; d="scan'208";a="151883702"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 22 Jul 2009 09:38:18 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 22 Jul 2009 09:38:17 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 22 Jul 2009 15:38:16 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040189300C@307622ANEX5.global.avaya.com>
In-Reply-To: <4A6715CA.4000709@lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-clf] draft CLF charter
thread-index: AcoK0WNUI4ePL3TgRiK7mZ2pF/N2tQAADwsw
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com>	<D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com> <EDC652A26FB23C4EB6384A4584434A0401892AF4@307622ANEX5.global.avaya.com> <4A664053.7070603@alcatel-lucent.com> <EDC652A26FB23C4EB6384A4584434A0401892EB9@307622ANEX5.global.avaya.com> <4A6715CA.4000709@lucent.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 22 Jul 2009 13:43:02 -0000

All these look good.=20

Thanks,

Dan
=20

> -----Original Message-----
> From: Vijay K. Gurbani [mailto:vkg@alcatel-lucent.com]=20
> Sent: Wednesday, July 22, 2009 4:36 PM
> To: Romascanu, Dan (Dan)
> Cc: Robert Sparks; sip-clf@ietf.org
> Subject: Re: [sip-clf] draft CLF charter
>=20
> Romascanu, Dan (Dan) wrote:
> > Thanks for the answers. Most clarifications are fine with=20
> me, a couple=20
> > of observations in line.
>=20
> Dan: Thank you.  I am suggesting some changes to the charter=20
> based on your comments.  Could the sip-clf list participants=20
> and the AD please review and comment.
>=20
> dromasca> Is it efficiency on storage, on transmission? etc.)
> vkg> More than storage costs or transmission overhead, efficiency is=20
> vkg> measured in processing time at the clients and servers.
> dromasca> Some clarification in the text of the charter would=20
> be welcome.
>=20
> OLD:
> The format will anticipate being used both for off-line=20
> analysis and on-line real-time processing applications. The=20
> working group will consider the need for efficient processing=20
> in its design of this format.
>=20
> NEW:
> The format will anticipate being used both for off-line=20
> analysis and on-line real-time processing applications. The=20
> working group will consider the need for efficient processing=20
> in its design of this format, where efficiency is measured in=20
> processing time of the CLF at the clients and servers (i.e.,=20
> the generation of the CLF should not cause an unnecessarily=20
> burden so as to slow the normal processing done by a server,=20
> and the processing of the file should not take undue time by=20
> a client.)
>=20
> dromasca> - if the WG ends by doing both a bit-field oriented and a=20
> dromasca> text-oriented format will these end being separate=20
> deliverables?
> vkg> Possibly; or they could be different sections in the=20
> same document. =20
> vkg> The CLF fields will be the same, just the representation of them=20
> vkg> will differ.
> dromasca> So, basically we are talking about fields=20
> definition (one) and=20
> dromasca> mapping of the fields to different formats (one or more).=20
> dromasca> Again, clarifying this in text may help.
>=20
> OLD:
> The working group is not pre-constrained to producing either=20
> a bit-field oriented or text-oriented format, and may choose=20
> to provide both.  If the group chooses to specify both, it=20
> must be possible to mechanically translate between the=20
> formats without loss of information.
>=20
> NEW:
> The working group is not pre-constrained to producing either=20
> a bit-field oriented or text-oriented format, and may choose=20
> to provide both.  The nature of the CLF information contained=20
> in a bit-field or text-oriented format will be the same, it=20
> is the representation that will differ.  If the group chooses=20
> to specify both, it must be possible to mechanically=20
> translate between the formats without loss of information.
>=20
> Thanks,
>=20
> - vijay
> --
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960=20
> Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
> Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
> Web:   http://ect.bell-labs.com/who/vkg/
>=20

From rjsparks@nostrum.com  Wed Jul 22 06:49:58 2009
Return-Path: <rjsparks@nostrum.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 800C93A6C15 for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 06:49:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MiaTKSjJo4i6 for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 06:49:57 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 6AE2C3A6BDF for <sip-clf@ietf.org>; Wed, 22 Jul 2009 06:49:57 -0700 (PDT)
Received: from dn3-232.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id n6MDnrx3051611 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 22 Jul 2009 08:49:53 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-Id: <CB8F8D6E-5908-446A-84B1-B4FF84010F06@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
In-Reply-To: <4A664053.7070603@alcatel-lucent.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 22 Jul 2009 08:49:52 -0500
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com>	<D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com> <EDC652A26FB23C4EB6384A4584434A0401892AF4@307622ANEX5.global.avaya.com> <4A664053.7070603@alcatel-lucent.com>
X-Mailer: Apple Mail (2.935.3)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 22 Jul 2009 13:49:58 -0000

Just to make sure we are all on the same page:

On Jul 21, 2009, at 5:25 PM, Vijay K. Gurbani wrote:

> Romascanu, Dan (Dan) wrote:
>> A few comments after the first reading of the charter.
>
> Dan: Thanks for your feedback; more inline.
>
>> - Is it Common Log File as it appears at the first instance, or  
>> Common
>> Log Format?
>
> CLF expands to Common Log File, though colloquially you will
> see references to "the CLF format", which simply means the
> specific fields and their representation.

This is something we need to state more clearly.

Are we defining a file are we defining a format that might go in a file?

I think the proposals I've read so far are trying to do the second.
Does anyone disagree?

I was planning to  change the word File Dan is pointing  to in the
proposed charter to Format.

RjS

From vkg@alcatel-lucent.com  Wed Jul 22 06:56:25 2009
Return-Path: <vkg@alcatel-lucent.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 19DD728C0F1 for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 06:56:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.034
X-Spam-Level: 
X-Spam-Status: No, score=-2.034 tagged_above=-999 required=5 tests=[AWL=0.565,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qtupcUnMM5WR for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 06:56:24 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id E35F628C0EA for <sip-clf@ietf.org>; Wed, 22 Jul 2009 06:56:23 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id n6MDaBKN023819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Jul 2009 08:36:11 -0500 (CDT)
Received: from [135.185.236.17] (il0015vkg1.ih.lucent.com [135.185.236.17]) by umail.lucent.com (8.13.8/TPES) with ESMTP id n6MDaAjf001423; Wed, 22 Jul 2009 08:36:10 -0500 (CDT)
Message-ID: <4A6715CA.4000709@lucent.com>
Date: Wed, 22 Jul 2009 08:36:10 -0500
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com>	<D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com> <EDC652A26FB23C4EB6384A4584434A0401892AF4@307622ANEX5.global.avaya.com> <4A664053.7070603@alcatel-lucent.com> <EDC652A26FB23C4EB6384A4584434A0401892EB9@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401892EB9@307622ANEX5.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 22 Jul 2009 13:56:25 -0000

Romascanu, Dan (Dan) wrote:
> Thanks for the answers. Most clarifications are fine with me, a
> couple of observations in line.

Dan: Thank you.  I am suggesting some changes to the charter based
on your comments.  Could the sip-clf list participants and
the AD please review and comment.

dromasca> Is it efficiency on storage, on transmission? etc.)
vkg> More than storage costs or transmission overhead, efficiency
vkg> is measured in processing time at the clients and servers.
dromasca> Some clarification in the text of the charter would be welcome.

OLD:
The format will anticipate being used both for off-line
analysis and on-line real-time processing applications. The
working group will consider the need for efficient processing
in its design of this format.

NEW:
The format will anticipate being used both for off-line
analysis and on-line real-time processing applications. The
working group will consider the need for efficient processing
in its design of this format, where efficiency is measured
in processing time of the CLF at the clients and servers (i.e.,
the generation of the CLF should not cause an unnecessarily
burden so as to slow the normal processing done by a server,
and the processing of the file should not take undue time by
a client.)

dromasca> - if the WG ends by doing both a bit-field oriented and a
dromasca> text-oriented format will these end being separate deliverables?
vkg> Possibly; or they could be different sections in the same
vkg> document.  The CLF fields will be the same, just the
vkg> representation of them will differ.
dromasca> So, basically we are talking about fields definition (one)
dromasca> and mapping of the fields to different formats (one
dromasca> or more). Again, clarifying this in text may help.

OLD:
The working group is not pre-constrained to producing either a
bit-field oriented or text-oriented format, and may choose to
provide both.  If the group chooses to specify both, it must be
possible to mechanically translate between the formats without
loss of information.

NEW:
The working group is not pre-constrained to producing either a
bit-field oriented or text-oriented format, and may choose to
provide both.  The nature of the CLF information contained in
a bit-field or text-oriented format will be the same, it is
the representation that will differ.  If the group chooses to
specify both, it must be possible to mechanically translate
between the formats without loss of information.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
Web:   http://ect.bell-labs.com/who/vkg/

From vkg@alcatel-lucent.com  Wed Jul 22 08:13:05 2009
Return-Path: <vkg@alcatel-lucent.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 462FE3A6882 for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 08:13:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.317
X-Spam-Level: 
X-Spam-Status: No, score=-2.317 tagged_above=-999 required=5 tests=[AWL=0.283,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UuCfXNZBT68y for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 08:13:04 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 0AFC03A68B2 for <sip-clf@ietf.org>; Wed, 22 Jul 2009 08:13:03 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id n6MDx7qS010772 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Jul 2009 08:59:07 -0500 (CDT)
Received: from [135.185.236.17] (il0015vkg1.ih.lucent.com [135.185.236.17]) by umail.lucent.com (8.13.8/TPES) with ESMTP id n6MDx6hh021451; Wed, 22 Jul 2009 08:59:06 -0500 (CDT)
Message-ID: <4A671B2A.6030800@alcatel-lucent.com>
Date: Wed, 22 Jul 2009 08:59:06 -0500
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com>	<D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com> <EDC652A26FB23C4EB6384A4584434A0401892AF4@307622ANEX5.global.avaya.com> <4A664053.7070603@alcatel-lucent.com> <CB8F8D6E-5908-446A-84B1-B4FF84010F06@nostrum.com>
In-Reply-To: <CB8F8D6E-5908-446A-84B1-B4FF84010F06@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 22 Jul 2009 15:13:05 -0000

Robert Sparks wrote:
> Just to make sure we are all on the same page:
> 
> On Jul 21, 2009, at 5:25 PM, Vijay K. Gurbani wrote:
> 
>> Romascanu, Dan (Dan) wrote:
>>> A few comments after the first reading of the charter.
>>
>> Dan: Thanks for your feedback; more inline.
>>
>>> - Is it Common Log File as it appears at the first instance, or Common
>>> Log Format?
>>
>> CLF expands to Common Log File, though colloquially you will
>> see references to "the CLF format", which simply means the
>> specific fields and their representation.
> 
> This is something we need to state more clearly.
> 
> Are we defining a file are we defining a format that might go in a file?

The latter; my apologies since I misrepresented this in my earlier
response.  Our model and inspiration of this work has been
HTTP CLF, which also expands to "Common Log Format".

> I think the proposals I've read so far are trying to do the second.
> Does anyone disagree?
> 
> I was planning to  change the word File Dan is pointing  to in the
> proposed charter to Format.

Sounds good.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
Web:   http://ect.bell-labs.com/who/vkg/

From spencer@wonderhamster.org  Wed Jul 22 08:25:28 2009
Return-Path: <spencer@wonderhamster.org>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E7913A6821 for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 08:25:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.778
X-Spam-Level: 
X-Spam-Status: No, score=-1.778 tagged_above=-999 required=5 tests=[AWL=0.821,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ij9MZPynH59l for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 08:25:27 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 6CC303A68AE for <sip-clf@ietf.org>; Wed, 22 Jul 2009 08:25:16 -0700 (PDT)
Received: from S73602b (w173.z064002096.dfw-tx.dsl.cnc.net [64.2.96.173]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MKp8S-1MTdNZ1urD-00015G; Wed, 22 Jul 2009 11:05:16 -0400
Message-ID: <F3298CA2E6E14FB3BA1B5234ACF402FC@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "SIP-CLF Mailing List" <sip-clf@ietf.org>
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com>	<D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com><EDC652A26FB23C4EB6384A4584434A0401892AF4@307622ANEX5.global.avaya.com><4A664053.7070603@alcatel-lucent.com> <CB8F8D6E-5908-446A-84B1-B4FF84010F06@nostrum.com>
Date: Wed, 22 Jul 2009 10:05:10 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX19ZLycZH4AULBnEacbJTh4DGwzUxLaXFGr4Z+e a1yGFbIfjEYKX6FKeOaYUmhkL/NWEy2cGCuOFp5rk5kOcNgndO JO4LRQ0UczQsoO/pm6346V47aRz18IumTIlsve/J1U=
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 22 Jul 2009 15:25:28 -0000

Just to stay on the same page :D

I had a short chat with Dave Harrington Monday, and he asked "why not 
IPFIX?" - has anyone looked at IPFIX yet?

I know Glen Zorn's question in February was "why not SYSLOG?" - the answer 
then, from Eric Burger, was (paraphrasing) "SYSLOG's the envelope, CLF might 
use SYSLOG but needs to define what goes in the envelope".

The answer may be the same for IPFIX, and we'll probably need to figure this 
out, but if anyone has already looked at this, that would be great to know.

Thanks,

Spencer


> Just to make sure we are all on the same page:
>
> On Jul 21, 2009, at 5:25 PM, Vijay K. Gurbani wrote:
>
>> Romascanu, Dan (Dan) wrote:
>>> A few comments after the first reading of the charter.
>>
>> Dan: Thanks for your feedback; more inline.
>>
>>> - Is it Common Log File as it appears at the first instance, or  Common
>>> Log Format?
>>
>> CLF expands to Common Log File, though colloquially you will
>> see references to "the CLF format", which simply means the
>> specific fields and their representation.
>
> This is something we need to state more clearly.
>
> Are we defining a file are we defining a format that might go in a file?
>
> I think the proposals I've read so far are trying to do the second.
> Does anyone disagree?
>
> I was planning to  change the word File Dan is pointing  to in the
> proposed charter to Format.
>
> RjS
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf 


From dromasca@avaya.com  Wed Jul 22 08:47:45 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C64BC3A6949 for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 08:47:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.188
X-Spam-Level: 
X-Spam-Status: No, score=-2.188 tagged_above=-999 required=5 tests=[AWL=0.411,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RQOozyrvAcYV for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 08:47:45 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id D54A23A6929 for <sip-clf@ietf.org>; Wed, 22 Jul 2009 08:47:44 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.43,247,1246852800"; d="scan'208";a="177670129"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 22 Jul 2009 11:45:44 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 22 Jul 2009 11:45:43 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 22 Jul 2009 17:45:24 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401893076@307622ANEX5.global.avaya.com>
In-Reply-To: <F3298CA2E6E14FB3BA1B5234ACF402FC@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-clf] draft CLF charter
thread-index: AcoK4KfZzNfNxEVnT/2kAOLMye5ViwAAf2Ng
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com>	<D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com><EDC652A26FB23C4EB6384A4584434A0401892AF4@307622ANEX5.global.avaya.com><4A664053.7070603@alcatel-lucent.com><CB8F8D6E-5908-446A-84B1-B4FF84010F06@nostrum.com> <F3298CA2E6E14FB3BA1B5234ACF402FC@china.huawei.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Spencer Dawkins" <spencer@wonderhamster.org>, "SIP-CLF Mailing List" <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 22 Jul 2009 15:47:45 -0000

I need to have a more careful look, but the answer I think is No, the
argument is different. IPFIX defines information elements based on
packets inspection that characterize a 'flow' - in a SIP you cannot
differentiate packets that belong to different sessions only based on
on-wire information, so the definition of an IPFIX Information Element
(IE) may have too little or too much granularity for what we need.=20

But, again, I need to read the CLF requirements and cross-match these
carefully with the IPFIX capabilities to make sure that I am not passing
a too easy judgment.=20

Dan


> -----Original Message-----
> From: sip-clf-bounces@ietf.org=20
> [mailto:sip-clf-bounces@ietf.org] On Behalf Of Spencer Dawkins
> Sent: Wednesday, July 22, 2009 6:05 PM
> To: SIP-CLF Mailing List
> Subject: Re: [sip-clf] draft CLF charter
>=20
> Just to stay on the same page :D
>=20
> I had a short chat with Dave Harrington Monday, and he asked=20
> "why not IPFIX?" - has anyone looked at IPFIX yet?
>=20
> I know Glen Zorn's question in February was "why not SYSLOG?"=20
> - the answer then, from Eric Burger, was (paraphrasing)=20
> "SYSLOG's the envelope, CLF might use SYSLOG but needs to=20
> define what goes in the envelope".
>=20
> The answer may be the same for IPFIX, and we'll probably need=20
> to figure this out, but if anyone has already looked at this,=20
> that would be great to know.
>=20
> Thanks,
>=20
> Spencer
>=20
>=20
> > Just to make sure we are all on the same page:
> >
> > On Jul 21, 2009, at 5:25 PM, Vijay K. Gurbani wrote:
> >
> >> Romascanu, Dan (Dan) wrote:
> >>> A few comments after the first reading of the charter.
> >>
> >> Dan: Thanks for your feedback; more inline.
> >>
> >>> - Is it Common Log File as it appears at the first instance, or =20
> >>> Common Log Format?
> >>
> >> CLF expands to Common Log File, though colloquially you will see=20
> >> references to "the CLF format", which simply means the specific=20
> >> fields and their representation.
> >
> > This is something we need to state more clearly.
> >
> > Are we defining a file are we defining a format that might=20
> go in a file?
> >
> > I think the proposals I've read so far are trying to do the second.
> > Does anyone disagree?
> >
> > I was planning to  change the word File Dan is pointing  to in the=20
> > proposed charter to Format.
> >
> > RjS
> > _______________________________________________
> > sip-clf mailing list
> > sip-clf@ietf.org
> > https://www.ietf.org/mailman/listinfo/sip-clf
>=20
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf
>=20

From rjsparks@nostrum.com  Wed Jul 22 10:23:15 2009
Return-Path: <rjsparks@nostrum.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 53AB73A6820 for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 10:23:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4dI0N4BzxCWN for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 10:23:14 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id EF4133A67DA for <sip-clf@ietf.org>; Wed, 22 Jul 2009 10:23:13 -0700 (PDT)
Received: from dn3-232.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id n6MHNAed068478 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 22 Jul 2009 12:23:10 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-Id: <AA6EC7DD-8331-41B6-AFC8-866CF5C73088@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
To: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE20707CECC@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 22 Jul 2009 12:23:10 -0500
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com> <D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com> <EDC0A1AE77C57744B664A310A0B23AE20707CECC@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
X-Mailer: Apple Mail (2.935.3)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: "sip-clf@ietf.org" <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 22 Jul 2009 17:23:15 -0000

This is just getting input from the opsarea. Conversation will  
continue on sip-clf.

RjS

On Jul 20, 2009, at 11:21 AM, DRAGE, Keith (Keith) wrote:

> Just to note that previously the input from the other area director  
> was to provide separate milestones for taking a draft to WGLC and  
> publication request to IESG.
>
>> We'll also be discussing this in Thursday's opsarea meeting.
>>
>
> Can you clarify what you mean by this? All discussion will  
> henceforward be in opsarea or just seeking their input to continuing  
> discussion on the dispatch mailing list.
>
> regards
>
> Keith
>
>> -----Original Message-----
>> From: sip-clf-bounces@ietf.org
>> [mailto:sip-clf-bounces@ietf.org] On Behalf Of Robert Sparks
>> Sent: Friday, July 17, 2009 10:14 PM
>> To: sip-clf@ietf.org
>> Subject: [sip-clf] draft CLF charter
>>
>> All -
>>
>> We are working on forming a CLF working group based on
>> DISPATCH's decision.
>>
>> Below is a proposed charter for this working group. Please
>> review and comment on this list. Depending on the feedback we
>> receive, we will target forming this group shortly after the
>> Stockholm meeting.
>>
>> We'll also be discussing this in Thursday's opsarea meeting.
>>
>> Thanks,
>>
>> RjS
>>
>>
>>> The SIP Common Log File (CLF) working group is chartered to
>> define a
>>> standard logging format for systems processing SIP messages.
>>>
>>> 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 to produce reports and trends and to
>>> search for a certain SIP message or messages, a transaction or a
>>> related set of transactions.  Furthermore, these log
>> records can also
>>> be used to train anomaly detection systems and feed events into a
>>> security event management system.
>>>
>>> The Session Initiation Protocol does not have a common log format.
>>> Diverse element provide distinct log formats making it complex to
>>> produce tools to analyze them.
>>>
>>> The CLF working group will produce a format suitable for
>> logging from
>>> any SIP element. The format will anticipate the need to
>> search, merge,
>>> and summarize the log records from diverse elements.
>>> The format will anticipate the need to correlate messages from
>>> multiple elements related to a given request (that may fork) or a
>>> given dialog. The format will take SIP's extensibility into
>>> consideration, providing a way to represent SIP message components
>>> that are defined in the future.  The format will anticipate
>> being used
>>> both for off-line analysis and on-line real-time processing
>>> applications. The working group will consider the need for
>> efficient
>>> processing in its design of this format.
>>>
>>> The working group is not pre-constrained to producing either a
>>> bit-field oriented or text-oriented format, and may choose
>> to provide
>>> both. If the group chooses to specify both, it must be possible to
>>> mechanically translate between the formats without loss of
>>> information.
>>>
>>> Specifying the mechanics of exchanging, transporting, and
>> storing SIP
>>> Common Log Format records is explicitly out of scope. Specifying a
>>> real-time transfer mechanism for heuristic analysis is
>> explicitly out
>>> of scope.
>>>
>>> The group will generate:
>>>
>>> - A problem statement enunciating the motivation,  and use
>> cases for a
>>> SIP Common Log Format. This analysis  will identify the required
>>> minimal information that must  appear in any record.
>>>
>>> - A specification of the SIP Common Log Format record.
>>>
>>> The group will consider providing one or more reference
>>> implementations for decoding a CLF record.
>>>
>>> Goals and Milestones
>>> ===========================
>>>
>>> Nov 09 - Problem statement, motivation, and use cases to IESG
>>> (Informational)
>>> Feb 10 - SIP Common Log Format specification to IESG (PS)
>>>
>>
>> _______________________________________________
>> sip-clf mailing list
>> sip-clf@ietf.org
>> https://www.ietf.org/mailman/listinfo/sip-clf
>>


From theo@crazygreek.co.uk  Wed Jul 22 14:43:20 2009
Return-Path: <theo@crazygreek.co.uk>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0032B3A67AA for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 14:43:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.977
X-Spam-Level: 
X-Spam-Status: No, score=-5.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RcWl4wX-Gz77 for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 14:43:18 -0700 (PDT)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by core3.amsl.com (Postfix) with SMTP id 098673A6AC1 for <sip-clf@ietf.org>; Wed, 22 Jul 2009 14:43:16 -0700 (PDT)
Received: from source ([72.14.220.154]) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKSmeHmv/GVyNdZO0w02fhMM1mMLeJyjfq@postini.com; Wed, 22 Jul 2009 14:43:18 PDT
Received: by fg-out-1718.google.com with SMTP id l27so968863fgb.1 for <sip-clf@ietf.org>; Wed, 22 Jul 2009 14:41:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.86.83.17 with SMTP id g17mr1208796fgb.25.1248298906079; Wed,  22 Jul 2009 14:41:46 -0700 (PDT)
In-Reply-To: <F3298CA2E6E14FB3BA1B5234ACF402FC@china.huawei.com>
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com>  <D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com> <EDC652A26FB23C4EB6384A4584434A0401892AF4@307622ANEX5.global.avaya.com> <4A664053.7070603@alcatel-lucent.com> <CB8F8D6E-5908-446A-84B1-B4FF84010F06@nostrum.com>  <F3298CA2E6E14FB3BA1B5234ACF402FC@china.huawei.com>
From: Theo Zourzouvillys <theo@crazygreek.co.uk>
Date: Wed, 22 Jul 2009 22:41:26 +0100
Message-ID: <167dfb9b0907221441x3d154660tc6275623f1dc3e56@mail.gmail.com>
To: Spencer Dawkins <spencer@wonderhamster.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: SIP-CLF Mailing List <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 22 Jul 2009 21:43:20 -0000

On Wed, Jul 22, 2009 at 4:05 PM, Spencer
Dawkins<spencer@wonderhamster.org> wrote:
> I had a short chat with Dave Harrington Monday, and he asked "why not
> IPFIX?" - has anyone looked at IPFIX yet?

yes :-)

see bottom of:

http://www.ietf.org/mail-archive/web/sipping/current/msg17205.html

 ~ Theo

-- 
http://twitter.com/zourzouvillys
http://crazygreek.co.uk/

From HKaplan@acmepacket.com  Wed Jul 22 19:31:43 2009
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 00DDB3A6CA8 for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 19:31:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EsRaQg-SD1fs for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 19:31:42 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id ED74C3A6BCD for <sip-clf@ietf.org>; Wed, 22 Jul 2009 19:31:41 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Wed, 22 Jul 2009 22:30:32 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Wed, 22 Jul 2009 22:30:32 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, Spencer Dawkins <spencer@wonderhamster.org>, SIP-CLF Mailing List <sip-clf@ietf.org>
Date: Wed, 22 Jul 2009 22:30:30 -0400
Thread-Topic: [sip-clf] draft CLF charter
Thread-Index: AcoK4KfZzNfNxEVnT/2kAOLMye5ViwAAf2NgABZPkPA=
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC3196D182386@mail>
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com> <D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com><EDC652A26FB23C4EB6384A4584434A0401892AF4@307622ANEX5.global.avaya.com><4A664053.7070603@alcatel-lucent.com><CB8F8D6E-5908-446A-84B1-B4FF84010F06@nostrum.com> <F3298CA2E6E14FB3BA1B5234ACF402FC@china.huawei.com> <EDC652A26FB23C4EB6384A4584434A0401893076@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401893076@307622ANEX5.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 23 Jul 2009 02:31:43 -0000

Yeah when I first heard someone mention ipfix at the beginning - the first =
thing in my mind was "we're not doing samples for flow counters".  But then=
 I thought about it some more and think what they mean is the ipfix record =
format concept in particular, not ipfix the protocol/architecture/mechanism=
.  So for example one could define a "SIP-CLF" template set of fields which=
 record what we want.

If that's what people mean when they say "ipfix", I like that way too, beca=
use in my mind that's pretty close to the advantages of a Pcap file format.=
  Ipfix is a little hokey when dealing with variable-length fields, as I re=
call (it was really optimized for fixed-length fields like counters and IP =
Addresses), but probably less hokey than Pcap.  And it'll probably be small=
er record sizes which is a big deal.

-hadriel

> -----Original Message-----
> From: sip-clf-bounces@ietf.org [mailto:sip-clf-bounces@ietf.org] On Behal=
f
> Of Romascanu, Dan (Dan)
> Sent: Wednesday, July 22, 2009 11:45 AM
>=20
> I need to have a more careful look, but the answer I think is No, the
> argument is different. IPFIX defines information elements based on
> packets inspection that characterize a 'flow' - in a SIP you cannot
> differentiate packets that belong to different sessions only based on
> on-wire information, so the definition of an IPFIX Information Element
> (IE) may have too little or too much granularity for what we need.
>=20
> But, again, I need to read the CLF requirements and cross-match these
> carefully with the IPFIX capabilities to make sure that I am not passing
> a too easy judgment.
>=20
> Dan
>=20
>=20
> > -----Original Message-----
> > From: sip-clf-bounces@ietf.org
> > [mailto:sip-clf-bounces@ietf.org] On Behalf Of Spencer Dawkins
> > Sent: Wednesday, July 22, 2009 6:05 PM
> > To: SIP-CLF Mailing List
> > Subject: Re: [sip-clf] draft CLF charter
> >
> > Just to stay on the same page :D
> >
> > I had a short chat with Dave Harrington Monday, and he asked
> > "why not IPFIX?" - has anyone looked at IPFIX yet?
> >
> > I know Glen Zorn's question in February was "why not SYSLOG?"
> > - the answer then, from Eric Burger, was (paraphrasing)
> > "SYSLOG's the envelope, CLF might use SYSLOG but needs to
> > define what goes in the envelope".
> >
> > The answer may be the same for IPFIX, and we'll probably need
> > to figure this out, but if anyone has already looked at this,
> > that would be great to know.
> >
> > Thanks,
> >
> > Spencer
> >
> >
> > > Just to make sure we are all on the same page:
> > >
> > > On Jul 21, 2009, at 5:25 PM, Vijay K. Gurbani wrote:
> > >
> > >> Romascanu, Dan (Dan) wrote:
> > >>> A few comments after the first reading of the charter.
> > >>
> > >> Dan: Thanks for your feedback; more inline.
> > >>
> > >>> - Is it Common Log File as it appears at the first instance, or
> > >>> Common Log Format?
> > >>
> > >> CLF expands to Common Log File, though colloquially you will see
> > >> references to "the CLF format", which simply means the specific
> > >> fields and their representation.
> > >
> > > This is something we need to state more clearly.
> > >
> > > Are we defining a file are we defining a format that might
> > go in a file?
> > >
> > > I think the proposals I've read so far are trying to do the second.
> > > Does anyone disagree?
> > >
> > > I was planning to  change the word File Dan is pointing  to in the
> > > proposed charter to Format.
> > >
> > > RjS
> > > _______________________________________________
> > > sip-clf mailing list
> > > sip-clf@ietf.org
> > > https://www.ietf.org/mailman/listinfo/sip-clf
> >
> > _______________________________________________
> > sip-clf mailing list
> > sip-clf@ietf.org
> > https://www.ietf.org/mailman/listinfo/sip-clf
> >
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf

From dromasca@avaya.com  Thu Jul 23 07:52:06 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5C4C73A6A21 for <sip-clf@core3.amsl.com>; Thu, 23 Jul 2009 07:52:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.209
X-Spam-Level: 
X-Spam-Status: No, score=-2.209 tagged_above=-999 required=5 tests=[AWL=0.390,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I9W98MQXhrrU for <sip-clf@core3.amsl.com>; Thu, 23 Jul 2009 07:52:05 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 330E93A687C for <sip-clf@ietf.org>; Thu, 23 Jul 2009 07:52:05 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.43,255,1246852800"; d="scan'208";a="177784863"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 23 Jul 2009 10:50:24 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 23 Jul 2009 10:50:23 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 23 Jul 2009 16:49:59 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04018CF520@307622ANEX5.global.avaya.com>
In-Reply-To: <167dfb9b0907221441x3d154660tc6275623f1dc3e56@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-clf] draft CLF charter
thread-index: AcoLFXLL0mIgfwFdSYuYva4qeNiWwQAjxsWw
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com> <D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com><EDC652A26FB23C4EB6384A4584434A0401892AF4@307622ANEX5.global.avaya.com><4A664053.7070603@alcatel-lucent.com><CB8F8D6E-5908-446A-84B1-B4FF84010F06@nostrum.com> <F3298CA2E6E14FB3BA1B5234ACF402FC@china.huawei.com> <167dfb9b0907221441x3d154660tc6275623f1dc3e56@mail.gmail.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Theo Zourzouvillys" <theo@crazygreek.co.uk>, "Spencer Dawkins" <spencer@wonderhamster.org>
Cc: SIP-CLF Mailing List <sip-clf@ietf.org>, Nevil Brownlee <n.brownlee@auckland.ac.nz>, Juergen Quittek <Quittek@nw.neclab.eu>
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 23 Jul 2009 14:52:06 -0000

It may be a good idea to have somebody from the SIP-CLF crowd come to
the IPFIX meeting next week and make a five minutes presentation so that
IPFIX folks are aware about this.=20

I am copying the IPFIX chairs so that they are not completely taken by
surprise.=20

Dan


> -----Original Message-----
> From: sip-clf-bounces@ietf.org=20
> [mailto:sip-clf-bounces@ietf.org] On Behalf Of Theo Zourzouvillys
> Sent: Thursday, July 23, 2009 12:41 AM
> To: Spencer Dawkins
> Cc: SIP-CLF Mailing List
> Subject: Re: [sip-clf] draft CLF charter
>=20
> On Wed, Jul 22, 2009 at 4:05 PM, Spencer=20
> Dawkins<spencer@wonderhamster.org> wrote:
> > I had a short chat with Dave Harrington Monday, and he=20
> asked "why not=20
> > IPFIX?" - has anyone looked at IPFIX yet?
>=20
> yes :-)
>=20
> see bottom of:
>=20
> http://www.ietf.org/mail-archive/web/sipping/current/msg17205.html
>=20
>  ~ Theo
>=20
> --
> http://twitter.com/zourzouvillys
> http://crazygreek.co.uk/
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf
>=20

From vkg@alcatel-lucent.com  Thu Jul 23 08:05:26 2009
Return-Path: <vkg@alcatel-lucent.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2F7653A67EF for <sip-clf@core3.amsl.com>; Thu, 23 Jul 2009 08:05:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[AWL=0.063,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zmJD6fbIUrIh for <sip-clf@core3.amsl.com>; Thu, 23 Jul 2009 08:05:25 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 24B9E3A687C for <sip-clf@ietf.org>; Thu, 23 Jul 2009 08:05:25 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id n6NF4N7N007025 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Jul 2009 10:04:23 -0500 (CDT)
Received: from [135.185.236.17] (il0015vkg1.ih.lucent.com [135.185.236.17]) by umail.lucent.com (8.13.8/TPES) with ESMTP id n6NF4MZh008091; Thu, 23 Jul 2009 10:04:22 -0500 (CDT)
Message-ID: <4A687BF6.30308@alcatel-lucent.com>
Date: Thu, 23 Jul 2009 10:04:22 -0500
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com>	<D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com><EDC652A26FB23C4EB6384A4584434A0401892AF4@307622ANEX5.global.avaya.com><4A664053.7070603@alcatel-lucent.com><CB8F8D6E-5908-446A-84B1-B4FF84010F06@nostrum.com>	<F3298CA2E6E14FB3BA1B5234ACF402FC@china.huawei.com>	<167dfb9b0907221441x3d154660tc6275623f1dc3e56@mail.gmail.com> <EDC652A26FB23C4EB6384A4584434A04018CF520@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04018CF520@307622ANEX5.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Cc: Nevil Brownlee <n.brownlee@auckland.ac.nz>, SIP-CLF Mailing List <sip-clf@ietf.org>, Juergen Quittek <Quittek@nw.neclab.eu>
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 23 Jul 2009 15:05:26 -0000

Romascanu, Dan (Dan) wrote:
> It may be a good idea to have somebody from the SIP-CLF crowd come to
> the IPFIX meeting next week and make a five minutes presentation so that
> IPFIX folks are aware about this. 

I am not an expert at ipfix, so if Theo, Hadriel, or Spencer
would rather make a presentation, that is fine.  Otherwise, since
I am making a presentation on SIP CLF at the opsarea meeting
anyway, I can quickly present a digested version of that
slide deck at ipfix.  Regardless of who makes the presentation,
I can share the opsarea SIP CLF slide deck so we can beg,
borrow or steal slides from it for ipfix.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
Web:   http://ect.bell-labs.com/who/vkg/

From ietfdbh@comcast.net  Thu Jul 23 08:06:15 2009
Return-Path: <ietfdbh@comcast.net>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D0FFD3A67EF for <sip-clf@core3.amsl.com>; Thu, 23 Jul 2009 08:06:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.788
X-Spam-Level: 
X-Spam-Status: No, score=-1.788 tagged_above=-999 required=5 tests=[AWL=0.811,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kDSDe5E4IpXL for <sip-clf@core3.amsl.com>; Thu, 23 Jul 2009 08:06:14 -0700 (PDT)
Received: from QMTA04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [76.96.62.40]) by core3.amsl.com (Postfix) with ESMTP id 958A63A67D2 for <sip-clf@ietf.org>; Thu, 23 Jul 2009 08:06:14 -0700 (PDT)
Received: from OMTA13.westchester.pa.mail.comcast.net ([76.96.62.52]) by QMTA04.westchester.pa.mail.comcast.net with comcast id KPb81c00217dt5G54T5Xck; Thu, 23 Jul 2009 15:05:31 +0000
Received: from Harrington73653 ([24.147.240.21]) by OMTA13.westchester.pa.mail.comcast.net with comcast id KT5W1c00U0UQ6dC3ZT5Wwh; Thu, 23 Jul 2009 15:05:31 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Spencer Dawkins'" <spencer@wonderhamster.org>, "'SIP-CLF Mailing List'" <sip-clf@ietf.org>
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com>	<D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com><EDC652A26FB23C4EB6384A4584434A0401892AF4@307622ANEX5.global.avaya.com><4A664053.7070603@alcatel-lucent.com> <CB8F8D6E-5908-446A-84B1-B4FF84010F06@nostrum.com> <F3298CA2E6E14FB3BA1B5234ACF402FC@china.huawei.com>
Date: Thu, 23 Jul 2009 11:05:29 -0400
Message-ID: <1e6401ca0ba7$04c65070$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-reply-to: <F3298CA2E6E14FB3BA1B5234ACF402FC@china.huawei.com>
Thread-Index: AcoK3iAJaVF9tBZXTJOEO1JkFNObywAI1zIw
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 23 Jul 2009 15:06:15 -0000

Hi,

My concern is that I am not quite sure what we are trying to log, or
why.

If we are trying to log events that occur, then syslog might be a
reasonable choice for a logging protocol.
If we are trying to log the series of IP flows that make up a SIP
transaction, then ipfix might be a reasonable choice for a logging
protocol.
Somebody suggested using libpcap format, which would indicate that we
are trying to capture the packets that make up a transaction, for
later off-line analysis. If so, then libpcap might be a reasonable
logging protocol.
If we want to use an IETF standard protocol for packet captures, or if
we do not need to capture every packet, but just sample the flows
enough to be able to track the transaction, then PSAMP might be a
reasonable logging protocol.

If there are multiple purposes we are trying to meet, then it might be
best to address each purpose separately. There may be existing
standards that would meet the separate requirements very well, but no
standard that can meet the combination of purposes because the
requirements are so varied and potentially in conflict.

I am not promoting any particular solution. I would like to make sure
we discuss the targeted purposes and the subsequent requirements, so
we can best assess whether any of the existing IETF standards or
industry defacto standards meet those requirments.

I am a bit concerned that the charter seems to have a goal of defining
a data model, without knowing what the corresponding transport
protocol will be (if transporting the data is not a requirement, why
should the IETF standardize it?). The format that the data can take is
often inter-dependent with the protocol to be used to transport it.
For example, we have existing pairings - SMIv2 MIBs and SNMP, IEs and
IPFIX, XML and Netconf, SDEs and syslog. I am not sure it makes sense
to define a common log format without knowing which protocols will be
used when it is being transported.

It is possible we could define an information model rather than a data
model, but the plan to define a specific vendor-neutral format says we
are working on a data model. See RFC 3444 for a discussion of the
difference between information model and data model.

Part of my concern about the data and the transport protocol is driven
by my OPS-DIR role; part of it is driven by my SEC-DIR role. How
sensitive will this information be? Will this potentially be used as
evidence in legal proceedings? How much information will there be?

If it used for intrusion detection purposes or as evidence, does the
data-in-flight need to have integrity protection? Will this data be
used as a legal audit log? i.e., does the data-at-rest need to have
integrity protection?  SIP transactions might include information that
should be subject to privacy protection - protection against revealing
personal information, and that means confidentiality and integrity
must be preserved for data-in-flight as well as data-at-rest. 

The charter talks about meeting efficiency requirements for client and
server. What about resource requirements? How much information do we
expect might be generated? What happens if the buffer fills? Do we
discard old data? That could enable an attacker to force a buffer
overflow to hide their tracks. Large buffers of information could
cause problems in storage-or-CPU-constrained enviornments; IPFIX is
designed to off-load information quickly to reduce local resource
requirements. 

Without understanding how this data is expected to be used, we do not
know the requirements that must be met for operations, management, and
security while at rest and while in transit to support the use cases.

I think the applicability of the data to be collected really needs to
be nailed down much better than this charter proposal does. I think
the operations, management, and security requirements need to be
nailed down better. Then we can realistically talk about what the
field formats should be.

David Harrington
dbharrington@comcast.net
ietfdbh@comcast.net
dharrington@huawei.com


> -----Original Message-----
> From: Spencer Dawkins [mailto:spencer@wonderhamster.org] 
> Sent: Wednesday, July 22, 2009 11:05 AM
> To: SIP-CLF Mailing List
> Cc: David Harrington
> Subject: Re: [sip-clf] draft CLF charter
> 
> Just to stay on the same page :D
> 
> I had a short chat with Dave Harrington Monday, and he asked "why
not 
> IPFIX?" - has anyone looked at IPFIX yet?
> 
> I know Glen Zorn's question in February was "why not SYSLOG?" 
> - the answer 
> then, from Eric Burger, was (paraphrasing) "SYSLOG's the 
> envelope, CLF might 
> use SYSLOG but needs to define what goes in the envelope".
> 
> The answer may be the same for IPFIX, and we'll probably need 
> to figure this 
> out, but if anyone has already looked at this, that would be 
> great to know.
> 
> Thanks,
> 
> Spencer
> 
> 
> > Just to make sure we are all on the same page:
> >
> > On Jul 21, 2009, at 5:25 PM, Vijay K. Gurbani wrote:
> >
> >> Romascanu, Dan (Dan) wrote:
> >>> A few comments after the first reading of the charter.
> >>
> >> Dan: Thanks for your feedback; more inline.
> >>
> >>> - Is it Common Log File as it appears at the first 
> instance, or  Common
> >>> Log Format?
> >>
> >> CLF expands to Common Log File, though colloquially you will
> >> see references to "the CLF format", which simply means the
> >> specific fields and their representation.
> >
> > This is something we need to state more clearly.
> >
> > Are we defining a file are we defining a format that might 
> go in a file?
> >
> > I think the proposals I've read so far are trying to do the
second.
> > Does anyone disagree?
> >
> > I was planning to  change the word File Dan is pointing  to in the
> > proposed charter to Format.
> >
> > RjS
> > _______________________________________________
> > sip-clf mailing list
> > sip-clf@ietf.org
> > https://www.ietf.org/mailman/listinfo/sip-clf 
> 
> 


From dromasca@avaya.com  Thu Jul 23 08:10:12 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 690E33A6A14 for <sip-clf@core3.amsl.com>; Thu, 23 Jul 2009 08:10:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.219
X-Spam-Level: 
X-Spam-Status: No, score=-2.219 tagged_above=-999 required=5 tests=[AWL=0.380,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02b8r6QRfJER for <sip-clf@core3.amsl.com>; Thu, 23 Jul 2009 08:10:11 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 38AAB3A6955 for <sip-clf@ietf.org>; Thu, 23 Jul 2009 08:10:11 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.43,255,1246852800"; d="scan'208";a="177787881"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 23 Jul 2009 11:09:43 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 23 Jul 2009 11:09:42 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 23 Jul 2009 17:09:37 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04018CF52F@307622ANEX5.global.avaya.com>
In-Reply-To: <4A687BF6.30308@alcatel-lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-clf] draft CLF charter
thread-index: AcoLpuMqkgIFSKSsQTeLhL63r1we5QAAIS3g
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com>	<D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com><EDC652A26FB23C4EB6384A4584434A0401892AF4@307622ANEX5.global.avaya.com><4A664053.7070603@alcatel-lucent.com><CB8F8D6E-5908-446A-84B1-B4FF84010F06@nostrum.com>	<F3298CA2E6E14FB3BA1B5234ACF402FC@china.huawei.com>	<167dfb9b0907221441x3d154660tc6275623f1dc3e56@mail.gmail.com> <EDC652A26FB23C4EB6384A4584434A04018CF520@307622ANEX5.global.avaya.com> <4A687BF6.30308@alcatel-lucent.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Cc: Nevil Brownlee <n.brownlee@auckland.ac.nz>, SIP-CLF Mailing List <sip-clf@ietf.org>, Juergen Quittek <Quittek@nw.neclab.eu>
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 23 Jul 2009 15:10:12 -0000

No expertise of IPFIX is required at this stage, I guess, but rather
presenting the problem space and mentioning that IPFIX is considered as
a possible solution or part of the solution for SIP-CLF. Stealing slides
used in OPSAREA should be fine.=20

Dan
=20

> -----Original Message-----
> From: Vijay K. Gurbani [mailto:vkg@alcatel-lucent.com]=20
> Sent: Thursday, July 23, 2009 6:04 PM
> To: Romascanu, Dan (Dan)
> Cc: Theo Zourzouvillys; Spencer Dawkins; SIP-CLF Mailing=20
> List; Nevil Brownlee; Juergen Quittek
> Subject: Re: [sip-clf] draft CLF charter
>=20
> Romascanu, Dan (Dan) wrote:
> > It may be a good idea to have somebody from the SIP-CLF=20
> crowd come to=20
> > the IPFIX meeting next week and make a five minutes presentation so=20
> > that IPFIX folks are aware about this.
>=20
> I am not an expert at ipfix, so if Theo, Hadriel, or Spencer=20
> would rather make a presentation, that is fine.  Otherwise,=20
> since I am making a presentation on SIP CLF at the opsarea=20
> meeting anyway, I can quickly present a digested version of=20
> that slide deck at ipfix.  Regardless of who makes the=20
> presentation, I can share the opsarea SIP CLF slide deck so=20
> we can beg, borrow or steal slides from it for ipfix.
>=20
> Thanks,
>=20
> - vijay
> --
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960=20
> Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
> Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
> Web:   http://ect.bell-labs.com/who/vkg/
>=20

From Quittek@nw.neclab.eu  Fri Jul 24 00:29:51 2009
Return-Path: <Quittek@nw.neclab.eu>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C369A28C122 for <sip-clf@core3.amsl.com>; Fri, 24 Jul 2009 00:29:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 57EuskZ9kAqG for <sip-clf@core3.amsl.com>; Fri, 24 Jul 2009 00:29:50 -0700 (PDT)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by core3.amsl.com (Postfix) with ESMTP id 392C33A691E for <sip-clf@ietf.org>; Fri, 24 Jul 2009 00:29:50 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id C07442C0012C3; Fri, 24 Jul 2009 09:02:06 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp0.neclab.eu ([127.0.0.1]) by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Nm0HXmAea4Y; Fri, 24 Jul 2009 09:02:06 +0200 (CEST)
Received: from VENUS.office (mx1.office [192.168.24.3]) by smtp0.neclab.eu (Postfix) with ESMTP id 8258F2C0012C6; Fri, 24 Jul 2009 09:01:36 +0200 (CEST)
Received: from 10.1.2.178 ([10.1.2.178]) by VENUS.office ([192.168.24.102]) with Microsoft Exchange Server HTTP-DAV ; Fri, 24 Jul 2009 07:01:36 +0000
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3331270894_23373717"
Content-class: urn:content-classes:message
Date: Fri, 24 Jul 2009 09:01:33 +0200
Message-ID: <C68F28ED.6FC95%Quittek@nw.neclab.eu>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04018CF52F@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-clf] draft CLF charter
thread-index: AcoLpuMqkgIFSKSsQTeLhL63r1we5QAAIS3gACFK9n8=
From: "Juergen Quittek" <Quittek@nw.neclab.eu>
To: "Dan Romascanu" <dromasca@avaya.com>, "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
X-Mailman-Approved-At: Fri, 24 Jul 2009 05:46:07 -0700
Cc: Nevil Brownlee <n.brownlee@auckland.ac.nz>, SIP-CLF Mailing List <sip-clf@ietf.org>
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 24 Jul 2009 07:29:51 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3331270894_23373717
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

At the IPFIX session we will have a presentation of

    http://www.ietf.org/id/draft-huici-ipfix-sipfix-00.txt

It would be great to have both presentations together in the same session.
I would prefer to have both in IPFIX as a use case discussion.

As Dan said, at this point in time no background knowledge of the
IPFIX protocol would be required. But for both use case we could
receive good advice from the SIP experts on pros and cons of using IPFIX.

Thanks,

    Juergen


On 23.07.09 17:09  "Dan Romascanu" <dromasca@avaya.com> wrote:

> No expertise of IPFIX is required at this stage, I guess, but rather
> presenting the problem space and mentioning that IPFIX is considered as
> a possible solution or part of the solution for SIP-CLF. Stealing slides
> used in OPSAREA should be fine.
> 
> Dan
>  
> 
>> -----Original Message-----
>> From: Vijay K. Gurbani [mailto:vkg@alcatel-lucent.com]
>> Sent: Thursday, July 23, 2009 6:04 PM
>> To: Romascanu, Dan (Dan)
>> Cc: Theo Zourzouvillys; Spencer Dawkins; SIP-CLF Mailing
>> List; Nevil Brownlee; Juergen Quittek
>> Subject: Re: [sip-clf] draft CLF charter
>> 
>> Romascanu, Dan (Dan) wrote:
>>> It may be a good idea to have somebody from the SIP-CLF
>> crowd come to 
>>> the IPFIX meeting next week and make a five minutes presentation so
>>> that IPFIX folks are aware about this.
>> 
>> I am not an expert at ipfix, so if Theo, Hadriel, or Spencer
>> would rather make a presentation, that is fine.  Otherwise,
>> since I am making a presentation on SIP CLF at the opsarea
>> meeting anyway, I can quickly present a digested version of
>> that slide deck at ipfix.  Regardless of who makes the
>> presentation, I can share the opsarea SIP CLF slide deck so
>> we can beg, borrow or steal slides from it for ipfix.
>> 
>> Thanks,
>> 
>> - vijay
>> --
>> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960
>> Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
>> Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
>> Web:   http://ect.bell-labs.com/who/vkg/
>> 

--B_3331270894_23373717
Content-type: application/pkcs7-signature; name="smime.p7s"
Content-transfer-encoding: base64
Content-disposition: attachment;
	filename = "smime.p7s"

MIIQ6gYJKoZIhvcNAQcCoIIQ2zCCENcCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
DpIwggU2MIIEHqADAgECAgQNLisHMA0GCSqGSIb3DQEBBQUAMIGQMQswCQYDVQQGEwJERTEY
MBYGA1UEChMPTkVDIEV1cm9wZSBMdGQuMSAwHgYDVQQLExdORUMgTGFib3JhdG9yaWVzIEV1
cm9wZTESMBAGA1UEAxMJTkVDTEFCLUNBMTEwLwYJKoZIhvcNAQkBFiJ6ZXJ0aWZpemllcnVu
Z3NzdGVsbGVAbncubmVjbGFiLmV1MB4XDTA4MTEwMzA3NTEyMFoXDTExMTEwMzA3NTEyMFow
YzELMAkGA1UEBhMCREUxGDAWBgNVBAoTD05FQyBFdXJvcGUgTHRkLjEgMB4GA1UECxMXTkVD
IExhYm9yYXRvcmllcyBFdXJvcGUxGDAWBgNVBAMTD0p1ZXJnZW4gUXVpdHRlazCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBALYRfFB9x4h1YO6Mva6A5GCwKjwpgvzjiayFSmdD
HwV8u5gHp3sHIhyVtxgMSifEp9AV+ChxWHS3KQwuQ3XhDAP/xDN6QSk4Bmqa6rCZuTJygxYh
K39rNKd47ZfpuRC7j/Mbzwe9DTsbbBtpBgl5UKFc9c+zMbPlSwwlVbshWaUEoM6HoVFaDJdh
tJBIpsblz1oQVKXDjxjGkUNh9Ds3m7BGXkr5yaGsEuEa0J/QAFdO+auvBJlAzIM0UwBAmlcT
UHanS6Sdw5MkeutQqnmsUBtoenydq2Tmd9hfSfuTfiFuLmsvL3udH/jDAgQZ+PH6Mprqpyd3
wSycF/xZF5zz8X0CAwEAAaOCAcIwggG+MAkGA1UdEwQCMAAwCwYDVR0PBAQDAgXgMCkGA1Ud
JQQiMCAGCCsGAQUFBwMCBggrBgEFBQcDBAYKKwYBBAGCNxQCAjAdBgNVHQ4EFgQUWQo3BPrO
OLA4qljzDL1H8/6hIWEwHwYDVR0jBBgwFoAUTxyHeh3gL5n2vhWq0TWdDkrmujYwHwYDVR0R
BBgwFoEUUXVpdHRla0Budy5uZWNsYWIuZXUwfQYDVR0fBHYwdDA4oDagNIYyaHR0cDovL2Nk
cDEucGNhLmRmbi5kZS9uZWNsYWItY2EvcHViL2NybC9jYWNybC5jcmwwOKA2oDSGMmh0dHA6
Ly9jZHAyLnBjYS5kZm4uZGUvbmVjbGFiLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGYBggrBgEF
BQcBAQSBizCBiDBCBggrBgEFBQcwAoY2aHR0cDovL2NkcDEucGNhLmRmbi5kZS9uZWNsYWIt
Y2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MEIGCCsGAQUFBzAChjZodHRwOi8vY2RwMi5wY2Eu
ZGZuLmRlL25lY2xhYi1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQEFBQAD
ggEBAB37+54yupDBTDpEMuyf+ouCRrOE3fPAD2SEGBXCpKTYteFkFSWvHlgN8ecRSma0Dz/5
QShzacGMeJ8o+XzVXHe2gtZbjzSVvJn+/nAKtKgDCzw0ltt3xkdMMv2ax6IKGR7BcccsXx7B
R2PMaxdmHfCJseXiMzZO9QlWN2NZq2SSo3eGX/YDhHCWXDsoSu+uaKU/aRL2uZa92ptak2MA
uKI5tylKLFZ3FHf08F8J+5tTaMGem6DfaMZR/9GZ8aRFJrdA7tzUAGKpl+CzRxsJVHbAAU5L
hm5oTt6XYbh2G/cgdpeucsHJWBz9NQJrSrfWZYSwrv6AekMcvMi9X/CVZxEwggUvMIIEF6AD
AgECAgQNIQpHMA0GCSqGSIb3DQEBBQUAMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4t
VmVyZWluMRAwDgYDVQQLEwdERk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9i
YWwgLSBHMDEwHhcNMDgxMDI0MDg1MjA4WhcNMTkwNjMwMDAwMDAwWjCBkDELMAkGA1UEBhMC
REUxGDAWBgNVBAoTD05FQyBFdXJvcGUgTHRkLjEgMB4GA1UECxMXTkVDIExhYm9yYXRvcmll
cyBFdXJvcGUxEjAQBgNVBAMTCU5FQ0xBQi1DQTExMC8GCSqGSIb3DQEJARYiemVydGlmaXpp
ZXJ1bmdzc3RlbGxlQG53Lm5lY2xhYi5ldTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBAJ7yFbG1EaoyDnG5367mJEXHljmacrzNnm52KW3dXD/s3Vpuskex0jvaaTntWWRSGrAK
6kKXnTxBb3J3EhveBUbltzQ+K0XKtPJm6VE5qVpl33WJSaUHs27Dhwlke+DV6BBGyukz2SDB
aSa+nc0AwMZ0XO1DoDuiUNVeNmd/QT4SGzyFs+uLfLL2n8WzkZsbpSZ+xecwyw3EdQBBsp/i
/W+uOQBsGqaCjYe3EkBU6nW+pBsj0Iy1n7b9PXb5gQynrK3Mi2V7g1idSzHos0o1BMoHUrMz
Vw94Hj4CWlWmQ0t6Pdt1uYAMjwk0saQBY/Fyfv+wKeYycGIYyYCfJIRUeyUCAwEAAaOCAcQw
ggHAMBIGA1UdEwEB/wQIMAYBAf8CAQEwCwYDVR0PBAQDAgEGMB0GA1UdDgQWBBRPHId6HeAv
mfa+FarRNZ0OSua6NjAfBgNVHSMEGDAWgBRJt8bP6D0ff+pEexMp9/EKcD7eZDAtBgNVHREE
JjAkgSJ6ZXJ0aWZpemllcnVuZ3NzdGVsbGVAbncubmVjbGFiLmV1MIGIBgNVHR8EgYAwfjA9
oDugOYY3aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY3JsL2Nh
Y3JsLmNybDA9oDugOYY3aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9w
dWIvY3JsL2NhY3JsLmNybDCBogYIKwYBBQUHAQEEgZUwgZIwRwYIKwYBBQUHMAKGO2h0dHA6
Ly9jZHAxLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0
MEcGCCsGAQUFBzAChjtodHRwOi8vY2RwMi5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWNhL3B1
Yi9jYWNlcnQvY2FjZXJ0LmNydDANBgkqhkiG9w0BAQUFAAOCAQEAbDEPnQ9JpouPHYA1OEek
P3l3GNM0HBzadVbtbN5MDtFmoVgdLYqlQaHb30wFhuOMbsNCOzV0k8EOvBVOT9BiEJ70RWcl
SZQ460jZS2MY6n5oG/ilZuu6N/N3GSLg2pBBNH9vZFCyBJ9n4Px7A4gQF07G+CNfV2jdE1yy
PjzIVPhg6bBgia8nXroBFe6oteavMspo0gLGIJ63NsCbl6ckPa96grT+mnnQD0h6jk/IGtXS
09mEWRbN7zZu0x0q+SScpljG36Q+jnG0U5zQI0jAx8CcYEQQH5QOlsw1Zu35OI4lsi7ycFkz
JNfbfEC4ihuw9J2L43BFGMojkhPkhVExHTCCBCEwggMJoAMCAQICAgDHMA0GCSqGSIb3DQEB
BQUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYD
VQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMwIQYDVQQDExpEZXV0c2NoZSBUZWxla29t
IFJvb3QgQ0EgMjAeFw0wNjEyMTkxMDI5MDBaFw0xOTA2MzAyMzU5MDBaMFoxCzAJBgNVBAYT
AkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdERk4tUEtJMSQwIgYDVQQDExtE
Rk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK
AoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAxBAuZgeKmFNJSoCgj
hIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84IkQ4wcOItqaACa
7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVgTe3RCSMq
ljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sWVlZD
z+HVEz2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjgdkw
gdYwcAYDVR0fBGkwZzBloGOgYYZfaHR0cDovL3BraS50ZWxlc2VjLmRlL2NnaS1iaW4vc2Vy
dmljZS9hZl9Eb3dubG9hZEFSTC5jcmw/LWNybF9mb3JtYXQ9WF81MDkmLWlzc3Vlcj1EVF9S
T09UX0NBXzIwHQYDVR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1UdIwQYMBaAFDHD
eRu69VPXF+CJei0XbAqzK50zMA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgEC
MA0GCSqGSIb3DQEBBQUAA4IBAQA74Vp3wEgX3KkY7IGvWonwvSiSpspZGBJw7Cjy565/lizn
8l0ZMfYTK3S9vYCyufdnyTmieTvhERHua3iRM347XyYndVNljjNj7s9zw7CSI0khUHUjoR8Y
4pSFPT8z6XcgjaK95qGFKUD2P3MyWA0Ja6bahWzAP7uNZmRWJE6uDT8yNQFb6YyC2XJZT7GG
hfF0hVblw/hc843uR7NTBXDn5U2KaYMo4RMJhp5eyOpYHgwf+aTUWgRo/Sg+iwK2WLX2oSw3
VwBnqyNojWOl75lrXP1LVvarQIc01BGSbOyHxQoLBzNytG8MHVQs2FHHzL8w00Ny8TK/jM5J
Y6gA9/IcMYICIDCCAhwCAQEwgZkwgZAxCzAJBgNVBAYTAkRFMRgwFgYDVQQKEw9ORUMgRXVy
b3BlIEx0ZC4xIDAeBgNVBAsTF05FQyBMYWJvcmF0b3JpZXMgRXVyb3BlMRIwEAYDVQQDEwlO
RUNMQUItQ0ExMTAvBgkqhkiG9w0BCQEWInplcnRpZml6aWVydW5nc3N0ZWxsZUBudy5uZWNs
YWIuZXUCBA0uKwcwCQYFKw4DAhoFAKBdMCMGCSqGSIb3DQEJBDEWBBTyx179+SHWjmcvy91k
DR5f1kiVKzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wOTA3
MjQwNzAxMzNaMA0GCSqGSIb3DQEBAQUABIIBAApAyJxL6nywjuTAkj+ymynYFqExQf5U4QIZ
gi1ue8G5Rnj7nExwKoLzjQtwhLXzAoFW+Ec0rWy5XvTF3A0kGEvq+AGQdMSCScbE0v7x3w0y
9Nl4U/dyB8U8XSQ4YxVWlLmJzfQulP11GFzzWVmkAzmbppHIEqqUx6rYT8G4kgw/iIVqsB3l
ma9MCk7fisdaOtbwK8zcdTXwLjgZzi4eq5fU0ISHXR6mjGht2BfZ6cj4jw8Hw2p2tGhro3hj
AxD28BqLGXDtk8LEpINk5fbV9prFdfWdNEStN3goC0U/rIbwRTWRQii2nJ+L38AYL0YkSitg
kE/2K+5Clo0R5XRDLwo=

--B_3331270894_23373717--


From spencer@wonderhamster.org  Fri Jul 24 08:43:13 2009
Return-Path: <spencer@wonderhamster.org>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 674D13A6974 for <sip-clf@core3.amsl.com>; Fri, 24 Jul 2009 08:43:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.606
X-Spam-Level: 
X-Spam-Status: No, score=-1.606 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id znmvzxLMyV3N for <sip-clf@core3.amsl.com>; Fri, 24 Jul 2009 08:43:12 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 18C9F3A6A50 for <sip-clf@ietf.org>; Fri, 24 Jul 2009 08:43:10 -0700 (PDT)
Received: from S73602b ([212.112.167.84]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1MUMjC0J32-000Nk9; Fri, 24 Jul 2009 11:30:45 -0400
Message-ID: <A6DAFC07E1564ADFBF19C65E3657DB4D@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com>	<D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com><EDC652A26FB23C4EB6384A4584434A0401892AF4@307622ANEX5.global.avaya.com><4A664053.7070603@alcatel-lucent.com><CB8F8D6E-5908-446A-84B1-B4FF84010F06@nostrum.com>	<F3298CA2E6E14FB3BA1B5234ACF402FC@china.huawei.com>	<167dfb9b0907221441x3d154660tc6275623f1dc3e56@mail.gmail.com> <EDC652A26FB23C4EB6384A4584434A04018CF520@307622ANEX5.global.avaya.com> <4A687BF6.30308@alcatel-lucent.com> <EDC652A26FB23C4EB6384A4584434A04018CF52F@307622ANEX5.global.avaya.com>
Date: Thu, 23 Jul 2009 19:03:12 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX18Ngmt1H+Y92Ubnetv2fMYVKARb63kolUuq0YV DGKDVGtXgxXS9l3xTlRro/YH7V5nvos+v8e2KSiByA3LuvcXnu OqB4aRQqRtLmHKXjKdCsffGpl7hHvpbLsZu1QP6ORU=
Cc: Nevil Brownlee <n.brownlee@auckland.ac.nz>, SIP-CLF Mailing List <sip-clf@ietf.org>, Juergen Quittek <Quittek@nw.neclab.eu>
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 24 Jul 2009 15:43:13 -0000

I agree with Dan here.

Thanks,

Spencer

----- Original Message ----- 
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Cc: "Theo Zourzouvillys" <theo@crazygreek.co.uk>; "Spencer Dawkins" 
<spencer@wonderhamster.org>; "SIP-CLF Mailing List" <sip-clf@ietf.org>; 
"Nevil Brownlee" <n.brownlee@auckland.ac.nz>; "Juergen Quittek" 
<Quittek@nw.neclab.eu>
Sent: Thursday, July 23, 2009 10:09 AM
Subject: RE: [sip-clf] draft CLF charter


No expertise of IPFIX is required at this stage, I guess, but rather
presenting the problem space and mentioning that IPFIX is considered as
a possible solution or part of the solution for SIP-CLF. Stealing slides
used in OPSAREA should be fine.

Dan


> -----Original Message-----
> From: Vijay K. Gurbani [mailto:vkg@alcatel-lucent.com]
> Sent: Thursday, July 23, 2009 6:04 PM
> To: Romascanu, Dan (Dan)
> Cc: Theo Zourzouvillys; Spencer Dawkins; SIP-CLF Mailing
> List; Nevil Brownlee; Juergen Quittek
> Subject: Re: [sip-clf] draft CLF charter
>
> Romascanu, Dan (Dan) wrote:
> > It may be a good idea to have somebody from the SIP-CLF
> crowd come to
> > the IPFIX meeting next week and make a five minutes presentation so
> > that IPFIX folks are aware about this.
>
> I am not an expert at ipfix, so if Theo, Hadriel, or Spencer
> would rather make a presentation, that is fine.  Otherwise,
> since I am making a presentation on SIP CLF at the opsarea
> meeting anyway, I can quickly present a digested version of
> that slide deck at ipfix.  Regardless of who makes the
> presentation, I can share the opsarea SIP CLF slide deck so
> we can beg, borrow or steal slides from it for ipfix.
>
> Thanks,
>
> - vijay
> --
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960
> Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
> Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
> Web:   http://ect.bell-labs.com/who/vkg/
> 


From vkg@alcatel-lucent.com  Fri Jul 24 09:22:45 2009
Return-Path: <vkg@alcatel-lucent.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 41C6628C1E6 for <sip-clf@core3.amsl.com>; Fri, 24 Jul 2009 09:22:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[AWL=0.051,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SdE8gwE8EEeS for <sip-clf@core3.amsl.com>; Fri, 24 Jul 2009 09:22:44 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 7B7E928C1E3 for <sip-clf@ietf.org>; Fri, 24 Jul 2009 09:22:44 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id n6OGMJf9020777 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <sip-clf@ietf.org>; Fri, 24 Jul 2009 11:22:19 -0500 (CDT)
Received: from [135.185.236.17] (il0015vkg1.ih.lucent.com [135.185.236.17]) by umail.lucent.com (8.13.8/TPES) with ESMTP id n6OGMJmX017284 for <sip-clf@ietf.org>; Fri, 24 Jul 2009 11:22:19 -0500 (CDT)
Message-ID: <4A69DFBB.3010307@alcatel-lucent.com>
Date: Fri, 24 Jul 2009 11:22:19 -0500
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "sip-clf@ietf.org" <sip-clf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Subject: [sip-clf] SIP-CLF slides for opsarea and possibly ipfix
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 24 Jul 2009 16:22:45 -0000

Hello: Here is a link to the slide show I plan to present
on SIP-CLF at the opsarea meeting on Thu.  An abbreviated
version of this may be presented at the ipfix meeting
on Mon as well.

Please do look at the contents and suggest any changes.

http://ect.bell-labs.com/who/vkg/IETF/75/IETF-75-sip-clf-vkg.ppt

Thank you,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
Web:   http://ect.bell-labs.com/who/vkg/

From HKaplan@acmepacket.com  Fri Jul 24 10:41:20 2009
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24CEE3A6B01 for <sip-clf@core3.amsl.com>; Fri, 24 Jul 2009 10:41:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rrNrfdVbluXu for <sip-clf@core3.amsl.com>; Fri, 24 Jul 2009 10:41:19 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 9BC9A3A6A13 for <sip-clf@ietf.org>; Fri, 24 Jul 2009 10:41:18 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Fri, 24 Jul 2009 13:41:16 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Fri, 24 Jul 2009 13:41:16 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>, "sip-clf@ietf.org" <sip-clf@ietf.org>
Date: Fri, 24 Jul 2009 13:41:15 -0400
Thread-Topic: [sip-clf] SIP-CLF slides for opsarea and possibly ipfix
Thread-Index: AcoMewhSCE45pU3/S2actHFv57HzhwABjPHg
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC31984654C6C@mail>
References: <4A69DFBB.3010307@alcatel-lucent.com>
In-Reply-To: <4A69DFBB.3010307@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [sip-clf] SIP-CLF slides for opsarea and possibly ipfix
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 24 Jul 2009 17:41:20 -0000

Hi Vijay,

I would recommend the following changes:

1) Get rid of the two slides on "Need for CLF in current literature".  Neit=
her of those two use-cases are actually addressed by SIP CLF, afaict.  At l=
east not for the purpose of performing anomaly detection by using the CLF. =
(CLF would be useful to report when anomalous events are found perhaps, but=
 we've said it's not a replacement for Syslog/SNMP event reporting, right?)=
  Even if you don't agree with my view of that, there's no need to debate i=
t in the meeting, because it's not central to the need for CLF.

2) Maybe summarize the proposed charter in a slide or two?  Like list what'=
s in/out-of-scope, and the deliverables?

3) on the last slide, include opsarea in the parenthesis list, since that's=
 planned for Stockholm as well I believe.

4) I'm not quite sure what the purpose of the "Challenges in defining SIP C=
LF" slides are, but if you're itemizing them... then add "To get a common v=
iew of merged/global CLF's, must choose where in the stack/system to log SI=
P messages", and "Security and privacy related issues of various forms".

5) editorial nit: slide 3, remove the word "problem" from the top, since th=
is is a slide on benefits, not problems. Unless you're saying the problem i=
s we don't have these benefits. ;)

-hadriel


> -----Original Message-----
> From: sip-clf-bounces@ietf.org [mailto:sip-clf-bounces@ietf.org] On Behal=
f
> Of Vijay K. Gurbani
>=20
> Hello: Here is a link to the slide show I plan to present
> on SIP-CLF at the opsarea meeting on Thu.  An abbreviated
> version of this may be presented at the ipfix meeting
> on Mon as well.
>=20
> Please do look at the contents and suggest any changes.
>=20
> http://ect.bell-labs.com/who/vkg/IETF/75/IETF-75-sip-clf-vkg.ppt
>=20

From vkg@alcatel-lucent.com  Fri Jul 24 14:03:11 2009
Return-Path: <vkg@alcatel-lucent.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E461B3A68BB for <sip-clf@core3.amsl.com>; Fri, 24 Jul 2009 14:03:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[AWL=0.047,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TOL1pvrycsge for <sip-clf@core3.amsl.com>; Fri, 24 Jul 2009 14:03:10 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id BC0C23A6809 for <sip-clf@ietf.org>; Fri, 24 Jul 2009 14:03:10 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id n6OKVbQO006895 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 Jul 2009 15:31:38 -0500 (CDT)
Received: from [135.185.236.17] (il0015vkg1.ih.lucent.com [135.185.236.17]) by umail.lucent.com (8.13.8/TPES) with ESMTP id n6OKVbuL027692; Fri, 24 Jul 2009 15:31:37 -0500 (CDT)
Message-ID: <4A6A1A29.9010504@alcatel-lucent.com>
Date: Fri, 24 Jul 2009 15:31:37 -0500
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Hadriel Kaplan <HKaplan@acmepacket.com>
References: <4A69DFBB.3010307@alcatel-lucent.com> <E6C2E8958BA59A4FB960963D475F7AC31984654C6C@mail>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC31984654C6C@mail>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Cc: "sip-clf@ietf.org" <sip-clf@ietf.org>
Subject: Re: [sip-clf] SIP-CLF slides for opsarea and possibly ipfix
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 24 Jul 2009 21:03:12 -0000

Hadriel Kaplan wrote:
> Hi Vijay,

Hadriel: Thanks for the feedback; more inline.

> I would recommend the following changes:
> 
> 1) Get rid of the two slides on "Need for CLF in current literature".
> Neither of those two use-cases are actually addressed by SIP CLF,
> afaict.  At least not for the purpose of performing anomaly detection
> by using the CLF. (CLF would be useful to report when anomalous
> events are found perhaps, but we've said it's not a replacement for
> Syslog/SNMP event reporting, right?)  Even if you don't agree with my
> view of that, there's no need to debate it in the meeting, because
> it's not central to the need for CLF.

OK; training anomaly detection systems for semantic attacks on
SIP through the CLF may well be classified as a research topic,
so you are right -- I have taken these two slides out.

> 2) Maybe summarize the proposed charter in a slide or two?  Like list
> what's in/out-of-scope, and the deliverables?

OK; will do.

> 3) on the last slide, include opsarea in the parenthesis list, since
> that's planned for Stockholm as well I believe.

OK.

> 4) I'm not quite sure what the purpose of the "Challenges in defining
> SIP CLF" slides are, but if you're itemizing them... then add "To get
> a common view of merged/global CLF's, must choose where in the
> stack/system to log SIP messages", and "Security and privacy related
> issues of various forms".

I have put in security and privacy related issues as a bullet.

The other point -- "to get a common view of merged/global CLFs ..."
may require some discussion.  Are you proposing that there be a
central CLF server where all SIP actors in a network send their
messages for correlation?  At least my view of the SIP CLF was
more along the lines of each SIP actor producing their own
CLF.

> 5) editorial nit: slide 3, remove the word "problem" from the top,
> since this is a slide on benefits, not problems. Unless you're saying
> the problem is we don't have these benefits. ;)

Done.

The updated copy is at the same location
http://ect.bell-labs.com/who/vkg/IETF/75/IETF-75-sip-clf-vkg.ppt

Thank you for your time on this.

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
Web:   http://ect.bell-labs.com/who/vkg/

From HKaplan@acmepacket.com  Fri Jul 24 14:18:02 2009
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E426A3A6AF6 for <sip-clf@core3.amsl.com>; Fri, 24 Jul 2009 14:18:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xGHJGMQnIAGj for <sip-clf@core3.amsl.com>; Fri, 24 Jul 2009 14:18:02 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 068EF3A68BB for <sip-clf@ietf.org>; Fri, 24 Jul 2009 14:18:01 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Fri, 24 Jul 2009 17:18:00 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Fri, 24 Jul 2009 17:18:00 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Date: Fri, 24 Jul 2009 17:17:59 -0400
Thread-Topic: [sip-clf] SIP-CLF slides for opsarea and possibly ipfix
Thread-Index: AcoMnce1HsJuEZtbRdeu20NMMEfCIQAA/Ixw
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC31984654FE0@mail>
References: <4A69DFBB.3010307@alcatel-lucent.com> <E6C2E8958BA59A4FB960963D475F7AC31984654C6C@mail> <4A6A1A29.9010504@alcatel-lucent.com>
In-Reply-To: <4A6A1A29.9010504@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "sip-clf@ietf.org" <sip-clf@ietf.org>
Subject: Re: [sip-clf] SIP-CLF slides for opsarea and possibly ipfix
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 24 Jul 2009 21:18:03 -0000

> -----Original Message-----
> From: Vijay K. Gurbani [mailto:vkg@alcatel-lucent.com]
> Sent: Friday, July 24, 2009 4:32 PM
>=20
> OK; training anomaly detection systems for semantic attacks on
> SIP through the CLF may well be classified as a research topic,
> so you are right -- I have taken these two slides out.

It's not so much that it's a research topic, but rather that some of the ne=
eds of anomaly detection literally require getting the entire SIP message (=
or at least a lot more than what we're proposing as the baseline header inf=
o).  Even the currently *deployed* anomaly detectors check more than what t=
he current drafts are proposing to include in a CLF.


> The other point -- "to get a common view of merged/global CLFs ..."
> may require some discussion.  Are you proposing that there be a
> central CLF server where all SIP actors in a network send their
> messages for correlation?  At least my view of the SIP CLF was
> more along the lines of each SIP actor producing their own
> CLF.

Nope, I'm talking about if all SIP actors generate their own CLF's, and one=
 or more central systems read and merge the CLF's generated by the actors. =
 In that case, then it's potentially important that we specify how/when the=
 data in the CLF was created, so that all actors provide a consistent view.=
 =20

For example, if B2BUA-1 generates CLF entries for SIP messages it's sending=
 out, but does so internally before certain manipulations such as number tr=
anslations - while a second B2BUA-2 receiving the message records its CLF o=
n reception but after its number translations, the view from a common place=
 is not consistent. (number translations just being an example)  And we may=
 decide it doesn't matter in the end - but it's a potential "Challenge".

Even for some sanity/consistency we'll probably need to define whether a CL=
F entry is generated at both receiving and sending of SIP messages, above v=
s. in vs. below a transaction layer, before or after Privacy anonymization,=
 etc.

-hadriel

From vkg@alcatel-lucent.com  Fri Jul 24 14:32:17 2009
Return-Path: <vkg@alcatel-lucent.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5C75828C18A for <sip-clf@core3.amsl.com>; Fri, 24 Jul 2009 14:32:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8f6VYvJJSufv for <sip-clf@core3.amsl.com>; Fri, 24 Jul 2009 14:32:16 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id 2C61A28C0EE for <sip-clf@ietf.org>; Fri, 24 Jul 2009 14:32:15 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id n6OLWDRl014335 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 Jul 2009 16:32:13 -0500 (CDT)
Received: from [135.185.236.17] (il0015vkg1.ih.lucent.com [135.185.236.17]) by umail.lucent.com (8.13.8/TPES) with ESMTP id n6OLWCLv015762; Fri, 24 Jul 2009 16:32:13 -0500 (CDT)
Message-ID: <4A6A285C.6050007@alcatel-lucent.com>
Date: Fri, 24 Jul 2009 16:32:12 -0500
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Hadriel Kaplan <HKaplan@acmepacket.com>
References: <4A69DFBB.3010307@alcatel-lucent.com> <E6C2E8958BA59A4FB960963D475F7AC31984654C6C@mail> <4A6A1A29.9010504@alcatel-lucent.com> <E6C2E8958BA59A4FB960963D475F7AC31984654FE0@mail>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC31984654FE0@mail>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: "sip-clf@ietf.org" <sip-clf@ietf.org>
Subject: Re: [sip-clf] SIP-CLF slides for opsarea and possibly ipfix
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 24 Jul 2009 21:32:17 -0000

Hadriel Kaplan wrote:
> It's not so much that it's a research topic, but rather that some of
> the needs of anomaly detection literally require getting the entire
> SIP message (or at least a lot more than what we're proposing as the
> baseline header info).  Even the currently *deployed* anomaly
> detectors check more than what the current drafts are proposing to
> include in a CLF.

Currently deployed anomaly detection systems that I am aware
of perform mostly at the parsing layer to determine whether or
not a SIP message is well-formed -- hence they need the whole
SIP message.  Are you aware of any anomaly detection systems that
do semantic anomaly detection for SIP above and beyond the
parsing layer?

> Nope, I'm talking about if all SIP actors generate their own CLF's,
> and one or more central systems read and merge the CLF's generated by
> the actors.  In that case, then it's potentially important that we
> specify how/when the data in the CLF was created, so that all actors
> provide a consistent view.

OK, but this merge is an orthogonal step.  Each actor still
produces CLF from the SIP messages that it is processing, yes?

> Even for some sanity/consistency we'll probably need to define
> whether a CLF entry is generated at both receiving and sending of SIP
> messages, 

Would not that depend on the specific role being played by the
SIP actor?  A proxy will, out of necessity, generate incoming
requests, responses sent upstream, requests sent downstream,
and responses received from downstream servers -- and do all
this so that the entire SIP search tree corresponding to the
incoming request can be rapidly recreated for analysis later.
A UAC, OTOH, can simply generate a CLF that has a list of requests
that it sent out and the responses it received for those
requests.

> above vs. in vs. below a transaction layer, 

Below the transaction layer is the parser -- probably need to
generate CLF at or above the transaction layer.

> before or after Privacy anonymization, etc.

Sure.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
Web:   http://ect.bell-labs.com/who/vkg/

From HKaplan@acmepacket.com  Fri Jul 24 15:58:10 2009
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9FF893A6BA3 for <sip-clf@core3.amsl.com>; Fri, 24 Jul 2009 15:58:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q9hP29VVZQ2P for <sip-clf@core3.amsl.com>; Fri, 24 Jul 2009 15:58:09 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 65AD03A6812 for <sip-clf@ietf.org>; Fri, 24 Jul 2009 15:58:09 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Fri, 24 Jul 2009 18:58:09 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Fri, 24 Jul 2009 18:58:09 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Date: Fri, 24 Jul 2009 18:58:08 -0400
Thread-Topic: anomaly detectors (was: SIP-CLF slides for opsarea and possibly ipfix)
Thread-Index: AcoMpjcfbWmOM+YRRau96GylkZkNRQAADbuQ
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC31984655059@mail>
References: <4A69DFBB.3010307@alcatel-lucent.com> <E6C2E8958BA59A4FB960963D475F7AC31984654C6C@mail> <4A6A1A29.9010504@alcatel-lucent.com> <E6C2E8958BA59A4FB960963D475F7AC31984654FE0@mail> <4A6A285C.6050007@alcatel-lucent.com>
In-Reply-To: <4A6A285C.6050007@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "sip-clf@ietf.org" <sip-clf@ietf.org>
Subject: Re: [sip-clf] anomaly detectors (was: SIP-CLF slides for opsarea and possibly ipfix)
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 24 Jul 2009 22:58:10 -0000

> -----Original Message-----
> From: Vijay K. Gurbani [mailto:vkg@alcatel-lucent.com]
> Sent: Friday, July 24, 2009 5:32 PM
>=20
> Hadriel Kaplan wrote:
> > It's not so much that it's a research topic, but rather that some of
> > the needs of anomaly detection literally require getting the entire
> > SIP message (or at least a lot more than what we're proposing as the
> > baseline header info).  Even the currently *deployed* anomaly
> > detectors check more than what the current drafts are proposing to
> > include in a CLF.
>=20
> Currently deployed anomaly detection systems that I am aware
> of perform mostly at the parsing layer to determine whether or
> not a SIP message is well-formed -- hence they need the whole
> SIP message.  Are you aware of any anomaly detection systems that
> do semantic anomaly detection for SIP above and beyond the
> parsing layer?

Yes, of course.  You do know I work for an SBC vendor, right? :)
SBC's do anomaly detection both at the parser layer _and_ at higher layers,=
 and have been for years.  Some of us just don't call the higher layer thin=
gs "anomaly detection" - because we market it more on the actions we take o=
nce we detect an anomaly (like reject or log or blacklist), or the benefit =
to the customer (like "Fraud Prevention", "Hijack prevention", "DDoS protec=
tion", "SPIT Protection", etc.). =20

But anyway, there are centralized "anomaly detectors" that purport to analy=
ze "anomalies" too - I don't know what all they mean by that, but they've a=
sked us to provide them SIP message feeds (which right now is basically eve=
rything).  If I was them and looked at a CLF, I'd want to get quite a bit m=
ore than what we define: Via's, Route's, Record-Route's, Refer-To's, P-Asse=
rted/P-Preferred/Remote-Party-ID, Path's, Max-Forwards, Content-Type's, His=
tory-Info, and Diversion... just off the top of my head. =20

And really, as an "anomaly detector" I would want to filter which headers I=
 *don't* care-about, not which I do.=20

-hadriel

From vkg@alcatel-lucent.com  Sun Jul 26 02:07:45 2009
Return-Path: <vkg@alcatel-lucent.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6F95828C0EA for <sip-clf@core3.amsl.com>; Sun, 26 Jul 2009 02:07:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9E8ynpMn9d9p for <sip-clf@core3.amsl.com>; Sun, 26 Jul 2009 02:07:44 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 3CDF73A6909 for <sip-clf@ietf.org>; Sun, 26 Jul 2009 02:07:44 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id n6Q97fBO020003 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Jul 2009 04:07:41 -0500 (CDT)
Received: from shoonya.ih.lucent.com (guard.research.bell-labs.com [135.104.2.10]) by umail.lucent.com (8.13.8/TPES) with ESMTP id n6Q97eDI012713; Sun, 26 Jul 2009 04:07:41 -0500 (CDT)
Message-ID: <4A6C1D08.9020301@alcatel-lucent.com>
Date: Sun, 26 Jul 2009 04:08:24 -0500
From: Vijay Gurbani <vkg@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Hadriel Kaplan <HKaplan@acmepacket.com>
References: <4A69DFBB.3010307@alcatel-lucent.com> <E6C2E8958BA59A4FB960963D475F7AC31984654C6C@mail> <4A6A1A29.9010504@alcatel-lucent.com> <E6C2E8958BA59A4FB960963D475F7AC31984654FE0@mail> <4A6A285C.6050007@alcatel-lucent.com> <E6C2E8958BA59A4FB960963D475F7AC31984655059@mail>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC31984655059@mail>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Cc: "sip-clf@ietf.org" <sip-clf@ietf.org>
Subject: Re: [sip-clf] anomaly detectors
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 26 Jul 2009 09:07:45 -0000

Hadriel Kaplan wrote:
> SBC's do anomaly detection both at the parser layer _and_ at higher
> layers, and have been for years.  Some of us just don't call the
> higher layer things "anomaly detection" - because we market it more
> on the actions we take once we detect an anomaly (like reject or log
> or blacklist), or the benefit to the customer (like "Fraud
> Prevention", "Hijack prevention", "DDoS protection", "SPIT
> Protection", etc.).

Do SBCs use learning algorithms to do such anomaly detection
or do policy based triggers form the foundation of such detection?
I suspect it is the latter.

Can existing SBC-based anomaly detection system be trained on
the infamous SIP PRACK state machine to detect anomalous behavior?
I suspect not -- though I may be wrong.  I am aware of some
preliminary work on training machines to recognize the temporal
association of SIP messages in a dialog (i.e., BYE is preceded by
an INVITE); but so far this work is just starting and the more
complex cases like it is okay to send an UPDATE and CANCEL
before an INVITE finishes, but one must not send a SUBSCRIBE
in similar scenarios are not supported.  For an SBC to do such
analysis, an awful lot of dialog state would be needed; OTOH,
doing such detection at the individual SIP actor level (i.e.,
a proxy receiving such requests from UAs and producing a CLF
record for analysis) may be more manageable.

> But anyway, there are centralized "anomaly detectors" that purport to
> analyze "anomalies" too - I don't know what all they mean by that,
> but they've asked us to provide them SIP message feeds (which right
> now is basically everything).  If I was them and looked at a CLF, I'd
> want to get quite a bit more than what we define: Via's, Route's,
> Record-Route's, Refer-To's, P-Asserted/P-Preferred/Remote-Party-ID,
> Path's, Max-Forwards, Content-Type's, History-Info, and Diversion...
> just off the top of my head.

I suspect that what we have been discussing in the mailing list, i.e.,
having a base set of headers and an extensibility model to account
for other headers is generally a good thing.  Reverting to logging
the whole SIP message seems to be throwing our hands up in the air
and saying that we don't really know what we want so we'll save the
whole kitchen sink just in case.  HTTP CLF has worked without
saving the whole message, and with some judicious thought I think
we can make SIP CLF work as well.

> And really, as an "anomaly detector" I would want to filter which
> headers I *don't* care-about, not which I do.

Possibly; however, for training and subsequent use of an anomaly
system, you would need the headers which you care about (i.e., if
two colluding UAs leak information by subscribing to event package
X but sending notifications for event package Y, I'd want to log
the appropriate headers that I care about.)

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://ect.bell-labs.com/who/vkg

From HKaplan@acmepacket.com  Sun Jul 26 05:24:27 2009
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 119623A67F8 for <sip-clf@core3.amsl.com>; Sun, 26 Jul 2009 05:24:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SYiKE+8mGcey for <sip-clf@core3.amsl.com>; Sun, 26 Jul 2009 05:24:26 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id E82723A6403 for <sip-clf@ietf.org>; Sun, 26 Jul 2009 05:24:25 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Sun, 26 Jul 2009 08:24:24 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Sun, 26 Jul 2009 08:24:21 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Vijay Gurbani <vkg@alcatel-lucent.com>
Date: Sun, 26 Jul 2009 08:24:20 -0400
Thread-Topic: anomaly detectors
Thread-Index: AcoN0JLDCy8mlATjRlmdqmaeda6RywABvQEw
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC31984655206@mail>
References: <4A69DFBB.3010307@alcatel-lucent.com> <E6C2E8958BA59A4FB960963D475F7AC31984654C6C@mail> <4A6A1A29.9010504@alcatel-lucent.com> <E6C2E8958BA59A4FB960963D475F7AC31984654FE0@mail> <4A6A285C.6050007@alcatel-lucent.com> <E6C2E8958BA59A4FB960963D475F7AC31984655059@mail> <4A6C1D08.9020301@alcatel-lucent.com>
In-Reply-To: <4A6C1D08.9020301@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "sip-clf@ietf.org" <sip-clf@ietf.org>
Subject: Re: [sip-clf] anomaly detectors
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 26 Jul 2009 12:24:27 -0000

> -----Original Message-----
> From: Vijay Gurbani [mailto:vkg@alcatel-lucent.com]
> Sent: Sunday, July 26, 2009 5:08 AM
>=20
> Do SBCs use learning algorithms to do such anomaly detection
> or do policy based triggers form the foundation of such detection?
> I suspect it is the latter.

As far as I know, many of them still use policy-based triggers in practice =
- but "learning algorithms" for the parser-layer detection and for some loa=
d-based behavior limits have been either claimed or hinted-at by some SBC v=
endors for a while, including the company I work for. (but what each of us =
do in that space in practice is not public info for competitive reasons)=20


> Can existing SBC-based anomaly detection system be trained on
> the infamous SIP PRACK state machine to detect anomalous behavior?
> I suspect not -- though I may be wrong.  I am aware of some
> preliminary work on training machines to recognize the temporal
> association of SIP messages in a dialog (i.e., BYE is preceded by
> an INVITE); but so far this work is just starting and the more
> complex cases like it is okay to send an UPDATE and CANCEL
> before an INVITE finishes, but one must not send a SUBSCRIBE
> in similar scenarios are not supported.  For an SBC to do such
> analysis, an awful lot of dialog state would be needed...

SBC's can and usually do maintain full dialog state for all dialogs (as a b=
2bua), and enforce protocol compliance for messages and their state machine=
s, with knobs for various control.  That was one of the basic tenets from t=
he beginning.  Of course whether the SBC's do it correctly, or whether they=
 should be doing it to begin with, is a different question. ;)  It's always=
 been a fine line, though, between enforcing protocol rules for security, a=
nd letting sessions succeed when they can or even fixing them so they do su=
cceed.  One man's anomalous signaling, is another man's paying customer.


> I suspect that what we have been discussing in the mailing list, i.e.,
> having a base set of headers and an extensibility model to account
> for other headers is generally a good thing. =20

Yup.

> Reverting to logging
> the whole SIP message seems to be throwing our hands up in the air
> and saying that we don't really know what we want so we'll save the
> whole kitchen sink just in case.  HTTP CLF has worked without
> saving the whole message, and with some judicious thought I think
> we can make SIP CLF work as well.

It's not that I don't think CLF has value - it's the central claim that's i=
t's for "anomaly detectors" that makes me wince.  Obviously it can be used =
for some anomaly purposes - just that we shouldn't be saying that's its mai=
n purpose/use-case, because it's not good enough for it, imho.

It's sorta like the sip-ipfix draft, which has as one of its use-cases "bil=
ling".  While it may be technically possible to do billing for very trivial=
 cases using a CLF formatted as ipfix, it is missing so much meta-data requ=
ired for billing in the real-world that the claim is distracting because it=
's so clearly not useable for that.

-hadriel

From vkg@alcatel-lucent.com  Sun Jul 26 05:45:12 2009
Return-Path: <vkg@alcatel-lucent.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 18DBA3A69E5 for <sip-clf@core3.amsl.com>; Sun, 26 Jul 2009 05:45:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level: 
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4tZCQZTb5MSI for <sip-clf@core3.amsl.com>; Sun, 26 Jul 2009 05:45:11 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id EEB083A67F8 for <sip-clf@ietf.org>; Sun, 26 Jul 2009 05:45:10 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id n6QCj94H006772 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Jul 2009 07:45:10 -0500 (CDT)
Received: from shoonya.ih.lucent.com (guard.research.bell-labs.com [135.104.2.10]) by umail.lucent.com (8.13.8/TPES) with ESMTP id n6QCj6iD008975; Sun, 26 Jul 2009 07:45:08 -0500 (CDT)
Message-ID: <4A6C4FFF.9030503@alcatel-lucent.com>
Date: Sun, 26 Jul 2009 07:45:51 -0500
From: Vijay Gurbani <vkg@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Hadriel Kaplan <HKaplan@acmepacket.com>
References: <4A69DFBB.3010307@alcatel-lucent.com> <E6C2E8958BA59A4FB960963D475F7AC31984654C6C@mail> <4A6A1A29.9010504@alcatel-lucent.com> <E6C2E8958BA59A4FB960963D475F7AC31984654FE0@mail> <4A6A285C.6050007@alcatel-lucent.com> <E6C2E8958BA59A4FB960963D475F7AC31984655059@mail> <4A6C1D08.9020301@alcatel-lucent.com> <E6C2E8958BA59A4FB960963D475F7AC31984655206@mail>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC31984655206@mail>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Cc: "sip-clf@ietf.org" <sip-clf@ietf.org>
Subject: Re: [sip-clf] anomaly detectors
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 26 Jul 2009 12:45:12 -0000

Hadriel Kaplan wrote:
> It's not that I don't think CLF has value - it's the central claim
> that's it's for "anomaly detectors" that makes me wince.  Obviously
> it can be used for some anomaly purposes - just that we shouldn't be
> saying that's its main purpose/use-case, because it's not good enough
> for it, imho.

I agree; I don't think it was claimed that anomaly detection is the
main purpose of SIP CLF.  It is but one possible use case if we
were to have a nicely digested information in the form of a CLF.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://ect.bell-labs.com/who/vkg

From vkg@alcatel-lucent.com  Sun Jul 26 14:41:49 2009
Return-Path: <vkg@alcatel-lucent.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 464AF3A6AD2; Sun, 26 Jul 2009 14:41:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level: 
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oQd393EH7c22; Sun, 26 Jul 2009 14:41:48 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 0A9CA3A6A0D; Sun, 26 Jul 2009 14:41:47 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id n6QLfmO1019824 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Jul 2009 16:41:48 -0500 (CDT)
Received: from shoonya.ih.lucent.com (guard.research.bell-labs.com [135.104.2.9]) by umail.lucent.com (8.13.8/TPES) with ESMTP id n6QLfh5b000704; Sun, 26 Jul 2009 16:41:44 -0500 (CDT)
Message-ID: <4A6CCDC3.5030502@alcatel-lucent.com>
Date: Sun, 26 Jul 2009 16:42:27 -0500
From: Vijay Gurbani <vkg@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: ipfix@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Cc: "sip-clf@ietf.org" <sip-clf@ietf.org>
Subject: [sip-clf] SIP CLF work to be presented in opsarea meeting
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 26 Jul 2009 21:41:49 -0000

Hello: In the RAI area, we will be starting work on the definition of
a SIP Common Log Format (CLF) -- this is essentially a summary of
a SIP packet in a well-defined format produced by a SIP actor (user
agent client, user agent server, proxy, etc.) that is saved to some
persistent store.

We will be making a presentation on this work at the opsarea
meeting on Thursday, 1300-1500.  This email is to kindly request
interested folks from ipfix to attend the opsarea meeting as
we discuss whether existing protocols can aid in SIP CLF work.

Thank you,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://ect.bell-labs.com/who/vkg

From vkg@alcatel-lucent.com  Mon Jul 27 09:09:15 2009
Return-Path: <vkg@alcatel-lucent.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CD6373A6B70 for <sip-clf@core3.amsl.com>; Mon, 27 Jul 2009 09:09:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.339
X-Spam-Level: 
X-Spam-Status: No, score=-2.339 tagged_above=-999 required=5 tests=[AWL=0.260,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gu1nPnA3RftJ for <sip-clf@core3.amsl.com>; Mon, 27 Jul 2009 09:09:14 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id C05873A6ABD for <sip-clf@ietf.org>; Mon, 27 Jul 2009 09:09:14 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id n6RG9Bi6001273 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <sip-clf@ietf.org>; Mon, 27 Jul 2009 11:09:11 -0500 (CDT)
Received: from shoonya.ih.lucent.com (guard.research.bell-labs.com [135.104.2.10]) by umail.lucent.com (8.13.8/TPES) with ESMTP id n6RG9AeV009302 for <sip-clf@ietf.org>; Mon, 27 Jul 2009 11:09:10 -0500 (CDT)
Message-ID: <4A6DD152.60602@alcatel-lucent.com>
Date: Mon, 27 Jul 2009 11:09:54 -0500
From: Vijay Gurbani <vkg@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: "sip-clf@ietf.org" <sip-clf@ietf.org>
Content-Type: multipart/mixed; boundary="------------030701040102010605080401"
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Subject: [sip-clf] [Fwd: [dispatch] Room for DISPATCH ad-hoc on CLF : Room 300 over Lunch on	Friday]
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 27 Jul 2009 16:09:15 -0000

This is a multi-part message in MIME format.
--------------030701040102010605080401
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

FYI ... just in case there is someone on sip-clf list not on
dispatch ...

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://ect.bell-labs.com/who/vkg

--------------030701040102010605080401
Content-Type: message/rfc822;
 name="[dispatch] Room for DISPATCH ad-hoc on CLF : Room 300 over Lunch on	Friday.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename*0="[dispatch] Room for DISPATCH ad-hoc on CLF : Room 300 over L";
 filename*1="unch on	Friday.eml"

Return-Path: <dispatch-bounces@ietf.org>
Received: from ihemail3.lucent.com (ihemail3.dmz.lucent.com [135.245.2.37])
	by umail.lucent.com (8.13.8/TPES) with ESMTP id n6RFkdvE019439;
	Mon, 27 Jul 2009 10:46:39 -0500 (CDT)
Received: from mail.ietf.org (mail.ietf.org [64.170.98.32])
	by ihemail3.lucent.com (8.13.8/IER-i) with ESMTP id n6RFkdLu010279;
	Mon, 27 Jul 2009 10:46:39 -0500 (CDT)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E090C3A6B15;
	Mon, 27 Jul 2009 08:46:36 -0700 (PDT)
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9F8BF3A6B5E
	for <dispatch@core3.amsl.com>; Mon, 27 Jul 2009 08:46:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id JVf132pr52LM for <dispatch@core3.amsl.com>;
	Mon, 27 Jul 2009 08:46:35 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net
	[IPv6:2001:470:1f03:267::2])
	by core3.amsl.com (Postfix) with ESMTP id 828833A6B15
	for <dispatch@ietf.org>; Mon, 27 Jul 2009 08:46:34 -0700 (PDT)
Received: from dhcp-26f2.meeting.ietf.org (dhcp-26f2.meeting.ietf.org
	[130.129.38.242]) (authenticated bits=0)
	by nostrum.com (8.14.3/8.14.3) with ESMTP id n6RFkRGi023102
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO)
	for <dispatch@ietf.org>; Mon, 27 Jul 2009 10:46:29 -0500 (CDT)
	(envelope-from rjsparks@nostrum.com)
Message-Id: <8889A362-7C1C-4712-94CC-3A0C9B6B6F79@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
To: dispatch mailing list <dispatch@ietf.org>
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 27 Jul 2009 17:46:26 +0200
X-Mailer: Apple Mail (2.935.3)
Received-SPF: pass (nostrum.com: 130.129.38.242 is authenticated by a trusted
	mechanism)
Subject: [dispatch] Room for DISPATCH ad-hoc on CLF : Room 300 over Lunch on
	Friday
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>,
	<mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>,
	<mailto:dispatch-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: dispatch-bounces@ietf.org
Errors-To: dispatch-bounces@ietf.org
X-Scanned-By: MIMEDefang 2.57 on 135.245.0.37

Room 300 over lunch on Friday
_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch

--------------030701040102010605080401--

From vkg@alcatel-lucent.com  Wed Jul 29 16:56:44 2009
Return-Path: <vkg@alcatel-lucent.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F6F03A690A for <sip-clf@core3.amsl.com>; Wed, 29 Jul 2009 16:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 tagged_above=-999 required=5 tests=[AWL=0.217,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kIbSWeIUtnQE for <sip-clf@core3.amsl.com>; Wed, 29 Jul 2009 16:56:43 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id 7DC503A68E0 for <sip-clf@ietf.org>; Wed, 29 Jul 2009 16:56:43 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id n6TNugvW012227 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <sip-clf@ietf.org>; Wed, 29 Jul 2009 18:56:42 -0500 (CDT)
Received: from shoonya.ih.lucent.com (guard.research.bell-labs.com [135.104.2.9]) by umail.lucent.com (8.13.8/TPES) with ESMTP id n6TNuffi016216 for <sip-clf@ietf.org>; Wed, 29 Jul 2009 18:56:41 -0500 (CDT)
Message-ID: <4A70E1E5.5040809@alcatel-lucent.com>
Date: Wed, 29 Jul 2009 18:57:25 -0500
From: Vijay Gurbani <vkg@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: "sip-clf@ietf.org" <sip-clf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Subject: [sip-clf] Updated SIP CLF slides for opsarea
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 29 Jul 2009 23:56:44 -0000

All: Based on the conversations we have been having this week, I have
updated the SIP CLF slides I distributed before for the opsarea meeting
tomorrow.  Slides 2-8 are new, the rest are same as before.  Please
eyeball them and let me know if there are any updates.

The slides are at: http://www.iit.edu/~gurbvij/IETF-75-sip-clf-vkg.pdf

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://ect.bell-labs.com/who/vkg

From spencer@wonderhamster.org  Thu Jul 30 05:20:08 2009
Return-Path: <spencer@wonderhamster.org>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5644D3A7133 for <sip-clf@core3.amsl.com>; Thu, 30 Jul 2009 05:20:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.005
X-Spam-Level: 
X-Spam-Status: No, score=-2.005 tagged_above=-999 required=5 tests=[AWL=0.594,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hSluqDG+7i0M for <sip-clf@core3.amsl.com>; Thu, 30 Jul 2009 05:20:07 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 28E3E3A6818 for <sip-clf@ietf.org>; Thu, 30 Jul 2009 05:20:07 -0700 (PDT)
Received: from S73602b (dhcp-63fb.meeting.ietf.org [130.129.99.251]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MKp8S-1MWUcA2fb1-00010h; Thu, 30 Jul 2009 08:20:08 -0400
Message-ID: <F4D6A2AAC1E7457DA47243E75C3CE011@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "SIP-CLF Mailing List" <sip-clf@ietf.org>
Date: Thu, 30 Jul 2009 14:19:59 +0200
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX19U+EPsVE7lkzg3Mq3K0nhyy0AUeVQ5QmOgFhY fy3tIHqbIci9tycNVMvpe3OQOZIIJBnUUDimS2WNTiQDcWHit0 tAEChBrcWnUf6xr3pUm9eriswXMB8quG6fcqXmWcWY=
Subject: [sip-clf] Fw: [dispatch] Room for DISPATCH ad-hoc on CLF : Room 300 overLunchon Friday
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 30 Jul 2009 12:20:08 -0000

My apologies - I mistyped the SIP-CLF mailing list userpart on my note 
below. Hopefully everyone is also subscribed to the DISPATCH mailing list, 
which I DID type correctly :-/

Thanks,

Spencer

----- Original Message ----- 
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "dispatch mailing list" <dispatch@ietf.org>
Cc: <clf@ietf.org>
Sent: Thursday, July 30, 2009 12:14 AM
Subject: Re: [dispatch] Room for DISPATCH ad-hoc on CLF : Room 300 
overLunchon Friday


> The SIP-CLF DISPATCH ad hoc on Friday is intended to form a working group,
> and we'll be noodling over charter text that Robert has produced (in
> consultation with others) during the meeting.
>
> Just to make sure we're all on the same page, here's the charter text 
> we'll
> be discussing - please look it over BEFORE the meeting (and if you want to 
> talk about it on the sip-clf@ietf.org mailing list before the meeting, 
> that's fine, too):
>
> The SIP Common Log Format (CLF) working group is chartered to define a
> standard logging format for systems processing SIP messages.
>
> 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 to produce reports and trends and to search for a certain SIP 
> message
> or messages, a transaction or a related set of transactions. Furthermore,
> these log records can also be used to train anomaly detection systems and
> feed events into a security event management system.
>
> The Session Initiation Protocol does not have a common log format. Diverse
> element provide distinct log formats making it complex to produce tools to
> analyze them.
>
> The CLF working group will produce a format suitable for logging from any
> SIP element. The format will anticipate the need to search, merge, and
> summarize the log records from diverse elements. The format will 
> anticipate
> the need to correlate messages from multiple elements related to a given
> request (that may fork) or a given dialog. The format will take SIP's
> extensibility into consideration, providing a way to represent SIP message
> components that are defined in the future. The format will anticipate 
> being
> used both for off-line analysis and on-line real-time processing
> applications. The working group will consider the need for efficient
> creation of records and the need for efficient processing of the records.
>
> The working group will identify the fields to appear in a log record and
> provide one or more formats for encoding those fields. The working group 
> is
> not pre-constrained to producing either a bit-field oriented or
> text-oriented format, and may choose to provide both. If the group chooses
> to specify both, it must be possible to mechanically translate between the
> formats without loss of information.
>
> Specifying the mechanics of exchanging, transporting, and storing SIP
> Common Log Format records is explicitly out of scope. Specifying a 
> real-time
> transfer mechanism for heuristic analysis is explicitly out of scope.
>
> The group will generate:
>
> A problem statement enunciating the motivation, and use cases for a SIP
> Common Log Format. This analysis will identify the required minimal
> information that must appear in any record.
>
> A specification of the SIP Common Log Format record
>
> The group will consider providing one or more reference implementations 
> for
> decoding a CLF record.
>
> One more piece of logistics ...
>
> We'll need at least one, and preferably two, scribes and a jabber scribe 
> for
> our CLF session on Friday during lunch.
>
> We'll call for volunteers at the meeting if necessary - we can't have the
> meeting without producing minutes - but it would be great if you could
> consider volunteering NOW.
>
> We have about an hour to get through some pretty important discussions, 
> and
> every minute we DON'T spend gazing meaningfully at the attendees (us) and
> looking down at computers trying not to make eye contact with the chairs
> (you) is a minute that we can use more productively!
>
> Thanks,
>
> Spencer and Theo
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch 


From bclaise@cisco.com  Thu Jul 30 06:38:06 2009
Return-Path: <bclaise@cisco.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 093C128C258 for <sip-clf@core3.amsl.com>; Thu, 30 Jul 2009 06:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.423
X-Spam-Level: 
X-Spam-Status: No, score=-1.423 tagged_above=-999 required=5 tests=[AWL=-0.901, BAYES_00=-2.599, SUBJ_ALL_CAPS=2.077]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LMF4273WxtmU for <sip-clf@core3.amsl.com>; Thu, 30 Jul 2009 06:38:05 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id 1358A3A6B62 for <sip-clf@ietf.org>; Thu, 30 Jul 2009 06:38:04 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id n6UDc2pr006101; Thu, 30 Jul 2009 15:38:02 +0200 (CEST)
Received: from [10.61.94.150] (ams3-vpn-dhcp7831.cisco.com [10.61.94.150]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id n6UDc1H8026973; Thu, 30 Jul 2009 15:38:02 +0200 (CEST)
Message-ID: <4A71A239.4090806@cisco.com>
Date: Thu, 30 Jul 2009 15:38:01 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: vkg@belllabs.com
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: sip-clf@ietf.org
Subject: [sip-clf] SIP CLF -> IPFIX?
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 30 Jul 2009 13:38:06 -0000

Hi Vijay,

During the OPSAREA, I asked you the following questions regarding your 
work at http://www.ietf.org/proceedings/75/slides/opsarea-2.pdf

QUESTION: if I understand correctly, you want a way to define 
Information Element types?

            Answer: Yes

QUESTION: just want to log the data locally, or if you want a push 
mechanism to a centralized point, or get the log file?

            Answer: So far, only local storing

If the answer to the second question changes to: one day we might want 
to export these Information Element to a centralized management, then 
IPFIX protocol (RFC5101) and IPFIX information model (RFC5102) is the 
right solution.
If the answer to the second question doesn't change: the IPFIX 
Information Model (RFC5102) might be the solution... just in case 
someone else would like to export the information. However, this is a 
less obvious case!

Btw, you should not see IPFIX as export only flow information in the 
sense of the 5 tuple (src IP, dst IP, protocol, src port, dst port), 
IPFIX is becoming a generic push mechanism.

Regards, Benoit.

From vkg@alcatel-lucent.com  Thu Jul 30 08:06:07 2009
Return-Path: <vkg@alcatel-lucent.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF91928C1CF for <sip-clf@core3.amsl.com>; Thu, 30 Jul 2009 08:06:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[AWL=0.163,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PasNWad6T-rD for <sip-clf@core3.amsl.com>; Thu, 30 Jul 2009 08:06:06 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id A2E2D28C1DB for <sip-clf@ietf.org>; Thu, 30 Jul 2009 08:06:06 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id n6UF65l5000044 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 30 Jul 2009 10:06:05 -0500 (CDT)
Received: from shoonya.ih.lucent.com (guard.research.bell-labs.com [135.104.2.9]) by umail.lucent.com (8.13.8/TPES) with ESMTP id n6UF64Vl014310; Thu, 30 Jul 2009 10:06:05 -0500 (CDT)
Message-ID: <4A71B709.4050805@alcatel-lucent.com>
Date: Thu, 30 Jul 2009 10:06:49 -0500
From: Vijay Gurbani <vkg@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Benoit Claise <bclaise@cisco.com>
References: <4A71A239.4090806@cisco.com>
In-Reply-To: <4A71A239.4090806@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] SIP CLF -> IPFIX?
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 30 Jul 2009 15:06:08 -0000

Benoit Claise wrote:
> Hi Vijay,

Benoit: Thanks for your interest in this.  One quick clarification
inline.

> During the OPSAREA, I asked you the following questions regarding your 
> work at http://www.ietf.org/proceedings/75/slides/opsarea-2.pdf
> 
> QUESTION: if I understand correctly, you want a way to define 
> Information Element types?
> 
>            Answer: Yes

Just to be sure, we want to define a logging format -- which fields
to include, how to ensure extensibility for future fields, etc.
In that vein, it is not so much about Information Element *types*
as it is about the choice and representation of the Information
Elements themselves.  I don't know if that is too fine a distinction
or not, but probably worth a clarification.

Once again, thank you for indulging us.

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://ect.bell-labs.com/who/vkg

From bclaise@cisco.com  Thu Jul 30 08:14:50 2009
Return-Path: <bclaise@cisco.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E03228C114 for <sip-clf@core3.amsl.com>; Thu, 30 Jul 2009 08:14:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.416
X-Spam-Level: 
X-Spam-Status: No, score=-2.416 tagged_above=-999 required=5 tests=[AWL=0.183,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NVuO5qAnbbHL for <sip-clf@core3.amsl.com>; Thu, 30 Jul 2009 08:14:49 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id 173473A6933 for <sip-clf@ietf.org>; Thu, 30 Jul 2009 08:14:48 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id n6UFElK4001547; Thu, 30 Jul 2009 17:14:47 +0200 (CEST)
Received: from [10.61.101.211] (dhcp-10-61-101-211.cisco.com [10.61.101.211]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id n6UFEkST008866; Thu, 30 Jul 2009 17:14:47 +0200 (CEST)
Message-ID: <4A71B8E6.7060601@cisco.com>
Date: Thu, 30 Jul 2009 17:14:46 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Vijay Gurbani <vkg@alcatel-lucent.com>
References: <4A71A239.4090806@cisco.com> <4A71B709.4050805@alcatel-lucent.com>
In-Reply-To: <4A71B709.4050805@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] SIP CLF -> IPFIX?
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 30 Jul 2009 15:14:50 -0000

Vijay,

> Benoit Claise wrote:
>> Hi Vijay,
>
> Benoit: Thanks for your interest in this.  One quick clarification
> inline.
>
>> During the OPSAREA, I asked you the following questions regarding 
>> your work at http://www.ietf.org/proceedings/75/slides/opsarea-2.pdf
>>
>> QUESTION: if I understand correctly, you want a way to define 
>> Information Element types?
>>
>>            Answer: Yes
>
> Just to be sure, we want to define a logging format -- which fields
> to include, how to ensure extensibility for future fields, etc.
> In that vein, it is not so much about Information Element *types*
> as it is about the choice and representation of the Information
> Elements themselves.
Sure. My mistake in choosing words

Regards, Benoit.
> I don't know if that is too fine a distinction
> or not, but probably worth a clarification.
>
> Once again, thank you for indulging us.
>
> - vijay


From rjsparks@nostrum.com  Fri Jul 31 03:07:19 2009
Return-Path: <rjsparks@nostrum.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4E65D3A6960; Fri, 31 Jul 2009 03:07:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z4whub+KjX2f; Fri, 31 Jul 2009 03:07:18 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 2046A3A68B7; Fri, 31 Jul 2009 03:07:17 -0700 (PDT)
Received: from dhcp-26f2.meeting.ietf.org (dhcp-26f2.meeting.ietf.org [130.129.38.242]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id n6VA7G1m052659 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 31 Jul 2009 05:07:17 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-Id: <DDC1E758-32DB-41B0-B3F3-254334341FB4@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
To: dispatch mailing list <dispatch@ietf.org>, sip-clf@ietf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 31 Jul 2009 12:07:14 +0200
X-Mailer: Apple Mail (2.935.3)
Received-SPF: pass (nostrum.com: 130.129.38.242 is authenticated by a trusted mechanism)
Subject: [sip-clf] Next revision for the proposed CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 31 Jul 2009 10:07:19 -0000

The SIP Common Log Format (CLF) working group is chartered to define
a standard logging format for systems processing SIP messages.

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 to produce reports and trends
and to search for a certain message or messages, a transaction
or a related set of transactions.  Furthermore, these log records
can also be used to train anomaly detection systems and feed events
into a security event management system.

The Session Initiation Protocol does not have a common log
format. Diverse elements provide distinct log formats making
it complex to produce tools to analyze them.

The CLF working group will produce a format suitable for logging
from any SIP element. The format will anticipate the need to
search, merge, and summarize the log records from diverse elements.
The format will anticipate the need to correlate messages from
multiple elements related to a given request (that may fork) or a
given dialog. The format will take SIP's extensibility into
consideration, providing a way to represent SIP message components
that are defined in the future.  The format will anticipate being
used both for off-line analysis and on-line real-time processing
applications. The working group will consider the need for
efficient creation of records and the need for efficient processing
of the records.

The working group will identify the fields to appear in a log
record and provide one or more formats for encoding those fields.
The working group is not pre-constrained to producing either a
bit-field oriented or text-oriented format, and may choose to
provide both. If the group chooses to specify both, it must be
possible to mechanically translate between the formats without loss
of information.

Specifying the mechanics of exchanging, transporting, and storing
SIP Common Log Format records is explicitly out of scope. Specifying
a real-time transfer mechanism for heuristic analysis is explicitly
out of scope.

The group will generate:

- A problem statement enunciating the motivation,
and use cases for a SIP Common Log Format. This analysis
will identify the required minimal information that must
appear in any record.

- A specification of the SIP Common Log Format record

The group will consider providing one or more reference
implementations for decoding a CLF record.

Goals and Milestones
===========================

Oct 09 - Problem statement, motivation, and use cases
          WGLC
Nov 09 - Problem statement, motivation, and use cases
          to IESG (Informational)
Jan 10 - SIP Common Log Format specification
          WGLC
Feb 10 - SIP Common Log Format specification
          to IESG (PS)


From rjsparks@nostrum.com  Fri Jul 31 05:29:59 2009
Return-Path: <rjsparks@nostrum.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D8FB23A6E20; Fri, 31 Jul 2009 05:29:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T42-ne40P1cd; Fri, 31 Jul 2009 05:29:58 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 24CB23A6E30; Fri, 31 Jul 2009 05:28:42 -0700 (PDT)
Received: from dhcp-26f2.meeting.ietf.org (dhcp-26f2.meeting.ietf.org [130.129.38.242]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id n6VCSf22067998 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 31 Jul 2009 07:28:42 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-Id: <FACEEDF3-11D3-42F3-B2C3-20B0C10BB6E7@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
To: sip-clf@ietf.org
In-Reply-To: <DDC1E758-32DB-41B0-B3F3-254334341FB4@nostrum.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 31 Jul 2009 14:28:40 +0200
References: <DDC1E758-32DB-41B0-B3F3-254334341FB4@nostrum.com>
X-Mailer: Apple Mail (2.935.3)
Received-SPF: pass (nostrum.com: 130.129.38.242 is authenticated by a trusted mechanism)
Cc: dispatch mailing list <dispatch@ietf.org>
Subject: Re: [sip-clf] Next revision for the proposed CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 31 Jul 2009 12:30:00 -0000

For those not in the ad-hoc - this was the text before the meeting we  
had today.

We got a lot of good feedback (minutes should be in soon). Expect a  
revision
of this in a few days (probably sometime week after next).

RjS

On Jul 31, 2009, at 12:07 PM, Robert Sparks wrote:

> The SIP Common Log Format (CLF) working group is chartered to define
> a standard logging format for systems processing SIP messages.
>
> 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 to produce reports and trends
> and to search for a certain message or messages, a transaction
> or a related set of transactions.  Furthermore, these log records
> can also be used to train anomaly detection systems and feed events
> into a security event management system.
>
> The Session Initiation Protocol does not have a common log
> format. Diverse elements provide distinct log formats making
> it complex to produce tools to analyze them.
>
> The CLF working group will produce a format suitable for logging
> from any SIP element. The format will anticipate the need to
> search, merge, and summarize the log records from diverse elements.
> The format will anticipate the need to correlate messages from
> multiple elements related to a given request (that may fork) or a
> given dialog. The format will take SIP's extensibility into
> consideration, providing a way to represent SIP message components
> that are defined in the future.  The format will anticipate being
> used both for off-line analysis and on-line real-time processing
> applications. The working group will consider the need for
> efficient creation of records and the need for efficient processing
> of the records.
>
> The working group will identify the fields to appear in a log
> record and provide one or more formats for encoding those fields.
> The working group is not pre-constrained to producing either a
> bit-field oriented or text-oriented format, and may choose to
> provide both. If the group chooses to specify both, it must be
> possible to mechanically translate between the formats without loss
> of information.
>
> Specifying the mechanics of exchanging, transporting, and storing
> SIP Common Log Format records is explicitly out of scope. Specifying
> a real-time transfer mechanism for heuristic analysis is explicitly
> out of scope.
>
> The group will generate:
>
> - A problem statement enunciating the motivation,
> and use cases for a SIP Common Log Format. This analysis
> will identify the required minimal information that must
> appear in any record.
>
> - A specification of the SIP Common Log Format record
>
> The group will consider providing one or more reference
> implementations for decoding a CLF record.
>
> Goals and Milestones
> ===========================
>
> Oct 09 - Problem statement, motivation, and use cases
>         WGLC
> Nov 09 - Problem statement, motivation, and use cases
>         to IESG (Informational)
> Jan 10 - SIP Common Log Format specification
>         WGLC
> Feb 10 - SIP Common Log Format specification
>         to IESG (PS)
>
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf


From akoba@nttv6.net  Fri Jul 31 21:21:05 2009
Return-Path: <akoba@nttv6.net>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AFE7D3A689C; Fri, 31 Jul 2009 21:21:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Gcg9IUcLIzB; Fri, 31 Jul 2009 21:21:04 -0700 (PDT)
Received: from mail.nttv6.net (mail.nttv6.net [IPv6:2001:fa8::25]) by core3.amsl.com (Postfix) with ESMTP id 4C22B3A67AD; Fri, 31 Jul 2009 21:21:04 -0700 (PDT)
Received: from [192.47.163.152] ([IPv6:2001:fa8:1000:0:cd57:c336:1bdd:a5b]) by mail.nttv6.net (8.14.3/8.14.3) with ESMTP id n714L4D2073718; Sat, 1 Aug 2009 13:21:05 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Sat, 01 Aug 2009 13:15:39 +0900
From: Atsushi Kobayashi <akoba@nttv6.net>
To: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <DDC1E758-32DB-41B0-B3F3-254334341FB4@nostrum.com>
References: <DDC1E758-32DB-41B0-B3F3-254334341FB4@nostrum.com>
Message-Id: <20090801130506.288A.17391CF2@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.50.05 [ja] (Unregistered)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (mail.nttv6.net [IPv6:2001:fa8::25]); Sat, 01 Aug 2009 13:21:05 +0900 (JST)
Cc: sip-clf@ietf.org, dispatch mailing list <dispatch@ietf.org>
Subject: Re: [sip-clf] Next revision for the proposed CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 01 Aug 2009 04:21:05 -0000

Dear all,

I have one question.
Does this charter include the media description part, i.e. SDP?
I understood this motivation, however regarding security and trouble
shooting, we need to track signaling and media as well.
If SIP-CLF outputs the media description, we can correlate SIP signaling
and media traffic data. The media traffic data may be outputted by IPFIX
or other protocols.

Otherwise, is it future work?

Regards,
Atsushi


On Fri, 31 Jul 2009 12:07:14 +0200
Robert Sparks <rjsparks@nostrum.com> wrote:

> The SIP Common Log Format (CLF) working group is chartered to define
> a standard logging format for systems processing SIP messages.
> 
> 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 to produce reports and trends
> and to search for a certain message or messages, a transaction
> or a related set of transactions.  Furthermore, these log records
> can also be used to train anomaly detection systems and feed events
> into a security event management system.
> 
> The Session Initiation Protocol does not have a common log
> format. Diverse elements provide distinct log formats making
> it complex to produce tools to analyze them.
> 
> The CLF working group will produce a format suitable for logging
> from any SIP element. The format will anticipate the need to
> search, merge, and summarize the log records from diverse elements.
> The format will anticipate the need to correlate messages from
> multiple elements related to a given request (that may fork) or a
> given dialog. The format will take SIP's extensibility into
> consideration, providing a way to represent SIP message components
> that are defined in the future.  The format will anticipate being
> used both for off-line analysis and on-line real-time processing
> applications. The working group will consider the need for
> efficient creation of records and the need for efficient processing
> of the records.
> 
> The working group will identify the fields to appear in a log
> record and provide one or more formats for encoding those fields.
> The working group is not pre-constrained to producing either a
> bit-field oriented or text-oriented format, and may choose to
> provide both. If the group chooses to specify both, it must be
> possible to mechanically translate between the formats without loss
> of information.
> 
> Specifying the mechanics of exchanging, transporting, and storing
> SIP Common Log Format records is explicitly out of scope. Specifying
> a real-time transfer mechanism for heuristic analysis is explicitly
> out of scope.
> 
> The group will generate:
> 
> - A problem statement enunciating the motivation,
> and use cases for a SIP Common Log Format. This analysis
> will identify the required minimal information that must
> appear in any record.
> 
> - A specification of the SIP Common Log Format record
> 
> The group will consider providing one or more reference
> implementations for decoding a CLF record.
> 
> Goals and Milestones
> ===========================
> 
> Oct 09 - Problem statement, motivation, and use cases
>           WGLC
> Nov 09 - Problem statement, motivation, and use cases
>           to IESG (Informational)
> Jan 10 - SIP Common Log Format specification
>           WGLC
> Feb 10 - SIP Common Log Format specification
>           to IESG (PS)
> 
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637

