IETF Logo Mail Archive

Re: [DNSOP] DNS Terminology: Glue

Phillip Hallam-Baker <phill@hallambaker.com> Thu, 12 March 2015 14:47 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 564951A1BE6 for <dnsop@ietfa.amsl.com>; Thu, 12 Mar 2015 07:47:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 N_ZBqtn641fN for <dnsop@ietfa.amsl.com>; Thu, 12 Mar 2015 07:47:50 -0700 (PDT)
Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 776681A6EF0 for <dnsop@ietf.org>; Thu, 12 Mar 2015 07:47:49 -0700 (PDT)
Received: by labgm9 with SMTP id gm9so16293179lab.13 for <dnsop@ietf.org>; Thu, 12 Mar 2015 07:47:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=yKFU6i6sk3nmce0e22PSC3qYq/khJnWckcBjlDOKCaE=; b=eSb4RsSwKkmfdYYRSOKdMSQeDdWdD5aq07Jx8kRJy1DcLCIALZrmn+N3h+fRgUz9CJ 1rrXT3ZZFKeA7XDHN0BHb9LONpT7hsr64w5SgKxp3MZn74uz+4U3teVJsEu/FtneFV0J 5YZLzIuYhECGy/a4Bn4luZSO4VI+HuAz4lI32guFSmTD7CCyPHJzSkudn7z/8mzfVtdB SpRC/Get2qHj2C353JH2touD+WbCH3ENM+dYeH+BG3mhyRSSXweK+I+JhkVpxL6Isoap 7so5vu5t3zGJ6b82iG8h65/jMc+N+goVJkQDnCmOz9kd2xFbPrG9e+reGZwtt6+hNvgA e5WQ==
MIME-Version: 1.0
X-Received: by 10.112.161.66 with SMTP id xq2mr39394488lbb.103.1426171668026; Thu, 12 Mar 2015 07:47:48 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.45.203 with HTTP; Thu, 12 Mar 2015 07:47:47 -0700 (PDT)
In-Reply-To: <911A1814-2C2A-41E2-84B5-5B2B2CDB1B8E@vpnc.org>
References: <m2vbi6ju6z.wl-Niall.oReilly@ucd.ie> <7fb23340.93af6.14c0e3c80ef.Coremail.zhengwang09@126.com> <CAMm+LwiPQJ7o-qMayrouHQ9dROuCaiZCiqMmBHwnn-M+n=jdpg@mail.gmail.com> <911A1814-2C2A-41E2-84B5-5B2B2CDB1B8E@vpnc.org>
Date: Thu, 12 Mar 2015 10:47:47 -0400
X-Google-Sender-Auth: QSyCtKUEggKcib9pFVaQz1GIzMA
Message-ID: <CAMm+LwgRKDFQg2FDz=1Eo_DJ9ZF-SEA_96n1j64v536E03NhwQ@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary="001a11c3447ea95ecc051118772c"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/H_GiLosEbeoMjL-m3WTgpwIhrjM>
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] DNS Terminology: Glue
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 12 Mar 2015 14:47:51 -0000

On Thu, Mar 12, 2015 at 10:42 AM, Paul Hoffman <paul.hoffman@vpnc.org>
wrote:

> On Mar 12, 2015, at 6:53 AM, Phillip Hallam-Baker <phill@hallambaker.com>
> wrote:
> > Its a bug in the spec.
>
> The terminology document is the wrong place to deal with bugs in the spec.
> We are happy to list differences of opinion about what a term means if they
> appear in different RFCs, but not to try to fix bugs.
>
> --Paul Hoffman


Maybe.

But what might help clear up some of the confusion would be to redefine
them as pseudo-records rather than DNS RRs.

The problem with glue records is that they are not properly in the DNS name
space. They do not originate from the server that is authoritative for the
zone in question. They cannot and should not be used for any purpose other
than interpreting the zone delegation passed in the same message.


The terminology document might be the wrong place to admit that they are a
bad idea but we can flag them as not being part of the Internet DNS name
space.

v2.23.0 | Report a Bug | By Email