IETF Logo Mail Archive

Re: [Json] JSON Log file encoding JSON-L

Carsten Bormann <cabo@tzi.org> Tue, 06 May 2014 20:42 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 180091A03D3 for <json@ietfa.amsl.com>; Tue, 6 May 2014 13:42:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level:
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VRkc33eLIo0u for <json@ietfa.amsl.com>; Tue, 6 May 2014 13:42:35 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id C449C1A03EE for <json@ietf.org>; Tue, 6 May 2014 13:42:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id s46KgPIs005141 for <json@ietf.org>; Tue, 6 May 2014 22:42:25 +0200 (CEST)
Received: from [192.168.217.145] (p54892947.dip0.t-ipconnect.de [84.137.41.71]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 39F041381; Tue, 6 May 2014 22:42:25 +0200 (CEST)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAMm+LwjB-51z4GoeC0riehmJg1HAddmLAyfMsVOCVM80i=RiMA@mail.gmail.com>
Date: Tue, 06 May 2014 22:42:23 +0200
X-Mao-Original-Outgoing-Id: 421101743.148251-9f2a9b633461b73751b7687820c49517
Content-Transfer-Encoding: quoted-printable
Message-Id: <B9D8B85D-EF2C-4B3A-90A4-873C714C06FA@tzi.org>
References: <CAMm+LwjB-51z4GoeC0riehmJg1HAddmLAyfMsVOCVM80i=RiMA@mail.gmail.com>
To: JSON WG <json@ietf.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/json/bjv0LS_EQuqxKkoj8mk2qpHXCPM
Subject: Re: [Json] JSON Log file encoding JSON-L
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 May 2014 20:42:37 -0000

> separated

There is some exciting technology for information separators that is documented in RFC 20, in particular in the penultimate paragraph of its section 5.2.
Transfers right to RFC 3629 without any problems, and works very well with unrestricted JSON texts.

Grüße, Carsten

PS.: Yes, I have briefly worked with Qunix/QNX in the early 1980s.

v2.23.0 | Report a Bug | By Email