Re: [DNSOP] New draft on representing DNS messages in JSON

Andreas Gustafsson <gson@araneus.fi> Sun, 07 September 2014 12:20 UTC

Return-Path: <gson@araneus.fi>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9D8E1A045E for <dnsop@ietfa.amsl.com>; Sun, 7 Sep 2014 05:20:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.664
X-Spam-Level:
X-Spam-Status: No, score=0.664 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] 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 i48U9MS4Ygj5 for <dnsop@ietfa.amsl.com>; Sun, 7 Sep 2014 05:20:04 -0700 (PDT)
Received: from gw03.mail.saunalahti.fi (gw03.mail.saunalahti.fi [195.197.172.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 276FC1A030A for <dnsop@ietf.org>; Sun, 7 Sep 2014 05:20:03 -0700 (PDT)
Received: from guava.gson.org (a91-153-56-171.elisa-laajakaista.fi [91.153.56.171]) by gw03.mail.saunalahti.fi (Postfix) with ESMTP id BCA65200F1; Sun, 7 Sep 2014 15:19:56 +0300 (EEST)
Received: by guava.gson.org (Postfix, from userid 101) id 8A2D075E2E; Sun, 7 Sep 2014 15:19:55 +0300 (EEST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <21516.19819.479645.991726@guava.gson.org>
Date: Sun, 07 Sep 2014 15:19:55 +0300
To: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <61891E93-8C39-4759-86B5-0DA42BF277DB@vpnc.org>
References: <B4ACD73A-25EF-4063-81D4-DCFE6DB78AB1@vpnc.org> <E87141BE-71E6-4F6F-9506-257A9FA681B7@vpnc.org> <21515.5128.207638.132193@guava.gson.org> <61891E93-8C39-4759-86B5-0DA42BF277DB@vpnc.org>
X-Mailer: VM 8.0.14 under 21.4.1 (i386--netbsdelf)
From: Andreas Gustafsson <gson@araneus.fi>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/tBWH-RU4kF8D1QoBZDueTtLs6rk
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] New draft on representing DNS messages in JSON
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Sep 2014 12:20:05 -0000

Paul Hoffman wrote:
> Or, we could use an actual standards-track RFC: 4343.

That's a good find.  Works for me.

> I take it no one remembers this one...

I must have mentally filed it under "Case Insensitivity" and
forgotten that it also discussed this issue.
-- 
Andreas Gustafsson, gson@araneus.fi