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

Shane Kerr <shane@time-travellers.org> Mon, 23 April 2018 14:23 UTC

Return-Path: <shane@time-travellers.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 5AF54129C51 for <dnsop@ietfa.amsl.com>; Mon, 23 Apr 2018 07:23:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.434
X-Spam-Level: *
X-Spam-Status: No, score=1.434 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_SBL_CSS=3.335, SPF_PASS=-0.001] autolearn=no 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 TNYTbYjuyBwM for <dnsop@ietfa.amsl.com>; Mon, 23 Apr 2018 07:23:25 -0700 (PDT)
Received: from time-travellers.org (c.time-travellers.nl.eu.org [IPv6:2a02:2770::21a:4aff:fea3:eeaa]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A7A5126D74 for <dnsop@ietf.org>; Mon, 23 Apr 2018 07:23:25 -0700 (PDT)
Received: from [78.109.23.1] (helo=[127.0.0.1]) by time-travellers.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <shane@time-travellers.org>) id 1fAcOL-0005Rp-Ib for dnsop@ietf.org; Mon, 23 Apr 2018 14:24:29 +0000
To: dnsop@ietf.org
References: <7C873271-A784-4594-91A3-48C697EEC613@vpnc.org>
From: Shane Kerr <shane@time-travellers.org>
Message-ID: <b3ed96d7-26fb-3d97-118b-39e8f352a38c@time-travellers.org>
Date: Mon, 23 Apr 2018 14:23:00 +0000
MIME-Version: 1.0
In-Reply-To: <7C873271-A784-4594-91A3-48C697EEC613@vpnc.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/yls4_MCjrfC3ARPwonqIRvYA_Pg>
Subject: [DNSOP] 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: Mon, 23 Apr 2018 14:23:26 -0000

Hello everyone,

Paul Hoffman:
> We're still not done yet. I took a hiatus from finishing the list of
> definitions that people wanted more scrutiny on, but will start that
> again soon. I hope we'll be done with that list by mid-April and then be
> ready for WG last call.

I noticed that the latest version of the terminology draft includes lame
delegation.

I ask because my understanding is that there are several flavors of
lame delegation, at least informally. I believe Ed Lewis spent some
time thinking about this long ago when he was updating ARIN's lame
delegation processes.

IIRC the main distinction is between a single NS being lame and all NS
being lame. So you can have a lame server (a single NS) or a lame
delegation (all NS). There may be further details with lameness above
and below the zone cut, or lameness caused by A/AAAA lookups failing
on the NS or lameness caused by the servers not responding.

I don't know if this is documented anywhere so that it can be
referenced properly, sorry. I am happy to discuss further but I think
this basically covers all I know. I don't mind proposing text, but
probably someone (Ed maybe?) would be a better person.

Cheers,

--
Shane