IETF Logo Mail Archive

Re: [DNSOP] broken compressed names, was A draft about the Name:Wreck problem draft-dashevskyi-dnsrr-antipatterns

Christian Huitema <huitema@huitema.net> Thu, 15 April 2021 16:41 UTC

Return-Path: <huitema@huitema.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E1FE3A2669 for <dnsop@ietfa.amsl.com>; Thu, 15 Apr 2021 09:41:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
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 0KgmjssiGSZi for <dnsop@ietfa.amsl.com>; Thu, 15 Apr 2021 09:41:14 -0700 (PDT)
Received: from mx36-out20.antispamcloud.com (mx36-out20.antispamcloud.com [209.126.121.68]) (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 D5CCB3A2668 for <dnsop@ietf.org>; Thu, 15 Apr 2021 09:41:14 -0700 (PDT)
Received: from xse472.mail2web.com ([66.113.197.218] helo=xse.mail2web.com) by mx136.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1lX53A-0009cJ-D3 for dnsop@ietf.org; Thu, 15 Apr 2021 18:41:06 +0200
Received: from xsmtp21.mail2web.com (unknown [10.100.68.60]) by xse.mail2web.com (Postfix) with ESMTPS id 4FLlTS35zJz9jw for <dnsop@ietf.org>; Thu, 15 Apr 2021 09:41:00 -0700 (PDT)
Received: from [10.5.2.12] (helo=xmail02.myhosting.com) by xsmtp21.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1lX536-0007B0-8x for dnsop@ietf.org; Thu, 15 Apr 2021 09:41:00 -0700
Received: (qmail 20662 invoked from network); 15 Apr 2021 16:40:59 -0000
Received: from unknown (HELO [192.168.1.52]) (Authenticated-user:_huitema@huitema.net@[88.141.82.217]) (envelope-sender <huitema@huitema.net>) by xmail02.myhosting.com (qmail-ldap-1.03) with ESMTPA for <dnsop@ietf.org>; 15 Apr 2021 16:40:59 -0000
To: John R Levine <johnl@taugh.com>
Cc: dnsop@ietf.org
References: <20210414133641.A18B572E0509@ary.qy> <59df7967-2fef-371a-4d34-4c8efec74ca0@dotat.at> <628E22EC-3395-45AB-9FD8-2405A92682BA@isc.org> <49f57263-c68c-eb2a-a7b7-7b3028dacbc8@huitema.net> <2fd24a58-b0b4-cd10-816-e94d586d8c6@taugh.com>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <12b7b654-aef9-eb74-1a73-2dc75510abe0@huitema.net>
Date: Thu, 15 Apr 2021 18:40:56 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.9.1
MIME-Version: 1.0
In-Reply-To: <2fd24a58-b0b4-cd10-816-e94d586d8c6@taugh.com>
Content-Type: multipart/alternative; boundary="------------24E6F7291DA589941049EB69"
Content-Language: en-US
X-Originating-IP: 66.113.197.218
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.197.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.197.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT9WLQux0N3HQm8ltz8rnu+BPUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5zUgvzNCu/tqNXO2HgXp/PwfYzfQXcfqmra3dmoHS4ygv0b VEWbTgt1aNXCHd5xQBpWuRWrkPihq53YqAd1ENNqBHtNXu1E6L4+KyOXc4QYanQOD0r6/AaHZiEt dTMtMlia0Lmg/jgHfCNZd+W+PXf65y6ZhH6ZKeWOYyqjbrQ8Qyue9TLOhN8AYRsvkjfngQDjpf2k SyK8Bj8ZxpWAOKEIzDkBvlIN1pUDU5DU5DggD98cjIN3reG9z0FKKQ5m2Qpw7sOVVcM1Xk+Tdz6g /UMvfWqyN3veeFIMJz/vumcqAwMU9kjfE7EFo+kP5riIEUmxU01QhuxnshSbl6nxbLZ35/xY0uvo WBEOfzq3RG28wI7w4vcwqZanLHsZM8r4s5ZjlHoGly8aneNxj+pRyx6DAzHPcWsnfqGSaNoXhWPo OpFVgpT1b21uZVckGp0ccOZtuBWXiK6eoWgQZnNLL6SbpUc7peFeo3eDQNYbhOKhzzgqmaDn5SlD Y9mmtv6e91aWBLor1oCWetcUjeG94V2X+T+fZOoQ9zEcN1Sfon8ia6TeVLW3pB0Q/PTyowo5Aft4 B3oS6YdJ/O9moQNrGaZWCFXoGKtafvOtcW/mP16byrL/nwvREHuP3/Ps3A4Pt7hRyBl07OVp2D/S 9ogT8aIX6abOyKlLsxs8P4CT3FEuG06VfYoMUyMd5pUpSAuCSZCC1AI9a3irbifzymzQYX+PLC7f Py7Itw/zs7Z3LcqcKGfSqO0M0QaiPAAoj/viqoSKuZkMyFBGaEBYeh6pTEjUPbKOoHt56ZZHlZDE 6E10636m+UeFXprlCOm3BAEbJtAT1BYHStA0OogdNtRxnRSLF+XCKxIG9XMEgRDdaWpvCv+zESlk TxdSCNcDfRohcehWBb39uS1TjWG2Inx+Ts2QNOYPIz4ynMa7pZQ4hi/HGtuWeHzx9sLaQmDwvYQn 76e9NXttZBkk6PeFqH6So31P
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/_SR1OLi2JKK2DTHXuTRrRxumXYg>
Subject: Re: [DNSOP] broken compressed names, was A draft about the Name:Wreck problem draft-dashevskyi-dnsrr-antipatterns
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 15 Apr 2021 16:41:17 -0000

On 4/15/2021 5:39 PM, John R Levine wrote:

> On Thu, 15 Apr 2021, Christian Huitema wrote:
>>> Adding test vectors would help, especially broken vectors.
>>
>> +1. That would be a pretty good way for the IETF to help clean the 
>> mess. That, and maybe a DNS site that would serve the test vectors.
>
> In this case I think it's a reasonable idea but I echo jck's concern 
> that test vectors can turn into de-facto standards, particularly when 
> the tests and the text turn out not to exactly match.

A test server could easily have a fuzz option...

>
> On the other hand, is it valid for a DNS compression pointer to point 
> forward in the message?  Why or why not? 

I had to implement a packet parser a few years ago, and I rather 
naturally added a test that the pointers had to be backward. Not doing 
that looked like inviting trouble. I tested that on a fair number of 
root server traces and never found an issue. So I tend to think that's a 
fairly safe test.

-- Christian Huitema

v2.23.0 | Report a Bug | By Email