Re: [DNSOP] [Ext] Lameness terminology (was: Status of draft-ietf-dnsop-terminology-bis)

David Huberman <david.huberman@icann.org> Thu, 03 May 2018 15:05 UTC

Return-Path: <david.huberman@icann.org>
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 4E47812778D for <dnsop@ietfa.amsl.com>; Thu, 3 May 2018 08:05:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 fPfh3d60p6Py for <dnsop@ietfa.amsl.com>; Thu, 3 May 2018 08:05:20 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-1.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E63F9127076 for <dnsop@ietf.org>; Thu, 3 May 2018 08:05:20 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Thu, 3 May 2018 08:05:18 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1178.000; Thu, 3 May 2018 08:05:18 -0700
From: David Huberman <david.huberman@icann.org>
To: Edward Lewis <edward.lewis@icann.org>, Shane Kerr <shane@time-travellers.org>, "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: [DNSOP] [Ext] Lameness terminology (was: Status of draft-ietf-dnsop-terminology-bis)
Thread-Index: AQHT4k6AbZ1gXO8t/ECjZikPlv0iNqQeTfkA
Date: Thu, 03 May 2018 15:05:18 +0000
Message-ID: <0AA87D00-17F7-4D10-A72D-E4723C4A0642@icann.org>
References: <7C873271-A784-4594-91A3-48C697EEC613@vpnc.org> <b3ed96d7-26fb-3d97-118b-39e8f352a38c@time-travellers.org> <87F43055-5B0E-4551-BD8D-241D93F9039F@icann.org>
In-Reply-To: <87F43055-5B0E-4551-BD8D-241D93F9039F@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.47.234]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha256"; boundary="B_3608190318_1907393914"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/GGuYiJQ3sSp2F7DFijKHVqr1xgY>
Subject: Re: [DNSOP] [Ext] Lameness terminology (was: Status of draft-ietf-dnsop-terminology-bis)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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, 03 May 2018 15:05:22 -0000

Ed Lewis wrote:

> (Only if you like reading history:)
   
> The reason was a flaw in "certain old resolvers" that followed the "upwards referral" to the root that 
> the "predominate server code of the time" had decided to use for lameness.  The result was a lot of 
> resolver stuck in an infinite loop, hitting the root servers.  I.e., this was an operational issue.  The 
> solution was updating and redeploying the buggy code, not stamping out lame servers (which was 
> the goal of the task).  FWIW, the "upwards referrals" were discontinued when it became apparent 
> they were being used in noticeable amplification attacks.
  
I sat on the front lines of ARIN’s war against lame delegations for the entire war.  We spent quite a few
years testing delegations for our definition of lameness, and then notifying the listed tech-c and admin-c.
E-mail recipients would either ignore the email, not understand the email and move on to the next thing,
or would write-in or call-in and speak to either me or my co-worker Jon Worley. Very few lame delegations
were fixed, even among those who called-in or wrote-in for clarification.  rDNS worked for the user, and
they weren’t willing to change anything.

The war was unwinnable. 
    
/david