Re: [DNSOP] moving forward on special use names

Ted Lemon <> Fri, 16 September 2016 22:15 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7B9D712B35D for <>; Fri, 16 Sep 2016 15:15:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2Ovh4QRBQKGO for <>; Fri, 16 Sep 2016 15:15:58 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4010:c07::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9613D12B35A for <>; Fri, 16 Sep 2016 15:15:57 -0700 (PDT)
Received: by with SMTP id g62so71109515lfe.3 for <>; Fri, 16 Sep 2016 15:15:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6vdCq4MElHm1ceIkMCoI7WLVEZDW+gBMp1TrXx4l83c=; b=MW1XudTWbKAiISC7e4v+hzffB7ioAg2f4MWMYCeDFZlwkXljI1RWOnjpEzvIIa6KYy aH4i5NK6EPg3rvxO4Hxv/+MIEwyKwYGSLmTnHtAyxWiCABYW/bHlhJsOKr1HYq2kz7S5 xgJsf8luibi87+rT654JfRRNw2e2y6om9IbxTQbBiE1QUR6neP7GNcSuuClHggrJvoNJ 8hj8BLI2Nf7DrRw3mqFzTTKwvpriGlivZrpgeqzuq+heQrhhVJfI3v4qcBmuKuOO5V36 O8EmcGjY5C8Ft/X6rE6Y92jCcDoA1668bjdfFM2n2XSCN15oyJPrW9a7vbqTN4z7948K SLWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6vdCq4MElHm1ceIkMCoI7WLVEZDW+gBMp1TrXx4l83c=; b=OsWGWjCnKhXbHOQeQK8yNgZCwIfV0kMSF4DS1eXCMQRq/1XeV20Tm+F2g6XjE9hp1o kxzMabYeOKF5w19dnt93WfxmF0Fpj+nGbFF9i5DXq8tEnBHGR4NmadHsSUsj4nu1yvrI mS3xYKQ68ChfmsD/Co2CQOHILslcP8aX4dbLcVECFh2suZgC8yErS7oNzuv5vVAUW3Zx DM8jBaVlx9zFzc5b8SKBfC7az2wi3DTVD9yGIYBcMPkY2WWe5M3nNeF33RPJNt2TPO4r zb0P5DUoIbV3ZooLZGw3kSaDVZZ6JFIazjtPptmhXZ0jZvl8TGw3OOylwN6lfXHRIUuK VKWA==
X-Gm-Message-State: AE9vXwPfBIZ9W3isBTLIJJEfIpDKQX0AKEL5f+/38hsRL5b0ZkFPgQDreNcYIhktcIO007Se0bp9JblMWFADOQ==
X-Received: by with SMTP id 91mr3266679lja.75.1474064155760; Fri, 16 Sep 2016 15:15:55 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Fri, 16 Sep 2016 15:15:14 -0700 (PDT)
In-Reply-To: <alpine.OSX.2.11.1609161808300.92010@ary.lan>
References: <> <20160916181356.70566.qmail@ary.lan> <> <> <> <alpine.OSX.2.11.1609161757100.92010@ary.lan> <> <alpine.OSX.2.11.1609161808300.92010@ary.lan>
From: Ted Lemon <>
Date: Fri, 16 Sep 2016 18:15:14 -0400
Message-ID: <>
To: John R Levine <>
Content-Type: multipart/alternative; boundary=001a1142bf2661632b053ca74e68
Archived-At: <>
Cc: dnsop WG <>
Subject: Re: [DNSOP] moving forward on special use names
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 16 Sep 2016 22:15:59 -0000

   o  When a top-level name is used as a means either of marking the
      rest of a Domain Name for resolution using a protocol other than
      DNS, or is used for resolution of names with no global meaning,
      not all software that processes such names will understand the
      names' special meanings.  Consequently, any such use results in
      queries for those names being sent to authoritative servers.

On Fri, Sep 16, 2016 at 6:10 PM, John R Levine <> wrote:

> Section 4.1.2 of the tldr document actually says almost exactly what you
>> said in your four-pronged strategy, but without the pejorative bit.
> I just looked at it again, and don't see anything about the toxic waste
> names.  Since they're the ones that are hard, I really think we need to
> call them out.  Feel free to come up with a different metaphor if you don't
> like the one about a part of the DNS space that's too polluted to use.
> R's,
> John