Re: [DNSOP] DNS Terminology: Glue

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 12 March 2015 15:27 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 E8D0A1A8849 for <dnsop@ietfa.amsl.com>; Thu, 12 Mar 2015 08:27:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level:
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] 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 GcuBa8oQAU9L for <dnsop@ietfa.amsl.com>; Thu, 12 Mar 2015 08:27:48 -0700 (PDT)
Received: from 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 BCA871A886E for <dnsop@ietf.org>; Thu, 12 Mar 2015 08:27:46 -0700 (PDT)
Received: from [10.20.30.101] (50-1-99-2.dsl.dynamic.fusionbroadband.com [50.1.99.2]) (authenticated bits=0) by proper.com (8.15.1/8.14.9) with ESMTPSA id t2CFRjWw083530 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Mar 2015 08:27:46 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: proper.com: Host 50-1-99-2.dsl.dynamic.fusionbroadband.com [50.1.99.2] claimed to be [10.20.30.101]
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <m2vbi6ju6z.wl-Niall.oReilly@ucd.ie>
Date: Thu, 12 Mar 2015 08:27:44 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <915A7EEB-CA46-41DC-AAC1-1B26E5BB227C@vpnc.org>
References: <m2vbi6ju6z.wl-Niall.oReilly@ucd.ie>
To: Niall O'Reilly <Niall.oReilly@ucd.ie>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/fhAsontWC-0XEHl0xcspTwp38cs>
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 15:27:49 -0000

On Mar 12, 2015, at 5:07 AM, Niall O'Reilly <Niall.oReilly@ucd.ie> wrote:
>  In http://www.ietf.org/id/draft-hoffman-dns-terminology-02.txt,
>  "glue" is defined as follows.
> 
>   Glue records -- Resource records which are not part of the
>   authoritative data, and are address resource records for the servers
>   listed in the message.  They contain data that allows access to name
>   servers for subzones.  (Definition from RFC 1034, section 4.2.1)
> 
>  Reference to "the message" seems to be a distraction here.  The
>  cited source defines (and motivates) glue records, in a section
>  which specifies "[t]he data that describes a zone", as follows
> 
>   [...] a zone contains "glue" RRs which are not
>   part of the authoritative data, and are address RRs for the servers.
>   These RRs are only necessary if the name server's name is "below" the
>   cut, and are only used as part of a referral response.
> 
>  I think that placing the definition of glue in the scope of "the
>  message" rather than in that of the zone data is likely to lead to
>  confusion.

Quite right. We'll fix this in the next draft.

--Paul Hoffman