Re: [dnsext] compression in UPDATE

Tony Finch <dot@dotat.at> Mon, 09 May 2011 18:50 UTC

Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF816E06C4 for <dnsext@ietfa.amsl.com>; Mon, 9 May 2011 11:50:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.725
X-Spam-Level:
X-Spam-Status: No, score=-4.725 tagged_above=-999 required=5 tests=[AWL=1.874, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rzVyp4RqNX8I for <dnsext@ietfa.amsl.com>; Mon, 9 May 2011 11:50:39 -0700 (PDT)
Received: from ppsw-52.csi.cam.ac.uk (ppsw-52.csi.cam.ac.uk [131.111.8.152]) by ietfa.amsl.com (Postfix) with ESMTP id E73FEE06BE for <dnsext@ietf.org>; Mon, 9 May 2011 11:50:37 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:36256) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:25) with esmtpa (EXTERNAL:fanf2) id 1QJVDZ-0000Tk-Di (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Mon, 09 May 2011 19:30:05 +0100
Received: from fanf2 (helo=localhost) by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1QJVDY-00008I-Md (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Mon, 09 May 2011 19:30:05 +0100
Date: Mon, 9 May 2011 19:30:04 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Paul Vixie <vixie@isc.org>
In-Reply-To: <46322.1304956246@nsa.vix.com>
Message-ID: <alpine.LSU.2.00.1105091921020.19348@hermes-2.csi.cam.ac.uk>
References: <46322.1304956246@nsa.vix.com>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: dnsext@ietf.org
Subject: Re: [dnsext] compression in UPDATE
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2011 18:50:42 -0000

Paul Vixie <vixie@isc.org> wrote:
>
> therefore my question: does any UPDATE initiator actually use compression?

BIND's nsupdate tool compresses owner names and names in the RDATA of RFC
1035 RR types. This is consistent with RFC 3597, which makes sense.

I don't think RFC 2136 needs to forbid compression; it just needs to say
that records (owner names and RDATA) are compared after they have been
decompressed and the RDLENGTH adjusted to match.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Rockall, Malin, Hebrides: South 5 to 7, occasionally gale 8 at first in
Rockall and Malin, veering west or northwest 4 or 5, then backing southwest 5
or 6 later. Rough or very rough. Occasional rain. Moderate or good,
occasionally poor.