Re: [sip-clf] International Oops in sipclf Problem Statement

Burger Eric <eburger@alum.mit.edu> Thu, 19 January 2012 01:08 UTC

Return-Path: <prvs=53658f5002=eburger@alum.mit.edu>
X-Original-To: sip-clf@ietfa.amsl.com
Delivered-To: sip-clf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FEC511E80F9 for <sip-clf@ietfa.amsl.com>; Wed, 18 Jan 2012 17:08:11 -0800 (PST)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fUQcmsHxbkYY for <sip-clf@ietfa.amsl.com>; Wed, 18 Jan 2012 17:08:11 -0800 (PST)
Received: from alum-mailsec-scanner-6.mit.edu (ALUM-MAILSEC-SCANNER-6.MIT.EDU [18.7.68.18]) by ietfa.amsl.com (Postfix) with ESMTP id D18A611E80F8 for <sip-clf@ietf.org>; Wed, 18 Jan 2012 17:08:10 -0800 (PST)
X-AuditID: 12074412-b7f1c6d00000092d-4f-4f176cfaed0b
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) by alum-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id B1.3B.02349.AFC671F4; Wed, 18 Jan 2012 20:08:10 -0500 (EST)
Received: from [192.168.15.184] (ip68-100-199-8.dc.dc.cox.net [68.100.199.8]) (authenticated bits=0) (User authenticated as eburger@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id q0J188ew024624 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 18 Jan 2012 20:08:09 -0500
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Burger Eric <eburger@alum.mit.edu>
In-Reply-To: <212E7733-3FF6-47D4-A3E3-65471F677A25@standardstrack.com>
Date: Wed, 18 Jan 2012 20:08:08 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D699B6CD-C257-417F-B6C4-F5C54DB2A7B4@alum.mit.edu>
References: <212E7733-3FF6-47D4-A3E3-65471F677A25@standardstrack.com>
To: "sip-clf@ietf.org Mailing" <sip-clf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrIIsWRmVeSWpSXmKPExsUixO6iqPsrR9zf4Nd1IYstN9+yWxzb08/s wOSxZMlPJo+5e14wBzBFcdskJZaUBWem5+nbJXBnTJp4gr3gLHPF1q6ZTA2Mr5m6GDk5JARM JI4/PcEKYYtJXLi3nq2LkYtDSOAyo8T8ln/sEM5RJonZ1w+zgVQJC1hLzNv1lQXE5hUwlFi6 qZ0dxGYW0JK48e8l2FQ2AQ2JZ53bwWxOATeJnmtvGLsYOThYBFQlfm8pgSl/0f2CFcLWlli2 8DUzxEh7icmzuhlBbCEBV4ll9zaDrRIBWnX41VKwMRICshJNyzImMArMQnLELCRHzEIydQEj 8ypGucSc0lzd3MTMnOLUZN3i5MS8vNQiXTO93MwSvdSU0k2MkEAV2sG4/qTcIUYBDkYlHt4I EXF/IdbEsuLK3EOMkhxMSqK8h7KBQnxJ+SmVGYnFGfFFpTmpxYcYJTiYlUR4d5oA5XhTEiur UovyYVLSHCxK4rw/F6v7CQmkJ5akZqemFqQWwWRlODiUJHjtgBEpJFiUmp5akZaZU4KQZuLg BBFcIBt4gDYkgxTyFhck5hZnpkMUnWJUlBLnbQRJCIAkMkrz4AbAUsorRnGgf4R5t4EczwNM R3Ddr4AGMwEN9mgSAxlckoiQkmpgXKPikeWhtXb+hsqmjXULd3WlftrxQXhmhXiIpq+yyHRZ 7j0qwRy+D7NW5/Rz8DXNnmux3isnS1xzWlvC/V7xxYx3RHztN3/JtK25KtW21jVo3ZQnKQdE 5kR8v6PyOvjzAukP8Q3nphWwiVxRsOyz4gnsnTHFeIZzAfec/olOvis+9hkXFp1RYinOSDTU Yi4qTgQAqgkK2QQDAAA=
Cc: Saint-Andre Peter <stpeter@stpeter.im>
Subject: Re: [sip-clf] International Oops in sipclf Problem Statement
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2012 01:08:11 -0000

The current text says SIPCLF fields are ASCII.  However, as we know, SIP fields are UTF-8.  We propose changing all instances of ASCII in the document with UTF-8. Same for the sipclf-format document.  This is an awesome catch by Peter Saint-Andre.

Our guess is that most of you read octets and write octets.  Rendering programs will not quite work if an extended UTF-8 character pops up, but that should be easy to fix.

Anyone disagree?