IETF Logo Mail Archive

Re: [DNSOP] A draft about the Name:Wreck problem draft-dashevskyi-dnsrr-antipatterns

John Levine <johnl@taugh.com> Wed, 14 April 2021 13:36 UTC

Return-Path: <johnl@iecc.com>
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 E7C4F3A091B for <dnsop@ietfa.amsl.com>; Wed, 14 Apr 2021 06:36:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level:
X-Spam-Status: No, score=-1.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=Gur4nk0m; dkim=pass (2048-bit key) header.d=taugh.com header.b=g8ds/sgA
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 iOdmyMSCZ1wR for <dnsop@ietfa.amsl.com>; Wed, 14 Apr 2021 06:36:45 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 334723A0918 for <dnsop@ietf.org>; Wed, 14 Apr 2021 06:36:44 -0700 (PDT)
Received: (qmail 77626 invoked from network); 14 Apr 2021 13:36:42 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=12f38.6076efea.k2104; bh=j20iH1yIYOS/XcFJMHisifgqZ7ColqsOl0HQbm7+rzE=; b=Gur4nk0mUOsFSRVDLeYrg9Z6WAUOHFNy0lcyw4y94NByF5nFvsd3l7K7iH257MYzUqlrhHmV1LmrkzQoJa+w7TTho24QwjHtzmYKID0lFSLI1PVX7WxrCtKB009FrBqk8sMW8CUCRiAed8UXfD6vGGmWIEgQDb+4BS/wx45U8j3tiHvXXrrwX+eWLH8R0aG27HRWNJTs0Ff8LRl6JVgdwYH+PTkFEf5lRGwEJcrgiP17+f28ysZk/MJ2NetCgYQc/k2p5Mugkv0t432y13fe+wXun0CUD9RHsR+D6fv2IxTzAdv4TvjnW3KiMAtN45oN78Io/SuJtaba06jHnNmPvQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=12f38.6076efea.k2104; bh=j20iH1yIYOS/XcFJMHisifgqZ7ColqsOl0HQbm7+rzE=; b=g8ds/sgAfqs6bL4B1rpLLbuTKw6B2KI3ttFgoasiIc1RQNvW7p4b8IsONXeLJ16GSol0taoR1t9Mcp1PNv7HeZ22I4UZqn8u2WPPTjrasJnVoCor1Ku+TPWb79YIJKXqorW5Gp4p3vWcG/0OEZZiX4ceHyf2CAV6GMwYtGW8CW0mNF3ZCvSIOIm7Z/E9/6VrBziODcUoTCyeYKuJWwKKBuSpitLXYLN0YxVVdxFDRkVtpY00Gy4WA++nBVpuBmkE0kAMeo4qNtt+afGVtGzhy219rFgnyoOTvh7RtlmWSe0G2RRjNoWWq0pS1jHeYdmVZgPNCaXb/eSaP904+4w9Zg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 14 Apr 2021 13:36:42 -0000
Received: by ary.qy (Postfix, from userid 501) id A18B572E0509; Wed, 14 Apr 2021 09:36:40 -0400 (EDT)
Date: Wed, 14 Apr 2021 09:36:40 -0400
Message-Id: <20210414133641.A18B572E0509@ary.qy>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <20210414124706.GC12570@nic.fr>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/C4vW3HsUl_V99Pv3EF9871ELS1g>
Subject: Re: [DNSOP] 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: Wed, 14 Apr 2021 13:36:51 -0000

It appears that Stephane Bortzmeyer  <bortzmeyer@nic.fr> said:
>On Wed, Apr 14, 2021 at 11:01:42AM +0200,
> Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote 
> a message of 10 lines which said:
>
>> The Name:Wreck compression pointer issue

I skimmed his very wordy paper and saw that all of the bugs he reported that affect software
I use were fixed a year ago.

We find that IoT stuff is crud.  This is not news and I don't think it's something that RFCs either caused or could fix.

On the other hand, all of the sloppy coding people use to handle compressed names is embarassing.


>Also
><https://www.scmagazine.com/home/security-news/vulnerabilities/namewreck-is-the-latest-collision-between-tcp-ip-and-the-standards-process/>
>talks about what IETF should do. (The article contains several errors
>about the RFC process.)
>
>> “I mean I don’t want to be the one telling the [Internet Engineering
>> Task Force] how to do their work. Things have worked for more than
>> 40 years on the internet because of the RFC systems,” he said. “But
>> indeed, I do believe that it’s time that we think of an
>> alternative.”
>

v2.23.0 | Report a Bug | By Email