IETF Logo Mail Archive

Re: [DNSOP] [Ext] Lameness terminology

"Paul Hoffman" <paul.hoffman@vpnc.org> Fri, 04 May 2018 15:53 UTC

Return-Path: <paul.hoffman@vpnc.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 B922412D870 for <dnsop@ietfa.amsl.com>; Fri, 4 May 2018 08:53:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 CEgo97e3UP0u for <dnsop@ietfa.amsl.com>; Fri, 4 May 2018 08:53:41 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 8016812D7EC for <dnsop@ietf.org>; Fri, 4 May 2018 08:53:41 -0700 (PDT)
Received: from [10.32.60.173] (50-1-51-141.dsl.dynamic.fusionbroadband.com [50.1.51.141]) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id w44FqUkt032540 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 4 May 2018 08:52:31 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-51-141.dsl.dynamic.fusionbroadband.com [50.1.51.141] claimed to be [10.32.60.173]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: Edward Lewis <edward.lewis@icann.org>
Cc: Amreesh Phokeer <amreesh.phokeer@gmail.com>, dnsop@ietf.org
Date: Fri, 04 May 2018 08:53:17 -0700
X-Mailer: MailMate (1.11.2r5479)
Message-ID: <1CEA7875-C86F-4EA6-B5F1-17B477B2EE0C@vpnc.org>
In-Reply-To: <547510AF-5D0E-42A6-B04F-DF0014648EDE@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> <CACRw5znmX559DpXv5Copn9u6YN0mUgrk9q5QT=bpUbYArU8VzA@mail.gmail.com> <81f139a9-b806-b505-946c-4c1880974073@time-travellers.org> <547510AF-5D0E-42A6-B04F-DF0014648EDE@icann.org>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/mMN_r7yyuDeLsbZH6w60dcUyceA>
Subject: Re: [DNSOP] [Ext] Lameness terminology
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: Fri, 04 May 2018 15:53:43 -0000

On 4 May 2018, at 8:16, Edward Lewis wrote:

> FWIW, if one is to cite a definition of lame, I'd use "Common DNS 
> Operational and Configuration Errors", February 1996, aka RFC 1912.

Yep, that's the one we already have. I think it's worthwhile to also add 
the wider definition that Amreesh pointed out in RFC 1713.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email