Re: [dnsext] alternatives to the proposed NEGATIVE pseudo-RR

"George Barwood" <george.barwood@blueyonder.co.uk> Sun, 28 September 2008 09:11 UTC

Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-dnsext-archive@core3.amsl.com
Delivered-To: ietfarch-dnsext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4ADC33A6916; Sun, 28 Sep 2008 02:11:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.701
X-Spam-Level: ***
X-Spam-Status: No, score=3.701 tagged_above=-999 required=5 tests=[AWL=-1.600, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_EQ_BLUEYON=1.4, HELO_MISMATCH_UK=1.749, J_CHICKENPOX_31=0.6, RDNS_NONE=0.1, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y8HuSPxJnDuY; Sun, 28 Sep 2008 02:11:15 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 544DC3A68AD; Sun, 28 Sep 2008 02:11:15 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1KjsAa-0001H6-O3 for namedroppers-data@psg.com; Sun, 28 Sep 2008 09:02:24 +0000
Received: from [195.188.213.7] (helo=smtp-out4.blueyonder.co.uk) by psg.com with esmtp (Exim 4.69 (FreeBSD)) (envelope-from <george.barwood@blueyonder.co.uk>) id 1KjsAW-0001GU-7b for namedroppers@ops.ietf.org; Sun, 28 Sep 2008 09:02:22 +0000
Received: from [172.23.170.144] (helo=anti-virus03-07) by smtp-out4.blueyonder.co.uk with smtp (Exim 4.52) id 1Kjs9z-0002xU-N5; Sun, 28 Sep 2008 10:01:47 +0100
Received: from [82.46.70.191] (helo=GeorgeLaptop) by asmtp-out5.blueyonder.co.uk with esmtpa (Exim 4.52) id 1Kjs9x-0001dI-7E; Sun, 28 Sep 2008 10:01:45 +0100
Message-ID: <216C320EE3074B51839095A95CDF7DA4@localhost>
From: George Barwood <george.barwood@blueyonder.co.uk>
To: Paul Vixie <vixie@isc.org>
Cc: Jim Reid <jim@rfc1035.com>, Olaf Kolkman <olaf@NLnetLabs.nl>, Stuart Cheshire <cheshire@apple.com>, Wouter Wijngaards <wouter@NLnetLabs.nl>, IETF DNSEXT WG <namedroppers@ops.ietf.org>, ajs@commandprompt.com
References: <200809110139.m8B1dtlX027081@drugs.dv.isc.org> <8D173E90-B53A-40C6-8A62-C78AEEBF22E3@apple.com> <48CA2183.4070803@nlnetlabs.nl> <B1055076-F36C-4A2F-98D9-265EAC322A94@apple.com> <72AED321-0A3D-4829-85CC-B909FB43F57A@NLnetLabs.nl> <DB5BE76E-84BD-4FEC-8964-C22B72C28A5A@rfc1035.com> <F8B1FBB2C3D64188B4C29D9E71E0DE69@localhost> <39068.1222344665@nsa.vix.com>
Subject: Re: [dnsext] alternatives to the proposed NEGATIVE pseudo-RR
Date: Sun, 28 Sep 2008 10:01:41 +0100
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>

----- Original Message ----- 
From: "Paul Vixie" <vixie@isc.org>
To: "George Barwood" <george.barwood@blueyonder.co.uk>
Cc: "Jim Reid" <jim@rfc1035.com>; "Olaf Kolkman" <olaf@NLnetLabs.nl>; 
"Stuart Cheshire" <cheshire@apple.com>; "Wouter Wijngaards" 
<wouter@NLnetLabs.nl>; "IETF DNSEXT WG" <namedroppers@ops.ietf.org>; 
<ajs@commandprompt.com>
Sent: Thursday, September 25, 2008 1:11 PM
Subject: Re: [dnsext] alternatives to the proposed NEGATIVE pseudo-RR


>> Has defining a class been considered?
> this isn't what classes are for, and it isn't how classes work, so, no.

The standard doesn't state the purpose of classes, it just enumerates them.

mRDNS is already using class for another purpose.

>> This seems cleaner to me than using a Type.
>
> rdata format is class independent.  rdlen=0 would be a protocol violation.

A and AAAA are specific to IN, so may have other formats in other classes 
surely?

Still,  class seems dead for practical purposes, so I concede that reviving 
it is probably not a good idea.

> further, the NSEC format is actually much more compact for this purpose.
> (the responder in stuart's case doesn't know what rrtypes the initiator
> may be contemplating, so it's nec'y to enumerate the full set and 
> illuminate
> those present/absent.) 



--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>