Re: [sip-clf] Defining Pros and Cons of ASCII/IPFIX

Hadriel Kaplan <HKaplan@acmepacket.com> Wed, 27 October 2010 17:27 UTC

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 B32B03A6A33 for <sip-clf@core3.amsl.com>; Wed, 27 Oct 2010 10:27:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.47
X-Spam-Level:
X-Spam-Status: No, score=-2.47 tagged_above=-999 required=5 tests=[AWL=0.129, 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 hYI5K4HndRkC for <sip-clf@core3.amsl.com>; Wed, 27 Oct 2010 10:27:03 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 9C6053A69B0 for <sip-clf@ietf.org>; Wed, 27 Oct 2010 10:27:03 -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.2.254.0; Wed, 27 Oct 2010 13:28:53 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Wed, 27 Oct 2010 13:28:32 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Peter Musgrave <peter.musgrave@magorcorp.com>
Date: Wed, 27 Oct 2010 13:28:15 -0400
Thread-Topic: [sip-clf] Defining Pros and Cons of ASCII/IPFIX
Thread-Index: Act1/F/mzUj8TuSkRyGI1yVxtexhWw==
Message-ID: <D2591488-77F2-423D-B2AE-187E627D4489@acmepacket.com>
References: <AANLkTin3+_+-ARa29=o4V8-Pp-TS0Xc5S04CYhy0sT=r@mail.gmail.com>
In-Reply-To: <AANLkTin3+_+-ARa29=o4V8-Pp-TS0Xc5S04CYhy0sT=r@mail.gmail.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: List SIP-CLF Mailing <sip-clf@ietf.org>
Subject: Re: [sip-clf] Defining Pros and Cons of ASCII/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: Wed, 27 Oct 2010 17:27:04 -0000

At a recent conference I asked a SIP monitoring vendor which format they thought we should specify, and surprisingly they said "do both".  I asked them why, and they said there was a market for both ascii and binary formats - that monitoring systems would prefer binary ones, but that humans prefer ascii style ones; and that in the Enterprise market ascii was more dominant, while in the SP market binary was more dominant.  They said we wouldn't be able to choose just one in the IETF - because whichever we picked there'd still be a market for the other and that market would continue the status-quo of proprietary formats or settle on some de-facto one.

In thinking about this more I think I agree with them.  It'd be like us picking a Registrar database access protocol as well as the fields in it - we could specify SQL or DIAMETER, but in some markets it'll be one not the other no matter which one we choose. (or it'll be Active Directory, etc.)

-hadriel

On Oct 27, 2010, at 11:23 AM, Peter Musgrave wrote:

> Hi all, 
> 
> As co-chair I am looking for a way to make a determination about how to meet the groups decision to move forward with just one format in a WG which has good support for two formats. 
> 
> In my (personal) opinion I think the objective is to develop something that will be widely implemented. I would like to solicit input from a larger audience - but first I think we need to frame the pros and cons.
> 
> I would like to suggest the following:
> 
> 1) Use the list and the Beijing meeting to come to a consensus on the pros and cons of each and the applications which may favour one format vs another. 
> 
> 2) Place these pros/cons on the WG Wiki [I can act as editor]
> 
> 3) Solicit input from SIP Implementors - referring them to the WG WIki
> - use the Columbia sip-implementors, sipforum list and SIPT27
> 
> 4) Review the feedback and try to come to a conclusion on the list (or failing that, in Prague at IETF80)
> 
> I will be at SIPIT27 - so I can raise awareness of this discussion in that community. 
> 
> How do people feel about this approach?
> 
> I welcome any other/additional ways to resolve this issue. 
> 
> Regards, 
> 
> Peter Musgrave
> co-chair
> 
> 
> 
> <ATT00001..c>