[DNSOP] Updated draft-hoffman-dns-in-json

Paul Hoffman <paul.hoffman@icann.org> Wed, 21 September 2016 20:47 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 4B79412C042; Wed, 21 Sep 2016 13:47:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.517
X-Spam-Status: No, score=-6.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id EnZ5Rm35JmoX; Wed, 21 Sep 2016 13:47:46 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4325912C035; Wed, 21 Sep 2016 13:47:46 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org ( by PMBX112-W1-CA-2.pexch112.icann.org ( with Microsoft SMTP Server (TLS) id 15.0.1178.4; Wed, 21 Sep 2016 13:47:44 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([]) with mapi id 15.00.1178.000; Wed, 21 Sep 2016 13:47:44 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: dnsop <dnsop@ietf.org>
Thread-Topic: Updated draft-hoffman-dns-in-json
Thread-Index: AQHSFElmmMfeHr2L6Uassd+ZIB78Eg==
Date: Wed, 21 Sep 2016 20:47:43 +0000
Message-ID: <F07708D9-528D-436A-B300-CD55F22DDE00@icann.org>
References: <147449058806.14589.3836574543576167857.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0D5E19F48A8CC142BEA074A6F8F44C9E@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/51Q8o0562eGPVm0XT1E2yM2A5Lw>
Cc: "dnsoverhttp@ietf.org" <dnsoverhttp@ietf.org>
Subject: [DNSOP] Updated draft-hoffman-dns-in-json
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 21 Sep 2016 20:47:47 -0000

Greetings. Based on the recent discussion on the DNSOP mailing list (noting again that this is not a WG work item!), I have updated draft-hoffman-dns-in-json. I still plan to send this to the ISE for Experimental in about two weeks, and am happy to make more changes before then (or after, based on the ISE review).

--Paul Hoffman

> A new version of I-D, draft-hoffman-dns-in-json-08.txt
> has been successfully submitted by Paul Hoffman and posted to the
> IETF repository.
> Name:		draft-hoffman-dns-in-json
> Revision:	08
> Title:		Representing DNS Messages in JSON
> Document date:	2016-09-21
> Group:		Individual Submission
> Pages:		13
> URL:            https://www.ietf.org/internet-drafts/draft-hoffman-dns-in-json-08.txt
> Status:         https://datatracker.ietf.org/doc/draft-hoffman-dns-in-json/
> Htmlized:       https://tools.ietf.org/html/draft-hoffman-dns-in-json-08
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-hoffman-dns-in-json-08
> Abstract:
>   Some applications use DNS messages, or parts of DNS messages, as
>   data.  For example, a system that captures DNS queries and responses
>   might want to be able to easily search those without having to decode
>   the messages each time.  Another example is a system that puts
>   together DNS queries and responses from message parts.  This document
>   describes a standardized format for DNS message data in JSON.