IETF Logo Mail Archive

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

Paul Hoffman <paul.hoffman@vpnc.org> Mon, 01 September 2014 23:06 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 433C81A1F20 for <dnsop@ietfa.amsl.com>; Mon, 1 Sep 2014 16:06:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.647
X-Spam-Level:
X-Spam-Status: No, score=-3.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 X0Ve5EuchyqP for <dnsop@ietfa.amsl.com>; Mon, 1 Sep 2014 16:06:39 -0700 (PDT)
Received: from proper.com (Hoffman.Proper.COM [207.182.41.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CDBF1A0B79 for <dnsop@ietf.org>; Mon, 1 Sep 2014 16:06:39 -0700 (PDT)
Received: from [10.20.30.90] (142-254-17-22.dsl.dynamic.fusionbroadband.com [142.254.17.22]) (authenticated bits=0) by proper.com (8.14.9/8.14.7) with ESMTP id s81N6aXm064027 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 1 Sep 2014 16:06:38 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: proper.com: Host 142-254-17-22.dsl.dynamic.fusionbroadband.com [142.254.17.22] claimed to be [10.20.30.90]
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <B4ACD73A-25EF-4063-81D4-DCFE6DB78AB1@vpnc.org>
Date: Mon, 01 Sep 2014 16:06:35 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E87141BE-71E6-4F6F-9506-257A9FA681B7@vpnc.org>
References: <B4ACD73A-25EF-4063-81D4-DCFE6DB78AB1@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/8GEAonM7BKoMk1MHkHTS7r9ERkQ
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: Mon, 01 Sep 2014 23:06:43 -0000

I have revised the draft to add some name types to make domain names with just a few non-ASCII characters easier to read. However, I would really like to hear from application developers who intend to represent DNS messages in JSON whether or not the new name forms are useful and, if not, what they would want to use in their applications.

--Paul Hoffman

> A new version of I-D, draft-hoffman-dns-in-json-01.txt
> has been successfully submitted by Paul Hoffman and posted to the
> IETF repository.
> 
> Name:		draft-hoffman-dns-in-json
> Revision:	01
> Title:		Representing DNS Messages in JSON
> Document date:	2014-09-01
> Group:		Individual Submission
> Pages:		18
> URL:            http://www.ietf.org/internet-drafts/draft-hoffman-dns-in-json-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-hoffman-dns-in-json/
> Htmlized:       http://tools.ietf.org/html/draft-hoffman-dns-in-json-01
> Diff:           http://www.ietf.org/rfcdiff?url2=draft-hoffman-dns-in-json-01

v2.29.0 | Report a Bug | By Email | System Status