IETF Logo Mail Archive

Re: [dnsext] draft-bellis-dnsext-dnsproxy-00

Florian Weimer <fw@deneb.enyo.de> Tue, 04 November 2008 20:20 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 4AB0928C21A; Tue, 4 Nov 2008 12:20:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level:
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
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 LhVWgwHW00z5; Tue, 4 Nov 2008 12:20:15 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 535763A6B0C; Tue, 4 Nov 2008 12:20:15 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1KxSIL-0003nW-2S for namedroppers-data@psg.com; Tue, 04 Nov 2008 20:14:33 +0000
Received: from [2001:14b0:202:1::a7] (helo=mail.enyo.de) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <fw@deneb.enyo.de>) id 1KxSIG-0003mv-9N for namedroppers@ops.ietf.org; Tue, 04 Nov 2008 20:14:30 +0000
Received: from deneb.vpn.enyo.de ([212.9.189.177] helo=deneb.enyo.de) by mail.enyo.de with esmtp id 1KxSI9-0004UM-U9; Tue, 04 Nov 2008 21:14:22 +0100
Received: from fw by deneb.enyo.de with local (Exim 4.69) (envelope-from <fw@deneb.enyo.de>) id 1KxSI9-0005Vc-Do; Tue, 04 Nov 2008 21:14:21 +0100
From: Florian Weimer <fw@deneb.enyo.de>
To: Ray.Bellis@nominet.org.uk
Cc: namedroppers@ops.ietf.org
Subject: Re: [dnsext] draft-bellis-dnsext-dnsproxy-00
References: <OF7E3816AF.C6D6EB41-ON802574F6.0076B6C3-802574F6.0077AF4E@nominet.org.uk>
Date: Tue, 04 Nov 2008 21:14:21 +0100
In-Reply-To: <OF7E3816AF.C6D6EB41-ON802574F6.0076B6C3-802574F6.0077AF4E@nominet.org.uk> (Ray Bellis's message of "Mon, 3 Nov 2008 21:47:17 +0000")
Message-ID: <87tzanw8o2.fsf@mid.deneb.enyo.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>

* Ray Bellis:

> Forward pointing ones certainly are:
>
> RFC1035, section 4.1.4: "In this scheme, an entire domain name or a list 
> of labels at the end of a domain name is replaced with a pointer to a 
> prior occurance of the same name"

I'm not sure if such strict reading is advisable.  From that quote,
it's not clear that compressing "ns1.example.com" as "ns1", followed
by a reference to the "example.com" in "www.example.com" is permitted.

>> Compression loops and compression references in places where actually
>> forbidden by the RFCs would be relevant examples, IMHO.
>
> Compression loops is a good one.  Can you provide an example or reference 
> to an illegal compression place?

Signer's name in an RRSIG, for instance.

> Interesting...  in my earlier research we were more concerned with missing 
> data, and never noticed extraneous data.  Is this a common occurrence?

I see it quite often, but I have no idea how much of that is accepted
by initiators.

--
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/>

v2.23.0 | Report a Bug | By Email